US20170142025A1 - Bi-directional and reverse directional resource reservation setup protocol - Google Patents

Bi-directional and reverse directional resource reservation setup protocol Download PDF

Info

Publication number
US20170142025A1
US20170142025A1 US15/419,561 US201715419561A US2017142025A1 US 20170142025 A1 US20170142025 A1 US 20170142025A1 US 201715419561 A US201715419561 A US 201715419561A US 2017142025 A1 US2017142025 A1 US 2017142025A1
Authority
US
United States
Prior art keywords
router
resources
message
reserved
user
Prior art date
Legal status (The legal status 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 status listed.)
Abandoned
Application number
US15/419,561
Inventor
Kamel M. Shaheen
Sharif M. Shahrier
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Technology Corp
Original Assignee
InterDigital Technology Corp
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
Priority to US33630401P priority Critical
Priority to US10/288,065 priority patent/US7400582B2/en
Priority to US12/170,825 priority patent/US8085664B2/en
Priority to US13/312,021 priority patent/US8630176B2/en
Priority to US14/138,767 priority patent/US9030933B2/en
Priority to US14/708,988 priority patent/US9560641B2/en
Application filed by InterDigital Technology Corp filed Critical InterDigital Technology Corp
Priority to US15/419,561 priority patent/US20170142025A1/en
Publication of US20170142025A1 publication Critical patent/US20170142025A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/70Admission control or resource allocation
    • H04L47/72Reservation actions
    • H04L47/724Reservation actions involving intermediate nodes, e.g. RSVP
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00
    • H04L29/02Communication control; Communication processing
    • H04L29/06Communication control; Communication processing characterised by a protocol
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/14Flow control or congestion control in wireless networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/70Admission control or resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/70Admission control or resource allocation
    • H04L47/82Miscellaneous aspects
    • H04L47/824Applicable to portable or mobile terminals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048Allocation of pilot signals, i.e. of signals known to the receiver
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements or protocols for real-time communications
    • H04L65/10Signalling, control or architecture
    • H04L65/1066Session control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/16Transmission control protocol/internet protocol [TCP/IP] or user datagram protocol [UDP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/16Transmission control protocol/internet protocol [TCP/IP] or user datagram protocol [UDP]
    • H04L69/161Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/22Header parsing or analysis
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/26Special purpose or proprietary protocols or architectures
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic or resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic or resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/26Resource reservation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management, e.g. wireless traffic scheduling or selection or allocation of wireless resources
    • H04W72/04Wireless resource allocation
    • H04W72/0406Wireless resource allocation involving control information exchange between nodes
    • H04W72/0413Wireless resource allocation involving control information exchange between nodes in uplink direction of a wireless link, i.e. towards network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management, e.g. wireless traffic scheduling or selection or allocation of wireless resources
    • H04W72/04Wireless resource allocation
    • H04W72/0406Wireless resource allocation involving control information exchange between nodes
    • H04W72/042Wireless resource allocation involving control information exchange between nodes in downlink direction of a wireless link, i.e. towards terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H04W80/045Network layer protocols, e.g. mobile IP [Internet Protocol] involving different protocol versions, e.g. MIPv4 and MIPv6
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management, e.g. wireless traffic scheduling or selection or allocation of wireless resources
    • H04W72/04Wireless resource allocation
    • H04W72/0406Wireless resource allocation involving control information exchange between nodes

Abstract

A method, system and apparatus for resource reservation are disclosed herein. In an example, a first router may transmit, to a second router, a path message comprising an indication of resources to be reserved and a bidirectional direction indicator. On a condition that the indicated resources to be reserved are available to the second router, the first router may receive, from the second router, a reserve message, which may indicate that transmission resources have been allocated by the second router. On a condition that the indicated resources to be reserved are not available to the second router, first router may receive, from the second router, an error message, which may indicate that transmission resources have not been allocated. In a further example, the resources to be reserved may be resources associated with voice traffic, video traffic or both. Voice traffic may include multiple party communications involving three or more users.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation of U.S. patent application Ser. No. 14/708,988 filed May 11, 2015, which is a continuation of U.S. patent application Ser. No. 14/138,767 filed Dec. 23, 2013, which issued as U.S. Pat. No. 9,030,933 on May 12, 2015, which is a continuation of U.S. patent application Ser. No. 13/312,021 filed Dec. 6, 2011, which issued as U.S. Pat. No. 8,630,176 on Jan. 14, 2014, which is a continuation of U.S. patent application Ser. No. 12/170,825 filed Jul. 10, 2008, which issued as U.S. Pat. No. 8,085,664 on Dec. 27, 2011, which is a continuation of U.S. patent application Ser. No. 10/288,065 filed Nov. 4, 2002, which issued as U.S. Pat. No. 7,400,582 on Jul. 15, 2008, which claims the benefit of U.S. Provisional Application Ser. No. 60/336,304 filed Nov. 2, 2001, the contents of which are hereby incorporated by reference herein.
  • FIELD OF INVENTION
  • The present invention relates to wireless packet based communications. In particular, the invention relates to establishing wireless packet based communications.
  • BACKGROUND
  • For certain Internet applications, resources are reserved to achieve the necessary quality of service (QOS). The reservation of resources allows packet based networks to operate like circuit switched networks. FIG. 1 is an illustration of a simplified wireless packet based, such as Internet based, communication session, such as for wireless Internet, wireless multimedia, voice over Internet Protocol, video conferencing or video telephony, between two wireless users, user A and user B. Differing sessions have differing performance requirements, such as setup time, delay, reliability, integrity and quality of service (QOS). User A is shown as user equipment (UE) 20 and user B is shown as UE 22. User A sends and receives communicates via the packet network 28 using its cellular network 24. User B similarly sends and receives communications via the packet network 28 using its cellular network 26.
  • FIG. 2 is an illustration of establishing such a session. User A sends a resource reservation setup protocol (RSVP) PATH message 30 to establish the session. The RSVP PATH message 30 is sent to user B via various network routers (Router 1-Router N). Each router determines whether the resources are available for the session. If adequate resources are available, the RSVP PATH message 30 is updated and passed to the next router. If adequate resources are not available, an error message is sent back to user A. When user B receives the RSVP PATH message 30, user B responds by sending a RSVP reservation (RESV) message 32 to reserve the resources throughout the networks 24, 26, 28. As the RSVP RESV message 32 is sent through the networks, resources are allocated to support the communications from user A to user B. If the resources are successfully allocated, user A receives the RSVP RESV message 32. User A sends a confirmation (RSVP confirm) message 34 to user B to acknowledge receipt of the RSVP RESV message 32.
  • To allocate resources for user B′s communications to user A, user B sends a RSVP PATH message 30 to user A via various network routers (Router 1-Router N). When user A receives the RSVP PATH message 30, user A responds by sending a RSVP RESV message 32 to reserve the resources throughout the networks 24, 26, 28. As the RSVP RESV message 32 is sent through the networks 24, 26, 28, resources are allocated to support the communications from user B to user A. If the resources are successfully allocated, user B receives the RESV message 32. User B sends a RSVP confirm message 34 to user A to acknowledge receipt of the RSVP RESV message 34.
  • To maintain the resource allocations, Refresh PATH messages 36 are periodically sent through the networks 24, 26, 28. User A sends Refresh PATH messages 36 through the networks 24, 26, 28 to user B to maintain the resources for user A′s transmissions and user B sends Refresh PATH messages 36 through the networks 24, 26, 28 to user A to maintain the resources for user B's transmissions. If the Refresh PATH messages 36 are not sent, the reservation states will expire with the allocated resources being released.
  • Sending all these messages to allocate resources uses valuable network resources. Accordingly, it is desirable to have alternate approaches to establishing wireless Internet sessions.
  • SUMMARY
  • A wireless user equipment (UE) configured to initiate a packet based session is disclosed. The UE includes a reservation setup protocol (RSVP) message generator configured to transmit a RSVP PATH message. The RSVP PATH message includes a direction indication. The direction indicator indicates that reservations should be made for the UE to transmit only, to receive only or to both transmit and receive. The UE also includes an RSVP message receiver configured to receive an RSVP RESV message indicating that reservations have been made as a result of the RSVP PATH message.
  • A method, system and apparatus for resource reservation are disclosed herein. In an example, a first router may transmit, to a second router, a path message comprising an indication of resources to be reserved and a bidirectional direction indicator. On a condition that the indicated resources to be reserved are available to the second router, the first router may receive, from the second router, a reserve message. The reserve message may indicate that transmission resources have been allocated by the second router.
  • On a condition that the indicated resources to be reserved are not available to the second router, first router may receive, from the second router, an error message. The error message may indicate that transmission resources have not been allocated.
  • In a further example, the resources to be reserved may be resources associated with voice traffic, video traffic or both. The voice traffic may include multiple party communications involving three or more users. In an example, the first router and the second router may be wired routers. In another example, the path message may include resource allocation information for both communications transmitted from the first router to the second router and from the second router to the first router.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is an illustration of simplified wireless packet based communication system.
  • FIG. 2 is an illustration of establishing a wireless packet session.
  • FIG. 3 is an illustration of establishing a wireless packet session using bi-directional reservation setup protocol.
  • FIG. 4 is an illustration of establishing a wireless packet session using reverse direction reservation setup protocol.
  • FIG. 5 is a simplified illustration of a preferred reservation setup message.
  • FIG. 6 is a simplified illustration of a preferred forward direction reservation setup message.
  • FIG. 7 is a simplified illustration of a preferred reverse direction reservation setup protocol message.
  • FIG. 8 is a simplified illustration of a preferred bi-directional reservation setup protocol message.
  • FIG. 9 is an illustration of a preferred bi-directional reservation setup protocol PATH message.
  • FIG. 10 is an illustration of the SENDER_TSPEC of FIG. 9.
  • FIGS. 11 and 12 are illustrations of the ADSPEC of FIG. 9.
  • FIG. 13 is an illustration of a preferred bi-directional reservation setup protocol reservation message.
  • FIGS. 14 and 15 are illustrations of FLOWSPECs of the bi-directional reservation setup protocol reservation message of FIG. 13.
  • FIG. 16 is a simplified block diagram of a wireless user equipment.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)
  • FIG. 3 is an illustration of bi-directional resource reservation setup protocol. User A desires to setup a bi-directional packet based, such as Internet, session with user B. The requirements, such as bit rate and relative delay, for the session are based on prior negotiations. Both users A and B may be wireless users or one of the two is a wireless user and the other is a wired user. To initiate the session, user A (the originating user) sends a bi-directional RSVP PATH message 38. The bi-directional RSVP PATH message 38 contains resource allocation information for both the communications transmitted from user A to user B and from user B to user A. The preferred format of these communications is discussed in more detail in conjunction with FIGS. 8, 9, 10, 11 and 12. Although the invention is described primarily in conjunction with two-direction communications, the invention is extendable to any multiple party communications, such as three-way calling.
  • The bi-directional RSVP PATH message 38 is send through the various routers (Router 1-Router N) of the networks to user B. User B sends a bi-directional RSVP RESV message 40 to allocate the resources for both users through the networks 24, 26, 28. A preferred bi-directional RSVP RESV message 40 is described in more detail in conjunction with FIGS. 8, 13, 14 and 15. Upon transferring the bi-directional RSVP RESV message 40, each network allocates the resources for both user A's and user B's transmissions. Upon receiving the bi-directional RSVP RESV message 40, indicating that the resources have been successfully allocated, user A sends a bi-directional RSVP confirm message 42 to user B through the networks. Upon receiving the bi-directional RSVP confirm message 42, bi-direction communication between users A and B begins. Preferably, the originating user, user A, is responsible for the session, such as for billing purposes. Making the originating user responsible for the session simplifies billing procedures.
  • To maintain the resource allocations, periodically, bi-directional Refresh PATH messages 44 are sent by user A through the networks to user B. Upon transferring the bi-directional Refresh PATH messages 44, the networks maintain the resource allocations for both directions.
  • Using the bi-directional messages reduces overhead required for the establishment of the session. Instead of both user A and user B sending RSVP PATH 30, RSVP RESV 32 and RSVP confirm 34 messages, only one user sends bi-directional messages. Although the information carried by each of these messages is typically increased, by reducing the number of messages, the overall network overhead is decreased. Additionally, the bi-directional messaging avoids call scenarios, where the resources in one direction are established and the resources in the other direction are not. The reduced overhead lessens the impact on air resources and improves network performance.
  • FIG. 4 is an illustration of reverse resource reservation setup protocol. User A desires to setup an Internet session where only user B transmits information. Both users A and B may be wireless users or one of the two is a wireless user and the other is a wired user. To initiate the session, user A (the originating user) sends a reverse direction RSVP PATH message 46. The reverse direction RSVP PATH message 46 contains resource allocation information for user B's transmissions to user A.
  • The reverse direction RSVP PATH message 46 is sent through the various routers (Router 1-Router N) of the networks to user B. User B sends a reverse direction RSVP RESV message 48 to allocate the resources for its transmission. Upon receiving the reverse direction RSVP RESV message 48, user A sends a reverse direction RSVP confirm message 50 to user B through the networks 24, 26, 28. Upon receiving the reverse direction RSVP confirm message 50, user B begins transferring data to user A. Preferably, user A (although user A is not transmitting any substantive information) is responsible for the session.
  • FIG. 5 is an illustration of a simplified preferred RSVP message, illustrating generically the RSVP PATH, RSVP RESV and RSVP confirm messages. The preferred message has an IP header having a direction indicator, (forward, reverse and bi-directional) and having objects 58 1-58 N. Preferably, the message is based on and is backward compatible with RFC 2205 and the direction indicator is a four bit indicator. For RFC 2205, the four bits of the direction indicator 541 are assigned the value “0000” for the forward direction (the originating user only sends information). A preferred forward direction RSVP message is shown in FIG. 6, with only objects 58 F1-58 FN for the forward direction, “(FORWARD)”, being included. In RFC 2205, each user (each of users A and B) is an originating user. A value “0011” for the direction indicator 542 indicates the reverse direction (the originating user only receives information). A preferred reverse direction RSVP message is shown in FIG. 7. In FIG. 7, all of the objects 58 R1-58 RN are for the reverse direction, “(REVERSE)”. A value “1111” for the direction indicator 54 3 indicates both directions are used (the originating user will receive and send). A preferred bi-directional RSVP message is shown in FIG. 8. In FIG. 8, both “(FORWARD)” 58 F1-58 FN and “(REVERSE)” 58 R1-58 RN objects are present.
  • FIG. 9 is an illustration of a preferred bi-directional RSVP PATH message compatible with RFC 2205. The bi-directional RSVP PATH message has fields for the “<Path Message>”, “<Common Header>”, “<INTEGRITY>”, “<SESSION>”, “<RSVP_HOP>”, “<TIME_VALUES>”, “<POLICY_DATA>”, “<sender description>”, “<sender descriptor>”, “<SENDER_TEMPLATE>”, “<SENDER_TSPEC>” and “<ADSPEC>”.
  • FIG. 10 is an illustration of a “<SENDER_TSPEC>”. Along the top of the figure are numbers indicating the bit positions from bit position 0 to 31. As shown in FIG. 10 for a bi-directional RSVP PATH message, both “(Forward)” and “(Reverse)” information is included.
  • Two illustrations of the “<ADSPEC>” field are shown in FIGS. 11 and 12. FIG. 11 illustrates a PATH Default ADSPEC and FIG. 12 illustrates a PATH Guaranteed Service ADSPEC. As shown in those figures, both ADSPECs contain both forward and reverse information.
  • FIG. 13 is an illustration of a preferred bi-directional RSVP RESV message compatible with RFC 2205. The bi-directional RSVP RESV message has fields for “<Resv Message>”, “<Common Header>”, “<INTEGRITY>”, “<SESSION>”, “<RSVP_HOP>”, “<TIME_VALUES>”, “<RESV_CONFIRM>”, “<SCOPE>”, “<POLICY_DATA>”, “<STYLE>”, “<flow descriptor list>” and “<flow descriptor>”.
  • The direction indicator is included in the “<flow descriptor list>”. Two illustrations of preferred FLOWSPECs of the “<flow descriptor list>” are shown in FIGS. 14 and 15. FIG. 14 is a FLOWSPEC for Guaranteed service and FIG. 15 is a FLOWSPEC for Guaranteed Service Extension Format. As shown in FIGS. 14 and 15 for a bi-directional RSVP RESV message, both forward and reverse direction information is carried by the message.
  • FIG. 16 is a block diagram of a wireless user equipment for use in bi-directional, reverse direction and forward direction reservation setup protocol messaging. An RSVP message generator 72 produces the RSVP PATH messages (including bi-directional RSVP and reverse direction RSVP PATH messages), RSVP RESV messages (including bi-directional RSVP and reverse direction RSVP RESV messages), RSVP Confirm messages (including bi-directional RSVP and reverse direction RSVP Confirm messages) and Refresh PATH messages (including bi-directional and reverse direction Refresh Path messages). An RSVP message receiver 74 is used to receive the various RSVP messages. The messages that the UE transmits or receives is based on the whether the UE is the originating user or non-originating user, as previously described. Session data is transmitted and received using a session data transmitter 76 and a session data receiver 78. An antenna 70 or antenna array are used to radiate and receive the various messages and communications across the air interface.

