JPH1051570A - Network current money system and management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve a quality and a performance and characteristics by serving various services freely and flexibly, without changing a charge system of a network and motivating subscribers for network cooperation. SOLUTION: An exchange 104 on a network and a network current money center 107 are connected. The center is provided with a packet transmitter- receiver sending/receiving a packet having each area of 'packet type', 'object subscriber ID' and 'network current money amount', able to be exchanged with various network resources and services, a memory storing a network current money residual amount by subscribers 101-103, and a processor reading/ writing each area and updating the network current money residual amount depending on the content.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a network currency system and a management method using a newly defined network currency.

[0002]

2. Description of the Related Art In a conventional communication network service, a predetermined communication function is provided with a predetermined quality, and a user pays for the communication function to a network service provider. The contents of service contracts, especially fees, are strictly defined. It is difficult to change the actual fee often and it is not preferable because of the stability of the service. Furthermore, it is very difficult to change the fee structure according to the traffic and network conditions from moment to moment because the subscriber needs to be able to confirm the conditions in terms of the transparency of the charges. On the other hand, the communication network service has a slight difference in quality or the like depending on the usage status of other subscribers or the current status of the network. Usually, even if the quality is slightly inferior, it satisfies a predetermined quality standard. These differences also occur between communications and subscribers who pay the same fee. For subscribers, discounts are the strongest desire. Therefore, there is a need for a method for easily and dynamically providing fee discounts and various fee systems in a form different from the fee in the conventional sense, and for more strongly motivating subscribers to use the network service. Further, even if the network resources are optimally discounted, a change in the situation may cause a desire from the network to move away from the optimal allocation and to perform the reallocation. Alternatively, a situation may arise between the subscribers that they want to make available the allocated resources. It is conceivable that such a kind of transaction is realized as a service-to-service barter by providing an intermediate agent instead of a normal fee / billing. In fact,
In addition to telecommunications, there are a variety of transactions and related services ranging from bartering and trading with securities, to discount coupons that can be given each time you use them, and commodity vouchers that can be used several times. There is a form.

[0003]

Conventionally, subscriber needs include the realization of various network services and the realization of various discounts associated therewith. However, excessively complicated fee structure is not preferable because it makes it difficult to understand services. On the other hand, network service providers want to easily realize flexible and diverse fee systems and fee services. It is also desirable that the network service can be motivated to use the network service again. It is difficult to directly respond to such demands with the flexibility of the tariff system. In addition, a stochastic quality difference occurs even within the same fee level, and there is a case where it is desired to perform some processing for this as well. Furthermore, the quality and performance of network services depend on subscriber behavior,
It is advantageous for network service providers to encourage cooperative subscribers to the network and be penalized for those who do not. However, performing such processing with a direct fee structure is extreme.
An object of the present invention is to improve such problems and to provide various services freely and flexibly without changing the fee system. It is another object of the present invention to provide a kind of reward to cooperating subscribers for the benefit of the whole network, to motivate the cooperation of the subscribers to the network, and to improve the quality and performance characteristics. And

[0004]

In order to achieve the above object, the present invention introduces a concept of a network currency which can be exchanged for various network services, instead of a direct fee form. The network currency balance is managed for each subscriber, and the balance is paid out when various services are used, and when there is cooperation with the network, the network pays the subscriber to reduce the conventional fixed fee. Provide flexible and diverse communication services. In addition, using the network currency as a broker, transactions such as network resource interchange between subscribers and between subscribers and the network,
Conduct negotiations. The network service provider does not pay out the network currency, which is the "right to use the network", unless the network is used, so that an effect of enclosing subscribers can be expected. For example, at the time of congestion, the network pays out the cooperation fee to the subscriber who controlled the recall, and the network currency is paid out to the subscriber who has many recalls, thereby encouraging the suppression of the recall, thereby reducing the congestion. We aim at reduction. As another example, a call that uses a specific line group is bypassed and reset, and a call that requires the use of the same line group is set for a free line generated by the call. At this time, the network encourages the subscriber of the rerouted and re-established call by paying the network currency corresponding to the cooperation fee by the network. As another example, when the network resource cannot be found, the subscriber requests the network to negotiate that the required network resource has been transferred because the user pays in the network currency. For the subscriber using the required network resources, the network negotiates, "I want to pay the network currency and transfer the network resources." When the negotiation is completed, the network currency balance is updated for these subscribers. This is an inter-user network resource transaction based on network currency. The network currency can be set independently of the fee structure, providing more flexible services. As yet another example, a subscriber may request network resources in a non-priority class, and when not available, pay network currency to obtain network resources in a priority class slot. This is a priority class transaction in network currency. The following is an example of a "blessing" and giving winners network currency. This is a kind of discount service, but it is equivalent to giving a gift certificate that can be exchanged for a network service or the like. A final example is to give subscribers with high billing amounts network currency, which is a kind of large discount. There is also a method in which a charge (invoice amount) is used in place of the network currency, and in the processing of the toll center, the amount to be charged to the subscriber is directly increased or decreased in the toll system to settle.

