WO2015000169A1 - Coordination de traitement de voip et de traitement de réseau sans fil - Google Patents

Coordination de traitement de voip et de traitement de réseau sans fil Download PDF

Info

Publication number
WO2015000169A1
WO2015000169A1 PCT/CN2013/078869 CN2013078869W WO2015000169A1 WO 2015000169 A1 WO2015000169 A1 WO 2015000169A1 CN 2013078869 W CN2013078869 W CN 2013078869W WO 2015000169 A1 WO2015000169 A1 WO 2015000169A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication interface
packets
processing
data
determining
Prior art date
Application number
PCT/CN2013/078869
Other languages
English (en)
Inventor
Yifeng Tu
Yuanxi WANG
Original Assignee
Qualcomm Incorporated
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 Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2013/078869 priority Critical patent/WO2015000169A1/fr
Publication of WO2015000169A1 publication Critical patent/WO2015000169A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/6215—Individual queue per QOS, rate or priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • Embodiments of the inventive subject matter generally relate to the field of network data processing, and, more particularly, to coordinating network data processing with VoIP processing.
  • VoIP Voice over Internet Protocol
  • DSP digital signal processor
  • ISA instruction set architecture
  • VoIP tasks typically need access to CPU cycles every 10ms or 20ms in order to meet real-time and latency requirements associated with VoIP processing.
  • VoIP tasks and wireless (e.g., Wi-Fi®) tasks are running simultaneously, CPU cycles are not guaranteed to VoIP tasks. The contention for CPU cycles may lead to reduced voice call quality or even dropped calls.
  • a method comprises receiving one or more packets associated with a first communication interface; determining a quantity of data for processing associated with a second communication interface; and in response to determining that the quantity of data for processing associated with the second communication interface exceeds a threshold, deferring processing of the one or more packets associated with the first communication interface.
  • the method further comprises receiving one or more packets associated with the second communication interface; and in response to receiving the one or more packets associated with the second communication interface, inserting a token into a token bucket associated with the second communication interface.
  • determining the quantity of data for processing at the second communication interface comprises determining a number of tokens in the token bucket associated with the second communication interface.
  • the method further comprises processing the one or more packets associated with the second communication interface; and in response to completing processing the one or more packets, removing the token associated with the one or more packets from the token bucket associated with the second communication interface.
  • the method further comprises determining the threshold based, at least in part, on a size of a buffer associated with the second communication interface.
  • receiving the one or more packets associated with the first communication interface comprises receiving the one or more packets for transmission using the first communication interface, and further comprises determining that a priority associated with the one or more packets is included in a subset of a plurality of packet transmission priorities; and in response to determining that the priority associated with the one or more packets is included in the subset of the plurality of packet transmission priorities, transmitting the packets using the first communication interface regardless of the quantity of data for processing associated with the second communication interface.
  • a device comprises a first communication interface to send and receive packets; a second communication interface; a packet processor for the first interface, the packet processor configured to determine a quantity of data for processing associated with the second communication interface; and in response to determining the quantity of data for processing associated with the second communication interface exceeds a threshold, defer processing one or more packets associated with the first communication interface.
  • the device further comprises an interrupt service routine for the second communication interface, the interrupt service routine configured to, in response to reception of one or more packets associated with the second communication interface, insert a token into a token bucket associated with the second communication interface.
  • the determination of the quantity of data for processing at the second communication interface comprises a determination of a number of tokens in the token bucket associated with the second communication interface.
  • the device further comprises a second packet processor to process the one or more packets associated with the second communication interface, the second packet processor configured to, in response to completing processing the one or more packets, remove the token from the token bucket associated with the second communication interface.
  • the threshold is determined, based, at least in part, on a size of a buffer associated with the second communication interface.
  • the communication interface comprise one or more packets for transmission using the first communication interface
  • the packet processor is further configured to determine that a priority associated with the one or more packets is included in a subset of a plurality of packet transmission priorities; and in response to the determination that the priority associated with the one or more packets is included in the subset of the plurality of packet transmission priorities, transmit the one or more packets using the first communication interface regardless of the quantity of data for processing associated with the second communication interface.
  • the first communication interface comprises a wireless networking interface and the second communication interface comprises a Subscriber Line Interface Circuit (SLIC).
  • SLIC Subscriber Line Interface Circuit
  • one or more machine-readable media having stored thereon machine executable instructions, which when executed by a processor causes the processor to perform operations that comprise receiving one or more packets associated with a first communication interface; determining a quantity of data for processing associated with a second communication interface; and in response to determining that the quantity of data for processing associated with the second communication interface exceeds a threshold, deferring processing of the one or more packets associated with the first communication interface.
  • the operations further comprise receiving one or more data packets associated with the second communication interface; and in response to receiving the one or more packets associated with the second communication interface, inserting a token into a token bucket associated with the second communication interface.
  • determining the quantity of data for processing at the second communication interface comprises determining a number of tokens in the token bucket associated with the second communication interface.
  • the operations further comprise processing the one or more packets associated with the second communication interface; and in response to completing processing the one or more packets, removing the token from the token bucket associated with the second communication interface.
  • the operations further comprise determining the threshold based, at least in part, on a size of a buffer associated with the second communication interface.
  • receiving the one or more packets associated with the first communication interface comprises receiving the one or more packets for transmission using the first communication interface, and the operations further comprise determining that a priority associated with the one or more packets is included in a subset of a plurality of packet transmission priorities; and in response to determining that the priority associated with the one or more packets is included in the subset of the plurality of packet transmission priorities, transmitting the one or more packets using the first communication interface regardless of the quantity of data for processing associated with the second communication interface.
  • a system comprises means for receiving one or more packets associated with a first communication interface; means for determining a quantity of data for processing associated with a second communication interface; and means for, in response to determining that the quantity of data for processing associated with the second communication interface exceeds a threshold, deferring processing of the one or more packets associated with the first communication interface.
  • the term "based on” is used in the specification and claims to describe one or more factors that affect a determination. This term does not foreclose additional factors that may affect a determination. That is, a determination may be solely based on those factors or based, at least in part, on those factors.
  • a determination may be solely based on those factors or based, at least in part, on those factors.
  • Figure 1 is a block diagram depicting components of a gateway system according to embodiments.
  • Figure 2 is a block diagram illustrating components of a communication coordination component according to embodiments.
  • Figure 3 is a flow chart illustrating a method for receiving data according to embodiments.
  • Figure 4 is a flow chart illustrating a method for coordinating processing of network data according to embodiments.
  • Figure 5 is a block diagram illustrating components of a communication coordination component according to alternative embodiments.
  • the embodiments coordinate VoIP processing with network processing for a wireless or wired network.
  • the embodiments defer processing associated with wireless or wired network tasks if the quantity of VoIP data to be processed exceeds a threshold quantity.
  • FIG. 1 is a block diagram depicting components of a system 100 according to some embodiments, wherein system 100 comprises a gateway system 102 that provides an interface between a telephone handset and a VoIP communication system.
  • Gateway system 102 includes at least one processor 104, a telephone interface 106, and either or both a wireless network interface 108 and a wired network interface 1 10.
  • Gateway 102 further includes communication coordination tasks 120 executed by processor 104 from memory 1 14 to coordinate processing between tasks associated with VoIP processing and tasks associated with processing data received at a wireless network interface 108 or wired network interface 1 10.
  • processor 104 is a single core processor having a RISC (Reduced Instruction Set Computing) architecture.
  • RISC Reduced Instruction Set Computing
  • RISC Complex Instruction Set Computing
  • single core processors e.g., a multi-core processor
  • system having a single processor e.g., an architecture including multiple CPUs for parallel or concurrent processing
  • Telephone interface 106 provides an interface between a telephone handset 1 12 and gateway system 102.
  • Telephone handset 1 12 may be an analog telephone handset or digital telephone handset configured to connect to a plain old telephone service (POTS), e.g., using a cable having a connector such as 6P2C, 6P4C, 6P6C, 8P4C, etc. formats for coupling to a registered jack (RJ, e.g., RJ1 1 , RJ12, RJ31X, etc.) of the telephone interface 106.
  • POTS plain old telephone service
  • RJ registered jack
  • telephone interface 106 is a Subscriber Line Interface Circuit (SLIC).
  • Telephone interface 106 may be configured to provide ring generation, on/off hook detection, analog to digital conversion (ADC) and digital to analog (DAC) conversion.
  • Telephone interface 106 may implement PCM (pulse code modulation) and Serial Peripheral Interface (SPI) as interface methods between telephone handset 1 12 and processor 104.
  • PCM pulse code modulation
  • Wireless network interface 108 may implement any of a variety of wireless network interfaces allowing gateway system 102 to communicate with peer wireless network devices.
  • wireless network interface 108 may be a WLAN interface, a BLUETOOTH® (Bluetooth) interface, a WiMAX interface, a ZigBee® interface, a Wireless USB interface, etc.
  • Wired network interface 1 when present, may be any type of wired interface communicably coupling gateway system 102 to a WAN (Wide Area Network).
  • wired network interface may be an Ethernet interface or a powerline communication network interface.
  • wired network interface 1 10 may implement a RGMII (Reduced Gigabit Media Independent Interface).
  • Coordinated communication tasks 120 are a set of tasks used to process data that is received or transmitted over the various interfaces provided by gateway system 102 (e.g., telephone interface 106, wireless network interface 108 and wired network interface 1 10), wherein the tasks may include methods of coordinating processing between some or all of the tasks. Further details on a set of coordinated communication tasks 120 according to
  • a task or tasklet may be a process, thread, subroutine, function or other unit of executable code that can be scheduled for execution on one or more processors (e.g., processor 104).
  • a task or tasklet may be embodied in firmware or in one or more embedded circuits.
  • a task or tasklet may be embodied as one or a combination of some or all of executable code, firmware and embedded circuits.
  • Tasks, tasklets, and routines are described below as executing, handling, and processing information, interrupts, etc., meaning that, in some embodiments, one or more processors of a device execute the tasks so that the device takes the action(s) described below.
  • firmware and/or software may be executed and/or an embedded circuit activated for the device to take the below described actions.
  • FIG. 2 is a block diagram illustrating coordinated communication components 200 according to embodiments.
  • coordinated communication components 200 include telephone interface ISR (Interrupt Service Routine) 202, VoIP task 204, VoIP call control task 206, wireless interface ISR 208, and wireless tasklet 210.
  • ISR Interrupt Service Routine
  • Telephone interface ISR 202 handles transmit and receive interrupts related to transmitting or receiving data via the telephone interface.
  • telephone interface ISR 202 is periodically triggered and moves voice frames between memory accessible by processor 104 and telephone interface 106.
  • the period for triggering an interrupt may be 10ms, in alternative embodiments, the period may be 20ms.
  • a transmit interrupt may be triggered when 10ms or 20ms of voice data frames are to be transmitted to telephone interface 106.
  • a receive interrupt may be triggered when 10ms or 20ms of voice data frames are received from telephone interface 106.
  • Telephone ISR 202 generally moves data to and from transmit and receive queues, and then schedules VoIP task 204 to process the data.
  • VoIP task 204 may be scheduled by telephone ISR 202 and processes data after it is received from telephone interface 106 or before transmission to telephone interface 106.
  • VoIP task 204 includes instructions or logic for various processing for data on transmit or receive queues associated with telephone interface 106. Such processing may include voice encoding, voice decoding, echo cancellation, tone generation and detection, jitter buffer processing, sample rate conversion, filtering data and mixing data.
  • the frequency at which VoIP task 204 runs can have an impact on call quality.
  • VoIP task 204 may be scheduled to run every 10ms or 20ms in order to provide desirable end-to-end latency.
  • VoIP call control task 206 is for handling call setup and teardown.
  • VoIP call control task 206 is event driven and typically does not have a stringent real-time processing requirement. Examples of events handled by execution of VoIP call control task 206 are phone off-hook events, session initiation events, phone on-hook transitions etc.
  • VoIP call control task 206 is used to implement Session Initiation Protocol (SIP) to start and end sessions and provide other session control functions.
  • SIP Session Initiation Protocol
  • Wireless interface ISR 208 is invoked when one or more wireless data frames are transmitted or received.
  • wireless interface ISR 208 performs minimal processing of the data, for example setting and clearing registers indicating the location and status of data transmitted or received via wireless interface 108.
  • Wireless tasklet 210 processes the data received via wireless network interface 108. For example, wireless tasklet 210 may process header information in received packets to determine a destination application to receive the data. Wireless tasklet 210 may also encrypt or decrypt data in packets transmitted or received, respectively, via wireless interface 108. The processing performed by wireless tasklet 210 may be processor intensive. Further, the processing performed by wireless tasklet 210 is dependent on the quantity of data transmitted or received through wireless interface 106; the more data that is transmitted/received, the more processor time consumed by wireless tasklet 210.
  • wireless tasklet 210 may maintain multiple transmit queues.
  • transmit queues may be assigned a priority. For example, four priorities may be assigned for data: Voice (VO), Video (VI), Best Effort (BE), and Background (BK) in descending priority.
  • a transmit queue may be maintained for each priority level.
  • Wireless tasklet 210 may insert data into a transmit queue based on the priority associated with the data, and wireless interface ISR 208 may select data for transmission based on the priority associated with a queue.
  • coordination data 220 is maintained by telephone interface ISR 202 and VoIP task 204.
  • VoIP coordination data 220 is monitored by wireless tasklet 210, which defers processing of wireless network data in the transmit and receive queues associated with a wireless interface if the quantity of data to be processed by VoIP task 204 exceeds a threshold quantity.
  • VoIP coordination data 220 is implemented as a token bucket. As voice data is received by telephone interface ISR 202, tokens 222 are added to the token bucket. As voice data is processed by VoIP task 204, tokens 222 are removed from the token bucket.
  • Wireless tasklet 210 monitors the VoIP token bucket and if the number of tokens in the VoIP token bucket exceeds a threshold quantity, wireless tasklet 210 defers processing, thereby allowing VoIP task 204 to use processor time to process voice data received for the telephone interface. Further details on operations performed by the above-described system are provided below with respect to Figures 3 and 4.
  • Figure 3 is a flow chart illustrating a method 300 for receiving data according to embodiments.
  • Method 300 begins at block 302 with receiving one or more packets associated with a communication interface.
  • the received data may be voice frames received via a telephone interface 106.
  • a token is inserted into a token bucket associated with the communication interface.
  • the token may represent a particular quantity of data. The quantity may be expressed in terms of bytes or in terms of time (e.g., 10ms, 20ms etc.)
  • telephone interface ISR 202 inserts a token into a token bucket associated with telephone interface 106 upon determining that transmission of data from telephone interface 106 has completed.
  • the packets received at block 302 are processed.
  • a VoIP task 204 may process the received data.
  • Such processing can include voice encoding, voice decoding, echo cancellation, tone generation and detection, jitter buffer processing, sample rate conversion, filtering data and mixing data.
  • a token associated with the data is removed from the token bucket.
  • VoIP task 204 may remove a token associated with the data processed by VoIP task 204.
  • Figure 4 is a flow chart illustrating a method 400 for coordinating processing of data received for various communication interfaces according to embodiments.
  • the method discussed above in Figure 3 describes operations that may be performed by a communication interface such as a VoIP interface that transmits or receives voice frames via a telephone interface.
  • Figure 4 describes operations that are performed by a first communication interface (e.g., a wireless interface) where the method coordinates processing with a second interface (e.g., a VoIP interface) based on the amount of data to be processed by the "second interface.
  • a first communication interface e.g., a wireless interface
  • a second interface e.g., a VoIP interface
  • first and second interfaces may be other types of interfaces and are not limited to wireless interfaces or VoIP interfaces.
  • Method 400 begins at block 402 with receiving packets associated with a first communication interface.
  • the first communication interface may be a wireless network interface 108.
  • the packets may be received from an application for transmission via the first communication interface or the packets may be received at the first communication interface for delivery to an application.
  • a packet processing task determines a quantity of data to be processed associated with a second communication interface.
  • a wireless tasklet 210 may determine a quantity of data associated with a telephone interface 106.
  • the quantity of data may be determined in terms of bytes or in terms of time (e.g., 10ms, 20ms etc.) In some
  • the quantity of data is represented by tokens, where each token represent a quantity of data.
  • a packet processing task such as wireless tasklet 210 may monitor a token bucket associated with a telephone interface 106.
  • the threshold quantity may be a predetermined or configurable quantity. In some embodiments, the threshold quantity may be determined based, at least in part, on the buffer capability of the second communication interface. As an example, if the second communication interface is a VoIP interface having a buffer capable of buffering 30ms of data, and if data is inserted at 10ms intervals, then the threshold may be configured to be 20ms of data. Thus, if each token represents 10ms of data, then the threshold may be set at two tokens.
  • the packet processing task proceeds to process the data associated with the first communication interface.
  • the packet processing task defers processing packets associated with the first communication interface. Such deferral can allow packets associated with the second communication interface to be processed. After processing of packets associated with the first communication interface has been deferred, the method may return to block 404 to determine whether the quantity of data to be processed at the second communication interface is still above the threshold quantity . In some implementations, this may be accomplished by rescheduling the packet processing task associated with the first communication interface.
  • the wireless tasklet 210 determines if there are any tokens in the VoIP token bucket. If the number of tokens in the token bucket exceeds the predetermined or configurable threshold, the wireless tasklet 210 defers processing of transmit or receive queues containing data associated with wireless network interface 108. The deferral allows the VoIP task 204 to utilize available processor cycles to process VoIP data, thereby avoiding reduced call quality or dropped calls that could result if the VoIP task 204 cannot process data in a timely manner.
  • the processing at block 410 includes examining the token bucket when wireless packets received via wireless interface 108 are available for processing and when packets are submitted for transmission via wireless interface 108.
  • the token bucket is examined when packets received via wireless interface 108 are available for processing.
  • the token bucket may not be examined if the packets to be transmitted have a priority that indicates the packet is to be transmitted immediately. For example, as noted above, some wireless implementations support four priorities for packet transmission: Voice (VO), Video (VI), Best Effort (BE), and Background (BK) in descending priority.
  • VO packets are transmitted regardless of the number of tokens in the token bucket or quantity of data to be processed by VoIP task 204.
  • VO and VI packets are transmitted regardless of the number of tokens in the token bucket or quantity of data to be processed by VoIP task 204.
  • BE and BK packets are processed if the number of tokens in the token bucket or quantity of data to be processed by VoIP task 204 are below the threshold.
  • wireless task 210 is subdivided into two tasks, a transmit task and a receive task.
  • the receive task is gated as described in Figure 4 and defers processing wireless data packets if the quantity of data associated with the telephone interface is above a threshold quantity. Such deferral occurs without regard to the priority of the packet.
  • the transmit task defers processing packets to be transmitted over wireless interface 108 when the packets have a lower priority (e.g., BE and BK priorities) and if the quantity of data associated with the telephone interface is above a threshold quantity. However, for higher priority packets (e.g., VI or VO priorities), the transmit task does not defer processing and may not perform any checks regarding whether the quantity of data associated with the telephone interface is above a threshold quantity.
  • ISRs e.g., telephone interrupt ISR 202 or wireless interface ISR 208
  • ISRs may be triggered during the execution of operations associated with other components, such as VoIP task 204 or wireless tasklet 210.
  • FIG. 5 is a block diagram illustrating components 500 of communication coordination tasks according to alternative embodiments.
  • a gateway system 102 may include multiple network interfaces (e.g., both a wireless interface 108 and a wired network interface 1 10).
  • communication coordination tasks include, in addition to the tasks illustrated in Figure 2, a WAN (Wide Area Network) interface ISR 502, a WAN tasklet 504 and WAN coordination data 520.
  • WAN Wide Area Network
  • WAN interface ISR 502 executes when one or more Ethernet data frames are transmitted or received. Typically, WAN interface ISR 502 performs minimal processing of the data, for example setting and clearing registers indicating the location and status of data transmitted or received via wired network interface 1 10.
  • WAN tasklet 504 processes the data received via wireless network interface 108. For example, WAN tasklet 504 may process header information in received packets to determine a destination application to receive the data. WAN tasklet 504 may also encrypt or decrypt data in packets received of transmitted via wired network interface 1 10.
  • WAN coordination data 520 like VoIP coordination data 220, comprises data that indicates a quantity of data to be processed by WAN tasklet 504, which may be expressed in terms of bytes.
  • WAN coordination data 520 may comprise a WAN coordination bucket, where tokens 522 represent the quantity of data to be processed by WAN tasklet 504. For example, a token may represent a particular amount of data or a particular number of packets.
  • wireless tasklet 210 in addition to monitoring VoIP coordination data 220, also monitors WAN coordination data 520. If either of VoIP coordination data 220 or WAN coordination data 520 indicates that the data to be processed exceeds a threshold quantity, wireless tasklet 210 may defer processing of wireless packets, thereby allowing VoIP task 204 or WAN tasklet 504 the opportunity to process packets.
  • WAN tasklet 504 monitors VoIP coordination data 220. If the VoIP coordination data 520 indicates that the quantity of data to be processed by VoIP task 204 exceeds a threshold quantity, then processing of packets by WAN tasklet 504 is deferred. [0066] Further details on system 100 of Figure 1 will now be provided.
  • An electronic device such as gateway system 102 includes a processor 104 (possibly including multiple processors, multiple cores, multiple nodes, and/or implementing multi-threading, etc.). In some
  • the electronic device may be implemented at least in part as a system on a chip (SOC).
  • the electronic device includes memory 1 14.
  • the memoryl 14 may be system memory (e.g., one or more of cache, SRAM, DRAM, zero capacitor RAM, Twin Transistor RAM, eDRAM, EDO RAM, DDR RAM, EEPROM, NRAM, RRAM, SONOS, PRAM, etc.) or any one or more of the above already described possible realizations of machine-readable media.
  • the electronic device also includes a bus l 16 (e.g., PCI, ISA, PCI-Express, HyperTransport®, InfiniBand®, NuBus, etc.), and one or more network interfaces (e.g., wired network interface 1 10 and wireless network interface 108).
  • Wired network interface 1 10 may be any type of wired network interface, including an ATM interface, an Ethernet interface, a Frame Relay interface, SONET interface, etc.).
  • system 100 may include a storage device(s)(not shown). Examples of such storage devices include optical storage, magnetic storage, etc.
  • the system memory 1 14 embodies functionality to implement embodiments described above.
  • the system memory 1 14 may include one or more communication coordination tasksl20.
  • any one of these functionalities may be partially (or entirely) implemented in hardware and/or on the processor 104.
  • the functionality may be implemented with an application specific integrated circuit, in logic implemented in the processor 104, in a co-processor on a peripheral device or card, etc.
  • realizations may include fewer or additional components not illustrated in Figure 1 (e.g., video cards, audio cards, additional network interfaces, peripheral devices, etc.).
  • the processor 104, the storage device(s), and the network interfaces are coupled to the bus l 16.
  • the memoryl 14 may be coupled to the processor unitl 04.
  • Embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit,” “module” or “system.”
  • embodiments of the inventive subject matter may take the form of a computer program product embodied in any tangible medium of expression having computer usable program code embodied in the medium.
  • the described embodiments may be provided as a computer program product, or software, that may include a machine -readable medium having stored thereon instructions, which may be used to program a computer system (or other electronic device(s)) to perform a process according to embodiments, whether presently described or not, since every conceivable variation is not enumerated herein.
  • a machine readable medium includes any mechanism for storing or transmitting information in a form (e.g., software, processing application) readable by a machine (e.g., a computer).
  • the machine-readable medium may include, but is not limited to, magnetic storage medium (e.g., floppy diskette); optical storage medium (e.g., CD-ROM); magneto-optical storage medium; read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; or other types of medium suitable for storing electronic instructions.
  • embodiments may be embodied in an electrical, optical, acoustical or other form of propagated signal (e.g., carrier waves, infrared signals, digital signals, etc.), or wireline, wireless, or other communication medium.
  • Computer program code for carrying out operations of the embodiments may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages.
  • the program code may execute entirely on a user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN), a personal area network (PAN), or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • PAN personal area network
  • WAN wide area network
  • Internet Service Provider an Internet Service Provider

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne des dispositifs, des procédés et des supports lisibles par machine qui coordonnent le traitement VoIP et le traitement réseau pour un réseau sans fil ou filaire. Dans certains modes de réalisation, un traitement associé à des tâches de réseau filaire ou sans fil est différé si la quantité de données VoIP à traiter dépasse une quantité seuil.
PCT/CN2013/078869 2013-07-05 2013-07-05 Coordination de traitement de voip et de traitement de réseau sans fil WO2015000169A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/078869 WO2015000169A1 (fr) 2013-07-05 2013-07-05 Coordination de traitement de voip et de traitement de réseau sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/078869 WO2015000169A1 (fr) 2013-07-05 2013-07-05 Coordination de traitement de voip et de traitement de réseau sans fil

