WO2000069129A1 - Dispositif reseau, appareil de commande d'un dispositif reseau et procede de reservation de ressources - Google Patents

Dispositif reseau, appareil de commande d'un dispositif reseau et procede de reservation de ressources Download PDF

Info

Publication number
WO2000069129A1
WO2000069129A1 PCT/JP1999/002396 JP9902396W WO0069129A1 WO 2000069129 A1 WO2000069129 A1 WO 2000069129A1 JP 9902396 W JP9902396 W JP 9902396W WO 0069129 A1 WO0069129 A1 WO 0069129A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
bucket
signaling
resource reservation
information
Prior art date
Application number
PCT/JP1999/002396
Other languages
English (en)
Japanese (ja)
Inventor
Shinya Kano
Original Assignee
Fujitsu Limited
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 Fujitsu Limited filed Critical Fujitsu Limited
Priority to PCT/JP1999/002396 priority Critical patent/WO2000069129A1/fr
Publication of WO2000069129A1 publication Critical patent/WO2000069129A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/822—Collecting or measuring resource availability data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/724—Admission control; Resource allocation using reservation actions during connection setup at intermediate nodes, e.g. resource reservation protocol [RSVP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/781—Centralised allocation of resources

Definitions

  • Network device Network device, network device control device, and resource reservation method
  • the present invention relates to a network device, a network device control device, and a resource reservation method, and more particularly to a network in a communication system that performs communication between terminals after securing resources of the network device existing on a path between two terminals.
  • the present invention relates to a device, a network device control device, and a resource reservation method.
  • RSV P a protocol called RSVP (Resourc e Res ervate on Protocol 1) has been used.
  • RSVP RSVP
  • a terminal requesting reservation transmits a RESV bucket (res e rve bucket) to a terminal of a communication partner.
  • the relay device router, etc.
  • the RESV bucket res e rve bucket
  • the reservation conditions bandwidth, priority, etc.
  • Reservation securing of the resource of the relay device ⁇ .
  • the resources are secured in all the relay devices between the reservation requesting terminal and the destination terminal, and communication for guaranteeing the required communication quality is performed between them. Enabled (a resource reservation service is provided).
  • RSVP secures resources in the relay device in the order in which signaling packets (RESV packets) are generated, that is, in the order in which resource reservation (service) is requested. For this reason, there was a problem that it was not possible to perform selective resource allocation such as allocating resources to important users and important applications.
  • a method has been adopted in which a server for managing the resource reservation service is provided, and the server determines whether the resource reservation is permitted or not.
  • the relay apparatus allocates resources according to the determination of the server.
  • FIG. 24 is an explanatory diagram of a resource reservation method in a conventional communication system using a server. In such a system,
  • the terminal (user) A transmits a reservation request packet (RESV packet) to the relay device (router) R1.
  • REV packet a reservation request packet
  • the relay device R1 inquires of the server SVR whether the reservation request may be accepted.
  • the server SVR determines whether or not the terminal A that has transmitted the reservation request has a reservation right.
  • the server SVR notifies the relay device R1 that the reservation is permitted.
  • the relay device R1 having received the reservation permission transfers the reservation request bucket (RESV) received from the terminal A to the next relay device R2.
  • RESV reservation request bucket
  • the relay device R2 that has received the reservation request packet inquires of the server SVR whether the reservation request can be accepted.
  • the server SVR that has received the inquiry determines whether the terminal A that has transmitted the reservation request has a reservation right.
  • the server notifies the relay device R2 that the reservation is permitted.
  • the relay device R 2 that has received the reservation transfers the reservation request packet (RESV) received from the terminal A to the next relay device.
  • RESV reservation request packet
  • resources are secured in all the relay devices R1 to R2 between the reservation request terminal A and the communication partner terminal B, and the communication quality of the reservation request terminal A and the communication partner terminal B is guaranteed (resource reservation). Service is provided).
  • the relay device inquires of the server whether the reservation request can be permitted. For this reason, it is necessary to send and receive an inquiry packet and a response packet a plurality of times before a signaling packet reaches a partner terminal, thereby increasing traffic, and increasing a processing delay due to a plurality of inquiry and response processes. Occurs.
  • an object of the present invention is to make it possible to omit a resource reservation permission inquiry from a second or subsequent relay device to a server, thereby preventing an increase in traffic and an increase in processing delay time.
  • Another object of the present invention is to perform a fine-grained service management according to a user by assigning a grade (priority) to a resource reservation right and permitting the relay device to reserve the resource.
  • Another object of the present invention is to encrypt a queried information inserted into a signaling bucket so that a malicious relay device cannot add the queried information without permission.
  • Another object of the present invention is to make a response of resource reservation permission only when resources can be secured by all the relay devices on the route between communication terminals, thereby ensuring that each relay device secures resources. And control the increase in traffic.
  • It has a relay device (network device) such as a router that configures the network, and a server (network device control device) that performs predetermined processing and responds to requests from the relay device.
  • a relay device network device
  • server network device control device
  • the resources are reserved according to the following (1) to (5).
  • One terminal transmits a signaling bucket to the other terminal for reserving the resources of the relay device existing on the path between the terminals.
  • the first relay device that has received the siddering bucket inquires of the server whether or not resource reservation is possible.
  • the server uses the reference information stored in advance to determine whether to permit the resource reservation, and responds to the relay device with the determination result.
  • the relay apparatus Upon receiving a response from the server that permits resource reservation, the relay apparatus performs processing for resource reservation, and sends a signaling packet containing the queried information to the other terminal.
  • the second and subsequent relay devices that have received the signaling bucket containing the queried information perform resource reservation processing without inquiring of the server whether or not the resource reservation is possible, and signaling containing the queried information.
  • the packet is transmitted to the other terminal.
  • the server holds the resource status of each relay device, finds a relay device on the route between the communication terminals by inquiring for resource reservation, and can secure resources in all the relay devices on the route. It is determined whether or not there is a certain power by referring to the resource status of the relay device. If all the relay devices can secure the resource, a response of resource reservation permission is made. In this way, each relay device can reliably secure resources and communication between communication terminals becomes possible. Also, if resources cannot be secured in any of the relay devices, it is not necessary to transmit the second and subsequent relay device hesidana ringing packets, so that an increase in traffic can be suppressed.
  • the present invention is not limited to the case where a server is inquired about permission for resource reservation and communication is performed based on the permission response. It can be applied to communication.
  • FIG. 1 is an overall configuration diagram of the network.
  • FIG. 2 is a configuration diagram of the relay device.
  • Figure 3 shows the bucket structure
  • Figure 4 is an example of a resource management table.
  • FIG. 5 is a configuration diagram of the server.
  • FIG. 6 shows an example of user information stored in the server.
  • FIG. 7 is a flowchart of a resource reservation process according to the first embodiment.
  • FIG. 8 is an explanatory diagram of various bucket structures.
  • FIG. 9 shows a resource reservation processing flow according to the second embodiment.
  • FIG. 10 shows an example of the structure of the permission response bucket according to the second embodiment.
  • FIG. 11 shows a resource reservation processing flow according to the third embodiment.
  • FIG. 12 is a flowchart of a resource securing process considering priority.
  • Figure 13 shows an example of a resource management table.
  • FIG. 14 is an explanatory diagram of various bucket structures.
  • FIG. 15 shows the resource reservation processing flow of the fourth embodiment.
  • FIG. 16 shows an example of the structure of the permission response bucket according to the fourth embodiment.
  • FIG. 17 is a server configuration diagram of the fifth embodiment.
  • Figure 18 shows an example of router information stored in the server.
  • FIG. 19 is a chart showing the topology of network devices.
  • FIG. 20 is a flowchart of the reservation permission determination process of the server of the fifth embodiment.
  • FIG. 21 shows a resource reservation processing flow according to the sixth embodiment.
  • FIG. 22 is a configuration example of a signaling bucket according to the sixth embodiment.
  • FIG. 23 is an explanatory diagram of a procedure when a signaling bucket having a sequential number is used.
  • FIG. 24 is an explanatory diagram of a resource reservation method using a conventional server.
  • 1 ⁇ Li in overall configuration diagram of a network to which the present invention can be applied 1 1, 1 2 End terminal (a host device) such as a personal computer, such as 1 3 ⁇ 1 3 2 constitutes a network router
  • the relay device 14 is a server that performs a predetermined process and responds with permission / rejection of reservation when an inquiry about resource reservation is made from the relay devices 13 to 1332.
  • terminal resources e.g. bandwidth
  • Terminal (user) requesting resource reservation 11 1 is a signal requesting a desired bandwidth.
  • a ring bucket (RESV bucket) is transmitted to the terminal 12 of the communication partner.
  • the relay device 13 that first receives the signaling packet transmits a permission request bucket for inquiring whether to permit the resource reservation request to the server 14 that manages the resource reservation service. .
  • the server 14 that has received the permission request packet determines whether to permit the resource reservation request with reference to the user information and the like stored in the database.
  • a permission response packet is transmitted to the relay device 13i to notify the reservation request permission.
  • the relay device 13 i Upon receiving the permission response packet instructing the reservation request permission, the relay device 13 i performs a process of securing the requested resource (bandwidth) at the terminal 11.
  • the relay device 13 attaches the already-inquired information to the signaling packet (information indicating that the resource reservation permission has already been inquired to the server). The next relay device 1 3 2 is transmitted.
  • the relay device 1 3 2 Upon receiving the signaling bucket to which the inquired information is attached, the relay device 1 3 2 immediately secures the resource (bandwidth) requested from the terminal without inquiring the server 14 of the resource reservation permission. To perform the process.
  • the relay device 1 3 2 if ensured requested resource (band), and transmits the signaling bucket bets query Align completion information is attached to the next repeater. Thereafter, in the same manner, the resource reservation service is completed when the communication counterpart terminal 12 of the terminal 11 which has finally requested the resource reservation receives the signaling bucket.
  • FIG. 2 is a configuration diagram of the relay device.
  • Reference numerals 13a and 13b denote a bucket receiving unit and a bucket transmitting unit, which transmit and receive packets (signaling packets and data buckets) in accordance with IP (intrenet Protocol).
  • the IP bucket is composed of an IP header 21 and a data part 22 as shown in FIG.
  • Reference numeral 13c denotes a signaling processing unit which performs analysis of received signaling packets, determination of necessity of inquiry to a server, instruction of resource reservation to the admission processing unit, instruction of generation of signaling packets, and the like.
  • 13d is a packet in the signaling bucket generating unit, and makes an inquiry about resource reservation permission according to an instruction from the signaling processing unit 13c.
  • 13 e is a routing table that holds routing information for determining the repacket sending route based on the destination IP address
  • 13 f is a resource management table that manages the resources of the relay device and its use
  • 13 g is a resource management table.
  • a resource securing processing unit 13h for controlling, 13h is a data communication unit for determining and transmitting a bucket transmission route with reference to a destination IP address and a routing table of the received data bucket.
  • the resource management table 13f has a bandwidth management table 13f-l and an allocated bandwidth management table 13f-2 as shown in FIGS. 4 (a) and 4 (b).
  • the allocated bandwidth management table 13 ⁇ -2 is the packet identifier. And manages the correspondence of the allocated bandwidth. As the packet identifier, the source IP address or a combination of the source IP address / destination IP address can be used.
  • the allocated bandwidth Fa is increased by f in the table of (a)
  • the remaining bandwidth Fe is reduced by f
  • the table of (b) is The allocated bandwidth f is registered corresponding to the packet identifier.
  • FIG. 5 is a configuration diagram of the server 14.
  • the server 14 includes: 1) a database unit 14a storing various information necessary for determining permission of resource reservation Z determination of non-permission; and 2) a permission request bucket for receiving a bucket for inquiring permission / non-permission of resource reservation from the relay device.
  • Receiving section 14b, 3 When receiving a permission request bucket, a reservation permission judgment processing section 14c, which determines permission / non-permission of resource reservation by referring to the information of the database section 14a, ⁇ permission / non-permission of resource reservation.
  • An authorization response bucket generating unit 14d for generating a bucket including information indicating permission is provided.
  • An authorization response bucket transmitting unit 14e for transmitting the authorization response bucket to the relay device.
  • Database 14a is a network resource that holds topology routing information and device-specific information.
  • a source information holding unit 14a-1 and a policy information holding unit 14a-2 for holding user information and the like are provided.
  • Fig. 6 shows an example of user information (1), the attributes of user (terminal) A, (1) user identifier (terminal IP address), (2) priority when the user uses the network, and (3) when the user uses the network. ⁇ ⁇ and other user-specific information.
  • the topology information and device-specific information will be explained when they are needed for explanation.
  • FIG. 7 is a flowchart of a resource reservation process according to the first embodiment of the present invention.
  • (A) is a process flow of the relay device, and
  • (b) is a process flow of the server.
  • FIG. 8 is an explanatory diagram of various packet structures used in the first embodiment.
  • (A) is a signaling packet
  • (b) is a permission request packet
  • (c) is a permission response packet. It has the same configuration as that shown in Fig. 2), and shows only a part of the IP header 21 and the data part 22.
  • the signaling packets sent from the source terminal and each relay device are included in the IP header part 21 as 1 destination address (destination terminal address), 2 source address (source terminal address)
  • the data section 22 has 2) packet type (resource reservation request packet), 2) inquired information (flag information indicating whether or not the server has been inquired of permission or non-permission of resource reservation), 3) system It has identification information of the data bucket targeted by the dunning packet, and 4 data bucket quality information. However, the inquired information in 2 does not necessarily need to be included in the signaling bucket from the source terminal.
  • the data bucket identification information includes a destination address, a source address, a protocol type, a destination port number, a source port number, etc., but these are all unnecessary and may be appropriately combined, for example, a combination of a destination address and a source address.
  • the data packet quality information includes a required relay delay, a required bandwidth, a required priority, and the like. However, any one or more qualities, for example, only the bandwidth, can be set as the required quality.
  • Bucket for permitting resource reservation sent from the relay device Z has (1) a destination address (server address) and (2) a source address (relay device address) in the IP header section 21 as shown in FIG. It has bucket type (permission request bucket), 2 data bucket identification information, and 3 data bucket quality information.
  • the response packet to the resource reservation inquiry transmitted from the server contains (1) the destination address (relay device address) and (2) the source address (server address) in the IP header section 21.
  • the data section 22 has (1) packet type (permission response packet) and (2) permission determination information (information indicating permission or non-permission).
  • the relay device 13 waits for reception of a signaling packet (step 101), and the server 14 waits for reception of a permission request packet (step 201).
  • the relay device 13 when the relay device 13 receives the signaling packet, it checks whether the packet is a resource reservation bucket by referring to the bucket type, and if the packet is a resource reservation bucket, checks whether the queried flag is set. (Step 102). If the queried flag is not set, the relay device 13 creates a permission request packet and queries the server 14 for permission or non-permission of resource reservation (step 10 3). Waiting for reception (step 104).
  • the server 14 Upon receiving the permission request bucket, the server 14 identifies the IP address of the source terminal from the data bucket identification information and recognizes the requested resource (for example, the requested bandwidth). Then, referring to the user information stored in the database section 14a, it is checked whether the source terminal (user) has the right to communicate using the requested band.
  • the requested resource for example, the requested bandwidth
  • the server 214 creates a response packet including the determination result and sends it to the relay device 13 (step 203).
  • the relay device 13 When the relay device 13 receives the response bucket, it determines whether the reservation is permitted or not. Is checked (step 105). If the reservation is not permitted, the resource reservation service is rejected (step 106). Thereafter, the processing is terminated and the reception of the next signaling bucket is waited.
  • step 105 if reservation permission is instructed, resource reservation control is executed, and it is determined whether or not the required band can be reserved (steps 107 and 108). For example, referring to the resource management table (FIG. 4 (a)), it is checked whether the required bandwidth is available.
  • the resource reservation service is rejected (step 106), and thereafter the processing is terminated and the reception of the next signaling packet is waited. If resources can be secured, the resource management tables (Figs. 4 (a) and 4 (b)) are updated, a signaling bucket with the queried flag set is created, and transmitted to the destination terminal side (step 109). This signaling packet is obtained by changing the queried flag to “set” in the signaling bucket received in step 101.
  • step 102 if the queried flag of the signaling bucket is set, the resource securing control is executed immediately without inquiring of the resource reservation permission / non-permission to the server to secure the required bandwidth. Determine whether the force is possible or not (steps 111, 112).
  • the resource reservation service is rejected (step 106), and thereafter the processing is terminated and the reception of the next signaling packet is waited. If resources can be secured, the resource management table is updated, and the received signaling packet (signaling bucket with the queried flag set) is transmitted to the destination terminal (step 113).
  • a predetermined bandwidth is requested as a resource from the user.
  • the server refers to the user information and requests the user to obtain the requested priority.
  • the above priority and the bandwidth more than the required bandwidth are permitted 91
  • Resource reservation is permitted only on -11-, and resource reservation is not permitted otherwise.
  • the signaling bucket is created by the relay device.However, the signaling bucket including the queried information is created in the server, and the signaling bucket is stored in the permission response bucket and transmitted to the relay device.
  • the relay device may be configured to extract the signaling bucket included in the permission response bucket and send the signaling bucket to the partner terminal side. In this way, it is possible to prevent an unauthorized relay device from transmitting a signaling bucket in which the inquired flag is set without permission and performing communication.
  • FIG. 9 shows a resource reservation processing flow of the second embodiment.
  • the same steps as those in the flow of the first embodiment are denoted by the same reference numerals.
  • FIG. 10 is an explanatory diagram of an authorization response bucket used in the second embodiment.
  • the signaling bucket includes queried information in addition to the information of the authorization response packet (see FIG. 8 (c)) of the first embodiment. It is included.
  • the relay device 13 waits for reception of a signaling packet (step 101), and the server 14 waits for reception of a permission request packet (step 201).
  • the relay device 13 checks whether the packet is a resource reservation bucket by referring to the packet type, and if the packet is a resource reservation packet, checks whether the queried flag is set. (Step 102). If the queried flag is not set, the relay device 13 creates a permission request packet and queries the server 14 for permission or non-permission of resource reservation (step 103). Waiting for reception (step 104).
  • the server 14 Upon receiving the permission request bucket, the server 14 identifies the IP address of the source terminal from the data bucket identification information and recognizes the requested resource (for example, the requested bandwidth). Next, by referring to the user information stored in the database unit 14a, it is checked whether the source terminal (user) has the right to communicate in the requested band. If the bandwidth allowed for the user (user bandwidth) is larger than the requested bandwidth, reservation allowed, small If not, it is determined that the reservation is not permitted (step 202).
  • the server 214 creates a response packet (FIG. 8 (c)) similar to that of the first embodiment and transmits it to the relay device 13 (251, 253). However, if the reservation is permitted, a signaling bucket with the queried flag set is created (step 252), and then a permission response packet having the signaling packet in the data section (see FIG. 10). Is created and transmitted to the relay device 13 (25 3).
  • the relay device 13 Upon receiving the permission response bucket, the relay device 13 checks whether reservation permission or reservation non-permission has been specified (step 105), and rejects the resource reservation service if reservation non-permission has been specified. Then (step 106), thereafter, the processing is terminated and the reception of the next signaling bucket is waited.
  • step 107 the process from step 107 is executed. Then, after securing the required bandwidth, the signaling packet included in the received response packet is transmitted to the destination terminal side (step 151), and thereafter, the reception of the next signaling bucket is awaited.
  • step 102 If the inquired flag is set in step 102, the processes in and after step 111 are performed as in the first embodiment.
  • the server 14 determines permission or non-permission of resource reservation and only notifies the relay device of the determination result. By permitting reservations, more fine-grained service management according to Liza can be performed.
  • FIG. 11 is a flowchart of a resource reservation process according to a third embodiment for assigning priorities and permitting resource reservation.
  • the same parts as those in the first embodiment in FIG. 7 are denoted by the same reference numerals.
  • FIG. 12 is a flowchart of the resource securing processing of the relay device in consideration of the priority
  • FIG. 13 is an example of a resource management table of the third embodiment
  • FIG. 14 is an example of various packet configurations of the third embodiment.
  • the resource management table manages almost the same contents as the resource management table (FIG. 4) of the first embodiment, but the packet is stored in the allocated bandwidth management table 13f-2. It differs in that it manages the correspondence between identifiers, priorities, and allocated bandwidth.
  • each The packet has substantially the same configuration as the packet of the first embodiment (FIG. 8) as shown in FIG. 14, but (1) a priority item column is provided in the data section 22 of the signaling packet. (2) The difference is that the priority is added to the permission response packet.
  • the relay device 13 waits for reception of a signaling packet (step 101), and the server 14 waits for reception of a permission request packet (step 201).
  • the relay device 13 refers to the packet type and checks whether the packet is a resource reservation packet, and if the packet is a resource reservation packet, checks whether the queried flag is set. (Step 102). If the inquired flag is not set, the relay device 13 creates a permission request bucket and queries the server 14 for permission / non-permission of the resource reservation (step 103), and then waits for the reception of the permission response bucket. (Step 104).
  • the server 14 Upon receiving the permission request bucket, the server 14 identifies the IP address of the source terminal based on the data bucket identification information, and recognizes the requested resource (for example, the requested bandwidth). Next, referring to the user information stored in the database unit 14a, it is checked whether the source terminal (user) has a right to communicate using the requested bandwidth. If the bandwidth (user bandwidth) allowed by the user is larger than the requested bandwidth, it is determined that the reservation is permitted, and if the bandwidth is smaller than the requested bandwidth, it is determined that the reservation is not permitted (step 202), and the priority is determined from the user information (step 261). . If the priority is obtained, the server 14 creates a permission response packet (FIG. 14 (c)) including the priority and transmits it to the relay device 13 (step 203).
  • the server 14 creates a permission response packet (FIG. 14 (c)) including the priority and transmits it to the relay device 13 (step 203).
  • the relay device 13 When receiving the permission response bucket, the relay device 13 checks whether reservation permission or reservation non-permission has been specified (step 105), and rejects the resource reservation service if reservation non-permission has been specified (step 105). Step 106) Thereafter, the processing is terminated and the reception of the next signaling bucket is waited.
  • step 105 if reservation permission is instructed, resource reservation control described later is executed in consideration of priority, and it is determined whether or not the required bandwidth can be reserved (steps 107 'and 108'). ). If the bandwidth cannot be secured, the resource reservation service is rejected (step 106), and thereafter, the processing is terminated and the reception of the next signaling bucket is waited.
  • step 109 If resources can be secured, the resource management tables (FIGS. 13A and 13B) are updated, a signaling bucket in which the queried flag and the priority are set is created, and transmitted to the destination terminal side (step 109). ').
  • This signaling packet changes the queried flag of the signaling bucket received in step 101 to a set, and includes the signaling priority received from the server.
  • the resource securing control described later is immediately executed without inquiring of the server whether the resource reservation is permitted or not. It is determined whether or not it is possible (steps 1 1 1 ', 1 1 2').
  • the resource reservation service is rejected (step 106), and thereafter, the processing is terminated and the reception of the next signaling bucket is waited.
  • the resource management table is updated, and the received signaling packet (signaling packet with the queried flag set) is transmitted to the destination terminal (step 113 ').
  • fine-grained service management according to the user can be performed.
  • resource allocation can be performed preferentially for users with high priority.
  • FIG. 12 is a processing flow of the resource securing control in step 107 'and step 11 1' of FIG.
  • step 301 it is determined whether the remaining bandwidth F e is larger than the required bandwidth (step 301). If Fe ⁇ Fr, the resource reservation service is accepted (step 302), and the resource management table is updated (step 303). The process ends.
  • step 301 If the requested bandwidth Fr is larger than the remaining bandwidth Fe in step 301, refer to the allocated bandwidth management table in FIG. 13 (b) and check if there is a reserved packet with a lower priority than the priority specified by the server. If it is not checked (step 304), rejection of the resource reservation service is rejected (step 305), and the process ends.
  • step 304 the priority lower than the priority specified by the server If there is a previously reserved bucket, the total bandwidth including the reserved bandwidth of the low priority and the remaining bandwidth is compared with the required bandwidth Fr (step 310). If the required bandwidth is larger, the resource reservation service is performed. Is rejected (step 305), and the process ends.
  • the reservation of the low priority reserved data packet is discarded (step 307), and the resource reservation is performed.
  • the service is accepted (step 302), the resource management table is updated (step 303), and the process is terminated.
  • the signaling bucket is created by the relay device.
  • a signaling bucket containing information indicating that the inquiry has been completed at the server and the priority is created, and the signaling bucket is stored in the permission response bucket to store the signaling bucket.
  • the relay device can extract the signaling bucket included in the authorization response bucket and send it to the partner terminal side.
  • FIG. 15 shows the resource reservation processing flow of the fourth embodiment.
  • the same steps as those in the processing flow of the third embodiment (FIG. 11) are given the same numbers.
  • FIG. 16 is an explanatory diagram of the permission / response bucket used in the fourth embodiment.
  • the signaling priority information is deleted from the permission / response packet of the third embodiment (see FIG. 14 (c)).
  • a signaling bucket containing queried information and signaling priority is stored.
  • the relay device 13 is waiting for reception of a signaling packet (step 101), and the server 14 is waiting for reception of a permission request packet (step 201).
  • the relay device 13 when receiving the signaling bucket, the relay device 13 refers to the packet type and checks whether the packet is a resource reservation packet, and if the packet is a resource reservation packet, checks whether the queried flag is set. (Step 102). If the queried flag is not set, the relay device 13 creates a permission request packet and queries the server 14 for permission / non-permission of resource reservation. (Step 104), and after that, it waits for the reception of the permission response packet (step 104).
  • the server 14 Upon receiving the permission request bucket, the server 14 identifies the IP address of the source terminal from the data bucket identification information, and recognizes the requested resource (eg, request band) of the source terminal. Then, referring to the user information stored in the database section 14a, it is checked whether or not the source terminal (user) has the right to communicate using the requested bandwidth. If the band allowed by the user (user band) is larger than the requested band, it is determined that the reservation is permitted, and if the band is smaller, the reservation is not permitted (step 202).
  • the server 14 creates a response packet (FIG. 8 (c)) similar to that of the first embodiment and sends it to the relay device 13 (271, 274). However, if the reservation is permitted, a priority is obtained from the user information (step 2722), and a signaling packet containing the priority and having the inquired flag set is created (step 2732). ). Next, the server 14 creates an authorization response packet (see FIG. 16) storing the signaling packet, and transmits it to the relay device 13 (274).
  • the relay device 13 Upon receiving the permission response bucket, the relay device 13 checks whether reservation permission or reservation non-permission has been specified (step 105), and rejects the resource reservation service if reservation non-permission has been specified. Then (step 106), thereafter, the processing is terminated and the reception of the next signaling bucket is waited.
  • step 107 the process from step 107 'is executed thereafter. Then, after securing the requested bandwidth, it transmits the signaling bucket included in the received response packet to the destination terminal side (step 161), and thereafter waits for reception of the next signaling bucket.
  • step 102 If the inquired flag is set in step 102, the processing from step 111 is performed in the same manner as in the third embodiment.
  • the server reserves or denies the resource reservation to the relay device based on whether or not the user has the right to communicate using the resource requested by the user. there were.
  • the relay device in addition to the above conditions, If the relay device can secure the required resources, the resource reservation is permitted.
  • FIG. 17 is a configuration diagram of a server 14 that performs resource reservation control according to the fifth embodiment.
  • This server 14 is composed of 1) a database section 14a for storing various information necessary for determining permission / non-permission of resource reservation, and 2) a bucket for inquiring permission / non-permission of resource reservation from the relay device.
  • ⁇ Information indicating permission of resource reservation Z not permitted Acknowledgment bucket generating unit 14 d for generating a bucket including: ⁇ an acknowledgment bucket transmitting unit 14 e for transmitting the acknowledgment bucket to the relay device, IP the IP address of the source terminal, the IP address of the destination terminal and the topology It has a relay device specifying unit 14f that specifies the relay device on the route between the two terminals using the information.
  • the database unit 14a includes a network resource information holding unit 14a-1 and a policy information holding unit 14a-2.
  • the network resource information holding unit 14a-1 holds topology route information and device specific information, and policy information.
  • the holding unit 14a-2 holds user information and operation policy information.
  • user information indicates the attributes of the user (terminal) (Fig. 6).
  • the device-specific information indicates the attributes of the relay device (router, etc.) as shown in Fig. 18; 1) the IP address of the router, 2) the maximum available bandwidth, 3) the allocated bandwidth, 4) the remaining bandwidth, and 4) other information.
  • Has router-specific information is included in Fig. 18.
  • the topology information indicates the connection relationship of the relay devices as shown in Figs. 19 (a) and (b).
  • the topology information of router A is a list of IP addresses of neighboring routers as shown in Fig. 19 (a).
  • the topology information of Router B is a list of IP addresses of neighboring routers. That is, FIG. 19 (a) shows that router A having an IP address of 192.168.15.1 is connected to three routers B to D. Of the three routers, router B with an address of 192.168.10.1 indicates that there are two adjacent routers A and E as shown in Fig. 19 (b).
  • a list of routers connected to a certain router is represented as a single table, and the number of nodes is prepared to represent and hold the topology of the network.
  • the configuration of the packet used in the fifth embodiment is the same as that of FIG. 8, and the entire resource reservation process is the same as the process of the first embodiment in FIG. The difference is the reservation permission determination process of the server 14.
  • FIG. 20 is a flowchart of a reservation permission determination process of the server 14 in the fifth embodiment.
  • the server 14 receives the permission request bucket from the relay device 13 (step 401)
  • the server 14 identifies the IP address of the source terminal from the data packet identification information, and outputs the required resources (for example, the required bandwidth). Recognize.
  • the required resources for example, the required bandwidth.
  • the source terminal (user) has the right to communicate in the requested band. For example, it is checked whether the bandwidth allowed for the user (user bandwidth) is larger than the required bandwidth, and it is determined that the reservation is possible if the user bandwidth is larger than the required bandwidth, and that the reservation is impossible if the user bandwidth is smaller than the required bandwidth (step 40). 2).
  • the server 14 creates a response packet indicating that the reservation is not permitted and sends it to the relay device (step 404). Thereafter, the next permission request bucket is transmitted. Wait for reception.
  • the server 14 obtains a communication route between the two terminals using the IP address and the topology information of the source terminal and the destination terminal included in the packet identification information, and performs the communication. All the relay devices on the route are specified (Step 405). For example, the server 14 calculates the shortest path between the two terminals using the Dijkstra Dijkstra algorithm, obtains IP routing information from the source terminal to the destination terminal from the path information, and obtains the IP routing information. Using the information, identify all the relay devices that relay between both terminals.
  • step 406 by referring to the router information of all the relay devices on the communication path, it is checked whether or not there is a remaining bandwidth exceeding the required band in all the relay devices (step 406). If the band does not exist, a response bucket indicating that the reservation is not permitted is created and transmitted to the relay device (step 404).
  • a response packet indicating reservation permission is created and transmitted to the relay device (step 407), and thereafter, the next permission request bucket is received. Wait for.
  • the resources can be reliably secured in each relay device, Communication between terminals becomes possible. Also, if resources cannot be secured in any of the relay devices, there is no need to transmit a signaling bucket to the second and subsequent relay devices, so that an increase in traffic can be suppressed.
  • the information already inquired into the signaling bucket is input without encryption and transmitted as it is.
  • By encrypting and inserting it is possible to prevent unauthorized communication by a malicious relay device. .
  • FIG. 21 is a flowchart of a resource reservation process according to the sixth embodiment for encrypting the queried information, and the same reference numerals are given to the same parts as those in the first embodiment in FIG. The difference from the first embodiment is that
  • step 101 decoding processing is executed (step 501), and the presence or absence of the queried information is determined based on the decoding result.
  • step 108 After securing the bandwidth for resource securing control (step 108), encrypt the queried information (step 502), and create and transmit a signaling packet containing encrypted data (step 5). 0 3).
  • the queried information is encrypted independently.
  • the encryption method (encryption key) may be easily discovered and misused. Therefore, when encrypting, a sequential number is generated, and the sequential number and the queried information are integrally encrypted. In this way, since the information to be encrypted does not have a constant value, it is possible to easily prevent the ⁇ key from being seen, and to prevent abuse.
  • FIG. 22 is a configuration example of a signaling bucket provided with a sequential number
  • FIG. 23 is an explanatory diagram of a procedure when the signaling bucket is used.
  • a procedure when a signaling packet having a sequential number is used will be described.
  • the terminal 11 requesting resource reservation transmits a reservation request signaling bucket (RESV) to the terminal 12 of the communication partner.
  • RESV reservation request signaling bucket
  • the relay device 13 1 that first receives the signaling packet (RESV) requests the server 14 that manages the resource reservation service to inquire whether the resource reservation request can be permitted. Send a packet.
  • RESV signaling packet
  • the server 14 that has received the permission request packet determines whether the reservation request may be permitted.
  • a permission response packet is transmitted to the relay device 13i to notify the reservation permission.
  • the relay device 13i Upon receiving the permission response packet indicating reservation permission, the relay device 13i performs a process for resource reservation. Then, a sequential number is created, and the created sequential number and the inquired information are combined and encrypted using an encryption key.
  • the encrypted inquiry information is attached to the signaling packet (RESV) and transmitted to the destination terminal.
  • a signaling packet (RESV) storing the received encrypted inquiry information is transmitted to the destination terminal.
  • relay device network device
  • server network device control device
  • One terminal transmits a signaling bucket requesting the start of a predetermined service to a relay device existing on a path between terminals, from one terminal to another terminal.
  • the relay device that has received the shidanering bucket inquires of the relay device control device (server) whether or not the service can be started.
  • the server uses the reference information stored in advance to determine whether service can be started or not, and returns the determination result to the relay device.
  • the relay device Upon receiving the response from the server to permit the start of the service, the relay device secures resources necessary for service execution and sends a signaling bucket containing the queried information to the next stage.
  • the relay device Upon receiving the signaling bucket containing the queried information, the relay device secures the resources required for service execution without inquiring of the server whether the service can be started or not, and relays the signaling packet containing the queried information to the next device. Send to the next step.
  • the server creates a signaling bucket containing the queried information, includes the signaling bucket in the response bucket notifying the relay device of the determination result, and extracts the signaling bucket included in the response bucket. It can also be configured to send the data to the communication partner terminal.
  • the reservation request permission between the second and subsequent relay devices and the server is It is possible to omit the inquiry, and it is possible to suppress an increase in traffic and an increase in relay delay of the signaling bucket.
  • the resource reservation right is assigned a grade (priority) to permit the relay apparatus to reserve the resource, it is possible to perform detailed service management according to the user. For example, resources can be allocated preferentially to users with high priority.
  • resources can be allocated preferentially to users with high priority.
  • by encrypting the queried information to be input to the signaling bucket only valid relay devices can input the queried information, and the malicious relay device adds the queried information without permission. Things can be avoided.
  • by encrypting the sequential number in addition to the inquiry information it is possible to avoid a situation in which a malicious relay device adds the inquired information without permission.
  • the server holds the resource status of each relay device, obtains a route between the remote communication terminals by inquiring for resource reservation, and all the relay devices on the route can secure required resources. It is determined whether or not there is any resource by referring to the resource status. If resources can be secured in all the relay devices, a response to resource reservation permission is made, so that the resources can be securely secured in each relay device. Communication between communication terminals becomes possible. Also, if resources cannot be secured in any of the relay devices, there is no need to transmit the sidan ringing bucket to the second and subsequent relay devices, so that an increase in traffic can be suppressed.
  • the present invention is not limited to the case where communication is performed by inquiring of the server for permission of the resource reservation service. It is also applicable when performing.

