WO2011016683A2 - Procédé pour gérer un réseau et assurer une qos de service - Google Patents

Procédé pour gérer un réseau et assurer une qos de service Download PDF

Info

Publication number
WO2011016683A2
WO2011016683A2 PCT/KR2010/005140 KR2010005140W WO2011016683A2 WO 2011016683 A2 WO2011016683 A2 WO 2011016683A2 KR 2010005140 W KR2010005140 W KR 2010005140W WO 2011016683 A2 WO2011016683 A2 WO 2011016683A2
Authority
WO
WIPO (PCT)
Prior art keywords
service
qos
network
managed element
unit
Prior art date
Application number
PCT/KR2010/005140
Other languages
English (en)
Other versions
WO2011016683A3 (fr
Inventor
Jung-Min Seo
Jinkyung Hwang
Eun-Ho Choi
Sun-Jong Kwon
Eunkyoung Paik
Original Assignee
Kt Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020090126111A external-priority patent/KR101548021B1/ko
Application filed by Kt Corporation filed Critical Kt Corporation
Priority to US13/389,225 priority Critical patent/US9225615B2/en
Publication of WO2011016683A2 publication Critical patent/WO2011016683A2/fr
Publication of WO2011016683A3 publication Critical patent/WO2011016683A3/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]

Definitions

  • SNMP Simple Network Management Protocol
  • the SNMP is a protocol for information exchanged between network devices in order to manage a network.
  • a SNMP agent mounted at a router or a switch transmits a device state and a network state to a SNMP manager.
  • the SNMP manager checks a traffic amount of each port of a network device, an error state generated in data transmission, and unused ports using the information transmitted from the SNMP agent.
  • the TRAP technology is an asynchronous communication scheme that enables a SNMP agent to transmit critical network states to a SNMP manager such as when a network device is turned on and off or when a specific port becomes malfunctioned.
  • the TRAP technology is a User Datagram Protocol (UDP) based technology
  • the TRAP technology does not require acknowledgement for receiving information on network states. Due to absence of receipt acknowledgement, the TRAP technology has an unreliability problem in data transmission. Further, a man power is required to manage a network in order to manage a network according to network state information. The requirement of man power increases a network managing cost. Also, a system availability problem may be arisen because network error is not handled in real time.
  • UDP User Datagram Protocol
  • An embodiment of the present invention is directed to a network management method for automatically managing a network in real time without a network manager.
  • Another embodiment of the present invention is directed to a network management method for providing a network management service using an overlay network.
  • Another embodiment of the present invention is directed to a method for providing service QoS in an overlay network when a service is provided through an overlay network.
  • a network management methodof a network manager includes monitoring events including state information of a managed element wherein the events are published by the managed element included in a network, and generating commands for an action performed in the managed element according to the events, wherein the events are subscribed by the network manager managing the network.
  • a network management method of a managed element included in a network includes generating events for state information of the managed element, and performing operations according to commands published by a network manager, wherein the commands are generated by the network manager according to the events and the commands are subscribed by the managed element.
  • a method for providing a service QoS of an overlay network includes configuring a service QoS including a service related QoS about services performed in an overlay network and a transport related QoS, searching a service according to the service QoS using the service QoS, performing the service related QoS and transmitting the transport related QoS to a service provider that provides the service, and monitoring whether the providing of the searched service is matched with the service QoS.
  • a network management method in accordance with embodiments of the present invention provides a network management service using events transmitted or received in real time. Therefore, using the network management method in accordancewith embodiments of the present invention, a network can be automatically managed in real time without a network manager.
  • a network management service can be provided using an overlay network and Service QoS can be provided in an overlay network.
  • Fig. 1 is a diagram illustrating a network management system in accordance with an embodiment of the present invention.
  • Fig. 2 a block diagram illustrating a network management system in accordance with an embodiment of the present invention.
  • Fig. 3 is a flowchart illustrating a network management method of a network manager 101 in accordance with an embodiment of the present invention.
  • Fig. 4 is a flowchart illustrating a network management method of a managed element 103 in accordance with an embodiment of the present invention.
  • Fig. 5 is a diagram illustrating the network management methods of Figs. 3 and 4 in detail.
  • Fig. 6 is a diagram for illustrating the network management methods shown in Figs. 3 and 4 in view of a QoS.
  • Fig. 7 is a diagram illustrating a network management system in accordance with another embodiment of the present invention.
  • Fig. 8 is a flowchart illustrating a network management method of an overlay network 704 in accordance with another embodiment of the present invention.
  • Fig. 9 is a diagram for illustrating a network management method of an overlay network 704 of Fig. 8 in detail.
  • Fig. 10 is a diagram for illustrating a method for providing a service QoS in an overlay network 704 in accordance with an embodiment of the present invention.
  • Fig. 11 is a flowchart illustrating a service QoS providing method of an overlay network 704 in accordance with an embodiment of the present invention.
  • Fig. 1 is a diagram illustrating a network management system in accordance with an embodiment of the present invention.
  • the network management system in accordance with an embodiment of the present invention includes an autonomic network manager 101 and at least one of managed elements.
  • the autonomic network manager 101 generates commands for the managed elements 103 using state information on the managed elements 103.
  • the state information is asynchronously transmitted from the managed elements 103.
  • the automatic network manager 101 transmits the commands to the managed elements 103 to manage the managed elements 103.
  • the network management system in accordance with an embodiment of the present invention employs a Data Distribution Service (DDS) defined in Object Management Group (OMG).
  • the Data Distribution Service (DDS) supports a data publication/subscriptionbased communication service to provide a real time data service.
  • published or subscribed data is asynchronously transmitted or received. That is, the DDS does not transmit datain response to a data transmission request.
  • the Data Distribution Service (DDS) transmits a generated event regardless of a data transmission request.
  • the network manager 101 employs a DDS middleware.
  • the network manager 101 subscribes events published by the managed element 103.
  • the events include state information of the managed elements 103.
  • the managed element 103 also employs a DDS middleware.
  • the managed element 103 subscribes commands that are published by the network manager 101 according to an event.
  • an event asynchronouslypublished by the managed element 103 is transmitted to the network manager 101 and the command asynchronously published by the network manager 101 is transmitted to the managed element 103.
  • the network manager 101 in accordance with an embodiment of the present invention can asynchronously receive state information from the managed element 103.
  • the network manager 101 in accordance with an embodiment of the present invention can receive the state information of the managed element 103 in real time. Therefore, a network management service can be provided to the managed element 103 in real time. Further, the network manager 101 generates a command to perform a predetermined operationin the managed element 103 and transmits the generated command to the managed element 103. Therefore, an autonomic network management service can be provided for managing a network without network managers.
  • a DDS based system can set up a QoS of a transport layer according to an application service performed in a DDS based system. That is, the DDS based system can use a protocol or a communication method such as UDP, IP, and Ethernet at a transport layer and can set up a QoS according to a used transport layer.
  • the network management method in accordance with an embodiment of the present invention supports acknowledgment to data transmission or data reception between a network manager and a managed elementaccording to QoS setting regardless of a protocol of a transport layer. Also, the network management method in accordance with an embodiment of the present invention supports determining whether a managed element is in live or not according to QoS setting regardless of a protocol of a transport layer. Therefore, the networkmanagement method in accordance with an embodiment of the present invention assures the service reliability.
  • the managed element 103 performs operations according to commands published by the network manger 101. Therefore, the managed element 103 can recover from a generated fault and change system information.
  • Fig. 2 is a block diagram illustrating a network management system in accordance with an embodiment of the present invention.
  • an event published by the managed element 103 is an event subscribed by the network manager 101
  • a command published by the network manager 101 is a command subscribed by the managed element 103.
  • the network manager 101 may be mounted at a central server of a network provider providing a network. Alternately, the network manager 103 may be mounted at an additional server.
  • the network manager 101 includes a network managing unit 201, a first DDS controlling unit 213, a first QoS managing unit 215, and a first communicating unit 217.
  • the managed element 103 includes a sensor 219, an actuator 221, a second DDS controlling unit 223, a second QoS managing unit 225, and a second communicating unit 227.
  • the first and second DDS controlling units 213 and 223 set up data to be published or subscribed according to a user setting.
  • the first DDS controlling unit 213 may be set up to publish a command and to subscribe an event and the second DDS controlling unit 223 may be set up to publish an event and to subscribe a command.
  • the first and second communicating units 217 and 227 perform a communication operation for transmitting and receiving data.
  • the first and second communicating units 217 and 227 also transmit and receive events and commands.
  • the first and second communicating units 217 and 227 discover a target object to communicate, generate events and commands in a form of a message or a packet, and transmit the generated events and commands.
  • each one of the first and second communicating units 217 and 227 may include a discover unit for discovering a target object to communicate, a message generator for generating a message, and a message transceiver for transmitting and receiving a message.
  • Fig. 3 illustrates that events and commands are transmitted and received between the network managing unit 201 and a sensor and actuator 219 and 221. However, such events and commands are transferred between the first and second communicating units 217 and 227.
  • the network managing unit 201 monitors events published by the managed element 103.
  • An event includes state information of the managed element 103.
  • the state information may be performanceinformation, fault information, or system information of the managed element.
  • the network managing unit 201 generates commands for controlling a managed element according to an event.
  • the discover unit 203 may include an event discover unit, an information collector, and an information storing unit.
  • the event discover unit discovers an event published by a managed element 103.
  • the information collector collects performance information, state information, and connection information of a managed element.
  • the information storing unit stores the collected information at the database 211.
  • the analysis unit 205 may include a state analyzing unit, a policy referring unit, and an action deciding unit.
  • the state analyzing unit analyzes the current state of the managed element 103 based on the stored information.
  • the policy referring unit refers a policy stored in the database 211.
  • the action deciding unit decides an action for a managed element103 according to the current state of the managed element 103.
  • the planning unit 207 creates a management plan for a managed element 103 by generating a work flow to process an event according to the decided actionof the managed element 103, which is decided by the analysis unit 205.
  • the execution unit 209 may include a workflow executor, a command generator, and a command storing unit.
  • the workflow executor executes the workflow to call an interface of a managed element 103 using the workflow generated by the planning unit 207.
  • the command generator generates commands according to the decided action of the managed element 103.
  • the command storing unit stores a calling history and a generated command at the database 211.
  • the first and second QoS managing units 215 and 225 set up a QoS accordingto published or subscribed data or a provided service.
  • the setup QoS varies according to a transport layer. That is, the first and second QoS managing units 215 and 225 set up a QoS as a reliability QoSor as a liveness QoS.
  • the network management system provides an acknowledgement for receiving transmitted data in order to assure reliability in data transmission reliability.
  • the network management system determines whether a target object to communicate is active or not.
  • An acknowledgement (ACK/NACK) method may vary according to a network bandwidth.
  • first and second QoS managing units 215 and 225 dynamically change a QoS according to a transport layer. Therefore, applications provided from a network manager may be provided regardless of a transport layer. Moreover, a QoS can be dynamically provided according to applications.
  • the first and second QoS managing units 215 and 225 may include a QoS setup unit and a QoS processor.
  • the QoS setup unit sets up a QoS according to published or subscribed data or a service.
  • the QoS processor changes a QoS setup to a service according to a transport layer and assigns reliability to a network management system according to the setup QoS.
  • the network management system in accordance with an embodiment of the present invention, which is set up with a reliability QoS or a liveness QoS by the first and second QoS managing units 215 and 225, will be described in detail.
  • the first communicating unit 215 generates an ACK/NACK packet or a liveness packet according to a setup QoS and transmits the generated packet to a managed element 103.
  • the ACK/NACK packet is generated under the reliability QoS in order to assure reliability in data transmission.
  • the liveness packet is generated under the liveness QoS to determine whether a managed element 103 is active or not.
  • the managed element 103 In response to the ACK/NACK packet from the network manager 101, the managed element 103 transmits an acknowledgement or a non-acknowledgement (ACK/NACK) for receiving a command to the network manager 101. In response to the liveness packet from the network manager 101, the managed element 103 transmits a response message within a predetermined time (lease_duration). In case of data transmission error, the data may be retransmitted.
  • ACK/NACK acknowledgement or a non-acknowledgement
  • the second communicating unit 227 may transmit an ACK/NACK packet or a liveness packet to a network manager 101.
  • the network manager 101 may also transmit a response message for the ACK/NACK packet or the liveness packet to a managed element 103
  • the managed element 103 may include at least one of managed resources.
  • the managed resource may be a router or a switch which is required to drive application of the networkmanager 101.
  • the managed resource may be a storage which is required to form a network.
  • a sensor 219 collects state information of a managed element including managed resources and generates an event including the state information.
  • the sensor 219 may include a state collector, a fault detector, and an event generator.
  • the state collector collects state informationof a managed element 103.
  • the fault detector detects a fault generated in a managed element based on the collected state information.
  • the event generator generates an event including the state information according to the generated fault.
  • the actuator 221 performs a predetermined action according to a command of the network manager 101. Therefore, when a fault is generated in the managed element103, the managed element 103 performs a predetermined action according to a command to recover from the generated fault.
  • the actuator 221 may include a command interpreter, a fault processor, and a statesetup unit.
  • the command interpreter interprets a command.
  • the fault processor handles the fault according to the command interpretation result.
  • the state setup unit changes a system setting value according to the command interpretation result.
  • Table 1 shows events published by a managed element 103, decision of the network manager 101 according to the event, and commands published by the network manager 101.
  • Event Current state switch, NIC information such as a bandwidth and vender, port information such as the number of ports, the number of frames transmitted per each port, the number of collisions, and the number of CRC error, and buffer information such as a buffer size and the number of buffers
  • NIC information such as a bandwidth and vender
  • port information such as the number of ports, the number of frames transmitted per each port, the number of collisions, and the number of CRC error
  • buffer information such as a buffer size and the number of buffers
  • Fault a part of traffic is not processed when traffic of L2 switch increases, port information
  • Network manager When a buffer size is too small, a network manager may expand the size of the buffer. When one of ports is malfunctioned after inquiring port information of a L2 switch, a network manager transfers traffics to other ports. Commands Changing a buffer to a predetermined value. Changing a port
  • Fig. 3 is a flowchart illustrating a network management method of a network manager 101 in accordance with an embodiment of the present invention.
  • the network manager 101 generates a command for an action to be performed in the managed element 103 according toan event. That is, the network manager 101 generates a command for a necessary operation to be performed in the managed element 103 according to a state of the managed element, for example, when the managed element becomes malfunctioned or when it is necessary to change a system setup value of the managed element 103. Accordingly, the networkmanager 101 can manage and control the managed element by transmitting the generated command to the managed element 103.
  • the network manager 101 decides a predetermined action to be performed in the managed element according to a predetermined policy or the state information at step S305 and generates commands according to the decided operation at step S307.
  • the network manager 101 may provide applications of the network manager 101 regardless of a network transport layer by changing the predeterminedQoS according to a protocol of the network transport layer.
  • Fig. 4 is a flowchart illustrating a network management method of a managed element 103 in accordance with an embodiment of the present invention.
  • a managed element 103 generates events for state information of the managed element 103.
  • the managed element 103 may monitor states of the managed element 103 and generate events including state information according to the monitoring result.
  • the managed element 103 performs operations according to commands published by a network manager 101.
  • the commands are generated by the network manager 101.
  • the commands are performed in the managed element 103.
  • the commands are subscribed by the managed element 103.
  • the managed element 103 receives commands from the network manager 101 and performs operations for handling a fault state and changing a system setting, thereby managing a network.
  • the network management method in accordance with an embodiment of the present invention may further include receiving an ACK request message for receiving commands from a network manager 101 and transmitting an ACK message to the network manager 101 according to a predetermined QoS or receiving a response request message for determining whether a managed element 103 is active or not from a network manager 101 and transmitting a response to the network manger 101 according to a predetermined QoS.
  • the predetermined QoS may be set up by the managed element 103.
  • Fig. 5 is a diagram illustrating the network management methods of Figs. 3 and 4 in detail.
  • a network management service scenario in accordance with an embodiment of the present invention will be described referring to Fig. 5.
  • an event published by a managed element 103 is an event subscribed by a network manager 101.
  • a command published by the network manager 101 is a command subscribed by the managed element 103.
  • a sensor 219 monitors a changed state and a fault state of managed resources included in a managed element 103.
  • the managed element 103 informs the sensor 219 of the monitoring result such as the changed state and the fault state of the resources included the managed element 103.
  • the sensor 219 generates an event including state information using the monitoring result.
  • a discover unit 203 discovers the generated event.
  • the discover unit 203 collects the state information.
  • a database 211 stores the collected state information.
  • the database 203 requests an analysis unit 205 to analyze the state information.
  • the analysis unit 205 requests a policy to the database 211.
  • the analysis unit 205 receives the requested policy from thedatabase 211.
  • the analysis unit 205 decides an action, which is a predetermined operation performed in a managed element, using the analysis result and the policy.
  • the analysis unit 205 requests a planning unit 207 to send a plan.
  • the planning unit 207 generates a workflow according to the plan in responseto the request from the analysis unit 205.
  • the planning unit 207 requests an execution unit 209 to execute the workflow.
  • the execution unit 209 generates commands according to the workflow.
  • the actuator 211 stores a calling history for an interface to the database 211.
  • the actuator 221 interprets the commands and performs predetermined operations according to the commands.
  • Fig. 6 is a diagram for illustrating the network management methods shown in Figs. 3 and 4 in view of a QoS.
  • a QoS required at a transport layer may be set up through applications performed in a network manager 101 and a managed element 103.
  • an event published by a managed element 103 is an event subscribed by the network manager 101.
  • a command published by a network manager 101 is a command subscribed by a managed element 103.
  • a reliability QoS and a liveness QoS are set up to guarantee reliability in data transmission between a network manager 101 and a managed element 103 and to confirm whether a target object to communicate is active or not.
  • the first and second QoS managing units 215 and 225 may set up a QoS when the network manager 101 and the managed element 103 publish and subscribe events and commands.
  • the network manager 101 and the managed element 103 transmit and receive an ACK/NACK packet or a liveness packet according to the setup QoS. Further, the network manager 101 and the managed element 103 transmit and receive a response of the ACK/NACK packet and the liveness packet.
  • the sensor 219 monitors a changed state or a fault state of managed resources.
  • the sensor 219 receives a changed state notice and a fault state notice from the managed resources.
  • the sensor 219 transfers events including state information of managed resources to the second communicating unit 227 and the second communicating unit 227 generates a communication packet according to a QoS.
  • the communication packet includes an event, an ACK/NACK packet, and a liveness packet.
  • the second communicating unit 227 transmits the communication packet to the first communicating unit 217 and receives a response thereof from the first communicating unit 217.
  • the first communicating unit 217 transfers an event to the network managing unit 201 in order to transmit the event to the managed element 103.
  • the network managing unit 201 generates commands for the managed elemetn1 03.
  • the first communicating unit 217 generates a communication packet including the command from the network managing unit 201 according to a QoS.
  • the communication packet includes a command, an ACK/NACK packet, and a liveness packet.
  • the first communicating unit 217 transmits the communication packet to the second communicating unit 227 and receives a response thereof from the second communicating unit 227 at step S623.
  • the second communicating unit 227 transmits a command to the actuator 221.
  • the actuator 221 performs a predetermined operation according to the command.
  • the communication packet may be operation, administration, and maintenance (OAM) packets.
  • OAM operation, administration, and maintenance
  • a network management service provided by a network manager may be provided by a network device or a dedicated service provider according to a service. That is, a network provider that provides a network may directly provide a network management service using a network manager. Further, a network device or a dedicated service provider may provide a network management service according to a service.
  • the network management service may be provided as a web service at an open platform environment such as web 2.0. Particularly, the network management service may be provided using an overlay network.
  • an overlay network a network management method using an overlay network will be described in detail.
  • the overlay network 704 selects a service among network management services provided from a service provider according to a predetermined service QoS in responseto a request of the network manager 701.
  • a service discovered according to a request of the network manager may be a composition service combined with a plurality of basic services.
  • the overlay network704 selects a composition service according to a service QoS and selects a plurality of basic services included in the composition service according to a service QoS.
  • the overlay network 704 may select a service additionally using context information about a service.
  • the overlay network 704 provides the selected service to the network manager 701.
  • the overlay network 704 requests a pluralityof selected basic services to a service provider and provides a network management service to the network manager 701 by performing a network management service published by the service provider in response to the request.
  • the overlay network 704 performs a service QoS and monitors whether or not the service provided from the network manager 701 is satisfied by the service QoS.
  • the network management service may be provided to an overlay network through publishing the network management service from a service provider of a low-level network as described above.
  • Fig. 9 is a diagram for illustrating a network management method of an overlay network 704 of Fig. 8 in detail. Referring to Fig. 9, a network management service scenario in according to an embodiment of the present invention will be described in detail.
  • the network manager 701 subscribes a fault event related to a fault state of the managed element 703, which is published from the managed element 703.
  • the service publication and directory unit 705 provides the selection result to the service composition unit 707.
  • the service composition unit 707 requests the service policy decision function 713 to control a service QoS.
  • the service composition unit 707 requests a basic service to the service provider 901.
  • the service provider 901 provides a basic service to the service composition unit 707.
  • the service provider provides the result of performing the basic service to the network manager 701.
  • Fig. 10 is a diagram for illustrating a method for providing a service QoS in an overlay network 704 in accordance with an embodiment of the present invention.
  • the service QoS providing method of the overly network 704 of Fig. 10 may be applied not only to the above described network management system but also a system or a method providing other network service.
  • a service requester requests service QoS configuration to a service publication and directory unit 705.
  • service QoS information may be newly created or modified.
  • the service QoS may be described in a service level agreement (SLA).
  • the service publication and directory unit 705 stores the configured service QoS.
  • the service QoS may be stored in a database.
  • the service publication and directory unit 705 transmits a response according to success or failure in the service QoS configuration to the service requester. In case of the service QoS configuration failure, error information is transmitted to the service requester.
  • a service requester requests the service publication and directory unit 705 to discover a service to according to a predetermined service QoS.
  • the service publication and directory unit 705 requests service QoS related context information to the context-aware unit 709.
  • the service publication and directory unit 705 searches a service according to a service QoS.
  • the service publication and directory unit 705 generates a query based on the service QoS and sends the generated query to the data base storing services.
  • the service publication and directory unit 705 transmits the search result to the service requester. That is, the service publication and directory unit 705 transmits a response according to success or failure in searching a requested serviceto the service requester. In case of the failure, error information is transmitted to the service requester.
  • a service requester requests a service policy decision function 713 to perform a service QoS.
  • the service policy decision function 713 classifies QoS into a service related QoS about services performed in the overlay network 704 and a transport related QoS in order to satisfy a general service QoS. That is, the service policy decision function 713 may convert the service related QoS to the transport related QoS.
  • the service policy decision function 713 performs the service related QoS performed in the overlay network 704.
  • the service policy decision function 713 transfers the transport related QoS to a service provider that provides services performed in the overlay network 704. That is, the transport related QoS information is transferred to the service provider.
  • a service requester requests a service policy decision function 713 to monitor a service QoS.
  • the service policy decision function 713 monitors a service QoS, collects and analyzes the monitoring result. That is, the service policy decision function 713 monitors whether the provided service is matched witha service QoS or not.
  • the service policy decision function 713 applies a predetermined QoS policy when a provided service is not satisfiedaccording to a service QoS. That is, the service policy decision function 713 monitors whether the provided service is matched with the service QoS or not according to the predefined QoS. The service policy decision function 713 performs a service related QoS again and transmits the transport related QoS to the service provider when the QoS policy is applied.
  • the service policy decisionfunction 713 transmits the monitoring result to the service requester. That is, the service publication and directory unit 705 transmits a response according to success or failure in monitoring to the service requester. In case of monitoring failure, error information is transmitted to the service requester.
  • the overlay network 704 configures a service QoS including a service related QoS about services performed in an overlay network 704 and a transport related QoS.
  • the overlay network 704 may configure a service QoS according to a request of a service requester that is provided with a service from the overlay network 704.
  • the overlay network 704 searches services according to theservice QoS using the service QoS.
  • the overlay network 704 may search services additionally using context information about a service QoS.
  • the overlay network 704 performs a service related QoS about services performed at the overlay network 704 and transmits a transport related QoS to a service provider. Since a service is provided to the service requester through the overlay network 704, it is required to convert a part of the service QoS to the transport related QoS.
  • the service provider may be a low-level network of the overlay network 704.
  • the overlay network 704 monitors whether the provided service is matched with the service QoS and a QoS for the overlay network 704.
  • the overlay network 704 monitors and confirms whether the overlay network 704 satisfies the service QoS or not.
  • the overlay network 704 may monitor whethera provided service searched according to the predetermined QoS policy is matched with a service QoS or not when the searched service is not matched with the service QoS.
  • the service QoS providing method of the overlay network 704 of Fig. 11 may be applied to the network management method using the overlay network.
  • the service provided at the step S1107 is published by the network managed element.
  • the service may includeat least one of a service for monitoring events for state information of the managed element, a service analyzing a state of the managed element according to an event, a service generating flowchart according to an operation performed in the managed element, and a service for generating commands for the operation performed in the managed element according to the flowchart.

Landscapes

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

Abstract

L'invention concerne un procédé de gestion de réseau mis en œuvre par un gestionnaire de réseau. Le procédé de gestion de réseau comporte les étapes consistant à surveiller des évènements comprenant des informations d'état d'un élément géré, les évènements étant publiés par l'élément géré appartenant à un réseau, et à générer des commandes d'action à réaliser au niveau de l'élément géré en fonction des évènements, lesdits évènements faisant l'objet d'un abonnement de la part du gestionnaire de réseau qui gère le réseau.
PCT/KR2010/005140 2009-08-06 2010-08-05 Procédé pour gérer un réseau et assurer une qos de service WO2011016683A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/389,225 US9225615B2 (en) 2009-08-06 2010-08-05 Method for managing network and for providing service QoS

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR20090072495 2009-08-06
KR10-2009-0072495 2009-08-06
KR20090077203 2009-08-20
KR10-2009-0077203 2009-08-20
KR1020090126111A KR101548021B1 (ko) 2009-08-06 2009-12-17 네트워크 관리 방법
KR10-2009-0126111 2009-12-17

Publications (2)

Publication Number Publication Date
WO2011016683A2 true WO2011016683A2 (fr) 2011-02-10
WO2011016683A3 WO2011016683A3 (fr) 2011-06-23

Family

ID=43544793

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2010/005140 WO2011016683A2 (fr) 2009-08-06 2010-08-05 Procédé pour gérer un réseau et assurer une qos de service

Country Status (1)

Country Link
WO (1) WO2011016683A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105357034B (zh) * 2015-10-20 2018-11-20 广州海格通信集团股份有限公司 基于snmp的叶子节点创建装置和通信方法及系统

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090076719A (ko) * 2008-01-09 2009-07-13 주식회사 대우일렉트로닉스 피어투피어 오버레이 네트워크 환경에서의 콘텐츠 공유시스템 및 그 방법

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090076719A (ko) * 2008-01-09 2009-07-13 주식회사 대우일렉트로닉스 피어투피어 오버레이 네트워크 환경에서의 콘텐츠 공유시스템 및 그 방법

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
S.W. KIM ET AL: 'Adaptive overlay network management algorithms for QoS sensitive multimedia services' IJIPS vol. 14-C, no. 1, February 2007, *
TUTOMU MURASE ET AL: 'Overlay network technologies for QoS control' IEICE TRANS. COMMUN. vol. E89-B, no. 9, September 2006, *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105357034B (zh) * 2015-10-20 2018-11-20 广州海格通信集团股份有限公司 基于snmp的叶子节点创建装置和通信方法及系统