Publications (1)

Publication Number Publication Date
WO2015000169A1 true WO2015000169A1 (fr) 2015-01-08

Family

ID=52143038

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/078869 WO2015000169A1 (fr) 2013-07-05 2013-07-05 Coordination de traitement de voip et de traitement de réseau sans fil

Country Status (1)

Country Link
WO (1) WO2015000169A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001008426A2 (fr) * 1999-07-23 2001-02-01 Telefonaktiebolaget Lm Ericsson (Publ) Multiplexages d'utilisateurs en temps reeel et d'utilisateurs non prioritaires sur une voie egprs
CN101610161A (zh) * 2008-06-17 2009-12-23 爱动摩杰（北京）科技有限公司 一种在网络会议中音频传输实时性的保证方法
CN102970757A (zh) * 2012-11-23 2013-03-13 南京邮电大学 基于实时业务的lte下行填充资源分配方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001008426A2 (fr) * 1999-07-23 2001-02-01 Telefonaktiebolaget Lm Ericsson (Publ) Multiplexages d'utilisateurs en temps reeel et d'utilisateurs non prioritaires sur une voie egprs
CN101610161A (zh) * 2008-06-17 2009-12-23 爱动摩杰（北京）科技有限公司 一种在网络会议中音频传输实时性的保证方法
CN102970757A (zh) * 2012-11-23 2013-03-13 南京邮电大学 基于实时业务的lte下行填充资源分配方法

