US 11689383

US Patent 11689383, titled "System, method, and computer-readable medium for streaming real-time data from a user device," was filed on September 13, 2022, and issued on June 27, 2023. The patent is currently assigned to Carbyne Ltd and lists Alexander DIZENGOF as the inventor.

Abstract:
The patent describes a method for streaming real-time video from a mobile device during an emergency call without requiring a full application download. This involves obtaining the mobile device's phone number during an emergency call conducted over a first connection. A URL link is then transmitted to the mobile device via an electronic message (a second, different connection) using the phone number. When the user clicks this URL, it opens a web browser to establish a WebRTC (Web Real-Time Communication) session for transmitting a real-time video stream. The URL is associated with the phone number. The system receives this real-time video stream through the WebRTC session and sends it to the recipient (e.g., an emergency call center) for display, while audio content of the emergency call is still received through the first connection. The real-time video stream is associated with a unique identifier for the mobile device.

Independent Claims Overview:

• Independent Claim 1 (Method): This claim outlines a method involving several steps. First, it obtains the phone number of a mobile device engaged in an emergency call, where the call is established with a recipient via a "first connection." Next, a URL link is sent to the mobile device through an electronic message (such as a text message) over a "second connection," which is distinct from the first. This electronic message is configured such that a user clicking the URL link will open a web browser on their mobile device—rather than a dedicated application—to initiate a WebRTC session. This WebRTC session is used to transmit a real-time video stream from the mobile device. The URL link is uniquely tied to the mobile device's phone number. Subsequently, the method involves receiving this real-time video stream via the WebRTC session and then sending it to the recipient for display. Crucially, the real-time video stream is received through the WebRTC session concurrently with the audio content of the emergency call being received through the first connection, and the video stream is linked to a unique identifier for the mobile device.

• Independent Claim 8 (System): This claim describes a system that performs the actions outlined in Claim 1. The system comprises processing circuitry and a non-transitory computer-readable medium. This medium stores computing instructions that, when executed by the processing circuitry, enable the system to: obtain a mobile device's phone number during an emergency call over a first connection; transmit a URL link via an electronic message (second, different connection) to the mobile device, allowing a user to click it to access a web browser (not a full application) to establish a WebRTC session for real-time video streaming, with the URL linked to the phone number; receive the real-time video stream through the WebRTC session; and send the video stream to the recipient for display, ensuring the video is received via WebRTC while audio comes through the first connection, and associating the video with a unique identifier for the mobile device.

• Independent Claim 15 (Non-transitory Computer-Readable Medium): This claim defines a non-transitory computer-readable medium that stores instructions. When these instructions are executed by processing circuitry, they cause the processing circuitry to perform the same method steps as described in Claim 1. Specifically, the instructions enable obtaining a mobile device's phone number during an emergency call over a first connection; transmitting a URL link via an electronic message (second, different connection) to the mobile device, allowing a user to click it to access a web browser (instead of a full application) to establish a WebRTC session for real-time video streaming, with the URL linked to the phone number; receiving the real-time video stream through the WebRTC session; and sending the video stream to the recipient for display, while ensuring the video is received via WebRTC concurrently with audio from the first connection, and associating the video with a unique identifier for the mobile device.

Legal Status and Litigation:
US Patent 11689383 is currently Active and is set to expire on November 27, 2037. The patent family is involved in litigation, with the first worldwide family litigation filed. Additionally, a PTAB (Patent Trial and Appeal Board) case, IPR2025-01179, was filed on May 19, 2025, and is currently in a "Pending - Instituted" status. The petitioner in this IPR is Unified Patents. A "Petitioner's Status Report and Update" for IPR2025-01179 was filed on May 13, 2026. No specific dockets for patent 11689383 were found in the CAFC 2026 dockets.

Known litigation involving US patent 11689383 includes one Inter Partes Review (IPR) case before the Patent Trial and Appeal Board (PTAB).

Case Details:

• Plaintiff(s): Unified Patents Inc.
• Defendant(s): Carbyne Ltd. (Patent Owner), Centralsquare Technologies, LLC (Opponent in IPR)
• Jurisdiction: Patent Trial and Appeal Board (PTAB) of the USPTO
• Case Number: IPR2025-01179
• Filing Date: August 12, 2025 (Date IPR trial proceeding filed)
• Outcome or Current Status: Pending - Instituted. The effective date for the institution was June 27, 2025.

Proceedings overview

One active Inter Partes Review (IPR) proceeding has been filed against US patent 11689383. This gives a defendant limited defensive hardening if new assertions are made on previously challenged claims.

IPR2025-01179 — CentralSquare Technologies, LLC v. Carbyne Ltd.

• Type: Inter Partes Review
• Filed: 2025-06-27
• Status: Trial Instituted. The PTAB has decided to proceed with a review of the challenged claims.
• Judge panel: Not publicly available in the provided information for this specific case. However, some PTAB judges active around this time include James A. Tartal, Frances L. Ippolito, Jeffrey N. Fredman, and Ken B. Barrett.
• Petition grounds: Specific claims, prior art, and statutory bases (§ 102 / § 103 / § 112) are not detailed in the provided information.
• Institution decision: Instituted on 2025-06-27. The specific reasoning for institution is not provided in the prompt.
• Final Written Decision (if issued): Not yet issued. The PTAB typically has a one-year deadline from institution to issue a Final Written Decision.
• Settlement / termination: No settlement or termination information is available yet.
• Appeal: No appeal information is available yet, as no Final Written Decision has been issued.
• Defensive value: This active IPR indicates that the patentability of at least some claims is currently being challenged. The outcome will be critical in determining the strength of the patent. If claims are invalidated, it could significantly weaken any assertion built on those claims.

Strategic summary

Currently, there is one active IPR, IPR2025-01179, challenging US patent 11689383. The claims under review in this IPR are currently untested as a Final Written Decision has not yet been issued. Therefore, it is not possible to definitively state which claims are canceled or sustained.

The estoppel landscape will depend on the outcome of IPR2025-01179. If the IPR proceeds to a Final Written Decision, CentralSquare Technologies, LLC (and its privies) would be estopped from asserting invalidity grounds that were raised or reasonably could have been raised in the IPR for any claims ultimately found patentable. For other potential defendants, the specific prior-art grounds challenged in IPR2025-01179 may still be available if they are not in privy with CentralSquare Technologies, LLC.

There is no observable pattern of multiple IPRs filed by the same petitioner, nor is there information about the patent owner's history of appealing PTAB decisions for this specific patent. Unified Patents, Inc. is listed as a plaintiff in the Litigation Summary, and CentralSquare Technologies, LLC is the petitioner for IPR2025-01179, suggesting potential involvement of a defensive aggregator.

Recommended next steps

Since IPR2025-01179 is currently instituted, the next key milestone will be the Final Written Decision, which is typically due within one year of institution (i.e., by approximately 2026-06-27). This decision will determine the patentability of the challenged claims.

Inventors

• Alexander DIZENGOF: CTO at Carbyne Ltd.

Original assignee

The original assignee named on the issued patent US11689383 is Carbyne Ltd.

Carbyne Ltd. is an American and Israeli technology company that develops emergency communication technologies, specifically cloud-based "Next Generation 911" (NG911) solutions. Their platform, Carbyne APEX, unifies voice, live video, text, real-time location, and other data for emergency response. They offer both an app-based service ("C-Now") and an app-free option ("C-Lite") that uses a web browser to stream video and location data.

Carbyne Ltd. was acquired by Axon Enterprise for $625 million in November 2025, with the deal expected to close in the first quarter of 2026. Therefore, its current status is acquired and it operates as a subsidiary of Axon.

Assignment timeline

• 2023-05-09 (executed) / recorded 2023-05-09 — Reel 063585/0787
  • Conveyance: Assignment of Assignor's Interest
  • Assignor: DIZENGOF, ALEXANDER
  • Assignee: CARBYNE LTD., ISRAEL
  • Correspondent: Not specified in available USPTO records.
  • Context: Internal transfer from inventor to the company

Timeline diagram

timeline
    title Ownership of US 11689383
    2017 : Priority date
    2022 : Filed by Carbyne Ltd
    2023 : Inventor assigns to Carbyne Ltd
         : Issued
    2025 : Carbyne acquired by Axon

NPE / troll-pattern signals

