[go: up one dir, main page]

WO2008010673A1 - Procédé de gestion de services de transfert de données sur réseau - Google Patents

Procédé de gestion de services de transfert de données sur réseau Download PDF

Info

Publication number
WO2008010673A1
WO2008010673A1 PCT/KR2007/003490 KR2007003490W WO2008010673A1 WO 2008010673 A1 WO2008010673 A1 WO 2008010673A1 KR 2007003490 W KR2007003490 W KR 2007003490W WO 2008010673 A1 WO2008010673 A1 WO 2008010673A1
Authority
WO
WIPO (PCT)
Prior art keywords
connection
traffic
information
received
event
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/003490
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 WO2008010673A1 publication Critical patent/WO2008010673A1/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/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H04L47/762—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the network
    • 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

Definitions

  • the present invention is related to a method for managing content transfer services through a home network such as the one based on UPnP.
  • UPnPTM (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.
  • multiple CPs can exist on a UPnP network and the user can control operations on a desired service by choosing a convenient
  • 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/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
  • multiple users can share the same device at the same time, in the same place.
  • required quantity of data transmission may exceed transmission bandwidth provided by a network. In this case, network access for data transmission should be restricted.
  • One objective of the present invention is to provide a method for managing traffic transfer services, the method, when available bandwidth is not sufficient for a new connection, retrieving resources for transfer service of the content being serviced in an optimal way and allocating the resources to a new connection.
  • Another objective of the present invention is to provide a method for informing the user of transfer resources retrieved after management of transfer service resources about the status of traffic transfer services, from which the cause of the retrieval can be identified.
  • One method for managing traffic transfer services on a network comprises requesting access allowance of a new connection to a network, determining a blocking connection to be released from among existing connections in service if access allowance of the new connection is rejected, and invoking an action for requesting release of the determined blocking connection, the action having an input argument carrying information identifying the new connection.
  • Another method for managing traffic transfer services on a network comprises setting a state variable for managing connections, where the state variable includes fields for recording identifying information for connections to be released and identifying information for pre-empting connections, and when an action for requesting release of a blocking connection is received, registering identifying information of a new connection received from the action in the identifying information field for pre-empting connections within the state variable and generating an event notifying of the change of the state variable.
  • Another method for managing traffic transfer services on a network comprises preparing traffic descriptor at the user's request for establishing a connection to a network and invoking a request for connection establishment along with the traffic descriptor; when a success response to the invocation is received, requesting an event subscription to at least one of devices or services identified by connection path information received together with the success response and storing traffic handles within the traffic descriptor received together with the success response; and when an event occurs, checking whether a first traffic handle received through the event is contained in the stored traffic handles and if contained, obtaining connection information specified by a second traffic handle received through the occurred event.
  • the information identifying a new connection is a traffic handle assigned to a traffic descriptor generated with respect to the new connection.
  • the action for requesting release of the determined blocking connection also includes information identifying the determined blocking connection in an input argument and the information identifying the determined blocking connection is a traffic handle assigned to a traffic descriptor generated with respect to the blocking connection.
  • the device or service if a device or a service carrying out the steps of requesting access allowance of a new connection to a network, selecting a blocking connection, and invoking an action for requesting release of a blocking connection receives a success response after requesting access allowance of an arbitrary connection, the device or service informs a control application that requested establishment of the connection about path information of the connection.
  • the path information of a connection comprises a list of UDN (Unique Device Name) and service ID of each device or service participating in transfer of traffic due to the corresponding connection.
  • the event generating step if an action for requesting release of an arbitrary connection does not contain information identifying a different connection other than the arbitrary connection, records an invalid value in the identifying information field for pre-empting connections and generates an event notifying of change of the state variable. At this moment, a field value indicating the number of successfully released connections within the state variable is increased.
  • a process is carried out to notify that a connection specified by the first traffic handle has been released, at least along with part of connection information specified by the obtained second traffic handle.
  • the step of subscribing to an event and storing a traffic handle within traffic descriptor received along with a success response requests event subscription to only a device or service corresponding to a source among devices or services identified by the received connection path information.
  • the event subscription is subscription to an event notifying of occurrence of pre-empting a connection. In another embodiment according to the present invention, the event subscription is subscription to an event notifying of occurrence of releasing a connection.
  • Fig. 1 illustrates a flow diagram of releasing a servicing connection for content according to one embodiment of the present invention
  • Fig. 2 illustrates a method for selecting a connection to be released according to one embodiment of the present invention
  • Fig. 3 illustrates a signal exchange procedure among devices or services for releasing a servicing connection for content according to one embodiment of the present invention
  • Fig. 4 illustrates a structure of a state variable defined for a device or a service that carries out actual transfer of traffic to manage connections according to one embodiment of the present invention
  • Fig. 5 illustrates a structure of an action for releasing a connection used for pre-empting a connection for traffic according to one embodiment of the present invention. 5. Best Mode for Carrying Out the Invention
  • ⁇ TD information' information which describes traffic conducting the transfer (which is also called as traffic descriptor and from now on, is referred to as ⁇ TD information' for short) is delivered to a manager that processes/manages requests for allowance of access.
  • 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, 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 v Tspec information') .
  • Tspec information includes information about service rate required for streaming of traffic of particular service quality.
  • Fig. 1 illustrates one example of a flow diagram regarding to the above.
  • SIl a request for allowance of access to a network
  • 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 (S12) .
  • a request for a new connection is accepted (Sl ⁇ ) , otherwise 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 (S13) . If the former is larger than the latter, a current servicing connection (s) is released (S14), otherwise the newly requested connection is rejected (S19) .
  • service quality of the connection can be degraded. Retrieved bandwidth is calculated by difference between original bandwidth and degraded bandwidth and connections to degrade are selected according to sum of the calculated bandwidth.
  • 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.
  • UIN User Importance Number
  • 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.
  • 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 B, 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) .
  • the selected connections (among connections, each UIN of which is lower than a determined pre-emption reference, 30)
  • Network resources for finally selected connections are pre-empted and used for a new connection.
  • finally selected connections are released (S23c) and a newly requested connection (connection E) is accommodated.
  • Fig. 3 illustrates a signal exchange procedure among devices according to one embodiment of the present invention for allowing connections for transfer services and at the lack of transfer resources, releasing an inferior blocking connection being in service .
  • the control point 15 configures TD information for the connection and requests (S31) connection establishment from an arbitrary QoS manager 14.
  • S31 connection establishment from an arbitrary QoS manager 14.
  • QoS manager 12 in the figure can also be used for this purpose .
  • 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 source and 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
  • Service ID 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 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 5 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
  • an action for requesting allowance of access to a network (AdmitTrafficQoS () ) is invoked on each individual QoS device on the path (including individual QoS devices at the source and destination) (a QoS device 13 in the example of Fig. 3) by loading the returned TD information
  • the QoS device 13 of Fig. 3 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
  • x 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'.
  • 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
  • Identifying information about individual QoS devices on a path can also be filled into the TD information when access allowance to the QoS device 13 is invoked (S33) .
  • 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 ( )
  • AdmitTrafficQoS ( ) connection admittance
  • the field value of AdmitTrafficQos is increased by one and accordingly, an event is generated as the value has been changed.
  • a device or a control point that is subscribed to the corresponding event receives the event and carries out a relevant procedure. Since the procedure has no immediate relevance to the present invention, further description thereon is not provided.
  • 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 (S35) .
  • 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.
  • connection request for the content 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 (S41) .
  • the QoS manager 12 that received the request assigns a traffic handle to TD information, provides the TD information for a QoS policy holder (QPH) (not shown) , and requests 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 .
  • the QoS manager 12 loads the TD information into an action, thus requesting (S42) allowance of access to a network on the QoS device 13.
  • S42 requesting
  • the QoS device 13 belonging to a traffic path described by the steps of S31 through S35 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 not admitting a connection (S43) . 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 not admitting a connection.
  • the QoS manager 12 When a request for connection allowance is rejected (when ⁇ no admittance' is received from at least one individual QoS device) , the QoS manager 12 requests information about servicing connections from the QoS device 13 (in practice, an individual QoS device that issued 'no admittance') (S44) , and obtains TD information about all the servicing connections (TDl, .. ,TDk, ..) from the QoS device 13 according to the request (S45) . 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.
  • priority information namely UIN
  • an inferior blocking connection or connections to be released are selected according to the selection method described with reference to Fig. 2 (SSl) .
  • 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 (ReleaseTrafficQoS () ) requesting release one (the connection of TDl) of the selected connections on the QoS device 13 (in practice on the QoS device that rejected a request for access allowance) (S46) .
  • the traffic release action (ReleaseTrafficQoS ()) 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 ⁇ PreemptionTRafficHandle' and loads a traffic handle recorded in TD information (TDl) selected previously for release into v ReleaseTrafficHandle' .
  • the traffic release action (ReleaseTrafficQoS ()) 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 S4 ⁇ .
  • 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 S4 ⁇ .
  • PreemptionTrafficHandle ' 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 (S46) 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. For example, since a received action is a traffic release action, the value of a field (ReleaseTrafficQos) 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 PreemptionTrafficHandle) , respectively. This applies equally to the case when a traffic pre-emption action (PreemptTrafficQoS () ) is used. Unless an input argument of
  • PreemptionTrafficHandle is contained in a received traffic release action, 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) on 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 (Event : Preemption) 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 (Event : Release) is generated (S36) .
  • Event Preemption
  • 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.
  • 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 S35.
  • 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 being a pre-emption event or a connection release event, the control point 15 invokes a TD browsing action "BrowseAllTrafficDescriptors ( ) " (S37) on 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 (S38) . 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 "GetQosState () " as done in the S44 step.
  • a TD browsing action "BrowseAllTrafficDescriptors ( ) " (S37) on an arbitrary QoS manager, e.g., the QoS manager 14 and the QoS manager 14 provides a list of TD information for the control
  • 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 (S39) . That is, a servicing connection that has been requested and allowed for access notifies of stopping of transfer service due to occupation of network resources by a different connection having provided information.
  • ReleaseTrafficHandle is needed e.g., when user priority information is needed, 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 .
  • 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 XX Mbps ! " can be provided for the user.
  • the user using transfer service e.g., watching streaming content can know the cause of suspension of screen display and if necessary, the user can again request content streaming in low quality, thereby being able to use transfer service within the allowed limit of network resources .
  • the QoS device 13 carries out stopping transfer of traffic specified by an input argument ReleaseTrafficHandle of a received traffic release action (S46) , updating a connection management state variable, and making an OK response with respect to the received traffic release action after occurrence of an event (S47) .
  • 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 on the QoS device 13 by using TD information (TDk) of a connection rejected at the previous request for allowance of access (S48) .
  • TDk TD information
  • 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 (S49-1) and issues an OK response to the control point 11 with respect to the traffic request action
  • At least one embodiment of the present invention described through a limited number of embodiments above allows data service through a network, e.g., releasing streaming service or changing service quality of the content in an appropriate way for other transfer services of higher priority to be accommodated, thereby enabling systematic use of network resources. If 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

