JP4053407B2 - Electronic device capable of communication, communication method therefor, and recording medium for the communication method - Google Patents

Description

Technical field
The present invention relates generally to electronic devices, and more particularly to a system and method for adjusting a schedule (scheduling) of a communication period between the electronic devices and program data including executable instructions for executing the method. And a computer-readable recording medium.
[0001]
Background
Computer and communication technology continues to advance at a rapid pace. In fact, computers and communication technologies are involved in many ways in people's daily lives. For example, many electronic devices used by consumers today incorporate a small computer within the electronic device.
[0002]
These small computers can vary in size and degree of sophistication. These small computers can vary in degree of technology from microcontrollers to fully functional computer systems. For example, the small computer may be a one-chip computer such as a microcontroller, a one-board type computer such as a controller, a typical desktop computer such as an IBM-PC compatible, or the like.
[0003]
Computers typically include one or more processors. At least one processor is typically interconnected to different external inputs and outputs to function to operate a particular computer or electronic device. For example, a thermostat processor is connected to a button for selecting a temperature setting, to a heating furnace or an air conditioner for changing the temperature, and to a sensor for displaying the temperature on a display by reading the temperature. Also good.
[0004]
Many appliances, electronic devices, etc. include one or more small computers. For example, thermostats, furnaces, air conditioning systems, refrigerators, telephones, typewriters, automobiles, vending machines, and many different types of industrial equipment are now typically equipped with small computers or processors inside them. Yes.
[0005]
Computer software runs the processors of these computers and sends instructions to the processors to do to perform certain tasks. For example, computer software running on a thermostat will shut down when the air conditioner reaches a certain temperature or turn on the heater when needed.
[0006]
These types of small computers that are part of devices, appliances, tools, etc. are often referred to as embedded systems. The phrase “embedded system” usually refers to computer hardware and software that is part of a larger system.
[0007]
Embedded systems may not include typical input / output devices such as a keyboard, mouse, and / or monitor. Usually, at the heart of each embedded system is at least one processor.
[0008]
As more and more electronic devices and embedded systems are used and information exchange demands increase, more devices can detect surrounding devices and establish electronic communications with these devices now It has become.
[0009]
The Bluetooth specification defines one standard that allows devices to communicate with each other through short-wave radio signals. Many types of devices can benefit from being able to connect with other devices without requiring user intervention. For example, printers, personal digital assistants, digital cameras, phones, laptop computers, video monitors, electronic calendars, desktops, fax machines, keyboards, joysticks, etc. are all part of the short wavelength wireless system for connecting to other devices. It may be.
[0010]
By enabling this type of communication, a bridge is provided to an existing data network to form a small personal special grouping of each device connected remotely from the fixed network infrastructure. In this way, a device network can be formed quickly as each device discovers each other.
[0011]
However, inefficiencies such as more devices trying to communicate with each other, causing communication slowdowns or otherwise hiding the entire communication of one or more electronic devices May occur. Thus, benefits can be gained if communication between each electronic device is enhanced with additional systems and methods to provide a more effective communication technology.
[0012]
Summary of the Invention
It is disclosed that the electronic device is adapted to communicate with a first device network and to a second device that is part of the second device network.
[0013]
The device is a communication module for communicating with a processor and each other device including a second device and at least one device from a first device network in electronic communication with the processor. Including.
[0014]
A memory may also be included for data storage in electronic communication with the processor.
[0015]
The electronic device may also include a pseudo-random scheduler for setting each time point that defines a schedule for the electronic device to communicate with other devices. A dynamic scheduler may also be included to change the schedule. The electronic device may also include an event queue.
[0016]
The dynamic scheduler may execute a fair allocation method that dynamically allocates communication processing capability. The above fair allocation method may include extending the previous communication period. The fair allocation method may also include reducing the number of start time points in the event queue.
[0017]
Opportunistic allocation methods may be executed by a dynamic scheduler to dynamically allocate communication processing capabilities. The opportunistic assignment method may include evaluating waiting traffic and device availability and changing the airline schedule based on the evaluation.
[0018]
The pseudo-random scheduler may be configured to execute a preset synchronized method in order to generate each time point. Further, the pseudo random scheduler may execute a preset asynchronous method in order to generate each time point.
[0019]
Real-time methods may also be used with a pseudo-random scheduler. The event queue may include a plurality of starting time points. A plurality of channel identifiers may be stored in the event queue. Furthermore, the event queue may include a plurality of indicators that indicate that data is waiting.
[0020]
The electronic device may further include a state machine for scheduling and communication. The state machine may include an idle state, a data state, a schedule negotiation state, and a re-establishment state.
[0021]
The electronic device may be used in a Bluetooth system. In such an environment, the device may be part of a piconet. If the device is part of a piconet, the pseudo-random scheduler may be adapted to provide each time point that defines a schedule for an electronic device that communicates with each piconet.
[0022]
A method for scheduling a communication period between electronic devices in a pseudo-random manner and dynamically is also disclosed. The method may include transmitting output data from the first electronic device to the first device network and receiving input data from the first device network by the first electronic device.
[0023]
The method also includes the steps of discovering a second electronic device of the second device network and each pseudo-random time point defining a schedule for communicating with the first device network and the second device network. Providing the time points in the event queue; dynamically changing the schedule to add additional communication bandwidth to the at least one communication channel to add additional communication processing power; May be included.
[0024]
A computer readable medium for executing program data is also disclosed. The program data includes executable instructions for performing the method. The method may include transmitting output data from the first electronic device to the first device network and receiving input data from the first device network by the first electronic device.
[0025]
The method also includes the steps of discovering a second electronic device of the second device network and each pseudo-random time point defining a schedule for communicating with the first device network and the second device network. Providing the time points in the event queue; dynamically changing the schedule to add additional communication bandwidth to the at least one communication channel to add additional communication processing power; May be included.
[0026]
This embodiment will become more fully apparent from the following description taken in conjunction with the accompanying drawings and the appended claims.
[0027]
It will be understood that each of these drawings is merely representative of exemplary embodiments and is not intended to limit the scope of the invention. This embodiment will be illustrated by the further specification and the accompanying drawings.
[0028]
Detailed description
In the present specification, as shown in each drawing and generally described, it is apparent that each configuration of the present embodiment is easily understood and arranged and designed in various different configurations. Will.
[0029]
Accordingly, the following more detailed description of the system and method embodiments of the present invention as represented in the drawings is merely an embodiment of the present invention, as claimed in the claims below. It is not intended to limit the scope of the present invention.
[0030]
FIG. 1A is a block diagram showing an electronic device pair 106 including two electronic devices (devices) 102 and 104. The electronic device pairs 106 can initiate communication 108 with each other.
[0031]
The electronic devices 102 and 104 include vending machines, telephones, door locks, temperature detectors, motors, switches, light sources, printers, fax machines, refrigerators, health monitors, elevators / escalators, copiers, scanners, manufacturing facilities, Examples include industrial equipment, computer equipment, peripheral equipment, security systems, monitoring equipment, thermostats, and the like.
[0032]
FIG. 1B shows a timing chart of each communication period including a schedule (plan) 110 for the communication period 112 between the respective electronic devices 102 and 104 of the electronic device pair 106.
[0033]
Usually, the schedule 110 is created according to a communication request of any electronic device of the electronic device pair 106. The schedule 110 may be specific to the electronic device pair 106 or may be set in both the electronic devices 102 and 104.
[0034]
As shown, the schedule 110 may include time points 114 and 116 that are signals indicating the start and end of communication between the electronic device pair 106.
[0035]
The time between the start time point 114 and the event end time point 116 is called the communication period 112. The start time point 114 is a typical method used to initiate communication between the two electronic devices 102, 104. Both electronic devices 102, 104 are normally aware of the start time point 114 so that communication can begin at the start time point 114.
[0036]
In the embodiment of FIG. 1A, both electronic devices 102 and 104 can end communication. The electronic device can optionally terminate the communication period 112, but in general, the communication period 112 is terminated by colliding with a time point from another electronic device pair schedule.
[0037]
The end of the communication period 112 may be executed by exchanging signals between the electronic device pairs 106 for each connection relationship. The end time point 116 may be used to end the communication period 112, but is not necessarily so. The end time point 116 is created by a schedule negotiation process performed between each electronic device in the pair.
[0038]
Typically, the starting time point 114 is determined by a unique (unique) random pre-set pseudo-random schedule relative to the pseudo-random schedule for each other pair of electronic devices connected together.
[0039]
The starting time point 114 is determined by negotiation between each pair of electronic devices where the negotiated time point is within the active range of the communication period as determined by a scheduled pseudo-random schedule. Also good. The above negotiation process is performed between a pair of electronic devices and is used to create free time in a schedule for other purposes.
[0040]
The electronic device pair 106 typically consists of one electronic device having a master role with respect to the connection and another electronic device having a slave role. The master electronic device generally initiates and controls the connection, while the slave electronic device responds to the master command. The schedule typically uses the master electronic device clock as the time base. The slave electronic device may maintain synchronization with the clock. If available for both electronic devices, another time base may be used.
[0041]
FIG. 1 (c) shows a series of communication periods 118, 120, including a plurality of start time points 124, 126, 128, a plurality of end time points 130, 132, 134, and / or each event end. 12 is a timing chart showing 122.
[0042]
In many situations, the electronic device pair 106 may continue to communicate with each other over a period of time. These communications may take place in a number of each communications period 118, 120, 122 rather than one continuous communications period 112.
[0043]
FIGS. 1 (a) through 1 (c) show two electronic devices 102, 104 communicating with each other, but there is a situation where there is communication between each electronic device exceeding two. In some cases, for example, as shown in FIG. 2 (a), there may be two electronic device (device) networks 202,204.
[0044]
Electronic device A 206, electronic device B 208, electronic device C 210, and electronic device D 212 form a first electronic device network 202. The electronic device E214, the electronic device F216, the electronic device G218, and the electronic device H220 form a second electronic device network 204.
[0045]
FIG. 2 (a) shows two separate electronic device networks 202, 204, in other words two different systems. The first electronic device network 202 includes one master and three slaves. The electronic device A206 is used as a master, while the electronic device B208, the electronic device C210, and the electronic device D212 are used as slaves. The second electronic device network 204 includes a master (electronic device E214) and three slaves (electronic device F216, electronic device G218, and electronic device H220).
[0046]
As shown, intra-system communication 222 occurs between each electronic device in the first electronic device network 202 and between each electronic device in the second electronic device network 204.
[0047]
One application for embodiments of the present invention may relate to the Bluetooth (Bluetooth) standard and the personal area network associated with Bluetooth. The Bluetooth standard described in the specification of the Bluetooth system is incorporated herein by reference.
[0048]
Depending on the type of communication system used, the application of the scheduler of the present invention can be extended to what was previously considered in the internal system link. The present invention is particularly preferably applied to a Bluetooth system in which a piconet is an individual independent system. In the Bluetooth field, each electronic device network 202, 204 may both be a piconet.
[0049]
When a connection between each piconet is formed, the scheduler of the present invention will both a new connection and, if a previous piconet master exists, a connection in the previous piconet to that piconet master. It is applicable to.
[0050]
Of course, it will be apparent to those skilled in the art that the embodiments disclosed herein and the principles of the present invention are not limited to personal area networks and / or Bluetooth networks.
[0051]
The inventive principles described herein are applicable to various types of communication systems, including each electronic device and / or each computer communicating with each other.
[0052]
Further, in the example shown in FIGS. 2 (a) to 2 (d), three generally possible ways of connecting two networks 202, 204 are shown. As described above, in FIGS. 2A to 2D, the electronic device A206 and the electronic device E214 serve as masters, while the other electronic devices serve as slaves. Thus, a master / slave relationship exists between the master and slave of each electronic device network 202,204.
[0053]
FIG. 2B shows an inter-system communication link 224 between the electronic device D212 and the electronic device F216. The scheduling apparatus and methods described herein may be used for the intersystem communication link 224.
[0054]
Further, as illustrated, each link between the electronic device A 206 and the electronic device D 212 and between the electronic device E 214 and the electronic device F 216 may be handled as the inter-system communication link 224.
[0055]
Therefore, the original connection between the slave and its master may now be treated as an intersystem link as the slave electronics will not be available to the master at all times due to the added link. .
[0056]
Each communication between the electronic device A206 and the electronic device D212, and between the electronic device E214 and the electronic device F216, now has a processing capability of each slave (electronic device D212 and electronic device F216) rather than just one connection. Rather, it may be rescheduled because it will be shared by each of the two communications.
[0057]
FIG. 2 (c) shows an intersystem communication link 224 between two master electronic devices 206, 214. FIG. 2D shows an intersystem communication link 224 between a master (electronic device A 206) and a slave (electronic device F 216).
[0058]
When the embodiments of FIGS. 2 (a) -2D are used and implemented in a Bluetooth environment, the two systems, each network 202, 204 and intersystem communication link 224, may be referred to as a scatternet. Good. As described above, each of the embodiments described herein and the principle of the present invention are not limited to the Bluetooth environment but are widely applied.
[0059]
Each of the embodiments described herein provides a solution to the scheduling problem for each electronic device that needs to have any number of connections. Further, each of the embodiments described in the present specification enables an arbitrary connection relationship (topology) of each electronic device to effectively communicate with each other when each connection relationship is treated as an interconnection between systems. ing.
[0060]
FIG. 3A shows a system of a simple connection relationship (topology) including an electronic device B302 that communicates with each of the other two electronic devices A304 and C306. The electronic device A 304 and the electronic device B 302 constitute an electronic device pair 308. Similarly, the electronic device B302 and the electronic device C306 constitute an electronic device pair 310.
[0061]
For each pair 308, 310 of communicating electronic devices, there is a schedule for communication showing each time point of start, as shown in FIG. 3 (b). Each communication period 314, 316, 318 between electronic device B302 and electronic device A304 begins through each time point 320, 322, 324 of the start of communication AB.
[0062]
Each start time point 320, 322, 324 starts a respective communication period 314, 316, 318 for the pair 308 corresponding to each electronic device 304, 302, respectively. Each communication period 326, 328, 330 between electronic device B302 and electronic device C306 is initiated through a respective time point 332, 334, 336 of the start of communication BC. Each of these start time points 332, 334, 336 starts a respective communication period 326, 328, 330 for the B-C pair 310 of each electronic device 302, 306.
[0063]
As shown in the figure, each start time point ends an event for the previous communication period. The end of a communication period is signaled to another electronic device when another start time point occurs to collide with the currently active communication period. For example, the start time point 320 starts a communication period 314 between the electronic device A 304 and the electronic device B 302.
[0064]
The communication period 314 continues until the start time point 332 is generated as a signal indicating the start of the communication period 326 between the electronic device B302 and the electronic device C306. FIG. 3 (b) shows a typical operation for the embodiment shown in FIG. 3 (a).
[0065]
FIG. 4 shows the connection relationship (topology) of the electronic device network. A communication link 402 exists between electronic device A 404 and electronic device B 406. Multiple electronic devices X in electronic communication with electronic device A 404 ₁ ~ X _n There is. Similarly, a plurality of electronic devices Y in electronic communication with electronic device B406 ₁ ~ Y _m There is.
[0066]
The performance (execution) of the system according to the present invention provides a fair distribution of processing power. The above performance can be easily generalized when all the links are fully utilized. The above relationship is given by the following equation for the generalized system illustrated in FIG.
[0067]
The processing capability available on link A-B 402 is inversely proportional to the total number of each other intersystem link in which both electronic device A 404 and electronic device B 406 are participating.
[0068]
The following equation does not take into account overhead (overhead costs) based on switching between connection relationships and overhead due to transmission / reception of other signals required for system operation. The following Cap _AB The number of indicates the relative processing power available for the connection. It indicates the relative amount of time utilized for communication between a pair of electronic devices. The above relationship is applicable to systems where the density of each time point is equal on each link between all systems, and each link has a random distribution relative to the others.
[0069]
Cap _AB = 1 / (1 + n + m)
FIG. 5 is a block diagram showing each configuration of main hardware generally used in the electronic / built-in electronic device 500. The electronic device 500 typically includes an input unit 504 and / or an output unit 506 and a processor 502 in electronic communication with them.
[0070]
The processor 502 is capable of electronically communicating with the processor 502, that is, operating them on input and / or output sections 504, 506 that can be input and / or output in the form of electrical signals. It is connected to the.
[0071]
Embodiments of the electronic device 500 may include an input 504, an output 506, and a processor 502 in the same physical structure, and are included in separate housings and structures. May be.
[0072]
The electronic device 500 may include a memory 508. The memory 508 may be provided as a separate configuration from the processor 502, may be provided as an on-board memory, or may be provided as part of the processor 502. For example, microcontrollers often include a certain amount of on-board memory.
[0073]
Further, a communication unit 510 that electronically communicates with the processor 502 and the processor 502 is provided. The communication unit 510 may be used for communication with other electronic devices. Therefore, the communication unit 510 of various electronic devices may be designed to communicate with each other in order to send signals and messages between the electronic devices 500.
[0074]
In addition, the electronic device 500 may include a communication transmitting / receiving unit 512 that is another communication port. Furthermore, another component 514 that is another component may be included in the electronic apparatus 500. Of course, it will be apparent to those skilled in the art that many different types of electronic devices can be used with the embodiments described herein. Accordingly, the block diagram of FIG. 5 is merely meant to illustrate typical components of the embedded electronic devices 102, 500 and is not meant to limit the scope of this embodiment.
[0075]
FIG. 6 shows software modules that may be used in electronic device 600. Built-in application 602 may be used to operate electronic device 600. Built-in application 602 may include functionality necessary for operation of electronic device 600.
[0076]
An input / output module 604 may be used to receive data from the input unit 504 and send data to the output unit 506. Depending on the type of electronic device 600, the specific functionality of the input / output module 604 may vary.
[0077]
The inter-electronic device communication module 606 may include functionality for handling incoming and outgoing messages. For example, the communication module 606 between electronic devices may include instructions for sending and receiving each communication using the communication unit 510.
[0078]
The communication module 606 between the electronic devices may be configured to send or transmit outgoing data 608 and receive incoming data 610.
[0079]
The electronic device 600 may generally include software for accomplishing each task including communication, input / output of the electronic device 600, and monitoring and control of the electronic device 600.
[0080]
The communication module 606 between the electronic devices may mean a routine or instruction of a computer program that handles each communication via the communication unit 510 or the communication transmitting / receiving unit 512.
[0081]
The input / output module 604 may mean a routine or instruction of a computer program that handles input to the electronic device 600 and output from the electronic device 600.
[0082]
For example, if there is a button (not shown) on the electronic device 600, the input / output module 604 may include code necessary to process input from the button (not shown).
[0083]
The application 602 may function as a main program that controls the electronic device 600 and executes each task of the electronic device 600. It will be apparent to those skilled in the art that each software block described above is merely an example, and the configuration of each block illustrated is not necessarily required to implement the present embodiment.
[0084]
As mentioned above, the embodiments described herein allow many different types of electronic devices 102, 500, 600 to be available and used. Typically, these electronic devices are already loaded with the software necessary to run the electronic device 600.
[0085]
The embodiments described herein are usable by each electronic device 102, 500, 600 having almost all electronic communication and some processing capabilities.
[0086]
In addition, the electronic device may include a pseudo-random scheduler 612 and a dynamic scheduler 614 that dynamically performs allocation. In the following, both the pseudo-random scheduler 612 and the dynamic scheduler 614 will be described.
[0087]
As described below, the dynamic scheduler 614 may include a fair allocation component 616 and an opportunistic allocation component 618. An event queue (event queue) 620 may also be included. The event queue 620 includes one or more queue items 622. Each queue item 622 may correspond to a specific communication channel.
[0088]
Each queue item 622 includes state information 630, status information 632, and other information 634 along with each communication time point 624, channel identifier (channel ID) 626, and waiting data 628. Also good.
[0089]
The above data that may be stored in the event queue 620 is described more fully below. It is disclosed herein that the method of the present invention dynamically allocates processing power between system interconnections when using a scheduled allocation that is not used by a pair of electronic devices. Is provided.
[0090]
A distributed algorithm is used to distribute the processing power to each intersystem link where traffic is available. Unused processing power may be assigned on a fair basis first, and then processing power may be assigned opportunistically where communication is possible.
[0091]
The above algorithm attempts to maximize the utilization of communication processing power for each electronic device. The principle used to achieve fair allocation is to effectively remove intersystem interconnections from electronic devices when there is actually no traffic without connection interruption.
[0092]
This, due to the inherent fairness of the pseudo-random scheduler 612, will reallocate unused processing power for each link that has traffic.
[0093]
In the embodiment described herein, two mechanisms are used to achieve a fair reassignment of unused processing power, one is a reduction in the starting time point and the other is a previous communication. It is an extension of the period.
[0094]
In the start time point reduction method, the electronic device monitors its internal event queue 620 and traffic on the link. If there is no traffic, the set schedule is changed by removing each time point of start.
[0095]
The schedule is changed so that there is only a portion remaining from each original time point. For example, in one possible embodiment, each starting time point may be removed so that only the fourth in every original time point is used.
[0096]
The method can effectively remove the connection to the short interval electronic device and allow its processing power to be used by each other intersystem link.
[0097]
The negotiation process between the electronic device pair is used to change the schedule and remove each time point. The above-mentioned method for extending the previous communication period means that the current communication period has been completed early (i.e., before the next start time point) with respect to other electronic devices with which the electronic device was previously communicating. To re-establish communication with the other electronic device that was communicating with.
[0098]
In this way, the above communication method is used to extend the previous communication period, and the electronic devices that have not fully used the scheduled processing power are effectively removed.
[0099]
As a general rule, opportunistic assignment attempts to maximize the number of parallel communication transfers. An additional process is performed to achieve an opportunistic assignment. In the above process, the electronic device 102 monitors the waiting traffic for each link and monitors how much the electronic device is available for establishing communications.
[0100]
The information equivalent to the monitor may be obtained from signal communication that occurred when the previous communication period was terminated for its respective intersystem link.
[0101]
Thereafter, the electronic device 102 may attempt to establish communication with another electronic device that has the waiting data to transfer and is available for communication. If two or more electronic devices meet the criteria, the most recently communicated electronic device may be selected from each of the electronic devices. These rules can improve the likelihood that both electronic devices can try to establish a connection with each other and establish communication.
[0102]
Some applications have very stringent communication requirements that may not be met with a pseudo-random scheduler 612 between systems. These requirements are usually expressed in terms of fixed data bit rate and maximum latency. In addition, the application generally provides the service only if sufficient processing power is available, negotiating the processing power required when establishing a channel for the service (the benefits of processing). Will be done.
[0103]
In order to meet more stringent requirements, methods are provided that support resource reserved channels (RRC). The above resource securing channel type may be implemented as a scheduled communication with an information period and a duty cycle between each information period fixed in a certain period.
[0104]
Resource reservation channel traffic has a higher priority than pseudo random scheduled (PRS) channels, and if a schedule conflict occurs, resource reservation channel traffic Traffic is replaced with PRS traffic. The above PRS schedule is modified to accept any RRC traffic.
[0105]
In the design of this embodiment, the resource securing channels are negotiated so that they do not collide with each other. Due to the periodic nature of the resource-reserved channel, in many cases the resource-reserved channel will use the fixed processing power of the communication link.
[0106]
Due to the periodic nature of the above, the processing power captured from PRS traffic is randomly distributed among all links. As a result, traffic between systems scheduled by the PRS method will be reduced by the RRC but will be fairly fairly allocated between each connection between systems.
[0107]
FIG. 7 shows an embodiment of a state machine for the scheduler of electronic device 102. Each electronic device 102 may execute the state machine to run a scheduler and support other related functions.
[0108]
The system description associated with the state machine may apply MAC / baseband components that are responsible for managing intersystem traffic for the electronic device 102.
[0109]
Unless stated otherwise, the above information applies equally to both electronic devices of an electronic device pair. The above protocol is mainly based on a master / slave access mechanism. The Bluetooth standard uses a master / slave relationship.
[0110]
To illustrate and clearly illustrate an example of how the state machine is used, the protocol is described in master / slave and sometimes in Bluetooth terms.
[0111]
Of course, for those skilled in the art, the principles and embodiments of the present invention described herein may be applied to a wide variety of variations of the electronic device 102 configured for electronic communication with other electronic devices. It will be clear.
[0112]
The aforementioned idle state 702 is illustrated in FIG. There is no PRS intersystem traffic in the idle state 702. The electronic device 102 is free to communicate with other electronic devices within its system or network.
[0113]
The electronic device 102 may be designed to avoid communication that may extend the PRS scheduled intersystem communication period. For Bluetooth systems, the above avoidance can occur when a long packet is received that extends past a scheduled time point.
[0114]
Also, the aforementioned data state 704 is shown in FIG. In the data state 704, data is exchanged between the intersystem electronic devices. Communication continues until an end event occurs.
[0115]
FIG. 7 shows a schedule negotiation state 706. This state 706 is used to change the schedule. Either electronic device may initiate this process 706 or state 706. This state 706 is an effective sub-state of the data state 704 because an active communication period is required to support the exchange of messages necessary for schedule negotiation.
[0116]
The aforementioned re-establishment state 708 is also illustrated in FIG. The re-establishment state 708 executes a procedure for establishing communication during a period when there is no scheduled communication. This mechanism is used to distribute unused processing power to intersystem channels that have data available for exchange.
[0117]
FIG. 7 shows events that cause a transition from one state to another state and events that maintain the electronic device 102 in the same state. An intersystem schedule manager (not shown) maintains a list of each communication event for each intersystem channel in the event queue 620. The event list is made up of a list in which each scheduled time point 624 and corresponding channel identifier 626 are ordered.
[0118]
The above scheduled event occurs when the current time matches the scheduled time. When the starting time point occurs, the electronic device 102 enters the data state 704 and begins communicating with the corresponding electronic device. If the electronic device is currently active for another communication channel, the electronic device will perform a kill process on the channel before entering the data state 704. .
[0119]
There are many different types of end events that may occur. Forced termination occurs when there is data waiting for data exchange, but one of the electronic devices wants to terminate the current communication period. The electronic device may perform the above termination due to another scheduled inter-system communication (or interpiconet communication in a Bluetooth network) or for other reasons.
[0120]
The electronic device ends the communication period by asserting (asserting) the display (instruction) of this event in a message to the other electronic device. Another type of end event is a scheduled end. When the schedule negotiation process 706 or state 706 is successfully completed, an end time point is agreed for the current communication period. When this time point occurs, a scheduled end event occurs.
[0121]
An event indicating that data has been exhausted is another type of end event. The above event occurs when all available data has been transferred by both electronic devices. The occurrence of this event is signaled to the other electronic device by a message indicating the event.
[0122]
The master electronic device signals the other electronic device that it has no data to send by conveying a Poll packet. The slave indicates that there is no data to send to the slave by passing a Null packet. Thus, when both electronic devices indicate that they have no data to transfer, an end event that indicates that the data has been exhausted occurs.
[0123]
Another type of end event is a non-responsive end event. A non-responsive end event is to occur when communication is scheduled but does not occur. The electronic device may wait for communication for a certain period. If no data is received, the communication period may be terminated.
[0124]
If the electronic device is the master, a non-response type end event occurs when no response is received for any packet sent to the slave electronic device. If the electronic device is a slave, an unresponsive end event will occur when it does not receive any packets from the master.
[0125]
When this embodiment is used in a Bluetooth network, the above-mentioned non-response type end event may occur when there is a scatternet scheduling violation.
[0126]
The non-responsive end event can occur when the electronic device has high priority activity and cannot meet the schedule agreed upon by the electronic device. The non-response end event can generally occur for a process that has an indefinite duration (eg, page response or inquiry response).
[0127]
Other types of events are also shown in FIG. 7, further illustrating other events that can cause changes in state. A negotiation request event is used by the electronic device to initiate the schedule negotiation process 706. The negotiation request event occurs during an active communication period between two electronic devices.
[0128]
An event (status) waiting for data is an indicator (indicator) of a composite status in all the inter-system links so that the electronic device can recognize the event or status (status). If any of the links is in a state where data to be transferred remains, the indicator may be true. The above state is well known by the method in which the communication period is terminated.
[0129]
For links where an event indicating that data has been exhausted occurs, the indicator may be false. The indicator is true for links that are forcibly terminated or non-responsive termination.
[0130]
Also, the event or state without data waiting is an indicator of the composite state of all the intersystem links, as recognized by the electronic device. This indicator indicates that there is no data waiting for each intersystem link with which the electronic device is associated.
[0131]
Further, the communication re-establishment event described above is shown in FIG. The above communication re-establishment event occurs when the POLL response procedure is completed and it is confirmed that the communication channel has been established.
[0132]
Failure to re-establish the event indicates that the electronic device was unable to establish communication during the re-establishment process 708. As described above, the idle state 702 is entered whenever there is no active PRS intersystem communication. The time spent in the idle state 702 depends on the inter-system traffic load and all of the changes that are matched to the pseudo-random (more generally inter-system) schedule between piconets.
[0133]
The electronic device may change the intersystem schedule so that the time for the idle state 702 can be freely set if needed for intrasystem links and other activities. The idle state 702 may imply that the electronic device is not involved in any PRS intersystem traffic, but may be active in other intra-system communication activities. .
[0134]
While the electronic device is in the idle state 702, the electronic device typically monitors the intersystem schedule and changes the states at times defined by the schedule. All other communication activities should be scheduled so that they do not conflict with the intersystem schedule.
[0135]
Referring to the data state 704 shown in FIG. 7, intersystem communication is initiated when a scheduled start event occurs or when the re-establishment procedure 708 is successful.
[0136]
The scheduled start event is usually the time point described by the pseudo-random scheduler, or may be another start time point previously negotiated between the electronic devices.
[0137]
The communication period is from the exchange of data between the electronic device pair to the end event. In data state 704, the master transmits the packet to the slave. If there is data such as an inquiry, a data packet is sent, otherwise a POLL packet is sent.
[0138]
A POLL packet is a packet composed of an access code and a packet header, like a NULL packet, and has a fixed length of 128 bits. The POLL packet is for managing the state of the communication link, like the NULL packet. However, unlike a NULL packet, a POLL packet always acknowledges the receipt of a POLL packet.
[0139]
The above data or POLL packet may be sent until an end event occurs. The slave may be in a standby state for a packet transmitted from the master. When a packet is received from the master, the slave sends a data packet to the master if a reply is possible, otherwise it sends a NULL packet to the master.
[0140]
A NULL packet is a packet composed of an access code and a packet header, and has no payload. The packet length is fixed at 128 bits. The NULL packet is for notifying the other party of the state of the communication link, such as reception confirmation (ARQN) and flow control (FLOW). Also, there is no need to send a packet response for confirmation that a NULL packet has been received.
[0141]
The electronic device detects a non-responsive state by monitoring communication activity. If there is no communication during each slot of the non-response type timeout period, the electronic device may end the communication.
[0142]
With respect to the master electronic device, the master electronic device may continuously transmit packets to the slave electronic device until the non-responsive timeout period expires. As for the slave electronic device, the slave electronic device may be in a continuous standby state in order to reliably receive packets from the master. If the slave does not receive any packets during the non-responsive timeout period, the slave may terminate the connection.
[0143]
The electronic device may terminate the active communication period at any time. In general, the electronic device terminates communication because it becomes necessary for the electronic device to execute another scheduled event. For example, the electronic device may need to respond to a starting time point for another link, or the electronic device needs to communicate with a slave, such as an in-system link. It may be the case.
[0144]
The forced termination may be signaled by an electronic device using various methods. Depending on the various types of electronic devices, systems, protocols, etc. being used, different techniques may be performed by the electronic device to signal a forced termination. In general, an electronic device may send a forced termination message to other electronic devices to convey a forced termination.
[0145]
It will be apparent to those skilled in the art many different ways in which the message is communicated. For example, in a Bluetooth system, the forced termination may be signaled by the electronic device by a FLOW bit in the packet header. Normally, the FLOW bit is set to enable (FLOW = 1) during data exchange. The electronic device may clear the FLOW bit (FLOW = 0) to force the end of the current communication period.
[0146]
The forced termination may be executed prior to the schedule negotiation process 706. If the forced termination is used, the use may indicate that the electronic device that initiated the new schedule is not available until a new negotiated time. The use may imply that the electronic device is not available on any re-establishable link.
[0147]
The schedule negotiation state 706 or process 706 described above may be used by an electronic device that has terminated active communication and knows that it will be busy in the near future.
[0148]
If forced termination is not used, its non-use may imply that the electronic device appears free to re-establish on the link to which the electronic device belongs. When both electronic devices do not have any data to exchange, a termination indicating that the data has been exhausted occurs. The termination occurs when both electronic devices empty their data queues.
[0149]
Similar to forced termination, terminations that indicate that the data has been exhausted in a variety of commonly used ways depending on each type of electronic device, system, protocol, etc. It may be signaled by an electronic device.
[0150]
In general, an electronic device may send an end message indicating that data has been exhausted to another electronic device to signal the end of data indicating that it has been used up.
[0151]
It will be apparent to those skilled in the art that an end message indicating that data has been exhausted may be communicated in a variety of different ways. For example, in a Bluetooth system, the end event may be signaled when the slave transmits a Null packet and when the master transmits a Poll or Null packet.
[0152]
The end slot is determined based on the last electronic device that sent the signal, ie, no data to send. When the master is the last to run out of data, a sequence (packet dispatch order) Poll-Null-Poll may be used with ACKN = 0. The last slot used is a Poll packet sent by the master.
[0153]
When the slave is the last to run out of data, a sequence (packet dispatch order) Null-Poll-Null may be used with ACKN = 0. In this case, the Null packet from the slave is the last used slot.
[0154]
If the schedule negotiation process 706 is completed during the current active communication period, an end of schedule may occur. While the part of the process is being processed, the start of a hold period (hold start time) is negotiated. During the communication period, the hold start time determines the last slave slot.
[0155]
As described above, schedule negotiation state 706 or process 706 is used to change the schedule. The electronic device may choose to change the schedule for many different reasons (eg, conflicting or avoiding each schedule).
[0156]
The electronic device changes its own schedule to avoid wasting processing power by notifying the other electronic device that the current schedule obligation cannot be met. A new schedule that is acceptable to both electronic devices is then negotiated.
[0157]
Schedule negotiation state 706 or process 706 may be used in each of several situations. The schedule negotiation state 706 may be used when there is a start time point event collision.
[0158]
In the above situation, the electronic device may have anticipated the next time point for the current active communication link, if the next time point collides with the time point for other intersystem links, If other links have higher priority, the schedule negotiation process 706 may be used to negotiate a new time point.
[0159]
Schedule negotiation state 706 may be used when there is a communication termination without an opportunity to re-establish communication. The above may occur in the following cases. The above case is when the communication period is about to be terminated by the local electronic device and the link has waiting traffic.
[0160]
The local electronic device may look ahead (previous) with its predicted availability. If the electronic device is expected to be busy, the electronic device may use the above procedure to indicate that it is not available by asserting a starting time point. The information is used by the fellow electronic device re-establishment process 708 in the selection of each communication link.
[0161]
Schedule negotiation state 706 may be used when other events occur. For example, if the communication processing capability of the electronic device is necessary for other purposes, the electronic device may make the communication processing capability available by obtaining an inactive period by negotiation in the inter-system schedule. Good. The above negotiation may be made in each intersystem link.
[0162]
Schedule negotiation state 706 or process 706 may be initiated by an electronic device attempting to change the current schedule. Different techniques may be used by the electronic device to initiate the schedule negotiation process. In general, the electronic device may send a schedule negotiation start message to other electronic devices to initiate the schedule negotiation process 706.
[0163]
It will be apparent to those skilled in the art how many different ways the message may be communicated. For example, in a Bluetooth system, the state may begin with the transmission of an LMP_hold_req message. The above message is for the hold start time to be set to correspond to the last slot of the communication period, as determined by the start time point for any other connection It is.
[0164]
The hold time parameter may be set to correspond to the next starting time point proposal for the current connection. The receiving electronic device compares the requested hold start time with the next time point event, and if the requested hold start time is shorter (next) than the next time point event, it determines the requested hold start time. Approve and schedule. Otherwise, the electronic device may request a new hold start time corresponding to the next scheduled event.
[0165]
In the design of this example, the electronic device of each example is configured to attempt to agree on the shorter of the two periods. The electronic device receiving the request can check the hold time parameter, and if it matches, accept the parameter, and if not, can suggest the next starting time point for the channel. If both parameters are acceptable, the electronic device may send LMP_Accepted. Otherwise, the electronic device may transmit LMP_hold_req as an alternative request.
[0166]
The receiving electronic device may perform a similar check and respond in a similar manner. After the negotiation is complete, the state may return to data state 704 and continue exchanging information until an end event occurs. The re-establishment state 708 attempts to establish communications opportunistically during periods of inactivity.
[0167]
In this embodiment, the aforementioned algorithm, when possible, first fairly allocates unused processing power among each electronic device and then optimistically communicates processing power where possible. Designed to distribute.
[0168]
The electronic device may enter the re-establishment state 708 when the current communication is terminated and there is data waiting on any of its intersystem communication links. The electronic device attempts to re-establish communication with another electronic device at a remote location that had a previously active connection with data waiting to be transmitted indicating that it may be available It may be like this.
[0169]
If the electronic device is a master, the above settings may include transmission of packets (POLL or data) until a response is received or another time point occurs. If the electronic device is a slave, the slave may be in a standby state until another time point occurs. When a response is received, the electronic device may transition to a data state.
[0170]
If an electronic device has signaled that it has finished its communication period and will soon be busy, the free electronic device will attempt to establish communication with another electronic device that will be available. It may be like this.
[0171]
Each electronic device may maintain an event queue 620 and status information 630 for each intersystem communication channel. The event queue 620 may consist of an ordered list of time points. Each time point may be generated from a pseudo-random sequence for any change or addition due to the connection, plus, or negotiation to which it corresponds.
[0172]
The electronic device may combine the lists to determine which connections are scheduled at any point in time. At least one of state information 630 and status information 632 may be maintained for each intersystem link. The information may be obtained from the end event and any storage in the data queue.
[0173]
Each electronic device may include link status information. The link status information may include information on waiting data 628 such as waiting / no waiting data. The information may indicate that there is some waiting transmission on the link.
[0174]
The above information is set when there is data waiting for transmission in the local queue, or when the previous communication period is ended together with the event waiting for data transmission.
[0175]
The electronic device may also include a remote processing capability indicator (not shown). The indicator may indicate whether the remote (remote) electronic device on the link is currently busy or free.
[0176]
This indicator may be set free if the previous communication period has been negotiated and has not been scheduled. The use of the schedule negotiation process implies that the remote electronic device is busy until a new time point due to negotiation. Link schedule information (not shown) may be stored in the electronic device. The link schedule information may include pseudo-random time points.
[0177]
Each of these time points may be automatically generated based on an algorithm that determines their location relative to the clock of the master electronics on the link. Moreover, these time points may prescribe | regulate the start of communication.
[0178]
Also, each scheduled time point may be stored. These time points may be generated through a negotiation process between two electronic devices connected by this link. These time points define the start of communication. The electronic device may store the end time point time.
[0179]
There are time points that define when communication should end. They are generated in the schedule negotiation process 706. Since each starting time point is typically generated pseudo-randomly, a collision of each time point may occur at each electronic device belonging to two or more intersystem links. The occurrence may be random at a rate depending on the density of each time point.
[0180]
In the embodiments described herein, the electronic device detects each time point that collides with each other and adjusts the schedule to reduce them. The electronic device may use schedule negotiation state 706 or process 706 to move or skip each time point that is colliding with each other when possible.
[0181]
When it is impossible to reschedule each starting time point that collides with each other, the electronic device communicates with the electronic device having the longest inactive period with respect to each other electronic device. Should be selected. This choice ensures a fair allocation of communication throughput and minimizes invalid periods.
[0182]
A pseudo-random generator may be used to generate each starting time point that creates a schedule. Each time point may be defined in relation to the clock of the master electronic device of the electronic device pair that forms the intersystem interconnection. In the design of this embodiment, both electronic devices can create their own schedules, both of which have clock knowledge (specifications) necessary to use the schedule.
[0183]
Given that each schedule can be unique (unique) and random with respect to other inter-system schedules, the unique (unique, unique) but shared part of each schedule above Information may be used as input to the generator.
[0184]
For example, if the electronic device is part of a Bluetooth network, this shared portion of information may be the master's electronic device address (BD_ADDR) and the slave's active member address (AM_ADDR) in Bluetooth.
[0185]
One characteristic of the generator is the density of each time point. The density defines the average between each time point. Other temporary relationships may also be imposed on the generating function to achieve specific operating characteristics.
[0186]
Each property associated with each of the three possible methods is described below. The following methods may be used, but each has its own unique system limitations and performance tradeoffs.
[0187]
It will be apparent to those skilled in the art that other methods may also be used based on the devices and software of this embodiment for effectively scheduling each communication period.
[0188]
FIG. 8A shows a preset synchronous method for generating each time point. As shown in the figure, in a preset synchronous time type method, each time point is first generated by applying to a period (A) with a fixed interval.
[0189]
The interval duration is set according to the density of each desired time point. One time point is arranged at a random position within the interval. The equation is described below describing how time points are generated using the above method.
[0190]
TP _N = A × N + Rand (0., A)
In the above equations, A defines the interval size and N indicates the interval number and time point index. The above function Rand () provides a random number from 0 to A. A unique random number is generated for each time point.
[0191]
This scheduled and synchronized method has the advantage that the length range of the communication period can be adjusted by the distribution of the time point arrangement.
[0192]
Different distributions of random numbers can be used to control the statistical characteristics of the length of the communication period. In general, a uniformly distributed random number is used.
[0193]
However, for example, a normal distribution of random numbers centered on A / 2 may be used to achieve a more narrowly distributed communication duration around the mean. This can reduce the variation in the length of the communication period, but increases the collision probability when compared with the uniform distribution.
[0194]
This method is suitable mainly for systems where the interval is linked between intersystem links. The above method has the advantage of being able to better control the tight distribution (ie easier to control) and the statistical distribution of the communication period duration for the maximum delay between each communication period.
[0195]
FIG. 8B shows a preset asynchronous method for generating each time point. As shown, in this generation method, each time point is determined by random number generation over an arbitrarily long period. The long period is usually several times longer than the density.
[0196]
Typically, the long period should be 10 to 100 times longer than the average period between each time point. Each time point is randomly generated in a state where there is a uniform distribution over the long period. Thereafter, the above time points are sorted in ascending order (from smallest to largest) by the scheduler.
[0197]
TP _{0., M} = Rand (0, A ^* N)
TP _{0., N} = Sort (TP _{0., M} )
In the above equation, TP _{0., N} Indicates an ordered list of each time point used by the scheduler.
[0198]
The function Rand () produces each time point that is uniformly distributed over a period defined by the density (A) and the number of each time point required (N). The total duration over which random numbers are produced uniformly is determined by the product of the required density (A) and the number of each time point (N).
[0199]
Preconfigured asynchronous methods have the advantage that no synchronization is required between the clocks of the different intersystem links.
[0200]
The first disadvantage of the above asynchronous method compared to the synchronous method is that the characteristics of the communication period are not coupled to each other, that is, they can be changed independently of each other. It is. The length of the communication period and the time between the communication periods are more likely to change.
[0201]
FIG. 8C shows a preset real-time method for generating each time point. In a real-time method, each time point is generated relative to the previous time point. The above method can also be used to pre-set a schedule, but is first appropriate when it is desirable to create a schedule in real time.
[0202]
In order to execute a real-time method, the electronic device may generate random numbers with a uniform distribution within a range of 0 to 2 times the density. The above random number is added to the previous start time point to determine the next start time point. This information is transferred to the other electronic device.
[0203]
This process is performed by one of the electronic devices of the electronic device pair, usually the master. This method is particularly suitable for the Hold mode of Bluetooth systems.
[0204]
The intersystem scheduler coexists pseudo-random scheduling (PRS) intersystem traffic and resource reservation channel (RRC) traffic.
[0205]
The example electronic device described herein is designed to allow the above coexistence while maintaining fair operating characteristics of the best effort channel (BEC) provided by the pseudo-random scheduler. Yes.
[0206]
Two mechanisms are defined on the BEC channel to manage the coexistence of each type of RRC channel, one mechanism is a traffic overlay method and the other mechanism is a dynamic rescheduling method.
[0207]
The above traffic overlay method is used when the active period of the resource reservation type traffic is relatively short compared to the average communication period of the PRS.
[0208]
If the active period is less than the non-responsive end event timeout threshold, the electronic device can provide the RRC channel without changing the intersystem schedule.
[0209]
In this case, the electronic device would simply carry RRC traffic instead of PRS traffic. After completion of the transmission, the channel will revert to PRS scheduled traffic. If the electronic device is nearing the end of the communication period, the electronic device will close communication early and then continue with RRC traffic.
[0210]
If the active period of the RRC traffic is long in proportion to the average length of the communication period, or the above active period is longer than the threshold of the non-responding end event of the PRS scheduled traffic A schedule change method is used.
[0211]
In this case, the PRS schedule is modified to form free time for this traffic. This occurs in the communication period before the period of RRC traffic. In order to provide data traffic within the system, the electronic device needs to ensure time available to engage with the traffic.
[0212]
This idle time corresponds to the idle state 702 of the intersystem state machine. The electronic device may choose to spend free time that naturally occurs with scheduled traffic between systems, or to change the inter-system schedule to make free time available.
[0213]
In the latter case, by re-negotiating the intersystem schedule, the electronic device can create idle time in the intersystem traffic. The process in the latter case is equivalent to the process used to manage resource-reserved channels. In general, it is desirable that the above process be performed periodically to meet the requirements for intra-system communication.
[0214]
The electronic device may also choose to handle intrasystem links as if it were an intersystem link. In this case, the PRS schedule for the intra-system link may be used with the same execution characteristics as the inter-system link. The method used may depend on the timing requirements of intra-system communication.
[0215]
FIG. 9 (a) and FIG. 9 (b) show the unique pseudo-random schedule created for each connection and the electronic device network configuration. As shown in FIG. 9 (a), the electronic device network includes three masters 902, 904, 906 and one slave 908.
[0216]
In the Bluetooth system, the configuration shown in FIG. 9A forms three piconets (one master for each piconet). Each timing chart showing each communication period in FIG. 9B shows several intervals (intervals). As shown, the density used allows an average of one communication period per interval. As described above, the communication period starts at the start time point and ends at the time point collision or end time point.
[0217]
FIGS. 10A and 10B show an example of an electronic device network configuration including four piconets. Similar to FIG. 9A, the electronic device network includes three masters 1002, 1004, 1006, one slave 1008, and one master / slave 1010.
[0218]
The timing chart of each communication period in FIG. 10B illustrates the minimum processing capability assigned to each connection. As described herein, dynamic allocation may be used to restore unused processing power.
[0219]
FIGS. 11 (a) and 11 (b) illustrate the correct allocation of unused processing power by the electronic device network.
[0220]
In this example, there is no traffic between electronic device A 1102 and electronic device D 1104. As a result, the original communication period between the electronic device A 1102 and the electronic device D 1104 is unused processing capability. Further, regarding the example of FIGS. 11A and 11B, it is assumed that complete processing capability is used between the electronic devices B1106 and D1104 and between the electronic devices C1108 and D1104.
[0221]
In fair allocation, the unused processing power between the pair of electronic device A 1102 and electronic device D 1104 is randomly determined depending on whether it is between each pair of electronic devices B 1106 and D 1104 or between each pair of electronic devices C 1108 and D 1104. used. In a Bluetooth system, such a condition would effectively make electronic device A 1102 appear to be absent from the scatternet.
[0222]
12 (a) and 12 (b) illustrate an opportunistic fair allocation of unused processing power by the electronic device network. In this example, there was no traffic between electronic device A 1202 and electronic device D 1204.
[0223]
As a result, the original communication period between each pair of electronic devices A 1202 and D 1204 is unused processing capability. 12A and 12B, the complete processing capability is between the electronic devices B1206 and D1204, and between the electronic devices C1208 and D1204, and the electronic devices E1210 and C1208. Assume that existed between.
[0224]
With fair allocation, an end event caused by an inactive electronic device causes the free electronic device to remain on the same channel and attempt to re-establish against the free electronic device.
[0225]
In opportunistic assignments, an end event caused by an active busy channel switches to an alternative channel to the channel, creating a free electronic device. Thus, opportunistic assignment allows a more parallel exchange of data.
[0226]
As shown in the timing chart of each communication period in FIG. 12 (b), unused processing power in each pair of electronic devices A1202 and D1204 is allocated fairly, and others are used to use the processing power. Are opportunistically assigned to channels. As described above, in the present invention, a pseudo-random dynamic scheduler for adjusting a schedule of a communication period between electronic devices is realized. The present invention also includes a computer-readable recording medium having program data including executable instructions for realizing the communication method of the communicable electronic device according to the present invention. As the form of the recording medium, a flexible disk-shaped recording medium (for example, floppy (registered trademark) disk), optical, magneto-optical, or disk-shaped recording medium using a dye (for example, CD-ROM, DVD), A magnetic tape, a magnetic stick, etc. are mentioned.
[0227]
The present invention may be embodied in other configurations and methods without departing from the spirit and essential characteristics thereof. The description of the present embodiment is for explaining the illustrated configuration, and should not be construed as limiting. Accordingly, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All modifications within the scope and meaning of each claim are to be included within the scope of the present invention.
[0228]
This application is based on a US patent application filed February 28, 2001 (Application No. 60 / 272,630) entitled “Effective Scheduling for Communication Between Systems” by Inventor: Daryl Haslani. And the contents of the above-mentioned US patent application are incorporated herein by reference.
[Brief description of the drawings]
1A is a block diagram of an embodiment of an electronic device pair, FIG. 1B is a timing chart of a communication period regarding the embodiment of the electronic device pair, and FIG. 1C is an implementation of the electronic device pair. It is a timing chart which shows a series of each communication period in an example.
2 (a) is a block diagram of two electronic device networks, and FIG. 2 (b) is a block diagram of two networks having intersystem communication links between slave electronic devices. c) is a block diagram of two networks with intersystem communication links between each master electronic device, and (d) has intersystem communication links between slave electronic devices and master electronic devices. It is a block diagram of each of two networks.
FIG. 3A is a block diagram illustrating an example of two electronic device pairs, and FIG. 3B is a timing chart illustrating a communication period in the example of two electronic device pairs.
FIG. 4 is a circuit diagram in a topology representation of an electronic device network.
FIG. 5 is a block diagram illustrating each configuration of hardware in an embodiment of an electronic device.
FIG. 6 is a block diagram illustrating each configuration of software in an embodiment of the electronic device.
FIG. 7 is a block diagram illustrating an embodiment of a state machine for an electronic device scheduler.
FIG. 8A is a timing chart showing a preset synchronous method for generating each time point, and FIG. 8B is a preset timing chart for generating each time point. 4C is a timing chart showing a preset real-time method for generating each time point.
FIG. 9A is a block diagram of an electronic device network including three master electronic devices, and FIG. 9B is a communication period timing chart for the embodiment of FIG.
FIG. 10A is a block diagram of an electronic device network including three master electronic devices, one slave electronic device, and one master / slave electronic device, and FIG. 10B is a block diagram of (a) above. It is a timing chart of the communication period for an Example.
FIG. 11A is a block diagram of an electronic device network including four electronic devices, and FIG. 11B is a timing chart of a communication period for the embodiment of FIG.
12A is a block diagram of an electronic device network including five electronic devices, and FIG. 12B is a timing chart of a communication period for the embodiment of FIG.
[Explanation of symbols]
502 processor
508 memory
606 Communication module
612 Pseudorandom scheduler
614 Dynamic Scheduler