[0005]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The embodiments of the present invention will be described below by showing embodiments including drawings. (First Embodiment) This embodiment is an application example of a network currency at the time of congestion. When traffic exceeding the processing capacity is added to the network, a congestion state occurs. At this time, a major cause of the increase in congestion is a subscriber recall. The call to the congested object is connected to a talkie such as "The call is congested and should be called again later." However, since the subscriber repeats the call, the congested state is not easily resolved.
In this embodiment, a network currency is paid out as an incentive to a subscriber who has not performed a recall for a congested target, and the network currency is collected from the subscriber for a call to a congested target. Suppress calls, reduce congestion and achieve early recovery. FIG. 1 shows a target network of this embodiment. The exchanges 104 and 105 are connected by a line, and subscribers (terminals) 101 to 1 through a subscriber line.
03 is housed. These exchanges are connected to the network control center 106 via signal lines. Note that “101”, “102”, and “103” indicate the subscriber IDs of the subscribers 101, 102, and 103, respectively. The network currency center 107 is connected to the exchange 1 via a signal line.
It is tied to 04. Note that a form in which the network currency center function of the present embodiment is accommodated in the exchange 104 is also conceivable. Since this can be easily inferred from the following description, the description is omitted. The detection, regulation, and cancellation of congestion are performed by a conventional technique. Now, the incoming call congestion to the subscriber 103 or an area including the subscriber 103 is detected by the exchange 105 and notified to the network control center 106. The center instructs the exchange 104 via a signal line to regulate calls to the congested subscriber 103 or the congested local exchange 105. For example, if subscriber 101 is a congested subscriber 10
It is assumed that communication with respect to No. 3 has been performed. At this time, the exchange 104
Recognizes that the call is subject to regulation, regulates the call, and stores the table in the exchange 104 (FIG. 2).
First, the subject of regulation (in this case, the subscriber 103) and the calling subscriber I
D (101 in this case) is registered, and an initial value “0” of the number of recalls in the table is set. Thereafter, the exchange 104
When a call is made to a congestion target, the call is regulated and the table is referred to. If the call is a recall (that is, if the call is to the same target), the number of recalls is set to “+1”. further,
The exchange 105 detects that the congestion has subsided, and notifies the network control center 106 of this through a signal line. The center notifies the exchange 104 of the release of the congestion regulation.

The exchange 104 releases the congestion restriction and performs the following processing based on the table of FIG. (1) A packet having a predetermined packet payload of FIG. 3A is transferred to the calling subscriber I described in the table of FIG.
Create for each D. Write “clearing” in the packet type area. (2) Put the calling subscriber ID in the table of FIG. 2 in the subscriber ID area with the packet. (3) In the table of FIG. 2, if the number of recalls of the calling subscriber is "0", a predetermined amount "a" is inserted in the network currency settlement amount column, and the number of recalls is "n". If so, "-bn" is set in the same column using a predetermined penalty amount "b" per recall. (4) This packet is sent to the network currency center 107 via a signal line. As shown in Fig. 5,
There are packet transmission / reception devices 501 and 504 that transmit / receive packets to / from an exchange via a signal line. The received packet is processed by the processor 502. The network currency balance (FIG. 4) for each subscriber stored in the memory 503 is updated according to the processed result. Specifically, the packet is received by the packet receiving apparatus 501 in FIG. 5, the subscriber 502 recognizes the subscriber ID and the settlement amount, and the network currency balance corresponding to the subscriber (the contents as shown in FIG.
Is stored as "a" if the settlement amount is "a"
And if it is “−bn”, it is decreased by “−bn” and stored in the memory 503. Next, the processor 502
Creates a network currency balance notification packet (FIG. 3B) updated and stored for the subscriber. In this case, the packet type is “notification”, the ID of the subscriber to be notified is put in the target subscriber ID area, and the updated network currency balance is put in the network currency amount area. The created packet is sent from the exchange 104 to the subscriber (for example, 101 in FIG. 1) via the packet transmission device 504 via a signal line.

FIG. 6 shows a flowchart from the occurrence of congestion to the time during regulation. In response to the occurrence of congestion (step 601), for example, the switch 105 detects congestion (step 60).
2). The detection is notified to the network control center 106, and the center instructs the exchange to restrict congestion (step 603). Each switch, eg, switch 104, performs congestion control (step 604). Here, for example, subscriber 1
01 to the congestion target (step 6)
08). The exchange that recognizes that the call is subject to congestion regulation is searched for a line that matches the calling subscriber ID (eg, 101) and the regulation subject (eg, 103) on the table shown in FIG. 2 (step 605). . If any (Step 6
Since the call is a recall, the number of recalls is increased by "1" (step 609). If not (NO in step 606), a line having the calling subscriber ID and the restriction target is added, and an initial value “0” of the number of recalls is set (step 607).

FIG. 7 shows a flowchart at the end of congestion. The end of congestion (step 701) is determined by, for example,
5 (step 702), and notifies it to the network control center 106. The center instructs each exchange to release congestion regulation (step 703). For example, the exchange 104 releases the congestion restriction (step 70).
4) In the table of FIG. 2 held by the same exchange, read and delete, one by one, the rows in which the items to be restricted are the same as those for which congestion restriction has been released this time (for example, 103) (step). 705), the following processing is performed until there is no corresponding line (step 706). That is, the exchange 10
4 creates the clearing packet of FIG. 3 (a) corresponding to the calling subscriber of the line and transmits it to the network currency center 106 (step 707). Network Currency Center 106
Receives the packet (step 708), and reads out the subscriber ID and the network currency settlement amount from the packet (step 709). The network currency balance table of FIG. 4 of the center is searched for a row having the subscriber ID, and the network currency balance is updated based on the settlement amount (step 710). Furthermore, for that subscriber,
A new network currency balance is notified by creating and sending the notification packet of FIG. 3B (step 711).
Although the present embodiment has been described based on incoming congestion, outgoing congestion and relay congestion can be easily analogized. Basically, it is also possible to cope with billing. In this case, the charge center and the network currency center are replaced with the charge and the network currency, respectively. In the present embodiment, in the case of responding by charging, for the purpose of obtaining a recall suppression incentive,
The network currency was used in view of the fact that some malicious subscribers may cause a first trial call for an object that is likely to be intentionally congested.

