Linkage Model of a Typical Qtdnd System 1.2.2.2- Linkage Development Support Department

Qos Assurance Methods for Multimedia Communications zt2i3t4l5ee zt2a3gs zt2a3ge zc2o3n4t5e6n7ts low. The EF PHB requires a sufficiently large number of output ports to provide low delay, low loss, and low jitter. EF PHBs can be implemented if the output port's bandwidth is sufficiently large, combined with small buffer sizes and other network resources dedicated to EF packets, to allow the router's service rate for EF packets on an output port to exceed the arrival rate λ of packets at that port. This means that packets with PHB EF are considered with a pre-allocated amount of output bandwidth and a priority that ensures minimum loss, minimum delay and minimum jitter before being put into operation. PHB EF is suitable for channel simulation, leased line simulation, and real-time services such as voice, video without compromising on high loss, delay and jitter values. Figure 2.10 Example of EF installation Figure 2.10 shows an example of an EF PHB implementation. This is a simple priority queue scheduling technique. At the edges of the DS domain, EF packet traffic is prioritized according to the values agreed upon by the SLA. The EF queue in the figure needs to output packets at a rate higher than the packet arrival rate λ. To provide an EF PHB over an end-to-end DS domain, bandwidth at the output ports of the core routers needs to be allocated in advance to ensure the requirement μ > λ. This can be done by a pre-configured provisioning process. In the figure, EF packets are placed in the priority queue (the upper queue). With such a length, the queue can operate with μ > λ. Since EF was primarily used for real-time services such as voice and video, and since real-time services use UDP instead of TCP, RED is generally not suitable for EF queues because applications using UDP will not respond to random packet drop and RED will strip unnecessary packets. 2.2.4.2 Assured Forwarding (AF) PHB PHB AF is defined by RFC 2597. The purpose of PHB AF is to deliver packets reliably and therefore delay and jitter are considered less important than packet loss. PHB AF is suitable for non-real-time services such as applications using TCP. PHB AF first defines four classes: AF1, AF2, AF3, AF4. For each of these AF classes, packets are then classified into three subclasses with three distinct priority levels. Table 2.8 shows the four AF classes and 12 AF subclasses and the DSCP values for the 12 AF subclasses defined by RFC 2597. RFC 2597 also allows for more than three separate priority levels to be added for internal use. However, these separate priority levels will only have internal significance. PHB Class PHB Subclass Package type DSCP AF4 AF41 Short 100010 AF42 Medium 100100 AF43 High 100110 AF3 AF31 Short 011010 AF32 Medium 011100 AF33 High 011110 AF2 AF21 Short 010010 AF22 Medium 010100 AF23 High 010110 AF1 AF11 Short 001010 AF12 Medium 001100 AF13 High 001110 Table 2.8 AF DSCPs The AF PHB ensures that packets are forwarded with a high probability of delivery to the destination within the bounds of the rate agreed upon in an SLA. If AF traffic at an ingress port exceeds the pre-priority rate, which is considered non-compliant or “out of profile”, the excess packets will not be delivered to the destination with the same probability as the packets belonging to the defined traffic or “in profile” packets. When there is network congestion, the out of profile packets are dropped before the in profile packets are dropped. When service levels are defined using AF classes, different quantity and quality between AF classes can be realized by allocating different amounts of bandwidth and buffer space to the four AF classes. Unlike EF, most AF traffic is non-real-time traffic using TCP, and the RED queue management strategy is an AQM (Adaptive Queue Management) strategy suitable for use in AF PHBs. The four AF PHB layers can be implemented as four separate queues. The output port bandwidth is divided into four AF queues. For each AF queue, packets are marked with three “colors” corresponding to three separate priority levels. In addition to the 32 DSCP 1 groups defined in Table 2.8, 21 DSCPs have been standardized as follows: one for PHB EF, 12 for PHB AF, and 8 for CSCP. There are 11 DSCP 1 groups still available for other standards. 2.2.5.Example of Differentiated Services We will look at an example of the Differentiated Service model and mechanism of operation. The architecture of Differentiated Service consists of two basic sets of functions: Edge functions: include packet classification and traffic conditioning. At the inbound edge of the network, incoming packets are marked. In particular, the DS field in the packet header is set to a certain value. For example, in Figure 2.12, packets sent from H1 to H3 are marked at R1, while packets from H2 to H4 are marked at R2. The labels on the received packets identify the service class to which they belong. Different traffic classes receive different services in the core network. The RFC definition uses the term behavior aggregate rather than the term traffic class. After being marked, a packet can be forwarded immediately into the network, delayed for a period of time before being forwarded, or dropped. We will see that there are many factors that affect how a packet is marked, and whether it is forwarded immediately, delayed, or dropped. Figure 2.12 DiffServ Example Core functionality: When a DS-marked packet arrives at a Diffservcapable router, the packet is forwarded to the next router based on Per-hop behavior is associated with packet classes. Per-hop behavior affects router buffers and the bandwidth shared between competing classes. An important principle of the Differentiated Service architecture is that a router's per-hop behavior is based only on the packet's marking or the class to which it belongs. Therefore, if packets sent from H1 to H3 as shown in the figure receive the same marking as packets from H2 to H4, then the network routers treat the packets exactly the same, regardless of whether the packet originated from H1 or H2. For example, R3 does not distinguish between packets from h1 and H2 when forwarding packets to R4. Therefore, the Differentiated Service architecture avoids the need to maintain router state about separate source-destination pairs, which is important for network scalability. Chapter Conclusion Chapter 2 has presented and clarified two main models of deploying and installing quality of service in IP networks. While the traditional best-effort model has many disadvantages, later models such as IntServ and DiffServ have partly solved the problems that best-effort could not solve. IntServ follows the direction of ensuring quality of service for each separate flow, it is built similar to the circuit switching model with the use of the RSVP resource reservation protocol. IntSer is suitable for services that require fixed bandwidth that is not shared such as VoIP services, multicast TV services. However, IntSer has disadvantages such as using a lot of network resources, low scalability and lack of flexibility. DiffServ was born with the idea of solving the disadvantages of the IntServ model. DiffServ follows the direction of ensuring quality based on the principle of hop-by-hop behavior based on the priority of marked packets. The policy for different types of traffic is decided by the administrator and can be changed according to reality, so it is very flexible. DiffServ makes better use of network resources, avoiding idle bandwidth and processing capacity on routers. In addition, the DifServ model can be deployed on many independent domains, so the ability to expand the network becomes easy. Chapter 3: METHODS TO ENSURE QoS FOR MULTIMEDIA COMMUNICATIONS In packet-switched networks, different packet flows often have to share the transmission medium all the way to the destination station. To ensure the fair and efficient allocation of bandwidth to flows, appropriate serving mechanisms are required at network nodes, especially at gateways or routers, where many different data flows often pass through. The scheduler is responsible for serving packets of the selected flow and deciding which packet will be served next. Here, a flow is understood as a set of packets belonging to the same priority class, or originating from the same source, or having the same source and destination addresses, etc. In normal state when there is no congestion, packets will be sent as soon as they are delivered. In case of congestion, if QoS assurance methods are not applied, prolonged congestion can cause packet drops, affecting service quality. In some cases, congestion is prolonged and widespread in the network, which can easily lead to the network being "frozen", or many packets being dropped, seriously affecting service quality. Therefore, in this chapter, in sections 3.2 and 3.3, we introduce some typical network traffic load monitoring techniques to predict and prevent congestion before it occurs through the measure of dropping (removing) packets early when there are signs of impending congestion. 3.1. DropTail method DropTail is a simple, traditional queue management method based on FIFO mechanism. All incoming packets are placed in the queue, when the queue is full, the later packets are dropped. Due to its simplicity and ease of implementation, DropTail has been used for many years on Internet router systems. However, this algorithm has the following disadvantages: − Cannot avoid the phenomenon of “Lock out”: Occurs when 1 or several traffic streams monopolize the queue, making packets of other connections unable to pass through the router. This phenomenon greatly affects reliable transmission protocols such as TCP. According to the anti-congestion algorithm, when locked out, the TCP connection stream will reduce the window size and reduce the packet transmission speed exponentially. − Can cause Global Synchronization: This is the result of a severe “Lock out” phenomenon. Some neighboring routers have their queues monopolized by a number of connections, causing a series of other TCP connections to be unable to pass through and simultaneously reducing the transmission speed. After those monopolized connections are temporarily suspended, Once the queue is cleared, it takes a considerable amount of time for TCP connections to return to their original speed. − Full Queue phenomenon: Data transmitted on the Internet often has an explosion, packets arriving at the router are often in clusters rather than in turn. Therefore, the operating mechanism of DropTail makes the queue easily full for a long period of time, leading to the average delay time of large packets. To avoid this phenomenon, with DropTail, the only way is to increase the router's buffer, this method is very expensive and ineffective. − No QoS guarantee: With the DropTail mechanism, there is no way to prioritize important packets to be transmitted through the router earlier when all are in the queue. Meanwhile, with multimedia communication, ensuring connection and stable speed is extremely important and the DropTail algorithm cannot satisfy. The problem of choosing the buffer size of the routers in the network is to “absorb” short bursts of traffic without causing too much queuing delay. This is necessary in bursty data transmission. The queue size determines the size of the packet bursts (traffic spikes) that we want to be able to transmit without being dropped at the routers. In IP-based application networks, packet dropping is an important mechanism for indirectly reporting congestion to end stations. A solution that prevents router queues from filling up while reducing the packet drop rate is called dynamic queue management. 3.2. Random elimination method – RED 3.2.1 Overview RED (Random Early Detection of congestion; Random Early Drop) is one of the first AQM algorithms proposed in 1993 by Sally Floyd and Van Jacobson, two scientists at the Lawrence Berkeley Laboratory of the University of California, USA. Due to its outstanding advantages compared to previous queue management algorithms, RED has been widely installed and deployed on the Internet. The most fundamental point of their work is that the most effective place to detect congestion and react to it is at the gateway or router. Source entities (senders) can also do this by estimating end-to-end delay, throughput variability, or the rate of packet retransmissions due to drop. However, the sender and receiver view of a particular connection cannot tell which gateways on the network are congested, and cannot distinguish between propagation delay and queuing delay. Only the gateway has a true view of the state of the queue, the link share of the connections passing through it at any given time, and the quality of service requirements of the traffic flows. The RED gateway monitors the average queue length, which detects early signs of impending congestion (average queue length exceeding a predetermined threshold) and reacts appropriately in one of two ways: − Drop incoming packets with a certain probability, to indirectly inform the source of congestion, the source needs to reduce the transmission rate to keep the queue from filling up, maintaining the ability to absorb incoming traffic spikes. − Mark “congestion” with a certain probability in the ECN field in the header of TCP packets to notify the source (the receiving entity will copy this bit into the acknowledgement packet). Figure 3. 1 RED algorithm The main goal of RED is to avoid congestion by keeping the average queue size within a sufficiently small and stable region, which also means keeping the queuing delay sufficiently small and stable. Achieving this goal also helps: avoid global synchronization, not resist bursty traffic flows (i.e. flows with low average throughput but high volatility), and maintain an upper bound on the average queue size even in the absence of cooperation from transport layer protocols. To achieve the above goals, RED gateways must do the following: − The first is to detect congestion early and react appropriately to keep the average queue size small enough to keep the network operating in the low latency, high throughput region, while still allowing the queue size to fluctuate within a certain range to absorb short-term fluctuations. As discussed above, the gateway is the most appropriate place to detect congestion and is also the most appropriate place to decide which specific connection to report congestion to. − The second thing is to notify the source of congestion. This is done by marking and notifying the source to reduce traffic. Normally the RED gateway will randomly drop packets. However, if congestion If congestion is detected before the queue is full, it should be combined with packet marking to signal congestion. The RED gateway has two options: drop or mark; where marking is done by marking the ECN field of the packet with a certain probability, to signal the source to reduce the traffic entering the network. − An important goal that RED gateways need to achieve is to avoid global synchronization and not to resist traffic flows that have a sudden characteristic. Global synchronization occurs when all connections simultaneously reduce their transmission window size, leading to a severe drop in throughput at the same time. On the other hand, Drop Tail or Random Drop strategies are very sensitive to sudden flows; that is, the gateway queue will often overflow when packets from these flows arrive. To avoid these two phenomena, gateways can use special algorithms to detect congestion and decide which connections will be notified of congestion at the gateway. The RED gateway randomly selects incoming packets to mark; with this method, the probability of marking a packet from a particular connection is proportional to the connection's shared bandwidth at the gateway. − Another goal is to control the average queue size even without cooperation from the source entities. This can be done by dropping packets when the average size exceeds an upper threshold (instead of marking it). This approach is necessary in cases where most connections have transmission times that are less than the round-trip time, or where the source entities are not able to reduce traffic in response to marking or dropping packets (such as UDP flows). 3.2.2 Algorithm This section describes the algorithm for RED gateways. RED gateways calculate the average queue size using a low-pass filter. This average queue size is compared with two thresholds: minth and maxth. When the average queue size is less than the lower threshold, no incoming packets are marked or dropped; when the average queue size is greater than the upper threshold, all incoming packets are dropped. When the average queue size is between minth and maxth, each incoming packet is marked or dropped with a probability pa, where pa is a function of the average queue size avg; the probability of marking or dropping a packet for a particular connection is proportional to the bandwidth share of that connection at the gateway. The general algorithm for a RED gateway is described as follows: [5] For each packet arrival Caculate the average queue size avg If minth ≤ avg < maxth div.maincontent .s1 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 15pt; } div.maincontent .s2 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: bold; text-decoration: none; font-size: 15pt; } div.maincontent .p { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; margin:0pt; } div.maincontent p { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; margin:0pt; } div.maincontent .s3 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: bold; text-decoration: none; font-size: 14pt; } div.maincontent .s4 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; } div.maincontent .s5 { color: black; font-family:"Times New Roman", serif; font-style: italic; font-weight: normal; text-decoration: none; font-size: 14pt; } div.maincontent .s6 { color: black; font-family:"Times New Roman", serif; font-style: italic; font-weight: bold; text-decoration: none; font-size: 14pt; } div.maincontent .s7 { color: black; font-family:Wingdings; font-style: normal; font-weight: normal; text-decoration: none; font-size: 14pt; } div.maincontent .s8 { color: black; font-family:Arial, sans-serif; font-style: italic; font-weight: bold; text-decoration: none; font-size: 15pt; } div.maincontent .s9 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: bold; text-decoration: none; font-size: 14pt; } div.maincontent .s10 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 9pt; vertical-align: 6pt; } div.maincontent .s11 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 13pt; } div.maincontent .s12 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-decoration: none; font-size: 10pt; } div.maincontent .s13 { color: black; font-family:"Times New Roman", serif; font-style: normal; font-weight: normal; text-d
Model system to assess the suitability of Vietnam's population-economic development process - 21

1.2.2.1- Platform parts

The basic components of the QTDND system include:

♦ CS QTDNDs: Are units that directly provide savings, credit, banking and non-banking services to customers. In any country, CS QTDNDs are the starting point of the process of building a QTDND system and are considered the "gateway" for members to join the QTDND system. Normally, the activities of CS QTDNDs are limited to a certain area according to the principle that CS QTDNDs cannot compete with each other, or in other words, in an area there is only one CS QTDND operating. This is completely different from other types of credit institutions.

♦ Lead People's Credit Fund: Is an organization that carries out business activities mainly to support the CS People's Credit Fund in the area (region or country) or coordinates with the CS People's Credit Fund to provide financial services that the CS People's Credit Fund is not capable of performing or is difficult to perform effectively. Lead People's Credit Fund often performs the task of regulating available capital, acting as a payment focal point for the entire system, providing co-financing loans with the CS People's Credit Fund, and seeking domestic and foreign capital sources to expand the scale of operations of the CS People's Credit Fund. In principle, lead People's Credit Funds are not allowed to have business activities that compete with the CS People's Credit Funds.

Study

Auditing

System Coordinating Agency

Safety Fund

Note : Support relationship, development association

Capital ownership relations

Train

QTDND

clue

CS QTDND

	CS QTDND		CS QTDND	CS QTDND	CS QTDND		CS QTDND

Maybe you are interested!

Diagram 1. 1- Linkage model of a typical QTDND system 1.2.2.2- Development linkage support department

The development association support unit was established from the need of the QTDNDs to gather together to cooperate, support each other and promote the combined strength of the entire system. In any country, each QTDND is an independent and autonomous legal entity, but at some point, the QTDNDs realize the need to unite to solve strategic issues, helping them develop and serve their members better. That is the reason for the establishment of the development association support unit.

In general, the development linkage support unit can include many different organizations depending on how the QTDND system model is arranged to suit the practical conditions of each country. However, regardless of the model,

In addition, this department also performs the same basic functions, which are: Representing the QTDND system in relations with state agencies, domestic and foreign partners; protecting the legitimate rights and interests of the QTDND system as well as of QTDND members; building and coordinating the implementation of development orientations to ensure the harmony of the QTDND system; proposing business processes, operating standards and internal management regulations applicable to the entire QTDND system; researching and designing products and services to help member QTDNDs satisfy customer needs; coordinating linkage mechanisms to improve operational efficiency and ensure safety for the units constituting the QTDND system such as: regulating available capital, system safety fund, auditing, training, etc.; Support the units that make up the QTDND system in applying scientific and technological advances to management and professional activities, especially information technology and banking technology; promote the image to enhance the position and reputation of the QTDND system domestically and internationally.

1.2.3- Organization and operation of basic units constituting the QTDND system

1.2.3.1- Grassroots People's Credit Fund

a- Organization

♦ Members and Board of Directors:

- Members: In the QTDND system in any country, members play the most important role in the process of establishing, operating and developing the QTDND system. In fact, members are both owners, customers and managers, operators and controllers of the QTDND.

In general, joining the QTDND is very easy and convenient for all subjects in accordance with the spirit of the cooperative principle. In addition, some countries regulate the admission of auxiliary members in order to create favorable conditions.

for many customers to access QTDND services; at the same time, to take advantage of idle capital sources to lend to members.

In general, membership is terminated when: An individual member dies, voluntarily leaves the QTDND or is expelled; a legal entity member is dissolved, liquidated or bankrupt.

In addition, in many countries, members who do not conduct transactions with the QTDND for a certain period of time (usually 12 months) are considered “inactive members” and will be deprived of the right to vote and run for positions in the QTDND until they are recognized as “active members”. This provision is intended to bind members to have a closer, more active relationship with the QTDND.

- Congress of members: In any QTDND model, the Congress of members is always identified as the highest decision-making authority. Depending on the number of members, the QTDND can organize the Congress of members in the form of a general congress (in case the QTDND has few members) or a congress of delegates (in case the QTDND has too many members). The election of delegates to attend the congress of members is conducted democratically and publicly in each locality. This can be seen as a way for members to authorize their representatives to attend the Congress of members. The process, content and authority of the general congress are exactly the same as the congress of delegates to members.

Regarding the method and procedure, it may vary from country to country, but in general, the General Meeting of Shareholders has the same basic powers, which are: Deciding on amending, supplementing and approving the Charter and internal regulations of the People's Credit Fund; electing and dismissing members of the Board of Directors and Supervisory Board; approving the previous year's periodic report and the following year's activity program; determining the bonus level for the established capital contribution and the regular capital contribution; deciding on the People's Credit Fund's joining other organizations; appointing auditors.

internal; handle other important issues related to the organization and operation of the People's Army.

The General Meeting of Shareholders is held periodically once a year, convened by the Board of Directors to pass resolutions, handle existing issues of the previous year and orient activities for the following year of the QTDND, called the annual General Meeting of Shareholders . The General Meeting of Shareholders is held to handle urgent issues beyond the authority of the Board of Directors, called the extraordinary General Meeting of Shareholders . The extraordinary General Meeting of Shareholders can be convened at any time by the Chairman of the Board of Directors, some members of the Board of Directors, the Supervisory Board or when some official members request. These issues are often specifically regulated in the QTDND Charter.

♦ Management, control and operation apparatus : In different countries, the management, control and operation apparatus of the People's Credit Fund is organized in many different forms. For example, in Africa, the Board of Directors is a mixed body that performs all functions of management, control and credit policy. In some other countries, the Board of Directors is the body that establishes and directs the activities of the Credit Committee and the Supervisory Board. These organizational models are generally not suitable for many different reasons, such as: (i) The roles and responsibilities are too broad; (ii) Heavy operation (such a Board of Directors often has up to 15 members); (iii) Lack of mutual control between functional departments; (iv) Difficulty in ensuring information confidentiality in an agency with such a large number of members; (v) Often tends to increase the concentration of power.

Reality has proven that to ensure a safe, effective and healthy development of a People's Credit Fund, there must be a clear division of authority between agencies under the Central Military Commission. The following is a typical organizational structure model of a People's Credit Fund that meets this criterion and has been successfully applied in Canada and several other countries.

- Board of Directors: The Board of Directors has the function of ensuring the implementation of the objectives of the People's Credit Fund and managing the activities of the People's Credit Fund in the best way. To perform that function, the Board of Directors has the following main tasks: Ensuring that the activities of the People's Credit Fund comply with the law, regulations, standards, codes of ethics, and regulations applicable to the Board of Directors and the People's Credit Fund; implementing the decisions of the General Meeting of Shareholders; ensuring that the People's Credit Fund properly implements sound and prudent management practices; providing authentic documents and information related to the People's Credit Fund to competent State agencies; regulating deposit interest rate policies, credit and pricing of products and services provided by the People's Credit Fund; approving or authorizing others to approve applications for membership of the People's Credit Fund of new members and carrying out the suspension and expulsion of members; implementing or controlling the implementation of the People's Credit Fund's investments; decide and plan the implementation of the socio-economic goals of the People's Army; appoint authorized persons to sign contracts and other documents of the People's Army on behalf of the People's Army; report on the results of performing tasks and present annual reports to the General Meeting of Shareholders; supervise the implementation of tasks of the Executive Board and specialized departments of the People's Army in accordance with the provisions of law, standards and professional ethics; hire or dismiss the Executive Director; prescribe the recruitment and dismissal process and working conditions for the People's Army employees; convene and prepare necessary documents for the General Meeting of Shareholders, including amending and supplementing the Charter.

The Board of Directors meets periodically or at the request of the Chairman of the Board of Directors or a certain number of Board members. When a decision needs to be made, the Board of Directors votes by majority vote; in the event that the number of votes in favor is equal to the number of votes against, the person chairing the meeting has the deciding vote.

Election

Monitor

Election

Appointment, direction

DIRECTOR

DOC

Control

Operation

BOARD OF DIRECTORS

BOARD OF SUPERVISION

Information

BOARD OF SUPERVISION

Control

MEETING OF MEMBERS (OR MEETING OF MEMBER REPRESENTATIVES)

In many countries, the law stipulates that the Board of Directors must establish a Supervisory Board under the Board of Directors consisting of at least 3 members of the Board of Directors, except for the General Director. The main functions of the Supervisory Board are: Researching and reporting to the Board of Directors on the results of inspections and audits of the People's Credit Fund; monitoring recommendations and implementation of measures to overcome shortcomings stated in inspection and audit reports; researching reviewed financial statements and making recommendations before the Board of Directors approves; performing other tasks assigned by the Board of Directors.

Member

Accountant

Credit

Capital

Treasurer

Diagram 1.2 - Organizational structure of a typical Communist Party of Vietnam

- Supervisory Board: Similar to the Board of Directors, the Supervisory Board is elected by the Executive Board to represent the members in supervising all aspects of the activities of the People's Credit Fund. The activities of the Supervisory Board aim to ensure that the People's Credit Fund operates in compliance with the law, the People's Credit Fund's charter and the resolutions of the Executive Board. To achieve that purpose, the Supervisory Board performs the following main tasks: Ensuring compliance with professional ethics; ensuring that the managers and operators of the People's Credit Fund perform their duties in the most appropriate manner; ensuring respect for the rights of members; ensuring that the People's Credit Fund promotes economic, social and cooperative education; ensuring that the People's Credit Fund facilitates cooperation among members, between members and the People's Credit Fund and between the People's Credit Fund and other cooperative organizations; ensuring the People's Credit Fund's participation in community development effectively and in accordance with cooperative values; Ensure the application of cooperative values in the management and business activities of the People's Credit Fund; ensure that the admission, suspension or expulsion of members complies with the provisions of law and the provisions of the People's Credit Fund; convene an extraordinary General Meeting of Members when necessary; send the term report of the Supervisory Board to the Board of Directors and present it to the General Meeting of Members; supervise compliance with the law, charter and internal regulations at the People's Credit Fund; receive, process or transfer to relevant departments for processing and respond to complaints from members.

Members of the Board of Directors and Supervisory Board usually serve a term of 3-5 years and can be re-elected. Many countries apply the principle of re-election of one-third of the members of the Board of Directors and Supervisory Board on an annual rotation basis. Some countries stipulate that the term of the Board of Directors cannot coincide with the term of the Supervisory Board to avoid compromise or forming teams that affect the health of the QTDND. Normally, members of the Board of Directors and Supervisory Board (except the General Director) do not receive salaries but only receive public service remuneration.

Comment