L'invention concerne un procédé de gestion de services de transfert de trafic sur réseau. Un des procédés de l'invention consiste: à demander une autorisation d'accès d'une nouvelle connexion à un réseau; à sélectionner la connexion à libérer parmi les connexions de blocage en service en cas de rejet de la demande d'autorisation d'accès; et enfin, à appeler à une action en vue de libérer la connexion de blocage sélectionnée. L'action appelée présente un argument d'entrée qui comporte des informations d'identification de la nouvelle connexion. Selon l'action appelée, la connexion de blocage appelée est réquisitionnée.
PCT/KR2007/003490 2006-07-19 2007-07-19 Procédé de gestion de services de transfert de données sur réseau Ceased WO2008010673A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US83226406P 2006-07-19 2006-07-19
US60/832,264 2006-07-19
US84475606P 2006-09-15 2006-09-15
US60/844,756 2006-09-15

Publications (1)

Publication Number Publication Date
WO2008010673A1 true WO2008010673A1 (fr) 2008-01-24

Family

ID=38956972

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2007/003490 Ceased WO2008010673A1 (fr) 2006-07-19 2007-07-19 Procédé de gestion de services de transfert de données sur réseau

Country Status (1)

Country Link
WO (1) WO2008010673A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6141322A (en) * 1997-05-09 2000-10-31 General Datacomm, Inc. Method and apparatus for precedence and preemption in ATM connection admission control
US6735176B1 (en) * 1998-03-26 2004-05-11 Nortel Networks Limited Dynamic bandwidth management and rerouting

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6141322A (en) * 1997-05-09 2000-10-31 General Datacomm, Inc. Method and apparatus for precedence and preemption in ATM connection admission control
US6735176B1 (en) * 1998-03-26 2004-05-11 Nortel Networks Limited Dynamic bandwidth management and rerouting

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
GUOQIANG MAO AND HABIBI D.: "Connection admission control - closing the loop", NETWORKS, 2003. ICON2003. THE 11TH IEEE INTERNATIONAL CONFERENCE, 28 September 2003 (2003-09-28) - 1 October 2003 (2003-10-01), pages 373 - 378, XP010683549, DOI: doi:10.1109/ICON.2003.1266219 *