(Second Embodiment) FIG. 8 shows a network configuration of this embodiment. There are exchanges 801 to 803, and lines 810 to 812 are provided between the exchanges. Each exchange houses subscribers (terminals) 804 to 809. Note that “804 to 809” are the subscribers 804 respectively.
809 indicates a subscriber ID. Now subscribers 804, 80
It is assumed that a call is set up using a line 810 between the exchanges 801 and 802 in order to perform communication between the exchanges 5. Here, it is assumed that a communication request between the subscribers 806 and 809 has occurred. Line 8
Since 10 is in use, it is conceivable to set up a call via the exchange 803 using the lines 811 and 812. Here, it is assumed that a call between the subscribers 804 and 805 has a severe request for information transfer delay, for example, and two-link connection is not permitted and only one-link connection is possible. Conventionally, the subscriber 806,
The call between 809 is a lost call. From the beginning, a call between the lines 804 and 805, which can be connected by two links, may be connected using the lines 811 and 812. However, this would not be suitable because it would not be possible to answer call requests between subscribers 808 and 809 or between subscribers 806 and 807. In the present embodiment, calls that have already been set (between the subscribers 804 and 805) are transferred to the subscribers 806 and 809.
When a one-link connection request is generated between the lines 811, 8
It is assumed that the connection is re-established via the connection 12. The network pays out the network currency for the instantaneous interruption of the call that may occur at this time or the quality deterioration (it is considered to be slightly lower than the quality of the one-link connection actually received but within an allowable range). This motivates the subscriber to approve the change. It is conceivable to reduce the actual charge. However, the charge for the call does not originally depend on the number of via links, and when the line 810 is occupied by calls between the subscribers 806 and 809, the two links are connected to the lines 811 and 812 at the same charge. Considering this, it is not appropriate to respond by charging. This embodiment is also applicable as an embodiment for a dedicated line. Also, call resetting itself is a conventional technique.

FIG. 9 shows a flowchart of this embodiment.
The configuration of the packet used in this embodiment is the same as that of the first embodiment (FIG. 3). In this embodiment, the subscriber 8 has already
It is assumed that a call is set up between 04 and 805 via a line 810. Now, it is assumed that there is a call connection request between the subscribers 806 and 809 (step 901). This is detected when the originating local exchange 802 receives the SETUP signal from the originating subscriber 806. The quality / connection request class such as one-link connection is described in the SETUP signal.
The exchange 802 detects that it is trying to seize the line 810 but is in a conversation (step 902). Since it is necessary to make a one-link connection, the exchange 802 extracts a non-one-link connection request call that is capturing the line (step 903), diverts the call, and attempts to set up a new connection request call. Then, for example, the extracted subscriber 80
A reset request packet for notifying that the call is to be reset is created and transmitted to the calling and called subscribers between 4,805 (step 904). The ID of the packet is held. Next, a negotiation packet (FIG. 3C) is generated and transmitted (step 905). In the subscriber ID area in the negotiation packet for the calling subscriber, the outgoing subscriber ID is set in the subscriber ID area, and in the network currency amount area, when the negotiation is accepted (that is, reset to a two-ring connection), A predetermined fixed amount obtained by the subscriber is entered, and the packet ID held in the negotiation content area is entered. In the negotiation packet for the called subscriber, the called subscriber ID area is filled with the called subscriber ID, and the network currency amount area is filled with a predetermined fixed amount that can be obtained by the called subscriber at the time of negotiating acceptance,
The packet ID held in the negotiation content area is entered.
The calling / receiving subscriber receives the reset request packet (step 906) and receives the negotiation packet (step 90).
7). After this, a packet is generated,
Tell by sending. The sending (receiving) subscriber, if unsatisfied with the negotiation, creates and transmits a non-resettable response packet (step 919). Next, the negotiation is not established in the packet type area of FIG.
The settlement amount notified from the network (exchange) is described in the network currency amount area, the received negotiation packet ID is entered in the negotiation content area, and the exchange 80
2 (step 920). The exchange 802 that has received the packet sends a RELEA to the calling subscriber 806.
By transmitting the SE signal, the call is regarded as a call loss (step 921). If the negotiation is satisfactory, a reset response packet is created and transmitted to the exchange 802 (step 90).
8). Next, the packet type area in FIG. 3 (c) is determined to have been negotiated, and otherwise transmitted to the exchange 802, which is the negotiation partner, in the same manner as in the case where the negotiation has not been established (step 909). When the exchange 802 receives the reset response packet and the negotiation establishment packet from the sending and receiving subscribers (steps 910 and 910)
11), the extracted call is reset (step 91).
2). In the case where one is not satisfied, step 916 is executed.
Proceed to. Specifically, the process of step 912 starts the resetting of the originating exchange 801 and the exchange 801
03 via the exchange 802 (that is, the lines 811, 81).
1), and releases the set call on the line 810.