Landscapes

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

Abstract

Un paquet de signalisation servant à réserver des ressources d'un répéteur situé entre des terminaux est transmis d'un terminal à un autre. En recevant le paquet de signalisation, le répéteur interroge la disponibilité d'une ressource du serveur. En réponse à cette interrogation, le serveur détermine si la ressource est disponible ou non, en se référant aux informations de référence stockées, et il envoie le résultat au répéteur. Si la ressource est disponible, le répéteur la réserve et envoie à l'autre terminal un paquet de signalisation contenant l'information interrogée. En recevant le paquet de signalisation contenant l'information interrogée, le répéteur réserve la ressource sans faire de requête auprès du serveur.
PCT/JP1999/002396 1999-05-10 1999-05-10 Dispositif reseau, appareil de commande d'un dispositif reseau et procede de reservation de ressources WO2000069129A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP1999/002396 WO2000069129A1 (fr) 1999-05-10 1999-05-10 Dispositif reseau, appareil de commande d'un dispositif reseau et procede de reservation de ressources

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP1999/002396 WO2000069129A1 (fr) 1999-05-10 1999-05-10 Dispositif reseau, appareil de commande d'un dispositif reseau et procede de reservation de ressources

Publications (1)

Publication Number Publication Date
WO2000069129A1 true WO2000069129A1 (fr) 2000-11-16