Claims (21)

What is claimed is:
1. A method for reserving resources in a network, the method comprising:
transmitting, by a router, a path message comprising a bidirectional direction indicator and an indication of resources to be reserved; and
receiving by the router, one of a reserve message or an error message, wherein the reserve message indicates that transmission resources have been allocated and the error message indicates that transmission resources have not been allocated.
2. The method of claim 1, wherein the resources to be reserved are resources associated with voice traffic.
3. The method of claim 1, wherein the resources to be reserved are resources associated with video traffic.
4. The method of claim 2, wherein the voice traffic includes multiple party communications involving three or more users.
5. The method of claim 1, wherein the router is wired router.
6. A method for reserving resources in a network, the method comprising:
transmitting, from a first router to a second router, a path message comprising an indication of resources to be reserved and a bidirectional direction indicator;
on a condition that the indicated resources to be reserved are available to the second router, receiving, by the first router from the second router, a reserve message, wherein the reserve message indicates that transmission resources have been allocated by the second router; and
on a condition that the indicated resources to be reserved are not available to the second router, receiving, by the first router from the second router, an error message, wherein the error message indicates that transmission resources have not been allocated.
7. The method of claim 6, wherein the resources to be reserved are resources associated with voice traffic.
8. The method of claim 6, wherein the resources to be reserved are resources associated with video traffic.
9. The method of claim 7, wherein the voice traffic includes multiple party communications involving three or more users.
10. The method of claim 6, wherein the first router and the second router are wired routers.
11. The method of claim 6, wherein the path message includes resource allocation information for both communications transmitted from the first router to the second router and from the second router to the first router.
12. A method for reserving resources in a network, the method comprising:
receiving, by a router, a path message comprising an indication of resources to be reserved and a bidirectional direction indicator;
on a condition that the indicated resources to be reserved are available to the router, transmitting, by the router, a reserve message, wherein the reserve message indicates that transmission resources have been allocated by the router; and
on a condition that the indicated resources to be reserved are not available to the router, transmitting, by the router, an error message, wherein the error message indicates that transmission resources have not been allocated.
13. The method of claim 12, wherein the resources to be reserved are resources associated with voice traffic.
14. The method of claim 12, wherein the resources to be reserved are resources associated with video traffic.
15. The method of claim 13, wherein the voice traffic includes multiple party communications involving three or more users.
16. The method of claim 12, wherein the router is wired router.
17. A router comprising:
a transmitter, operatively coupled to a processor, the transmitter and the processor configured to transmit a path message comprising a bidirectional direction indicator and an indication of resources to be reserved; and
a receiver, operatively coupled to a processor, the receiver and the processor configured to receive one of a reserve message or an error message, wherein the reserve message indicates that transmission resources have been allocated and the error message indicates that transmission resources have not been allocated.
18. The router of claim 17, wherein the resources to be reserved are resources associated with voice traffic.
19. The router of claim 17, wherein the resources to be reserved are resources associated with video traffic.
20. The router of claim 18, wherein the voice traffic includes multiple party communications involving three or more users.
21. The router of claim 17, wherein the router is wired router.
US15/419,561 2001-11-02 2017-01-30 Bi-directional and reverse directional resource reservation setup protocol Abandoned US20170142025A1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
US33630401P true 2001-11-02 2001-11-02
US10/288,065 US7400582B2 (en) 2001-11-02 2002-11-04 Bi-directional and reverse directional resource reservation setup protocol
US12/170,825 US8085664B2 (en) 2001-11-02 2008-07-10 Bi-directional and reverse directional resource reservation setup protocol
US13/312,021 US8630176B2 (en) 2001-11-02 2011-12-06 Bi-directional and reverse directional resource reservation setup protocol
US14/138,767 US9030933B2 (en) 2001-11-02 2013-12-23 Bi-directional and reverse directional resource reservation setup protocol
US14/708,988 US9560641B2 (en) 2001-11-02 2015-05-11 Bi-directional and reverse directional resource reservation setup protocol
US15/419,561 US20170142025A1 (en) 2001-11-02 2017-01-30 Bi-directional and reverse directional resource reservation setup protocol

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US15/419,561 US20170142025A1 (en) 2001-11-02 2017-01-30 Bi-directional and reverse directional resource reservation setup protocol

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US14/708,988 Continuation US9560641B2 (en) 2001-11-02 2015-05-11 Bi-directional and reverse directional resource reservation setup protocol

