Source: http://www.google.com/patents/US20040151166?dq=mirroring+data+in+a+remote+data+storage+system
Timestamp: 2016-10-27 17:26:34
Document Index: 701169349

Matched Legal Cases: ['arts 661', 'arts 662', 'arts 661', 'arts 662', 'art 661', 'art 661', 'art 662', 'art 661', 'art 661', 'art 662', 'art 662', 'art 661', 'art 661', 'arts 661', 'arts 661']

Patent US20040151166 - Packet communication system, network device and method of managing resource ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA network device is provided which is capable of contributing to construction of a system without a centralized resource management function, ensuring system expandability to install additional call control processors, and isolating a capability of each user data processing unit from a call control section....http://www.google.com/patents/US20040151166?utm_source=gb-gplus-sharePatent US20040151166 - Packet communication system, network device and method of managing resource employed thereforAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20040151166 A1Publication typeApplicationApplication numberUS 10/768,082Publication dateAug 5, 2004Filing dateFeb 2, 2004Priority dateFeb 5, 2003Publication number10768082, 768082, US 2004/0151166 A1, US 2004/151166 A1, US 20040151166 A1, US 20040151166A1, US 2004151166 A1, US 2004151166A1, US-A1-20040151166, US-A1-2004151166, US2004/0151166A1, US2004/151166A1, US20040151166 A1, US20040151166A1, US2004151166 A1, US2004151166A1InventorsTsutomu Tsukagoshi, Naoto Suzuki, Kazushi Saeki, Toshio MoriOriginal AssigneeTsutomu Tsukagoshi, Naoto Suzuki, Kazushi Saeki, Toshio MoriExport CitationBiBTeX, EndNote, RefManPatent Citations (3), Referenced by (10), Classifications (28), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetPacket communication system, network device and method of managing resource employed therefor
BRIEF DESCRIPTION OF THE DRAWINGS [0034] [0034]FIG. 1 is a block diagram showing a configuration of a network device according to a preferred embodiment of the present invention; [0035] [0035]FIG. 2 is a block diagram showing a configuration of a packet communication system according to an example of the present invention; [0036] [0036]FIG. 3 is a sequence chart showing operations of the packet communication system according to the example of the present invention; [0037] [0037]FIG. 4 is a sequence chart showing the operations of the packet communication system according to the example of the present invention; [0038] [0038]FIG. 5 is a sequence chart showing the operations of the packet communication system according to the example of the present invention; [0039] [0039]FIG. 6 is a sequence chart showing the operations of the packet communication system according to the example of the present invention; and [0040] [0040]FIG. 7 is block diagram showing a configuration of a conventional packet communication system.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0041] Referring now to the accompanying drawings, a preferred embodiment of the present invention will be described. FIG. 1 is a block diagram showing a configuration of a network device according to the embodiment of the present invention. As observed therefrom, the network device 1 comprises a C-plane (call control section) 2 consisting of a plurality of processors 21 to 23, and a U-plane 30 consisting of a plurality of user data processing units 31 to 33. The C-plane 2 is operative for controlling signalling, and the U-plane 30 is operative for transferring user data. [0042] In the network device 1, the C-plane 2 and the plurality of user data processing units 31 to 33 are logically and physically separated from each other so that the C-plane 2 does not manage (capture or release) band resource and the number-of-sessions resource of the user data processing units 31 to 33. [0043] More specifically, each of the user data processing units 31 to 33 manages (captures and releases) the band resource and the number-of-sessions resource of its own circuit. Furthermore, when responding to a call setup request sent from the C-plane 2 in order to establish a session, each of the user data processing units 31 to 33 notifies the C-plane 2 of a status of the remaining band and number of sessions of its own circuit by attaching it to a response message. This status is indicated by an available resource ratio that represents a ratio of the remaining band and number of sessions to resources, and is hereinafter referred to as an available resource ratio. [0044] Moreover, when responding to a call release request sent from the C-plane 2 in order to release a session, each of the user data processing units 31 to 33 notifies the C-plane 2 of the available resources ratio of its own circuit by attaching it to a response message. [0045] In addition, when responding to a health check signal sent from the C-plane 2 in order to check whether the circuit of each of the user data processing units 31 to 33 is operable or not, each of the user data processing units 31 to 33 notifies the C-plane 2 of the available resource ratio of its own circuit by attaching it to a response message. [0046] The C-plane 2 stores thus obtained available resource ratios of each of the user data processing units 31 to 33, and selects the user data processing units 31 to 33 having remaining resources thereby to send a call setup request thereto for establishment of a session. [0047] [0047]FIG. 1 shows that processors 21 to 23 in the C-plane 2 are connected with the user data processing units 31 to 33 based on bus topology, however, switch topology is also applicable to connect them in which case the C-plane 2 has connection through switches to all the user data processing units 31 to 33. [0048] The capability of each of the user data processing units 31 to 33 has heretofore been closely managed by a centralized resource management function provided to the C-plane 2, and both capturing and releasing of resources in the user data processing units 31 to 33 have also been controlled by this function. [0049] This embodiment is so designed as to eliminate the need for the C-plane 2 to closely recognize the band and number of sessions of the user data processing units 31 to 33, therefore the centralized resource management function is no longer necessary. [0050] In the prior art, the centralized resource management function is, by its nature, engaged in processing signals from a plurality of call control sections, thus causing a bottleneck in extending system capability. This embodiment, however, does not require this centralized resource management function, which leads to a greater potential for system expandability. [0051] When the plurality of user data processing units 31 to 33 have each different capability associated with available bands and sessions, the call control section has conventionally required the centralized resource management function to recognize the capability of each of the user data processing units. [0052] However, this embodiment allows the C-plane 2 to recognize only the above-described remaining resources of each of the user data processing units 31 to 33, therefore the C-plane 2 no longer needs to recognize the capability of each of the user data processing units 31 to 33. Accordingly, it is possible to easily construct a system using user data processing units 31 to 33 each having different capability. [0053] Thus, since this embodiment eliminates the function of closely managing resources from the C-plane 2, it no longer needs to have such a resource management processor as the conventional one, thereby enabling construction of a system with less processors. [0054] Furthermore, this embodiment does not require such a resource management processor as the conventional one, preventing a processing bottleneck caused by a specific processor even in installing additional call processors for expansion of the system capability. [0055] Moreover, in this embodiment, the user data processing units 31 to 33 closely manage by themselves their own resources. This eliminates the need for the C-plane 2 to be explicitly conscious of the capability of each of the user data processing units 31 to 33, so that the user data processing units 31 to 33 each having different capability can be mounted with one another in the network device 1. [0056] [0056]FIG. 2 is a block diagram showing a configuration of a packet communication system according to an example of the present invention. As apparent from FIG. 2, shown is a structure of an SGSN [Serving GPRS (General Packet Radio Service) Support Node] 6 in the packet communication system of a mobile communication network according to the example of the present invention. [0057] The SGSN 6 is located between an RNC (Radio Network Controller) 5 and a GGSN (Gateway GPRS Support Node) 7, and is responsible for relaying user data while encapsulating it in a packet communication performed between a moving user (mobile unit 3) and a Web server 8 and the like provided in an ISP (Internet Service Provider) or office LAN (Local Area Network) 200. The encapsulating is carried out based on a GTP (GPRS Tunneling protocol). [0058] Though the SGSN 6 and the GGSN 7 are directly connectable with each other, they are generally connected via a backbone network constructed by an IP (Internet Protocol) network 100. [0059] The configuration of the foregoing packet communication system and protocols utilized therefor are defined in 3GPP (3rd Generation Partnership Project) TS23.060 V3.14.0 (2002-12), chapter 5.4 and TS29.060 V3.15.0 (2002-12), Chapter 5.6 “User and Control Planes”, which provide international standards for third generation mobile communication. The RNC 5, the GGSN 7, and a Node B (radio base station) 4 are also defined by 3GPP with regard to their functionality, so the descriptions thereof will be omitted. [0060] In order to realize packet communication between the mobile unit 3 and the Web server 8, the SGSN 6 comprises a C-plane (call control section) communicating with the RNC 5/GGSN 7, and a U-plane having user data processing units 66 to 68. [0061] The user data processing units 66 to 68 each decapsulate the GTP encapsulated user data transmitted from the RNC 5, and encapsulate it again to send for the GGSN 7. To the contrary, the user data processing units 66 to 68 each decapsulate GTP encapsulated user data transmitted from the GGSN 7, and encapsulate it again to send for the RNC 5. [0062] The C-plane comprises a plurality of call processors 62 to 64, a load distribution unit 61 for distributing signals thereto, and a maintenance operation unit 65 providing a maintenance capability. The call processors 62, 63 and 64 have memories 621, 631 and 641, respectively, for storing the available resources ratio in each of the user data processing units 66 to 68. [0063] The user data processing units 66, 67 and 68 comprise resource management parts 661, 671 and 681, and GTP protocol parts 662, 672, 682, respectively. The resource management parts 661, 671 and 681 are operable for managing a status of band resources and the number-of-sessions resources in use of the circuits of the corresponding user data processing units and for capturing and releasing resources in response to a request from the C-plane. The GTP protocol parts 662, 672 and 682 are operable for encapsulating and decapsulating user data. [0064] FIGS. 3 to 6 are sequence charts showing operations of the packet communication system according to the example of the present invention. Referring now to FIGS. 2 to 6, description will be made for the operations of the packet communication system according to the example of the present invention. [0065] Upon restart of the system (a1 of FIG. 3), the call processor 62 recognizes the presence of all the user processing units 66 to 68 existing in the system (a2 of FIG. 3) by broadcast from the user data processing units 66 to 68 (a21 to a24 of FIG. 3). [0066] Alternatively, when the maintenance operation unit 65 notifies (a33 to a35 of FIG. 3) all the call processors 62 to 64 in the system of signals (a31, a32 of FIG. 3) sent from the user data processing units 66 to 68 to the maintenance operation unit 65, the call processor 62 recognizes the presence of all the user data processing units 66 to 68 existing in the system (a3 of FIG. 3). [0067] Alternatively, when the maintenance operation unit 65 reads out the presence of all the user data processing units 66 to 68 existing in the system that is stored in a database (not shown) managed by the maintenance operation unit 65 (a41 of FIG. 3) and then notifies all the call processor 62 to 64 (a42, a43 of FIG. 3) of it, the call processor 62 recognizes the presence of all the user data processing units 66 to 68 in the system (a4 of FIG. 3). [0068] The call processor 62 reserves an area in the memory 621 for storage of available resources ratios (hereinafter, referred to as remaining resource information) of all the user data processing units 66 to 68 existing in the system. Although not shown, other call processors 63 and 64 also perform the same processing as the call processor 62, that is, they reserve areas in the memories 631 and 641, respectively, for storage of remaining resource information of all the user data processing units 66 to 68 existing in the system. [0069] Upon receipt of a call setup signal (b0, b1 of FIG. 4), the call processor 62 ascertains the remaining resource information of each of the user data processing units 66 to 68 which is stored in the memory 621 thereby to select a user data processing unit having more remaining resources (user data processing unit 66 has the most remaining resources herein) (b12 of FIG. 4), and then sends a call setup request to the selected user data processing unit 66 (b21 of FIG. 4). [0070] Upon receipt of the call setup request, the user data processing unit 66 determines at the resource management part 661 whether the requested band and session are reservable (b22 of FIG. 4). If reservable, the resource management part 661 sends the call setup request to the GTP protocol part 662. (b23 of FIG. 4). [0071] Upon receipt of a call setup response from the resource management part 661 (b24 of FIG. 4), the user data processing unit 66 reads out the latest remaining resource information from the resource management part 661 (b25 of FIG. 4), prepares a response signal for the call processor 62, and then notifies the call processor 62 of the readout remaining resource information of its own circuit by attaching it to the response message (b26 of FIG. 4). [0072] Upon receipt of the response signal to the call setup request, the call processor 62 fetches the attached remaining resource information of the user data processing unit 66, and updates the remaining resource information of each of the user data processing units 66 to 68 which is stored in the memory 621 (b31 of FIG. 4). [0073] If the received response signal to the call setup request is a positive response, the call processor 62 stores in the memory 621 identification information of the user data processing unit 62 as call control information. Although not shown, other call processors 63 and 64 perform the same processing as the call processor 62. [0074] Next, upon receipt of a call release request (c0, c11 of FIG. 5), the call processor 62 specifies the active user data processing unit 66 in accordance with the call control information stored in the memory 621 (c12 of FIG. 5), and then sends a call release request to the specified user data processing unit 66 (c21 of FIG. 5). [0075] Upon receipt of the call release request, the user data processing unit 66 sends the call release request to the GTP protocol part 662 (c22 of FIG. 5). When a call release response is obtained from the GTP protocol part 662 (c23 of FIG. 5), the user data processing unit 66 releases the band and number of sessions at the resource management part 661 (c24 of FIG. 5). [0076] The user data processing unit 66 also reads out the latest remaining resource information from the resource management part 661 (c25 of FIG. 5), prepares a response signal for the call processor 62, and then notifies the call processor 62 of the readout remaining resource information of its own circuit by attaching it to the response message (c26 of FIG. 5). [0077] Upon receipt of the response signal to the call release request, the call processor 62 fetches the attached remaining resource information of the user data processing unit 66, and updates the remaining resource information of each of the user data processing units 66 to 68 which is stored in the memory 621 (c31 of FIG. 5). [0078] Meanwhile, when the call processor 62 receives a health check signal readout and directly transmitted from the resource management parts 661, 671 and 681 of the user data processing units 66, 67 and 68, respectively (d11 to d16 of FIG. 6) (d1 of FIG. 6), the call processor 62 fetches the remaining resource information of the user data processing units 66 to 68 that is transmitted together with the health check signal, and then updates the remaining resource information of each of the user data processing units 66 to 68 which is stored in the memory 621 (d31 of FIG. 6) (d3 of FIG. 6). [0079] Or alternatively, when the maintenance operation unit 65 performs health checking of the user data processing units 66 to 68 (d21, d22 of FIG. 6) and thereafter transmits to the call processor 62 the health check information read out from the resource management parts 661, 671 and 681 of the user data processing units 66, 67 and 68, respectively (d23 to d28 of FIG. 6) (d2 of FIG. 6), the call processor 62 fetches the remaining resource information of the user data processing units 66 to 68 that is transmitted together with the health check information from the maintenance operation unit 65, and then updates the remaining resource information of each of the user data processing units 66 to 68 which is stored in the memory 621 (d31 of FIG. 6) (d3 of FIG. 6). [0080] Thus, in this embodiment, the resource management function is provided to each of the user data processing units 66 to 68 so that the call processors 62, 63 and 64 may store only the remaining bands in memories 621, 631 and 641, respectively. Therefore, the system can easily be constructed without a centralized resource management function. Furthermore, system expandability to install additional call processors can be ensured and the capability of each of the user data processing units 66 to 68 can be isolated from the call processors 62 to 64. [0081] This embodiment has shown the case in which the call processors 62, 63 and 64 store in memories thereof 621, 631 and 641, respectively, the remaining resource information of the user data processing units 66 to 68, however, it is also allowable not to store the remaining resource information. This is realized when the call processors 62 to 64 simply select one of the plurality of user data processing units 66 to 68 in a sequential manner, through call setup processing sequences. [0082] By this, the call processors 62 to 64 no longer need to acquire the latest remaining resource information from the user data processing units 66 to 68 upon call setting and releasing or health checking. [0083] This embodiment has dealt with the case in which the foregoing processing procedure is applied to the SGSN 6, however, it is also applicable to the GGSN 7 which is another packet switch node in a mobile communication packet network, the RNC 5 which is another node in a mobile communication network, or an MSC (Mobile Switching Center) which is a node in a mobile communication line switching network. [0084] As described above, the present invention provides the foregoing constitution and operations and thereby offers several advantages such that a system can easily be constructed without the centralized resource management function, and system expandability to install additional call control processors can be ensured, and furthermore the capability of each user data processing unit can be isolated from the call control section (C-plane). Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5434852 *Aug 31, 1994Jul 18, 1995At&T Corp.Distributed processing architechture for control of broadband and narrowband communications networksUS5640678 *Jan 19, 1996Jun 17, 1997Kokusai Denshin Denwa Kabushiki KaishaMacrocell-microcell communication system with minimal mobile channel hand-offUS6909690 *Jan 14, 2000Jun 21, 2005Sprint Communications Company L.P.Call admission control in telecommunication networks* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS6975625 *Aug 20, 2001Dec 13, 2005Cisco Technology, Inc.Distributed call control processingUS7522607 *Jan 26, 2004Apr 21, 2009Sprint Communications Company LpCongestion handling in a packet communication systemUS8010677Aug 30, 2011Avaya Inc.Alternative bandwidth management algorithmUS8311207Nov 13, 2012Avaya Inc.Efficient and cost-effective distribution call admission controlUS8718261Jul 21, 2011May 6, 2014Avaya Inc.Efficient and cost-effective distributed call admission controlUS20050163126 *Jan 26, 2004Jul 28, 2005Bugenhagen Michael K.Congestion handling in a packet communication systemUS20110131331 *Dec 2, 2009Jun 2, 2011Avaya Inc.Alternative bandwidth management algorithmUS20150163090 *Dec 3, 2014Jun 11, 2015Fujitsu LimitedSystem for wireless communication and apparatus for wireless communicationCN102088402A *Sep 30, 2010Jun 8, 2011阿瓦雅公司Novel bandwidth management algorithmEP2330780A1 *Sep 29, 2010Jun 8, 2011Avaya Inc.Alternative bandwidth management algorithm* Cited by examinerClassifications U.S. Classification370/352International ClassificationH04L12/801, H04L12/911, H04L29/06, H04L29/08, H04W28/26, H04W88/14Cooperative ClassificationH04L67/1036, H04L67/1008, H04L67/1002, H04L47/15, H04W28/26, H04L12/5695, H04W88/14, H04L47/824, H04L47/808, H04L47/825, H04L47/822European ClassificationH04L12/56R, H04L29/08N9A1B, H04L29/08N9A13, H04L47/82B, H04L47/15, H04L47/82E, H04L47/80E, H04L47/82D, H04L29/08N9A, H04W28/26Legal EventsDateCodeEventDescriptionFeb 2, 2004ASAssignmentOwner name: NEC CORPORATION, JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TSUKAGOSHI, TSUTOMU;SUZUKI, NAOTO;SAEKI, KAZUSHI;AND OTHERS;REEL/FRAME:014950/0465Effective date: 20040123RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services