JP2003218881A - Electronic equipment capable of communication, its communication method and recording medium therefor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide electronic equipment capable of communication wherein processing ability of communication is distributed in an optimum manner and communication is enabled more smoothly, its communication method and recording medium for the communication method. <P>SOLUTION: A communication module 606 which performs electrical communication to a processor is installed in order to perform communication to other devices containing a second device and to at least one device from a first device network. A pseudo-random scheduler 612 for providing each time point which regulates schedule for the electronic equipment which performs communication to other devices is installed. A dynamic scheduler 614 for changing the schedule is installed. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

TECHNICAL FIELD The present invention relates generally to electronic devices, and more particularly to a system and method for coordinating schedules of communication periods between electronic devices and each executable instruction for executing the method. And a computer-readable recording medium having program data including the following.

Background computer and communication technologies continue to advance at a rapid pace. In fact, computers and communication technology are involved in many ways in human daily life. For example, many electronic devices used by consumers today incorporate a small computer within the electronic device.

These small computers can vary in size and degree of sophistication. These small computers can vary in degree of sophistication from microcontrollers to full-featured 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.

Computers typically include one or more processors. At least one processor is typically interconnected with different external inputs and outputs and serves to operate a particular computer or electronic device. For example, the thermostat's processor is connected to buttons to select temperature settings, to furnaces and air conditioners to change the temperature, and to sensors to display the temperature on the display by reading the temperature. Good.

Many appliances, electronic devices, etc., contain 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 nowadays have small computers, or processors, usually inside them. There is.

Computer software runs the processors of these computers and sends instructions to the processors to do certain tasks in order to perform certain tasks. For example, computer software running on a thermostat shuts down the air conditioner when a certain temperature is reached or turns on the heater when needed.

These types of small computers that are parts of devices, appliances, tools, etc. are often referred to as embedded systems. Usually "embedded system"
The term refers to computer hardware and software that is part of a larger system.

Embedded systems may not include typical input / output devices such as keyboards, mice, and / or monitors. At least one processor is typically provided at the heart of each embedded system.

With the increasing use of electronic devices and embedded systems, and the increasing demand for information exchange, more and more devices have detected surrounding devices and are now establishing electronic communication with these devices. You can do it.

Bluetooth (Bluetooth, registered trademark)
The specification defines one standard by which devices can communicate with each other through short wavelength radio signals. Many types of devices can benefit from being able to interface 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 shortwave radio system for connecting to other devices. May be.

By enabling this type of communication, bridges are provided to existing data networks to form a special grouping of small individuals of each device connected remotely from a fixed network infrastructure. In this way, the device network
As devices discover each other, they can form quickly.

However, when more devices attempt to communicate with each other, they cause a slowdown in communication, or otherwise hide the communication of one or more electronic devices altogether. This can cause inefficiencies. Thus, benefits can be gained if communication between each electronic device is augmented with additional systems and methods to provide a more effective communication technique.

SUMMARY OF THE INVENTION It is disclosed that an electronic device is adapted to communicate with a first device network and a second device that is part of a second device network.

The device is for electronic communication with the processor, each other device including the second device, and at least one device from the first device network. Communication module.

A memory may also be included for data storage in electronic communication with the processor.

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. Also, a dynamic scheduler may be included to change the schedule. Also,
The electronic device may include an event queue.

The above dynamic scheduler may be adapted to execute a fair allocation method, which dynamically allocates the communication processing power. The fair allocation method above may include the step of extending the previous communication period. The fair allocation method may also include reducing the number of each starting time point in the event queue.

An opportunistic allocation method may be implemented by the dynamic scheduler to dynamically allocate communication capacity. An opportunistic assignment method may include the steps of assessing waiting traffic and device availability, and altering the uptime schedule based on the assessment.

The pseudo-random scheduler uses a preset synchronous type (sync) to generate each time point.
hronized) method may be executed. In addition, the pseudo-random scheduler uses a preset asynchronous (as
ynchronized) method may be executed.

Real-time methods may also be used with a pseudo-random scheduler. The event queue may include a plurality of starting time points. Also, a plurality of channel identifiers may be stored in the event queue. Further, the event queue may include a plurality of respective indicators indicating that the data is waiting.

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 reestablishment state.

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 time points that define a schedule for electronic devices in communication with each piconet.

A method for pseudo-randomly and dynamically scheduling the communication period between the electronic devices 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.

The method also includes a pseudo-random, which defines a step of discovering a second electronic device of the second device network and a schedule for communicating with the first device network and the second device network. Providing each time point, storing each time point in an event queue, and dynamically rescheduling additional communication bandwidth to add additional communication processing power to at least one communication channel And the step of performing.

A computer readable medium for executing program data is also disclosed. The program data includes executable instructions for implementing 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.

The method also includes a pseudo-random, which defines a step of discovering a second electronic device of the second device network and a schedule for communicating with the first device network and the second device network. Providing each time point, storing each time point in an event queue, and dynamically rescheduling additional communication bandwidth to add additional communication processing power to at least one communication channel And the step of performing.

The present embodiments will become more fully apparent from the following description, which is understood in conjunction with the accompanying drawings and the appended claims.

It is understood that each of these drawings merely illustrates a typical embodiment and is not limiting on the scope of the invention. This example will be illustrated by further description and accompanying drawings.

DETAILED DESCRIPTION As shown in the drawings and generally described herein, each configuration of the present embodiment is readily understood and arranged in a variety of different configurations. It will be clear that it will be designed.

Accordingly, the following more detailed description of embodiments of the systems and methods of the present invention as represented in the drawings is merely an example of the present invention and is claimed in the following claims. As such, it is not intended to limit the scope of the invention.

FIG. 1A is a block diagram showing an electronic device pair 106 including two electronic devices (devices) 102 and 104. The electronic device pair 106 can initiate communication 108 with each other.

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, Examples include manufacturing equipment, industrial equipment, computer equipment, peripheral equipment, security systems, monitoring equipment, thermostats and the like.

FIG. 1B shows a timing chart of each communication period, including a schedule 110 for a communication period 112 between each electronic device 102, 104 of the electronic device pair 106.

Typically, the schedule 110 is created by any one of the electronic devices of the electronic device pair 106 wishing to communicate. The schedule 110 may be specific to the electronic device pair 106 or may be set for both electronic devices 102 and 104.

Schedule 11 as shown
0 may include each time point 114, 116 which is a signal indicating the start or end of communication between electronic device pair 106.

The time between the start time point 114 and the event end time point 116 is called the communication period 112. Start time point 114 is a typical method used to initiate communication between two electronic devices 102, 104. Both electronic devices 102, 10
4 is typically aware of the start time point 114 so that it can start communicating at the start time point 114.

In the embodiment shown in FIG. 1A, both electronic devices 102 and 104 can terminate communication. The electronic device can optionally end the communication period 112, but generally the communication period 112 is ended by clashing with time points from the schedule of another electronic device pair.