Publications (1)

Publication Number Publication Date
US20170142025A1 true US20170142025A1 (en) 2017-05-18

Family

ID=23315481

Family Applications (6)

Application Number Title Priority Date Filing Date
US10/288,065 Expired - Fee Related US7400582B2 (en) 2001-11-02 2002-11-04 Bi-directional and reverse directional resource reservation setup protocol
US12/170,825 Expired - Fee Related US8085664B2 (en) 2001-11-02 2008-07-10 Bi-directional and reverse directional resource reservation setup protocol
US13/312,021 Expired - Fee Related US8630176B2 (en) 2001-11-02 2011-12-06 Bi-directional and reverse directional resource reservation setup protocol
US14/138,767 Expired - Fee Related US9030933B2 (en) 2001-11-02 2013-12-23 Bi-directional and reverse directional resource reservation setup protocol
US14/708,988 Active US9560641B2 (en) 2001-11-02 2015-05-11 Bi-directional and reverse directional resource reservation setup protocol
US15/419,561 Abandoned US20170142025A1 (en) 2001-11-02 2017-01-30 Bi-directional and reverse directional resource reservation setup protocol

Family Applications Before (5)

Application Number Title Priority Date Filing Date
US10/288,065 Expired - Fee Related US7400582B2 (en) 2001-11-02 2002-11-04 Bi-directional and reverse directional resource reservation setup protocol
US12/170,825 Expired - Fee Related US8085664B2 (en) 2001-11-02 2008-07-10 Bi-directional and reverse directional resource reservation setup protocol
US13/312,021 Expired - Fee Related US8630176B2 (en) 2001-11-02 2011-12-06 Bi-directional and reverse directional resource reservation setup protocol
US14/138,767 Expired - Fee Related US9030933B2 (en) 2001-11-02 2013-12-23 Bi-directional and reverse directional resource reservation setup protocol
US14/708,988 Active US9560641B2 (en) 2001-11-02 2015-05-11 Bi-directional and reverse directional resource reservation setup protocol

