[go: up one dir, main page]

WO2008044893A1 - Procédé de traitement d'une demande d'accès à un réseau - Google Patents

Procédé de traitement d'une demande d'accès à un réseau Download PDF

Info

Publication number
WO2008044893A1
WO2008044893A1 PCT/KR2007/005002 KR2007005002W WO2008044893A1 WO 2008044893 A1 WO2008044893 A1 WO 2008044893A1 KR 2007005002 W KR2007005002 W KR 2007005002W WO 2008044893 A1 WO2008044893 A1 WO 2008044893A1
Authority
WO
WIPO (PCT)
Prior art keywords
connection
information
establishment
request
requesting
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.)
Ceased
Application number
PCT/KR2007/005002
Other languages
English (en)
Inventor
Yu Kyoung Song
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.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
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 LG Electronics Inc filed Critical LG Electronics Inc
Publication of WO2008044893A1 publication Critical patent/WO2008044893A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/78—Architectures of resource allocation
    • H04L47/781—Centralised allocation of resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/15—Flow control; Congestion control in relation to multipoint traffic
    • 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/74—Admission control; Resource allocation measures in reaction to resource unavailability
    • H04L47/745—Reaction in network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L2012/2847—Home automation networks characterised by the type of home appliance used
    • H04L2012/2849—Audio/video appliances