The communication period 112 is ended for each connection relationship.
It may be performed by exchanging signals between the electronic device pair 106. End time point 116
May be used to end communication period 112, but need not be. The end time point 116 is created by a schedule negotiation process performed between each electronic device in the pair.

Usually, the starting time point 114 is determined by a unique, random, preset pseudo-random schedule relative to the pseudo-random schedule for each other interconnected electronic device pair. .

The starting time point 114 is determined by the negotiation between each pair of electronic devices whose time points have been negotiated within the active range of the communication period as determined by the scheduled pseudo-random schedule. May be determined. The above negotiation process is performed between electronic device pairs and is used to create free time in a schedule for other purposes.

The electronic device pair 106 typically consists of one electronic device having the role of master and another electronic device having the role of slave for connection. The master electronic device is generally the one that initiates and controls the connection, while the slave electronic device responds to the commands of the master. The schedule typically uses the clock of the master electronic device as the time base. The slave electronic device may maintain synchronization with the clock. Another time base may be used if it is available for both electronic devices.

FIG. 1 (c) illustrates a series of communication periods 118 including a plurality of start time points 124, 126, 128, a plurality of end time points 130, 132, 134, and / or the end of each event. , 120, 12
6 is a timing chart showing No. 2.

In many situations, the electronic device pair 10
6 may continue to communicate with each other over a period of time.
These communications are in each of several communication periods 118, 120, 1 rather than one continuous communication period 112.
It may be performed at 22.

Although FIGS. 1 (a) -1 (c) show two electronic devices 102, 104 communicating with each other,
In a situation where there is mutual communication between two or more electronic devices, for example, as shown in FIG. 2A, two electronic device (device) networks 2
02, 204 may be present.

Electronic device A 206, electronic device B 208, electronic device C 210, and electronic device D 212 form a first electronic device network 202. Electronic device E
214, the electronic device F216, the electronic device G218, and the electronic device H220 are the second electronic device network 204.
Is formed.

FIG. 2A 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. Electronic device A 206 is used as a master, while electronic device B 208, electronic device C 210, and electronic device D 212 are used as slaves. The second electronic device network 204 also includes a master (electronic device E214) and three slaves (electronic device F216, electronic device G218, and electronic device H220).

As shown, the intra-system communication 222 includes a first electronic device network 202.
Between the respective electronic devices of the second electronic device network 20
It occurs between the respective electronic devices of No. 4.

One application for the embodiment of the present invention is
It may relate to the Bluetooth standard and the personal area networks associated with Bluetooth. The Bluetooth standards described in the Bluetooth system specifications are incorporated herein by reference.

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 on the internal system link. The present invention is
Particularly, it is preferable to apply the Piconet to a certain Bluetooth system which is an independent system. In the field of Bluetooth, each electronic device network 202,
Both 204 may be piconets.

When the connection between each piconet is formed,
The scheduler of the present invention is applicable to both new connections and, if a piconet master previously exists, to that piconet master within the previous piconet.

Of course, it will be apparent to those skilled in the art that the embodiments disclosed herein and the principles of the invention are not limited to personal area networks and / or Bluetooth networks.

The principles of the invention described herein are applicable to various communication systems of various types, including electronic devices and / or computers that communicate with each other.

In addition, the examples shown in FIGS. 2 (a) -2 (d) show three generally possible ways of connecting two networks 202,204. As described above, the electronic device A is not shown in FIGS.
The electronic device 206 and the electronic device E214 function as masters, while the other electronic devices function as slaves. Thus, a master / slave relationship exists between the master and slave of each electronic device network 202,204.

FIG. 2B shows an intersystem communication link 224 between electronic device D212 and electronic device F216. The scheduling devices and methods described herein can be used for intersystem communication link 224.

Also, as shown, the electronic device A20
6 and the electronic device D212, and the links between the electronic device E214 and the electronic device F216 may also be treated as the intersystem communication link 224.

Therefore, the original connection between the slave and its master is now treated as an intersystem link, since the slave electronics are not made available to the master at all times by the added link. May be.

Communication between the electronic device A206 and the electronic device D212 and between the electronic device E214 and the electronic device F216 is performed by each slave (the electronic device D212 and the electronic device F2).
It may be rescheduled because the processing power of 16) will now be shared by each of the two communications rather than just by one connection.

FIG. 2C shows two master electronic devices 20.
An intersystem communication link 224 between 6, 214 is shown. FIG. 2 (d) shows an intersystem communication link 224 between the master (electronic device A206) and the slave (electronic device F216).

When the embodiments of FIGS. 2A-2D are used and implemented in a Bluetooth environment, the two systems, each network 202, 204 and the intersystem communication link 224 are referred to as a scatternet. You may As mentioned above, the embodiments and principles of the present invention described herein are not limited to the Bluetooth environment but have wide application.

The present embodiments described herein provide a solution to the scheduling problem for each electronic device that needs to have any number of each connection relationship. Further, each of the embodiments described in the present specification enables any connection relationship (topology) of each electronic device to effectively communicate with each other when each connection relationship is treated as a system interconnection. ing.

FIG. 3A shows another two electronic devices A3.
04, consisting of electronic device B302 communicating with C306,
A system with a simple connection relationship (topology) is shown. The electronic device A 304 and the electronic device B 302 are the electronic device pair 308.
Are configured. Similarly, the electronic device B302 and the electronic device C306 form an electronic device pair 310.

Each pair of communicating electronic devices 308, 3
As shown in FIG. 3 (b), for 10 there is a schedule for communication indicating each starting time point. Each communication period 314, 316, 318 between electronic device B 302 and electronic device A 304 is initiated through each time point 320, 322, 324 of the beginning of communication A-B.

Starting time points 320, 322,
324 is a pair 3 corresponding to each electronic device 304, 302.
Each communication period 314, 316, 318 for 08 is started. Each communication period 326, 328, 330 between the electronic device B302 and the electronic device C306.
Are the time points 332, 33 of the start of communication B-C.
4, 336 respectively. Each of these starting time points 332, 334, 336 starts each communication period 326, 328, 330 for the BC pair 310 of each electronic device 302, 306.

As shown, each of the starting time points ends the event for the previous communication period. The end of the communication period is signaled to another electronic device when another starting time point occurs to collide with the currently active communication period. For example, start time point 3
20 initiates a communication period 314 between electronic device A 304 and electronic device B 302.

The communication period 314 continues until the start time point 332 occurs between the electronic device B 302 and the electronic device C 306 as a signal indicating the start of the communication period 326. FIG. 3 (b) shows typical operation for the embodiment shown in FIG. 3 (a).

FIG. 4 shows the connection relationship (topology) of the electronic device network. Communication link 402 exists between electronic device A 404 and electronic device B 406. Electronic devices X _{1 in} electronic communication with electronic device A 404
There is ~ _Xn . Similarly, there are a plurality of electronic devices Y ₁ to Y _m that communicate with electronically electronic device B 406.