Country Status (13)

Country Link
US (6) US7400582B2 (en)
EP (2) EP2487846A1 (en)
JP (4) JP3896118B2 (en)
KR (8) KR20080091230A (en)
CN (2) CN100521826C (en)
AR (1) AR039363A1 (en)
CA (2) CA2669413A1 (en)
DK (1) DK1440591T3 (en)
HK (2) HK1070778A1 (en)
MX (1) MXPA04004156A (en)
NO (1) NO20042075L (en)
TW (5) TWI272026B (en)
WO (1) WO2003041431A1 (en)

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2487846A1 (en) * 2001-11-02 2012-08-15 Interdigital Technology Corporation Bi-directional and reverse directional resource reservation setup protocol
WO2004047376A1 (en) * 2002-11-18 2004-06-03 Sharp Kabushiki Kaisha Network relay device, network relay program, and recording medium containing the network relay program
US7525994B2 (en) 2003-01-30 2009-04-28 Avaya Inc. Packet data flow identification for multiplexing
US7437458B1 (en) * 2003-06-13 2008-10-14 Juniper Networks, Inc. Systems and methods for providing quality assurance
US7701915B2 (en) * 2003-06-27 2010-04-20 Nokia Corporation Method in a communication system, a communication system and a communication device
EP1521405A1 (en) * 2003-09-30 2005-04-06 Siemens Aktiengesellschaft Bidirectional QoS reservation within an in-band signaling mechanism
US7447211B1 (en) * 2004-03-23 2008-11-04 Avaya Inc. Method and apparatus of establishing a communication channel using protected network resources
US7403544B2 (en) * 2004-06-04 2008-07-22 Broadcom Corporation VoIP WLAN conference calling via home wireless routers
US7680100B1 (en) 2004-09-30 2010-03-16 Avaya Inc. Internet protocol appliance manager
CN100346620C (en) * 2004-12-16 2007-10-31 中国科学院计算技术研究所 A transmitter-oriented resource reservation implementing method having backtracking ability
US7636302B2 (en) 2005-05-20 2009-12-22 Cisco Technology, Inc. Avoiding unnecessary RSVP-based preemptions
KR101265954B1 (en) * 2005-07-11 2013-05-23 더 트러스티이스 오브 콜롬비아 유니버시티 인 더 시티 오브 뉴욕 Method and apparatus of performing tunnel signaling over ip tunneling path
JPWO2007102208A1 (en) * 2006-03-08 2009-07-23 株式会社国際電気通信基礎技術研究所 Multi-hop wireless network system
US9154512B2 (en) * 2006-03-30 2015-10-06 Cisco Technology, Inc. Transparently proxying transport protocol connections using an external server
US20080031623A1 (en) * 2006-08-04 2008-02-07 Fujitsu Limited Providing optical signal regeneration information at the control plane
JP2008193395A (en) * 2007-02-05 2008-08-21 Fujitsu Ltd Two-way path setting method, and communication system and node device for achieving it
FI20075387A0 (en) 2007-05-29 2007-05-29 Nokia Corp Broadcast Resource Reservation Management on a Wireless Network
CN101345722A (en) * 2007-07-11 2009-01-14 华为技术有限公司 Method and apparatus for implementing resource reservation, media gateway
JP4980992B2 (en) * 2008-06-27 2012-07-18 富士通テレコムネットワークス株式会社 Communication apparatus and communication system
US9369371B2 (en) 2012-10-05 2016-06-14 Cisco Technologies, Inc. Method and system for path monitoring using segment routing

