The above and other objects, features and other advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which:
Preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings.
Referring to
The UPnP QoS processor 310 is connected to an UPnP QoS manager 400 that is a controller for an UPnP QoS structure. The UPnP QoS manager 400 is commonly connected to devices 100 and 200 connected to the first and second networks having the bridge 300, and each of the devices 100 and 200 comprises an UPnP QoS processor 110 and 210 which are UPnP QoS devices to be controlled.
When applications 120 and 220 in the devices 100 and 200 request application service, the UPnP QoS manager 400 decides a path for providing a requested service, and transfers connection information and QoS information for providing the request application service to devices 100, 200 and 300 located between the decided path.
The QoS information provided from the UPnP QoS manager 400 is transferred as a traffic specification (TSpec) parameter. The TSpec parameter denotes an amount of traffic required for a predetermined service flow.
The devices 100, and 200 in the first and second networks establish and process connections to be suitable to its network based on the connection information and the QoS information such as traffic information, which are transferred from the UPnP QoS manager 400.
The bridge 300 performs a bridge function for connecting the device 100 of the first network to the device 200 of the second network.
In more detail, the bridge 300 collects connection information of all services and QoS information, which are transferred from the UPnP QoS manager 400, through the UPnP QoS processor 310 and stores the connection information and QoS information according to each service in the bridge function unit 320. Also, the bridge 300 establishes or releases the connections, differently queues the received frames, and transmits frames based on the stored information.
In order to perform such operations, the bridge function unit 320 comprises an adaptive QoS managing unit 321 for transforming the collected connection information of application services and QoS requirement information to global information that can be processed in the bridge, and controlling the bridge function unit 320 to bridge the requested application service and the QoS; a flow managing unit 322 for storing and managing connection information of each flow of service and the QoS information thereof in response to the control of the adaptive QoS managing unit 321; a bridge QoS processing unit 323 for managing resources in the bridge in response to the control of the adaptive QoS managing unit 321, allocating resources for establishing a connection, obtaining connection information of a received frame corresponding to the QoS information from the flow managing unit 322, and providing QoS according to the obtained information to the QoS processing unit 323; and first and second network QoS processor for monitoring QoS setting and link states in each of the first and second networks.
Hereinafter, the constitutional elements of the bridge function unit 320 will be described in detail with reference to
Referring to
The adaptive QoS manager 321a receives connection information and QoS information for requested application service on the first and second networks through the UPnP QoS processing unit 310.
As described above, the TSpec, which is QoS information used in a general UPnP QoS structure, is not used in other network system. Therefore, it requires the TSpec to transform to global format to be independent from networks and application programs and to be used in all systems.
In order to transform the TSpec, the adaptive QoS manager 321a transfers the received TSpec information to the global QoS transformer 321b for transforming the received TSpec to a global format to be used in all systems. The global QoS transformer 321b transfers the TSpec parameter of the UPnP to a global format such as XML through a global QoS transform function.
The adaptive QoS manager 321a transfers the transformed global QoS information and connection information of each service to lower systems such as the flow manager 323, the bridge QoS processor 323, and the first and second network QoS processors 324 and 325. The adaptive QoS manager 321a receives the result of establishing and releasing the connections and the link monitoring information of the first and second networks from the lower systems, and decides to allocate or release the resources. The function of the adaptive QoS function will be described with other lower systems in more detail.
Referring to
In order manage them, the flow managing unit 322 comprises a flow manager 322a defines correlation by connecting the connection information of each service from the adaptive QoS manager 321a and the connection information of each network established by the bridge QoS processing unit 323 and the first and second network QoS processing unit 324 and 234.
The defined information in the connection table 322b is provided as bridge information according to the registered connection information corresponding to a received frame when the frame is received and when the request for the connection information of the received frame is received.
The connection table 322b may comprise one or more tables.
Referring
The detailed structure of the bridge QoS processing unit 323 can be divided into a control block for setting up QoS information and controlling constitutional elements of the bridge, and a data block for processing the received data. In more detail, the control block of the bridge QoS processing unit 323 comprises the local resource manager 323a, the local QoS mapper 232b, the admission controller 323d, the local QoS monitor 323d, and the data block comprises the identifying unit 323e, the scheduler 323f, and the buffer manager 323g.
The local resource manger 323a receives the connection information and the global QoS information thereof, which are transferred from the adaptive QoS manager 321a. The local resource manager 322a transforms the global QoS information provided through the local QoS mapper 323b to local QoS information required in the bridge QoS processing unit 323.
The local resource manager 323a inquiries the admission controller 323d whether a request QoS can be provided or not based on the transformed local QoS information. The admission controller 323d determines whether the requested QoS can be provided or not. In more detail, the admission controller 323d calculates the amount of resources for guaranteeing the request QoS based on the global QoS information, compares the calculated amount of the resources and available resources in the bridge, and determines whether the requested QoS can be provided or not.
If the requested QoS can be provided, the local resource manager 323a allocates resources required for providing QoS of a corresponding service to the data block such as the identifying unit 323e, the scheduler 323f and the buffer manager 323g, and requests them to process the allocated resources.
On the contrary, if the admission controller 323d determines that the requested QoS cannot be provided, the local resource manager 323a checks the currently provided QoS through the local QoS monitor 323d, and transfers modified QoS information, TSpec parameter, for providing the request service to the adaptive QoS managing unit 321. The adaptive QoS managing unit 321 decides to approve the modified QoS information, and returns it to the local resource manager 323a. If the modifying request is approved, the local resource manager 323a request allocation and process the modified resource.
When data frame is received, the data block receiving and requested to process the resources of services extracts the connection information of the received frame from the identifying unit 323a. Based on the extracted connection information, the data block searches the connection table 322b of the flow managing unit 322 and selects one of the first and second networks for the corresponding service connection with an output interface. That is, the data block selects one of connections in the first or the second networks. The connection information extracted from the identifying unit 32a comprises at least one of a MAC address, an IP address, a port number, a protocol number, priority information, and an interface number, combination of connection information in the first or the second networks.
Based on the selected interface and connection information from the identifying unit 323e, the scheduler 323f queues frames in an output buffer that provides a proper QoS to the selected connection, and the buffer manager 323g sequentially reads and transmits the data frames in each output buffer through a device driver.
The first and second network QoS processing unit 324 and 325 provide QoS managing function to each of the first and second networks. The device connection manager 601 receives the connection information of each service and the global QoS information from the adaptive QoS manager 321a, and transforms the received global QoS information to QoS information to be used in a corresponding network, that is, the first network or the second network, through the device QoS mapper 602. Using the connection information of each service and the modified QoS information, the device connection manager 601 requests corresponding network device driver 330 or 340 to establish a QoS connection for each service flow or to release the QoS connection. Also, the device connection manager 601 receives the result of establishing and releasing and transfers the received result to the adaptive QoS manager 321a. The adaptive QoS manager 321a can confirm whether the requested service connection is established or not based on the received result. The confirmed connection information of the network device driver is transferred and stored to the flow manager 322.
Furthermore, the first and second network QoS processing units 324 and 325 monitor the QoS state and the link state of all connections established in each corresponding network through the link monitor 605. Such monitoring information is regularly or occasionally transferred to the adaptive QoS manager 321a through the device connection manager 601. Herein, the monitoring cycle can vary according to the network state or the QoS state. The adaptive QoS manager 321a monitors the QoS state of each service and performs the QoS adaptation using the monitoring information. Also, the adaptive QoS manager 321a transfers the state information of the requested service to the UPnP QoS managing unit 400.
As described above, the bridge according to certain embodiments of the present invention obtains connection information through an UPnP QoS structure when connecting networks supporting different QoS, controls and manages QoS of resources in the bridge based on the obtained QoS information, and adaptively manages resources and connections according to the QoS characteristics of each network. Therefore, the heterogeneity problem between networks can be solved.
While the present invention has been shown and described in connection with the preferred embodiments, it will be apparent to those skilled in the art that modifications and variations can be made without departing from the spirit and scope of the invention as defined by the appended claims.
Number | Date | Country | Kind |
---|---|---|---|
10-2006-0096419 | Sep 2006 | KR | national |