1. Shell-entity transfer — Not present. The only assignment recorded is from the inventor to Carbyne Ltd., which is an operating company with a clearly defined product and business model.
2. Known asserter in the chain — Not present. Carbyne Ltd. is an operating company in the emergency communication technology sector. The patent was recently acquired by Axon Enterprise, another operating company. None of the listed assignees are known patent assertion entities like Acacia Research Corp, Marathon Patent Group, Intellectual Ventures, IPNav, Wi-LAN, Mosaid/Conversant, Vringo, Pendrell, or Innovatio IP Ventures. MPHJ Technology is also a known patent troll.
3. Repeat correspondent across the chain — Unclear. Only one assignment is recorded, and the correspondent information is not readily available in the Google Patents record for this specific assignment.
4. Cascading transfers — Not present. Only one assignment from the inventor to the operating company is recorded.
5. Pre-litigation transfer — Not present. The assignment from the inventor to Carbyne Ltd. occurred on May 9, 2023. The IPR was filed on August 12, 2025, which is more than 6 months after the assignment.
6. Bankruptcy fire-sale — Not present. Carbyne Ltd. was acquired by Axon Enterprise in November 2025, not due to bankruptcy.
7. Privateering — Not present. The patent is owned by Carbyne Ltd., an operating company that was acquired by another operating company, Axon Enterprise. There is no indication of transfer to an NPE to assert on Carbyne's behalf.
8. Defensive aggregator (anti-NPE) — Not present. The current assignee, Carbyne Ltd., and its acquirer, Axon Enterprise, are operating companies.

Verdict

Operating-company assertion. The patent is owned by Carbyne Ltd., an operating company that develops emergency communication technologies, and was recently acquired by Axon Enterprise, another operating company in public safety technology. The only recorded assignment is from the inventor to Carbyne Ltd. (Reel 063585/0787, executed and recorded 2023-05-09), indicating a standard transfer to an employer, not a shell entity.

To verify, refer to the USPTO Assignment Center: https://assignmentcenter.uspto.gov/ and search for patent number 11689383.

The following is an analysis of the patent citations listed within US11689383, interpreted as its prior art. A comprehensive determination of anticipation under 35 U.S.C. § 102 for specific claims would require a detailed, claim-by-claim comparison with the full text of each cited patent, which is beyond the scope of this summary. However, a brief description based on the title and a general statement regarding potential relevance is provided for each.

Here are the patent citations for US11689383:

1. US7751826B2

   • Full Citation: US7751826B2
   • Publication/Filing Date: Priority Date: 2002-10-24, Publication Date: 2010-07-06
   • Assignee: Motorola, Inc.
   • Brief Description: Titled "System and method for E911 location privacy protection," this patent generally relates to location privacy in enhanced 911 (E911) systems.
   • Potential Anticipation Relevance: This patent is relevant to the general field of emergency services and location data transmission. It may potentially anticipate aspects related to obtaining and managing location information in emergency calls, but not necessarily the specific method of streaming video via a URL and WebRTC session on a second connection as claimed in US11689383.

2. US20050176441A1

   • Full Citation: US20050176441A1
   • Publication/Filing Date: Priority Date: 2004-02-06, Publication Date: 2005-08-11
   • Assignee: Jurecka Joseph W.
   • Brief Description: Titled "Method and apparatus for locating mobile stations in a wireless telecommunications system," this application describes techniques for determining the location of mobile devices.
   • Potential Anticipation Relevance: This patent may be relevant to the broad concept of mobile device location determination within telecommunication systems, which is a component of emergency services. Its relevance to the specific video streaming method of US11689383 would likely be limited to the collection of location data as a type of real-time data.

3. US20100261492A1

   • Full Citation: US20100261492A1
   • Publication/Filing Date: Priority Date: 2004-08-06, Publication Date: 2010-10-14
   • Assignee: Powerphone, Inc.
   • Brief Description: Titled "Integrated call handler and email systems and methods," this application describes integrating call handling with email systems, potentially for incident reporting or communication.
   • Potential Anticipation Relevance: This patent touches upon integrated communication systems for call centers, but does not appear to directly address real-time video streaming from a mobile device via a web browser and WebRTC initiated by a link on a second connection, as a core element of US11689383.

4. US20070028279A1

   • Full Citation: US20070028279A1
   • Publication/Filing Date: Priority Date: 2005-08-01, Publication Date: 2007-02-01
   • Assignee: Pandoratv Co., Ltd.
   • Brief Description: Titled "System for personal video broadcasting and service method using internet," this application describes a system for broadcasting personal video over the internet.
   • Potential Anticipation Relevance: This patent introduces general concepts of personal video broadcasting over the internet. While it involves video, it does not specifically describe the emergency call context, the use of a second connection for a URL, or WebRTC session via a browser instead of a full application for emergency real-time streaming, as claimed in US11689383.

5. US8145183B2

   • Full Citation: US8145183B2
   • Publication/Filing Date: Priority Date: 2005-09-23, Publication Date: 2012-03-27
   • Assignee: University Of South Florida
   • Brief Description: Titled "On-demand emergency notification system using GPS-equipped devices," this patent describes systems for emergency notifications utilizing GPS data.
   • Potential Anticipation Relevance: This patent covers emergency notification and GPS, which aligns with the emergency context and location data aspects of US11689383. However, it does not appear to detail the specific mechanism of streaming real-time video via a browser-initiated WebRTC session triggered by a link on a second connection.

6. US8270935B2

   • Full Citation: US8270935B2
   • Publication/Filing Date: Priority Date: 2007-12-05, Publication Date: 2012-09-18
   • Assignee: [Apple Inc.](/litigations/by-plaintiff/Apple%20Inc.)
   • Brief Description: Titled "Method and system for prolonging emergency calls," this patent describes techniques related to managing and extending the duration of emergency calls.
   • Potential Anticipation Relevance: This patent addresses the management of emergency calls. Its relevance to US11689383 would be in the general domain of emergency call handling, but it does not specify the method for streaming real-time video from the user device as the core inventive step of US11689383.

7. US20100174560A1

   • Full Citation: US20100174560A1
   • Publication/Filing Date: Priority Date: 2008-03-27, Publication Date: 2010-07-08
   • Assignee: Tom Quan
   • Brief Description: Titled "Method, system and apparatus for assembling data associated with an emergency call event," this application describes compiling various data related to an emergency call.
   • Potential Anticipation Relevance: This patent is relevant to collecting and assembling data during an emergency. While US11689383 also involves collecting data (video, audio, location), the method of initiating and transmitting real-time video via a browser-based WebRTC session on a separate connection is a distinguishing feature.

8. US20100220840A1

   • Full Citation: US20100220840A1
   • Publication/Filing Date: Priority Date: 2009-02-27, Publication Date: 2010-09-02
   • Assignee: Embarq Holdings Company, Llc
   • Brief Description: Titled "Teletypewriter (tty) for communicating pre-stored emergency messages to public safety answering points (psaps)," this application describes TTY communication for PSAPs.
   • Potential Anticipation Relevance: This patent focuses on TTY communication, which is text-based. It does not appear to teach or suggest real-time video streaming from a mobile device via a web browser and WebRTC, as described in US11689383.

9. US20110086607A1

   • Full Citation: US20110086607A1
   • Publication/Filing Date: Priority Date: 2009-10-13, Publication Date: 2011-04-14
   • Assignee: Verizon Patent And Licensing Inc.
   • Brief Description: Titled "Method and apparatus for extended emergency service," this application describes systems for enhanced emergency services.
   • Potential Anticipation Relevance: This patent pertains to extended emergency services broadly. It would need to be thoroughly examined to see if it teaches or implies the specific combination of a second connection for a URL, browser-based WebRTC, and real-time video streaming without a full application, which characterizes US11689383.

10. US20110111726A1

    • Full Citation: US20110111726A1
    • Publication/Filing Date: Priority Date: 2009-11-06, Publication Date: 2011-05-12
    • Assignee: Research In Motion Limited
    • Brief Description: Titled "Location determination for mobile devices in emergency situations," this application describes methods for locating mobile devices during emergencies.
    • Potential Anticipation Relevance: This patent focuses on location determination, similar to US20050176441A1 and US8145183B2. While relevant to emergency services and location data, it does not directly address the real-time video streaming method of US11689383.

11. US8504090B2

    • Full Citation: US8504090B2
    • Publication/Filing Date: Priority Date: 2010-03-29, Publication Date: 2013-08-06
    • Assignee: Motorola Solutions, Inc.
    • Brief Description: Titled "Enhanced public safety communication system," this patent describes various improvements to public safety communication systems.
    • Potential Anticipation Relevance: This patent is broadly related to enhanced public safety communication. A detailed analysis would be needed to ascertain if any specific claims within US11689383, particularly those regarding browser-based WebRTC video streaming from a link on a second connection, are anticipated.

12. US20120027189A1

    • Full Citation: US20120027189A1
    • Publication/Filing Date: Priority Date: 2010-07-28, Publication Date: 2012-02-02
    • Assignee: Cisco Technology, Inc.
    • Brief Description: Titled "Call to Call Center as Trigger to Capture and Record Other Geographically Relevant Data," this application describes using a call to a call center as a trigger to capture additional geographically relevant data.
    • Potential Anticipation Relevance: This patent covers the concept of triggering data capture based on a call. While it includes "geographically relevant data," it doesn't specify real-time video streaming initiated by a URL via a browser and WebRTC on a different connection, as is central to US11689383.

