Dismiss
InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Showing 1 - 10 of 436 from April 2010
Browse Prior Art Database
  1. 1.
    L'invention propose un boitier de réception recevant le dispositif électronique à fixer (par exemple FoMoCo, SRx, Indy2, Récepteur_TPMS, ...) à l'extérieur du véhicule. Bien sûr, ce boitier est étanche. Il reçoit via un connecteur standard le dispositif électronique à fixer (par exemple un Récepteur_TPMS). Un...
    IPCOM000195351D | 2010-Apr-30
  2. 2.
    In the past few years, there has been a rapid adoption of the Session Initiation Protocol (SIP) [1] and deployment of SIP-based communications networks. This has often outpaced the development and implementation of protocol specifications to meet network operator requirements. This has led to the development of...
    IPCOM000195350D | Original Publication Date: 2010-Apr-01
  3. 3.
    The Session Traversal Utilities for NAT (STUN)[RFC5389] protocol defines two different hashes that may be included in messages exchanged by peers implementing that protocol:
    IPCOM000195349D | Original Publication Date: 2010-Apr-01
  4. 4.
    RFC 3264 [RFC3264] defines a two-phase exchange of Session Description Protocol (SDP) [RFC4566] messages for the purposes of establishment of multimedia sessions. This offer/answer mechanism is used by protocols such as the Session Initiation Protocol (SIP) [RFC3261].
    IPCOM000195348D | Original Publication Date: 2010-Apr-01
  5. 5.
    [RFC3323] defines a privacy mechanism for the Session Initiation Protocol (SIP) [RFC3261], based on techniques available at the time of its publication. This mechanism relies on the use of a separate privacy service to remove privacy-sensitive information from SIP messages sent by a User Agent (UA) before forwarding...
    IPCOM000195347D | Original Publication Date: 2010-Apr-01
  6. 6.
    A host behind a NAT may wish to exchange packets with other hosts, some of which may also be behind NATs. To do this, the hosts involved can use "hole punching" techniques (see [RFC5128]) in an attempt discover a direct communication path; that is, a communication path that goes from one host to another through...
    IPCOM000195346D | Original Publication Date: 2010-Apr-01
  7. 7.
    The Real-time Transport Protocol (RTP) [1] is widely used in video streaming, telephony, and other real-time networked applications. RTP can run over a range of lower-layer transport protocols, and the performance of an application using RTP is heavily influenced by the choice of lower-layer transport. The Datagram...
    IPCOM000195345D | Original Publication Date: 2010-Apr-01
  8. 8.
    The Real-time Transport Protocol (RTP) [1] comprises two components: a data transfer protocol and an associated control protocol (RTCP). Historically, RTP and RTCP have been run on separate UDP ports. With increased use of Network Address Port Translation (NAPT) [14], this has become problematic, since maintaining...
    IPCOM000195344D | Original Publication Date: 2010-Apr-01
  9. 9.
    RFC 3264 [RFC3264] defines a two-phase exchange of Session Description Protocol (SDP) messages [RFC4566] for the purposes of establishment of multimedia sessions. This offer/answer mechanism is used by protocols such as the Session Initiation Protocol (SIP) [RFC3261].
    IPCOM000195343D | Original Publication Date: 2010-Apr-01
  10. 10.
    L'invention consiste à donner la possibilité aux unités roues de réveiller les récepteurs (unité centrale ou leur antennes) des véhicules environnants endormis afin que ceux-ci communiquent la configuration (n° des identifiants monté sur le véhicule environnant ainsi que position (localisation) des unités roues...
    IPCOM000195342D | 2010-Apr-30