Next, since the line 810 is free, the exchange 80
2 is a new connection request call (ie, subscribers 806, 809)
The call is set during (interval) (step 913). In particular,
The secondary exchange 801 and the terminating subscriber 809 are activated, and a response signal is received. Next, processing corresponding to the conclusion of the negotiation is performed. The exchange 802 generates the settlement packet at the time of the negotiation, and generates a clearing packet.
(Step 914). Two clearing packets are generated, one for each of the calling and called subscribers. In the subscriber ID area, the originating subscriber or the terminating subscriber, and the amount settled for the network currency are the amounts indicated to the originating subscriber and the terminating subscriber at the time of negotiation. This packet is sent to the network currency center 813 via a signal line. The configuration of the network currency center 813 is the same as that of the first embodiment (FIG. 5). The center receives the packet by the packet receiving device 501 (step 915), and reads out the subscriber ID and the settlement amount by the processor 502 (step 916). The read subscriber ID is searched for in the network currency balance table (similar to FIG. 4) in the memory 503, and the value of the network currency balance in the row having the ID is obtained as follows.
The received packet is increased by the amount settled in the network currency amount area of the received packet and stored (step 91).
7). Next, the processor 502 has the ID and stores the value of the network currency amount area in the newly stored I
A notification packet described as the value of the network currency balance for D is created, and the subscriber (the originating subscriber /
(Step 918). This notifies the subscriber that the network currency balance has been updated.

(Third Embodiment) This embodiment is an application example of a network currency when increasing or decreasing the bandwidth allocated to a connection. This embodiment will be described with reference to FIG. The configuration of the network currency center 1008 is the same as that of the first embodiment (FIG. 5). Exchanges 1005, 1006
A path 1007 is set between the terminals 1001 and 1002 and the path between the terminals 1001 and 1002.
3,1004 are set. Each connection defines a band, and the sum of the bands of all the connections accommodated in the path cannot exceed the band of the path. Note that “1001 to 1004” indicates the subscriber IDs of the terminals 1001 to 1004, respectively. Now, it is assumed that a request to increase the bandwidth of the connection between the terminals 1001 and 1002 has occurred. It is assumed that the bandwidth in the path is used depending on the bandwidth of the connection between the terminals 1003 and 1004, so that the bandwidth increase request between the terminals 1001 and 1002 cannot be satisfied. At this time, the bandwidth of the connection between the terminals 1003 and 1004 is reduced if possible,
I want to satisfy the request to increase the bandwidth of the connection between 1002. The increase / decrease of the bandwidth itself is within the range of the conventional technology.

This embodiment will be described with reference to the flowchart of FIG. The terminal 1001 that has generated the bandwidth increase request creates a packet requesting that “the bandwidth of the connection between the terminals 1001 and 1002 be increased by the increase amount A”.
The packet I transmitted to the exchange 1005 and the packet I
D is held (step 1101). Next, a negotiation packet is created by describing the subscriber ID as its own ID and the network currency settlement amount as an amount to be paid out when the bandwidth increase negotiation is completed, and writing the held packet ID in the negotiation content area.
005 (step 1102). The bandwidth increase request packet and the negotiation packet are exchanged by the exchange 1005.
Are received (steps 1103 and 1104). Exchange 1
005 is based on the bandwidth increase request packet and indicates “terminal 1
In order to determine whether it is possible to increase the bandwidth of the connection between 001 and 1002 by A ”, a search is made for a free bandwidth in the path, etc., to recognize that the increase is not possible (step 1105). If the number can be increased, step 110
9, 1120 are performed and the processing is terminated. This processing is within the range of the related art. In step 1105, the exchange 10
05 is the path 10 to increase the bandwidth by A.
07, the terminal 1003 recognizes that it is necessary to reduce the bandwidth of the connection sharing
Connection between terminals 1004 (actually terminals 1003, 10
04) is extracted (step 1106). A packet for requesting both terminals to reduce the bandwidth of the connection between the terminals 1003 and 1004 is created and transmitted, and the packet ID is held (step 1107). Next, for both terminals, both terminal IDs (1003
Or 1004), the network currency amount area is prepared and transmitted with the network currency increase amount in response to the bandwidth reduction of the connection and the held packet ID described in the negotiation content area (step 1108). Both terminals 100
3, 1004 receives the bandwidth reduction packet and the negotiation packet (steps 1109, 1110). If the bandwidth cannot be reduced, the terminals 1003 and 1004 create a bandwidth reduction impossible response packet and transmit it to the exchange 1005 (step 1131). Next, the negotiation failure packet (packet type = negotiation failure, subscriber ID = own ID (100
3 or 1004), the network currency amount = the settlement amount at the time of the negotiation being completed, the negotiation content = the bandwidth reduction negotiation packet ID), and transmit it to the exchange 1005 (step 11).
32). The exchange 1005 receives the bandwidth reduction impossible response packet and the negotiation failure packet (step 1133).
1134), thereby knowing that the bandwidth increase request between the terminals 1001 and 1002 cannot be fulfilled, creating a bandwidth increase response packet, and transmitting it to the terminal 1001 which is the bandwidth increase request source (step 1135). Furthermore, a negotiation failure packet (packet type = negotiation failure, network currency amount = clearing amount at the time of negotiation success, subscriber ID = negotiation request terminal 1
001, negotiation content = bandwidth increase negotiation packet ID), and transmits it to terminal 1001. This allows the terminal 100
1 knows that the bandwidth increase request cannot be satisfied. If at least one of the terminals 1003 and 1004 cannot perform bandwidth reduction and negotiation is not established, it is determined that bandwidth cannot be reduced and negotiation is not established.

On the other hand, if the bandwidth can be reduced, the terminal 100
3, 1004 creates a bandwidth reduction response packet and transmits it to the exchange 1005 (step 1111). Next, the negotiation completed packet (packet type = negotiation completed, subscriber I
D = own ID (1003 or 1004), network currency amount = settlement amount at the time of negotiation completion (that is, the amount presented by the negotiation packet), negotiation contents = bandwidth reduction negotiation packet ID), and transmit to exchange 1005 (Step 1112). The exchange 1005 receives the bandwidth reduction response packet and the negotiation establishment packet (step 111).
3, 1114), and notifies the terminal 1001 which is the bandwidth increase request source that a bandwidth increase response packet is created and transmitted to increase the bandwidth (step 1115). Next, the exchange 1005 sends a negotiation completion packet (packet type = negotiation completed, subscriber ID = 1001 (terminal that is a negotiation request source), network currency amount = terminal 1001 when negotiation is completed.
Creates the amount to be paid, negotiation contents = bandwidth increase negotiation packet ID) and transmits it to the terminal 1001 (step 11).
16). Further, the exchange 1005 includes terminals 1003, 10
In order to reduce the bandwidth between 04, the bandwidth change is started for the next-level switch 1006 and the bandwidth is reduced by changing the bandwidth parameter on its own memory (step 1117). Typically, rates are bandwidth dependent,
The exchange 1005 changes the billing factor by changing the billing coefficient registered per unit time next (step 111).
8). Fees and charges mentioned here are actual amounts, not network currencies. Further, the exchange 1005 is connected to the terminal 1
In order to increase the bandwidth of the connection between 001 and 1002, the bandwidth parameter on its own memory is changed, and a bandwidth parameter change is started for the next-level switch 1006 (step 1119). Further, in order to realize a charge increase accompanying the bandwidth increase, the charge coefficient is changed to change the charge contents (step 1120).