The performance of the system according to the invention provides a fair distribution of processing power. It can be said that the above performance is easy to generalize when all links are fully utilized. The above relationships are given by the following equations for the generalized system shown in FIG.

The processing power available on links AB 402 is inversely proportional to the total number of other intersystem links in which both electronic device A 404 and electronic device B 406 are participating.

The following equation does not take into consideration the overhead (indirect cost) due to switching between connection relationships and the overhead due to transmission and reception of other signals required for system operation. The number of Cap _AB below indicates the relative throughput available for connection. It indicates the relative amount of time used for communication between electronic device pairs. The above relationship is applicable to systems in which the density of each time point is equal on each link between all systems and each link has a random distribution with respect to the others.

Cap _AB = 1 / (1 + n + m) FIG. 5 is a block diagram showing the configuration of major hardware generally used in the electronic / built-in electronic device 500. The electronic device 500 typically includes an input unit 504, and / or
Alternatively, it includes an output 506 and a processor 502 in electronic communication therewith.

The processor 502 is arranged to communicate with the processor 502 electronically, ie to input and / or output sections 504, 506 which are capable of input and / or output in the form of electrical signals. Is operably connected.

Embodiments of electronic device 500 may include input 504, output 506, and processor 502 in the same physical structure, and may be in separate housings or structures. May be included.

The electronic device 500 has a memory 508.
May be included. The memory 508 may be provided as a separate component from the processor 502, may be provided as an onboard memory, or may be provided as part of the processor 502. For example, microcontrollers often include some amount of onboard memory.

Further, the processor 502 processor 5
02 is provided to communicate electronically with 02. The communication unit 510 may be used for communication with other electronic devices. Therefore, the communication unit 5 of various electronic devices
The devices 10 may be designed to communicate with each other to send signals and messages between the electronic devices 500.

Further, the electronic device 500 may include a communication transmitting / receiving unit 512 which is another communication port. In addition, another component 5 that is another component.
14 may be included in the electronic device 500. Of course, it will be apparent to those skilled in the art that many different types of different electronic devices can be used with the embodiments described herein. Therefore, the block diagram of FIG. 5 is merely meant to show the typical components of the embedded electronic device 102, 500, and not to limit the scope of this embodiment.

FIG. 6 illustrates 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 the functionality needed to operate electronic device 600.

The input / output module 604 has an input unit 504.
May be used to receive data from and send data to the output 506. Depending on the type of electronic device 600, the particular functionality of input / output module 604 may vary.

The inter-electronic device communication module 606 may include functionality for handling incoming and outgoing messages. For example, a communication module 60 between electronic devices
6 may include instructions for sending and receiving each communication using the communication unit 510.

Communication module 606 between the electronic devices
Sends or transmits outgoing data 608 to the outside,
Also, the incoming data 610 to the inside may be received.

The electronic device 600 may generally include software for accomplishing each task of the communication, input / output of the electronic device 600, monitoring and control of the electronic device 600.

Communication module 606 between the electronic devices
May mean a routine or an instruction of a computer program that handles each communication via the communication unit 510 or the communication transmission / reception unit 512.

The input / output module 604 may mean a computer program routine or instruction for handling an input to the electronic device 600 and an output from the electronic device 600.

For example, when a button (not shown) is provided on the electronic device 600, the input / output module 604 is
It may include the code necessary to process input from the buttons (not shown).

The application 602 may function as a main program that controls the electronic device 600 and executes each task of the electronic device 600. For those skilled in the art,
It will be apparent that the software blocks described above are merely examples, and the configurations of the illustrated blocks are not necessarily essential for implementing the present embodiment.

As mentioned above, the embodiments described herein allow for many different types of electronic devices 102,
500 and 600 are available and can be used. Typically, these electronic devices are electronic devices 60.
The software needed to run 0 is already loaded.

The embodiments described herein are usable with each electronic device 102, 500, 600 having almost all electronic communication and some processing capabilities.

The electronic device may also include a pseudo-random scheduler 612 and a dynamic scheduler 614 that dynamically assigns. Both pseudo-random scheduler 612 and dynamic scheduler 614 are described below.

As will be described later, the dynamic scheduler 61
4 may include a fair allocation component 616 and an opportunistic allocation component 618. In addition, an event queue (event queue) 620
May be included. The event queue 620 includes one or more queue items 622. Each cue item 622 may correspond to a particular communication channel.

Each cue 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. May be included.

The above data that may be stored in the event queue 620 will be 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, It is provided.

A distributed algorithm is used to distribute the above processing power to each intersystem link where traffic is available. Unused processing power may be assigned first on a fair basis, and then processing power may be assigned opportunistically where communication is possible.

The above algorithm attempts to maximize utilization of communication throughput for each electronic device. The principle used to achieve fair allocation is to effectively remove the system interconnections from electronic devices when there is actually no traffic without interruption of the connection.

This is because the pseudo random scheduler 6
The inherent fairness of 12 results in reallocating unused processing power for each link that has traffic.

In the embodiments described herein, two mechanisms are used to achieve a fair re-allocation of unused processing power, one is a reduction in the starting timepoint and the other is It is an extension of the previous communication period.

In the start time point reduction method, the electronic device monitors traffic on its internal event queue 620 and on the link. If there is no traffic, then the set schedule is changed by removing each starting time point.

The above schedule is modified so that there is only the remaining portion from each original time point. For example, in one possible embodiment, each starting time point may be removed so that only every fourth of the original each time point is used.

The method described above effectively removes the connection to the electronic device at each time point with a short interval so that its processing power is used by each other intersystem link.

A negotiation process between electronic device pairs has been used to reschedule and eliminate each time point. The aforementioned method of extending the previous communication period means that the electronic device has completed the current communication period earlier than the other electronic device with which the electronic device was previously communicating (that is, before the time point of the next start). (Indicating that the termination has occurred), and re-establishing communication with the other electronic device with which the above communication was made.

In this way, the above method extends the previous communication period and effectively removes electronic devices for which the scheduled processing capacity has not been fully used.

In principle, opportunistic allocation attempts to maximize the number of parallel communication transfers. Additional processes are performed to achieve opportunistic quotas. In the above process, the electronic device 102 monitors the waiting traffic for each link,
It monitors how much electronic equipment is available to establish communications.

Equivalent information to the above monitor may have been obtained from signaling that occurred when the previous communication period was terminated for its respective intersystem link.

Electronic device 102 may then attempt to establish communication with another electronic device that has data waiting to be transferred and is available for communication. If two or more electronic devices meet the above criteria,
From each of these electronic devices, the electronic device that has recently communicated may be selected. These rules can improve the likelihood that both electronic devices will attempt to establish a connection with each other and can establish communication.

Some applications have very stringent communication requirements that may not be met by the pseudo random scheduler 612 between systems. These requirements are typically expressed in terms of fixed data bit rate and maximum latency. Moreover, the application generally negotiates the processing power required when establishing a channel for the service (processing benefit), and the service is provided only if sufficient processing power is available. Will be done.