Family Cites Families (49)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3020284B2 (en) * 1990-12-15 2000-03-15 日本電信電話株式会社 Bidirectional search self-healing method
US5546388A (en) 1994-03-18 1996-08-13 Lin; Feng Packet-switched facsimile network and method of operation
US6101549A (en) * 1996-09-27 2000-08-08 Intel Corporation Proxy-based reservation of network resources
US6385195B2 (en) * 1997-07-21 2002-05-07 Telefonaktiebolaget L M Ericsson (Publ) Enhanced interworking function for interfacing digital cellular voice and fax protocols and internet protocols
KR100232491B1 (en) * 1997-09-26 1999-12-01 김덕중 Driving method for shared explicit filter in resource reservation protocol
JPH11103303A (en) * 1997-09-26 1999-04-13 Sony Corp Network resource reservation control method and system, reception terminal, transmission terminal and repeater
US6671276B1 (en) 1997-11-18 2003-12-30 Nec Corporation Switch based network architecture for IP multicast and integrated services
NL1007702C2 (en) * 1997-12-05 1999-06-08 Koninkl Kpn Nv Method and structure for communication.
DE19832290B4 (en) 1998-07-17 2011-12-08 Telefonaktiebolaget Lm Ericsson (Publ) Communication system and method for establishing connections between terminals of a first and a second communication network
JP2000078145A (en) 1998-08-28 2000-03-14 Fujitsu Ltd Boundary device conducting connection control at border of two communication networks and its method
KR100276684B1 (en) * 1998-11-13 2001-01-15 정선종 Network resource management system and network resource reservation method to guarantee service level between end users
US6416342B2 (en) * 1998-12-10 2002-07-09 Advantest Corporation Socket and connector therefor for connecting with an electrical component
JP3766223B2 (en) * 1999-02-18 2006-04-12 富士通株式会社 Border device and connection setting method thereof
US6519254B1 (en) * 1999-02-26 2003-02-11 Lucent Technologies Inc. RSVP-based tunnel protocol providing integrated services
DE69927238T2 (en) 1999-02-26 2006-07-13 Lucent Technologies Inc. Mobile IP with quality of service support
US6538416B1 (en) * 1999-03-09 2003-03-25 Lucent Technologies Inc. Border gateway reservation protocol for tree-based aggregation of inter-domain reservations
KR20010010980A (en) 1999-07-24 2001-02-15 김영환 Horizontal linearity compensating circuit in a monitor
JP3704003B2 (en) 1999-08-16 2005-10-05 株式会社東芝 Radio base station apparatus, radio terminal apparatus, and information communication method
US6728365B1 (en) * 1999-09-13 2004-04-27 Nortel Networks Limited Method and system for providing quality-of-service on packet-based wireless connections
US7532613B1 (en) * 1999-10-14 2009-05-12 Nortel Networks Limited Establishing a communications session having a quality of service in a communications system
US7369536B2 (en) * 1999-11-02 2008-05-06 Verizon Business Global Llc Method for providing IP telephony with QoS using end-to-end RSVP signaling
US6366577B1 (en) * 1999-11-05 2002-04-02 Mci Worldcom, Inc. Method for providing IP telephony with QoS using end-to-end RSVP signaling
US20010027490A1 (en) * 2000-01-25 2001-10-04 Gabor Fodor RSVP handling in 3G networks
AT419697T (en) * 2000-01-26 2009-01-15 Ericsson Telefon Ab L M Method, server and arrangement in a communication network
DE10012967A1 (en) * 2000-03-16 2001-09-20 Andreas Plettner Transponder used in radio frequency identification system, includes coupling elements connected to chip surface, and structurally designed to act as dipole antenna and disk capacitor
JP2001292167A (en) * 2000-04-10 2001-10-19 Fujitsu Ltd Network-repeating system and repeater
US6654610B1 (en) * 2000-05-05 2003-11-25 Lucent Technologies Inc. Two-way packet data protocol methods and apparatus for a mobile telecommunication system
EP1154600A1 (en) * 2000-05-09 2001-11-14 Lucent Technologies Inc. Resource reservation in 3G or Future Generation telecommunication network (iv)
US7423971B1 (en) * 2000-05-31 2008-09-09 Cisco Technology, Inc. Method and apparatus providing automatic RESV message generation for non-RESV-capable network devices
US6950397B1 (en) * 2000-07-14 2005-09-27 At&T Corp. RSVP/SBM based side-stream session setup, modification, and teardown for QoS-driven wireless lans
US6925075B2 (en) * 2000-07-31 2005-08-02 Telefonaktiebolaget Lm Ericsson Method and system for inter-operability between mobile IP and RSVP during route optimization
KR100356185B1 (en) 2000-08-31 2002-10-18 윈스로드 주식회사 Method for guaranteeing transmission service quality in internet
EP1211851A1 (en) * 2000-11-30 2002-06-05 TELEFONAKTIEBOLAGET L M ERICSSON (publ) Method and system for resource reservation in a multicasting network
US6973035B2 (en) * 2000-12-29 2005-12-06 Nortel Networks Limited Method and system for a routing mechanism to support two-way RSVP reservations
US20020110087A1 (en) * 2001-02-14 2002-08-15 David Zelig Efficient setup of label-switched connections
US6999436B2 (en) * 2001-04-16 2006-02-14 Nokia Corporation Method and apparatus for efficient routing of mobile node packets
US7287070B2 (en) * 2001-05-25 2007-10-23 Interdigital Technology Corporation Determining control of an internet communication between a sender and receiver
US7281043B1 (en) * 2001-05-31 2007-10-09 Cisco Technology, Inc. System for sharing resources among RSVP sessions
US7027400B2 (en) * 2001-06-26 2006-04-11 Flarion Technologies, Inc. Messages and control methods for controlling resource allocation and flow admission control in a mobile communications system
US7123598B1 (en) * 2001-06-29 2006-10-17 Nokia Inc. Efficient QoS signaling for mobile IP using RSVP framework
US7272651B1 (en) * 2001-08-28 2007-09-18 Cisco Technology, Inc. RSVP transmitter proxy
EP2487846A1 (en) * 2001-11-02 2012-08-15 Interdigital Technology Corporation Bi-directional and reverse directional resource reservation setup protocol
KR100411134B1 (en) * 2001-11-27 2003-12-18 에스케이 텔레콤주식회사 MPLS based Multicast Routing Protocol Method
US8014380B2 (en) * 2002-07-03 2011-09-06 Alcatel Lucent Method and system for automatically establishing a return label switched path
CN1612316A (en) * 2003-10-27 2005-05-04 上海宏力半导体制造有限公司 Method for manufacturing character line gap wall for forming good square contour
US7821929B2 (en) * 2004-04-05 2010-10-26 Verizon Business Global Llc System and method for controlling communication flow rates
JP4847711B2 (en) 2004-04-16 2011-12-28 株式会社日立ハイテクノロジーズ Charged particle beam equipment
FR2877078B1 (en) * 2004-10-25 2007-02-02 Snecma Moteurs Sa Energy system using stored natural gas in liquid form and thermoelectric machines
US7742482B1 (en) * 2006-06-30 2010-06-22 Juniper Networks, Inc. Upstream label assignment for the resource reservation protocol with traffic engineering