Next, the exchange 1005 performs a process for liquidating the network currency resulting from the negotiation. First, it is proposed that the terminal 1001 pays out the settlement packet (packet type = clearing, subscriber ID = 1001, network currency amount = bandwidth increase negotiation is completed) for the settlement of the subscriber (terminal 1001) having increased the bandwidth. Is created and transmitted to the network currency center 1008 (step 1121). Network Currency Center 1
008, the packet is received by the packet receiving device 501 (step 1122), and the subscriber I
D and the settlement amount are read by the processor 502 (step 1123). Next, the subscriber's network currency balance (see FIG. 4) stored in the memory 503 is settled and updated based on the settled amount (step 1124). In order to notify the subscriber 1001 of the updated balance, the processor 502 creates a notification packet (packet type = notification, subscriber ID = 1001, network currency amount = balance), and notifies the subscriber. (Step 112
5). Next, the exchange 1005 is connected to the terminals 1003 and 1004
Of the result of the bandwidth reduction negotiation between the two. First, a clearing packet (packet type = clearing, subscriber ID = 100
3,1004, network currency amount = network currency amount obtained by the subscriber (1003 or 1004) at the time of accepting the bandwidth reduction, and the network currency center 100
8 (step 1126). The network currency center 1008 sends the packet to the packet receiving device 50.
1 (step 1127), and the processor 502 reads out the settlement amount corresponding to the subscriber ID (1003, 1004) from the packet (step 1128). Next, the subscriber's network currency balance stored in the memory 503 is updated based on the settlement amount (step 112).
9). To notify the subscriber of this updated balance, a notification packet (packet type = notification, subscriber ID = 100
3,1004, network currency amount = balance)
Send to applicable subscribers. Although the present embodiment has been described with respect to the bandwidth, the present invention can be similarly applied to logical resources such as a memory, a buffer, and a number.

(Fourth Embodiment) In this embodiment, when a certain subscriber proposes a non-priority class service, when the service cannot be realized, a certain fixed network currency is paid to the network for priority. An example of receiving service as a class service. In this embodiment,
Although priority / non-priority regarding the capture of a line will be described, logical resources such as a memory, a buffer, and a number can be similarly realized. This embodiment will be described with reference to FIGS. Note that “1201”, “1202”,
“1207” indicates subscribers (terminals) 1201 and 12
02, 1207. Subscriber 1201
Sends a call setting request to the exchange 1203 to the subscriber 1202 to set up the call in the non-priority class (step 1301). The exchange that has received the signal selects a line group between the exchanges 1203 and 1204 as an outgoing route, and checks the number of lines in use in the same line group (step 1302). If the number is equal to or less than the threshold value, the exchange 1204 and the terminal 1202 are activated to set up a call (step 1316). If it exceeds the threshold,
The non-priority call sends a release signal to the terminal 1201 to block the call, and holds the ID of the signal packet (step 1303). Next, since the exchange 1203 can set up a call if it is in the priority class, the negotiation packet (packet type = negotiation, subscriber ID = 1201, network currency amount = subscriber 12
01 creates an amount to be paid to the network, negotiation contents = packet ID held), and transmits it (step 1304). Note that the network accesses the network currency center 1205 before creating the negotiation packet and refers to the network currency balance of the subscriber stored in the center, and only when the subscriber has a high balance, It is also conceivable to generate a negotiation packet.
The subscriber 1201 receives the release signal and the negotiation packet (steps 1305, 1306). As a result, although the call was lost as a non-priority class, it is recognized that there is room for negotiation. When the negotiation is not accepted, the negotiation failure packet (packet type = negotiation failure, subscriber ID = own I
D, the amount of the network currency = the amount to be paid to the network when the negotiation presented in the negotiation packet is established, and the content of the negotiation = negotiation packet ID) are created and transmitted to the exchange 1203 (step 1317). If the negotiation is successful, the negotiation success packet (packet type = negotiation success, subscriber ID =
The self-ID, the amount of the network currency = the amount to be paid to the network when the negotiation presented by the negotiation packet is established, and the negotiation content = the negotiation packet ID) are created and transmitted to the exchange 1203 (step 1307). At this point, the exchange 1
When a non-priority call setting request is received from the subscriber and the call cannot be set due to non-priority, a non-priority call setting reception waiting timer is set for the subscriber to set a call as a priority class. If a non-priority class call setup does not arrive before this timer expires, the negotiation is invalidated. Subscriber 1
201 then sends a non-priority class call setup signal to switch 120
3 (step 1308). Exchange 12
03 selects a line group between the exchanges 1203 and 1204 as an outgoing route, and checks the number of lines in use of the line group (step 1309). If this is below the threshold,
A call is set as a non-priority class (step 1318).
If this exceeds the threshold, exchange 1203
Since the non-priority call setting reception waiting timer has been started as a result of the negotiation, the call is set as the priority class (step 1310). If the line is busy, the priority signal is a call loss even in the priority class.
(Step 1319). Otherwise,
By activating the exchange 1204 and the subscriber 1202, call setting can be performed. After the call is set up, the negotiation result is settled. The exchange 1203 transmits the clearing packet (packet type =
Payment, subscriber ID = 1201, network currency amount = amount to be paid when negotiations are established), and sends it to network currency center 1205 (step 1311). The network currency center 1205 receives the packet by the packet receiving device 501 (step 1312), reduces the subscriber's balance (similar to FIG. 4) stored in the in-center memory 503 by the amount of the settlement, and stores it. (Step 131
4). Next, a notification packet (packet type = notification, subscriber ID = 1201, network currency amount = subscriber balance) is created in the processor 502, and the packet transmission device 5
04 notifies the subscriber 1201 via the exchange 1203 of the update of the balance (step 1315).