In order to meet stricter requirements, resource reserved channels (resource reserved channels,
Methods supporting RRC) are provided. The resource-reserved channel type described above may be realized as a scheduled communication with a fixed period of time, an information period, and a duty cycle between each information period.

The traffic of the resource reservation type channel has a higher priority than the high level pseudo random scheduled (PRS) channel, and when a schedule collision occurs, the resource reservation type channel is generated. Traffic on these channels is replacing PRS traffic. PR above
The S schedule is modified to accept any RRC traffic.

In the design of the present 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 channels mentioned above, in many cases they will use the fixed throughput of the communication link.

Due to the above-mentioned periodic nature, the processing power taken from PRS traffic is randomly distributed among all links. As a result, inter-system traffic scheduled by the PRS method is reduced fairly by the RRC, but is fairly fairly allocated among the connections between the systems.

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 execute a scheduler and support other related functions.

The system description associated with the above state machine is
MAC / baseband components responsible for managing intersystem traffic for electronic device 102 may be applied.

Unless stated otherwise, the above information applies equally to both electronic devices of an electronic device pair.
The above protocol is mainly based on the master / slave access mechanism. The Bluetooth standard uses a master / slave relationship.

In order to illustrate and clearly explain the example of how the above state machine is used, the protocol above
It is written in master / slave and sometimes in Bluetooth terms.

Of course, to those skilled in the art, the principles and embodiments of the invention described herein may be applied to a wide variety of variations of electronic device 102 that are configured for electronic communication with other electronic devices. It will be obvious.

The idle state 702 described above is illustrated in FIG. In the idle state 702, there is no PRS intersystem traffic. The electronic device 102 is free to communicate with other electronic devices within its system or network.

The electronic device 102 may be designed to avoid communications that may extend the PRS scheduled intersystem communications period. Due to the Bluetooth system, the above avoidance can occur when long packets are received that extend past the scheduled time point.

The data state 704 described above is shown in FIG. In the data state 704, data is exchanged between the intersystem electronic devices. Communication continues until the end event occurs.

FIG. 7 shows the schedule negotiation state 70.
6 is shown. This state 706 is used to change the schedule. Either electronic device may initiate this process 706 or state 706. This state 70
6 is an effective substate of data state 704 because active communication periods are needed to support the exchange of messages needed for schedule negotiation.

The reestablished state 708 described above is also illustrated in FIG. The reestablishment state 708 executes a procedure for establishing communication during a period in which scheduled communication does not exist. This mechanism is used to distribute unused processing power to intersystem channels that have data available for exchange.

FIG. 7 shows each event that causes a transition from one state to another state and each event that keeps 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 event queue 620. The above event list has 62 scheduled time points.
4 and the channel identifiers 626 corresponding to them are composed of an ordered list.

The above scheduled event occurs when the current time matches the scheduled time. When the start time point occurs, electronic device 102 enters 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 is adapted to perform a kill process on the channel before entering the data state 704. .

There are many different types of end events that may occur. A forced termination occurs when there is data waiting for data exchange, but one of each electronic device wants to end the current communication period. The electronic device may perform the above termination due to another scheduled intersystem communication (or interpiconet communication in a Bluetooth network) or for other reasons.

The electronic device ends the communication period by asserting (asserting) the display (instruction) of this event in the message to the other electronic device. Another type of end event is a scheduled end. When the schedule negotiation process 706 or state 706 completes successfully, the end time point is agreed for the current communication period. The scheduled end event occurs when this time point occurs.

An event that indicates that the data has been exhausted is another type of end event. When all available data was transferred by both electronic devices,
The above events occur. The occurrence of this event is signaled to the other electronic device by a message indicating the event.

The master electronic device signals to the other electronic device that it has no data to send by communicating it a Poll packet. The slave indicates by sending a Null packet that it has no data to send. Therefore, when both electronic devices indicate they have no data to transfer,
An end event occurs indicating that the data has been exhausted.

Another type of end event is a non-responsive end event. A non-responsive end event is meant to occur when a communication is scheduled but does not happen. The electronic device may wait for communication for a period of time. If no data is received,
The communication period may be terminated.

If the electronic device is a master, a non-responsive end event will occur when it does not receive a response to any packet sent to the slave electronic device. If the electronic device is a slave, a non-responsive end event will occur when it does not receive any packets from the master.

When this embodiment is used in a Bluetooth network, the above non-responsive end event may occur when there is a scatternet scheduling violation.

[0126] When the electronic device has a high priority activity and cannot meet the schedule agreed upon by the electronic device,
The non-responsive end event can be triggered. Generally, the non-responsive end event is an indefinite time.
It can occur for a process that has (eg, a page response or an inquiry response).

Each of the other types of events is also shown in FIG. 7, further illustrating other events that can cause a change in state. The 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.

Data waiting event or status (stat
us) is an indicator of the composite status in all intersystem links, as recognized by electronic devices. The indicator may be true if any of the links are in the state where there is data to be transferred. The above conditions are well known due to the way the communication period is terminated.

The indicator may be false for links in which an event occurs indicating that the data has been exhausted. For links with forced termination or non-responsive termination, the above indicator is true.

Also, the no data wait event or state is a composite state indicator of all each intersystem link, as recognized by the electronic device. This indicator indicates that each intersystem link involving the electronic device has no data waiting.

The event of reestablishment of communication described above is shown in FIG. The above communication re-establishment event occurs when the POLL response procedure has been completed and the communication channel has been established.

Failure to reestablish the event indicates that the electronic device was unable to establish communication during the reestablishment process 708. As previously mentioned, the idle state 702 is entered whenever there is no active PRS intersystem communication. Idle state 70
The time spent for 2 depends on the traffic load between systems,
Depends on all scheduled changes between piconets (and more generally between systems) that are set pseudo-randomly.

The electronic device may modify the intersystem schedule so that it is free to set the time for the idle state 702 if needed for intrasystem links or other activities. The idle state 702 may imply that the electronic device may not be involved in PRS intersystem traffic, but the electronic device may be active in other intra-system communication activities. .

While the electronic device is in the idle state 702,
The electronic device typically monitors an intersystem schedule and changes states at times defined by the schedule. All other communication activities should be scheduled so that they do not conflict with the intersystem schedule.

Referring to data state 704, shown in FIG. 7, when a scheduled start event occurs or when the reestablishment procedure 708 is successful.
Intersystem communication is started.

The scheduled start event is
It may typically be the time point described by the pseudo-random scheduler, or another start time point previously negotiated between the electronic devices.

The communication period is from the exchange of data between the electronic device pair to the end event. In data state 704, the master passes the packet to the slave.
If there is data such as an inquiry, a data packet is sent, otherwise a POLL packet is sent.

The POLL packet, like the NULL packet,
A packet composed of an access code and a packet header, which has a fixed length of 128 bits. POLL
The packet, like the NULL packet, is for managing the state of the communication link. However, unlike the NULL packet, the POLL packet always makes an acknowledgment response to the receipt of the POLL packet.