13. US20120149324A1

    • Full Citation: US20120149324A1
    • Publication/Filing Date: Priority Date: 2010-12-14, Publication Date: 2012-06-14
    • Assignee: At&T Mobility Ii Llc
    • Brief Description: Titled "Provision of text messages to emergency call takers," this application describes providing text messages to emergency call takers.
    • Potential Anticipation Relevance: This patent focuses on text messaging in emergency contexts. While US11689383 uses electronic messages (like text messages) to send the URL, the core invention of real-time video streaming via WebRTC through a browser is not addressed.

14. US20120190384A1

    • Full Citation: US20120190384A1
    • Publication/Filing Date: Priority Date: 2011-01-26, Publication Date: 2012-07-26
    • Assignee: The Goodyear Tire & Rubber Company
    • Brief Description: Titled "Management of roadside service requests," this application describes systems for managing roadside assistance requests.
    • Potential Anticipation Relevance: This patent is in a different domain (roadside assistance) and does not appear to be relevant to the specific technical solution for emergency video streaming described in US11689383.

15. US20120202447A1

    • Full Citation: US20120202447A1
    • Publication/Filing Date: Priority Date: 2011-02-07, Publication Date: 2012-08-09
    • Assignee: Qualcomm Incorporated
    • Brief Description: Titled "Method and/or Apparatus for Location Privacy Via Uniform Resource Identifier Provisioning," this application describes managing location privacy using URIs.
    • Potential Anticipation Relevance: This patent relates to location privacy and URIs, which has some overlap with US11689383's use of a URL. However, its focus on privacy and lack of mention of real-time video streaming, WebRTC, or browser-based initiation without a full application means it likely doesn't anticipate the core claims of US11689383.

16. US20140007158A1

    • Full Citation: US20140007158A1
    • Publication/Filing Date: Priority Date: 2012-06-29, Publication Date: 2014-01-02
    • Assignee: Cable Television Laboratories, Inc.
    • Brief Description: Titled "Emergency alert system (eas) alert generation," this application describes generating alerts for emergency alert systems.
    • Potential Anticipation Relevance: This patent deals with emergency alerts. It is not directly related to real-time video streaming from a user device to a call center in the manner described by US11689383.

17. US9167379B1

    • Full Citation: US9167379B1
    • Publication/Filing Date: Priority Date: 2012-12-17, Publication Date: 2015-10-20
    • Assignee: Tritech Software Systems
    • Brief Description: Titled "Automatic location-based emergency response system," this patent describes an automated system for emergency response based on location.
    • Potential Anticipation Relevance: This patent addresses automatic location-based emergency response. While location is a component of US11689383's broader data streaming, the core inventive step of video streaming via WebRTC through a browser is not present.

18. US8976939B1

    • Full Citation: US8976939B1
    • Publication/Filing Date: Priority Date: 2013-01-29, Publication Date: 2015-03-10
    • Assignee: Tritech Software Systems
    • Brief Description: Titled "Prioritization of emergency calls," this patent describes methods for prioritizing emergency calls.
    • Potential Anticipation Relevance: This patent deals with call prioritization, a different aspect of emergency response than the real-time video streaming method of US11689383.

19. US9420116B1

    • Full Citation: US9420116B1
    • Publication/Filing Date: Priority Date: 2013-01-29, Publication Date: 2016-08-16
    • Assignee: Tritech Software Systems
    • Brief Description: Also titled "Prioritization of emergency calls," similar to US8976939B1.
    • Potential Anticipation Relevance: Similar to US8976939B1, this patent focuses on call prioritization and does not appear to anticipate the specific video streaming mechanism of US11689383.

20. US20160014585A1

    • Full Citation: US20160014585A1
    • Publication/Filing Date: Priority Date: 2013-02-28, Publication Date: 2016-01-14
    • Assignee: Anand SUNDARARAJ
    • Brief Description: Titled "Method and system for optimal emergency communication," this application describes optimizing emergency communication.
    • Potential Anticipation Relevance: This patent broadly covers optimal emergency communication. A detailed review would be needed, but its title does not suggest the specific browser-based WebRTC video streaming aspects of US11689383.

21. WO2014158562A1

    • Full Citation: WO2014158562A1
    • Publication/Filing Date: Priority Date: 2013-03-13, Publication Date: 2014-10-02
    • Assignee: Echostar Technologies L.L.C.
    • Brief Description: Titled "Systems and methods for securely providing adaptive bit rate streaming media content on-demand," this international application describes secure adaptive bit rate streaming.
    • Potential Anticipation Relevance: This patent is relevant to adaptive bit rate streaming of media. While US11689383 involves streaming, the context of emergency services, the use of a second connection for a URL, and WebRTC through a browser without a full application are key distinctions.

22. US9792654B1

    • Full Citation: US9792654B1
    • Publication/Filing Date: Priority Date: 2013-03-15, Publication Date: 2017-10-17
    • Assignee: United Services Automobile Association (Usaa)
    • Brief Description: Titled "Insurance claim processing via streaming video," this patent describes using streaming video for insurance claim processing.
    • Potential Anticipation Relevance: This patent involves streaming video, but in the context of insurance claims, not emergency services. It is unlikely to anticipate the specific claims of US11689383 related to emergency call handling, separate connections, and browser-initiated WebRTC for public safety.

23. US20140293046A1

    • Full Citation: US20140293046A1
    • Publication/Filing Date: Priority Date: 2013-03-26, Publication Date: 2014-10-02
    • Assignee: Verizon Patent And Licensing Inc.
    • Brief Description: Titled "Web based security system," this application describes a security system that is web-based.
    • Potential Anticipation Relevance: This patent broadly relates to web-based security systems. While it involves web technology, its focus on "security system" may not align with the specific real-time video streaming in an emergency call context as detailed in US11689383, particularly regarding WebRTC and the second connection method.

24. WO2014182638A2

    • Full Citation: WO2014182638A2
    • Publication/Filing Date: Priority Date: 2013-05-04, Publication Date: 2014-11-13
    • Assignee: Christopher Decharms
    • Brief Description: Titled "Mobile security technology," this international application describes technology for mobile security.
    • Potential Anticipation Relevance: This patent refers to general mobile security technology. Without further details, it's difficult to assess its relevance to the specific video streaming mechanism of US11689383, but the title alone does not suggest anticipation of the core claims.

25. EP2992692A2

    • Full Citation: EP2992692A2
    • Publication/Filing Date: Priority Date: 2013-05-04, Publication Date: 2016-03-09
    • Assignee: DECHARMS, Christopher
    • Brief Description: Titled "Mobile security technology," this European application appears to be a family member of WO2014182638A2.
    • Potential Anticipation Relevance: Similar to WO2014182638A2, its relevance to the specific video streaming invention of US11689383 is unlikely to be direct based on the title.

26. US9414225B2

    • Full Citation: US9414225B2
    • Publication/Filing Date: Priority Date: 2013-07-23, Publication Date: 2016-08-09
    • Assignee: Broadcom Corporation
    • Brief Description: Titled "User equipment having web real time communication architecture," this patent describes user equipment with WebRTC architecture.
    • Potential Anticipation Relevance: This patent is highly relevant as it explicitly mentions "Web Real Time Communication architecture" in user equipment. It potentially anticipates the use of WebRTC for real-time communication from a mobile device. However, US11689383's claims include specific elements such as initiating the WebRTC session via a URL in an electronic message on a second connection and using a web browser instead of a full application in an emergency call context, which would require a detailed comparison to determine if US9414225B2 fully discloses these aspects.

27. US20150056946A1

    • Full Citation: US20150056946A1
    • Publication/Filing Date: Priority Date: 2013-08-21, Publication Date: 2015-02-26
    • Assignee: Tritech Software Systems
    • Brief Description: Titled "Sms communication during emergencies," this application describes using SMS for communication during emergencies.
    • Potential Anticipation Relevance: This patent is relevant to SMS communication in emergencies. While US11689383 uses SMS (or similar) to transmit the URL, this patent does not describe the subsequent real-time video streaming via WebRTC through a browser.

28. US9301117B2

    • Full Citation: US9301117B2
    • Publication/Filing Date: Priority Date: 2013-08-21, Publication Date: 2016-03-29
    • Assignee: Tritech Software Systems
    • Brief Description: Titled "SMS communication during emergencies," this patent appears to be a granted version of US20150056946A1.
    • Potential Anticipation Relevance: Similar to US20150056946A1, its relevance is to SMS in emergencies, not the video streaming aspect of US11689383.

29. US20150099482A1

    • Full Citation: US20150099482A1
    • Publication/Filing Date: Priority Date: 2013-10-09, Publication Date: 2015-04-09
    • Assignee: SWN Communications, Inc.
    • Brief Description: Titled "System and method for two-way message transmission on mobile platforms for emergency and non-emergency communications," this application describes two-way messaging for emergency and non-emergency communications.
    • Potential Anticipation Relevance: This patent describes two-way messaging. While it is in the emergency communication domain, it does not specifically describe real-time video streaming via WebRTC through a browser initiated by a URL on a separate connection as in US11689383.

