# US 12,120,162 B2 · Communication protocol switching method, apparatus, and system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,120,162 B2
- Document ID: US12120162B2
- Status: Granted
- Kind: B2
- Application number: 17/667,912
- Filed: 2022-02-09
- Published: 2022-07-28
- Granted: 2024-10-15
- Earliest claimed: 2019-08-09
- Assignees: Huawei Technologies Co., Ltd.
- Applicants: Huawei Technologies Co., Ltd.
- Inventors: Licheng Song; Xiaolei Liu; Bihai Wang
- Web page: https://patentgrep.com/patent/US12120162B2

## CPC

- H04L 65/61: for supporting one-way streaming services, e.g. Internet radio
- H04W 76/14: Direct-mode setup
- H04L 65/1069: Session establishment or de-establishment
- H04L 65/611: for multicast or broadcast (systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06)
- H04L 67/04: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
- H04L 67/104: Peer-to-peer [P2P] networks
- H04L 69/08: Protocols for interworking; Protocol conversion
- H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
- H04W 84/12: WLAN [Wireless Local Area Networks]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A communication protocol switching method includes that a first device communicates with a second device using a first protocol to project a screen of the first device to the second device; and when a first application in the first device is opened or a media file stored in the first device is opened, the first device switches to a second protocol to communicate with the second device and to project a display user interface of the first application or the media file to the second device, where the first application manages or plays at least one media file.

## Claims

### Claim 1

A method implemented by a first device, wherein the method comprises:
communicating, using a first protocol, with a second device to project a screen of the first device to the second device;
detecting that a first application in the first device is opened or a first media file stored in the first device is opened, wherein the first application manages or plays at least one second media file; and
switching, in response to detecting that the first application is opened or the first media file is opened, to a second protocol to project a display user interface of the first application or the first media file to the second device.

### Claim 2 (depends on 1)

The method of claim 1, further comprising triggering, using the first application or a second application that is used to open the first media file, switching to the second protocol.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
detecting, using a software development kit (SDK) for screen projection in the first device, that the first application is opened or the first media file is opened; and
further switching, in response to detecting, using the SDK, that the first application is opened or the first media file is opened, to the second protocol.

### Claim 4 (depends on 1)

The method of claim 1, further comprising projecting the display user interface or the first media file to the second device in full screen.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
maintaining a device list corresponding to the second protocol, wherein the device list comprises an identifier of a device that can communicate with the first device using the second protocol;
querying, in response to detecting the first application is opened or the first media file is opened, the device list;
further switching to the second protocol when a unique device identifier (UDID) of the second device is found; and
when the UDID is not found:
sending indication information to the second device to indicate the second device to perform protocol switching; and
receiving, from the second device and using the second protocol, the UDID.

### Claim 6 (depends on 1)

The method of claim 1, further comprising identifying, using a near-field communication (NFC) technology, the second device.

### Claim 7 (depends on 6)

The method of claim 6, further comprising further identifying the second device by identifying an NFC tag of the second device.

### Claim 8 (depends on 1)

The method of claim 1, wherein after identifying the second device, the method further comprises receiving, using the first protocol, a unique device identifier (UDID) of the second device.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
detecting that the first application is closed or the first media file is closed; and
switching, in response to detecting that the first application is closed or the first media file is closed, back to the first protocol to further communicate with the second device.

### Claim 10 (depends on 1)

The method of claim 1, wherein the first protocol is based on a Miracast technology, and wherein the second protocol is based on a Digital Living Network Alliance (DLNA) technology.

### Claim 11

A first device comprising:
a screen;
a memory configured to store instructions; and
at least one processor in communication with the memory and coupled to the screen, wherein the instructions cause the at least one processor to be configured to:
communicate, using a first protocol, with a second device to project the screen to the second device;
detect that a first application in the first device is opened or a first media file stored in the first device is opened, wherein the first application manages or plays at least one second media file; and
switch, in response to detecting that the first application is opened or the first media file is opened, to a second protocol to project a display user interface of the first application or the first media file to the second device.

### Claim 12 (depends on 11)

The first device of claim 11, wherein the instructions further cause the at least one processor to be configured to trigger, using the first application or a second application that is used to open the first media file, switching to the second protocol.

### Claim 13 (depends on 11)

The first device of claim 11, wherein the instructions further cause the at least one processor to be configured to:
detect, using a software development kit (SDK) for screen projection in the first device, that the first application is opened or the first media file is opened; and
further switch, in response to detecting, using the SDK, that the first application is opened or the first media file is opened, to the second protocol.

### Claim 14 (depends on 11)

The first device of claim 11, wherein the instructions further cause the at least one processor to be configured to project the display user interface or the first media file to the second device in full screen.

### Claim 15 (depends on 11)

The first device of claim 11, wherein the instructions further cause the at least one processor to be configured to:
maintain a device list corresponding to the second protocol, wherein the device list comprises an identifier of a device that can communicate with the first device using the second protocol;
query, in response to detecting the first application is opened or the first media file is opened, the device list;
further switch to the second protocol when a unique device identifier (UDID) of the second device is found; and
when the UDID is not found:
send indication information to the second device to indicate the second device to perform protocol switching; and
receive, from the second device and using the second protocol, the UDID.

### Claim 16

A computer program product comprising computer-executable instructions that are stored on a non-transitory computer-readable storage medium and that, when executed by a processor, cause a first device to:
communicate, using a first protocol, with a second device to project a screen of the first device to the second device;
detect that a first application in the first device is opened or a first media file stored in the first device is opened, wherein the first application manages or plays at least one second media file; and
switch, in response to detecting that the first application is opened or the first media file is opened, to a second protocol to project a display user interface of the first application or the first media file to the second device.

### Claim 17 (depends on 16)

The computer program product of claim 16, wherein the computer-executable instructions further cause the first device to trigger, using the first application or a second application that is used to open the first media file, switching to the second protocol.

### Claim 18 (depends on 16)

The computer program product of claim 16, wherein the computer-executable instructions further cause the first device to:
detect, using a software development kit (SDK) for screen projection in the first device, that the first application is opened or the first media file is opened; and
further switch, in response to detecting, using the SDK, that the first application is opened or the first media file is opened, to the second protocol.

### Claim 19 (depends on 16)

The computer program product of claim 16, wherein the computer-executable instructions further cause the first device to project the display user interface or the first media file to the second device in full screen.

### Claim 20 (depends on 16)

The computer program product of claim 16, wherein the computer-executable instructions further cause the first device to:
maintain a device list corresponding to the second protocol, wherein the device list comprises an identifier of a device that can communicate with the first device using the second protocol;
query, in response to detecting the first application is opened or the first media file is opened, the device list;
further switch to the second protocol when a unique device identifier (UDID) of the second device is found; and
when the UDID is not found:
send indication information to the second device to indicate the second device to perform protocol switching; and
receive, from the second device and using the second protocol, the UDID.