Also Published As

Publication number Publication date
KR20100013327A (en) 2010-02-09
JP2009124763A (en) 2009-06-04
JP2008035556A (en) 2008-02-14
US9560641B2 (en) 2017-01-31
KR20090095616A (en) 2009-09-09
US8630176B2 (en) 2014-01-14
CA2466144C (en) 2009-09-08
HK1139814A1 (en) 2010-09-24
TWI309955B (en) 2009-05-11
TW201006267A (en) 2010-02-01
KR20090034975A (en) 2009-04-08
CN1582588A (en) 2005-02-16
KR20050042217A (en) 2005-05-06
DK1440591T3 (en) 2014-02-10
KR20050090088A (en) 2005-09-12
EP2487846A1 (en) 2012-08-15
US8085664B2 (en) 2011-12-27
TW200635398A (en) 2006-10-01
TW200302651A (en) 2003-08-01
TWI334737B (en) 2010-12-11
JP4850264B2 (en) 2012-01-11
AR039363A1 (en) 2005-02-16
US20140112293A1 (en) 2014-04-24
CA2466144A1 (en) 2003-05-15
KR100730012B1 (en) 2007-06-20
US20080267125A1 (en) 2008-10-30
JP2005354745A (en) 2005-12-22
CA2669413A1 (en) 2003-05-15
JP2005509382A (en) 2005-04-07
CN101616447B (en) 2011-07-20
KR20100071119A (en) 2010-06-28
EP1440591B1 (en) 2013-12-25
KR20080091230A (en) 2008-10-09
US7400582B2 (en) 2008-07-15
NO20042075L (en) 2004-05-19
WO2003041431A1 (en) 2003-05-15
CN101616447A (en) 2009-12-30
US20120076096A1 (en) 2012-03-29
TW200420158A (en) 2004-10-01
JP4711778B2 (en) 2011-06-29
US20150249983A1 (en) 2015-09-03
JP3896118B2 (en) 2007-03-22
EP1440591A4 (en) 2010-02-24
KR100864040B1 (en) 2008-10-16
CN100521826C (en) 2009-07-29
MXPA04004156A (en) 2004-09-06
US20030161322A1 (en) 2003-08-28
JP4712014B2 (en) 2011-06-29
US9030933B2 (en) 2015-05-12
HK1070778A1 (en) 2005-06-24
TW200742457A (en) 2007-11-01
TWI272026B (en) 2007-01-21
KR20070119066A (en) 2007-12-18
TW582155B (en) 2004-04-01
EP1440591A1 (en) 2004-07-28