Claims (57)

An electronic device that communicates with a first device network and communicates with a second device that is part of a second device network,
A processor;
A communication section in electronic communication with the processor to communicate with other devices, including a second device, and at least one device from the first device network;
A memory for electronically communicating with the processor for storing data;
A pseudo-random scheduler for providing each time point defining a schedule for the electronic device to communicate with the other device;
An event queue for storing the time points defining the schedule ;
Only contains a dynamic scheduler for changing the schedule,
The dynamic scheduler enters a schedule negotiation state when it detects each time point that collides with each other, a new time point is determined during the schedule negotiation state, and the new time point is used to A communicable electronic device adapted to change the schedule and reduce each of the time points that collide with each other .   2. The communicable electronic device according to claim 1, wherein the dynamic scheduler executes a fair allocation method that dynamically allocates communication processing capability.   The communicable electronic device of claim 2, wherein the fair allocation method includes extending a previous communication period.   The communicable electronic device of claim 2, wherein the fair allocation method includes reducing the number of each starting time point in the event queue.   5. The communicable electronic device according to claim 1, wherein the dynamic scheduler executes an opportunistic allocation method that dynamically allocates communication processing capability. 6.   6. The communicable electronic device of claim 5, wherein the opportunistic allocation method includes evaluating waiting traffic and device availability, and changing the schedule based on the evaluation. apparatus.   The communicable electronic device according to claim 1, wherein the pseudo random scheduler executes a preset synchronous method for generating each time point.   7. The communicable electronic device according to claim 1, wherein the pseudo random scheduler executes a preset asynchronous method for generating each time point.   7. The communicable electronic device according to claim 1, wherein the pseudo-random scheduler executes a preset real-time method for generating each time point.   10. The communicable electronic device according to claim 1, wherein the event queue includes a plurality of start time points, a plurality of channel identifiers, and a plurality of waiting data indicators. . In addition, it includes a state machine for scheduling and communication,
11. The communicable electronic device according to claim 1, wherein the state machine includes an idle state, a data state, a schedule negotiation state, and a re-establishment state.   12. The communicable electronic device according to claim 1, wherein the electronic device is configured to be a part of a piconet.   13. The pseudo-random scheduler as set forth in claim 1, wherein each pseudo-point scheduler provides a time point that defines a schedule for the electronic device communicating with a first piconet and a second piconet. An electronic device that can communicate.   14. The dynamic scheduler according to claim 1, wherein the dynamic scheduler enters a schedule negotiation state, determines a new time point, and changes the schedule using the new time point. An electronic device that can communicate.   15. The communicable electronic device according to claim 1, wherein the electronic device sends a forced termination message for terminating a communication period.   15. The communicable electronic device according to claim 1, wherein the electronic device transmits an end message indicating that data for ending a communication period has been used up.   15. The communicable electronic device according to claim 1, wherein the electronic device generates each end time point for scheduling the end of each communication period. 18. The communicable electronic device according to claim 1, wherein the electronic device executes a traffic overlay method for managing resource reservation type traffic. 18. The communicable electronic device according to claim 1, wherein the electronic device executes a dynamic schedule change method for managing resource reservation type traffic.   A computer-readable recording medium having program data including executable instructions for performing the method,
  The above method
  Transmitting output data from the first device to the first device network;
  Receiving input data from the first device network by the first device;
  Discovering a second device of the second device network;
  Providing pseudo-randomly each time point defining a schedule for the first device to communicate with the first device network and the second device;
  Storing the time points in the event queue;
  Dynamically changing the schedule to add additional communication processing power to at least one channel;
  Including entering a schedule negotiation state upon detecting each time point that collides with each other;
  A new time point is determined during the schedule negotiation state, and the new time point is A recording medium for a communication method of a communicable electronic device, wherein the schedule is changed using a system point and the time points that collide with each other are reduced.   The recording medium according to claim 20, wherein the step of dynamically changing executes a fair allocation method that dynamically allocates communication processing capability.   The recording medium of claim 21, wherein the fair allocation method includes extending a previous communication period.   The recording medium of claim 21, wherein the fair allocation method includes reducing the number of each starting time point in the event queue.   The recording medium according to claim 21, wherein the step of dynamically changing executes an opportunistic allocation method that dynamically allocates communication processing capability.   25. The recording medium of claim 24, wherein the opportunistic allocation method includes evaluating waiting traffic and device availability, and changing the schedule based on the evaluation.   26. The recording medium according to claim 20, wherein the step of providing time points in a pseudo-random manner executes a preset synchronous method for generating each time point. .   26. The recording medium according to claim 20, wherein the step of providing the time points in a pseudo-random manner executes a preset asynchronous method for generating each time point. .   The recording medium according to any one of claims 20 to 25, wherein the step of providing time points in a pseudo-random manner executes a preset real-time method for generating each time point.   29. The recording medium according to claim 20, wherein the event queue includes a plurality of start time points, a plurality of channel identifiers, and a plurality of waiting data indicators.   In addition, it includes a state machine for scheduling and communication,
  30. The recording medium according to claim 20, wherein the state machine includes an idle state, a data state, a schedule negotiation state, and a re-establishment state.   31. The recording medium according to claim 20, wherein the first device network is a piconet.   32. The recording medium according to claim 31, wherein the second device network is a piconet.   33. The recording medium according to claim 20, further comprising a step of entering a schedule negotiation state in which a new time point is determined and the schedule is changed using the new time point. .   The method includes sending a forced termination message to end a communication period. Item 34. The recording medium according to any one of Items 20 to 33.   34. The recording medium according to claim 20, wherein the method includes a step of sending an end message indicating that data for ending the communication period has been used up.   34. A recording medium according to any of claims 20 to 33, wherein the method includes the step of generating end time points for scheduling the end of each communication period.   37. A recording medium according to any one of claims 20 to 36, wherein the method includes the step of using a traffic overlay method for managing resource reservation type traffic.   37. A recording medium according to any of claims 20 to 36, wherein the method includes the step of using a dynamic schedule change method for managing resource reservation type traffic.   A method for scheduling each communication period between electronic devices pseudo-randomly and dynamically,
  The above method
  Transmitting output data from the first device to the first device network;
  Receiving input data from the first device network by the first device;
  Discovering a second device of the second device network;
  Providing pseudo-randomly each time point defining a schedule for the first device to communicate with the first device network and the second device;
  Storing the time points in the event queue;
  Dynamically changing the schedule to add additional communication processing power to at least one channel;
  Including entering a schedule negotiation state upon detecting each time point that collides with each other;
  A new time point is determined between the schedule negotiation states, the schedule is changed using the new time point, and the time points that collide with each other are reduced. Electronic device communication method.   40. The communication method according to claim 39, wherein the step of dynamically changing executes a fair allocation method that dynamically allocates communication processing capability.   41. The communication method of claim 40, wherein the fair allocation method includes extending a previous communication period.   41. The communication method of claim 40, wherein the fair allocation method includes reducing the number of each starting time point in the event queue.   41. The communication method according to claim 40, wherein the step of dynamically changing executes an opportunistic assignment method that dynamically assigns communication processing capability.   44. The communication method of claim 43, wherein the opportunistic assignment method includes evaluating waiting traffic and device availability, and changing the schedule based on the evaluation.   Providing pseudo-random time points above generates each time point 45. The communication method according to any one of claims 39 to 44, wherein a preset synchronous method for executing the method is executed.   45. The communication method according to claim 39, wherein the step of providing time points in a pseudo-random manner executes a preset asynchronous method for generating each time point. .   45. The communication method according to any one of claims 39 to 44, wherein the step of providing time points in a pseudo-random manner executes a preset real-time method for generating each time point.   48. The communication method according to claim 39, wherein the event queue includes a plurality of start time points, a plurality of channel identifiers, and a plurality of waiting data indicators.   In addition, it includes a state machine for scheduling and communication,
  49. A communication method according to any of claims 39 to 48, wherein the state machine includes an idle state, a data state, a schedule negotiation state, and a re-establishment state.   50. The communication method according to claim 39, wherein the first device network is a piconet.   The communication method according to claim 50, wherein the second device network is a piconet.   52. The communication method according to claim 39, further comprising a step of entering a schedule negotiation state in which a new time point is determined and the schedule is changed using the new time point. .   53. A communication method according to any of claims 39 to 52, wherein the method includes the step of sending a forced termination message to terminate the communication period.   53. A communication method according to any of claims 39 to 52, wherein the method includes a step of sending an end message indicating that data for ending the communication period has been used up.   53. A communication method according to any of claims 39 to 52, wherein the method includes the step of generating end time points for scheduling the end of each communication period.   56. A communication method according to any of claims 39 to 55, wherein the method includes the step of using a traffic overlay method for managing resource reservation type traffic.   56. A communication method according to any of claims 39 to 55, wherein the method includes the step of using a dynamic schedule change method for managing resource reservation type traffic.

Images