Family

ID=14235643

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP1999/002396 WO2000069129A1 (fr) 1999-05-10 1999-05-10 Dispositif reseau, appareil de commande d'un dispositif reseau et procede de reservation de ressources

Country Status (1)

Country Link
WO (1) WO2000069129A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007004565A (ja) * 2005-06-24 2007-01-11 Nippon Telegr & Teleph Corp <Ntt> 個人環境を制御するための方法及び装置
JP2009518972A (ja) * 2005-12-06 2009-05-07 リッパーシイ・セレッシャル・エルエルシイ サービス要求に基づくデジタル・オブジェクトのルーティング
US7720947B2 (en) 2001-05-18 2010-05-18 Fujitsu Limited Method and device for reserving transmission band on internet

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH04168835A (ja) * 1990-11-01 1992-06-17 Oki Electric Ind Co Ltd Ａｔｍ交換機のルーティング方式及びａｔｍ交換網のルーティング方式
JPH09247190A (ja) * 1996-02-16 1997-09-19 Lucent Technol Inc 通信ネットワークのオペレーティング方法
JPH10308776A (ja) * 1997-05-08 1998-11-17 Hitachi Ltd ネットワークリソース予約方式
JPH1198147A (ja) * 1997-09-18 1999-04-09 Nippon Telegr & Teleph Corp <Ntt> Ａｔｍ交換装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH04168835A (ja) * 1990-11-01 1992-06-17 Oki Electric Ind Co Ltd Ａｔｍ交換機のルーティング方式及びａｔｍ交換網のルーティング方式
JPH09247190A (ja) * 1996-02-16 1997-09-19 Lucent Technol Inc 通信ネットワークのオペレーティング方法
JPH10308776A (ja) * 1997-05-08 1998-11-17 Hitachi Ltd ネットワークリソース予約方式
JPH1198147A (ja) * 1997-09-18 1999-04-09 Nippon Telegr & Teleph Corp <Ntt> Ａｔｍ交換装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HIDEHIRO FUKUSHIMA, TAKESHI ISHIZAKI, OSAMU TAKADA, "Daikibo Internet ni okeru kougi Qos hoshou houshiki no teian", Denshi Jouhou Tsuushin Gakkai Gijutsu Kenkyuu Houkoku, Vol. 98, No. 90, CQ98-2, 29 May, 1998 (29.05.98), pages 9-14. *
HIROSHI NOMURA, et al., "Porishi no motozuku doutekina Qos seigyo houshiki no ichikentou", Denshi Jouhou Tsuushin Gakkai Gijutsu Kenkyuu Houkoku, Vol. 98, No. 542, IN98-150, 22 January, 1999 (22.01.99), pages 69-76. *
JUN'ICHI MURAYAMA et al., "Kouiki networking service platform ni okeru hinshitsu hoshou architecture no sekkei", Denshi Jouhou Tsuushin Gakkai Gijutsu Kenkyuu Houkoku, Vol. 97, No. 564, IN97-160, 20 February, 1998 (21.02.98), pages 1-8. *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7720947B2 (en) 2001-05-18 2010-05-18 Fujitsu Limited Method and device for reserving transmission band on internet
JP2007004565A (ja) * 2005-06-24 2007-01-11 Nippon Telegr & Teleph Corp <Ntt> 個人環境を制御するための方法及び装置
JP2009518972A (ja) * 2005-12-06 2009-05-07 リッパーシイ・セレッシャル・エルエルシイ サービス要求に基づくデジタル・オブジェクトのルーティング