(Embodiment 5) This embodiment is an embodiment of a lottery service using a network currency. This embodiment will be described with reference to FIG. In addition, network configuration,
The configuration and the like of the network currency center are the same as in the above embodiment. In the present embodiment, it is assumed that a lottery is performed at regular intervals, and the time is set in a timer on the originating local exchange. The winning amount of the lottery is fixed and stored in advance on the exchange. In addition, it is also possible to fluctuate the lottery amount by a random number. When the timer expires (step 1401), a fixed time is set again in the timer (step 1402). Then, the following processing relating to the execution of the lottery is performed. First, a random number is assigned (step 140
3). This is to determine the winner of the blessing. For each call being set, a random number between [0, 1] is assigned, for example, 0.9
The number of hits may be 9 or more. However, if the processing of random numbers is difficult, the following method can be considered. That is, using the output port number and the call number, the call set in the exchange is ordered. For example, the output port numbers are in ascending order, the call numbers are in ascending order, or the calling subscriber numbers are in ascending order.
At the same time, the number of calls N being set is measured. Further [0,1]
The random number between them is assigned, multiplied by N, and the integer part is taken. This is i. i is an integer of 0 or more and (N-1) or less.
The (i + 1) -th call being set is hit, and the other calls are disconnected. It is also conceivable to use this method not for the call being set up but for all subordinate subscribers. Realization in this case is easier. In this way, something was decided in response to the blessing (step 140
4) Perform the following processing. First, the calling subscriber of the winning call is specified (step 1405). This is easy for the originating local exchange. Next, a clearing packet (packet type = clearing, target subscriber = calling subscriber ID, network currency amount = preliminary stored winning amount) is created and transmitted to the network currency center (step 14).
06). The network currency center receives the packet with the packet receiving device 501 (step 1407),
The processor 502 reads the lottery winner ID and the winning amount from the packet from the target subscriber and the network currency amount area from the packet (step 1408). The subscriber's network currency balance is updated by storing the winning amount in the subscriber's network currency balance (similar to FIG. 4) stored in the memory 503 (step 1).
409). Next, the processor 502 creates a notification packet (packet type = notification, target subscriber = subscriber ID, network currency amount = updated balance), and notifies the subscriber that the lottery has been won (step). 14
10).

(Sixth Embodiment) This embodiment provides a large discount service using network currency by paying out network currency from a network to a user who pays a large amount of money. This embodiment will be described with reference to FIG. The network configuration, the configuration of the network currency center, and the like are the same as those in the above-described embodiment. In this embodiment, the charge center accumulates the call volume in the billing month for each subscriber from the collected billing records for each call to obtain the billing amount (step 1501). It is checked whether the billed amount exceeds a predetermined value stored in advance (step 1502). If it exceeds, since it is a subscriber to be discounted based on the network currency (that is, a subscriber to be increased in network currency balance), a clearing packet (packet type = clearing, target subscriber = subscriber ID,
A network currency amount = amount to be increased) is created and transmitted (step 1503). Thus, the clearing packet created at the toll center is transmitted to the network currency center. The network currency center receives the packet at the packet receiving device 501 (step 1504), and the processor 502 reads out the subscriber ID and the settlement amount to be settled from the packet (step 15).
05). The network currency balance corresponding to the subscriber stored in the in-center memory 503 is increased by the readout amount and stored (step 1506). Next, the processor 502 sends a notification packet (packet type = notification, target subscriber = subscriber I
D, network currency amount = updated balance)
The packet is transmitted to the subscriber by the packet transmitting device 504 (step 1507).

It should be noted that, between network subscribers, ISD
N, ATM, telephone, etc. can be supported. However,
For example, the processing of the notification packet and the like are slightly different depending on which communication method is used. In the transfer of a notification packet by a VC and a management procedure different from the main information in the D channel of the ISDN or the ATM, the notification packet can be transmitted and received regardless of the presence or absence of the main information. For example, in a telephone service on a telephone or an ATM, it is conceivable that the notification packet is changed to a notification by voice at the local exchange and notified. In addition, a method of notifying the balance by notifying the balance on the bill is also conceivable.
As for the negotiation packet, the embodiment has been described on the assumption that the packet can be transmitted and received regardless of the presence or absence of the main information. Further, as a more realistic configuration, a call fee may be used instead of the network currency in the above-described embodiment, and the charge center may have a network currency center function.

[0020]

According to the present invention, when a network currency is defined, a "discount service" and a "network resource exchange negotiation service" can be provided freely and flexibly without changing the fee system. In the call service, differences in quality and performance occur depending on subscriber behavior. It is possible to provide a kind of reward to cooperative subscribers for the benefit of the whole network, to motivate the subscribers to cooperate with the network, and to improve the quality and performance characteristics.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating a network configuration according to a first embodiment of the present invention.

FIG. 2 is a diagram showing a table for registering congestion restriction targets and the number of recalls according to the first embodiment of the present invention.

FIG. 3 is a diagram showing a configuration of various packets in the first embodiment of the present invention.

FIG. 4 is a diagram showing a network currency balance table according to the first embodiment of the present invention.

FIG. 5 is a configuration diagram of a network currency center according to the first embodiment of the present invention.

FIG. 6 is a flowchart of a congestion restriction process according to the first embodiment of the present invention.

FIG. 7 is a flowchart of congestion regulation end processing according to the first embodiment of the present invention.

FIG. 8 is a diagram illustrating a network configuration according to a second embodiment of the present invention.

FIG. 9 is a flowchart of negotiation between a network (switch) and a subscriber in the second embodiment of the present invention.

FIG. 10 is a diagram illustrating a network configuration according to a third embodiment of the present invention.

FIG. 11 is a flowchart of negotiation between subscribers according to a third embodiment of the present invention.

FIG. 12 is a diagram illustrating a network configuration according to a fourth embodiment of the present invention.

FIG. 13 is a flowchart of negotiation between a network (switch) and a subscriber in a fourth embodiment of the present invention.

FIG. 14 is a flowchart of a subscriber lottery service according to a fifth embodiment of the present invention.

FIG. 15 is a flowchart of a discount service for a large user according to the sixth embodiment of the present invention.

[Description of Signs] 101 to 103: subscriber terminals, 104 and 105: exchanges, 106: network control center, 107: network currency center.

Claims (19)