The transmission of the above data or the packet of POLL may be performed until the end event occurs. The slave may be in a standby state for the transmitted packet of the master. If a packet is received from the master, the slave passes the data packet to the master if it can reply, otherwise sends a NULL packet to the master.

A NULL packet is a packet composed of an access code and a packet header and has no payload. The packet length is fixed and is 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, it is not necessary to send a packet as a response to confirm that a NULL packet has been received.

The electronic device detects a non-responsive condition by monitoring communication activity. If there is no communication during each slot of the non-responsive timeout period, the electronic device may terminate the communication.

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. With respect to slave electronic devices, the slave electronic devices may be in a continuous standby state to ensure receipt of packets from the master. If the slave does not receive any packets during the unresponsive timeout period, the slave may terminate the connection.

The electronic device may end the active communication period at any time. Generally, the electronic device terminates communication because the electronic device needed to perform another scheduled event. For example, it may be the case that the electronic device needs to respond to the starting time point for another link, or the electronic device needs to communicate with a slave, such as in an in-system link. In some cases.

Force termination may be signaled by an electronic device using various methods. Depending on the different types of electronic devices, systems, protocols, etc. used, different techniques may be performed by the electronic device to signal the termination. Generally, the electronic device may send a forced termination message to other electronic devices to convey the forced termination.

Many different ways of communicating the above messages will be apparent to those skilled in the art. For example, in Bluetooth systems, termination may be signaled by the electronic device by the FLOW bit in the packet header. Normally, the above FLOW bit is set to enable (FLOW = 1) during the exchange of data. The electronic device is
The FLOW bit may be cleared (FLOW = 0) to force the end of the current communication period.

Forced termination may also be performed prior to schedule negotiation process 706. If the kill is used, the use may indicate that the electronic device that initiated the new schedule is unavailable until the new negotiated time. The use may imply that the electronic device is unavailable at any re-establishable link.

The schedule negotiation state 706 or process 706 described above may be used by an electronic device that has finished active communication and knows that it will be busy in the near future.

When forced termination is not used, its non-use may imply that the electronic device appears to be free to re-establish on the link to which it belongs. When both electronic devices do not have any data to exchange, termination occurs indicating that the data has been exhausted. The above termination occurs when both electronic devices empty their data queues.

As with forced termination, it is possible that data may have been exhausted by various commonly used methods, depending on each type of electronic device, system, protocol, etc. The indicated end may be signaled by the electronic device.

In general, the electronic device may send another electronic device an end message indicating that the data has been used up to convey an end indicating that the data has been used up.

It will be apparent to those skilled in the art that the termination message indicating that the 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 sends a Null packet and when the master sends a Poll or Null packet.

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 Poll-Null-Poll may be used with ACKN = 0. The last slot used is the Poll packet sent by the master.

When the slave is the last to run out of data, the sequence Null-Poll-Null may be used with ACKN = 0. In this case, the Null packet from the slave is the last used slot.

Schedule termination may occur if the schedule negotiation process 706 is completed during the current active communication period. While the part of the above process is being processed, the start of the hold period (hold start time, hold instant) is negotiated. During the communication period, the hold start time determines the last slave slot.

As described above, the schedule negotiation state 7
06 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).

The electronic device modifies its own schedule to avoid wasting processing power by notifying the other electronic device that it cannot meet the obligations of the current schedule. Then, a new schedule acceptable for both electronic devices is negotiated by the doctor.

The 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 conflict of initiating time point events.

In the above situation, the electronic device may anticipate the next time point for the current active communication link, if the next time point collides with time points for other intersystem links. However, the schedule negotiation process 706 may be used to negotiate a new time point if the other links mentioned above have a higher priority.

Schedule negotiation state 706 may be used when there is an end of communication without the opportunity to reestablish 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 traffic waiting.

The local electronic device may look ahead in its predicted availability. If the electronic device is expected to be busy, the electronic device may use the procedure to indicate that it is unavailable by asserting a starting time point. The above information is used by the associate electronic device re-establishment process 708 in selecting each communication link.

Schedule negotiation state 706 may be used when other events occur. For example, if the communication power of the electronic device is needed for other purposes, the electronic device may enable the communication power by negotiating an inactive period within the intersystem schedule. Good. The above negotiations may be made at each of the intersystem links.

Schedule negotiation state 706 or process 706 may be initiated by an electronic device attempting to change the current schedule. Different techniques have been used to initiate the schedule negotiation process.
It may be used by electronic devices. In general, the electronic device may send a schedule negotiation start message to another electronic device to initiate the schedule negotiation process 706.

It will be apparent to those skilled in the art about the many different ways in which the above messages may be communicated. For example, in a Bluetooth system,
It may start with the delivery of the 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. Is.

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 than (or ahead of) the next time point event, the requested hold start time. It may be approved and scheduled. Otherwise, the electronic device may request a new hold start time corresponding to the next scheduled event.

In the design of this example, the electronic device of each example is configured to attempt to agree on the shorter of the two time periods. The electronic device receiving the request can check the hold time parameter and, if that time is met, accept this parameter and, if not, suggest a next starting time point for the channel. If both parameters are acceptable, the electronic device may send LMP_Accepted. Otherwise, the electronic device may use LMP_ho as an alternative request.
ld_req may be transmitted.

The receiving electronic device may perform similar checks and respond similarly. After the negotiation is complete, the state may return to the data state 704 to continue exchanging information until an end event occurs. Reestablished state 708
Attempts to establish communication opportunistically during periods of inactivity.

In this embodiment, the algorithm described above, when possible, first fairly distributes the unused processing power among the electronic devices and then the communication processing power where possible. Designed for opportunistic distribution.

The electronic device has completed the current communication, and
The reestablished state 708 may be entered when there is pending data on any of the intersystem communication links.
The electronic device attempts to re-establish communication with another electronic device at a remote location that has made a previously active connection with data awaiting transmission indicating that it may be available. It may be like this.

If the electronic device is a master, the settings may include the 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 the data state.

If the electronic device has ended the communication period and is signaling an immediate busy, the free electronic device establishes communication with another electronic device that will be available. You may try to try.

Each electronic device has an event queue 620 and status information 63 for its intersystem communication channel.
You may maintain 0. 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 changes or additions by the connection, plus, or negotiation to which it corresponds.

The electronic device may combine the lists to determine which connections are scheduled at any point in time. State information 630 and status information 632 for each inter-system link
At least one of the above may be maintained. The information may be available from the end event and any storage in the data queue.

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 are some pending transmissions on the link.

The above information is set when there is data waiting to be transmitted in the local queue, or when the previous communication period has ended together with the event waiting for data transmission.

The electronic device may also include a remote throughput indicator (not shown). The indicator may indicate whether the remote (remote) electronic device on the link is currently busy or free.