30. US20150106528A1

    • Full Citation: US20150106528A1
    • Publication/Filing Date: Priority Date: 2013-10-15, Publication Date: 2015-04-16
    • Assignee: Verizon Patent And Licensing Inc.
    • Brief Description: Titled "Communication of data of a web real-time communication via a carrier-grade environment," this application describes WebRTC data communication in a carrier-grade environment.
    • Potential Anticipation Relevance: This patent is highly relevant as it explicitly mentions "Web Real-Time Communication" for data communication. It may anticipate aspects of using WebRTC. The distinction for US11689383 would lie in the specific initiation mechanism (URL in electronic message on a second connection) and the explicit instruction for a web browser instead of a full application in an emergency call context for video streaming. This citation is marked with an asterisk (*), indicating it was cited by the examiner, suggesting its high relevance.

31. US20170126751A1

    • Full Citation: US20170126751A1
    • Publication/Filing Date: Priority Date: 2014-06-26, Publication Date: 2017-05-04
    • Assignee: Unify Gmbh & Co. Kg
    • Brief Description: Titled "Method for establishing a communication connection which is suitable for transmitting media streams between a first rtc client and a second rtc client," this application describes establishing communication for media streams between RTC clients.
    • Potential Anticipation Relevance: This patent is relevant to establishing connections for media streams between "RTC clients," which could include WebRTC. It potentially anticipates the general concept of real-time media streaming. However, the unique aspects of US11689383, such as the emergency context, the specific URL-based initiation via a separate connection to a web browser, and avoiding a full application, would need careful comparison.

32. US20160088455A1

    • Full Citation: US20160088455A1
    • Publication/Filing Date: Priority Date: 2014-09-19, Publication Date: 2016-03-24
    • Assignee: Rapidsos, Inc.
    • Brief Description: Titled "Method and system for emergency call management," this application describes methods and systems for managing emergency calls.
    • Potential Anticipation Relevance: This patent is in the emergency call management domain. While broadly related, the title does not indicate the specific real-time video streaming mechanism via WebRTC through a browser as taught by US11689383.

33. US20170164175A1

    • Full Citation: US20170164175A1
    • Publication/Filing Date: Priority Date: 2014-09-19, Publication Date: 2017-06-08
    • Assignee: Rapidsos, Inc.
    • Brief Description: Also titled "Method and system for emergency call management," this appears to be a continuation or related application to US20160088455A1.
    • Potential Anticipation Relevance: Similar to US20160088455A1, its direct relevance to the video streaming specifics of US11689383 is not evident from the title.

34. US20160037126A1

    • Full Citation: US20160037126A1
    • Publication/Filing Date: Priority Date: 2014-10-21, Publication Date: 2016-02-04
    • Assignee: Livegenic Inc.
    • Brief Description: Titled "Real-Time Visual Customer Support Enablement System and Method," this application describes a system for real-time visual customer support.
    • Potential Anticipation Relevance: This patent is highly relevant due to "Real-Time Visual ... System and Method." While in the "customer support" context rather than emergency services, it involves real-time visual streaming. A detailed analysis would be required to see if it teaches the specific initiation method (URL via electronic message on a second connection, opening in a browser instead of a full application) and WebRTC for emergency response, as claimed by US11689383.

35. US20160337831A1

    • Full Citation: US20160337831A1
    • Publication/Filing Date: Priority Date: 2015-05-15, Publication Date: 2016-11-17
    • Assignee: Rave Wireless, Inc.
    • Brief Description: Titled "Real-time over the top 9-1-1 caller location data," this application describes real-time location data for 9-1-1 callers.
    • Potential Anticipation Relevance: This patent is directly related to 9-1-1 and real-time data, specifically location. It potentially anticipates the real-time data aspect within an emergency context. However, it focuses on location and doesn't explicitly mention real-time video streaming via WebRTC through a browser initiated by a URL on a second connection, as distinct in US11689383. This citation is marked with an asterisk (*), indicating it was cited by the examiner, suggesting its high relevance.

36. US20160381091A1

    • Full Citation: US20160381091A1
    • Publication/Filing Date: Priority Date: 2015-06-27, Publication Date: 2016-12-29
    • Assignee: Avaya Inc.
    • Brief Description: Titled "System and method for managing multi-modal communication sessions," this application describes managing communication sessions with multiple modes (e.g., voice, video, text).
    • Potential Anticipation Relevance: This patent is relevant to managing multi-modal communication, which could encompass voice and video. The general concept of combining different media types is present. However, the specific initiation method for video (URL in electronic message, browser-based WebRTC without full application) in an emergency context, which is key to US11689383, would need specific comparison.

37. US20170034353A1

    • Full Citation: US20170034353A1
    • Publication/Filing Date: Priority Date: 2015-07-29, Publication Date: 2017-02-02
    • Assignee: Genesys Telecommunications Laboratories, Inc.
    • Brief Description: Titled "System and method for dynamic call diversion," this application describes dynamically diverting calls.
    • Potential Anticipation Relevance: This patent concerns call diversion, a different functional aspect of call centers than the real-time video streaming mechanism of US11689383.

38. US20170124853A1

    • Full Citation: US20170124853A1
    • Publication/Filing Date: Priority Date: 2015-11-02, Publication Date: 2017-05-04
    • Assignee: Rapidsos, Inc.
    • Brief Description: Titled "Method and system for situational awareness for emergency response," this application describes systems for providing situational awareness in emergency response.
    • Potential Anticipation Relevance: This patent addresses situational awareness for emergency response, which aligns with the overall goal of US11689383. However, the specific technical means of achieving this through browser-based WebRTC video streaming initiated by a URL on a second connection needs to be thoroughly checked against this prior art.

39. US20170180964A1

    • Full Citation: US20170180964A1
    • Publication/Filing Date: Priority Date: 2015-12-17, Publication Date: 2017-06-22
    • Assignee: Rapidsos, Inc.
    • Brief Description: Titled "Devices and methods for efficient emergency calling," this application describes efficient emergency calling.
    • Potential Anticipation Relevance: This patent broadly covers efficient emergency calling. Its specific relevance to the unique video streaming method of US11689383 cannot be determined from the title alone.

40. US20190052474A1

    • Full Citation: US20190052474A1
    • Publication/Filing Date: Priority Date: 2017-08-13, Publication Date: 2019-02-14
    • Assignee: Carbyne Ltd.
    • Brief Description: Titled "Method for streaming real-time data from a user device to a dispatch unit terminal," this is an earlier publication of an application by the same assignee and inventor as US11689383, sharing the same priority date. This is a family member.
    • Potential Anticipation Relevance: As a family member with the same priority date, this document is not prior art under 35 U.S.C. § 102 against US11689383, but rather describes closely related subject matter.

41. US10686618B2

    • Full Citation: US10686618B2
    • Publication/Filing Date: Priority Date: 2017-08-13, Publication Date: 2020-06-16
    • Assignee: Carbyne Ltd.
    • Brief Description: Titled "Method for streaming real-time data from a user device to a dispatch unit terminal," this is a granted patent by the same assignee and inventor as US11689383, sharing the same priority date. This is a family member. In the parentage information of US11689383, it explicitly states that US11689383 is a continuation of U.S. patent application Ser. No. 17/492,757, which is a continuation of U.S. patent application Ser. No. 16/901,074, which is a continuation of U.S. patent application Ser. No. 15/822,927, now U.S. Pat. No. 10,686,618.
    • Potential Anticipation Relevance: As a family member with the same priority date, this document is not prior art under 35 U.S.C. § 102 against US11689383, but rather describes closely related subject matter from the same inventive lineage.

42. US20200313922A1

    • Full Citation: US20200313922A1
    • Publication/Filing Date: Priority Date: 2017-08-13, Publication Date: 2020-10-01
    • Assignee: Carbyne Ltd.
    • Brief Description: Titled "Method for streaming real-time data from a user device to a dispatch unit terminal," this is an earlier publication by the same assignee and inventor as US11689383, sharing the same priority date. This is a family member.
    • Potential Anticipation Relevance: As a family member with the same priority date, this document is not prior art under 35 U.S.C. § 102 against US11689383, but rather describes closely related subject matter.

The most relevant prior art, based on their titles and examiner citations (marked with *), appear to be:

• US9414225B2 (Broadcom Corporation): Explicitly mentions "Web Real Time Communication architecture."
• US20150106528A1 (Verizon Patent And Licensing Inc.): Explicitly mentions "Web Real-Time Communication" for data communication in a carrier-grade environment, and was cited by the examiner.
• US20160337126A1 (Livegenic Inc.): Mentions "Real-Time Visual Customer Support," indicating real-time video streaming capabilities.
• US20160337831A1 (Rave Wireless, Inc.): Directly relates to "Real-time over the top 9-1-1 caller location data" and was cited by the examiner, indicating relevance to real-time data in an emergency context.