Similar Documents

Publication Publication Date Title
US8437367B2 (en) Method for changing service quality of a content adaptively
JP3145083B2 (ja) 伝送システム，帯域管理装置，および帯域管理方法
EP1892882A1 (fr) Procédé pour fournir une qualité de service
CN101641917B (zh) 网络资源协商
US20100005154A1 (en) Method and apparatus for obtaining information for transfer of an external content
US20050076336A1 (en) Method and apparatus for scheduling resources on a switched underlay network
KR20040014993A (ko) 시간 민감 정보의 통신 시스템
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
JP2005526452A (ja) 品質駆動するストリーミング方法及び装置
US8145757B2 (en) Method for changing service quality of a content adaptively
US7872970B2 (en) Method for selecting a determinator of priority to access a network
JP2001156838A (ja) 通信リソース予約方法及び装置並びに通信リソース予約プログラムを記録した記録媒体
CN101156379B (zh) 一种选择服务质量策略的方法及系统
EP1317109B1 (fr) Système et procédé pour contrôler l'adaptation des applications multimédia distribuées adaptatives
WO2008010673A1 (fr) Procédé de gestion de services de transfert de données sur réseau
JP6248497B2 (ja) コンテンツ配信制御システム、転送装置、配信制御装置、視聴制御装置、転送プログラム、配信制御プログラム及び視聴制御プログラム
US5778056A (en) Broadband network and method for connecting information providers
US20040105436A1 (en) System and method for controlling the service engagement in a data bus system
WO2008044893A1 (fr) Procédé de traitement d'une demande d'accès à un réseau
WO2005099175A1 (fr) Procede et appareil permettant la compatibilite avec la multidiffusion de donnees audiovisuelles dans un reseau
JP2003108393A (ja) ビデオストリーム送信プロセスの負荷分散方法及びその装置と負荷分散プログラムと該プログラムを記録した記録媒体
KR100765321B1 (ko) 보장된 큐오에스를 제공하는 브이오디 시스템 및 그 방법
WO2006115339A1 (fr) Procede de gestion des controles d'acces aux reseaux
EP0894395A1 (fr) Methode et dispositif pour delivrer des informations et des services d'identification de l'appelant

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: 07793211

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 07793211

Country of ref document: EP

Kind code of ref document: A1