Similar Documents

Publication Publication Date Title
JP4727126B2 (ja) 近距離無線コンピューティング装置用のセキュア・ネットワーク・アクセスの提供
US6092113A (en) Method for constructing a VPN having an assured bandwidth
US7649890B2 (en) Packet forwarding apparatus and communication bandwidth control method
JP4541848B2 (ja) ユーザ端末接続制御方法および装置
JP2004048234A (ja) ユーザ認証システムおよびユーザ認証方法
EP2648371A1 (fr) Système et procédé de gestion de qualité de service
JPH1070540A (ja) 無線ネットワークにおける無線端末の認証方法および無線ネットワーク
KR100953595B1 (ko) 홈네트워크 서비스 품질 관리 시스템
US7320034B2 (en) System and method for reserving a virtual connection in an IP network
US20200203027A1 (en) Internet of things connectivity device and method
EP1830520B1 (fr) Méthode et système de redirection de client
US7694015B2 (en) Connection control system, connection control equipment and connection management equipment
US7656794B2 (en) Method and apparatus for authenticated quality of service reservation
US20220232000A1 (en) Secure communication system
US8102762B2 (en) Communication control system and communication control method
EP1244265A2 (fr) Service d&#39;implémentation de politique intégrée pour réseau de communication
WO2000069129A1 (fr) Dispositif reseau, appareil de commande d&#39;un dispositif reseau et procede de reservation de ressources
US20220368688A1 (en) Secure communication system
Cisco Intranet and Extranet VPN Business Scenarios
JPH11112503A (ja) ネットワークシステムおよびネットワーク機器
JP3771523B2 (ja) ゲートウェイ装置
WO2013060224A1 (fr) Procédé, système et élément de réseau pour connexion sécurisée
JP3628557B2 (ja) 通信品質制御装置および記録媒体
US20230171228A1 (en) Secure communication system
KR20050054308A (ko) 패킷 데이터 통신에 적용되는 접속 단말 식별자 관리 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): JP US

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
ENP Entry into the national phase

Ref country code: JP

Ref document number: 2000 617610

Kind code of ref document: A

Format of ref document f/p: F