These patents and applications would require thorough analysis to determine the extent to which they anticipate or render obvious the claims of US11689383, particularly regarding the specific combination of features related to initiating a WebRTC video stream via a URL in an electronic message on a second connection that accesses a web browser instead of a full application during an emergency call.

Obviousness Analysis of US Patent 11689383 under 35 U.S.C. § 103

This analysis assesses the obviousness of US Patent 11689383, titled "System, method, and computer-readable medium for streaming real-time data from a user device," by combining elements from existing prior art references. The focus will be on Independent Claim 1, with the understanding that Independent Claims 8 and 15, which describe a corresponding system and computer-readable medium, would be similarly rendered obvious. The priority date of US11689383 is August 13, 2017.

Independent Claim 1 Elements:

Independent Claim 1 of US11689383 describes a method comprising the following key elements:

• [1a] Obtaining a phone number of a mobile device used by a user making an emergency call.
• [1b] The emergency call is conducted with a recipient through a first connection.
• [1c] Transmitting a URL link to the mobile device through an electronic message.
• [1d] The electronic message is transmitted through a second connection using the phone number, wherein the second connection is different from the first connection.
• [1e] The electronic message allows the user to click on the URL link to access a web browser on the mobile device, instead of a full application on the mobile device, to establish a WebRTC session.
• [1f] The WebRTC session is used to transmit a real-time video stream from the mobile device.
• [1g] The URL link is associated with the phone number of the mobile device.
• [1h] Receiving the real-time video stream from the mobile device through the WebRTC session.
• [1i] Sending the real-time video stream to the recipient for display on a screen of the recipient.
• [1j] The real-time video stream is received through the WebRTC session while audio content of the emergency call is received through the first connection.
• [1k] The real-time video stream is associated with a unique identifier for the mobile device.

Identified Prior Art References:

To demonstrate obviousness, the following prior art references, which predate the August 13, 2017, priority date of US11689383, are considered:

1. US9113030B2 (Verizon Patent And Licensing Inc.): Titled "Multimedia-enhanced emergency call systems," granted on August 18, 2015, with a priority date of July 25, 2013. This patent describes systems for providing multimedia data, including streaming video, from a mobile device to a Public Safety Answering Point (PSAP) or emergency call center during an emergency call.
2. US20150106528A1 (Verizon Patent And Licensing Inc.): Titled "Communication of data of a web real-time communication via a carrier-grade environment," published on April 16, 2015, with a priority date of October 15, 2013. This publication details the use of WebRTC for real-time communication, including voice and video calls, within a web browser.
3. US20120202447A1 (Qualcomm Incorporated): Titled "Method and/or Apparatus for Location Privacy Via Uniform Resource Identifier Provisioning," published on August 9, 2012, with a priority date of February 7, 2011. This publication teaches the use of an electronic message, such as SMS, to provision a URL on a mobile device, which, when accessed, causes the mobile device to access a webpage.

Obviousness Combination and Motivation:

A person having ordinary skill in the art (POSA) at the time of the invention (i.e., by August 2017) would have found it obvious to combine the teachings of US9113030B2, US20150106528A1, and US20120202447A1 to arrive at the invention claimed in US11689383. The motivation for such a combination would be to enhance emergency response capabilities by providing real-time visual information to emergency operators efficiently and without requiring users to install specialized applications, addressing known challenges in emergency communication.

Element-by-Element Analysis:

• [1a] Obtaining a phone number & [1b] Emergency call through a first connection: US9113030B2 explicitly discloses "multimedia-enhanced emergency call systems" that receive emergency calls from mobile devices. The abstract describes "receiving multimedia data from a mobile device of a caller during an emergency call conducted with a public safety answering point (PSAP)." This inherently involves obtaining the caller's phone number and conducting the emergency call (typically a voice call) over a first connection, such as a cellular network.

• [1c] Transmitting a URL link through an electronic message & [1d] Second connection different from the first: US9113030B2 teaches that a PSAP can send a "call-back number or text message" to the mobile device of a caller. While not explicitly a URL, it establishes the use of a second, different connection (e.g., SMS for a text message) to communicate with the mobile device during an emergency call. US20120202447A1 directly teaches sending a "short message service (SMS) message, electronic mail (email), or other appropriate mechanism may be used to provision a URL on the mobile device." A POSA would have been motivated to combine the concept of sending an electronic message during an emergency call (from US9113030B2) with the proven method of embedding a URL in such a message to initiate a web action (from US20120202447A1). The SMS message constitutes a second connection, distinct from the voice call of the first connection.

• [1e] Click URL to access web browser (instead of full app) to establish WebRTC session & [1f] Transmit real-time video stream via WebRTC: US20150106528A1 extensively describes WebRTC as enabling "web applications and sites to capture and optionally stream audio and/or video media". It explicitly states that "WebRTC typically enables real-time communication between browsers (e.g., peer-to-peer)" and can be used for "a video call". The advantage of WebRTC is that it operates natively within a web browser, eliminating the need for a user to download and install a "full application" to stream real-time video. A POSA, recognizing the critical time savings and ease of use in emergency situations (as articulated in the background of US11689383, which states, "these proposed systems require a user to download and install specialized applications, which may take time, losing precious moments of data" [cite: US11689383, Description]), would be strongly motivated to leverage WebRTC via a browser to provide video streaming. Initiating this browser-based WebRTC session via a clicked URL in an SMS message (as taught by US20120202447A1) would be a natural combination to achieve this benefit.

• [1g] URL link associated with phone number & [1k] Real-time video stream associated with unique identifier: US9113030B2 discusses associating multimedia content with the emergency call. In the context of a web-based session initiated by a URL sent to a specific phone number, embedding the phone number or a related unique identifier within the URL itself, or using it to generate a session identifier, would be a standard and obvious practice for a POSA to maintain the association between the streaming video and the ongoing emergency call. The patent US11689383 itself states, "the URL is associated with the phone number of the mobile device." [cite: US11689383, Abstract] and "the unique identifier may be the suffix of the URL, referencing a web address of the call center connected to the UD." [cite: US11689383, Description].

• [1h] Receiving real-time video stream & [1i] Sending to recipient for display: US9113030B2 discloses "receiving multimedia data from a mobile device... and providing the multimedia data to the PSAP for display on a user interface." Given that US20150106528A1 teaches WebRTC for video communication, the act of receiving and displaying the video stream from the WebRTC session at the recipient's end would be a direct and obvious outcome of the combined system.

• [1j] Video via WebRTC while audio via first connection: US9113030B2 describes handling both the voice call (first connection) and separate multimedia data (streaming video) from the mobile device to the PSAP. The concurrent reception of audio via the initial emergency call connection and video via the newly established WebRTC session, and then presenting them to the recipient, is an obvious design choice for a POSA seeking to provide comprehensive situational awareness to emergency responders. This integration enhances the existing multimedia emergency call systems by using WebRTC for the video component.

Conclusion

The combination of US9113030B2, US20150106528A1, and US20120202447A1 would have rendered Independent Claim 1, and by extension, Claims 8 and 15, of US11689383 obvious to a person having ordinary skill in the art at the time of the invention. The motivation for combining these references stems from the clear advantages of providing real-time video to emergency services, the known technical capabilities of WebRTC for browser-based streaming without dedicated applications, and the common practice of using URL links in electronic messages to initiate web interactions, all aimed at improving the efficiency and effectiveness of emergency response.

To determine the full details regarding patent term adjustments (PTA), patent term extensions (PTE), continuation and divisional applications, related family members, and the projected expiration date for US Patent 11689383, a direct search of the USPTO database (Patent Center) is necessary. Unfortunately, I do not have direct, real-time access to the USPTO's Patent Center to pull up all this specific information for the given patent number. While I can access general information about the patent via Google Patents, the USPTO provides the authoritative and most detailed records for these legal and application-specific aspects.

However, based on the information provided in the prompt and general patent law, I can offer some insights and explain what would be found through a USPTO search:

Patent Term Adjustment (PTA) and Patent Term Extension (PTE):

• PTA: Patent Term Adjustment is granted to compensate for certain delays caused by the USPTO during the prosecution of a patent application. It adds days to the patent's term. The USPTO calculates PTA, and this information would be available in the patent's file history on Patent Center.
• PTE: Patent Term Extension is distinct from PTA and primarily addresses delays due to regulatory review processes (e.g., FDA approval) for products like drugs, medical devices, and food additives. It is also calculated and managed by the USPTO. For US11689383, which pertains to a system for streaming real-time data, PTE is less likely to be applicable unless the system's deployment is subject to a specific regulatory approval process.