This indicator may be set to Free if the previous communication period has not been ended with the scheduled event negotiated. 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.

Each of these time points may be automatically generated based on an algorithm that determines their position relative to the clock of the master electronic device on the link. Also, these time points may define the start of communication.

Also, each scheduled time point may be stored. These time points are
It 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 also store the end time point time.

There are time points that define when communication should end. They are created in the schedule negotiation process 706. Since each starting time point is typically generated pseudo-randomly, collisions of each time point may occur at each electronic device belonging to two or more inter-system links. The occurrences may be random at a rate that depends on the density of each time point.

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 the schedule negotiation state 706 or process 706 when possible to move or skip each time point that is colliding with each other.

When it is not possible to reschedule the starting time points that collide with each other, the electronic device has the longest inactive period with respect to each of the other electronic devices. Should choose to communicate with. This choice guarantees a fair allocation of communication throughput and minimizes periods of inactivity.

A pseudo-random generator may be used to generate each time point of initiation, creating a schedule. Each time point may be defined in relation to the master electronic device clock of the electronic device pair forming the system interconnection. In the design of this embodiment, both electronic devices can create a schedule independently of each other, and both have the knowledge (specification) of the clock necessary to use the schedule.

If each schedule is given so as to be unique (random) and random with respect to other intersystem schedules, it is unique (unique, unique) with respect to each of the above schedules, but shared. The portion of the information may be used as an input to the generator.

For example, if the electronic device is part of a Bluetooth network, this shared portion of the information may be due to the master electronic device address (BD_A
DDR), and active member address of the slave
It may be (AM_ADDR).

One characteristic of the generator is the density of each time point. The density defines the average between each time point. Also, other temporal relationships may be imposed on the generating function to achieve particular operating characteristics.

Each property associated with each of the three possible methods is described below. Each of the following methods may be used, but each has its own unique system limits and performance tradeoffs.

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 to effectively schedule each communication period.

FIG. 8A shows a preset synchronous method for generating each time point. As shown in the figure, in the preset synchronous time type method, each time point is first generated by applying it to the period (A) in which the interval is fixed.

The interval duration is set corresponding to the desired density of each time point. One time point is placed at a random position within the above interval. The equations that describe how time points are generated using the above method are shown below.

TP _N = A × N + Rand (0., A) In the above equation, A defines the interval size, and N indicates the interval number and time point index. The function Rand () above provides a random number from 0 to A. A unique random number is generated for each time point.

This scheduled and synchronized method has the advantage that the range of communication period lengths can be adjusted by the distribution of the distribution of time points.

Different distributions of random numbers can be used to control the statistical characteristics of communication period length. Generally, uniformly distributed random numbers are used.

However, for example, a normal distribution of random numbers centered on A / 2 may be used to achieve a narrower distributed communication period 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.

This method is primarily suitable for systems where the interval works between intersystem links. The method has the advantages of tighter coupling (i.e. easier control) and better control of the statistical distribution of communication durations for the maximum delay between each communication duration.

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 above-mentioned long period is usually several times longer than the above-mentioned density.

Generally, the above long period should be 10 to 100 times longer than the average period between each time point. Each time point is randomly generated with a uniform distribution in the above long period. Thereafter, the above time points are sorted by the scheduler in ascending order (smallest to largest).

TP _{0., M} = Rand (0., A ^* N) TP _{0., N} = Sort (TP _{0., M} ) In the above equation, TP _{0., N} is used by the scheduler. Shows an ordered list of each time point.

The above function Rand () produces each time point uniformly distributed during the period defined by the density (A) and the number of each time point (N) required. The total duration for which the random numbers are produced uniformly is determined by the product of the required density (A) and the number of each time point (N).

The preset asynchronous method has the advantage that no synchronization is required between the clocks of different intersystem links.

The first disadvantage of the asynchronous method compared with the synchronous method is that the characteristics of the communication periods are not coupled to each other, that is, they change independently of each other. It is possible.
The length of the above communication period and the time between each communication period are more variable.

FIG. 8C shows a preset real-time method for generating each time point. In the real-time method, each time point is generated in relation to the previous time point. The above method can also be used to preset the schedule, but is first appropriate when it is desired to create the schedule in real time.

To execute the method in real time, the electronic device may generate random numbers with a uniform distribution within the range of 0 to 2 times the density. The random number above is added to the previous start time point to determine the next start time point. This information is transferred to the other electronic device.

This process is performed by one of the electronic devices in the electronic device pair, typically the master. This method is particularly suitable for Hold mode in Bluetooth systems.

The intersystem scheduler described above causes pseudo-random scheduling (PRS) intersystem traffic and resource reservation channel (RRC) traffic to coexist.

The electronic devices of the embodiments described herein allow the above coexistence while maintaining fair operating characteristics of the Best Effort Channel (BEC) provided by the pseudo-random scheduler. It has become.

Two respective mechanisms are defined to manage the coexistence of each type of RRC channel on the BEC channel, one mechanism is a traffic overlay method and the other mechanism is a dynamic rescheduling method. .

The above traffic overlay method is used when the active period of the resource secured traffic is relatively short compared to the average communication period of the PRS.

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 inter-system schedule.

In this case, the electronic device would simply carry the RRC traffic in place of the PRS traffic. After the above transmission is completed, the channel is PRS
Will return to the scheduled traffic. If the electronic device is nearing the end of the communication period, the electronic device will end communication early and then continue with RRC traffic.

[0210] The active period of the RRC traffic is longer in proportion to the average communication period length, or the active period is more than the threshold of the non-responsive end event of the PRS scheduled traffic. If long, the reschedule method is used.

In this case, the PRS schedule is modified to form free time for this traffic. This happens in the communication period before the period of RRC traffic. In order to provide data traffic within the system, electronic devices need to have available time available to engage with the traffic.

This free time corresponds to the idle state 702 of the intersystem state machine. The electronic device may choose to spend the free time that naturally occurs with scheduled traffic between the systems, or change the inter-system schedule to make the free time available.

In the latter case, by renegotiating the intersystem schedule, the electronic device can create free time in the intersystem traffic. The process in the latter case is equivalent to the process used to manage resource-reserved channels. Normal,
The above process is preferably performed periodically to meet the requirements for intra-system communication.

The electronic device may also choose to treat the intrasystem link as if it were an intersystem link. In this case, the PRS schedule for the intrasystem link may be used with the same performance characteristics as the intersystem link. The method used may depend on the timing requirements of intra-system communication.

9 (a) and 9 (b) show a unique pseudo-random schedule created for each connection,
2 shows an electronic device network configuration. As shown in FIG. 9A, the electronic device network includes three masters 90.
2, 904, 906 and one slave 908.

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 some intervals (intervals). As shown, the density used allows on average 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 the end time point.

10 (a) and 10 (b) show examples of electronic device network configurations including four piconets. Figure 9
Similar to (a), the electronic device network includes three masters 1002, 1004, 1006, one slave 1008, and one master / slave 1010.