Similar Documents

Publication Publication Date Title
US10635630B2 (en) Flexible protocol and associated hardware for one-wire radio frequency front-end interface
US10489223B2 (en) Methods and apparatus for scheduling time sensitive operations among independent processors
CN101867511B (zh) 流控帧发送方法、相关设备及系统
EP1137226B1 (fr) Amélioration de l'ordonnancement de paquets véhivulant des informations en temps réel sur un réseau par paquets
US7519076B2 (en) Method and node for using a communication network in parallel for real-time applications and non-real-time applications
CN102893566B (zh) 用于实现非阻塞式基于优先级流控的方法和装置
KR20180092969A (ko) 메시징을 위한 최적의 레이턴시 패킷화기 유한 상태 머신 및 입력/출력 트랜스퍼 인터페이스들
CN106850565A (zh) 一种高速的网络数据传输方法
US20150326698A1 (en) Network timeouts using intentionally delayed transmissions
US20220321493A1 (en) Method for transmitting data packet and apparatus for implementing the same
CN110247942A (zh) 一种数据发送方法、装置和可读介质
CN109388597A (zh) 一种基于fpga的数据交互方法及装置
WO2018132436A1 (fr) Compression forcée d'écritures i2c uniques
US9413672B2 (en) Flow control for network packets from applications in electronic devices
WO2017062218A1 (fr) Communication d'accusé de réception de données sans fil utilisant une agrégation de trames
WO2015000169A1 (fr) Coordination de traitement de voip et de traitement de réseau sans fil
CN105119788A (zh) 以太网网口系统及其网络环境自适应方法、以太网设备
CN105337888B (zh) 基于多核转发的负载均衡方法、装置及虚拟交换机
CN110505607B (zh) 基于蓝牙安全设备的通信方法、蓝牙芯片及蓝牙安全设备
Runge et al. Low latency network traffic processing with commodity hardware
CN109729014A (zh) 一种报文存储方法和装置
CN104796994B (zh) 无线通信系统的资源调度方法
CN111385219B (zh) 借用硬件中断实现高性能高精度软件tcp限速的方法
CN115022245A (zh) 一种数据传输的方法、相关装置、设备以及存储介质
CN112910709A (zh) 一种业务质量的确定方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13888834

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13888834

Country of ref document: EP

Kind code of ref document: A1