Continuation Applications, Divisional Applications, and Related Family Members:
The provided "Family Applications" and "Priority Applications" sections already list this information.

• Priority Applications (claims benefit of these):

  • US17/943,956 (the application that matured into US11689383B2)
  • U.S. patent application Ser. No. 17/492,757, filed on Oct. 4, 2021
  • U.S. patent application Ser. No. 16/901,074, filed on Jun. 15, 2020, now U.S. Pat. No. 11,139,996
  • U.S. patent application Ser. No. 15/822,927, filed on Nov. 27, 2017, now U.S. Pat. No. 10,686,618
  • U.S. Provisional Application No. 62/544,835, filed on Aug. 13, 2017.

• Applications Claiming Priority (descendants):

  • US17/943,956 (this patent, also listed as a priority application for itself)
  • US18/195,257 (US12309207B2)
  • US19/212,069 (US20250280044A1)

• Related Parent Applications (from which this application claims benefit):

  • US17/492,757 (Continuation of)

• Related Child Applications (claiming priority from this application):

  • US18/195,257 (Continuation of)

• Family Applications: The patent family includes several US applications that are active, along with two EP applications (EP3445016B2 and EP4007324A1).

Projected Expiration Date:
The patent document explicitly states that US11689383 is Active and expires 2037-11-27. This "Adjusted expiration" date already accounts for any Patent Term Adjustment (PTA) if applicable.

The general rule for patent term is 20 years from the earliest non-provisional filing date. Given the priority date of August 13, 2017, a simple 20-year term would typically extend to August 13, 2037. The stated expiration date of November 27, 2037 suggests that there has been a Patent Term Adjustment of approximately 3 months and 14 days (November 27th minus August 13th). A definitive calculation and breakdown of this PTA would be found in the patent's file wrapper on the USPTO Patent Center.

Defensive Disclosure: Derivatives of US Patent 11689383

This document provides technical disclosures of derivative variations and combinations of the invention described in US Patent 11689383, "System, method, and computer-readable medium for streaming real-time data from a user device." The aim is to establish prior art that renders obvious or non-novel future incremental improvements by competitors. This analysis focuses on extrapolating from the core concepts of transmitting a URL via a second connection to initiate a browser-based WebRTC video stream from a mobile device to a recipient during an emergency call, while audio continues on a first connection.

Derivative Variations based on Core Claims (referencing Claim 1 implicitly)

The following derivatives expand upon the method, system, and computer-readable medium aspects of US11689383.

---

1. Material & Component Substitution: Satellite Network for First Connection and Data Link

• Enabling Description: The primary communication pathways for both the "first connection" (emergency voice call) and the "second connection" (electronic message carrying the URL link) are implemented over a satellite communication network. This requires the mobile device to possess integrated satellite communication capabilities (e.g., Iridium, Globalstar, or Starlink direct-to-cell compatibility). The emergency call's audio content is transmitted via the satellite voice channel, while the URL link is delivered via a satellite data burst message (e.g., Short Burst Data, SMS over satellite, or a low-bandwidth IP over satellite connection). The subsequent WebRTC session for real-time video streaming from the mobile device is established over the satellite data link, routed through a satellite ground station acting as an intermediary and WebRTC signaling server. The recipient's dispatch unit terminal (DUT) integrates a satellite modem and associated communication gateway for direct receipt and processing of both the satellite-relayed audio and video streams. This configuration specifically addresses emergency scenarios in areas devoid of terrestrial cellular or internet infrastructure, such as remote wilderness, maritime environments, or disaster-stricken regions.
• Mermaid Diagram:

  sequenceDiagram
      actor UserDevice: Mobile Device (Satellite-enabled)
      participant SatNetwork: Satellite Network
      participant Server: Server (Satellite Gateway)
      participant CallCenter: Call Center / Recipient
  
      UserDevice->>SatNetwork: Initiate Emergency Call (Audio - First Connection via Satellite Voice)
      SatNetwork->>CallCenter: Route Emergency Call
      activate CallCenter
      activate SatNetwork
  
      Server->>UserDevice: Transmit URL (Satellite Data Burst - Second Connection)
      activate Server
      UserDevice->>UserDevice: User Clicks URL, Launches Browser
      UserDevice->>SatNetwork: Establish WebRTC Session (Video Stream via Satellite Data)
      SatNetwork->>Server: Route WebRTC Video Stream
      Server->>CallCenter: Send Real-time Video Stream
      deactivate SatNetwork
      deactivate Server
      deactivate CallCenter
  

---

2. Material & Component Substitution: Specialized Low-Latency Hardware-Accelerated Video Encoder/Decoder

• Enabling Description: To minimize end-to-end latency and improve video quality under varied network conditions, the mobile device is equipped with a dedicated, low-power hardware-accelerated video encoder, such as an ASIC-based H.265 (HEVC) or AV1 encoder. This hardware encoder directly interfaces with the mobile device's camera sensor and is exposed to the WebRTC API via a browser extension, WebAssembly module, or direct operating system integration, allowing the browser to leverage it for real-time video compression. Concurrently, the recipient's dispatch unit terminal (DUT) incorporates a corresponding hardware-accelerated H.265/AV1 video decoder. This dedicated decoder offloads video processing from the general-purpose CPU, enabling rapid decoding and display of the incoming real-time video stream with sub-100ms processing latency. This specialized hardware approach ensures high-fidelity, ultra-low latency video transmission critical for dynamic emergency situations, even on computationally limited mobile devices and high-throughput dispatch systems.
• Mermaid Diagram:

  flowchart TD
      subgraph Mobile Device
          UD_Cam[Camera Sensor] --Raw Video--> UD_HW_Encoder[Hardware HEVC/AV1 Encoder]
          UD_HW_Encoder --Encoded Video (Low Latency)--> UD_Browser[Web Browser (WebRTC)]
          UD_Browser --WebRTC Stream--> Network
      end
  
      Network --WebRTC Stream--> Server[Server (Optional Transcoding)]
      Server --WebRTC Stream--> Recipient_DUT[Recipient DUT]
  
      subgraph Recipient DUT
          Recipient_DUT --WebRTC Stream--> DUT_HW_Decoder[Hardware HEVC/AV1 Decoder]
          DUT_HW_Decoder --Decoded Video (Sub-100ms)--> DUT_Display[Display Screen]
          DUT_Audio[Audio (First Connection)] --Synchronize--> DUT_Display
      end
  

---

3. Operational Parameter Expansion: High-Resolution, Multi-Spectral Video for Industrial Incident Response

• Enabling Description: The real-time data stream is expanded to include high-resolution (e.g., 4K or 8K UHD) video captured by a specialized mobile device, integrated with multi-spectral imaging capabilities (e.g., near-infrared, thermal, ultraviolet bands). This mobile device could be a ruggedized smartphone with attachable or built-in multi-spectral sensors. The WebRTC session is configured to transmit these multiple video channels (visible light + spectral bands) using advanced, high-efficiency codecs such as AV1 or VVC (Versatile Video Coding), with adaptive bitrate streaming to accommodate varying network capacities. The recipient's dispatch unit terminal in an industrial or HAZMAT response center features a multi-spectral display capable of rendering and false-coloring these additional spectral data streams. This allows operators to detect specific chemical signatures, heat anomalies, or structural damage invisible to the naked eye, providing unprecedented situational awareness for industrial accidents or environmental hazards. The system dynamically adjusts which spectral channels are transmitted based on incident type and available bandwidth.
• Mermaid Diagram:

  graph TD
      A[Mobile Device (Multi-Spectral Camera)] --Captures--> B{Raw Multi-Spectral Video Data (4K/8K)}
      B --Encoded (AV1/VVC, Multi-Channel)--> C[Web Browser (WebRTC Session)]
      C --Stream (High Bandwidth/Adaptive)--> D[Network]
      D --Stream--> E[Server (Adaptive Streaming / Transcoding)]
      E --Stream--> F[Recipient DUT (Multi-Spectral Display)]
      F --Renders--> G{Detailed Multi-Spectral Incident View}
  
      subgraph Real-time Data Flow
          B --> C
          C --> D
          D --> E
          E --> F
      end
  

---

4. Operational Parameter Expansion: Ultra-Low Bandwidth Stills and Metadata for Remote Disaster Zones