The timing chart of each communication period of FIG. 10B illustrates the minimum processing capacity assigned to each connection. Dynamic allocation, as described herein, may be used to reclaim unused processing power.

11 (a) and 11 (b) illustrate the correct allocation of unused processing power by the electronic device network.

In this example, no traffic exists between electronic device A 1102 and electronic device D 1104. As a result, electronic device A 1102 and electronic device D 1
The original communication period with 104 is unused processing power. In addition, regarding the example of FIG. 11A and FIG.
Between D1104 and each electronic device C1108, D1104
Suppose it was used between.

With fair allocation, electronic device A 1102
And the unused throughput between the pair of electronic device D1104 and
It is randomly used by either the pair of electronic devices B1106 and D1104 or between the pair of electronic devices C1108 and D1104. In a Bluetooth system, such a condition would effectively cause electronic device A 1102 to appear as if it were absent from the scatternet.

12 (a) and 12 (b) illustrate the opportunistic and fair allocation of unused processing power by the electronic device network. In this example, the electronic device A12
There was no traffic between 02 and electronic device D1204.

As a result, each of the electronic devices A1202 and D12
The original communication period between the pair of 04 has unused processing capability. In addition, regarding the example of FIG. 12A and FIG.
Between D1204, each electronic device C1208, D1204
Between the electronic devices E1210 and C1208.

In fair allocation, a termination event triggered by an inactive electronic device causes the free electronic device to remain on the same channel and attempt to re-establish it.

In an opportunistic assignment, an end event triggered by an active busy channel will switch to an alternate channel to that channel to create a free electronic device. Thus, opportunistic allocation allows for more parallel exchange of data.

As shown in the timing chart of each communication period of FIG. 12B, each electronic device A 1202,
Unused processing power in the D1204 pair is fairly allocated and opportunistically allocated to other channels to use the processing power. As described above, in the present invention, a pseudo-random dynamic scheduler for adjusting the schedule of the communication period between the electronic devices is realized. The present invention also includes a computer-readable recording medium having program data including executable instructions for implementing the communication method of a communicable electronic device according to the present invention. Examples of the form of the recording medium include a flexible disc-shaped recording medium (for example, a floppy (registered trademark) disc), a disc-shaped recording medium using optical, magneto-optical, or dye (for example, CD-ROM, DVD), Examples include magnetic tapes and magnetic sticks.

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. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All modifications within the scope and meaning corresponding to each claim should be included in the scope of the present invention.

The present application is made by the inventor: "Effective scheduling for communication between systems" by Darryl Haslany
No. 60 / 272,630 filed February 28, 2001, the content of which is hereby incorporated by reference. is there.

[Brief description of drawings]

1A is a block diagram of an embodiment of an electronic device pair, FIG. 1B is a timing chart of communication periods for an embodiment of an 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.

FIG. 2 (a) is a block diagram of each of the two electronic device networks, and FIG. 2 (b) is a block diagram of each of the two networks with intersystem communication links between each slave electronic device; c) is a block diagram of each of the two networks having intersystem communication links between each master electronic device, and (d) has an intersystem communication link between a slave electronic device and a master electronic device. Two
FIG. 3 is a block diagram of each network.

FIG. 3A is a block diagram showing an embodiment of two electronic device pairs, and FIG. 3B is a timing chart showing a communication period in the embodiment of two electronic device pairs.

FIG. 4 is a circuit diagram in a topological representation of an electronic device network.

FIG. 5 is a block diagram showing each component of hardware in the embodiment of the electronic device.

FIG. 6 is a block diagram showing each component of software in the embodiment of the electronic device.

FIG. 7 is a block diagram illustrating an embodiment of a state machine for an electronic device scheduler.

FIG. 8 (a) is a timing chart showing a preset synchronous method for generating each time point, and FIG. 8 (b) is a timing chart for generating each time point. 2C is a timing chart showing an asynchronous method, and FIG. 6C is a timing chart showing a preset real-time method for generating each time point.

9 (a) is a block diagram of an electronic device network including each of the three master electronic devices, and FIG. 9 (b) is a timing chart of communication periods for the embodiment of (a) above.

FIG. 10 (a) is a block diagram of an electronic device network including three master electronic devices, one slave electronic device, and one master / slave electronic device,
(B) is a timing chart of the communication period for the embodiment of (a).

FIG. 11 (a) is a block diagram of an electronic device network including four electronic devices, and FIG. 11 (b) is a timing chart of a communication period for the embodiment of (a) above.

FIG. 12 (a) is a block diagram of an electronic device network including five electronic devices, and FIG. 12 (b) is a timing chart of a communication period for the embodiment of (a) above.

[Explanation of symbols]

502 processor 508 memory 606 Communication module 612 Pseudo Random Scheduler 614 Dynamic scheduler

Claims (60)

