Method for transmitting H264 and H265 data formats by using JAVA NIO during screen projection of Android recording screen

Abstract

The invention relates to a method for transmitting H264 and H265 data formats by using JAVA NIO in Android screen recording and screen projection, which comprises the following steps that: enabling ascreen recording end to record a screen to acquire first data, and encapsulate the first data into the H264 or H265 data format; and converting the packaged H264 or H265 data into byte data, converting the byte data into a ByteBuffer, and transmitting the ByteBuffer to an NIO (Network Input Output) for data transmission. The screen recording end is used as a server end, and the nio socket is usedfor transmitting data to the client end, so that the one-to-many purpose can be achieved, and the many-to-one pair of mobile phones can be controlled. And meanwhile, the client also adopts the nio socket to receive and transmit data, so that more efficient interaction with the server can be achieved.

Description

technical field [0001] The present invention relates to Android screen recording and projection technology, in particular to a method for Android recording and projection using JAVA NIO to transmit H264 and H265 data formats. Background technique [0002] figure 1 It is a schematic diagram of a standard io socket, which shows the structure of multi-thread processing on the server side. For the server side: it is responsible for continuously requesting echoServer.accept(). If no client requests the main thread, it will block. When a client requests the server, The main thread will use the thread pool to create a new thread for execution. That is to say, a thread is responsible for a client socket. When a client socket is delayed due to the network, the thread responsible for the client on the server side will wait, wasting resources. [0003] For the client: Suppose the main thread creates 10 sub-threads to request the server. This is a client socket that simulates network ...

AI Technical Summary

Problems solved by technology

That is to say, a thread is responsible for a client socket. When a client socket is delayed due to the network, the thread responsible for the client on the server side will wait, wasting resources.

[0003] For the client: Suppose the main thread creates 10 sub-threads to request the server. This is a client socket that simulates network congestion. Every time a character is typed, it will stop for 1 second, so that the server-side thread has to wait, which will cause server-side resources. Being wasted, using the standard io socket for Android screen recording and projection also has the problem of inefficiency

Images