Similar Documents

Publication Publication Date Title
US10045356B2 (en) Apparatus, system and method for the transmission of data with different QOS attributes
US9001652B2 (en) Method and arrangement for transferring information in a packet radio service
JP5905365B2 (en) Dynamic bandwidth allocation for multiple access communications using session queues.
US8929394B2 (en) End-to-end service quality for latency-intensive internet protocol (IP) applications in a heterogeneous, multi-vendor environment
US20160330121A1 (en) Method and devices for installing packet filters in a data transmission
US8787889B2 (en) Conferencing system
EP1392077B1 (en) Managing the Quality of Service (QoS) levels during transfer between a wireless local area network (WLAN) and a mobile telephone network
KR100701637B1 (en) Circuit-switched and packet-switched communications
US6678252B1 (en) Method and apparatus for dynamic source routing in ad hoc wireless networks
US8161158B2 (en) Method in a communication system, a communication system and a communication device
KR100464893B1 (en) Method and apparatus for enabling multimedia calls using session initiation protocol
EP1374494B1 (en) Method and apparatus for establishing a protocol proxy for a mobile host terminal in a multimedia session
CN1822573B (en) System and method for controlling data traffic in a wireless communication system
JP4549599B2 (en) Method and apparatus for synchronizing and transmitting data in a wireless communication system
EP1309139B1 (en) Signaling for parameterized Quality of Service (QoS) Support
RU2323548C2 (en) Device and corresponding method intended for selection of information, related to quality of service in radio communication system
AU2005222356B2 (en) Method in a communication system to allocate resources
US6763392B1 (en) Media streaming methods and arrangements
US8825070B2 (en) Radio resource reservation for wireless networks
KR100542090B1 (en) Method for controlling error, designing medium access control frame and registering terminal in wireless communication system and recording medium
US6690679B1 (en) Method and system for bearer management in a third generation mobile telecommunications system
US6487595B1 (en) Resource reservation in mobile internet protocol
KR100613177B1 (en) A network for utilizing session initiation protocol for identifying user equipment resource reservation setup protocol capabilities
EP1183803B1 (en) Method and apparatus for routing packet data in a communications system
FI114768B (en) An improved method and arrangement for transmitting information in a packet radio service

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION