JP4662445B2 - Streaming service management program and method - Google Patents

Description

  The present invention relates to a streaming service management system, and more particularly to an additional service and a method thereof in a video distribution service, and particularly to a service suitable for fault management of the video distribution service.

  In recent years, with the spread of broadband networks, video distribution services such as sports broadcasts and concerts are spreading. The video distribution system includes a display client that normally displays video to a user, a distribution server that transmits video, and a distribution manager that receives a request from the user, determines an appropriate distribution server, and issues a distribution request. . The key technologies in the video distribution system are a signaling technology for video requests and a video distribution technology.

  In recent years, RTSP (Real Time Streaming Protocol) described in RFC2326 and SIP (Session Initiation Protocol) described in RFC2543 have attracted attention as signaling technologies. RTSP is a control protocol specialized for video distribution control, and control commands such as distribution, stop, fast forward, and rewind of video content are defined in advance.

  On the other hand, SIP is a general-purpose protocol for so-called multimedia session control, and basic commands such as session establishment, disconnection, and transfer are defined. However, extension according to the control target is usually required. . Currently, this technology is mainly used for IP telephone signaling.

  Here, the feature of SIP will be supplemented. In general, the response time (corresponding to the ringing time) from the destination server is long for telephones. Therefore, taking into consideration the possibility that the status of the source client has changed during this period, the status mismatch between the client and server In order to prevent it as much as possible, the system is characterized by a three-way handshake method in which a request (INVITE) is sent to the server, and the client that receives the response (OK) returns the response (ACK). In SIP, other messages such as stream session change and status notification are defined.

  On the other hand, multicast transfer using RTP (Real Time Protocol) is widely used as a video distribution technique. RTP stores the time that the video should be displayed in the packet storing the video information, and the client that has received the RTP packet can buffer or wait until the time to display is reached. The process of disposal is performed.

  Further, as a protocol used together with RTP, there is RTCP (RTP Control Protocol). In this case, the transmission server periodically notifies the display client of a transmission rate (sender report), and conversely the display client notifies the distribution server of a reception rate notification (receiver report). Supplementing the relationship between RTSP and SIP, and RTP and RTCP, the former is a protocol for starting and stopping the delivery of a stream, and the latter is a relationship for controlling the stream traffic itself.

  FIG. 29 is a block diagram showing a configuration example of a conventional system. In the figure, 10 is a streaming service provider that distributes video, and 20 is a communication provider that is connected to the streaming service provider 10. The streaming data distribution means 11 in the streaming service provider 10 distributes the streaming data to the communication provider 20. In the figure, only two streaming data delivery means 11 are shown, # 1 and # 2, but this number need not be limited.

  Within the communication carrier 20, a router (node) 21 receives distribution data from the streaming data distribution unit 11 and routes it. Reference numeral 22 denotes network state management means connected to the router 21, and 23 denotes network configuration information storage means connected to the network state management means 22. Streaming data via the communication carrier 20 is delivered to the streaming data display means 1. Here, only two units # 1 and # 2 are shown as streaming data display means, but it is not necessary to limit to this number.

Conventional techniques of this kind include means for obtaining fault information from a network device, fault information communication means for communicating fault information via a fault information dedicated line communicated via the network, and faults communicated There is known a system that includes a failure management server that receives and analyzes information and can flexibly cope with troubles without degrading the performance of a network environment (see, for example, Patent Document 1).
JP 2002-111782 (paragraphs 0029 to 0034, FIG. 2)

  RTP is generally transferred over UDP (User Data Protocol). Since UDP is a protocol that does not guarantee the arrival of data packets and does not monitor connection, there is a problem that even if a failure occurs in the relay network, the distribution server cannot detect it.

  However, if RTCP is used, the distribution server can detect a failure between display clients by monitoring the arrival of the receiver report. However, since a large number of display clients are connected to one distribution server and so many receiver reports arrive, the distribution server generally does not process the receiver reports.

  In addition, even if processing is performed, the receiver report notification interval is relatively long, so it takes time to make a decision, and it is difficult to provide additional services such as prompt failure notification to the user and to determine the time when the failure occurred. There was a problem.

  When the distribution is interrupted due to a failure of the relay network or the like, the display client requests the distribution manager or the distribution server to redistribute the current data from the point of the interruption. If the distribution manager or distribution server is a redistribution request from the point where it was interrupted based on the request, after generating a new stream and distributing the data, the distribution manager or distribution server notifies the display client of the address and port, and the current data is regenerated. If it is a distribution request, a process of notifying the currently distributed address and port is performed.

  At this time, since the transmission timing of the redistribution request from the point where it was interrupted does not match at the display client, a large number of redistribution requests arrive at different timings due to failure of one relay network, so a lot of distribution traffic is generated There was a problem of being.

  In summary, in the streaming service using RTP, the distribution server cannot detect the failure of the network, and even if it can be detected, it takes time to detect and it is difficult to determine the time of occurrence of the failure. For this reason, additional services such as data retransmission from the failure occurrence time at the time of failure recovery could not be provided. Furthermore, when a plurality of redistribution requests arrive at different timings, there is a problem that a lot of distribution traffic is generated and bandwidth is consumed.

  The present invention has been made in view of such problems, and in a video distribution system using SIP and RTP, a failure of a relay network can be quickly and accurately handled without modifying the network management system and the video distribution system. It is an object of the present invention to provide a streaming service management system that can be detected at the same time and can provide additional services such as data retransmission from the failure occurrence time at the time of failure recovery.

In order to solve the above-mentioned problems, a failure of a relay network from a network management system using a video distribution system, a network management system having a network failure detection function and an influence deployment function, and a request message capture means connecting the both By obtaining the information and occurrence time of the user who has been out of service, an additional message such as data retransmission from the failure occurrence time is provided.
(1) In the first aspect of the present invention , when a failure notification regarding a failure is received by a computer having a storage unit for storing the address of the terminal, the address of the terminal affected by the failure is extracted from the failure notification. , When storing the address in the storage unit and receiving a data re-distribution request from the terminal, from how many terminals having the address stored in the storage unit received the re-distribution request In response to this, a process of performing control to execute redistribution of the data is executed on each terminal that has transmitted the redistribution request .
(2) In the invention according to claim 2 , when the number of terminals indicating whether the redistribution request has been received from the some terminals exceeds a threshold, the processing is performed for each terminal that has transmitted the redistribution request. Control is performed to execute data redistribution .
(3) The invention according to claim 3 is provided with a computer having a storage unit for storing the address of the terminal, and when receiving a failure notification about the failure, extracts the address of the terminal affected by the failure from the failure notification. When the process of storing the address in the storage unit and the data redistribution request from the terminal are received, from how many terminals among the terminals having the address stored in the storage unit have received the redistribution request And a process for controlling each terminal that has transmitted a redistribution request to execute the redistribution of the data .
(4) In the invention according to claim 4 , when the number of terminals indicating whether or not the redistribution request has been received from the some terminals exceeds a threshold, the processing is performed for each terminal that has transmitted the redistribution request. Control is performed to execute data redistribution .

(1) According to the first aspect of the present invention, redistribution can be performed for each terminal that has transmitted a redistribution request .
(2) According to the invention described in claim 2, when the number of terminals indicating whether a redistribution request has been received from several terminals exceeds a threshold, data redistribution to each terminal that has transmitted the redistribution request it can be carried out.
(3) According to the invention described in claim 3, redistribution can be performed to each terminal that has transmitted the redistribution request .
(4) According to the invention described in claim 4, when the number of terminals indicating whether redistribution requests have been received from several terminals exceeds a threshold value, data redistribution to each terminal that has transmitted the redistribution request it can be carried out.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a principle block diagram of the present invention. The same components as those in FIG. 29 are denoted by the same reference numerals. In the figure, 10 is a streaming service provider, and 20 is a communication provider connected to the streaming service provider 10. In the streaming service provider 10, reference numeral 11 denotes a streaming data distribution system as a streaming data distribution means for distributing streaming data, and the figure shows a case where # 1 and # 2 are provided. The present invention is not limited to this, and an arbitrary number of streaming data distribution systems can be provided. The IP address of the streaming data distribution system # 1 is 10.20.10.10, and the IP address of the streaming data distribution system # 2 is 10.20.0.10.

  In the communication carrier 20, 21 is a router (node) for routing a plurality of provided streaming data. In the figure, a case is shown in which an IP network is configured by connecting routers 21 to N1 to N4. A combination of these routers 21 constitutes an IP network. The router 21 that receives data from the streaming data distribution system 11 functions as a streaming data receiving unit. 22 is a network state management means for managing the physical connection configuration and the state of the network, and 24 is a control message monitoring means for monitoring a control message between the streaming data receiving means and the streaming data distribution system 11. .

  A network configuration information storage unit 23 is connected to the network status management unit 22 and stores the status of the streaming service based on information from the message monitoring unit 24. Reference numeral 25 denotes a streaming service management system comprising user extraction means for extracting a user (streaming data display means) using a network link or node as a key. The network / service relation management means 25a and the streaming state management means 25b. Reference numeral 1 denotes streaming data display means. The figure shows an example in which two units # 1 and # 2 are provided. However, the present invention is not limited to this, and an arbitrary number of streaming data display means can be provided. The streaming data display unit may be simply referred to as a data display unit, a user, or a display client. The operation of the system configured as described above will be described as follows.

  The main process is that the communication carrier 20 creates information on the user affected by the failure and notifies the streaming service carrier 10 of the information, but it is necessary to register the information on the user in advance. Therefore, this will be described as a service registration phase, and then described as an affected user information notification phase.

  2 shows a processing flow of the streaming data display means 1, FIG. 3 shows a processing flow of the message monitoring means 24, FIG. 4 shows a processing flow of the streaming data distribution system 11, and FIG. 5 shows a streaming state management. It is a figure which shows the processing flow of the means 25b.

  Hereinafter, these processing flows will be described. First, the operation of the streaming data display unit 1 shown in FIG. 2 will be described. First, a request message for content information to be browsed is transmitted to the streaming data distribution system 11 (S11). Next, the streaming data display means 1 checks whether a response message is obtained from the distribution system 11 (S12). If it is obtained, it is checked whether or not the response content is browsing OK (S13). If it is not OK, the process is terminated (S15). In the case of OK, the address and port number of the distribution server (here, the streaming data distribution system 11) included in the response message are accessed and browsed (S14).

  Next, the processing flow of the message monitoring unit 24 shown in FIG. 3 will be described. First, it waits until a streaming control message is received (S21). Next, when the control message is received, it is checked whether it is a request message from the data display means 1 (S22). If it is not a request message from the data display means 1, it is checked whether it is a response message from the streaming data distribution system 11 (S24). If it is not a response message from the distribution system, the process returns to step S21.

  If the response message is from the streaming data distribution system 11, the IP address of the data display means 1, the IP address of the distribution server, and the content band are extracted from the response message and notified to the streaming state management means 25b (S25). Return to step S21. In step S22, when it is a request message from the display means 1, it transfers to a delivery system (S23), and returns to step S21.

  Next, the processing flow of the streaming data distribution system 11 of FIG. 4 will be described. First, it waits until a control message is received (S31). Next, when a control message is received, it is checked whether it is a request message from the data display means 1 (S32). If it is not a request message from the data display means 1, it is checked whether it is a failure notification from the communication carrier 20 (S34). If it is not a failure notification, the process returns to step S31. If it is a failure notification, information (IP address) of the user affected by the failure is acquired (S35), and the process returns to step S31. If it is a request message in step S32, the streaming data distribution system 11 that can provide the requested content is selected, its IP address, port, and bandwidth information of the content are returned as a response (S33), and the process returns to step S31. .

  Next, the processing flow of the streaming state management unit 25b in FIG. 5 will be described. First, a notification from another component is waited (S41). Next, when the notification is received, it is checked whether it is a service occurrence notification from the message monitoring means 24 (S42). If not, it is checked whether it is a failure notification from the network state management means 22 (S45). If it is not a failure notification, the process returns to step S41.

  If it is a failure notification, a failure location (node or link) is extracted from the failure notification (S46). Then, referring to the network configuration information storage means 23, the service using the failure location obtained in the previous step is extracted, and the IP address of the data display means 1 is notified to the streaming data distribution system 11 (S47). Return to S41.

In step S42, if it is a service occurrence notification from the message monitoring unit 24, information on the generated service (the IP address of the data display unit 1, the IP address of the streaming data distribution system 11, the bandwidth of the content, etc.) is displayed. Obtain (S43). Next, the network configuration information storage means 23 is referred to calculate the route between the data display means 1 to the streaming data distribution system 11, and this is stored in the network / service relationship management means 25a (S44), and the process returns to step S41. .
(Service registration phase)
A request message for content information desired to be browsed is transmitted from the streaming data display means 1 to the streaming data distribution system 11 (S11). At this time, the message monitoring unit 24 operates as a proxy of the streaming data distribution system 11 to detect the generation of the request message (S21 to S22). From the request message, identification information (for example, content ID = 100) of the content to be browsed and an address (for example, IP address = 10.10.10.10 and port 2003) of the transmission source (that is, streaming data display means 1) are obtained. It is done. However, when the information obtained from the request message is obtained from the response message, the message may simply be transferred (through) (S23).

  Next, the streaming data distribution system 11 uses information related to the requested content (distribution server IP address (eg, IP address = 10.20.10.10 and port = 2000)) and content bandwidth (eg, 10 Mbps) as streaming data. It responds with respect to the display means 1 (S31-> S32-> S33). At this time, as in the case of the request message, the message monitoring unit 24 detects the response message and then notifies the streaming state management unit 25b that the service has occurred (S21 → S22 → S24 → S25).

The notification contents include, for example, the IP address (10.10.10.10) of the streaming data display means 1, the IP address (10.20.10.10) of the streaming data distribution system 11, and the bandwidth (10 Mbps) of the content. . The streaming state management unit 25b calculates the stream data path from the service information as described above and the network configuration data stored in the network configuration information storage unit 23 (in this case, for example, 10.10.10.10). -N1-N3-10.20.10.10), this is stored in the relationship management means 25a (S41->S42->S43-> S44).
(Affected user notification phase)
It is assumed that a failure has occurred in the relay network (for example, node N1). At this time, the node (router) that detected the failure is notified of the occurrence of the failure to the network state management means 22 (for example, a SNMP (Simple Network Management Protocol) Trap message notifies the disconnection of the link from N2 and N3 to N1. ) The network state management unit 22 notifies the streaming state management unit 25b of the location where the link break has occurred (N1-N2, N1-N3) (S41 → S42 → S45).

  The streaming state management unit 25b extracts service information from the relationship management unit 25a, and extracts services using the corresponding resources (N1-N2 and N1-N3) (S46). In this example, 10.10.10.10-N1-N3-10.20.10.10 is extracted.

  The communication carrier 20 informs the streaming service carrier 10 of information relating to the failure, for example, information on the affected user (IP address = 10.10.10.10) and the IP address of the streaming data distribution system 11 ( 10.20.10.10) etc. is notified to the streaming service provider 10 (S47). At this time, the notification method is not particularly limited (e-mail or the like is also possible). The streaming service provider 10 acquires information (IP address, etc.) of the user who is affected by the failure notification message from the communication provider 20 (S31 → S32 → S34 → S35).

  With this configuration, the telecommunications carrier 20 extracts all affected users from the failure information of the network and notifies the streaming service operator 10 so that the failure of the relay network can be detected by the network management system and the video distribution. Detection can be performed quickly and accurately without any modification to the system.

  FIG. 6 is a block diagram showing a second embodiment of the present invention. The same components as those in FIG. 1 are denoted by the same reference numerals. In this embodiment, after the streaming service management system 25 extracts all affected users from the failure information of the network, the streaming service management system 25 notifies the streaming data distribution system 11.

  With this configuration, the telecommunications carrier 20 extracts all affected users from the failure information of the network and notifies the streaming service operator 10 so that the failure of the relay network can be detected by the network management system and the video distribution. Detection can be performed quickly and accurately without any modification to the system.

  FIG. 7 is a block diagram showing a third embodiment of the present invention. The same components as those in FIG. 1 are denoted by the same reference numerals. In this embodiment, the streaming service management system 25 in the telecommunications carrier 20 issues a control signal to the message monitoring means 24, and the streaming data distribution system in the streaming service provider 10 receives the control signal from the message control means 24. 11 is provided with a control signal. The operation of the system configured as described above will be described as follows.

  FIG. 8 is a diagram showing a processing flow of the streaming state management means 25b, and FIG. 9 is a diagram showing a processing flow of the message monitoring means 24. Hereinafter, these processing flows will be described. First, the processing flow shown in FIG. 8 will be described. First, a notification from another component is waited (S41). Then, when a notification is received, it is checked whether or not it is a service occurrence notification from the message monitoring means 24 (S42).

  If it is not a service occurrence notification from the message monitoring means 24, it is checked whether it is a failure notification from the network state management means 22 (S45). If it is not a failure notification from the network state management means 22, the process returns to step S41. If the notification is from the network state management means 22, the failure location (node or link) is extracted from the failure notification (S46). Next, the network configuration information storage unit 23 is referred to, a service using the failure location obtained in the previous step is extracted, and the IP address of the data display unit 1 is notified to the streaming data distribution system 11. The monitoring unit 24 is requested (S48), and the process returns to step S41.

  In step S42, if it is a service occurrence notification from the message monitoring means, information relating to the generated service (IP address of the data display means 1, IP address of the streaming data distribution system 11, content bandwidth, etc.) is obtained. (S43). Next, the network configuration information storage unit 23 is referred to calculate a route between the data display unit 1 and the streaming data distribution system 11, and stores this in the relationship management unit 25a (S44), and the process returns to step S41.

  Next, the flow shown in FIG. 9 will be described. First, the message monitoring unit 24 waits until a streaming control message is received (S21). When the streaming control message is received, it is checked whether it is a request message from the data display means 1 (S32). If it is not a request message, it is checked whether it is a response message from the streaming data distribution system 11 (S24). If it is not a response message, it is checked whether it is a request from the streaming state management means 25b (S26). If the request is not from the streaming state management unit 25b, the process returns to step S21. If the request is from the streaming state management unit 25b, the content (failure information) of the request message is notified to the streaming data distribution system 11 (S27), and the process returns to step S21.

  In step S24, if the response message is from the streaming data distribution system, the IP address of the data display means 1, the IP address of the streaming data distribution system 11, and the content band are extracted from the response message, and the streaming state management is performed. The means 25b is notified (S25), and the process returns to step S21. In step S22, when it is a request message from the data display means 1, it transfers to the streaming data delivery system 11 (S23), and returns to step S21.

  The overall operation will be described below. Differences from the embodiment shown in FIG. 1 will be described. In the influence user notification phase, the network state management unit 22 notifies the streaming state management unit 25b of the location where the link break has occurred (N1-N2, N1-N3) (S41 → S42 → S45). The streaming state management unit 25b extracts service information from the relationship management unit 25a, and extracts services using the corresponding resources (N1-N2 and N1-N3) (S46).

  In this example, 10.10.10.10-N1-N3-10.20.10.10 is extracted. The streaming state management unit 25b sends information related to the failure to the message monitoring unit 24, for example, information on the affected user (data display unit) 1 (IP address = 10.10.10.10) or a streaming data distribution system. 11 is requested to notify the streaming data distribution system 11 of the IP address (10.20.10.10) of 11 or the like (S48).

  The message monitoring unit 24 notifies the above-described failure information to the streaming data distribution system 11 (S21 → S22 → S24 → S26 → S27). At this time, the notification method is not particularly limited (e-mail or the like is also possible). The streaming data distribution system 11 acquires the information (IP address, etc.) of the affected user from the failure notification message from the communication carrier 20 (S31 → S32 → S34 → S35).

According to this embodiment, the message monitoring unit 24 can notify the failure information to the streaming data distribution system.
FIG. 10 is a block diagram showing a fourth embodiment of the present invention. The same components as those in FIG. 1 are denoted by the same reference numerals. In this embodiment, the configuration of the streaming service provider 10 is different from the conventional one. In the figure, reference numeral 13 denotes a distribution server that distributes streaming data. In the figure, the case where two units # 1 and # 2 are provided is shown, but the present invention is not limited to this. Reference numeral 12 denotes a node connected to the distribution server 13, which is connected to the IP network and further connected to the distribution manager 14. The distribution manager 14 is connected to the streaming service management system 25 of the communication carrier 20. The operation of the system configured as described above will be described as follows.

  FIG. 11 is a diagram showing a processing flow of the streaming state management means 25b, and FIG. 12 is a diagram showing a processing flow of the distribution manager 14. First, these flows will be described. First, FIG. 11 will be described. The streaming state management unit 25b waits for a notification from another component (S41). When the notification is received, it is checked whether or not it is a service occurrence notification from the message monitoring means 24 (S42).

  If it is not a service occurrence notification from the message monitoring means 24, it is checked whether it is a failure notification from the network state management means 22 (S45). If it is not a failure notification, the process returns to step S41. If it is a failure notification, a failure location (node or link) is extracted from the failure notification (S46). Next, the network configuration information storage means 23 is referred to extract the service using the failure location obtained in the previous step, notify the distribution manager 14 of the IP address of the data display means 1 (S49), and step S41. Return to.

  In step S42, if it is a service occurrence notification from the message monitoring means 24, information relating to the generated service (IP address of the data display means 1, IP address of the distribution server 13, contents, etc.) is obtained (S43). Next, the network configuration information storage unit 23 is referred to calculate the route between the data display unit 1 to the distribution server 13, and this is stored in the relationship management unit 25a (S44), and the process returns to step S41.

  Next, FIG. 12 will be described. First, it waits until a control message is received (S51). Next, when the control message is received, it is checked whether it is a request message from the data display means 1 (S52). If it is not a request message from the data display means 1, it is checked whether it is a failure notification from the communication carrier 20 (S54). If not, the process returns to step S51. If so, information (IP address) of the user affected by the failure is acquired (S55), and the process returns to step S51. If it is a request message from the data display means 1 in step S52, the distribution server 13 that can provide the requested content is selected, and its IP address, port, and content bandwidth information are returned as a response (S53). Return to step S51.

  Next, the overall operation will be described. First, the difference between the system shown in FIG. 10 and the system shown in FIG. 1 will be described. In the influence user notification phase, the network state management unit 22 notifies the streaming state management unit 25b of the location where the link break has occurred (N1-N2, N1-N3) (S41 → S42 → S45). The streaming state management unit 25b extracts service information from the relationship management unit 25a, and extracts services using the corresponding resources (N1-N2 and N1-N3) (S46).

  In this example, 10.10.10.10-N1-N3-10.20.10.10 is extracted. The streaming state management unit 25b distributes information related to the failure, for example, information on the affected user (IP address = 10.10.10.10), the IP address of the distribution server 13 (10.20.10.10), and the like. The manager 14 is notified (S49). At this time, the notification method is not particularly limited. For example, e-mail may be used. The distribution manager 14 acquires the information (IP address) of the user who is affected by the failure notification message from the communication carrier 20 (S51 → S52 → S54 → S55).

According to this embodiment, the distribution manager 14 can acquire information (IP address or the like) of users who are affected by the communication carrier 20.
FIG. 13 is a block diagram showing a fifth embodiment of the present invention. The same components as those in FIG. 10 are denoted by the same reference numerals. This embodiment is different from FIG. 10 in that the output of the streaming service management system 25 is input not to the distribution manager 14 but to the distribution server 13. The operation of the system configured as described above will be described as follows.

  FIG. 14 is a diagram showing a processing flow of the streaming state management means 25b, and FIG. 15 is a diagram showing a processing flow of the distribution server. First, FIG. 14 will be described. First, a notification from another component is waited (S41). When the notification comes, it is checked whether or not it is a service occurrence notification from the message monitoring means 24 (S42). If it is not a service occurrence notification, it is checked whether it is a failure notification from the network state management means 22 (S45). If it is not a failure notification from the network state management means 22, the process returns to step S41. If it is a failure notification from the network state management means 22, a failure location (node or link) is extracted from the failure notification (S46). Next, the network configuration information storage means 23 is referred to extract the service using the failure location obtained in the previous step, notify the distribution server 13 of the IP address of the data display means 1 (S47), and step S41. Return to.

  In step S42, if it is a service occurrence notification from the message monitoring unit 24, information on the generated service (the IP address of the data display unit 1, the IP address of the distribution server 13, the content bandwidth, etc.) is obtained ( S43). Then, referring to the network configuration information storage means 23, the route between the data display means 1 and the distribution server 13 is calculated, stored in the relationship management means 25a (S44), and the process returns to step S41.

  Next, FIG. 15 will be described. First, the distribution server 13 waits until a control message is received (S61). When the control message is received, it is checked whether or not the failure notification is received from the communication carrier 20 (S62). If it is not a failure notification from the communication carrier 20, the process returns to step S61. In the case of a failure notification from the communication carrier 20, information (IP address) of the user affected by the failure is acquired (S63), and the process returns to step S61.

  Next, the overall operation will be described. First, the difference between the system shown in FIG. 13 and the system shown in FIG. 1 will be described. In the influence user notification phase, the network state management unit 22 notifies the streaming state management unit 25b of the location where the link break has occurred (N1-N2, N1-N3) (S41 → S42 → S45). The streaming state management unit 25b extracts service information from the relationship management unit 25a, and extracts services using the corresponding resources (N1-N2 and N1-N3) (S46). In this example, 10.10.10.10-N1-N3-10.20.10.10 is extracted.

  The streaming state management unit 25b is configured to provide information related to the failure, for example, the information of the affected user (data display unit) 1 (IP address = 10.10.10.10) or the IP address of the distribution server 13 (10.20). .10.10) to the distribution server 13 (S47). At this time, the notification method is not particularly limited. For example, e-mail or the like is also possible. The distribution server 13 acquires information (IP address, etc.) of users who are affected by the communication carrier 20 (S61 → S62 → S63).

According to this embodiment, the distribution server 13 can acquire information on the affected user.
FIG. 16 is a block diagram showing a sixth embodiment of the present invention. The same components as those in FIG. 10 are denoted by the same reference numerals. In this embodiment, the control signal from the streaming state management unit 25b in the streaming service management system 25 enters the message monitoring unit 24, and the output of the message monitoring unit 24 receiving this control signal enters the distribution manager 14. It is composed of.

  The operation of this embodiment is a combination of the embodiment shown in FIG. 7 and the embodiment shown in FIG. According to this embodiment, the message monitoring unit 24 can notify the failure information to the distribution manager 14 of the streaming data distribution system 20.

  FIG. 17 is a block diagram showing a seventh embodiment of the present invention. The same components as those in FIG. 10 are denoted by the same reference numerals. In this embodiment, the control signal from the streaming state management unit 25b in the streaming service management system 25 enters the message monitoring unit 24, and the output of the message monitoring unit 24 receiving this control signal enters the distribution server 13. It is composed of.

  The operation of this embodiment is a combination of the embodiment shown in FIG. 7 and the embodiment shown in FIG. According to this embodiment, the distribution server 13 can acquire information on the affected user.

  FIG. 18 is a block diagram showing an eighth embodiment of the present invention. The same components as those in FIG. 1 are denoted by the same reference numerals. In this embodiment, the control signal is notified from the communication carrier 20 to the streaming data distribution system 11 of the streaming service carrier 10. FIG. 19 is a diagram showing a processing flow of the streaming state management means 25b, and FIG. 20 is a diagram showing a processing flow of the streaming data distribution system 11.

  First, the flow shown in FIG. 19 will be described. First, the streaming state management unit 25b waits for a notification from another component (S41). When the notification arrives, it is checked whether or not it is a service occurrence notification from the message monitoring means 24 (S42). If it is not a service occurrence notification, it is checked whether it is a failure notification from the network state management means 22 (S45). If it is not a failure notification, it is checked whether it is a recovery notification from the network state management means 22 (S411).

  If it is not a recovery notification, the process returns to step S41. If it is a recovery notification, the previous recovery destination (streaming data distribution system 11 or message monitoring means 24) is notified of the failure recovery (S412), and the process returns to step S41. If it is a failure notification from the network state management means 22 in step S45, a failure location (node or link) is extracted from the failure notification (S46). Then, referring to the network configuration information storage means 23, the service using the failure location obtained in the previous step is extracted, and the IP address of the data display means 1 is notified to the streaming data distribution system 11 (S47). Return to S41.

  In step S42, if it is a service occurrence notification, information on the generated service (IP address of the data display means 1, IP address of the streaming data distribution system 11, content bandwidth, etc.) is obtained (S43). Next, the network configuration information storage unit 23 is referred to calculate a route between the data display unit 1 and the streaming data distribution system 11, and stores this in the relationship management unit 25a (S44), and the process returns to step S41.

  Next, the flow shown in FIG. 20 will be described. The streaming data distribution system 11 waits until a control message is received (S31). When the control message is received, it is checked whether it is a request message from the data display means 1 (S32). If it is not a request message, it is checked whether it is a failure notification from the communication carrier 20 (S34). If it is not a failure notification, it is checked whether it is a recovery notification from the communication carrier 20 (S36). If it is not a recovery notification, the process returns to step S31.

  If it is a recovery notification, a stream reproduced from before the failure occurrence time is created, and the data display means 1 indicated by the IP address included in the request is requested to switch the stream (S37), and step S31. Return to. If it is a failure notification in step S34, information (IP address) of the user affected by the failure is acquired (S35), and the process returns to step S31.

  If it is a request message in step S32, the streaming data distribution system 11 that can provide the requested content is selected, and its IP address, port, and bandwidth information of the content are returned as a response (S33), and the process returns to step S31. Return.

  Next, the overall operation will be described. Differences from the embodiment shown in FIG. 1 will be described. In the influence user notification phase, the network state management unit 22 notifies the streaming state management unit 25b of the location where the link establishment has occurred (N1-N2, N1-N3) (S41 → S42 → S45 → S411). The streaming state management unit 25b notifies the failure recovery to the destination that has notified the occurrence of the failure (S412). At this time, the notification method is not particularly limited. For example, e-mail or the like is also possible.

  The streaming data distribution system 11 requests stream switching to an IP address (for example, 10.10.10.10) indicating the data display means 1 included in the failure recovery message from the communication carrier 20 (S31 → S32 → S34 → S36 → S37). The stream switching itself uses a signaling protocol (conventional technology) such as RTSP or SIP, and notifies the data display means 1 (display client) 1 of the address and port number of the new streaming data distribution system 11. Can be implemented.

According to this embodiment, the streaming state management unit 25b can notify the failure recovery to the destination that has notified the occurrence of the failure.
Next, a ninth embodiment will be described. 21 shows the processing flow of the streaming state management means, FIG. 22 shows the processing flow of the distribution manager, and FIG. 23 shows the processing flow of the distribution server. For example, FIG. 10 is used as the system.

  First, the processing flow of FIG. 21 will be described. The streaming state management unit 25b waits for a notification from another component (S41). If a notification is received, it is checked whether or not it is a service occurrence notification from the message monitoring means 24 (S42). If it is not a service occurrence notification, it is checked whether it is a failure notification from the network state management means 22 (S45). If it is not a failure notification, it is checked whether it is a recovery notification from the network state management means 22 (S411).

  If it is not a recovery notification in step S411, the process returns to step S41. If it is a recovery notification, the destination (distribution system or message monitoring means 24) that has notified the previous failure is notified of the failure recovery (S412), and the process returns to step S41. If it is a failure notification from the network state management means 22 in step S45, a failure location (node or link) is extracted from the failure notification (S46). Next, the network configuration information storage means 23 is referred to extract the service using the failure location obtained in the previous step, notify the distribution server 13 of the IP address of the data display means 1 (S410), and step S1 Return to.

  In step S42, if it is a service occurrence notification from the message monitoring means 24, information relating to the generated service (IP address of the data display means 1, IP address of the distribution server, content bandwidth, etc.) is obtained (S43). ). Then, referring to the network configuration information storage means 23, the route between the data display means and the distribution server 13 is calculated, stored in the relationship management means 25a (S44), and the process returns to step S41.

  Next, the processing flow of FIG. 22 will be described. The distribution manager 14 first waits until a control message is received (S51). If a control message is received, it is checked whether it is a request message from the data display means 1 (S52). If it is not a request message, it is checked whether it is a failure notification from the communication carrier 20 (S54). If it is not a failure notification, it is checked whether it is a recovery notification from the communication carrier 20 (S56). If it is not a recovery notification, the process returns to step S51.

  In the case of a recovery notification, a stream reproduced from before the failure occurrence time is created, and the distribution server 13 is switched to switch the stream to each data display means 1 indicated by the IP address included in the request. Request (S57) and return to step S51. If it is a failure notification from the communication carrier 20 in step S54, information (IP address) of the user affected by the failure is acquired (S55), and the process returns to step S51. If it is a request message from the data display means 1 in step S52, the distribution server 13 that can provide the requested content is selected, and its IP address, port, and content bandwidth information are returned as a response (S53). Return to step S51.

  Next, the processing flow of FIG. 23 will be described. The distribution server 13 waits until a control message is received (S61). If it is received, it is checked whether it is a failure notification from the communication carrier 20 (S62). If it is not a failure notification, it is checked whether it is a switching request from the distribution manager 14 (S64). If it is not a switching request, the process returns to step S61.

  If it is a switching request, a new stream is generated, the data display means indicated by the IP address included in the request is requested to switch to the new stream (S65), and the process returns to step S61. If it is a failure notification from the communication carrier in step S62, information (IP address) of the user affected by the failure is acquired (S63), and the process returns to step S61.

  Next, the overall operation of the ninth embodiment will be described. In this embodiment, differences from the first embodiment will be described. In the influence user notification phase, the network state management unit 22 notifies the streaming state management unit 25b of the location where the link establishment has occurred (N1-N2, N1-N3) (S41 → S42 → S45 → S411). The streaming state management unit 25b notifies the failure recovery to the destination that has notified the occurrence of the failure (S412). At this time, the notification method is not particularly limited (e-mail or the like is also possible).

  The distribution manager 14 instructs the distribution server to switch the stream toward the IP address (for example, 10.10.10.10) indicating the data display means 1 included in the failure recovery message from the communication carrier 20. Request (S51 → S52 → S54 → S56 → S57). The distribution server 13 requests the designated data display means 1 to switch the stream (S61 → S62 → S64 → S65). Note that the stream switching itself can be performed by notifying the display client 1 of the address and port number of the new distribution server using a signaling protocol (conventional technology) such as RTSP or SIP.

According to this embodiment, the distribution server 13 can request the designated data display means 1 to switch the stream.
Next, the operation of the tenth embodiment will be described. FIG. 24 is a diagram showing a processing flow of the streaming state management means 25b, and FIG. 25 is a diagram showing a processing flow of the distribution server 13. FIG. 10 is used as the system configuration.

  First, the processing flow of FIG. 24 will be described. The streaming state management unit 25b waits for a notification from another component (S41). When notification is received, it is checked whether or not it is a service occurrence notification from the message monitoring means 24 (S42). If it is not a service occurrence notification, it is checked whether it is a failure notification from the network state management means 22 (S45). If it is not a failure notification from the network state management unit 22, it is checked whether it is a recovery notification from the network state management unit 22 (S411).

  If it is not a recovery notification from the network state management means 22, the process returns to step S41. In the case of the recovery notification from the network management means 22, the failure recovery is notified to the destination (distribution system or message monitoring means 24) that notified the failure last time (S412), and the process returns to step S41. If it is a failure notification from the network state management means 22 in step S45, the failure location (node or link) is extracted from the failure notification (S46). Next, the network configuration information storage means 23 is referred to extract the service using the failure location obtained in the previous step, notify the distribution server 13 of the IP address of the data display means 1 (S410), and step S41. Return to.

  In step S42, if it is a service occurrence notification from the message monitoring unit 24, information about the generated service (display unit IP address, distribution server IP address, content bandwidth, etc.) is obtained (S43). Next, the network configuration information storage unit 23 is referred to calculate the route between the data display unit 1 to the distribution server 13, and this is stored in the relationship management unit 25a (S44), and the process returns to step S41.

  Next, the processing flow of FIG. 25 will be described. The distribution server 13 waits until a control message is received (S61). When the control message is received, it is checked whether or not a failure notification is received from the communication carrier 20 (S62). If it is not a failure notification, it is checked whether it is a switching request from the distribution manager 14 (S64). If it is not a switching request, it is checked whether or not it is a recovery notification from the communication carrier 20 (S66). If it is not a recovery notification, the process returns to step S61.

  If it is a restoration notification, a stream reproduced from before the failure occurrence time is created, and the distribution server 13 is configured to switch the stream to each data display means 1 indicated by the IP address included in the request. (S67), and the process returns to step S61. If it is a switching request from the distribution manager in step S64, a new stream is generated, and the data display means 1 indicated by the IP address included in the request is requested to switch to the new stream. (S65), the process returns to step S61. If it is a failure notification from the communication carrier 20 in step S62, information (IP address) of the user affected by the failure is acquired (S63), and the process returns to step S61. Here, the user is the data display means 1.

  Next, the difference between the tenth embodiment and the first embodiment will be described. In the influence user notification phase, the network state management unit 22 notifies the streaming state management unit 25b of the location where the link establishment has occurred (N1-N2, N1-N3) (S41 → S42 → S45 → S411). The streaming state management unit 25b notifies the failure recovery to the destination that has notified the occurrence of the failure (S412). At this time, the notification method is not particularly limited (e-mail or the like is also possible).

  The distribution server 13 requests the IP address (for example, 10.10.10.10) included in the failure recovery message from the communication carrier 20 to switch the stream (S61 → S62 → S64 → S66 → S67). Stream switching itself can be performed by using a signaling protocol (conventional technology) such as RTSP or SIP and notifying the data display means 1 of the address and port number of the new distribution server.

  According to this embodiment, the distribution server 13 can request to perform stream switching toward the address included in the failure recovery message from the communication carrier 20.

  In the eleventh embodiment, S37, S57, S65, and S67 in the eighth to tenth are not requested to switch the stream to the IP address (data display means 1 indicated) included in the recovery notification. , “Send to the IP address included in the failure notification (S35, S55, S63) received in advance”.

According to this embodiment, the control information can be transmitted to the IP address included in the failure notification received in advance.
Next, a twelfth embodiment will be described. 26 and 27 are diagrams showing a processing flow of the streaming data distribution system. As the system configuration unit, FIG. 1 is used. The streaming delivery system 11 waits until a control message is received (S31). If a control message is received, it is checked whether it is a request message from the data display means 1 (S32). If it is not a request message, it is checked whether it is a failure notification from the communication carrier 20 (S34).

  If it is not a failure notification, the process returns to step S31. If it is a failure notification, information (IP address) of the user (data display means 1) affected by the failure is acquired (S35), and the process returns to step S31. If it is a request message from the data display means 1 in step S32, it is checked whether it is a redistribution request (S321). If it is not a redistribution request, a distribution server that can provide the requested content is selected, its IP address, port, and bandwidth information of the content are returned as a response (S33), and the process returns to step S31.

  If it is a distribution request in step S321, it is checked whether it is from the IP address acquired in step S35 (S68). If so, the redistribution request flag of the redistribution request table is set, and the redistribution request rate = (number of redistribution flag set) ÷ (number of rows of the redistribution request table) is calculated. (S70). FIG. 28 is a diagram showing management data of the streaming data distribution system. As is clear from the figure, it is a diagram showing a redistribution request table and a redistribution execution threshold.

  The redistribution request table shows a data display means IP address and a redistribution request flag. The IP address obtained in step S35 is stored in the IP address of the data display means 1. The redistribution request flag is set to “1” in step S70. The redistribution implementation threshold is 80%, for example.

  When step S70 is executed, it is checked whether the redistribution request rate exceeds the redistribution execution threshold (S71). If not, the process returns to step S31. If exceeded, a stream reproduced from before the failure occurrence time is created, and streaming is performed so as to perform stream switching for each data display means 1 indicated by the IP address for which the redistribution request flag is set. The data distribution system 11 is requested (S72), and the process returns to step S31.

  Next, the overall operation of the embodiment 12 will be described. Here, the redistribution execution threshold is set to 80% as shown in FIG. 27 (that is, redistribution is performed when requests are received from all the data display means 1). Until the IP address (for example, 10.10.10.10 and 10.10.20.10) of the data display means 1 affected by the failure is acquired by the stream data distribution system, The same is true (S31 → S32 → S34 → S35).

  Thereafter, when the network is restored, each data display means 1 independently transmits a redistribution request. The streaming data distribution system 11 acquires the address of the data display means 1 that has requested redistribution from the received IP packet, and compares it with the IP address registered earlier (S31 → S32 → S321 → S68). If the requested IP address of the data display means 1 is. If it is 10.10.10, it matches the previously registered IP address, so the number of redistribution requests is incremented by 1 and the redistribution request rate is calculated (S70).

  The redistribution request rate is calculated by (number of redistribution flags set) ÷ (number of rows in the redistribution request table). Next, the number of redistribution requests is compared with the implementation threshold (two in this case) (S71). In the redistribution request table of the embodiment, since the redistribution request rate is 75% or less, redistribution is not performed. If the IP address of the data display means 1 requested next is 10.10.20.10, the redistribution request rate exceeds the redistribution execution threshold value, so redistribution is performed.

According to this embodiment, redistribution can be performed based on the redistribution request rate.
(Appendix 1) A streaming service provider having a streaming data distribution means;
An IP network consisting of routers and network switches;
Streaming data receiving means for receiving streaming data;
Control message monitoring means for monitoring a control message between the streaming data receiving means and the streaming data distribution means;
Network status management means for managing the physical connection configuration and the status of the network, network configuration information storage means for storing the status of the streaming service based on information from the message monitoring means, and using the network link or node as a key A telecommunications carrier having a streaming service management system comprising user extraction means for extracting users to be used;
A streaming service management system, characterized in that the telecommunications carrier extracts all affected users from network fault information and notifies the streaming service carrier.
(Supplementary note 2) The streaming service management system according to supplementary note 1, wherein after the streaming service management system extracts all affected users from the failure information of the network, the management system notifies the streaming data distribution means.
(Supplementary Note 3) After the streaming service management system has extracted all affected users from the failure information of the network, the control message monitoring means requests the notification of information regarding the affected users to the streaming data distribution means. The streaming service management system according to Supplementary Note 1, wherein the system is a streaming service management system.
(Supplementary Note 4) When the streaming data distribution means includes a distribution server that transmits data and a distribution manager that manages the selection of the distribution server and the user's viewing status, the user affected by the failure information of the network The streaming service management system as set forth in appendix 1, wherein all are extracted and notified to a distribution manager.
(Supplementary Note 5) When the streaming data distribution means includes a distribution server that transmits data and a distribution manager that manages the selection of the distribution server and the user's viewing status, the user who is affected by the failure information of the network The streaming service management system as set forth in appendix 1, wherein all are extracted and notified to a distribution server.
(Supplementary Note 6) In the case where the streaming data distribution means includes a distribution server that transmits data and a distribution manager that manages the selection of the distribution server and the user's viewing status, the service management system uses network failure information. 2. The streaming service management system according to claim 1, wherein after all the affected users are extracted, the control message monitoring unit is requested to notify the distribution manager of information relating to the affected users.
(Supplementary Note 7) When the streaming data distribution means includes a distribution server that transmits data and a distribution manager that manages the selection of the distribution server and the viewing status of the user, the management system is affected by the failure information of the network. 2. The streaming service management system according to claim 1, wherein after all users who receive the request are extracted, the control message monitoring means for monitoring the control message is requested to notify the distribution server of information relating to the affected user.
(Supplementary Note 8) The streaming data distribution means stores failure information from the management system and distributes the streaming that goes back to the failure occurrence time to the affected user by using failure recovery information from the communication carrier as a trigger. The streaming service management system according to appendix 1, characterized by the above.
(Supplementary Note 9) When the streaming data distribution means includes a distribution server that transmits data and a distribution manager that manages the selection of the distribution server and the viewing status of the user, and the failure information is notified to the distribution manager, 7. The streaming service management system according to appendix 4 or 6, wherein the distribution manager distributes the streaming that goes back to the failure occurrence time to the affected user by using the failure recovery information from the service management system as a trigger.
(Supplementary Note 10) When the streaming data distribution means includes a distribution server that transmits data and a distribution manager that manages the selection of the distribution server and the viewing status of the user, and the failure information is notified to the distribution server, 8. The streaming service management system according to appendix 5 or 7, wherein the distribution server distributes the streaming that goes back to the failure occurrence time to the affected user by using the failure recovery information from the management system as a trigger.
(Supplementary Note 11) The streaming data distribution means stores failure information (affected user information) from the management system, and the failure occurrence time for the affected user is triggered by the failure recovery information from the streaming service management system. The streaming service management system according to appendix 1, wherein streaming data traced back to is distributed.
(Supplementary Note 12) The streaming data distribution means includes means for determining whether or not the retransmission request from the streaming data display means is included in failure information (affected user information) from the streaming service management system stored in advance. Appendix 1 characterized in that, when the number of retransmission requests included in the failure information exceeds a threshold set in advance by the administrator, streaming that is traced back to the failure occurrence time is delivered to the affected user who transmitted the retransmission request. The streaming service management system described.

  As described above in detail, according to the present invention, in the video distribution system using SIP and RTP, the distribution manager / server cannot be detected conventionally, and even if it can be detected, it takes time to detect, and By using message capture, it is possible to quickly and accurately detect a failure in a relay network, where it was difficult to determine the time when the failure occurred, and restore the failure without changing the network management system and video distribution system. Additional services such as data retransmission from the time of failure occurrence can be provided. In the twelfth embodiment, the number of redistributed streams for one failure (that is, consumed network resources) is compared with the case of individually redistributing data display means that has requested retransmission. Can be reduced.

1 is a block diagram illustrating a first exemplary embodiment of the present invention. It is a figure which shows the processing flow of a streaming data display means. It is a figure which shows the processing flow of a message monitoring means. It is a figure which shows the processing flow of a streaming data delivery system. It is a figure which shows the processing flow of a streaming state management means. It is a block diagram which shows the 2nd Example of this invention. It is a block diagram which shows the 3rd Embodiment of this invention. It is a figure which shows the processing flow of a streaming state management means. It is a figure which shows the processing flow of a message monitoring means. It is a block diagram which shows the 4th Embodiment of this invention. It is a figure which shows the processing flow of a streaming state management means. It is a figure which shows the processing flow of a delivery manager. It is a block diagram which shows the 5th example of embodiment of this invention. It is a figure which shows the processing flow of a streaming state management means. It is a figure which shows the processing flow of a delivery server. It is a block diagram which shows the 6th Embodiment of this invention. It is a block diagram which shows the example of 7th Embodiment of this invention. It is a block diagram which shows the 8th Embodiment of this invention. It is a figure which shows the processing flow of a streaming state management means. It is a figure which shows the processing flow of a streaming data delivery system. It is a figure which shows the processing flow of a streaming state management means. It is a figure which shows the processing flow of a delivery manager. It is a figure which shows the processing flow of a delivery server. It is a figure which shows the processing flow of a streaming state management means. It is a figure which shows the processing flow of a delivery server. It is a figure which shows the processing flow of a streaming data delivery system. It is a figure which shows the processing flow of a streaming data delivery system. It is a figure which shows the management data of a streaming data delivery system. It is a block diagram which shows the structural example of a conventional system.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Streaming data display means 10 Streaming service provider 11 Streaming data distribution system 20 Communication carrier 21 Router (node)
22 Network status management means 23 Network configuration information storage means 24 Message monitoring means 25 Streaming service management system 25a Network / service relation management means 25b Streaming status management means

Claims (4)

In a computer having a storage unit for storing the address of the terminal,
When receiving a failure notification related to a failure, a process of extracting the address of the terminal affected by the failure from the failure notification and storing the address in the storage unit;
When receiving a data redistribution request from the terminal, depending on how many terminals have received the redistribution request among the terminals having the addresses stored in the storage unit, to each terminal that has transmitted the redistribution request Processing for performing redistribution of the data,
A streaming service management program characterized in that In the processing, when the number of terminals indicating whether redistribution requests have been received from the some terminals exceeds a threshold, control is performed to redistribute the data to each terminal that has transmitted the redistribution request. The streaming service management program according to claim 1. A computer having a storage unit for storing the address of the terminal;
When receiving a failure notification related to a failure, a process of extracting the address of the terminal affected by the failure from the failure notification and storing the address in the storage unit;
When receiving a data redistribution request from the terminal, depending on how many terminals have received the redistribution request among the terminals having the addresses stored in the storage unit, to each terminal that has transmitted the redistribution request Processing for performing redistribution of the data,
A streaming service management method comprising: In the processing, when the number of terminals indicating whether redistribution requests have been received from the some terminals exceeds a threshold, control is performed to redistribute the data to each terminal that has transmitted the redistribution request. The streaming service management method according to claim 3.

Images