WO2003055247A2 - Communications device, method and program for receiving process execution, and computer-readable recording medium having same program recorded thereon - Google Patents

Communications device, method and program for receiving process execution, and computer-readable recording medium having same program recorded thereon Download PDF

Info

Publication number
WO2003055247A2
WO2003055247A2 PCT/JP2002/013045 JP0213045W WO03055247A2 WO 2003055247 A2 WO2003055247 A2 WO 2003055247A2 JP 0213045 W JP0213045 W JP 0213045W WO 03055247 A2 WO03055247 A2 WO 03055247A2
Authority
WO
WIPO (PCT)
Prior art keywords
communications
interrupt
link
receive
communications link
Prior art date
Application number
PCT/JP2002/013045
Other languages
French (fr)
Other versions
WO2003055247A3 (en
Inventor
Kazuyuki Kashiwabara
Wataru Tachibana
Noriyuki Ogawa
Masaaki Morioka
Original Assignee
Matsushita Electric Industrial Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Matsushita Electric Industrial Co., Ltd. filed Critical Matsushita Electric Industrial Co., Ltd.
Priority to KR10-2004-7004915A priority Critical patent/KR20040063905A/en
Priority to DE60211211T priority patent/DE60211211T2/en
Priority to US10/496,668 priority patent/US20050080754A1/en
Priority to EP02790749A priority patent/EP1454472B1/en
Publication of WO2003055247A2 publication Critical patent/WO2003055247A2/en
Publication of WO2003055247A3 publication Critical patent/WO2003055247A3/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14Handling requests for interconnection or transfer
    • G06F13/20Handling requests for interconnection or transfer for access to input/output bus
    • G06F13/24Handling requests for interconnection or transfer for access to input/output bus using interrupt
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B1/00Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
    • H04B1/38Transceivers, i.e. devices in which transmitter and receiver form a structural unit and in which at least one part is used for functions of transmitting and receiving
    • H04B1/40Circuits
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols

Definitions

  • the present invention relates to a communications device for fetching, in response to an occurrence of a receive interrupt or a timer interrupt, data which has been received from some other device and stored in a receive buffer, a method and a program for executing a receiving process , and a computer-readable recording medium having the same program recorded thereon.
  • interrupts are used for software to acknowledge hardware communications, for example.
  • the hardware stores, in a receive buffer, data including requests and acknowledgements and the like, and coming from some other device.
  • the software switches the task in process to an interrupt handler.
  • a receive interrupt occurs when the hardware performs data reception.
  • the resulting receive interrupt notified by the hardware is detected by a receive interrupt handler.
  • the software fetches the received data stored in the receive buffer into memory.
  • the software analyzes the received data thus fetched into the memory. If the analysis result shows that the received data is representing a connection request, for example, an acknowledgement is returned back to the source from where the request was forwarded.
  • Such a handshake establishes a communications link with the source from where the request was forwarded.
  • a timer interrupt occurs at regular intervals.
  • a timer interrupt handler detects a timer interrupt notified by the hardware (SI). Even if a timer interrupt is detected, a receive buffer does not always carry the received data therein. Thus, the software then determines whether or not the received data has been stored in the receive buffer (S2). If determined that the received data is stored in the receive buffer, the software accordingly fetches the received data in the receive buffer into memory (S3) .
  • the present invention is proposed in consideration of such problems of the prior art as described above.
  • An object thereof is to provide a communications device with which a communications efficiency can be improved without depending on CPU or hardware throughput, and a communications link with some other device can be smoothly established. Also provided are a method and a program forreceivingprocess execution, andacomputer-readablerecording medium having the same program recorded thereon.
  • the present invention adopts the following means .
  • data provided from some other device and stored in a receive buffer is fetched in response to a receive interrupt or a timer interrupt .
  • a link state determination unit determines whether or not a communications link with the other device is established. Based on the determination result, if the communications link has been established, a receive interrupt control unit causes the receive interrupt to stop occurring for the duration. That is, while the communications link is established, the dataprovided from the other device and stored in the receive buffer is fetched responding to an occurrence of a timer interrupt . There is no requirement for quick response while the communications link is established, and thus there is no need to shorten the interval between occurrences of the timer interrupts .
  • the link state determinationunit In order to cause the receive interrupt to stop occurring while the communications link is established, the link state determinationunit alsodetermineswhetherthecommunications link has been cut off. If the communications link is determined as having been cut off, the receive interrupt is allowed to occur again.
  • the receive interrupt is free to occur.
  • an occurrence of areceive interrupt maycause, to fetch, the data provided from the other device and stored in the receive buffer.
  • responding only to an occurrence of a timer interrupt may not ensure enough response to establish a communications link, responding to an occurrence of a receive interrupt can ensure this response.
  • the link state determination unit may refer to an application instruction to determine whether to accept or reject the request.
  • the receive interrupt is temporarily allowed to occur again, so that thus requested communications link can be smoothly established.
  • the link state determination unit may refer to a setting of QoS (Quality Of Service) to determine whether or not to accept the request for establishing another communications link receivedwhileonecommunications linkhas beenalreadyestablished. If the QoS setting is indicating a guaranteed type, it predicts possible difficulty of multilink communications. As such, the QoS setting automatically leads to appropriate determination without users ' or developers ' instructions .
  • QoS Quality Of Service
  • FIG.2 is adiagramshowing the relationshipbetween a timeout time and a response time.
  • FIG.3 is a diagram roughly showing the structure of a mobile phone of a first embodiment.
  • FIG. 4 is a flowchart of a receiving process executed by hardware .
  • FIG.5 is a diagram roughly showing the structure of a device for executing a receiving process equipped in the mobile phone of the first embodiment.
  • FIG. 6 is a flowchart of a receive interrupt process.
  • FIG. 7 is a flowchart of a timer interrupt process.
  • FIG.8 is a diagram roughly showing the structure of a device for executing a receiving process equipped in a mobile phone of a second embodiment .
  • FIG.9 is a diagram showing a specific example of a setting screen through which an inquiry is made to a user whether or not to enable multilink.
  • FIG. 10 is a flowchart of a setting process for a multilink establishment setting flag in accordance with a request coming from application software.
  • FIG. 11 is a flowchart of a multilink establishment determination process responding to a request coming from other devices for establishing a communications link.
  • FIG. 12 is a flowchart of the multilink establishment determination process responding to a request coming from application software for establishing a communications link.
  • FIG. 13 is a flowchart of a setting process for a multilink establishment setting flag based on a QoS setting.
  • the present invention is embodied in a receiving process program operating on a mobile terminal exemplarily having a radio communications capability.
  • a mobile terminal A is connected with an other device B via a radio path 100.
  • the mobile terminal A uses hardware 101 and software 102 to activate its communications capability.
  • the hardware 101 corresponds to lower layers of a protocol stack such as an RF layer, a baseband layer, and the like, in this communications capability.
  • Thehardware 101 receives from the other device B data including connection requests, acknowledgements, and the like.
  • the received data is copied into a receive buffer 103 (S102) .
  • S102 receive buffer 103
  • What resulted by this copying is data storage in the receive buffer 103 , and accordingly a request is made for a receive interrupt to occur.
  • the hardware In response to thus made request for an occurrence of a receive interrupt, the hardware
  • the hardware 101 determines whether a receive interrupt flag 104 is now turned ON or OFF (S103) . If the receive interrupt flag 104 is determined as being turned ON, the hardware 101 notifies the software 102 of the occurrence of the receive interrupt (S104 ) . Afternotifying the software 102 of the occurrence of the receive interrupt, or after determining that the receive interrupt flag 104 is being turnedOFF, the hardware 101 ends the data receiving process. That is, with the receive interrupt flag 104 turned OFF, the software
  • the hardware 101 also causes a timer interrupt to occur at regular intervals according to a timer 105, and every time a timer interrupt occurs, notifies the software 102 thereof.
  • the software 102 corresponds upper layers of the protocol stack such as a link management layer, a controller interface, an application programinterface, and the like. Upon notification from the hardware 101 of an occurrence of a receive interrupt or a timer interrupt, responding thereto, the software 102 fetches into the memory the data stored in the receive buffer 103.
  • the software 102 includes a receiving process program.
  • This receiving process program uses the microprocessor, the memory, and the like, of the mobile terminalA to operate the mobile phone A as a communications device having a device for executing a receiving process.
  • the receiving process device Al is provided with a receiving unit 1 , a link state determination unit 2, and a receive interrupt control unit 3.
  • the receivingunit 1 When notified by the hardware 101 that a receive interrupt oratimer interrupt has occurred, the receivingunit 1 responsively fetches into the memory the received data stored in the receive buffer 103.
  • Determined by the link state determination unit 2 is whether or not a (virtual) communications link 106 has been established on the radio path 100 between the mobile terminal A and the other device B , and if established, whether or not the communications link 106 has been cut off.
  • the receive interrupt control unit 3 turns OFF thereception interrupt flag 104 in thehardware 101 for the duration .
  • the hardware 101 does not notify the software 102 of the occurrence of the receive interrupt .
  • the receiving unit 1 receives no notification about occurrence of the receive interrupt. That is, the receive interrupt is caused to stop occurring.
  • the link state determination unit 2 determines as the communications link 106 having been cut off, the receive interrupt flag 104 is turned ON.
  • the hardware 101 determines that the receive interrupt flag 104 is now ON, and then notifies the software 102 of the occurrence of thereceive interrupt . As aresult , if the linkstate determination unit 2 determines that the communications link 106 has been cut off, the receive interrupt is allowed again to occur.
  • the device Al receives notification about occurrence of the receive interrupt only when the communications link 106 is not established, that is, before the communications link 106 is established (after the communications link 106 is cut off) .
  • FIG.6 is a flowchart for demonstrating the receive interrupt process.
  • the receiving unit 1 fetches the data stored in the receive buffer 103 into memory (S201).
  • the data thus fetched into the memory is analyzed by the receiving unit 1 (S202) .
  • the receiving unit 1 executes the receivingprocess withrespect to upper layers (S203) .
  • S203 upper layers
  • the link state determination unit 2 determines whether or not the communications link 106 has been established (S204). If the communications link 106 is determined as having been established, the receive interrupt controlunit 3 turns OFF the receive interrupt flag 104 (S205) . This is the end of the receive interrupt process .
  • the link state determination unit 2 uses the result derived by the receive interrupt process to determine whether or not the communications link 106 has been cut off (S206) . If the communications link 106 is determined as having been cut off, thereceive interrupt flag 104 is responsivelyturnedON (S207) . After the receive interrupt flag 104 is turned ON, or if the communications link 106 is determined as not being cut off, this is the end of the receive interrupt process.
  • the receive interrupt flag 104 is turned OFF. Therefore, notified to the receiving process device Al after the establishment of the communications link 106 are only occurrences of the timer interrupts.
  • a timer interrupt handler Upon notification of a timer interrupt by the hardware 101 to the receiving process device Al , a timer interrupt handler is responsivelywaked up, and the device Al starts executing a process relating to the timer interrupt.
  • the receiving unit 1 determines whether or not the receive buffer 103 carries data (S302) . If the receive buffer 103 is determined as carrying data, executed is a process similar to the receive interrupt process.
  • the receiving unit 1 performs data fetching from the receive buffer 103 into memory (S303) .
  • the data thus fetched into thememory is analyzedby the receiving unit 1 ( S304) .
  • the receiving unit 1 executes a receiving process with respect to the upper layers (S305) .
  • the link state determination unit 2 determines whether or not the communications link 106 has been established (S306).
  • the link state determinationunit 2 refers to the result derived by the receiving process to determine whether or not the communications link 106 has been cut off (S308). If the communications link 106 is determined as having been cut off, the receive interrupt flag 104 is responsively turned ON (S309) . In either case where the receive interrupt flag 104 is turned ON, or the communications link 106 is determined as not being cut off, the process is ended.
  • the receive interrupt is caused to stop occurring, and in response to an occurrence of a timer interrupt, the data stored in the receive buffer 103 is fetched. In this manner, the dispatching time to be taken associated with interrupt occurrences can be shortened, and a CPU load can be reduced. Further, as described above, responding to the receive interrupt is enabled before the communications link 106 is established. As is evident therefrom, the mobile terminal A is capable of improving the communications efficiency without the help of CPU or hardware throughput, and further, achieving smooth establishment of the communications link with the other device B .
  • the mobile terminal includes a mobile phone and a personal digital assistant to which a communications module meeting the W-CDMA standard or the Bluetooth standard is adopted
  • the communications device of the present invention is not restricted to such a mobile terminal.
  • the present invention is surely applicable to other types of communications devices, exemplified by communications devices with which wired communications is carried out .
  • the receiving process program is stored in flash memory, or the like, often equipped in the communications device. It is also possible to put it on the market through a telecommunications circuit such as the Internet, or recorded on a computer-readable recording medium such as CD-ROMs.
  • steps S206 andS207 maybe skipped, and if determination tells no link establishment , the receive interrupt process may be then ended.
  • steps S306 and S307 may be skipped, and step S308 may be carried out after step S305 of the receiving process is carried out to the upper layers.
  • the software 102 on the mobile terminal A fetches, into memory, data received from the other device B and stored in the receive buffer 103.
  • the issue here is that, while the communications link is established, if the receive buffer 103 stores only data communicated only via the link, no quick response is required for the data reception. There may be a case, however, the data to be stored in the receive buffer 103 may include any request for establishing another communications link.
  • the link state determination unit 2 in the receiving process device therein further determines whether or not to accept a request asking for establishing another communications linkwhile one communications link has been already established. Such a determination is made based on, for example, a multilink establishment setting flag.
  • the multilink establishment setting flag is used to set whether or not to reject establishment of a plurality of communications links. Assuming that the value thereof is represented in binary, with one value VI, the link state determination unit 2 determines to accept the request, andwiththe othervalueV2, therequest is rejectedthrough determination.
  • a flag setting unit 5 sets the flag by value in accordance with a request made by application software 4, which operates on the mobile terminal A, for example.
  • the application software 4 displays such a setting screen as shown in FIG. 9 on a display so that an inquiry can be made, asking a user whether or not to enable multilink.
  • the application software 4 asks for the flag setting unit 5 to make a setting request of the multilink establishment setting flag.
  • the flag setting unit 5 determines whether the request is rejectingmultilinkestablishment ornot (S401) . If therequest is accepting the multilink establishment, the flag setting unit
  • the value of the multilink establishment setting flag is set to the value VI (S402). If the request is rejecting multilink establishment, on the other hand, the value of the multilink establishment setting flag is set to the value V2 (S403).
  • the determination for multilink establishment will reflect the user's instruction provided to the application software 4 , the specifications of the application software 4, and the like.
  • FIG. 11 is a flowchart for demonstrating a process to determine multilink establishment in a case where a request comes from the other device for establishing a communications link.
  • the link state determination unit 2 determines whether or not any communications link has been already established (S501).
  • the link state determination unit 2 refers to themultilink establishment setting flag for its value to determine whether to accept the request or not (S503).
  • the link state determination unit 2 determines to reject the request, a response of connection rejection is given back to the source from where the request was provided (S504). If the link state determination unit 2 determines to accept the request , the receive interrupt control unit 3 allows a receive interrupt to occur again (S505). Once the receive interrupt is allowed to occur again, after the communications link is established, as described in the first embodiment, the receive interrupt is caused again to stop occurring in response to the receive interrupt flag 104 turned OFF by the receive interrupt control unit 3.
  • described in the present embodiment is a case where the mobile terminal A receives a request from the other device B for establishing a communications link therewith.
  • This is not restrictive, and when the application software operating on the mobile terminal A asks for any software lower than itself in the protocol stack to establish another communications link with the other device, a determination may be made whether or not to accept the request .
  • the link state determination unit 2 determines whether or not the communications link has been already established (S601). If no communications link is determined as having been already established, as described in the first embodiment, a process is executed to establish a communications link (S602). If the communications link is determined as having been already established, on the other hand, the link state determination unit 2 refers to the multilink establishment setting flag for its value to determine whether or not to accept the request (S603).
  • the receive interrupt control unit 3 allows the receive interrupt to occur again (S604).
  • Bluetooth software includes software on the side of an application as host , and software on the side of a host controller controlled by the application.
  • the host can make the QoS (Quality of Service) setting about communications with the hosts of other Bluetooth devices .
  • the QoS setting is made via an asynchronous connectionless link, which is established between the host of a certain Bluetooth device and the host of another Bluetooth device.
  • the host making the QoS setting transmits a QoS setup command to link management software, which is included in a local host controller via the link.
  • This setup command includes information about a service type, a peak bandwidth, for example.
  • the service type includes a best-effort type and a guaranteed type.
  • the link management software Upon reception of the QoS setup command, the link management software returns a command status event to the host, and then transmits a request to the link management software included in the host controller of the other Bluetooth device. With a response to accept the request, the link management software notifies a QoS setup completion event to the host locating upper thereto through the link. Further, the link management software having received the request-accepting response also notifies the QoS setup completion event to the host locating upper thereto through the link.
  • the QoS setting is made as such, and accordingly, the link management software locating lower than the application software can acquire the service type.
  • the link management software locating lower than the application software can acquire the service type.
  • operating any software corresponding to the link management software on the CPU realizes the flag setting unit 5, and the resulting flag setting unit 5 may set the flag by value based on the service type.
  • the flag settingunit 5 determines whether the service type information included in the command is indicating the guaranteed type or not (S701).
  • the flag setting unit 5 sets the value of the multilink establishment setting flag to the value V2 (S702) . If the service type information is determined as not indicating the guaranteed type, the link state determination unit 2 determines whether a communications linkhas been already established (S703) . Without a communications link being already established, the flag settingunit 5 sets thevalue of themultilinkestablishment setting flag to the value VI (S704).
  • the QoS setting is reflected to the value of the multilink establishment setting flag, even if a request comes for establishing another communications link while a communications link has been already established, the request is rejected if the already-established communications link shows a guaranteed type for its QoS type.
  • the dispatching time to be taken associatedwith interrupt occurrences can be shortened, and a CPU load can be reduced. This is because no receive interrupt occurs while a communications link is established. Consequently, the communications efficiency can be successfully improved without depending on CPU or hardware throughput. What is better, an occurrence of a receive interrupt can be used as a cue to establish a communications link, which is smoothly established with other devices.

Abstract

A communications device for fetching data received from some other device from a receive buffer into a memory managed by software, responding to an occurrence of a receive interrupt or a timer interrupt. A frequent occurrence of the receive interrupt or the timer interrupt leads to smooth establishment of a communications link with the other device, but results in reduction of the communications efficiency unless adopting a CPU higher in throughput or additional hardware. In the communications device, determination is made whether a communications link has been established or not. If established, the data is fetched in response to only the timer interrupt. If not, the data is fetched in response to either the receive interrupt or the timer interrupt. Consequently, the communications efficiency can be successfully improved, and the link can be smoothly established, without depending on CPU or hardware throughput.

Description

DESCRIPTION
COMMUNICATIONS DEVICE, METHOD AND PROGRAM FOR RECEIVING PROCESS
EXECUTION, AND COMPUTER-READABLE RECORDING MEDIUM
HAVING SAME PROGRAM RECORDED THEREON
TECHNICAL FIELD The present invention relates to a communications device for fetching, in response to an occurrence of a receive interrupt or a timer interrupt, data which has been received from some other device and stored in a receive buffer, a method and a program for executing a receiving process , and a computer-readable recording medium having the same program recorded thereon.
BACKGROUND ART In communications devices , interrupts are used for software to acknowledge hardware communications, for example. The hardware stores, in a receive buffer, data including requests and acknowledgements and the like, and coming from some other device. Upon notification from the hardware that a receive interrupt or a timer interrupt has occurred, the software switches the task in process to an interrupt handler.
A receive interrupt occurs when the hardware performs data reception. The resulting receive interrupt notified by the hardware is detected by a receive interrupt handler. The software fetches the received data stored in the receive buffer into memory. The software then analyzes the received data thus fetched into the memory. If the analysis result shows that the received data is representing a connection request, for example, an acknowledgement is returned back to the source from where the request was forwarded. Such a handshake establishes a communications link with the source from where the request was forwarded.
A timer interrupt, on the other hand, occurs at regular intervals. As shown in FIG.1 example, a timer interrupt handler detects a timer interrupt notified by the hardware (SI). Even if a timer interrupt is detected, a receive buffer does not always carry the received data therein. Thus, the software then determines whether or not the received data has been stored in the receive buffer (S2). If determined that the received data is stored in the receive buffer, the software accordingly fetches the received data in the receive buffer into memory (S3) .
The issue here is that, data fetching by the timer interrupt often slows response comparedwiththe casebythereceive interrupt , This is because, in such a case of data fetching responding to the timer interrupt, even if data storage is made in the receive buffer, the data is not fetched unless another timer interrupt occurs. Therefore, if the data storage is made in the receive buffer immediately after a timer interrupt occurs, it means that data fetching has to wait for the interval, approximately, between timer interrupt occurrences. Referring to FIG. 2 example, when a communications device A receives a connection request, set in another communications device B having forwarded the request is a timeout time To , which is a time before an acknowledgement is returned. The longer a time Ti , which is between request reception by the communications device A and occurrence of another timer interrupt, the longer, correspondingly, a response time Tr. As a result, if no acknowledgement is returned within the timeout time To , a communications link fails to be established. Even if a communications link is established after trying again, the resulting communications link may require extra time for data transfer.
For betterment, to shorten the response time, such measures are taken as shortening the interval between occurrences of the timer interrupts, or continuously using the receive interrupt. The problem here is that, shortening the interval between occurrences of the timer interrupts, or continuously using the receive interrupt consequentlywakes up the interrupt handlermore often. As a result of the interrupt handler being waked up frequently, the dispatching time takes longer for that, resulting in increase of a CPU load. If this is the case, the communications efficiency may be reduced unless using a CPU higher in throughput or additional hardware.
Such a problem becomes critical in communications devices exemplified by mobile phones. The recent type of mobile phones has been enhanced to be faster in data communications speed, but adopting a CPU higher in throughput for the purpose is difficult in terms of cost. Similarly, increasing the size of the hardware is not preferable. Also in terms of power consumption, CPU or hardware implementation on the mobile phones has a restriction. The present invention is proposed in consideration of such problems of the prior art as described above. An object thereof is to provide a communications device with which a communications efficiency can be improved without depending on CPU or hardware throughput, and a communications link with some other device can be smoothly established. Also provided are a method and a program forreceivingprocess execution, andacomputer-readablerecording medium having the same program recorded thereon.
DISCLOSURE OF THE INVENTION In order to attain the object above, the present invention adopts the following means .
In the present invention, data provided from some other device and stored in a receive buffer is fetched in response to a receive interrupt or a timer interrupt . A link state determination unit determines whether or not a communications link with the other device is established. Based on the determination result, if the communications link has been established, a receive interrupt control unit causes the receive interrupt to stop occurring for the duration. That is, while the communications link is established, the dataprovided from the other device and stored in the receive buffer is fetched responding to an occurrence of a timer interrupt . There is no requirement for quick response while the communications link is established, and thus there is no need to shorten the interval between occurrences of the timer interrupts . Because no receive interrupt occurs in the meantime, the dispatching time to be taken associated with interrupt occurrences can be shortened. What resulted thereby is better communications efficiency achieved independent of CPU or hardware throughput . In order to cause the receive interrupt to stop occurring while the communications link is established, the link state determinationunit alsodetermineswhetherthecommunications link has been cut off. If the communications link is determined as having been cut off, the receive interrupt is allowed to occur again.
Without the communications link being established, the receive interrupt is free to occur. Thus , while no communications link is established, an occurrence of areceive interruptmaycause, to fetch, the data provided from the other device and stored in the receive buffer. Although responding only to an occurrence of a timer interrupt may not ensure enough response to establish a communications link, responding to an occurrence of a receive interrupt can ensure this response.
In this manner, without depending on the CPU or hardware throughput, the communications efficiency can be successfully improved, further leading to smooth establishment of a communications link with some other device.
If a request comes for establishing another communications link when one communications link has been already established, the link state determination unit may refer to an application instruction to determine whether to accept or reject the request.
If therequest is acceptedthroughdetermination, thereceive interrupt control unit allows the receive interrupt to occur again.
If the request is rejected through determination, a negative response is made with respect to the request.
As such, even if a request comes for establishing another communications link when one communications link has been already established, the receive interrupt is temporarily allowed to occur again, so that thus requested communications link can be smoothly established.
Herein, the link state determination unit may refer to a setting of QoS (Quality Of Service) to determine whether or not to accept the request for establishing another communications link receivedwhileonecommunications linkhas beenalreadyestablished. If the QoS setting is indicating a guaranteed type, it predicts possible difficulty of multilink communications. As such, the QoS setting automatically leads to appropriate determination without users ' or developers ' instructions . BRIEF DESCRIPTION OF THE DRAWINGS FIG.1 is a flowchart of a receiving process applied to data to be received by means of a timer interrup .
FIG.2 is adiagramshowing the relationshipbetween a timeout time and a response time.
FIG.3 is a diagram roughly showing the structure of a mobile phone of a first embodiment.
FIG. 4 is a flowchart of a receiving process executed by hardware . FIG.5 is a diagram roughly showing the structure of a device for executing a receiving process equipped in the mobile phone of the first embodiment.
FIG. 6 is a flowchart of a receive interrupt process. FIG. 7 is a flowchart of a timer interrupt process. FIG.8 is a diagram roughly showing the structure of a device for executing a receiving process equipped in a mobile phone of a second embodiment .
FIG.9 is a diagram showing a specific example of a setting screen through which an inquiry is made to a user whether or not to enable multilink.
FIG. 10 is a flowchart of a setting process for a multilink establishment setting flag in accordance with a request coming from application software.
FIG. 11 is a flowchart of a multilink establishment determination process responding to a request coming from other devices for establishing a communications link.
FIG. 12 is a flowchart of the multilink establishment determination process responding to a request coming from application software for establishing a communications link. FIG. 13 is a flowchart of a setting process for a multilink establishment setting flag based on a QoS setting.
BEST MODE FOR CARRYING OUT THE INVENTION In the below, embodiments of the present invention are described by referring to accompanying drawings.
In the following embodiments, the present invention is embodied in a receiving process program operating on a mobile terminal exemplarily having a radio communications capability.
(First Embodiment) Referring to FIG. 3, a mobile terminal A is connected with an other device B via a radio path 100. The mobile terminal A uses hardware 101 and software 102 to activate its communications capability. The hardware 101 corresponds to lower layers of a protocol stack such as an RF layer, a baseband layer, and the like, in this communications capability. Thehardware 101 receives from the other device B data including connection requests, acknowledgements, and the like.
Referring to FIG. 4, upon data reception by the hardware
101 from the other device B (S101), the received data is copied into a receive buffer 103 (S102) . What resulted by this copying is data storage in the receive buffer 103 , and accordingly a request is made for a receive interrupt to occur. In response to thus made request for an occurrence of a receive interrupt, the hardware
101 determines whether a receive interrupt flag 104 is now turned ON or OFF (S103) . If the receive interrupt flag 104 is determined as being turned ON, the hardware 101 notifies the software 102 of the occurrence of the receive interrupt (S104 ) . Afternotifying the software 102 of the occurrence of the receive interrupt, or after determining that the receive interrupt flag 104 is being turnedOFF, the hardware 101 ends the data receiving process. That is, with the receive interrupt flag 104 turned OFF, the software
102 receives no occurrence notification of the receive interrupt.
The hardware 101 also causes a timer interrupt to occur at regular intervals according to a timer 105, and every time a timer interrupt occurs, notifies the software 102 thereof.
The software 102 corresponds upper layers of the protocol stack such as a link management layer, a controller interface, an application programinterface, and the like. Upon notification from the hardware 101 of an occurrence of a receive interrupt or a timer interrupt, responding thereto, the software 102 fetches into the memory the data stored in the receive buffer 103.
Here, the software 102 includes a receiving process program.
This receiving process program uses the microprocessor, the memory, and the like, of the mobile terminalA to operate the mobile phone A as a communications device having a device for executing a receiving process.
Referring to FIG. 5, the receiving process device Al is provided with a receiving unit 1 , a link state determination unit 2, and a receive interrupt control unit 3. When notified by the hardware 101 that a receive interrupt oratimer interrupt has occurred, the receivingunit 1 responsively fetches into the memory the received data stored in the receive buffer 103.
Determined by the link state determination unit 2 is whether or not a (virtual) communications link 106 has been established on the radio path 100 between the mobile terminal A and the other device B , and if established, whether or not the communications link 106 has been cut off.
Based on the determination result thus derived by the link state determination unit 2, if the communications link 106 has been established, the receive interrupt control unit 3 turns OFF thereception interrupt flag 104 in thehardware 101 for the duration . As described above, through determination whether the receive interrupt flag 104 has been turned ON or OFF, and if the receive interrupt flag 104 is determined as having been turned OFF, the hardware 101 does not notify the software 102 of the occurrence of the receive interrupt . As a result , while the communications link 106 is established, the receiving unit 1 receives no notification about occurrence of the receive interrupt. That is, the receive interrupt is caused to stop occurring. In the case where the link state determination unit 2 determines as the communications link 106 having been cut off, the receive interrupt flag 104 is turned ON. Responsively, the hardware 101 determines that the receive interrupt flag 104 is now ON, and then notifies the software 102 of the occurrence of thereceive interrupt . As aresult , if the linkstate determination unit 2 determines that the communications link 106 has been cut off, the receive interrupt is allowed again to occur.
The device Al receives notification about occurrence of the receive interrupt only when the communications link 106 is not established, that is, before the communications link 106 is established (after the communications link 106 is cut off) .
Prior to establishment of the communications link 106, if the device Al (or a receive process program) is notified by the hardware 101 that the receive interrupt has occurred, a receive interrupt handler is waked up responding to the notification, and then the receiving process deviceAl starts going through a receive interrupt process. Here, FIG.6 is a flowchart for demonstrating the receive interrupt process. As shown in FIG. 6, the receiving unit 1 fetches the data stored in the receive buffer 103 into memory (S201). The data thus fetched into the memory is analyzed by the receiving unit 1 (S202) . Thereafter, through the analysis applied to the fetched data, based on the result derived thereby, the receiving unit 1 executes the receivingprocess withrespect to upper layers (S203) . Here, even if the fetched data is analyzed as being a connection request, an acknowledgement response is quickly made, leading to smooth establishment of the communications link 106. This is because the receiving process is already done by the receive interrupt .
Next, based on the result derived by the receiving process, the link state determination unit 2 determines whether or not the communications link 106 has been established (S204). If the communications link 106 is determined as having been established, the receive interrupt controlunit 3 turns OFF the receive interrupt flag 104 (S205) . This is the end of the receive interrupt process .
If the communications link 106 is not determined as having been established, the link state determination unit 2 uses the result derived by the receive interrupt process to determine whether or not the communications link 106 has been cut off (S206) . If the communications link 106 is determined as having been cut off, thereceive interrupt flag 104 is responsivelyturnedON (S207) . After the receive interrupt flag 104 is turned ON, or if the communications link 106 is determined as not being cut off, this is the end of the receive interrupt process.
As already described in the above, when the communications link 106 is established responding to the reception of the connection request, the receive interrupt flag 104 is turned OFF. Therefore, notified to the receiving process device Al after the establishment of the communications link 106 are only occurrences of the timer interrupts.
Upon notification of a timer interrupt by the hardware 101 to the receiving process device Al , a timer interrupt handler is responsivelywaked up, and the device Al starts executing a process relating to the timer interrupt.
Referring to FIG. 7, when the software 102 detects a timer interrupt (S301) , the receiving unit 1 determines whether or not the receive buffer 103 carries data (S302) . If the receive buffer 103 is determined as carrying data, executed is a process similar to the receive interrupt process.
That is, the receiving unit 1 performs data fetching from the receive buffer 103 into memory (S303) . The data thus fetched into thememory is analyzedby the receiving unit 1 ( S304) . Through the analysis applied to the fetched data, according to the result, the receiving unit 1 executes a receiving process with respect to the upper layers (S305) . In this case, although the receiving process is carried out responding to the timer interrupt, the response is not required to be quick after the communications link 106 is established. Next, based on the result derived by the receiving process, the link state determination unit 2 determines whether or not the communications link 106 has been established (S306). If the communications link 106 is determined as having been established, thereceive interrupt controlunit 3 turnsOFF thereceive interrupt flag 104 (S307), and this is the end of the process. In both cases that the receive buffer 103 is determined as carrying no data, or the communications link 106 is determined as not being established, the link state determinationunit 2 refers to the result derived by the receiving process to determine whether or not the communications link 106 has been cut off (S308). If the communications link 106 is determined as having been cut off, the receive interrupt flag 104 is responsively turned ON (S309) . In either case where the receive interrupt flag 104 is turned ON, or the communications link 106 is determined as not being cut off, the process is ended.
After the communications link 106 is established by going through such a receiving process method, the receive interrupt is caused to stop occurring, and in response to an occurrence of a timer interrupt, the data stored in the receive buffer 103 is fetched. In this manner, the dispatching time to be taken associated with interrupt occurrences can be shortened, and a CPU load can be reduced. Further, as described above, responding to the receive interrupt is enabled before the communications link 106 is established. As is evident therefrom, the mobile terminal A is capable of improving the communications efficiency without the help of CPU or hardware throughput, and further, achieving smooth establishment of the communications link with the other device B . It should be noted here that, although the mobile terminal includes a mobile phone and a personal digital assistant to which a communications module meeting the W-CDMA standard or the Bluetooth standard is adopted, the communications device of the present invention is not restricted to such a mobile terminal. The present invention is surely applicable to other types of communications devices, exemplified by communications devices with which wired communications is carried out .
Moreover, the receiving process program is stored in flash memory, or the like, often equipped in the communications device. It is also possible to put it on the market through a telecommunications circuit such as the Internet, or recorded on a computer-readable recording medium such as CD-ROMs.
Priorto establishment of the communications link106 , either a receive interrupt or a timer interrupt occurs . Therefore, even before the communications link 106 is established, data fetching may be performed from the receive buffer 103 responding to a timer interrupt. Here, to ensure a steady quick acknowledgement response, data fetching responding only to a timer interrupt is not enough. Therefore, there needs to respond only to a receive interrupt, or either a timer interrupt or a receive interrupt.
Further, in the receive interrupt process to be executed respondingtoareceive interrupt, steps S206 andS207maybe skipped, and if determination tells no link establishment , the receive interrupt process may be then ended. Similarly, in the receiving interrupt process responding to a timer interrupt, steps S306 and S307 may be skipped, and step S308 may be carried out after step S305 of the receiving process is carried out to the upper layers. (Second Embodiment)
While a communications link is established, no receive interrupt occurs in the mobile terminal A in the first embodiment . Responding to an occurrence of a timer interrupt, the software 102 on the mobile terminal A fetches, into memory, data received from the other device B and stored in the receive buffer 103. The issue here is that, while the communications link is established, if the receive buffer 103 stores only data communicated only via the link, no quick response is required for the data reception. There may be a case, however, the data to be stored in the receive buffer 103 may include any request for establishing another communications link. In this case, if the software 102 performs fetching, into memory, with respect to even a request for establishing another communications link responding only to an occurrence of a timer interrupt, there may be a possibility for repeated timeouts before thus requested another communications link is established. For betterment, referring to FIG. 8, the link state determination unit 2 in the receiving process device therein further determines whether or not to accept a request asking for establishing another communications linkwhile one communications link has been already established. Such a determination is made based on, for example, a multilink establishment setting flag. Here, the multilink establishment setting flag is used to set whether or not to reject establishment of a plurality of communications links. Assuming that the value thereof is represented in binary, with one value VI, the link state determination unit 2 determines to accept the request, andwiththe othervalueV2, therequest is rejectedthrough determination.
A flag setting unit 5 sets the flag by value in accordance with a request made by application software 4, which operates on the mobile terminal A, for example. The application software 4 displays such a setting screen as shown in FIG. 9 on a display so that an inquiry can be made, asking a user whether or not to enable multilink. Through the user selection between "Yes" and "No" on the setting screen, in order to reflect the selection result to a setting, the application software 4 asks for the flag setting unit 5 to make a setting request of the multilink establishment setting flag.
If such a setting request comes from the application software
4 for setting the multilink establishment setting flag, as shown in FIG.10, the flag setting unit 5 determines whether the request is rejectingmultilinkestablishment ornot (S401) . If therequest is accepting the multilink establishment, the flag setting unit
5 sets the value of the multilink establishment setting flag to the value VI (S402). If the request is rejecting multilink establishment, on the other hand, the value of the multilink establishment setting flag is set to the value V2 (S403).
As such, after the multilink establishment setting flag is set according to the setting request provided from such local application software 4, the determination for multilink establishment will reflect the user's instruction provided to the application software 4 , the specifications of the application software 4, and the like.
FIG. 11 is a flowchart for demonstrating a process to determine multilink establishment in a case where a request comes from the other device for establishing a communications link.
In the mobile terminal A, when the receiving unit 1 analyzes that the data fetched from the receive buffer 103 into the memory is a request for establishing a communications link, the link state determination unit 2 determines whether or not any communications link has been already established (S501).
If determination tells that no communications link is established, asalreadydescribedin thefirst embodiment , executed is a process for establishing a communications link (S502). If determination tells that a communications link is established, on the other hand, the link state determination unit 2 refers to themultilink establishment setting flag for its value to determine whether to accept the request or not (S503).
If the link state determination unit 2 determines to reject the request, a response of connection rejection is given back to the source from where the request was provided (S504). If the link state determination unit 2 determines to accept the request , the receive interrupt control unit 3 allows a receive interrupt to occur again (S505). Once the receive interrupt is allowed to occur again, after the communications link is established, as described in the first embodiment, the receive interrupt is caused again to stop occurring in response to the receive interrupt flag 104 turned OFF by the receive interrupt control unit 3.
As such, even if a request for establishing another communications linkwhile one communications linkhas been already established, temporarily allowing the receive interrupt to occur will smoothly establish another communications link.
Here, described in the present embodiment is a case where the mobile terminal A receives a request from the other device B for establishing a communications link therewith. This is not restrictive, and when the application software operating on the mobile terminal A asks for any software lower than itself in the protocol stack to establish another communications link with the other device, a determination may be made whether or not to accept the request .
Upon reception from the application software of a request for establishing a communications link, similarly to an establishment request from the other device B , as shown in FIG. 12, the link state determination unit 2 determines whether or not the communications link has been already established (S601). If no communications link is determined as having been already established, as described in the first embodiment, a process is executed to establish a communications link (S602). If the communications link is determined as having been already established, on the other hand, the link state determination unit 2 refers to the multilink establishment setting flag for its value to determine whether or not to accept the request (S603).
When the link state determination unit 2 determines to accept the request, similarly to the establishment request coming from the other device B, the receive interrupt control unit 3 allows the receive interrupt to occur again (S604).
When the link state determination unit 2 determines to reject the request, a response of connection rejection is given to the application (S605). Instead of referring to the request provided from the application software to set the multilink establishment setting flag, referring to information managed by any software locating lower than the application software in the protocol stack is a possibility. As an example, Bluetooth software includes software on the side of an application as host , and software on the side of a host controller controlled by the application. The host can make the QoS (Quality of Service) setting about communications with the hosts of other Bluetooth devices . The QoS setting is made via an asynchronous connectionless link, which is established between the host of a certain Bluetooth device and the host of another Bluetooth device. The host making the QoS setting transmits a QoS setup command to link management software, which is included in a local host controller via the link. This setup command includes information about a service type, a peak bandwidth, for example. The service type includes a best-effort type and a guaranteed type. Upon reception of the QoS setup command, the link management software returns a command status event to the host, and then transmits a request to the link management software included in the host controller of the other Bluetooth device. With a response to accept the request, the link management software notifies a QoS setup completion event to the host locating upper thereto through the link. Further, the link management software having received the request-accepting response also notifies the QoS setup completion event to the host locating upper thereto through the link.
In the Bluetooth device, the QoS setting is made as such, and accordingly, the link management software locating lower than the application software can acquire the service type. Alternatively, operating any software corresponding to the link management software on the CPU realizes the flag setting unit 5, and the resulting flag setting unit 5 may set the flag by value based on the service type.
If this is the case, when received the QoS setup command from thehost , as shown in FIG.13 , the flag settingunit 5 determines whether the service type information included in the command is indicating the guaranteed type or not (S701).
If the service type information is determined as indicating the guaranteed type, the flag setting unit 5 sets the value of the multilink establishment setting flag to the value V2 (S702) . If the service type information is determined as not indicating the guaranteed type, the link state determination unit 2 determines whether a communications linkhas been already established (S703) . Without a communications link being already established, the flag settingunit 5 sets thevalue of themultilinkestablishment setting flag to the value VI (S704).
As such, when the QoS setting is reflected to the value of the multilink establishment setting flag, even if a request comes for establishing another communications link while a communications link has been already established, the request is rejected if the already-established communications link shows a guaranteed type for its QoS type.
As is evident from the above, in the present invention, the dispatching time to be taken associatedwith interrupt occurrences can be shortened, and a CPU load can be reduced. This is because no receive interrupt occurs while a communications link is established. Consequently, the communications efficiency can be successfully improved without depending on CPU or hardware throughput. What is better, an occurrence of a receive interrupt can be used as a cue to establish a communications link, which is smoothly established with other devices.
Moreover, if there is a request asking for establishing another communications linkwhile one communications link has been alreadyestablished, the request is checked to seewhether to accept or reject. If the request is accepted, allowing the request interrupt to occur again will lead to smooth establishment of multilink.

Claims

1. A communications device for fetching, in response to an occurrence of a receive interrupt or a timer interrupt, data received from an other device and stored in a receive buffer, the communications device comprising: alinkstate determinationunit operable todeterminewhether a communications link with the other device is established; and a receive interrupt control unit operable to cause, based on a determination result derived by the link state determination unit, the receive interrupt to stop occurring while the communications link is established.
2. The communications device according to claim 1 , wherein the link state determination unit determines whether the communications link is cut off, and the receive interrupt control unit allows, when the link state determination unit determines that the communications link is cut off, the receive interrupt to occur again.
3. The communications device according to claim 1, wherein the link state determination unit determines, if there comes a request to establish an other communications link while the communications link is being established, whether to accept or reject the request.
4. The communications device according to claim 3 , wherein the link state determination unit determines whether to accept or reject the request based on a QoS (Quality of Service) setting.
5. The communications device according to claim 3, wherein the link state determination unit determines whether to accept or reject the request based on an application instruction.
6. The communications device according to claim 3, wherein the request for establishing the other communications link is the one made with respect to the device itself or the other device.
7. The communications device according to claim 3, wherein the receive interrupt control unit allows the receive interrupt to occur again when the link state determination unit determines to accept the request.
8. The communications device according to claim 3 , wherein, when the link state determination unit determines to reject the request, a rejection response is given to the request.
9. A receiving process method for fetching, in response to an occurrence of a receive interrupt or a timer interrupt , data received from an other device and stored in a receive buffer, the method comprising the steps of: determining whether a communications link with the other device is established; and causing, based on a result derived by the determination, the receive interrupt to stop occurring while the communications link is established.
10. A receiving process program for fetching, in response to an occurrence of a receive interrupt or a timer interrupt, data received from an other device and stored in a receive buffer, the program comprising the steps of, for computer execution: determining whether a communications link with the other device is established; and causing, based on a result derived by the determination, the receive interrupt to stop occurring while the communications link is established.
11. A computer-readable recording medium, having recorded thereon the receiving process program according to claim 10.
PCT/JP2002/013045 2001-12-13 2002-12-12 Communications device, method and program for receiving process execution, and computer-readable recording medium having same program recorded thereon WO2003055247A2 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR10-2004-7004915A KR20040063905A (en) 2001-12-13 2002-12-12 Communications device, method and program for receiving process execution, and computer-readable recording medium having same program recorded thereon
DE60211211T DE60211211T2 (en) 2001-12-13 2002-12-12 COMMUNICATION DEVICE, RECEPTION PROCESSING METHOD AND PROGRAM, AND COMPUTER READABLE MEDIUM ON WHICH THIS PROGRAM IS STORED
US10/496,668 US20050080754A1 (en) 2001-12-13 2002-12-12 Communications device, method and program for receiving process execution, and computer-readable recording medium having same program recorded thereon
EP02790749A EP1454472B1 (en) 2001-12-13 2002-12-12 Communications device, method and program for receiving process execution, and computer-readable recording medium having same program recorded thereon

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2001-379450 2001-12-13
JP2001379450 2001-12-13

Publications (2)

Publication Number Publication Date
WO2003055247A2 true WO2003055247A2 (en) 2003-07-03
WO2003055247A3 WO2003055247A3 (en) 2004-02-19

Family

ID=19186819

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2002/013045 WO2003055247A2 (en) 2001-12-13 2002-12-12 Communications device, method and program for receiving process execution, and computer-readable recording medium having same program recorded thereon

Country Status (6)

Country Link
US (1) US20050080754A1 (en)
EP (1) EP1454472B1 (en)
KR (1) KR20040063905A (en)
CN (1) CN100444594C (en)
DE (1) DE60211211T2 (en)
WO (1) WO2003055247A2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100426789C (en) * 2004-11-01 2008-10-15 华为技术有限公司 High-speed message transmitting method with high reliability

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090319810A1 (en) * 2007-01-11 2009-12-24 Panasonic Corporation Receiving apparatus and activation control method for receiving apparatus
JP2009259089A (en) * 2008-04-18 2009-11-05 Nec Corp Device and method for tracking program execution path, and program
US8219713B2 (en) * 2008-07-01 2012-07-10 Broadcom Corporation Method and system for a network controller based pass-through communication mechanism between local host and management controller
US20150173116A1 (en) * 2013-12-13 2015-06-18 Mediatek Inc. Communications method, device and system
CN106485293A (en) * 2015-08-31 2017-03-08 中兴通讯股份有限公司 A kind of control method of write operation, device and equipment
US20190313311A1 (en) * 2018-04-09 2019-10-10 Mediatek Inc. Apparatuses, service networks, and methods for handling plmn-specific parameters for an inter-plmn handover
US11026124B2 (en) 2018-07-02 2021-06-01 Mediatek Inc. Enhanced handling on 5G QoS operations
US11039369B2 (en) 2018-08-10 2021-06-15 Mediatek Inc. Handling 5G QoS rules on QoS operation errors

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0447054A2 (en) * 1990-03-15 1991-09-18 International Business Machines Corporation Integrated data link controller with synchronous link interface and asynchronous host processor interface

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5317692A (en) * 1991-01-23 1994-05-31 International Business Machines Corporation Method and apparatus for buffer chaining in a communications controller
JPH05167680A (en) * 1991-12-19 1993-07-02 Fujitsu Ltd Terminal interrupt control system
US5319752A (en) * 1992-09-18 1994-06-07 3Com Corporation Device with host indication combination
CA2126174C (en) * 1993-06-30 2003-01-21 David Thielen Method and system for interrupt-responsive execution of communications protocols
US6292508B1 (en) * 1994-03-03 2001-09-18 Proxim, Inc. Method and apparatus for managing power in a frequency hopping medium access control protocol
FI98181C (en) * 1995-01-04 1997-04-25 Nokia Telecommunications Oy Procedure for making continuation calls in an intelligent network
FR2730114B1 (en) * 1995-01-27 1997-04-11 France Telecom INTERRUPTION OF A COMMUNICATION BETWEEN TWO TERMINALS BY A CALL FROM ANOTHER TERMINAL
US6377548B1 (en) * 1997-10-14 2002-04-23 Lucent Technologies Inc. Method for admitting new connections based on measured quantities in a multiple access system for communications networks
US6338111B1 (en) * 1999-02-22 2002-01-08 International Business Machines Corporation Method and apparatus for reducing I/O interrupts
US6434651B1 (en) * 1999-03-01 2002-08-13 Sun Microsystems, Inc. Method and apparatus for suppressing interrupts in a high-speed network environment
JP4181685B2 (en) * 1999-03-12 2008-11-19 富士通株式会社 Power control method, electronic device, and recording medium
US6647440B1 (en) * 1999-09-15 2003-11-11 Koninklijke Philips Electronics N.V. End-of-message handling and interrupt generation in a CAN module providing hardware assembly of multi-frame CAN messages
US6760799B1 (en) * 1999-09-30 2004-07-06 Intel Corporation Reduced networking interrupts
CN1088218C (en) * 1999-11-14 2002-07-24 邓国顺 Electronic flash storage method and device for data processing system
JP3600095B2 (en) * 1999-12-07 2004-12-08 松下電器産業株式会社 Interrupt management device and interrupt management method
US6990555B2 (en) * 2001-01-09 2006-01-24 Pact Xpp Technologies Ag Method of hierarchical caching of configuration data having dataflow processors and modules having two- or multidimensional programmable cell structure (FPGAs, DPGAs, etc.)

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0447054A2 (en) * 1990-03-15 1991-09-18 International Business Machines Corporation Integrated data link controller with synchronous link interface and asynchronous host processor interface

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100426789C (en) * 2004-11-01 2008-10-15 华为技术有限公司 High-speed message transmitting method with high reliability

Also Published As

Publication number Publication date
DE60211211T2 (en) 2007-02-15
EP1454472B1 (en) 2006-05-03
DE60211211D1 (en) 2006-06-08
EP1454472A2 (en) 2004-09-08
KR20040063905A (en) 2004-07-14
US20050080754A1 (en) 2005-04-14
WO2003055247A3 (en) 2004-02-19
CN100444594C (en) 2008-12-17
CN1572100A (en) 2005-01-26

Similar Documents

Publication Publication Date Title
US11405837B2 (en) Information processing apparatus, communication terminal, and non-transitory storage medium storing instructions executable by information processing apparatus
KR101251439B1 (en) Automatical test system and method performance of smart phone using android debug bridge interface
JP7419482B2 (en) Software upgrade management method, servers, terminals, devices and storage media
EP1685494A2 (en) System and method for establishing a communication between a peripheral device and a wireless device
US8868065B2 (en) System and method for reducing power consumption for push messaging
US7937499B1 (en) Methods and apparatus for dynamically switching between polling and interrupt mode for a ring buffer of a network interface card
US20050204189A1 (en) Network apparatus, method for controlling the same, and program for the same
US20050097226A1 (en) Methods and apparatus for dynamically switching between polling and interrupt to handle network traffic
JPH0824320B2 (en) Method and device for buffer chaining in communication control device
EP1454472B1 (en) Communications device, method and program for receiving process execution, and computer-readable recording medium having same program recorded thereon
JP4609113B2 (en) Processor
JPH06139031A (en) Printer controller
WO2020102940A1 (en) Abnormality processing method, terminal device and storage medium
JP4044831B2 (en) COMMUNICATION DEVICE, COMMUNICATION METHOD, COMPUTER PROGRAM, AND COMPUTER-READABLE RECORDING MEDIUM
CN109614248B (en) Message compression method, device, storage medium and terminal equipment
US20070081412A1 (en) Apparatus and method for controlling dual port memory in a mobile communication terminal with multi processors
JP2001236302A (en) Information processor
JPH1078856A (en) Interruption by priority printing method and system therefor
KR102582483B1 (en) the Method for Wireless Communication and the Electronic Device supporting the same
CN109597576B (en) Method, device, readable storage medium and system for improving response speed of NCQ command
JP2006285401A (en) Image processor, control method for image processor, program and storage medium
JP3452656B2 (en) DMA controller
KR20230104625A (en) System and Method for Modem Stabilization When Waiting for AP Powered Link Recovery
JP2002229756A (en) Data processing system and its control method
JP2000312244A (en) Network interface switching method, its system and its recording medium

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): CN KR US

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): DE FR GB

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: 2002790749

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 1020047004915

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 20028208412

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 10496668

Country of ref document: US

WWP Wipo information: published in national office

Ref document number: 2002790749

Country of ref document: EP

WWG Wipo information: grant in national office

Ref document number: 2002790749

Country of ref document: EP