Also Published As

Publication number Publication date
WO2011016683A3 (fr) 2011-06-23

Similar Documents

Publication Publication Date Title
US9225615B2 (en) Method for managing network and for providing service QoS
WO2015072709A1 (fr) Procédé de commande de contrôleur et de commutateur pour reprise après défaillance du réseau à partir d'une sdn, et contrôleur et commutateur correspondants
WO2012030190A2 (fr) Système et procédé de gestion de ressources dans un système de communication
WO2020032769A1 (fr) Procédé et dispositif de gestion de trafic de réseau dans un système de communication sans fil
WO2014010992A1 (fr) Procédé de communication entre un demandeur de contenu et un fournisseur de contenu pour fournir un contenu et diffuser en continu, en temps réel, un contenu dans un réseau centré sur le contenu et basé sur un nom de contenu
WO2022005170A1 (fr) Procédé et dispositif d'interfonctionnement entre un réseau de communication mobile et un système informatique de bord pour fournir un service informatique de bord
WO2015030491A1 (fr) Procédé de fourniture de bande passante sur la base d'un groupement de plusieurs flux
WO2021141291A1 (fr) Procédé et appareil de collecte de trafic réseau dans un système de communication sans fil
KR20150068317A (ko) Ｓｄｎ 환경에서 네트워크 장치에 대한 장애를 처리하는 방법
WO2016003234A1 (fr) Procédé et dispositif pour recevoir et transmettre des informations dans un système multimédia
JP5282628B2 (ja) ネットワーク監視制御装置及び監視制御方法
WO2017131285A1 (fr) Système de gestion de réseau conteneur et procédé de mise en réseau conteneur
WO2015080525A1 (fr) Procédé et appareil destinés à la régulation dynamique du trafi dans un environnement sdn
WO2018008933A1 (fr) Procédé pour fournir un service de cpe virtuel à l'aide d'une seule ligne internet et d'un nuage de virtualisation de fonction de réseau
WO2020027378A1 (fr) Contrôleur sdn basé sur un réseau défini par logiciel, et système d'ingénierie de trafic et procédé d'ingénierie de trafic l'utilisant
WO2011016683A2 (fr) Procédé pour gérer un réseau et assurer une qos de service
US10191465B2 (en) Monitoring and control system and monitoring and control method
WO2015002436A1 (fr) Procédé et appareil permettant d'optimiser un trajet de données dans un système de communications mobiles
WO2015065003A1 (fr) Procédé de contrôle de qos via une gestion de trafic dépendant du service
WO2015088268A1 (fr) Procédé de traitement de défaillance de dispositif de réseau dans un environnement de réseautage défini par logiciel (sdn)
WO2022092632A2 (fr) Procédé de découverte de créneau et de trajet de transmission basé sur un décalage pour une transmission de trafic à faible latence de bout en bout périodique, et dispositif de commande le mettant en œuvre
WO2022039359A1 (fr) Dispositif de commande d'intégration de bord et procédé de fonctionnement d'un dispositif de commande d'intégration de bord
WO2012150778A2 (fr) Procédé et un appareil de gestion d'une connexion entre des objets de communication basée sur un événement de confirmation d'état de connexion
WO2022102949A1 (fr) Serveur de configuration de bord, serveur de validation de bord et procédé de commande associé
WO2015080512A1 (fr) Procédé pour traiter un événement entre un dispositif de commande et un dispositif de réseau

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

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 13389225

Country of ref document: US

122 Ep: pct application non-entry in european phase

Ref document number: 10806657

Country of ref document: EP

Kind code of ref document: A2