[Claims] 1. A network system comprising a plurality of subscriber terminals and an exchange accommodating the subscriber terminals, comprising: a packet type, a target subscriber ID, a currency exchangeable with network resources and network services. A packet transmitting / receiving apparatus for transmitting / receiving a packet having an area for describing an amount of a network currency defined as: a memory for storing a balance of the network currency for each subscriber; and reading / writing each area of the packet and according to the content thereof And a processor for updating a network currency balance by using a network currency center connected to the exchange. 2. The method according to claim 1, wherein the amount of the network currency exchanged with the network resource and the network service and the ID of the subscriber who exchanges the network resource and the network service are stored. The described packet is received by the packet transmitting / receiving device, the processor reads the subscriber ID and the network currency amount from the packet, and the network currency balance of the subscriber stored in the memory is read out from the network currency amount. A network currency management method characterized by storing and updating the network currency balance after the settlement by liquidation. 3. The management method for a network currency system according to claim 1, wherein when a request for network resources and network services is made from the network side to the subscriber, the request is stored in a predetermined area of the packet. Describe the network currency settlement amount paid to the subscriber at the time of acceptance and send it to the target subscriber, and if a packet indicating request acceptance is returned from the subscriber, respond to the subscriber in the memory And updating the network currency balance to be updated by increasing the network currency settlement amount, and storing the network currency balance after the settlement. 4. The management method for a network currency system according to claim 1, wherein when the subscriber makes a request for network resources and network services to the network side, the subscriber enters the predetermined area of the packet. When the network side accepts the request, it returns a packet indicating the acceptance of the request from the exchange,
A network currency management method, wherein the network currency center updates the network currency balance corresponding to the subscriber in its own memory by reducing the network currency settlement amount, and stores the network currency balance after the settlement. 5. The management method for a network currency system according to claim 1, wherein the exchange includes a congestion restriction target, an ID of a calling party who has called the restriction target, and a re-establishment for each restriction target. A storage means for storing the number of calls is provided. When congestion is detected, the ID of the calling party to the restriction target and the number of recalls are stored in the storage means. With respect to the above, the exchange sends the network currency clearing amount to be reduced from the network currency balance of the calling subscriber in a predetermined area of the packet in a predetermined area of the packet, and transmits the packet. The originating subscriber was sent from the exchange to the network currency center.
In a predetermined area of the packet, the network currency settlement amount to be added to the network currency balance of the calling subscriber is described and transmitted, and the network currency center stores the network currency balance corresponding to the calling subscriber in its own memory, A network currency management method comprising: updating the network currency by increasing or decreasing the network currency settlement amount and storing the network currency balance after the settlement. 6. The management method for a network currency system according to claim 1, wherein the packet has an area for describing negotiation contents between subscribers or between subscribers and a network. When detecting that all lines are busy, extracting one of the calls using the same line group, and requesting the subscriber of the call to reestablish the detour of the call from the network side, a predetermined area of the packet The target subscriber ID indicating the subscriber
When the request is accepted, the network currency settlement amount paid to the subscriber and the content of the negotiation are described and transmitted to the subscriber, and when the subscriber returns a packet indicating acceptance of the request, At the network currency center, the network currency balance corresponding to the subscriber in the memory is
A network currency management method, characterized in that the network currency is updated by increasing the network currency settlement amount and storing the network currency balance after the settlement. 7. The management method for a network currency system according to claim 1, wherein the packet has an area for describing contents of negotiation between subscribers or between subscribers and a network. Along with requesting the exchange to increase or acquire network resources, the packet shall be sent to the specified area of the packet with the network currency settlement amount paid by the requesting subscriber when the request is fulfilled. If it is determined, the subscriber competing for the network resource is extracted, and in a predetermined area of the packet, the network currency settlement amount paid to the subscriber at the time of transfer of the network resource is described and transmitted to the subscriber. If the subscriber negotiates with the subscriber and a packet indicating the acceptance of the request is returned from the subscriber to the exchange, the exchange receives the packet from the subscriber. The network resource is transferred to the predetermined area of the packet and transferred to the network communication center from the network currency balance of the subscriber and the requesting subscriber when the network resource is transferred. The currency settlement amount is described and transmitted, and at the network communication center, the network currency balance corresponding to both subscribers in the memory is increased or decreased according to the network currency settlement amount, and the network currency balance after the settlement is updated. A network currency management method characterized by storing. 8. The network currency management method according to claim 7, wherein said network resource is a band allocated to a connection between subscriber terminals. 9. The management method for a network currency system according to claim 1, wherein the packet has an area for describing contents of negotiations between subscribers or between subscribers and a network. On the other hand, in a predetermined area of the packet,
Treating the non-priority class service as a priority class, and transmitting the network currency settlement amount paid by the subscriber to the network side when the priority class treatment is executed, and transmitting the service to the exchange. When returning a packet indicating that the negotiation has been completed and requesting a non-priority class service, the exchange executes the non-priority class service as a priority class service for the subscriber, and instructs the network currency center to provide the network currency center with the predetermined packet. In the area, the subscriber ID of the subscriber and the network currency settlement amount are described and transmitted. The network currency center stores the network currency balance corresponding to the subscriber in its own memory in the network currency settlement amount. Network currency management, characterized by storing and updating the network currency balance after liquidation Method. 10. The method according to claim 9, wherein the service is call setting. 11. The management method for a network currency system according to claim 1, wherein the subscribers are extracted by a stochastic method from a call being set at regular time intervals, or a subscriber accommodated in an exchange. In the case where a network currency determined in advance or determined by a stochastic factor is given to a subscriber corresponding to a terminal extracted in a stochastic manner from the terminals, the exchange sends the packet to the network currency center. In a predetermined area, the subscriber ID of the extracted subscriber and the network currency settlement amount given from the network side to the subscriber are described and transmitted. The network currency center stores the subscriber ID stored in its own memory. The feature is that the network currency balance corresponding to the subscriber is updated by increasing the network currency settlement amount described above, and the network currency balance after the settlement is stored. Network currency management method for the. 12. The management method for a network currency system according to claim 1, further comprising a toll center for performing a billing process based on a traffic volume between the subscriber terminals, wherein the toll center is provided for each subscriber by the billing process. The billing amount is calculated, and it is determined whether the billing amount exceeds a predetermined value. If the billing amount exceeds the predetermined value, the network currency center informs the subscriber of the packet in a predetermined area of the packet. The network currency center describes the subscriber ID and the network currency clearing amount given from the network side and transmits the network currency balance corresponding to the subscriber stored in its own memory. A network currency management method, characterized in that the amount is updated by increasing the amount, and the network currency balance after the settlement is stored. 13. A plurality of subscriber terminals, an exchange accommodating the subscriber terminals, and a charge center for performing a billing process based on a traffic volume between the subscriber terminals. A packet transmitting / receiving apparatus for transmitting / receiving a packet having an area in which a target subscriber ID and a charge amount to be increased / decreased from the charge amount for the subscriber, a memory for storing the charge amount for each subscriber, and reading / writing each area of the packet And a processor for updating a billing amount in accordance with the contents thereof, wherein the exchange includes a congestion-regulated object, an ID of a calling subscriber who has called the congested object, A storage means for storing the number of recalls for each of the restriction targets is provided, and when congestion is detected, the ID of the calling subscriber to the restriction target and the number of recalls are stored in the storage means. For the calling subscriber whose number of recalls is equal to or greater than a predetermined number, the packet is transmitted in a predetermined area of the packet by describing a charge amount to be added to the amount charged to the calling subscriber, and For the calling subscriber whose number has been less than the above number, the charge amount to be reduced from the billed amount for the calling subscriber is transmitted in a predetermined area of the packet and transmitted. A charge management method comprising: updating a charge amount to a user by increasing or decreasing the charge amount, and storing the charge amount after settlement. 14. A system comprising: a plurality of subscriber terminals; an exchange accommodating the subscriber terminals; and a toll center for performing a billing process based on a traffic volume between the subscriber terminals. A packet transmission / reception device for transmitting / receiving a packet having an area in which a target subscriber ID, a charge amount to be increased / decreased from the amount charged to the subscriber, and negotiation contents between the subscribers or between the subscriber and the network, and a charge amount for each subscriber And a processor that reads and writes each area of the packet and updates the billing amount according to the contents of the packet. Then, when one of the calls using the same line group is extracted and the network side requests the subscriber of the call to re-establish the detour of the call, a predetermined area of the packet is used. , The target subscriber ID indicating the subscriber
When the request is accepted, the charge amount reduced from the billing amount for the calling subscriber and the negotiation content are transmitted to the subscriber, and if a packet indicating the acceptance of the request is returned from the subscriber, A charge management method, wherein a charge center updates the charge amount for the subscriber in its own memory by reducing the charge amount and stores the charge amount after settlement. 15. A system comprising: a plurality of subscriber terminals; an exchange accommodating the subscriber terminals; and a toll center for performing a billing process based on a traffic volume between the subscriber terminals. A packet transmission / reception device for transmitting / receiving a packet having an area in which a target subscriber ID, a charge amount to be increased / decreased from the amount charged to the subscriber, and negotiation contents between the subscribers or between the subscriber and the network, and a charge amount for each subscriber And a processor for reading and writing each area of the packet and updating the billing amount according to the content of the packet. Request to increase or obtain the number of packets, and transmit the information in the specified area of the packet, stating the amount paid by the requesting subscriber when the request is fulfilled, and exchange If it is determined that the request cannot be achieved, a subscriber competing for the network resource is extracted, and the fee paid to the subscriber when the network resource is transferred is described in a predetermined area of the packet, and the subscriber is registered. To the subscriber, negotiates with the subscriber, and when the subscriber returns a packet indicating acceptance of the request to the exchange, the exchange receives the network resources from the subscriber, and To the charge center, and in a predetermined area of the packet, transmit and write the charge amount to be increased or decreased from the billing amount of the subscriber and the requesting subscriber at the time of transfer of the network resource. A charge management method comprising: increasing or decreasing the billing amount corresponding to both subscribers in its own memory in accordance with the fee amount, updating the billing amount, and storing the billed amount after settlement. 16. The charging management method according to claim 15, wherein said network resource is a band allocated to a connection between subscriber terminals. 17. A system comprising: a plurality of subscriber terminals; an exchange accommodating the subscriber terminals; and a toll center for performing a billing process based on a traffic volume between the subscriber terminals. A packet transmission / reception device for transmitting / receiving a packet having an area in which a target subscriber ID, a charge amount to be increased / decreased from the amount charged to the subscriber, and negotiation contents between the subscribers or between the subscriber and the network, and a charge amount for each subscriber And a processor that reads and writes each area of the packet and updates a billing amount in accordance with the content of the packet. The non-priority class service is treated as a priority class in a predetermined area, and the subscriber pays the network side when the priority class treatment is performed. When the subscriber returns a packet indicating that negotiation has been completed to the exchange and requests a non-priority class service, the exchange sends the non-priority class service to the subscriber. Is executed as a priority class service, and to the charge center,
In a predetermined area of the packet, a subscriber ID of the subscriber,
The charge center is described and transmitted, and the charge center updates the charge amount corresponding to the subscriber in its own memory by increasing the charge amount and stores the charge amount after settlement. Charge management method. 18. The charging management method according to claim 17, wherein the service is a call setup. 19. A system comprising: a plurality of subscriber terminals; an exchange accommodating the subscriber terminals; and a toll center for performing a billing process based on a traffic volume between the subscriber terminals. A packet transmitting / receiving apparatus for transmitting / receiving a packet having an area in which a target subscriber ID and a charge amount to be increased / decreased from the charge amount for the subscriber, a memory for storing the charge amount for each subscriber, and reading / writing each area of the packet A billing management method for a network system comprising a processor for updating a billing amount according to the contents thereof, wherein the billing method is extracted from a call being set at regular intervals by a stochastic method, or an exchange. In the case where a predetermined or determined stochastic factor is applied to a subscriber corresponding to a subscriber terminal extracted by a stochastic method from subscriber terminals accommodated in a terminal , Relative rates center from the exchange, a predetermined region of the packet, subscriber I of the extracted subscriber
D and the fee amount given from the network side to the subscriber, and transmit the same. The fee center reduces the billing amount corresponding to the subscriber stored in its own memory by the fee amount. A billing management method comprising updating and storing a billed amount after settlement.