[Claims] 1. An electronic device in communication with a first device network and a second device that is part of a second device network, comprising: a processor; and other devices including a second device, and A communication unit in electronic communication with the processor for communicating with at least one device from the first device network; a memory in electronic communication with the processor for storing data; and the other device. A communicable electronic device including a pseudo-random scheduler for providing time points defining a schedule for the electronic device to communicate with, a dynamic scheduler for changing the schedule, and an event queue. 2. The communicable electronic device according to claim 1, wherein the dynamic scheduler executes a fair allocation method for dynamically allocating communication processing power. 3. The communicable electronic device of claim 2, wherein the fair allocation method includes the step of extending a previous communication period. 4. The communicable electronic device of claim 2, wherein the fair allocation method comprises 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 for dynamically allocating communication processing power. apparatus. 6. The opportunistic allocation method of claim 5 including the steps of evaluating waiting traffic and device availability, and modifying the schedule based on the evaluation. , An electronic device capable of communication. 7. The communication according to claim 1, wherein the pseudo random scheduler executes a preset synchronous method for generating each time point. Electronic device. 8. The communicable type according to claim 1, wherein the pseudo-random scheduler executes a preset asynchronous method for generating each time point. Electronic device. 9. The communicable electronic device according to claim 1, wherein the pseudo-random scheduler executes a preset real-time method for generating each time point. apparatus. 10. The event queue according to claim 1, wherein each of the event queues includes each of a plurality of start time points, a plurality of channel identifiers, and a plurality of waiting data indicators. An electronic device that can communicate. 11. A state machine for scheduling and communication, further comprising: an idle state, a data state, a schedule negotiation state, and a reestablishment state. An electronic device capable of communicating as described in. 12. The communicable electronic device according to claim 1, wherein the electronic device is configured to be a part of a piconet. 13. A pseudo-random scheduler as claimed in any one of claims 1 to 12, wherein the pseudo-random scheduler provides time points defining a schedule for the electronic device to communicate with a first piconet and a second piconet. An electronic device capable of communicating as described in. 14. The dynamic scheduler is adapted to enter a schedule negotiation state, determine a new time point, and change the schedule using the new time point. An electronic device capable of communication according to any one of 1. 15. The dynamic scheduler enters a schedule negotiation state when detecting time points that collide with each other, a new time point is determined during the schedule negotiation state, and the new time is set. 14. The communicable electronic device according to any one of claims 1 to 13, wherein the schedule is changed by using points to reduce the time points that collide with each other. 16. The communicable electronic device according to claim 1, wherein the electronic device is adapted to send a forced termination message for terminating a communication period. 17. The communicable device according to claim 1, wherein the electronic device is adapted to send an end message indicating that the data for ending the communication period has been used up. Electronic device. 18. The communicable electronic device according to claim 1, wherein the electronic device is adapted to generate end time points for scheduling the end of each communication period. apparatus. 19. The communicable electronic device according to claim 1, wherein the electronic device is adapted to execute a traffic overlay method for managing resource-secured traffic. 20. The communicable electronic device according to claim 1, wherein the electronic device is adapted to execute a dynamic rescheduling method for managing resource-secured traffic. apparatus. 21. A computer-readable recording medium having program data including each executable instruction for performing the method, the method comprising: outputting output data from a first device to a first device network. Transmitting, receiving input data from the first device network by the first device, discovering a second device of the second device network, the first device network and the second device Pseudo-randomly providing each time point defining a schedule for the first device to communicate with, storing each time point in an event queue, and for at least one channel, Add additional communication processing power A recording medium for a communication method of a communicable electronic device, which comprises dynamically changing the schedule for the purpose of 22. The recording medium according to claim 21, wherein the step of dynamically changing executes a fair allocation method for dynamically allocating communication processing power. 23. The recording medium of claim 22, wherein the fair allocation method includes the step of extending a previous communication period. 24. The recording medium of claim 22, wherein the fair allocation method includes reducing the number of starting time points in the event queue. 25. The recording medium according to claim 22, wherein said dynamically changing step executes an opportunistic allocation method for dynamically allocating communication processing power. 26. The opportunistic assignment method above is
26. The recording medium according to claim 25, comprising: evaluating waiting traffic and device availability; and modifying the schedule based on the evaluation. 27. The method of providing pseudo-random time points as described above, wherein a preset synchronous method for generating each time point is executed. The recording medium described. 28. The method according to claim 21, wherein the step of providing time points in a pseudo-random manner executes a preset asynchronous method for generating each time point. The recording medium described. 29. A method according to any one of claims 21 to 26, wherein the step of providing time points in a pseudo-random manner executes a preset real-time method for generating each time point. Recording medium. 30. The event queue according to claim 21, wherein the event queue includes a plurality of start time points, a plurality of channel identifiers, and a plurality of waiting data indicators. recoding media. 31. A state machine for scheduling and communication, further comprising: an idle state, a data state, a schedule negotiation state, and a re-establishment state. The recording medium described in. 32. The recording medium according to claim 21, wherein the first device network is a piconet. 33. The recording medium according to claim 32, wherein the second device network is a piconet. 34. The method of any one of claims 21 to 33, further comprising the step of entering a schedule negotiation state in which a new time point is determined and the schedule is modified using the new time point. The recording medium described. 35. The method further comprises entering a schedule negotiation state upon detecting each time point that collides with each other, wherein a new time point is determined during the schedule negotiation state and the new time point is determined. The recording medium according to any one of claims 21 to 33, wherein the schedule is changed using time points to reduce the time points that collide with each other. 36. The recording medium according to claim 21, wherein the method includes a step of sending a forced termination message for ending the communication period. 37. The recording medium according to any one of claims 21 to 35, wherein the method includes the step of sending an end message indicating that the data for ending the communication period has been used up. 38. A method according to any of claims 21 to 35, wherein the method comprises the step of generating each end time point for scheduling the end of each communication period.
recoding media. 39. The recording medium according to claim 21, wherein the method includes the step of using a traffic overlay method for managing resource-secured traffic. 40. A recording medium according to any one of claims 21 to 38, wherein the method includes the step of using a dynamic rescheduling method for managing resource reserved traffic. 41. A method for pseudo-randomly and dynamically scheduling each communication period between each electronic device, said method transmitting output data from a first device to a first device network. The step of receiving input data from the first device network by the first device, the step of discovering a second device of the second device network, the first device network and the second device Providing pseudo-randomly each time point defining a schedule for the first device to communicate, storing each time point in an event queue, and adding at least one channel Dynamically change the above schedule to add communication processing capacity And a communication method of a communicable electronic device. 42. The communication method according to claim 41, wherein the dynamically changing step executes a fair allocation method for dynamically allocating communication processing power. 43. The communication method according to claim 42, wherein said fair allocation method includes the step of extending a previous communication period. 44. The communication method according to claim 42, wherein said fair allocation method comprises the step of reducing the number of each starting time point in said event queue. 45. The communication method according to claim 42, wherein said dynamically changing step executes an opportunistic allocation method for dynamically allocating communication processing power. 46. The opportunistic assignment method above is
46. The communication method according to claim 45, comprising the steps of evaluating waiting traffic and device availability, and modifying the schedule based on the evaluation. 47. The method according to any one of claims 41 to 46, wherein the step of providing time points in a pseudo-random manner executes a preset synchronous method for generating each time point. The communication method described. 48. The step of providing time points in a pseudo-random manner executes a preset asynchronous method for generating each time point. The communication method described. 49. A method according to any one of claims 41 to 46, wherein the step of providing time points in a pseudo-random manner executes a preset real-time method for generating each time point. Communication method. 50. The event queue according to claim 41, wherein each of the event queues includes a plurality of start time points, a plurality of channel identifiers, and a plurality of waiting data indicators. Communication method. 51. A state machine for scheduling and communication, further comprising: an idle state, a data state, a schedule negotiation state, and a re-establishment state. The communication method described in. 52. The communication method according to claim 41, wherein the first device network is a piconet. 53. The communication method according to claim 52, wherein the second device network is a piconet. 54. The method of any one of claims 41 through 53, wherein the method further comprises the step of entering a schedule negotiation state in which a new time point is determined and the schedule is modified using the new time point. The communication method described. 55. The method further comprises the step of entering a schedule negotiation state upon detecting each time point that collides with each other, wherein a new time point is determined during the schedule negotiation state and the new The communication method according to any one of claims 41 to 53, wherein the schedule is changed by using time points to reduce the time points that collide with each other. 56. The communication method according to claim 41, wherein the method includes a step of sending a forced termination message for ending the communication period. 57. The communication method according to any one of claims 41 to 55, wherein the method includes the step of sending an end message indicating that the data for ending the communication period has been used up. 58. A method according to any of claims 41-55, wherein the method comprises the step of generating each end time point for scheduling the end of each communication period.
Communication method. 59. The communication method according to any one of claims 41 to 58, wherein said method includes the step of using a traffic overlay method for managing resource reservation type traffic. 60. The communication method according to claim 41, wherein the method includes a step of using a dynamic schedule change method for managing resource-reserved traffic.