Definitions

  • This document is related to managing contents transfer services through a home network such as UPnP-based home network.
  • UPnP 1 M (hereinafter, it is referred to as UPnP for short) specifications have been proposed.
  • a UPnP network consists of a plurality of UPnP devices, services, and control points.
  • a service on a UPnP network represents a smallest control unit on the network, which is modeled by state variables.
  • a CP (Control Point) on a UPnP network represents a control application equipped with functions for detecting and controlling other devices and/or services.
  • a CP can be operated on an arbitrary device which is a physical device such as a PDA providing a user with a convenient interface.
  • a CP can also constitute a single device together with another service, e.g., a renderer service which expresses images by rendering media data. Therefore, multiple CPs can exist on a UPnP network and the user can control operations on a desired service by choosing a convenient CP depending on his or her current location or employed device.
  • a home network as above is built in a particular place such as a home, the user can conveniently make use of desired operations (e.g., operations of duplicating or transferring data between separate devices) irrespective of his or her current location; moreover, multiple users can share the same device at the same time, in the same place.
  • desired operations e.g., operations of duplicating or transferring data between separate devices
  • One objective of the present invention is to provide a method supporting various ways of handling a current servicing connection or a new connection when available bandwidth is not sufficient for the new connection.
  • Another objective of the present invention is to provide a method for dealing with a current problem of transfer resources in case of insufficiency thereof by a method selected according to the user's convenience.
  • One method for processing a connection request for traffic transfer on a network according to the present invention comprises receiving a request for establishment of a first connection that carries information specifying a procedure when access allowance is rejected and requesting access allowance of the first connection according thereto; and when the request for access allowance of the first connection is rejected, processing the request for establishment of the first connection according to the information specified in the procedure.
  • the information of the above procedure specifies at least one from among TCFS (First Come First Service)', 'pre-emption of an existing connection', and 'provision of information about an existing connection'.
  • TCFS First Come First Service
  • a second connection to be released is determined from among existing connections in service and an action for requesting release of the determined second connection is invoked, where the action has an input argument carrying information for identifying the first connection; subsequently the second connection is released and access allowance of the first connection is again requested.
  • the information identifying a connection is a traffic handle assigned to a traffic descriptor generated with respect to the connection.
  • a second connection to be released is determined from among existing connections in service and an action for requesting release of the determined second connection is invoked, where the action has an input argument carrying information for identifying the first connection.
  • the second connection is then released and access allowance of the first connection is requested again. If a success response is received with respect to the request, information about the released second connection is provided along with the success response associated with the request for establishment of the first connection.
  • a second connection to be released is determined from among existing connections in service and information of the determined second connection is provided to a requester of establishment of the first connection.
  • the provided information includes a progression request
  • an action for requesting release of the determined second connection is invoked, where the action has an input argument carrying information for identifying the first connection.
  • the second connection is then released and access allowance of the first connection is requested again. If a success response is received with respect to the request, the success response with respect to the request for establishment of the first connection is transmitted.
  • the step of processing a request for establishment of the first connection if the information of the above procedure specifies at least 'provision of information about an existing connection', obtains information about existing connections in service and provides a requester of establishment of the first connection with information about all the existing connections or part of connections having priority lower than that of the first connection.
  • the step of processing a request for establishment of the first connection if the information of the above procedure specifies 'FCFS', rejects the request of establishment of the first connection.
  • One method for traffic transfer services on a network comprises requesting information about processing capability in case of insufficiency of network transfer resources from at least one of management devices managing traffic on the network and obtaining the information; and at the user's request for connection establishment, selecting a management device based on the obtained information about processing capability and invoking an action for requesting establishment of a first connection to the selected management device, the management device supporting a method to process insufficiency of transfer resources selected at the time of the request.
  • a step of requesting establishment of the first connection is carried out by pre-empting a connection selected to be released according to the user's request.
  • the step of requesting establishment of the first connection uses an action having the same name as the action requesting establishment of the first connection.
  • the action used in the step of requesting establishment of the first connection includes an input argument specifying only 'pre-emption of an existing connection' with respect to a method to process insufficiency of transfer resources.
  • the step of requesting establishment of the first connection uses an action having a name different from that of the action for requesting establishment of the first connection and the action is the one for requesting pre-emption including in its input argument identifying information about a pre-empting connection and a connection to be pre-empted.
  • Fig. 1 illustrates a flow diagram of a method for processing a connection requested for establishment for transfer services according to one embodiment of the present invention
  • Fig. 2 illustrates a method for selecting a connection to be released in case of pre-empting an existing connection in service according to one embodiment of the present invention
  • Figs. 3A and 3B illustrate signal exchange procedures among devices or services according to one embodiment of the present invention, wherein an existing or a new connection is processed by a specified or selected method in case of insufficiency of transfer resources;
  • Fig. 4 illustrates the structure of a state variable defined and used for managing connections in a device or a service that actually carries out transfer of traffic according to one embodiment of the present invention;
  • Fig. 5 illustrates the structure of an action for releasing a connection used for pre-empting a connection for traffic
  • Fig. 6 illustrates a signal exchange procedure among devices or services according to one embodiment of the present invention, wherein information about an existing connection is provided by a specified or selected method in case of insufficiency of transfer resources;
  • Figs. 7A and 7B respectively illustrate a signal exchange procedure among devices or services according to one embodiment of the present invention, wherein pre-emption of an existing connection and provision of information about the connection are carried out by a specified or selected method in case of insufficiency of transfer resources.
  • 'TD information' information which describes traffic conducting the transfer
  • 'TD information' information which describes traffic conducting the transfer
  • TD information includes type of the corresponding traffic (e.g., information indicating realtime data (streaming data) or non-realtime data), information indicating applicability of change of service quality, information about the user who requested the corresponding traffic, and also information specifying conditions depending on service quality (e.g., HD (High Definition) or SD (Standard Definition)) of the corresponding traffic (which is also called as 'Tspec information').
  • Tspec information includes information about service rate required for streaming of traffic of particular service quality. The above terms such as TD, Tspec, etc are not main points to the present invention and therefore can be replaced with different terms.
  • Fig. 1 illustrates one example of a flow diagram regarding to the above.
  • a request for a new connection (a request for allowance of access to a network) is made SIl
  • service rate of the quality specified in TD information accompanying the request (service rate specified in Tspec information which is set as active in TD information) is checked and whether the required bandwidth is available within current remaining bandwidth (unoccupied bandwidth after subtracting bandwidth reserved for streaming and so on from total available bandwidth provided by a network) is determined S 12.
  • a request for a new connection is accepted Sl 6, otherwise a method for processing a new connection in case of insufficiency of transfer resources is checked or selected Sl 3. If a checked or selected method is 'pre-emption', service rate of a connection (or sum of service rates of connections) selected among current servicing connections after a selection policy, which is to be described later, is compared with that of the new connection required in addition to available bandwidth S14. If the former is larger than the latter, a current servicing connection ⁇ ) is released sequentially Sl 5 until a new connection can be accommodated S16, otherwise the newly requested connection is rejected S19.
  • service quality of the connection instead of releasing a connection, service quality of the connection can be degraded. Additional bandwidth is calculated by difference of bandwidth obtained from degrading service quality, from which connections are selected.
  • an "inferior blocking connection” denotes the one from among blocking connections being in service and whose priority information, e.g., UIN (User Importance Number), is lower than that of a newly requested connection. Namely, in the example of Fig. 2, connections A, B, C, and D are inferior blocking connections with respect to a newly requested connection E.
  • Fig. 2 illustrates specifically a method for selecting a connection to be released according to one example of a selection policy.
  • bandwidth occupied by current servicing connections is 95 Mbps on a network of 100 Mbps bandwidth.
  • connection E bandwidth marked as active
  • UIN is set as 50
  • a preliminary group of connections is formed, where release of the connections starting from the lowest UIN yields necessary bandwidth, namely, 15 Mbps.
  • Blocking connections are finally selected in such a way that among the preliminary group of connections, the number of connections to be released are kept smallest and at the same time, total available bandwidth secured from the release is larger than necessary bandwidth S23B.
  • a lowest UIN is selected from among UINs yielding total available bandwidth larger than necessary bandwidth, the total available bandwidth being secured by choosing a particular UIN among individual UINs of current servicing connections and releasing connections with UINs lower than the particular UIN.
  • Blocking connections are finally selected from connections of UINs lower than the selected UIN in such a way that the number of released connections is kept as small as possible and total available bandwidth secured from the release is larger than necessary bandwidth.
  • connections C, and D can yield total available bandwidth of 18 Mbps in a preliminary selection procedure, the above connections are selected (that is, as a reference of pre-emption, UIN 30 is determined). Among the selected connections (among connections, each UIN of which is lower than a determined pre-emption reference, 30), a combination of connections where the number of connections to be released is smallest and total available bandwidth is still larger than necessary bandwidth — namely, connections B and D — is finally selected. Network resources for finally selected connections are pre-empted and used for a new connection. In other words, finally selected connections are released S23C and a newly requested connection (connection E) is accommodated. As a matter of course, in the example of Fig.
  • FIGs. 3A and 3B illustrate signal exchange procedures among devices or services according to one embodiment of the present invention, wherein a connection for transfer services is allowed and an existing or a new connection is processed by a specified or selected method in case of insufficiency of transfer resources.
  • the procedures illustrated in Figs. 3A and 3B and Figs. 6, 7A and 7B to be described below correspond only to a specific example among various signal exchange methods between devices for dealing with insufficiency of transfer resources; principles and purpose of the present invention are not limited to the illustrated procedure in Fig. 3. Therefore, inventions employing different signal exchange methods but utilizing principles and purpose suggested in the description of the present invention should necessarily be considered to belong to the scope of the present invention.
  • a control point on a network invokes an action for requesting information about pre-emption capability at the time of initial connection to a network or when connection of a QoS manager to a network is perceived S311A, S311B.
  • Each QoS manager on which the action has been invoked returns information about a method available in case of insufficiency of resources set to the QoS manager itself ("PreemptionCapabilities") to a control point that requested the action S312A, S312B.
  • 'FCFS' is a method that allows access to a network in order of a request of a transfer service connection, where a new connection is not accommodated when available bandwidth is insufficient.
  • availability for support of 'a method to process resource insufficiency' is represented by a flag in order of 'FCFS', 'pre-emption of an existing connection', and 'provision of information about a blocking connection' in accordance with respective methods described above.
  • three flags of "0.1.1” indicate that 'pre-emption of an existing connection' and 'provision of information about a blocking connection' are available.
  • Such a representation is equally used for other actions, e.g., 'action for requesting establishment of a connection (RequestTrafficQoSQ)'.
  • 'action for requesting establishment of a connection RequestTrafficQoSQ
  • SelectedPreemptionRule a method to process 'resource insufficiency'
  • control point 15 inquires of the user how to process in case of insufficiency of network transfer resources and receives a response thereto SSOl.
  • the control point 15 chooses a QoS manager having 'pre-emption capability' supporting a processing method selected according to the response by referring to previously received information (PreemptionCapabilities) about 'pre-emption capability' of all the QoS managers and configures TD information (TDl) about a connection for streaming of contents.
  • PreemptionCapabilities previously received information about 'pre-emption capability' of all the QoS managers
  • TDl TD information
  • the control point 15 requests S331 connection establishment while providing the configured TD information (TDl) for the chosen QoS manager 14 (A different QoS manager 12 in the figure can also be used for this purpose.
  • TDl TD information
  • relationship between a control point and a QoS manager selected by the control point for connection establishment is described in terms of the letter A and B introduced in the figure.
  • Information about a source and a destination of a connection designated by the information selected by the user is also contained in the TD information configured by the control point 15.
  • Information about a source and a destination is composed of, e.g., UDN (Unique Device Name) of a device or a service that becomes a source or a destination and a service identifier (Service ID).
  • the QoS manager 14 that has received the request for connection establishment creates a traffic handle that is composed of string information — this information is used for unique identification and management of TD information (that is, a connection for traffic transfer) among devices, where a device may imply a 'service' within the device and in the following, the term of 'device' can alternatively indicate a 'service' unless description of operations is impaired — and records the traffic handle within the received TD information (TDl) (before this recording, the corresponding fields within TD information exchanged among devices and/or services are left blank or filled with NULL).
  • TDl received TD information
  • the QoS manager 14 provides TD information for a QoS policy holder (QPH) (not shown) and requests an inquiry of priority information about a requested connection.
  • QPH QoS policy holder
  • the QoS policy holder determines priority information according to a priority determination policy or algorithm applied already thereto. The determination is made by applying information such as identifying information of the user who requests access and type of traffic requested for access (e.g., whether it is of AV data or traffic for external call at emergency) to its policy or algorithm. According to the determination, e.g., TIN (Traffic Importance Number) and UIN are determined as priority information, which is subsequently recorded in TD information and returned to the QoS manager 14 in response to the inquiry request.
  • TIN Traffic Importance Number
  • the QoS manager 14 that received the returned TD information determines a traffic path based on source and destination information within the TD information. According to the path determination, besides individual QoS devices corresponding to a source and a destination, QoS devices through which traffic passes can be included in the path. Once a path is determined, an action for requesting allowance of access to a network (AdmitTrafficQoSQ) is invoked to each individual QoS device on the path (including individual QoS devices at the source and destination) (a QoS device 13 in the examples of Figs. 3A and 3B) by loading the returned TD information into the action S332.
  • AdmitTrafficQoSQ an action for requesting allowance of access to a network
  • the QoS device 13 of Figs. 3A and 3B represents a source and a destination device to establish a connection, and also applies to the case of multiple devices when other devices exist on a data transmission path between the two devices; in what follows, the term of 'QoS device' should be understood as a device or a service of the above meaning unless it is specifically prefixed with a modifier such as 'individual'.
  • connection allowance is given from the QoS device 13 since current bandwidth available can accommodate requested bandwidth (in reality, "Admitted" response is received from each individual QoS device on the path) S333
  • the QoS manager 14 fills TD information with identifying information of individual QoS devices (e.g., UDN and service ID) belonging to the path of an admitted connection and provides the control point 15 with the identifying information, thereby delivering an OK response to the request for connection establishment (RequestTrafficQoSQ) S334.
  • Identifying information about individual QoS devices on a path can also be filled into the TD information when allowance of access to the QoS device 13 is invoked S333.
  • the QoS manager 14 delivers a FAIL response in response to the request for connection establishment (RequestTrafficQoSQ) instead of carrying out an operation such as pre-emption or provision of information about blocking connections.
  • the QoS device 13 in order to manage connections that it has admitted, assigns and manages a state variable in the name of, e.g., "MostRecentStreamAction".
  • the state variable has internal fields as shown in Fig. 4 according to one embodiment of the present invention.
  • the state variable is an evented state variable which generates an event when the value of a field changes.
  • the upper three fields 401 among illustrated fields are those counting the number of successful invocations of an action with a name indicated in the table of Fig. 4.
  • the lower two fields 402 are those for the case of releasing or pre-empting a connection of traffic being in service, functions of which are described later with exemplified applications thereof.
  • AdmitTrafficQoS() connection admittance
  • the control point 15 that received an OK response with respect to a request for connection establishment stores a traffic handle contained within TD information as a connection created by its own invocation, the TD information being received as a response.
  • the control point 15 With reference to identifying information of individual QoS devices on a path within received TD information, the control point 15 also requests subscription to a 'pre-emption' event (or a connection release event) for a device corresponding to the source of the path S335.
  • the control point 15 can request subscription to a 'pre-emption' event (or a connection release event) for each individual QoS device belonging to a path within received TD information.
  • user-requested traffic e.g., streaming of AV data is carried out between user-designated devices by additional invocation of an action by the control point 15 and/or information exchange in accordance with a relevant protocol between a traffic source and a destination device. Since the procedure also has no immediate relevance to the present invention, further description thereon is not provided.
  • While more than one connection is handling traffic transfer on a network according to the steps ranging from S331 to S335, as shown in Fig. 3B, if a connection request for the contents to be streamed is made S41 from the user through the control point 15 and a different control point 11 (it should not necessarily be a different control point; for the case of the same control point, the following description equally applies), the control point 11 configures TD information (TDk) for the connection in the same way described earlier and requests connection establishment on a QoS manager 12 that the control point 11 has selected S341. As a matter of course, before the request for connection establishment, the control point 11 inquires of the user about how to process under insufficiency of network resources.
  • TDk TD information
  • the control point 11 then chooses the QoS manager 12 equipped with 'pre-emption related capability' supporting a processing method selected according thereto by referring to the previously received information (PreemptionCapabilities) about 'pre-emption related capabilities' of all the QoS managers SS02.
  • the control point 11 can specify FCFS as a default.
  • the QoS manager 12 that received the request for connection establishment S341 assigns a traffic handle to TD information, provides the TD information for a QoS policy holder (QPH) (not shown), and requests an inquiry of priority information (e.g., UIN and/ or TIN) about a requested connection.
  • QPH QoS policy holder
  • the QoS policy holder determines priority information according to a priority determination policy or algorithm applied already thereto, fills TD information with the priority information, and returns TD information to the QoS manager 12 in response to the inquiry request. Subsequently the QoS manager 12 loads the TD information into an action, thus requesting S342 allowance of access to a network from the QoS device 13.
  • the QoS device 13 belonging to a traffic path described by the steps of S331 through S335 has been assumed to belong to a currently requested traffic path for simplicity of figures and description of the present invention, in practice the present description and figures also include the case where an arbitrary single QoS device is employed doubly on determined paths of separate traffic.
  • the QoS device 13 when it cannot accommodate service rate requested by the TD information with current bandwidth available, makes a response notifying of rejecting a connection S343. This applies equally to the case where at least one QoS device rather than all of individual QoS devices on the path cannot accommodate requested bandwidth, thereby responding by rejecting a connection.
  • the QoS manager 12 automatically carries out the procedure of pre-empting transfer resources used by an existing connection. For this purpose, the QoS device 13 first requests S344 information about connections in service from the QoS device 13 (in practice, an individual QoS device that issued 'rejection'), and obtains TD information about all the connections in service (TDl,.. ,TDn,..) from the QoS device 13 according to the request S345. The QoS manager 12 then checks priority information, namely UIN, corresponding to each obtained TD information and determines those connections having UINs lower than that of a connection that has been previously rejected for access as inferior blocking connections.
  • an inferior blocking connection or connections to be released are selected according to the selection method described with reference to Fig. 2, SS03.
  • a necessary procedure for releasing is carried out for each of selected connections.
  • description of a procedure for releasing one connection (a connection whose corresponding TD information is TDl) among the selected connections is provided.
  • a procedure for degrading service quality can be carried out instead of releasing a connection.
  • the QoS manager 12 invokes a traffic release action (ReleaseTrafficQoSQ) requesting release one (the connection of TDl) of the selected connections to the QoS device 13 (in practice on the QoS device that rejected a request for access allowance) S346.
  • the traffic release action (ReleaseTrafficQoSQ) invoked at this point has a structure as shown in Fig. 5. As shown in the figure, input arguments of 'ReleaseTrafficHandle' and 'PreemptionTrafficHandle' are loaded into a traffic release action.
  • the QoS manager 12 loads a traffic handle — which has been assigned to TDk by the QoS manager 12 — into TreemptionTRafficHandle' and loads a traffic handle recorded in TD information (TDl) selected previously for release into 'ReleaseTrafficHandle'.
  • the traffic release action (ReleaseTrafficQoSQ) is also used for the case when a connection is released through a normal procedure — for example, when release of a connection is requested from a control point by the request of the user who has established the corresponding connection — in addition to the case of releasing a connection for pre-empting to allow access of another connection as done in the step S346.
  • TreemptionTrafficHandle' which is one of input arguments shown in Fig. 5, carries an invalid handle value such as "NULL" or input argument of 'PreemptionTrafficHandle' is not contained in the action.
  • an action used for pre-empting a connection of low priority is distinguished from the name of an action used for releasing a connection in a general situation.
  • an action for pre-empting traffic uses a name of "PreemptTrafficQos". This action also has an input argument as illustrated in Fig. 5.
  • the QoS device 13 Upon invocation S346 of the traffic release action or traffic pre-emption action, the QoS device 13, according to a received action, changes the value of a connection management state variable "MostRecentStreamAction" that is under management thereof.
  • a received action is a traffic release action
  • the value of a field (ReleaseTraff ⁇ cQos) of the connection management state variable is increased by one and the values contained in an input argument (ReleaseTrafficHandle and PreemptionTrafficHandle of Fig. 5) of the action are copied to the corresponding fields (ReleaseTrafficHandle and PreemptionTraff ⁇ cHandle), respectively.
  • an invalid value such as "NULL" is recorded in the field PreemptionTrafficHandle of a connection management state variable.
  • the QoS device 13 before or along with updating the value of a connection management state variable as above, requests an operation for stopping transfer of traffic specified by an input argument ReleaseTrafficHandle of a traffic release action (or a traffic pre-emption action) from a physical transfer means.
  • connection management state variable is defined as an evented state variable
  • the QoS device 13 Since the connection management state variable is defined as an evented state variable, the QoS device 13 generates an event according to the update of the variable. If the value of PreemptionTrafficHandle has been updated, a pre-emption event (EventPreemption) is generated; if the values of ReleaseTrafficQos and ReleaseTrafficHandle have been updated with the value of PreemptionTrafficHandle intact (namely, if it is kept in the "NULL" state), a connection release event (EventRelease) is generated S336. At the occurrence of an event, a connection management state variable "MostRecentStreamAction" under management of the QoS device 13 is delivered together with the event and a device that has previously subscribed to the event becomes the object of eventing.
  • EventPreemption a pre-emption event
  • EventRelease a connection release event
  • a preemption event and a connection release event are not distinguished from each other but are generated as a single event. This is possible because a device or a control point that has received eventing can know the cause of eventing through the event and an associated connection management state variable.
  • the generated event is delivered to a control point 15 of A group that has already subscribed to the corresponding event S335.
  • the control point that has received the event first checks whether the value of ReleaseTrafficHandle within the information received through the event is already in it. Unless the value is found in it — which implies that a released connection is not the one that the control point 15 has requested for establishment — the control point 15 ignores the released connection. On the other hand, if the value is found in it, the control point 15 checks the value of PreemptionTrafficHandle in the information received through an event. If the value is "NULL" and a generated event is a 'pre-emption' event, it implies an event error and therefore, the event is ignored.
  • the control point 15 handles the event according to a normal procedure. If the value of PreemptionTrafficHandle is valid irrespective of occurrence of a pre-emption event or a connection release event, the control point 15 invokes a TD browsing action "BrowseAllTrafficDescriptorsO" S337 to an arbitrary QoS manager, e.g., the QoS manager 14 and the QoS manager 14 provides a list of TD information for the control point 15 in response to the invocation S338. The QoS manager 14, to provide the list of TD information for the control point 15, receives the list of TD information from the QoS device 13 through an action "GetQosStateO" as done in the S344 step.
  • the control point 15 that received the list of TD information searches the received list of TD information for TD information whose traffic handle field is assigned the same value as a previously checked field PreemptionTrafficHandle and provides the user with user information, traffic type and/or priority information and the like within the found TD information as the information of a pre-empting connection through a relevant UI S339. That is, a servicing connection that has been requested and allowed for access notifies of stopping of transfer services due to occupation of network resources by a different connection carrying provided information.
  • the information can be provided together with information about a pre-empted connection obtained from TD information within the received list of TD information, the TD information containing the same traffic handle as ReleaseTrafficHandle received through the generated event. For instance, a notification message such as "Your traffic transfer service having priority K( ⁇ N) has been stopped due to the network access of another traffic having priority N and requested service rate of XX Mbps! can be provided for the user.
  • the QoS device 13 carries out stopping transfer of traffic specified by an input argument ReleaseTrafficHandle of a received traffic release action S346, updating a connection management state variable, and making an OK response with respect to the received traffic release action after occurrence of an event S347.
  • the QoS manager 12 when an OK response is received with respect to the invocation of a traffic release action, requests again allowance of access from the QoS device 13 by using TD information (TDk) of a connection rejected at the previous request for allowance of access S348.
  • the QoS device 13 if it can accommodate service rate requested by active Tspec of TD information (TDk) accompanying a received access request, provides a response allowing the access S349-1 and issues an OK response to the control point 11 with respect to the traffic request action (RequestTrafficQoSQ) S341 according to the allowance response S349-2.
  • the control point 11 invokes S341 ' an action for requesting connection establishment carrying an input argument of "SelectedPreemptionRule ⁇ O.O.l" to the QoS manager 12.
  • the QoS manager 12 dose not automatically carry out an action for pre-empting an existing connection even if rejection of a request for connection establishment S342 has been received S343 from the QoS device 13.
  • the QoS manager 12 only carries out a process providing information about an existing blocking connection.
  • the QoS manager 12 issues a request for information about connections in service to the QoS device 13 S344 (actually to an individual QoS device that has been rejected) and obtains traffic information about all the connections in service from the QoS device 13 according to the request S345.
  • Traffic information obtained at the step is either TD information (TDl,.. ,TDn,..) or a traffic handle.
  • TD information can be replaced with a traffic handle when a device or a service that has received a traffic handle can obtain TD information about the traffic by specifying the corresponding traffic based on the traffic handle.
  • the QoS manager 12 provides S351 information about the corresponding connections that can be checked from each of the received TD information (e.g., type information of traffic, service rate and information about the user who has requested traffic) for the control point 11 along with a 'FAIL' response with respect to the previously requested action for connection establishment S341'.
  • the control point 11 shows the user in a proper way the fact that a request for connection establishment for a traffic transfer service issued previously by the user has been rejected and information about blocking connections occupying network resources SSIl.
  • at the time of providing information about the blocking connections S351 only the information about connections of priority lower than that of a requested connection, namely inferior blocking connections is provided instead of information about all of blocking connections occupying network resources.
  • a mediod to process insufficiency of transfer resources can have multiple options at the same time.
  • a method to process insufficiency of transfer resources can have both options of 'pre-empting an existing connection' and 'provision of information about a blocking connection'.
  • a QoS manager automatically carries out pre-emption of an existing connection and provides a control point with information about a pre-empted connection.
  • Fig. 7A illustrates a procedure of exchanging signals among devices and/or services according thereto.
  • an action for requesting connection establishment includes an input argument of "SelectedPreemptionRule ⁇ 0.1.1" S341". Since 'pre-emption of an existing connection' has been specified, the QoS manager 12 that received the action for requesting connection establishment, if a request for access to the QoS device 13 is rejected, carries out operations described with reference to Fig. 3B sequentially (that is, selection of an inferior blocking connection and release thereof and repetition of requesting access allowance). When an allowance response for the request is received from the QoS device 13, the QoS manager 12 transmits an OK response to the request for connection establishment S341".
  • PreemptedConnectionlnfo information about an inferior blocking connection determined previously to be pre-empted
  • Fig. 7A illustrates a procedure of exchanging signals among devices and/or services carried out according to the present embodiment.
  • the QoS manager 12 selects an inferior blocking connection to be pre-empted according to the specification of 'pre-emption of an existing connection' SS03.
  • information for confirming whether to pre-empt the selected connections is provided SS04 for the control point 11 in response to the previous action for connection establishment S341".
  • the response includes a response value indicating suspension of approval of the previous request for connection establishment, TD information (TDk) accompanying the initial request for connection establishment, and TD information (TDl) about a connection determined to be pre-empted.
  • the control point 11 that received the above information extracts information about a connection to be pre-empted (e.g., the user who requested traffic, service rate, and so on) from received TD information, displays the information for the user, and at the same time, inquires about whether to proceed pre-emption SS05. If the user chooses cancellation with respect to the inquiry, the entire procedure is terminated. On the other hand, if the user chooses confirmation, the control point 11, by using TD information previously received as a response SS04, configures TD information for requesting connection establishment and TD information of a connection to be pre-empted into an input argument, invoking an action for requesting pre-emption (RequestPreemptionQ) to the QoS manager 12, SS06.
  • information about a connection to be pre-empted e.g., the user who requested traffic, service rate, and so on
  • the control point 11 by using TD information previously received as a response SS04, configures TD information for requesting connection establishment and TD information of a connection
  • the QoS manager 12 receiving the action for requesting pre-emption, by using TD information (TDl) of a connection to be pre-empted accompanying the action, invokes an action for releasing traffic to the QoS device 13. If admittance ("Admitted") of a request for access allowance is received S349-1 from the QoS device 13, however, the QoS manager 12 returns a success response ("OK") with respect to the previous action for requesting pre-emption S439-2". According thereto, traffic transfer requested by the user is carried out through the QoS device 13. As a matter of course, invocation of an action necessary for the above can be added by the control point 11.
  • TD information TD information
  • control point 11 instead of receiving SS04 information for confirming whether to pre-empt connections and providing the information for the user SS05 and carrying out operations such as invoking the previous action for requesting pre-emption upon receiving confirmation of pre-emption from the user, invokes again the action for establishing a connection that is invoked for the first place for traffic transfer (RequestTrafficQoSQ) with an input argument containing TD information (TDk) of a connection whose allowance has been suspended.
  • RequestTrafficQoSQ requestTrafficQoSQ
  • 3B (S342 ⁇ S345, SS03, S346 ⁇ S348, S349-1, S349-2, and S336 ⁇ S339) are carried out as described and repeating the request for connection establishment is accommodated by pre-empting transfer resources of other connections.
  • At least one embodiment of the present invention described through a limited number of embodiments above allows the user of a network to select one method suitable for the user's current situation at the time of insufficiency of network resources, improves user convenience and allows a data service through a network, e.g., releasing a streaming service or changing service quality of the contents in an appropriate way for other transfer services of higher priority to be accommodated, thereby enabling systematic use of network resources. If a service of a connection is stopped during the above process, the user is allowed to know the cause thereof, thereby dissatisfaction factors of the user in using a network being removed beforehand.

Landscapes

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

Abstract

La présente invention concerne un procédé de traitement d'une demande d'accès à un réseau. A la réception d'une demande d'établissement d'une première connexion comportant des informations qui précisent une manière de traiter un refus d'accès, un des procédés de l'invention permet de solliciter une autorisation d'accès de la première connexion à un réseau. Si la demande d'autorisation d'accès est rejetée, le procédé est mis en œuvre pour libérer une seconde connexion conformément à la manière indiquée et solliciter à nouveau une autorisation d'accès de la première connexion, et fournir des informations sur les connexions de blocage existantes ou refuser la demande d'établissement de la première connexion.
PCT/KR2007/005002 2006-10-12 2007-10-12 Procédé de traitement d'une demande d'accès à un réseau Ceased WO2008044893A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US82926406P 2006-10-12 2006-10-12
US60/829,264 2006-10-12
US86619506P 2006-11-16 2006-11-16
US60/866,195 2006-11-16

Publications (1)

Publication Number Publication Date
WO2008044893A1 true WO2008044893A1 (fr) 2008-04-17

Family

ID=39283048

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2007/005002 Ceased WO2008044893A1 (fr) 2006-10-12 2007-10-12 Procédé de traitement d'une demande d'accès à un réseau

Country Status (1)

Country Link
WO (1) WO2008044893A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5872771A (en) * 1995-08-17 1999-02-16 Electronics And Telecommunications Research Institute Adaptive connection admission control method using traffic measurement and estimation
KR20020000653A (ko) * 2000-06-27 2002-01-05 서평원 신호망의 효율적인 트래픽 관리방법
KR20050070658A (ko) * 2003-12-30 2005-07-07 엘지전자 주식회사 3세대 패킷망에서 트래픽 전달경로의 부하 분산처리 방법

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5872771A (en) * 1995-08-17 1999-02-16 Electronics And Telecommunications Research Institute Adaptive connection admission control method using traffic measurement and estimation
KR20020000653A (ko) * 2000-06-27 2002-01-05 서평원 신호망의 효율적인 트래픽 관리방법
KR20050070658A (ko) * 2003-12-30 2005-07-07 엘지전자 주식회사 3세대 패킷망에서 트래픽 전달경로의 부하 분산처리 방법

Similar Documents

Publication Publication Date Title
EP1892882A1 (fr) Procédé pour fournir une qualité de service
US8437367B2 (en) Method for changing service quality of a content adaptively
US6363434B1 (en) Method of managing resources within a network of consumer electronic devices
US20030005130A1 (en) Audio-video management in UPnP
CN101641917B (zh) 网络资源协商
US20100005154A1 (en) Method and apparatus for obtaining information for transfer of an external content
US20060031888A1 (en) Centralized resource management and un-managed device support
JP2002540739A (ja) ネットワークにおけるリソースの管理方法及び装置
EP1671460A2 (fr) Procede et appareil pour ordonnancer les ressources dans un reseau sous-jacent commute
US20050223087A1 (en) Quality driving streaming method and apparatus
EP1897281B1 (fr) Procede et systeme permettant de fournir un service en continu (streaming) dans un reseau domestique
US8472321B2 (en) Method for managing data transfer services on a network
CN102244604B (zh) 一种家庭网关的服务质量控制方法及家庭网关及系统
US8145757B2 (en) Method for changing service quality of a content adaptively
US7872970B2 (en) Method for selecting a determinator of priority to access a network
WO2008044893A1 (fr) Procédé de traitement d'une demande d'accès à un réseau
US7328291B2 (en) System and method for controlling the service engagement in a data bus system
CN117834801A (zh) 区域间级联带宽分配方法及其系统
WO2008010673A1 (fr) Procédé de gestion de services de transfert de données sur réseau
JP4647097B2 (ja) 家庭内通信ネットワークにおいてリソースの動作をプログラミングする方法
US9391850B2 (en) Method and apparatus for quality-of-service (QoS) management
Simon et al. DIPCS: An interprocess communication architecture for distributed multimedia systems
WO2006115339A1 (fr) Procede de gestion des controles d'acces aux reseaux
MXPA00012213A (en) Domestic system resource access priority management method and device for the implementation thereof
MXPA00012221A (en) Method for programming resource actions in a domestic communication network

Legal Events

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

Ref document number: 07833313

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07833313

Country of ref document: EP

Kind code of ref document: A1