CN108090024B - Ad hoc network module bottom layer driving development device based on LC1860 chip - Google Patents
Ad hoc network module bottom layer driving development device based on LC1860 chip Download PDFInfo
- Publication number
- CN108090024B CN108090024B CN201711482382.6A CN201711482382A CN108090024B CN 108090024 B CN108090024 B CN 108090024B CN 201711482382 A CN201711482382 A CN 201711482382A CN 108090024 B CN108090024 B CN 108090024B
- Authority
- CN
- China
- Prior art keywords
- data
- android
- hoc network
- interface
- push
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/76—Architectures of general purpose stored program computers
- G06F15/78—Architectures of general purpose stored program computers comprising a single central processing unit
- G06F15/7807—System on chip, i.e. computer system on a single chip; System in package, i.e. computer system on one or more chips in a single package
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/76—Architectures of general purpose stored program computers
- G06F15/78—Architectures of general purpose stored program computers comprising a single central processing unit
- G06F15/7896—Modular architectures, e.g. assembled from a number of identical packages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Microelectronics & Electronic Packaging (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses an Ad hoc network module bottom layer driving development device based on an LC1860 chip, which is applied to the LC1860 chip, wherein the Ad hoc network module is used for acquiring voice and data communication information in real time, and an Ad hoc network interface kernel driving layer is used for receiving the voice and data communication information; the self-networking local code module is used for obtaining program code information which can be identified by the self-networking application program unit; the ad hoc network application program unit is used for acquiring audio data; the Android frame unit is used for acquiring sampled Android Socket communication data; the Android hardware abstraction layer is used for acquiring an interface driving code identifier and the Android Socket communication data; the self-networking interface kernel driving layer is used for driving the corresponding interface according to the interface driving code identification, and then sending the communication data from the interface to the push-to-talk key audio unit.
Description
Technical Field
The invention belongs to the technical field of electronics and communication, and particularly relates to an Ad hoc network module bottom layer driving development device based on an LC1860 chip, which is suitable for an Ad hoc network and can operate on the LC1860 without errors to complete the functions.
Background
The LC1860 chip supports LTE-TDD/LTE-FDD/TD-SCDMA/WCDMA/GEE five modes, has the characteristic of 4G+28nm, integrates the features of 4+1 Cortex A7.5 GHz CPU, dual-core GPU Mail T628, trustzone security architecture and the like, can fully meet the real-time transmission requirement of the mobile terminal big data in the mobile interconnection era, but has insufficient development and utilization at the present stage, less development resources and development technology, and needs to be developed in a large scale.
The ad hoc network has the characteristics of network ad hoc property, high dynamic property of a topological structure, a multi-hop communication mode and the like; in the military field, the wireless ad hoc network is a main communication form on an automatic battlefield, and has inherent survivability, ad hoc property and maneuverability, so that the wireless ad hoc network has wide application prospect in the field. In addition to the military field, wireless ad hoc networks are also widely used in civil fields, such as disaster relief, environmental monitoring, etc.; the LC1860 chip has the characteristics of miniaturization, low power consumption and low cost, and can completely meet the requirements of an ad hoc network module, but the ad hoc network module is developed in recent years, and the technology market combined with the LC1860 is not yet developed.
Disclosure of Invention
Aiming at the problems existing in the prior art, the invention aims to provide an Ad hoc network module bottom driving development device based on an LC1860 chip, which can combine the LC1860 chip with the Ad hoc network module to work, and develop the Ad hoc network module bottom driving based on the LC1860 chip as a main chip, so that the Ad hoc network can operate on the LC1860 without errors to complete the functions.
In order to achieve the technical purpose, the invention is realized by adopting the following technical scheme.
An Ad hoc network module bottom layer driving development device based on an LC1860 chip is applied to the LC1860 chip and comprises: the system comprises an ad hoc network application program unit, an Android frame unit, an Android hardware abstraction layer, an ad hoc network interface kernel driving layer, an ad hoc network local code module, a push-to-talk key audio unit and an ad hoc network module;
the self-networking application program unit comprises a first bidirectional end and a second bidirectional end, the self-networking interface kernel driving layer comprises a third bidirectional end, a fourth bidirectional end, a fifth bidirectional end and a sixth bidirectional end, the self-networking local code module comprises a seventh bidirectional end and an eighth bidirectional end, the Android framework unit comprises a ninth bidirectional end, a tenth bidirectional end and a first unidirectional end, and the Android hardware abstraction layer comprises an eleventh bidirectional end and a twelfth bidirectional end;
the first bidirectional end of the Ad hoc network application program unit is in bidirectional connection with the ninth bidirectional end of the Android frame unit, the second bidirectional end of the Ad hoc network application program unit is in bidirectional connection with the seventh bidirectional end of the Ad hoc network local code module, the eighth bidirectional end of the Ad hoc network local code module is in bidirectional connection with the third bidirectional end of the Ad hoc network interface kernel driving layer, the fourth bidirectional end of the Ad hoc network interface kernel driving layer is in bidirectional connection with the eleventh bidirectional end of the Android hardware abstraction layer, the fifth bidirectional end of the Ad hoc network interface kernel driving layer is in bidirectional connection with the push-to-talk key audio unit, the sixth bidirectional end of the Ad hoc network interface kernel driving layer is in bidirectional connection with the eighth bidirectional end of the Ad hoc network module, and the first unidirectional end of the Android frame unit is in unidirectional connection with the Ad hoc network application program unit.
The self-networking module is used for acquiring voice and data communication information in real time and respectively transmitting the voice and data communication information to the self-networking interface kernel driving layer and the self-networking local code module;
the self-networking interface kernel driving layer is used for receiving the voice and data communication information sent by the self-networking module and sending the received voice and data communication information to the self-networking local code module;
the self-networking local code module is used for receiving the voice and data communication information received by the self-networking interface kernel driving layer, converting the voice and data communication information into program code information which can be identified by the self-networking application program unit by adopting an Android JNI mechanism, and sending the program code information to the self-networking application program unit;
the self-networking application program unit is used for receiving the program code information sent by the self-networking local code module, converting the program code information into audio data and then sending the audio data to the Android frame unit;
the Android frame unit is used for receiving the audio data sent by the ad hoc network application program unit, collecting Android Socket communication data of the audio data, and then sending the sampled Android Socket communication data to the Android hardware abstraction layer;
the Android hardware abstraction layer is used for receiving the Android Socket communication data sent by the Android frame unit, performing interface driving adaptation on the Android Socket communication data, further obtaining an interface driving code identifier, and sending the interface driving code identifier and the Android Socket communication data to an Ad hoc network interface kernel driving layer;
the Ad hoc network interface kernel driving layer is used for receiving the interface driving code identification and the Android Socket communication data sent by the Android hardware abstraction layer, driving a corresponding interface according to the interface driving code identification, and then sending the communication data to a push-to-talk key audio unit from the interface.
The invention is characterized and further improved in that:
1. the self-networking application program unit is also used for converting voice and data communication information into push-to-talk data, network protocol data and voice data, transmitting the push-to-talk data, the network protocol data and the voice data to the self-networking local code module to obtain push-to-talk data codes, network protocol data codes and voice data codes, transmitting the push-to-talk data codes, the network protocol data codes and the voice data codes to the self-networking interface kernel driving layer, driving the corresponding interface by the self-networking interface kernel driving layer according to the push-to-talk data codes, the network protocol data codes and the voice data codes, and transmitting the push-to-talk data codes, the network protocol data codes and the voice data codes to the self-networking module from the interface to carry out code interpretation, and respectively obtaining the push-to-talk data, the network protocol data and the voice data.
2. The self-networking application program unit is also used for reading the push-to-talk key data from the audio data and then sending the push-to-talk key data to the Android frame unit, and the Android frame unit is used for collecting Android Socket push-to-talk key data after receiving the push-to-talk key data, and sending the collected Android Socket push-to-talk key data to the Android hardware abstraction layer; the Android hardware abstraction layer is used for carrying out interface driving adaptation after receiving the collected Android Socket push-to-talk key data, so as to obtain a push-to-talk key data interface driving code; the Ad hoc network interface kernel driving layer is used for receiving the push-to-talk key data interface driving code and the collected Android Socket push-to-talk key data;
the push-to-talk key audio unit is also used for acquiring a hardware interface signal and sending the hardware interface signal to the self-networking interface kernel driving layer; the self-networking interface kernel driving layer is also used for receiving a hardware interface signal sent by the push-to-talk key audio unit, driving a corresponding interface according to the push-to-talk key data interface driving code, and sending the push-to-talk key data interface driving code to the Android hardware abstraction layer from the interface; and the Android hardware abstraction layer receives the push-to-talk key data interface driving code, and sends the collected Android Socket push-to-talk key data to an Android frame unit, and the Android frame unit sends the collected Android Socket push-to-talk key data to an ad hoc network application program unit.
The invention has the beneficial effects that:
due to the advantages of LC1860 chips: miniaturization, low power consumption and low cost; the self-organizing network has the characteristics of self-organizing property of the network, high dynamic property of a topological structure, multi-hop communication mode and the like, and the self-organizing network complete BSP based on 1860 is developed by using the device of the invention, so that the related functions of the self-organizing network can be realized; the device has strong universality and can be suitable for more application occasions.
Drawings
The invention is described in further detail below with reference to the drawings and the detailed description.
FIG. 1 is a schematic diagram of an Ad hoc network module bottom layer driving development device based on an LC1860 chip;
FIG. 2 is a diagram showing an implementation of a device for developing a bottom layer driver of an ad hoc network module based on an LC1860 chip;
FIG. 3 is an IP configuration diagram of an ad hoc network module;
fig. 4 is a multicast non-link establishment PTT voice flow diagram;
FIG. 5 is a flow chart of unicast link establishment voice service data;
fig. 6 is a flowchart of an application program.
Detailed Description
The Android software comprises an APP, a framework, a HAL layer, a Linux Kernel and corresponding peripheral equipment and peripheral equipment firmware programs from top to bottom; android software adaptation is performed on a new peripheral, and it is usually required to distinguish whether the device is an Android standard device or an Android nonstandard device.
For an Android standard device such as a Wifi & BT & FM three-in-one module, which is a peripheral device that an Android device usually has, the Android whole framework includes a native APP, a framework and a HAL, which are all supported by the framework of the module, so the adaptation work of the standard device is mainly focused on the HAL layer and the Linux Kernel layer, and mainly is to adapt the driving and use interfaces of the device.
For Android nonstandard equipment, the Android does not support such frames, and a third party APP generally packages various access interfaces of the equipment by using JNI local codes through an Android JNI mechanism; android Framework can be skipped using the Android JNI mechanism to adapt and use a wider range of devices; for example, the RS232 serial port and the Android API have no function accessing the serial port device, for the serial port device customized by the hardware platform, the user must customize the JNI code to package the access to the serial port device, and then access the local codes in the Android APP to achieve the purpose of accessing the serial port device.
The native code of Android Framework has a number of drawbacks to access to various devices, primarily because the native Android Framework is primarily customized for commercial handsets, tablet devices. If some defect is to be broken through to accommodate more peripherals, it may be necessary to modify Android Framework code, or implement a third party's native program, or otherwise implement it. Regardless of the manner in which it is implemented, this approach is collectively referred to herein as "modification Android Framework"; the current complete machine equipment integrates a plurality of communication modules, a standard communication module is adapted in a RIL mode, and a nonstandard communication module is adapted in an APP+JNI mode; however, if multiple RIL modules exist simultaneously (e.g., heaven+lte+ad hoc network), the communication portion (telephenyl, RIL) of Android Framework may not be able to handle the concurrent data channels of the multiple modules; this may require the concurrent use of multiple data channels to be handled in a modified Android Framework manner.
In the device, the self-networking module adopts a JNI adapting mode, and a designated self-networking module is selected to realize communication of VOIP voice and data, and the module adopts a USB interface only for communication, so that GPIO of a CPU is required to be used for providing power management of an IO port of the module, such as dormancy awakening, state display and the like. The module needs to receive BD time service data to carry out internal correction, and the ad hoc network is provided with a special encryption port, and the module is directly connected to the BM module through the SPI port to carry out encryption and decryption operations.
The ad hoc network module is adapted in an Android nonstandard equipment mode, namely, the Android framework is integrated into the system in a mode of skipping a third party APP+local JNI code. The module firmware program, programming protocol and other possible useful codes and interface drivers of Linux Kernel, local JNI code encapsulation of ad hoc network and DemoAPK are applied.
The access of the Ad hoc network APP to the Ad hoc network is realized through the encapsulated local code; PTT key event and audio data acquisition required by the ad hoc network are realized through an Android standard framework.
Referring to fig. 1, a schematic diagram of an ad hoc network module bottom layer driving development device based on an LC1860 chip according to the present invention is shown; the Ad hoc network module bottom layer driving development device based on the LC1860 chip is applied to the LC1860 chip and comprises: the system comprises an ad hoc network application program unit, an Android frame unit, an Android hardware abstraction layer, an ad hoc network interface kernel driving layer, an ad hoc network local code module, a push-to-talk key audio unit and an ad hoc network module.
The self-networking application program unit comprises a first bidirectional end and a second bidirectional end, the self-networking interface kernel driving layer comprises a third bidirectional end, a fourth bidirectional end, a fifth bidirectional end and a sixth bidirectional end, the self-networking local code module comprises a seventh bidirectional end and an eighth bidirectional end, the Android frame unit comprises a ninth bidirectional end, a tenth bidirectional end and a first unidirectional end, and the Android hardware abstraction layer comprises an eleventh bidirectional end and a twelfth bidirectional end.
The first bidirectional end of the Ad hoc network application program unit is in bidirectional connection with the ninth bidirectional end of the Android frame unit, the second bidirectional end of the Ad hoc network application program unit is in bidirectional connection with the seventh bidirectional end of the Ad hoc network local code module, the eighth bidirectional end of the Ad hoc network local code module is in bidirectional connection with the third bidirectional end of the Ad hoc network interface kernel driving layer, the fourth bidirectional end of the Ad hoc network interface kernel driving layer is in bidirectional connection with the eleventh bidirectional end of the Android hardware abstraction layer, the fifth bidirectional end of the Ad hoc network interface kernel driving layer is in bidirectional connection with the push-to-talk key audio unit, the sixth bidirectional end of the Ad hoc network interface kernel driving layer is in bidirectional connection with the eighth bidirectional end of the Ad hoc network module, and the first unidirectional end of the Android frame unit is in unidirectional connection with the Ad hoc network application program unit.
Referring to fig. 2, a specific implementation diagram of an ad hoc network module bottom layer driving development device based on an LC1860 chip according to the present invention is shown; the self-networking module is used for acquiring voice and data communication information in real time and respectively transmitting the voice and data communication information to the self-networking interface kernel driving layer and the self-networking local code module.
The self-networking interface kernel driving layer is used for receiving the voice and data communication information sent by the self-networking module, receiving the voice and data communication information by obtaining corresponding driving codes according to the voice and data communication information, and then sending the received voice and data communication information to the self-networking local code module.
The self-networking local code module is used for receiving the voice and data communication information received by the self-networking interface kernel driving layer, converting the voice and data communication information into program code information which can be identified by the self-networking application program unit by adopting an Android JNI mechanism, and sending the program code information to the self-networking application program unit.
The self-networking application program unit is used for receiving the program code information sent by the self-networking local code module, converting the program code information into audio data and then sending the audio data to the Android frame unit.
The Android frame unit is used for receiving the audio data sent by the ad hoc network application program unit, collecting Android Socket communication data of the audio data, and then sending the sampled Android Socket communication data to the Android hardware abstraction layer.
The Android hardware abstraction layer is used for receiving the Android Socket communication data sent by the Android frame unit, performing interface driving adaptation on the Android Socket communication data, further obtaining an interface driving code identifier, and sending the interface driving code identifier and the Android Socket communication data to the Ad hoc network interface kernel driving layer.
The Ad hoc network interface kernel driving layer is used for receiving the interface driving code identification and the Android Socket communication data sent by the Android hardware abstraction layer, driving a corresponding interface according to the interface driving code identification, and then sending the communication data to a push-to-talk key audio unit from the interface.
Specifically, referring to fig. 3, an ad hoc network module IP configuration diagram is shown; wherein all AT commands are communicated through serial/dev/ttyUSB [0-3], other business voice data are communicated through network card device zzw0, and the opposite end module IP address can be ping before voice communication is confirmed, as shown in figure 4 and figure 5.
Methods of making and using the device of the invention:
file manifest
driver/usb Linux driving catalog corresponding to ZZW module
| lc1860_usb_serial.c | ZZW module driving source file |
| lc1860_usb_serial.ko | Compiling and generating driving module file |
| Makefile | Compiling and generating file |
zzw-jni/2def: the related protocol data document is recorded under the directory
zzw-jni: specific implementation of test application code and library function under directory
Compile download
The current test Linux host environment is shown in the following table:
| operating system version | Ubuntu 14.04.5LTS |
| Linux kernel version | 3.16.0-30-generic |
| GCC compiler version | 4.8.4 |
| JAVA JDK version | 1.6.0_45 |
| JSON version | 2.90 |
| Android version | 4.4 |
Before compiling and downloading operation, firstly, determining that the Android compiling and downloading environment is configured and installed on the current Linux host, and specifically, the Android compiling environment and docx document can be configured by referring to Ubuntu14.04 in the specific installation step. The following command compiling and downloading are directly executed by entering a source code target path:
referring to fig. 6, in order to use the application program flow chart of the apparatus of the present invention, the following is a test procedure of the DEMO program test:
test procedure
1) Turning on module power
a) Note that if the default poweren and powerctrl nodes are both 0, the module power can be correctly turned on only by executing the above operations; otherwise, the two nodes need to be written with 0 and then written with 1 before the module power is turned on again.
b) Whether the module is powered on successfully checks whether the network card device zzw exists or not according to the serial port terminal printing information or the execution command #netcfg.
2) The configuration module configures own IP address and the IP address of the opposite terminal module to be transmitted. Note that this step needs to be performed around 10S after the module is powered up, otherwise a timeout may be returned.
3) The opposite terminal equipment is configured into another same-network-segment IP address according to the two steps; and then using a command to ping the IP address of the opposite terminal, if the IP address of the opposite terminal module can be ping, executing the following steps, otherwise, sending data and not receiving the data by the opposite terminal. If ping is not successful, it can be checked whether the antenna is connected well or an attempt is made to restart.
4) The multicast non-link establishment PTT voice data was received at one end using zzw command option-w waiting module and tested at the other end using zzw command option-g send PTT voice data.
a) Waiting to receive multicast non-link-established PTT voice data
And (4) waiting for receiving PTT voice data in a circulating way until the PTT voice data are received once and are stored in the/mnt/sdcard/Music/test2.wav file, and the file can be directly played by clicking file browsing- > Music- > test2.wav.
b) Transmitting multicast non-linking PTT voice data
Where the application will automatically open the recording channel and prompt please start speak for record-! The following is carried out The following is carried out The recording is started, the default recording is about 5S, the recording file is stored in a/mnt/sdcard/Music/test1. Wav file, and then the file is circularly read and 800 bytes are sent each time at a rate of 500 ms. After receiving PTT voice data, the opposite terminal can store the PTT voice data in a/mnt/sdcard/Music/test2.wav file, and then find file browsing- > Music- > test2.wav click playing in a tablet cos system graphic desktop.
5) The unicast link-up voice traffic data was received at one end using zzw command option-r waiting module and tested at the other end using zzw command option-s send voice traffic data.
And (3) waiting for receiving the voice service data in a circulating way until the voice service data are received once and storing the voice service data in a/mnt/sdcard/Music/test2.wav file, wherein the file can be directly played by clicking file browsing- > Music- > test2.wav.
Where the application will automatically open the recording channel and prompt please start speak for record-! The following is carried out The following is carried out The recording is started, the default recording is around 5S, the recording file is stored in a/mnt/sdcard/Music/test1. Wav file, and then the file is circularly read and 800 bytes are sent each time at a rate of 500 ms. After receiving PTT voice data, the opposite terminal can store the PTT voice data in a/mnt/sdcard/Music/test2.wav file, and then find file browsing- > Music- > test2.wav click playing in a tablet cos system graphic desktop.
Note that: the two voice data transmission modes can not lose packets under normal conditions, but sometimes the network is unstable, and packet loss can occur occasionally; if the packet is lost, the file may not be played, if the packet is lost, the file may be played if the packet is lost, the audio file is in the middle or end of the audio file, but the quality of sound may be somewhat problematic.
Common problems
1) Description of the problem: after the module is powered on, the IP address and the node ID number of the module are ready to be set, but an error timeout is always returned.
The solution method comprises the following steps:
2) Description of the problem: ping a failed peer module IP address using a ping command
The solution method comprises the following steps: checking whether the module node ID is the same as the last byte of the IP address, checking whether the antenna is connected and has interference too close to the connection, and finally, electrifying again after attempting to restart the system, wherein the always ping opposite-end module is not stable all the time, and multiple restarting tests may be required.
3) Description of the problem: immediately after the opposite terminal module is ping-passed, PTT voice service data or a link establishment request is sent, and situations that channel numbers are unavailable or link establishment fails may occur.
The solution method comprises the following steps:
The display data indicates that the opposite end module can be ping, and connection between the ping command testing modules is not needed.
Claims (3)
1. An ad hoc network module bottom layer drive development device based on an LC1860 chip is applied to the LC1860 chip and is characterized by comprising: the system comprises an ad hoc network application program unit, an Android frame unit, an Android hardware abstraction layer, an ad hoc network interface kernel driving layer, an ad hoc network local code module, a push-to-talk key audio unit and an ad hoc network module;
the self-networking application program unit comprises a first bidirectional end and a second bidirectional end, the self-networking interface kernel driving layer comprises a third bidirectional end, a fourth bidirectional end, a fifth bidirectional end and a sixth bidirectional end, the self-networking local code module comprises a seventh bidirectional end and an eighth bidirectional end, the Android framework unit comprises a ninth bidirectional end, a tenth bidirectional end and a first unidirectional end, and the Android hardware abstraction layer comprises an eleventh bidirectional end and a twelfth bidirectional end;
the first bidirectional end of the ad hoc network application program unit is in bidirectional connection with the ninth bidirectional end of the Android frame unit, the second bidirectional end of the ad hoc network application program unit is in bidirectional connection with the seventh bidirectional end of the ad hoc network local code module, the eighth bidirectional end of the ad hoc network local code module is in bidirectional connection with the third bidirectional end of the ad hoc network interface kernel driving layer, the fourth bidirectional end of the ad hoc network interface kernel driving layer is in bidirectional connection with the eleventh bidirectional end of the Android hardware abstraction layer, the fifth bidirectional end of the ad hoc network interface kernel driving layer is in bidirectional connection with the push-to-talk key audio unit, the sixth bidirectional end of the ad hoc network interface kernel driving layer is in bidirectional connection with the ad hoc network module, the twelfth bidirectional end of the Android hardware abstraction layer is in bidirectional connection with the tenth bidirectional end of the Android frame unit, and the first unidirectional end of the Android frame unit is in unidirectional connection with the ad hoc network application program unit;
the self-networking module is used for acquiring voice and data communication information in real time and respectively transmitting the voice and data communication information to the self-networking interface kernel driving layer and the self-networking local code module;
the self-networking interface kernel driving layer is used for receiving the voice and data communication information sent by the self-networking module and sending the received voice and data communication information to the self-networking local code module;
the self-networking local code module is used for receiving the voice and data communication information received by the self-networking interface kernel driving layer, converting the voice and data communication information into program code information which can be identified by the self-networking application program unit by adopting an Android JNI mechanism, and sending the program code information to the self-networking application program unit;
the self-networking application program unit is used for receiving the program code information sent by the self-networking local code module, converting the program code information into audio data and then sending the audio data to the Android frame unit;
the Android frame unit is used for receiving the audio data sent by the ad hoc network application program unit, collecting Android Socket communication data of the audio data, and then sending the sampled Android Socket communication data to the Android hardware abstraction layer;
the Android hardware abstraction layer is used for receiving the Android Socket communication data sent by the Android frame unit, performing interface driving adaptation on the Android Socket communication data, further obtaining an interface driving code identifier, and sending the interface driving code identifier and the Android Socket communication data to an Ad hoc network interface kernel driving layer;
the Ad hoc network interface kernel driving layer is used for receiving the interface driving code identification and the Android Socket communication data sent by the Android hardware abstraction layer, driving a corresponding interface according to the interface driving code identification, and then sending the communication data to a push-to-talk key audio unit from the interface.
2. The device of claim 1, wherein the ad hoc network application unit is further configured to convert voice and data communication information into push-to-talk data, network protocol data and voice data, send the push-to-talk data, the network protocol data and the voice data to the ad hoc network local code module to obtain push-to-talk data codes, network protocol data codes and voice data codes, send the push-to-talk data codes, the network protocol data codes and the voice data codes to the ad hoc network interface kernel driving layer, and drive the corresponding interfaces according to the push-to-talk data codes, the network protocol data codes and the voice data codes by the ad hoc network interface kernel driving layer, and then send the push-to-talk data codes, the network protocol data codes and the voice data codes to the ad hoc network module from the interfaces for code interpretation, so as to obtain push-to-talk data, network protocol data and voice data respectively.
3. The device for developing an ad hoc network module bottom layer driver based on an LC1860 chip as claimed in claim 1, wherein the ad hoc network application unit is further configured to read push-to-talk key data from audio data and send the push-to-talk key data to the Android frame unit, and the Android frame unit is configured to receive the push-to-talk key data and collect Android Socket push-to-talk key data, and send the collected Android Socket push-to-talk key data to the Android hardware abstraction layer; the Android hardware abstraction layer is used for carrying out interface driving adaptation after receiving the collected Android Socket push-to-talk key data, so as to obtain a push-to-talk key data interface driving code; the Ad hoc network interface kernel driving layer is used for receiving the push-to-talk key data interface driving code and the collected Android Socket push-to-talk key data;
the push-to-talk key audio unit is also used for acquiring a hardware interface signal and sending the hardware interface signal to the self-networking interface kernel driving layer; the self-networking interface kernel driving layer is also used for receiving a hardware interface signal sent by the push-to-talk key audio unit, driving a corresponding interface according to the push-to-talk key data interface driving code, and sending the push-to-talk key data interface driving code to the Android hardware abstraction layer from the interface; and the Android hardware abstraction layer receives the push-to-talk key data interface driving code, android sends the collected Android Socket push-to-talk key data to an Android frame unit, and the Android frame unit sends the collected Android Socket push-to-talk key data to an ad hoc network application program unit.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711482382.6A CN108090024B (en) | 2017-12-29 | 2017-12-29 | Ad hoc network module bottom layer driving development device based on LC1860 chip |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711482382.6A CN108090024B (en) | 2017-12-29 | 2017-12-29 | Ad hoc network module bottom layer driving development device based on LC1860 chip |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108090024A CN108090024A (en) | 2018-05-29 |
| CN108090024B true CN108090024B (en) | 2023-05-02 |
Family
ID=62180910
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711482382.6A Active CN108090024B (en) | 2017-12-29 | 2017-12-29 | Ad hoc network module bottom layer driving development device based on LC1860 chip |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108090024B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109147822B (en) * | 2018-10-26 | 2023-05-09 | 上海创远仪器技术股份有限公司 | System and method for VOLTE voice recording and voice quality evaluation |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7308484B1 (en) * | 2000-06-30 | 2007-12-11 | Cisco Technology, Inc. | Apparatus and methods for providing an audibly controlled user interface for audio-based communication devices |
| CN203193909U (en) * | 2012-12-24 | 2013-09-11 | 浙江中呼科技有限公司 | An ad-hoc network terminal device |
| CN103353839A (en) * | 2013-06-07 | 2013-10-16 | 杭州竞天数码科技有限公司 | Universal serial device communication module based on Android system |
| CN103902389A (en) * | 2014-03-06 | 2014-07-02 | 厦门雅迅网络股份有限公司 | Equipment management method supporting bidirectional communication based on android platform |
| CN205212923U (en) * | 2015-11-02 | 2016-05-04 | 上海唐舜电信科技有限公司 | Restructural network media phone terminal |
| WO2016127495A1 (en) * | 2015-02-12 | 2016-08-18 | 无锡识凌科技有限公司 | Method for developing device driver architecture in intelligent terminal |
| WO2017177873A1 (en) * | 2016-04-15 | 2017-10-19 | 中兴通讯股份有限公司 | System and method for synchronous audio recording and playing, and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10425411B2 (en) * | 2012-04-05 | 2019-09-24 | Arizona Board Of Regents On Behalf Of Arizona State University | Systems and apparatuses for a secure mobile cloud framework for mobile computing and communication |
-
2017
- 2017-12-29 CN CN201711482382.6A patent/CN108090024B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7308484B1 (en) * | 2000-06-30 | 2007-12-11 | Cisco Technology, Inc. | Apparatus and methods for providing an audibly controlled user interface for audio-based communication devices |
| CN203193909U (en) * | 2012-12-24 | 2013-09-11 | 浙江中呼科技有限公司 | An ad-hoc network terminal device |
| CN103353839A (en) * | 2013-06-07 | 2013-10-16 | 杭州竞天数码科技有限公司 | Universal serial device communication module based on Android system |
| CN103902389A (en) * | 2014-03-06 | 2014-07-02 | 厦门雅迅网络股份有限公司 | Equipment management method supporting bidirectional communication based on android platform |
| WO2016127495A1 (en) * | 2015-02-12 | 2016-08-18 | 无锡识凌科技有限公司 | Method for developing device driver architecture in intelligent terminal |
| CN205212923U (en) * | 2015-11-02 | 2016-05-04 | 上海唐舜电信科技有限公司 | Restructural network media phone terminal |
| WO2017177873A1 (en) * | 2016-04-15 | 2017-10-19 | 中兴通讯股份有限公司 | System and method for synchronous audio recording and playing, and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 李佳 ; 亓妍妍 ; 朱维杰 ; .Android***下SAEJ1939协议的移植.计算机应用.2013,(09),全文. * |
| 林献坤 ; 潘志彬 ; 张毅刚 ; .支持4G通道的自动化监控***通信管理机开发.仪表技术与传感器.2017,(10),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108090024A (en) | 2018-05-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Ruge et al. | Frankenstein: Advanced wireless fuzzing to exploit new bluetooth escalation targets | |
| US8442509B2 (en) | System and method for managing a wireless device from removable media with processing capability | |
| TWI244295B (en) | Method and system for simulating multiple independent client devices in a wired or wireless network | |
| KR102024533B1 (en) | Methods for operating software-defined radio application | |
| US20150382212A1 (en) | Method and apparatus for monitoring and adjusting multiple communication services at a venue | |
| US10499311B2 (en) | Method and apparatus for implementing network sharing | |
| CN109918306B (en) | Audio processing device, system, method, apparatus and storage medium | |
| CN102447738B (en) | A kind of method and device realizing base station remote debugging | |
| US20120106441A1 (en) | Supporting a wireless network protocol on a mobile device using a wired interface | |
| CN106487847B (en) | Information processing method and transfer server | |
| CN101662838B (en) | Device, method and USB data card for realizing internet surfing without drive | |
| WO2022267815A1 (en) | Data packet filtering method and apparatus, and electronic device and computer-readable storage medium | |
| CN113259996A (en) | IOT wireless debugging method and equipment | |
| CN113742236B (en) | Test configuration method, electronic equipment and storage medium | |
| CN108090024B (en) | Ad hoc network module bottom layer driving development device based on LC1860 chip | |
| GB2429603A (en) | Wireless interface device able to convert between different communication standards | |
| Heinze et al. | {ToothPicker}: Apple Picking in the {iOS} Bluetooth Stack | |
| JP2009529277A (en) | Wireless network device inspection method | |
| CN104570967B (en) | Long-range control method and system based on android system | |
| CN103269293B (en) | Android platform utilize microwave telecommunication devices carry out the method for debugging acid ADB debugging | |
| CN112367362A (en) | Data processing method, device and equipment and computer storage medium | |
| Tang et al. | Internet of things security: Principles and practice | |
| US20110270970A1 (en) | Network device testing system and method | |
| CN112363743A (en) | User program updating method based on internet access transmission | |
| US20230413163A1 (en) | Network configuration method, electronic device, and computer-readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |