CN106888271B - BLE5.0 protocol system - Google Patents

BLE5.0 protocol system Download PDF

Info

Publication number
CN106888271B
CN106888271B CN201710205000.9A CN201710205000A CN106888271B CN 106888271 B CN106888271 B CN 106888271B CN 201710205000 A CN201710205000 A CN 201710205000A CN 106888271 B CN106888271 B CN 106888271B
Authority
CN
China
Prior art keywords
hardware
software
state
module
link layer
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
Application number
CN201710205000.9A
Other languages
Chinese (zh)
Other versions
CN106888271A (en
Inventor
马越涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Peach Core Technology (Suzhou) Co., Ltd.
Original Assignee
Peach Core Technology Suzhou Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Peach Core Technology Suzhou Co ltd filed Critical Peach Core Technology Suzhou Co ltd
Priority to CN202010271543.2A priority Critical patent/CN111510481B/en
Priority to CN201710205000.9A priority patent/CN106888271B/en
Publication of CN106888271A publication Critical patent/CN106888271A/en
Application granted granted Critical
Publication of CN106888271B publication Critical patent/CN106888271B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/323Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the physical layer [OSI layer 1]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/10Flow control between communication endpoints
    • H04W28/14Flow control between communication endpoints using intermediate storage
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE 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/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Abstract

The invention relates to a BLE5.0 protocol system and a software and hardware interactive interface applied in the system, wherein the software and hardware interactive interface based on a linked list completes data and information interaction between a controller and a physical layer, the interface is realized based on events, each Event is represented by a structure named ECPT during realization, each ECPT comprises all parameter information describing one Event, the ECPT structure is associated with a data receiving linked list and a data sending linked list, and the hardware side of the software and hardware interactive interface judges whether the ECPT is effective or not by periodically polling the Event list. The interface effectively shields the implementation details of bottom hardware, completes data receiving and sending, and obtains and configures hardware parameters, reduces the difficulty of system implementation, and simultaneously, the invention effectively and reasonably divides each function specified in the protocol, and is easy to implement and maintain the function.

Description

BLE5.0 protocol system
Technical Field
The invention relates to a BLE5.0 protocol system and a software and hardware interaction interface applied in the system, and belongs to the technical field of wireless communication.
Background
The low-power consumption Bluetooth technology (BLE) is one of the most common wireless transmission technologies which are developed most quickly at present, the BLE has permeated into all places of our lives, no integrated BLE communication module is available in the existing general smart phone, and the BLE module is widely applied to various aspects such as household terminal equipment, environment monitoring, light control and wireless upgrading due to the characteristics of low cost, low power consumption and the like. Popularization of the internet of things plays a crucial role in updating iteration of the BLE protocol, and rapid realization and easy expansion of the protocol put higher demands on front-line developers. Because the bluetooth protocol provides a complete protocol from a bottom physical layer to an upper application layer, the protocol implementation difficulty is increased, the protocol function becomes very complex, unreasonable protocol level division can increase the protocol implementation difficulty, subsequent protocol updating and expansion are not convenient, and the online period of a product is prolonged, so that the protocol level division according to the function in the implementation process is very important.
The development of a BLE software protocol stack is the most complicated link and the longest time consumption link in the process of realizing the whole BLE system, functions of all layers are staggered, and the development progress of the system is seriously influenced if the layers cannot be effectively divided.
In the BLE protocol stack implementation, link layer function development occupies a long period, and a great deal of description is also performed on BLE link layer functions in the protocol, but the link layer is not divided into modules according to the functions, if system development is performed according to the protocol, it is difficult to develop an efficient core protocol stack in a short period, and no document in the available public document can describe the implementation of the link layer in detail.
The design of software and hardware interfaces in the realization of the BLE protocol stack belongs to the most critical place of the realization of system functions, relates to the division of the functions of the software and the hardware, has no description on the division of the functions of software and hardware interaction interfaces in the protocol, is a place which is freely played by a developer in the realization process, and has different specific division and realization modes.
Disclosure of Invention
The invention provides a linked list-based software and hardware interaction interface, which effectively shields the implementation details of bottom hardware, completes data receiving and sending and hardware parameter acquisition and configuration, is convenient to implement and easy to expand. The link layer is as important module in BLE5.0 agreement, divides the link layer module for each level function is more clear and definite, reduces and realizes the degree of difficulty, shortens the debugging cycle, and it is more convenient to carry out protocol function extension on this basis. The invention also provides a BLE5.0 protocol system, which effectively and reasonably divides each function specified in the protocol and is easy to realize and maintain the function.
The invention is realized by the following technical scheme: the interface is realized based on events, each Event is represented by a structure named ECPT during realization, each ECPT contains all parameter information describing one Event, the ECPT structure is associated with a data receiving chain table and a data sending chain table, and the hardware side of the software and hardware interactive interface judges whether the ECPT is effective or not by periodically polling the Event list.
A software and hardware interaction method applied to a BLE5.0 protocol system is a linked list-based software and hardware interaction method, completes data and information interaction between a controller and a physical layer, and comprises the following steps:
(1) when the BLE5.0 system transmits data, the software side of the software and hardware interaction interface puts the prepared data in a transmission cache;
(2) setting an ECPT valid flag to inform the hardware side of the software and hardware interaction interface of sending data;
(3) when the hardware polls that the ECPT is effective, acquiring the content in the sending cache according to the specified parameters in the ECPT, and sending the data to be sent to an air interface;
(4) when the BLE5.0 system receives data, the hardware performs de-whitening and CRC (cyclic redundancy check) operations on the received data and then puts the data in a receiving cache, the software and hardware interaction interface software side is informed in an interruption mode, and the interaction interface software side acquires interruption and takes out the data to be further processed by upper-layer software.
Furthermore, the method comprises three interaction modes, namely a shared memory, a register set and an interrupt, wherein the shared memory is used for completing the steps of data transceiving process control and data packet transmission between devices, the register set is used for completing the steps of hardware parameter configuration and state parameter acquisition in the working process of the devices, and the interrupt function is used for completing the step of asynchronously informing software to execute related actions.
Preferably, the software and hardware interaction method is implemented in a shared memory.
The BLE5.0 protocol system is characterized in that a BLE protocol stack is divided into a physical layer, a core protocol stack and an application layer protocol stack from bottom to top, wherein the core protocol stack comprises a host protocol stack and a controller, the host protocol stack comprises a safety management protocol, an attribute protocol, a logic link control and an adaptation layer protocol, the controller comprises a link layer, the physical layer comprises a baseband and a radio frequency, the host protocol stack and the controller are communicated by adopting an HCI (host control interface) protocol specified by the protocol, and a linked list-based software and hardware interaction interface is adopted between the controller and the physical layer to complete data and information interaction.
Further, the system may be implemented in a single chip mode or a dual chip mode.
Preferably, the link layer and the host protocol stack are communicated through an HCI interface, and the interaction with the hardware is realized through a shared memory.
A BLE5.0 protocol system for realizing link layer layering comprises a host protocol stack, a controller and a physical layer, wherein the controller comprises a link layer, the physical layer comprises a baseband and a radio frequency, data and information interaction is completed between the controller and the physical layer by adopting a software and hardware interaction interface, and the link layer is divided into the following modules:
the management module is responsible for the management and the skip of a top layer state machine of a link layer;
the control module completes information interaction and state information maintenance between the devices in a connection state, provides a data and control information channel, and completes device state management and data transmission;
the public module is responsible for receiving the configuration command from the host side and transmitting a command execution result to the host side;
the debugging module is responsible for completing the system working state management in the direct test mode and simultaneously testing and debugging hardware in the development stage;
the driving module is a realization module of software and hardware interfaces, is responsible for interaction of data streams between hardware and software, and is a realization module of system broadcasting, scanning, initialization and connection functions.
Further, the top state machine comprises a broadcast state, a scanning state, an initial state, a connection state and an idle state, and the maintenance of the five states is realized by the management module.
Further, the management module is configured to implement management and scheduling of the device in a non-connection state among a broadcast state, a scan state, an initial state, a connection state, and an idle state, and complete interaction of events and commands with the host side.
Further, the driving module is directly scheduled by the management module, the control module and the public module.
Preferably, each module is implemented by a separate state machine, and information transfer is completed by adopting a message transfer mechanism among the modules.
Preferably, the communication between the link layer and the host protocol stack is realized through an HCI interface, and the interaction with the physical layer is realized through a shared memory.
Preferably, the software and hardware interactive interface adopted between the controller and the physical layer is a linked list-based software and hardware interactive interface, which completes data and information interaction between the controller and the physical layer, and the interface is realized based on Event, and when the interface is realized: each Event is represented by a structure named ECPT, each ECPT contains all parameter information describing one Event, the ECPT structure is associated with a data receiving linked list and a data sending linked list, and the hardware side of the software and hardware interaction interface judges whether the ECPT is effective or not by periodically polling the Event list. Preferably, the software and hardware interactive interface is implemented in a shared memory.
In summary, compared with the prior art, the invention has the following advantages:
the linked list-based software and hardware interaction interface is defined based on Event, combines a data receiving and transmitting linked list to complete information interaction and data transmission with hardware, and is used as a key link for realizing the system.
Through carrying out effectual level and module division to BLE5.0 overall protocol according to the function, each level function is clear and definite, and the communication interface is simple between the module, is convenient for collaborative development and integration. The realization of the functions of the link layer is completed by effectively dividing the modules of the link layer, the realization mode meets the protocol requirements, is convenient for quick realization and debugging, and meanwhile, on the basis of not changing the existing architecture, the function expansion based on a new protocol is completed, the quick iteration of products is realized, the marketing period of the products is shortened, the communication among the modules adopts a message transmission mechanism, the zero copy of data transmission is realized, and the working efficiency of the system is improved.
Drawings
Figure 1 is a schematic diagram of a BLE5.0 protocol system architecture;
FIG. 2 is a schematic diagram of link layer functional module partitioning;
FIG. 3 is a schematic diagram of a link layer top state machine;
FIG. 4 is a schematic diagram of the position of the software and hardware interaction interface in the system;
FIG. 5 is a diagram illustrating software and hardware interaction;
FIG. 6 is a linked list based software and hardware interaction interface.
Detailed Description
To further describe the present invention, it is further described below with reference to the accompanying drawings.
As shown in fig. 1, a BLE5.0 protocol system structure diagram is shown, where a BLE protocol stack is divided into a physical layer, a core protocol stack and an application layer protocol stack from bottom to top, where the core protocol stack includes a host protocol stack and a controller, the host protocol stack includes a security management protocol, an attribute protocol, a logical link control and an adaptation layer protocol, the controller includes a link layer, the physical layer includes a baseband and a radio frequency, an HCI interface protocol specified by the protocol is used between the host protocol stack and the controller for communication, and a linked list-based software and hardware interaction interface is used between the controller and the physical layer for data and information interaction.
The application layer protocol stack is a specific implementation of a plurality of BLE application scenes specified by a protocol, and the protocol is deeply and secondarily encapsulated based on a plurality of application protocols defined by the protocol, including temperature and humidity service, environment service, battery service and the like, so that a user can develop BLE application on the basis of not knowing details of the BLE protocol, and the development process is greatly simplified.
The host protocol stack completes functions of host side data and control path management, security management, equipment discovery, service discovery and the like, and interacts with the bottom layer protocol stack through a Host Controller Interface (HCI).
Host Controller Interface (HCI) is used for communication between a host protocol stack and a controller, and there are two common BLE system implementations, i.e., single chip mode and dual chip mode. In the implementation mode of the single chip, a host protocol stack and a controller run on the same processor, communication between the host protocol stack and the controller can realize user-defined and expansion on the basis of an HCI (host control interface) interface, the interface is completely realized by software, and a specific physical communication interface is not needed. Under the double-chip mode, the interface of the host controller is realized based on physical communication interfaces such as UART and the like, and follows the HCI interface standard defined in the protocol, so that the controller can be adapted to different host protocol stacks, and the use flexibility is improved.
The link layer realizes the state machine management of the equipment in a broadcasting state, a scanning state, an initial state and a connection state, completes the realization of data and control paths from a host to hardware, and completes the realization of various link layer control and interaction processes specified in a protocol. The operation of the link layer on the data packet is performed in the shared memory, so that zero copy operation of data receiving and transmitting from a host controller interface (controller side) to a software and hardware interaction interface in the whole processing process is realized, and the working efficiency of the system is improved.
The physical layer consists of a baseband and a radio frequency module and cooperates with an upper protocol stack to complete the functions of a BLE5.0 protocol layering system.
In the core protocol stack, the link layer completes the definition and realization of the states of equipment broadcasting, scanning, connection and the like, completes the selection of a physical channel, the definition of a related link state, the realization of an equipment filtering mechanism and the like, and for the upper link host side high-level protocol, the lower hardware scheduling and the management of a data receiving and transmitting channel and a control channel are realized, and the lower hardware scheduling and the management are responsible for the framing operation of the core frame of the layer, so that the reasonable functional module division is particularly important for realizing the functions of the link layer, and the functional modules realized by the link layer are divided by the method, and the specific division is shown in fig. 2.
The communication between the link layer and the host protocol stack is realized through an HCI interface, the interaction with hardware is realized through a shared memory, and the link layer is divided into the following layers according to the function requirements in the specific realization process of the link layer function: the system comprises a management module, a control module, a public module, a debugging module and a driving module.
The management module is responsible for management and jumping of a top layer state machine of a link layer, and according to a protocol, the module realizes maintenance of 5 system working states including a broadcast state, a scanning state, a connection state, an initial state and an idle state, and simultaneously realizes management and scheduling of equipment in a non-connection state among the broadcast state, the scanning state, the initial state, the connection state and the idle state, and completes interaction with events and commands on a host side, wherein the top layer state machine of the link layer is shown in fig. 3.
The control module completes information interaction and state information maintenance between the devices in a connection state, provides a data and control information channel, and completes device state management and data transmission. The control module realizes all control processes of a link layer in a protocol, including a connection parameter updating process, a connection parameter requesting process, a starting/stopping encryption process, a characteristic interaction process and the like, and simultaneously realizes functions of process conflict control, overtime control and the like.
The public module is responsible for receiving configuration commands from the host side, such as reading the size of a cache space, resetting a system and the like, and transmitting command execution results to the host side, and the module does not change state information of a link layer and is only responsible for executing the configuration commands and feeding back the state results.
The debugging module is responsible for completing the system working state management in the direct test mode and simultaneously testing and debugging hardware in the development stage.
The driving module is a realization module of a software-hardware interface, is responsible for interaction of data streams between hardware and software, is a realization module of system broadcasting, scanning, initialization and connection functions, completes transmission of data between the software and the hardware by reading and writing a register, interrupting, sharing a memory and the like, controls the working state of the hardware and obtains state information, and can be directly scheduled by a management module, a control module, a public module and the like to realize the interaction of the software and the hardware information.
The system simplifies the system development and debugging process by dividing the functional modules, is convenient for maintenance and protocol extension, adopts a message transmission mechanism to complete information transmission among the modules, realizes each module by an independent state machine, adopts a zero copy mode for cache space management and event processing, and improves the working efficiency of the system.
The baseband and part of the link layer functions of the controller are realized by hardware, the link layer software completes the direct interaction with the hardware, the hardware completes the execution operation of specific tasks by controlling the hardware through the software, and meanwhile, the hardware feeds back the action execution state to the software, so that the software needs an interface to complete the interaction with the hardware, and the position of the software and hardware interaction interface in the whole system is shown in fig. 4. The design and implementation of the software and hardware interactive interface relate to the working efficiency and stability of the system, and meanwhile, the design of the good interactive interface can accelerate the development of the system and shorten the debugging period.
As shown in fig. 5, the software/hardware interface implemented by the present invention includes three ways, namely, shared memory, register set and interrupt. The shared memory is mainly used for completing the data transceiving process control and data packet transmission among devices, the register group completes the hardware parameter configuration and the acquisition of the state parameters in the working process of the devices, and the interrupt function is used for asynchronously informing software to execute relevant actions, such as data receiving, overtime processing, error state reporting and the like.
The shared memory is a memory specially divided for realizing the high-efficiency interaction of software and hardware, the software and the hardware can directly access the memory block to complete the operation of data in the memory, the software and the hardware complete the information interaction through the memory block and need to follow a uniform interaction format and flow, and the invention designs and realizes a linked list-based software and hardware interaction interface and a linked list-based software and hardware interaction method under the mode of sharing the memory by combining the BLE protocol specification, wherein the format definition and the interaction flow definition are included, as shown in figure 6.
Because the standard specifies that the system transmits and receives data in events, the definition of the linked list-based software and hardware interactive interface format and the flow needs to fully consider the attributes of the events, and when the definition is realized: each Event is represented by a structure named ECPT (Event control parameter table), each ECPT contains all parameter information describing one Event, the ECPT structure is associated with a data receiving linked list and a data sending linked list, and the hardware side of the software and hardware interactive interface judges whether the ECPT is effective or not by periodically polling the Event list. When the system carries out data sending operation, the software side of the software and hardware interaction interface is only required to put prepared data in a sending cache, an ECPT valid flag is set to inform the hardware side of the software and hardware interaction interface of sending data, when the hardware polls that the ECPT is valid, the contents in the sending cache are obtained according to the specified parameters in the ECPT, and the data to be sent is sent to an air interface; when the system receives data, the hardware carries out de-whitening and CRC check operation on the received data and then puts the data in a receiving cache, the software and hardware interaction interface software side is informed in an interruption mode, and the interaction interface software side obtains interruption and takes out the data to be further processed by upper-layer software.
The BLE5.0 protocol system implemented by the present invention, the BLE5.0 protocol system implemented by the link layer layering, and the linked list-based software and hardware interactive interface applied in the system can be applied to the layering and implementation of other wireless protocol stacks, and the above are preferred embodiments of the present invention, and for those skilled in the art, several improvements may be made without departing from the principle of the present invention, and these improvements should also be regarded as the protection scope of the present invention.

Claims (8)

1. A BLE5.0 protocol system implementing link layer layering, comprising:
a host protocol stack, a controller, a physical layer;
the controller includes a link layer;
the physical layer comprises a baseband and a radio frequency;
data and information interaction is completed between the controller and the physical layer by adopting a software and hardware interaction interface;
the link layer is divided into the following modules:
the management module is responsible for the management and the skip of a top layer state machine of a link layer;
the control module completes information interaction and state information maintenance between the devices in a connection state, provides a data and control information channel, and completes device state management and data transmission;
the public module is responsible for receiving the configuration command from the host side and transmitting a command execution result to the host side;
the debugging module is responsible for completing the system working state management in the direct test mode and simultaneously testing and debugging hardware in the development stage;
the driving module is a realization module of software and hardware interfaces, is responsible for interaction of data streams between hardware and software, and is a realization module of system broadcasting, scanning, initialization and connection functions.
2. A BLE5.0 protocol system implementing link layer layering according to claim 1, wherein:
the top state machine comprises a broadcast state, a scanning state, an initial state, a connection state and an idle state, and the maintenance of the five states is realized by the management module.
3. A BLE5.0 protocol system implementing link layer layering according to claim 2, wherein:
and the management module is used for realizing the management and the scheduling of the equipment in the non-connection state among the broadcasting state, the scanning state, the initial state, the connection state and the idle state and finishing the interaction of events and commands with the host side.
4. A BLE5.0 protocol system implementing link layer layering according to claim 1, wherein:
the driving module is directly scheduled by the management module, the control module and the public module.
5. A BLE5.0 protocol system implementing link layer layering according to claim 1, wherein:
each module is realized by a separate state machine, and information transmission is completed among the modules by adopting a message transmission mechanism.
6. A BLE5.0 protocol system implementing link layer layering according to claim 1, wherein:
the communication between the link layer and the host protocol stack is realized through an HCI interface, and the interaction with the physical layer is realized through a shared memory.
7. A BLE5.0 protocol system implementing link layer layering according to claim 1, wherein:
the software and hardware interactive interface is a linked list-based software and hardware interactive interface, completes data and information interaction between the controller and the physical layer, and is realized based on Event, and during realization: each Event is represented by a structure named ECPT, each ECPT contains all parameter information describing one Event, the ECPT structure is associated with a data receiving linked list and a data sending linked list, and the hardware side of the software and hardware interaction interface judges whether the ECPT is effective or not by periodically polling the Event list; wherein ECPT denotes an event control parameter table.
8. A BLE5.0 protocol system implementing link layer layering according to claim 7, wherein:
the software and hardware interaction interface is realized under a shared memory.
CN201710205000.9A 2017-03-30 2017-03-30 BLE5.0 protocol system Active CN106888271B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010271543.2A CN111510481B (en) 2017-03-30 2017-03-30 Software and hardware interaction method applied to BLE5.0 protocol system
CN201710205000.9A CN106888271B (en) 2017-03-30 2017-03-30 BLE5.0 protocol system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710205000.9A CN106888271B (en) 2017-03-30 2017-03-30 BLE5.0 protocol system

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN202010271543.2A Division CN111510481B (en) 2017-03-30 2017-03-30 Software and hardware interaction method applied to BLE5.0 protocol system

Publications (2)

Publication Number Publication Date
CN106888271A CN106888271A (en) 2017-06-23
CN106888271B true CN106888271B (en) 2020-06-02

Family

ID=59182487

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202010271543.2A Active CN111510481B (en) 2017-03-30 2017-03-30 Software and hardware interaction method applied to BLE5.0 protocol system
CN201710205000.9A Active CN106888271B (en) 2017-03-30 2017-03-30 BLE5.0 protocol system

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN202010271543.2A Active CN111510481B (en) 2017-03-30 2017-03-30 Software and hardware interaction method applied to BLE5.0 protocol system

Country Status (1)

Country Link
CN (2) CN111510481B (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109683877B (en) * 2018-12-11 2022-03-15 中国航空工业集团公司西安航空计算技术研究所 SystemC-based GPU software and hardware interaction TLM system
CN109831765A (en) * 2019-03-06 2019-05-31 东南大学 A kind of hard-wired low-power consumption bluetooth HCI layer data method of flow control
CN110572387B (en) * 2019-09-04 2022-05-10 大唐半导体科技有限公司 Link layer processing method
CN110519740B (en) * 2019-09-04 2022-07-22 大唐半导体科技有限公司 Link layer processing device
CN111884684B (en) * 2020-08-26 2021-07-16 北京百瑞互联技术有限公司 Bluetooth physical connection method and system based on state machine control

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100514233C (en) * 2007-09-30 2009-07-15 重庆邮电大学 EPA on-site controller based on SOPC
CN102916969B (en) * 2012-10-29 2015-07-08 广州碧德电子科技有限公司 Uninterrupted data communication equipment and communication method
CN104184687B (en) * 2013-05-23 2018-03-09 北京信威通信技术股份有限公司 A kind of flow control method and hardware accelerator circuit of communications baseband processing
US9832578B2 (en) * 2015-02-23 2017-11-28 Intricon Corporation Enabling concurrent proprietary audio and Bluetooth low energy using enhanced LE link layer for hearing device

Also Published As

Publication number Publication date
CN106888271A (en) 2017-06-23
CN111510481B (en) 2023-01-10
CN111510481A (en) 2020-08-07

Similar Documents

Publication Publication Date Title
CN106888271B (en) BLE5.0 protocol system
CN107018175B (en) Scheduling method and device of mobile cloud computing platform
CN109976925B (en) Method and system based on mixed multi-system inter-core real-time communication
CN103645954B (en) A kind of CPU dispatching method based on heterogeneous multi-core system, device and system
CN104699736B (en) A kind of distributed larger scale data acquisition system and method based on movable equipment
CN203206480U (en) Client device for intelligent scheduling of network tasks based multiple network scheduling constraints
Kim et al. System architecture directions for post-soc/32-bit networked sensors
CN107439030A (en) DRX processing in LTE permits to assist access operation
CN107846672A (en) Communication pattern system of selection, IoT equipment and the storage medium of multimode IoT equipment
CN103092701A (en) Communication method, communication device and electronic device
CN112332997B (en) Distribution network method of terminal equipment, terminal equipment and computer readable storage medium
CN108337127A (en) application performance monitoring method, system, terminal and computer readable storage medium
CN103812953B (en) Communication interface system of micro-control unit and ARM (advanced RISC (reduced instruction-set computer) machines) processor
CN103107825A (en) Bluetooth adapter, system and method of realizing mobile terminal controlling operation terminal
CN110417871A (en) A kind of smart machine upgrade method
CN103826246B (en) A kind of multiband wireless sensor node
CN110032429A (en) Information processing method, device, mobile terminal and computer readable storage medium
CN106059877B (en) EtherCAT main station module based on SPARC framework CPU
CN103678244B (en) A kind of smart machine without using application processor
Ruckebusch et al. A unified radio control architecture for prototyping adaptive wireless protocols
CN106843890A (en) Sensor network, node and its operation method based on intelligent decision
CN104918113B (en) A kind of the function card end compatibility method and system of module TV
CN106354486B (en) The method and system of nand flash equipment management
CN111459034A (en) Household appliance
CN102945181A (en) Method for updating device software based on power line

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
TA01 Transfer of patent application right

Effective date of registration: 20190429

Address after: Room 402-403, Building D, Zhangjiagang Economic and Technological Development Zone, Suzhou City, Jiangsu Province

Applicant after: Peach Core Technology (Suzhou) Co., Ltd.

Address before: 100080 Haidian Street, Haidian District, Beijing

Applicant before: Beijing firefly Technology Co., Ltd.

TA01 Transfer of patent application right
GR01 Patent grant
GR01 Patent grant