• Enabling Description: For environments with severely compromised or extremely limited network connectivity (e.g., remote disaster zones, deep rural areas), the system automatically defaults to an ultra-low bandwidth mode. In this mode, continuous real-time video streaming is replaced by the transmission of highly compressed still images (e.g., JPEG 2000, WebP, or AVIF) captured at a reduced frequency (e.g., one image every 5-30 seconds). Each still image is transmitted via the WebRTC data channel and is meticulously interleaved with essential metadata: high-precision GPS coordinates, barometric altitude, device orientation (compass heading), timestamp, battery status, and ambient environmental sensor readings (temperature, humidity, air pressure, CO2 levels from mobile device sensors). The recipient's dispatch terminal processes these intermittent data packets, reconstructing a visual timeline from the stills and dynamically overlaying the sensor and location data on a geospatial mapping interface. This "telemetry-rich still image stream" provides crucial, bandwidth-efficient situational awareness where continuous video is infeasible.
• Mermaid Diagram:

  sequenceDiagram
      actor MobileDevice: User Device (Ultra-Low Bandwidth Mode)
      participant Network: Constrained Network (e.g., LEO Satellite, Mesh, HF Radio Link)
      participant Server: Server (Data Aggregation & Reconstruction)
      participant Recipient: Dispatch Unit Terminal
  
      MobileDevice->>Network: Emergency Call (Audio - First Conn. - degraded)
      Note over MobileDevice,Network: Audio may be severely compressed, intermittent, or text-based
      
      Server->>MobileDevice: Send URL (SMS/Satellite Burst - Second Conn. - delayed)
      MobileDevice->>MobileDevice: User Clicks, Browser/WebRTC Lite
      
      loop Intermittent Still Images & Metadata
          MobileDevice->>Network: Capture Still Image (Highly Compressed) + Full Telemetry Data
          MobileDevice->>Network: Transmit (WebRTC Data Channel, prioritized)
          Network-->>Server: Forward Stills & Metadata (potentially delayed)
          Server-->>Recipient: Reconstruct & Display Image, Overlay Telemetry
      end
      
      Recipient->>Recipient: Comprehensive Situational Awareness from Stills & Data
  

---

5. Cross-Domain Application: Remote Agricultural Diagnostics for Livestock

• Enabling Description: This invention is adapted for precision agriculture, specifically for remote veterinary diagnostics and livestock management. A farm worker or animal handler (user) initiates a call to an agricultural or veterinary support center (recipient) upon observing signs of distress or injury in livestock. The mobile device (e.g., a ruggedized tablet or smartphone) obtains the unique animal ID (e.g., via NFC tag scan, RFID reader integration, or manual input) and its GPS location. The support center obtains the mobile device's phone number and sends a URL via SMS. Upon activation, the mobile device's browser launches a WebRTC session, streaming real-time video of the animal, often augmented with specialized thermal imaging from the device's camera for fever detection. This video, along with the animal ID, GPS coordinates, and any collected biometric data (e.g., heart rate from a connected collar), is transmitted to a veterinarian at the support center. The veterinarian uses this integrated real-time data to conduct remote diagnostic assessments, monitor herd health, and provide immediate guidance for animal care or determine the necessity of an on-site visit, improving response times and efficiency in large-scale farming operations.
• Mermaid Diagram:

  sequenceDiagram
      actor Farmer: Farmer (Mobile Device w/ RFID/NFC, Optional Thermal Cam)
      participant Network: Cellular/Internet Network
      participant VetCenter: Agricultural/Veterinary Support Center
      participant Veterinarian: Veterinarian (Recipient DUT)
  
      Farmer->>Network: Initiate Call (VoIP/Cellular - First Connection)
      Note over Farmer: Identifies distressed animal
      Network->>VetCenter: Route Call
      activate VetCenter
  
      VetCenter->>Farmer: Send URL (SMS - Second Connection)
      Farmer->>Farmer: Clicks URL, Browser Launches WebRTC
      Farmer->>Network: Stream Real-time Video (Animal) + Animal ID + GPS + (Optional Biometrics/Thermal)
      Network->>VetCenter: Forward Video + Data
      VetCenter->>Veterinarian: Display Video + Data Overlays
      deactivate VetCenter
      Veterinarian->>Farmer: Provide Remote Diagnosis & Guidance (via First Connection Audio)
  

---

6. Cross-Domain Application: Construction Site Safety Incident Reporting with Indoor Positioning

• Enabling Description: The system is deployed for immediate safety incident reporting within large-scale construction projects or industrial complexes. A construction worker (user) encounters a safety hazard (e.g., equipment malfunction, structural integrity issue, or personnel injury) and initiates an "emergency call" to the site's central safety control center (recipient). The mobile device, which may be a ruggedized tablet or smartphone, leverages advanced indoor positioning systems (IPS) such as Ultra-Wideband (UWB) tags, Bluetooth Low Energy (BLE) beacons, or Wi-Fi triangulation to provide precise sub-meter location data within the complex, complementing GPS outdoors. The safety control center obtains the worker's device identifier and transmits a URL via SMS. Upon clicking, the worker's browser establishes a WebRTC session, streaming real-time video of the incident. This video stream, along with the highly accurate indoor/outdoor location data and potentially sensor data from the mobile device (e.g., accelerometer data indicating impact, gas sensor readings if integrated), is displayed on a dynamic 3D map interface at the safety control center. This enables safety officers to precisely pinpoint the incident location, visualize the scene, and guide the worker on immediate containment or first aid, while dispatching appropriate emergency teams to the exact coordinates.
• Mermaid Diagram:

  flowchart LR
      A[Construction Worker Mobile Device] --1. Emergency Call (Audio)--> B(Safety Control Center)
      A --Collects--> C(Indoor/Outdoor Location Data)
      B --2. Obtain Device ID--> D{Server}
      D --3. Transmit URL (SMS)--> A
      A --4. Click URL, Launch Browser--> E[WebRTC Session]
      E --5. Stream Real-time Video + Location Data (IPS/GPS)--> F(Safety Control Center Display)
      F --6. Display Video, Location Overlay on 3D Map--> G[Safety Officer]
  
      subgraph Connections
          A --First Connection (Voice)--> B
          D --Second Connection (SMS)--> A
          A --WebRTC Session--> F
      end
  

---

7. Integration with Emerging Tech: AI-Driven Video Content Analysis and Alert Triggering

• Enabling Description: The real-time video stream originating from the mobile device via the WebRTC session is not directly sent to the recipient's display. Instead, it is first routed through an intermediary server equipped with an AI-driven video analytics module. This module leverages advanced computer vision algorithms, including object detection (e.g., for firearms, smoke, fire, specific vehicle types), activity recognition (e.g., detecting falls, struggles, large crowds, rapid movement), and environmental state analysis (e.g., water level changes, structural collapse). The AI continuously processes the incoming video frames, performing real-time inference. Upon detecting predefined critical events or objects, the AI system generates immediate, prioritized alerts or visual overlays (e.g., bounding boxes, heat maps, text labels) on the video feed that is subsequently forwarded to the dispatch unit terminal. For example, if the AI identifies an unconscious person or active flames, an audible alert is triggered at the DUT, and the relevant area of the video is highlighted, providing enhanced contextual information and reducing cognitive load on the human operator, potentially enabling faster and more accurate emergency response.
• Mermaid Diagram:

  graph TD
      A[Mobile Device] --WebRTC Stream (Raw Video)--> B[Server (AI Pre-processing)]
      B --Input Video Feed--> C{AI Video Analytics Module}
      C --Real-time Inference--> C1(Object Detection: e.g., Fire, Weapon, Person)
      C --Real-time Inference--> C2(Activity Recognition: e.g., Fall, Struggle)
      C --Output: Analyzed Video + Alerts/Overlays--> D[Dispatch Unit Terminal (DUT)]
      D --Display Video + AI-generated Visualizations--> E[Dispatch Operator]
      
      style C1 fill:#f9f,stroke:#333,stroke-width:2px
      style C2 fill:#f9f,stroke:#333,stroke-width:2px
  

---

8. Integration with Emerging Tech: IoT Sensor Data Fusion and Blockchain for Evidentiary Integrity

• Enabling Description: This derivative enhances the system by fusing the real-time video stream with rich, contextual data from proximate Internet of Things (IoT) sensors and ensuring the integrity of this combined dataset using blockchain technology. The mobile device, upon initiating the WebRTC session, also collects data from paired or nearby IoT devices (e.g., smart wearable sensors providing biometric data like heart rate and body temperature, environmental sensors measuring air quality, radiation levels, or chemical presence in hazardous situations, or integrated vehicle telemetry). This heterogeneous IoT data is synchronized with video frames using precise timestamps and embedded within the WebRTC data channel or streamed alongside the video. Before being displayed at the recipient's DUT, critical segments of the fused video and IoT data, along with unique identifiers and location metadata, are securely committed to a permissioned blockchain network. Each data block contains cryptographic hashes of preceding data, establishing an immutable and auditable chain of custody. The dispatch terminal displays the real-time video with synchronized IoT data overlays and a clear indicator of blockchain verification status, providing verifiable evidence for post-incident analysis, forensics, or legal proceedings.
• Mermaid Diagram:

  flowchart TD
      A[Mobile Device] --WebRTC Stream--> B(WebRTC Server)
      A --Collects--> C[Co-located IoT Sensors (e.g., Biometrics, Environmental)]
      C --IoT Data--> A
      
      B --Video + Synchronized IoT Data--> D{Data Fusion & Blockchain Integration Module}
      D --Commits Hashed Data--> E[Blockchain Network (Immutable Ledger)]
      D --Real-time Fused Feed--> F[Dispatch Unit Terminal (DUT)]
      
      F --Displays--> G{Video + Synchronized IoT Overlays + Blockchain Verification Status}
  

---

9. The "Inverse" or Failure Mode: Privacy-Preserving Low-Power Mode for Sensitive Situations

• Enabling Description: The system incorporates a "privacy-preserving low-power mode" that activates under specific conditions: critically low mobile device battery (e.g., below 10%), explicit user activation of a privacy setting, or detection of a sensitive environment (e.g., in a hospital, school, or private residence where full video streaming might be inappropriate or restricted). In this mode, the WebRTC session automatically degrades from a full video stream to transmitting only highly anonymized or obfuscated visual data. This could involve motion vectors without explicit pixel data, extreme pixelation/blurring of the video feed, abstract heat map representations of movement, or periodic still images with significant facial/identifiable object blurring. This obfuscated visual data is combined with continuous audio (if privacy concerns allow, otherwise audio may also be modulated or converted to speech-to-text summaries) and precise location data. The primary goal is to conserve battery life and protect privacy while still providing critical contextual information (e.g., "Is the user moving?", "What is the general environment's activity level?", "Is audio present?") to the dispatch unit. The recipient's DUT is specifically designed to interpret and display these privacy-enhanced visual cues and summarized information, ensuring effective communication in sensitive and resource-constrained scenarios.
• Mermaid Diagram:

  stateDiagram-v2
      [*] --> NormalOperation
      NormalOperation --> LowBattery : Battery < 10%
      NormalOperation --> PrivacyModeTriggered : User Activates Privacy / Environment Detected
      
      LowBattery --> LowPowerPrivacyMode : Automatic Transition
      PrivacyModeTriggered --> LowPowerPrivacyMode : User/System Activated
      
      LowPowerPrivacyMode --> TransmitAudioLocation : Audio + GPS
      LowPowerPrivacyMode --> TransmitObfuscatedVideo : + Pixelated/Blurred Video / Motion Vectors
      LowPowerPrivacyMode --> DisplaySummarizedInfo : Dispatch Displays Essential Data
      
      TransmitAudioLocation --> DispatchDisplay : Contextual Audio & Location
      TransmitObfuscatedVideo --> DispatchDisplay : Abstract Visual Cues
      
      LowPowerPrivacyMode --> NormalOperation : Battery Charged / Privacy Deactivated / All Clear
  

---

10. The "Inverse" or Failure Mode: Limited-Functionality "Safe-Mode" for Compromised Devices

• Enabling Description: In situations where the mobile device's integrity is compromised (e.g., detection of malware, unauthorized root access, or suspicious OS activity through device attestation) or when a full WebRTC video connection cannot be established due to severe network degradation or explicit user refusal of camera access, the system enters a "limited-functionality safe-mode." In this mode, the WebRTC session attempts to transmit only a minimal, verifiable stream of still images (e.g., one image per minute) from the most accessible camera (front or rear), critical device health metrics (e.g., battery level, signal strength, detected malware signature, available storage), and periodic, coarse-grained location updates (e.g., cell tower IDs, Wi-Fi SSID scans, or last known GPS fixes). All transmitted data, including the still images and metadata, is subjected to enhanced end-to-end encryption using a hardware security module (HSM) if available on the device, and digitally signed with a unique device key. A simplified, tamper-evident manifest accompanies each data packet. This ensures that even in a compromised state, the dispatch receives critical, authenticated, and minimal information, potentially aiding in identifying the user's general whereabouts and device status, without risking further exploitation or misrepresentation.
• Mermaid Diagram:

  flowchart TD
      A[Mobile Device] --Detects Compromise/Network Failure--> B{Safe-Mode Activation Logic}
      B --Activates--> C[Limited-Functionality WebRTC Session]
      
      C --Transmit Encrypted & Signed Still Images (Periodic)--> D(Network)
      C --Transmit Encrypted & Signed Device Health Metrics--> D
      C --Transmit Encrypted & Signed Coarse Location Updates--> D
      
      D --Encrypted & Authenticated Stream--> E[Server (Decryption/Verification/Attestation)]
      E --Verified & Minimal Data--> F[Dispatch Unit Terminal]
      F --Displays--> G{Still Images + Health/Location Overlay + Integrity Status}
  
      style B fill:#faa,stroke:#333,stroke-width:2px
      style E fill:#aaf,stroke:#333,stroke-width:2px
  

---

Combination Prior Art Scenarios

These scenarios describe combinations of the core invention (US11689383) with existing open-source standards, demonstrating obviousness for certain enhancements.

1. Combination with Session Initiation Protocol (SIP) and SIPREC for Unified Communication Recording

• Description: The emergency call (the "first connection") is initiated and managed using the open-source Session Initiation Protocol (SIP), a widely adopted standard for multimedia communication over IP networks. This means the call setup, tear-down, and mid-call changes are controlled by a SIP server at the emergency call center (PSAP). When the URL is transmitted via the "second connection" (e.g., SMS) to trigger the WebRTC video stream, the WebRTC signaling itself is also brokered or coordinated by the existing SIP infrastructure, treating the WebRTC stream as an additional media channel within the established SIP session. Crucially, the entire communication, encompassing both the audio content from the SIP voice call and the real-time video stream from the WebRTC session, is unified and recorded using the SIP Recording (SIPREC) standard. The unique identifier for the mobile device, as described in US11689383, is explicitly integrated into the SIP call metadata and SIPREC session data, ensuring a comprehensive, synchronized, and legally compliant record of the multi-modal emergency interaction.
• Prior Art Value: The integration of WebRTC streams into an existing SIP-based communication environment for emergency services is a natural and obvious extension for professionals skilled in telecommunications and VoIP. Leveraging SIPREC for unified recording of both voice and supplemental media (like WebRTC video) is a standard practice for compliance and archival in call centers, particularly those handling critical communications. The use of a unique identifier to correlate these streams would be a logical necessity.

2. Combination with MPEG-DASH (Dynamic Adaptive Streaming over HTTP) for Server-Side Adaptive Delivery

• Description: The real-time video stream received from the mobile device via the WebRTC session at the server (Server 120 in FIG. 1) is immediately processed and transcoded into an adaptive bitrate (ABR) format using the open-source MPEG-DASH (Dynamic Adaptive Streaming over HTTP) standard. While WebRTC provides the initial low-latency, peer-to-peer (or relayed) connection, the server simultaneously segments the incoming stream into multiple quality representations (e.g., 360p, 720p, 1080p, 4K) and stores them for adaptive delivery. This allows dispatch unit terminals or other authorized viewers within the PSAP network to access the same incident video feed via standard HTTP, capable of dynamically adjusting the video quality based on their local network conditions, device capabilities, or explicit user preferences. This also facilitates efficient archival and VOD (Video on Demand) playback within the emergency response system, allowing operators to rewind, fast-forward, or review specific moments of the incident stream with optimal performance on diverse viewing platforms (e.g., desktop displays, tablets, or even large situation room monitors).
• Prior Art Value: Integrating real-time WebRTC input with an adaptive streaming standard like MPEG-DASH for broader consumption, archiving, and flexible playback within an enterprise or public safety context is a straightforward engineering task. The benefits of adaptive streaming (network resilience, device compatibility, VOD features) are well-known, and applying them to a WebRTC ingest stream would be an obvious optimization.

3. Combination with OpenStreetMap (OSM) for Enhanced Geospatial Context and Visualization

• Description: The GPS coordinates and/or indoor location data transmitted by the mobile device through the WebRTC session (as optionally described in US11689383 for real-time data or claim 7) are explicitly integrated and rendered onto an interactive map interface powered by OpenStreetMap (OSM) data at the recipient's dispatch unit terminal. The unique identifier associated with the mobile device is used to track the real-time position and movement of the user on a highly detailed, open-source basemap. This integration extends to leveraging other publicly available and crowd-sourced spatial information from OSM, such as building footprints, points of interest (e.g., hospitals, schools), public transportation routes, and even fine-grained details like fire hydrants or accessibility ramps, which are dynamically overlaid onto the map. This provides dispatch operators with significantly enhanced geospatial context, allowing them to visualize the incident location within a rich, real-world framework and communicate precise, landmark-based instructions to emergency responders. The map interface also displays the mobile device's compass heading and estimated speed to provide dynamic situational awareness.
• Prior Art Value: The use of open-source mapping platforms like OpenStreetMap for visualizing real-time location data is a common and obvious application in fields requiring geospatial awareness. Integrating the location data from a real-time streaming event (like a WebRTC video stream during an emergency) onto such a map, and overlaying additional contextual data from the map itself, is a direct and uninventive enhancement.