WO2009123265A1 - データ中継装置およびデータ中継方法 - Google Patents
データ中継装置およびデータ中継方法 Download PDFInfo
- Publication number
- WO2009123265A1 WO2009123265A1 PCT/JP2009/056820 JP2009056820W WO2009123265A1 WO 2009123265 A1 WO2009123265 A1 WO 2009123265A1 JP 2009056820 W JP2009056820 W JP 2009056820W WO 2009123265 A1 WO2009123265 A1 WO 2009123265A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- transfer
- unit
- charging
- mobile device
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1432—Metric aspects
- H04L12/1439—Metric aspects time-based
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/82—Criteria or parameters used for performing billing operations
- H04M15/8207—Time based data metric aspects, e.g. VoIP or circuit switched packet data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/20—Technology dependant metering
- H04M2215/204—UMTS; GPRS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/78—Metric aspects
- H04M2215/7813—Time based data, e.g. VoIP or circuit switched packet data
Definitions
- the present invention relates to a data relay apparatus and a data relay method for performing charging processing for data.
- Patent Document 1 holds a charging information table that stores the number of packets and the number of bytes for each destination address in a router that transmits and receives packets to and from a connectionless computer network, and uses this charging information table. The billing process is described.
- the charging processing method based on the amount of packets flowing on the network just like the technique described in Patent Document 1 has the following problems. That is, in a device that can move out of communication range, such as a mobile device, even if data is transmitted from the content server to the mobile device, if the mobile device goes out of communication range, Even though the data does not reach the mobile device, it is charged.
- an object of the present invention is to provide a data relay apparatus and a data relay method capable of performing appropriate accounting processing even when a connectionless protocol such as UDP is used.
- the data relay apparatus of the present invention includes a transfer unit that transfers data transmitted and received between a mobile device and a server using the mobile device or the server as a transfer destination, and the transfer Charging means for performing charging processing according to the amount of data transferred by the means, detection means for detecting that response data is transmitted from the transfer destination of the transfer means, and detection from the transfer destination by the detection means Transfer stop means for stopping transfer processing by the transfer means when response data is not detected, and charge stop for stopping charge processing of the charge means when response data from the transfer destination is not detected by the detection means Means.
- data transmitted / received between a mobile device and a server is transferred using the mobile device or server as a transfer destination, and charging processing is performed according to the data amount of the transferred data. It is detected that the response data is transmitted from the mobile phone, and when the response data from the transfer destination is not detected, the transfer process is controlled to stop and the accounting process can be stopped.
- a connectionless protocol such as UDP
- UDP connectionless protocol
- the transfer stopping unit stops the transfer process by the transfer unit when response data is not detected within a predetermined time after the transfer process by the transfer unit is started
- the charging stop unit stops the charging process by the charging unit when response data is not detected within a predetermined time after the transfer process by the transfer unit is started.
- the response data when the response data is not detected within a predetermined time after the transfer process is started, it is possible to confirm the connection state more accurately by controlling the transfer process and the billing process to be stopped. .
- the data relay device of the present invention measures, for each port, the uplink no-communication time that is the non-detection time of the response data from the mobile device and the downlink no-communication time that is the no-detection time of the response data from the server. And when the detection means cannot detect response data from the mobile device at each port for a predetermined time, the measuring means is configured to perform an uplink non-communication time corresponding to all ports secured by the mobile device.
- the charging stop unit stops the charging process by the charging unit for data received after the predetermined time through all ports, and the transfer stop unit closes all the ports. To stop the transfer process by the transfer means, and the response data from the server connected through one of the reserved ports.
- the measuring means stops the measurement processing of the no-communication time corresponding to the one port, and the charging stop means stops after the predetermined time via the one port.
- the charging process by the charging unit for the received data is stopped, and the transfer stop unit stops the transfer process by the transfer unit by performing a process of closing the one port.
- the uplink no-communication time and the downlink no-communication time are managed in units of ports, and when the uplink data cannot be detected from the mobile device, the timing measurement processing of the uplink no-communication time is stopped for all ports. At the same time, the accounting process is stopped. In addition, when downlink data cannot be detected from the server, the timing processing for the downlink non-communication time corresponding to the port to which the server is connected is stopped and the accounting process is stopped. Therefore, processing according to the reserved port can be performed, for example, the uplink no-communication time indicates the state between the mobile device and the proxy device, and only one port is out of communication range, Since the other ports are not in communication range, stop processing is performed for all ports.
- the downlink no-communication time indicates the state between the server connected through the one target port and the proxy device, and the server connected through the one port fails.
- a server connected through another port may be in a communicable state even if the communication is not performed. Therefore, in this case, management is performed so that communication connection processing and billing processing for servers connected via other ports can be continuously performed.
- the present invention can be described as an invention of a data relay apparatus as described above, and can also be described as an invention of a data relay method as follows. These are substantially the same inventions only in different categories, and exhibit the same actions and effects.
- the data relay method of the present invention includes a transfer step of transferring data transmitted and received between a mobile device and a server using the mobile device and the server as a transfer destination, and a transfer of the data transferred by the transfer step.
- a charging step for performing charging processing according to the amount of data, a detection step for detecting that response data is transmitted from the transfer destination of the transfer step, and a case where response data from the transfer destination is not detected by the detection step A transfer stop step for stopping the transfer process in the transfer step; and a charge stop step for stopping the charge process in the charge step when response data from the transfer destination is not detected in the detection step.
- the transmission side and the reception side can communicate with each other, and when the connection is established It is possible to perform the accounting process only for the period, and it is possible to realize an appropriate accounting process.
- FIG. 1 is a system configuration diagram of a communication system including a proxy device 100 which is a data relay device of the present embodiment.
- FIG. 3 is a block diagram illustrating functions of the proxy device 100.
- FIG. 6 is an explanatory diagram showing timer management in a timer unit 105.
- FIG. 6 is a schematic diagram showing a relationship between a charging processing point and a detection point of response data from a mobile device 300.
- FIG. 6 is a schematic diagram showing a relationship between a charging processing point and a detection point of response data from the server 400.
- FIG. 6 is a schematic diagram showing a relationship between a charging processing point and a detection point of response data from the server 400.
- DESCRIPTION OF SYMBOLS 100 ... Proxy apparatus, 101 ... Gateway part, 102 ... Charge processing part, 103 ... Detection part, 104 ... Control part, 105 ... Timer part, 106 ... Gateway part, 107 ... Detection part, 110 ... Gateway apparatus, 120 ... Gateway apparatus , 200 ... exchange, 300 ... mobile equipment, 400 ... server.
- FIG. 1 is a system configuration diagram of a communication system including a proxy device 100 which is a data relay device of this embodiment. As shown in FIG. 1, this communication system includes a proxy device 100, an exchange 200, a mobile device 300, and a server 400.
- the proxy device 100 is a data relay device for connecting the server 400 and the exchange 200, and can transmit the content data transmitted from the server 400 to the exchange 200 in order to transfer it to the mobile device 300. Further, the data transmitted from the mobile device 300 can be received via the exchange 200 and transmitted to the server 400.
- the exchange 200 is arranged between the mobile device 300 and the proxy device 100, and controls the establishment and release of a call and performs the routing process of data from the mobile device 300.
- the mobile device 300 is, for example, a mobile phone, and is connected for communication with the exchange 200 and the server 400 using a connectionless protocol (for example, UDP) via a wireless communication network including a base station, RNC, and the like. Can do.
- a connectionless protocol for example, UDP
- the mobile device 300 is preferably configured to transmit response data to the server 400 every predetermined time or every predetermined amount of received packets. This is to enable the proxy device 100 to recognize that the mobile device 300 can communicate.
- the mobile device 200 may be other than a mobile phone, and includes, for example, a PDA having a wireless communication function, a PC, a home electronic device, and a game machine.
- the server 400 is, for example, a server on the Internet (hereinafter referred to as a content provider) provided by a content provider, and sends content data to the mobile device 300 in accordance with a request from the mobile device 300 (for example, UDP). ).
- the server 400 is not limited to a content provider or the like, but is a gateway server for connecting to another communication network, a corporate LAN, a PC that can be connected to the Internet, a game machine, or a home electronic device (TV, DVD recorder) In this case, the mobile device 300 can communicate with a mobile device connected to another communication network.
- the proxy device 100 charges the network usage fee between the proxy device 100 and the mobile device 300.
- a billing process corresponding to the amount of data transmitted is performed, and the data is transferred to the exchange 200.
- the exchange 200 further transfers data to the mobile device 300.
- the proxy device 100 detects the presence / absence of response data from the mobile device 300 for the data transmitted from the server 400. If the response data cannot be detected within a predetermined time, the proxy device 100 charges the mobile device 300. The process is stopped and the port is closed so that data transmission from the server 400 is not accepted.
- the response data is data generated and transmitted by an application in the mobile device 300.
- the response data corresponds to a control signal for the server 400 every predetermined time or every predetermined byte.
- the application may be a browser, an application that executes VoIP, an online competitive game, a streaming playback player such as a moving image / music, or the like.
- the response data may be data that is generated and transmitted by a user operation, and may be data that is processed so as to be transmitted to the server 400 at least periodically.
- the proxy device 100 can determine that the data transmitted from the server 400 is transmitted to the mobile device 300 by detecting the presence or absence of the response data.
- the proxy device 100 receives the data via the exchange 200, performs charging processing, and transfers the data to the server 400. If the response data for the data transmitted from the mobile device 300 cannot be detected from the server 400 within a predetermined time, the proxy device 100 stops the charging process for the mobile device 300.
- FIG. 2 is a block diagram illustrating functions of the proxy device 100.
- the proxy device 100 is composed of two gateway devices 110 and 120.
- the gateway device 110 is mainly a device that performs billing processing and protocol conversion processing, and the gateway device 120 is the Internet or the like. This is a device for connecting to an external network. In addition, you may comprise by a single gateway apparatus, without providing such gateway apparatuses 110 and 120.
- FIG. 1 A configuration of the proxy device 100 that performs such processing will be described.
- FIG. 2 is a block diagram illustrating functions of the proxy device 100.
- the proxy device 100 is composed of two gateway devices 110 and 120.
- the gateway device 110 is mainly a device that performs billing processing and protocol conversion processing
- the gateway device 120 is the Internet or the like. This is a device for connecting to an external network.
- the gateway device 110 includes a gateway unit 101 (transfer unit), a billing processing unit 102 (billing unit), a detection unit 103, a control unit 104 (billing stop unit 104a: billing stop unit, transfer stop unit 104b: transfer stop unit), and A timer unit 105 (measuring means) is included.
- the gateway device 110 is realized by hardware as shown in FIG. FIG. 3 is a hardware configuration diagram of the gateway device 110. As shown in FIG. 3, the gateway device 110 shown in FIG. 2 physically includes a CPU 11, a RAM 12 and a ROM 13 as main storage devices, an input device 14 such as a keyboard and a mouse as input devices, and an output from a display or the like.
- the computer 15 includes a device 15, a communication module 16 that is a data transmission / reception device such as a network card, an auxiliary storage device 17 such as a hard disk, and the like.
- a communication module 16 that is a data transmission / reception device such as a network card
- an auxiliary storage device 17 such as a hard disk, and the like.
- Each function described in FIG. 2 has the input device 14, the output device 15, and the communication module 16 under the control of the CPU 11 by reading predetermined computer software on the hardware such as the CPU 11 and the RAM 12 shown in FIG. 3. This is realized by reading and writing data in the RAM 12 and the auxiliary storage device 17.
- each functional block will be described based on the functional blocks shown in FIG.
- the gateway unit 101 is a device for connecting the mobile device 300 and the server 400.
- the gateway unit 101 secures a port in association with the mobile device 300 and manages the association. And receiving data transmitted from the gateway device 120 (server 400) via the port, transferring the data to the mobile device 300 (wireless communication network), and receiving data transmitted from the mobile device 300, This is a part to be transmitted to the gateway device 120 (server 400).
- the billing processing unit 102 is a part that counts the amount of data transmitted from the gateway unit 101 to the mobile device 300 or the server 400 and performs billing processing according to the count number.
- the detection unit 103 transmits response data from the server 400 to the data transmitted from the mobile device 300 to the server 400 or transmits the response data from the server 400 to the mobile device 300. It is a part for detecting that response data is transmitted from the mobile device 300 to the received data, and is a part for detecting to which port either uplink data or downlink data has been received. .
- the detection unit 103 determines which port the data is through, or whether the data is uplink data or downlink data. 104 is notified.
- the control unit 104 includes a charging stop unit 104a and a transfer stop unit 104b.
- the charging stop unit 104a controls to stop the charging process of the charging processing unit 102
- the transfer stop unit 104b includes the gateway unit 101 and the gateway.
- the transfer processing of the unit 106 is controlled to stop.
- the control unit 104 receives a notification that the response data has been detected from the detection unit 103, that is, upon receiving a notification that a communication port and uplink data or downlink data have been detected, the timer unit 105
- the controlled no-communication time is reset and re-timed.
- control unit 104 (billing stop unit 104a) is configured to detect response data (that is, uplink data or downlink data) from the mobile device 300 or the server 400 within a predetermined time in one port by the detection unit 103. Controls the charging processing unit 102 to stop the charging processing for the mobile device 300 that secures the one port. Further, the control unit 104 (transfer stop unit 104b) instructs the gateway device 110 and the gateway device 120 to perform processing for closing the reception port so that data transmitted from the mobile device 300 or the server 400 is not accepted. Is output.
- the control unit 104 stops the charging process and the gateway device 120 (gateway unit 106) Control is performed so that all ports secured by the mobile device 300 are closed.
- the control unit 104 stops the charging process and the gateway device 110 (gateway unit 101) concerned. Control to close the port.
- the gateway device 110 or the gateway device 120 by performing the location to be closed by the gateway device 110 or the gateway device 120 according to the upstream and downstream of the data, the data communication distance can be shortened, and the traffic can be reduced.
- the port on the mobile device 300 side of the gateway device 110 is closed.
- the communication path configured using the ports secured in the gateway unit 110 and the gateway unit 120 does not function as a communication path if any of the ports of the gateway unit 110 and the gateway unit 120 is closed. Any one of the ports may be closed. In this case, the billing process is not performed after the closing.
- the control unit 104 secures a port for communication so that the gateway unit 101 and the gateway unit It is comprised so that 106 may be controlled.
- control unit 104 can determine the transfer direction of data transmitted and received by the gateway unit 101 and the gateway unit 106 based on the notification from the detection unit 103, and after securing the port, the source address of the received data Based on the destination address, it is possible to determine whether the data is uplink data or downlink data, and in response to the notification, the timer value of the uplink no-communication time counted by the timer unit 105, the downlink no-communication time Reset any of the timer values and retime. For example, when receiving a notification that uplink data has been received, the control unit 104 resets the timer value for the uplink no-communication time and controls the timer unit 105 so as to start counting again from the initial value.
- the timer unit 105 manages the uplink no-communication time for each mobile device, and manages the downlink no-communication time for each port. For example, when data is transmitted from the gateway unit 101 to the mobile device 300, This is a part for starting the time measurement process of the timer and resetting the time measurement process and receiving the time measurement process again when the gateway unit 101 receives response data from the mobile device 300. If the control unit 104 determines that the response data cannot be received from the mobile device 300 within a predetermined time based on the timing process by the timer unit 105, the reception port of the gateway device 120 (gateway unit 106) as described above. Process to close.
- the timer unit 105 will be described more specifically.
- the timer unit 105 performs timer management for each mobile device 300 with respect to the uplink non-communication time indicating the response data non-detection time for the data transmitted from the server 400 to the mobile device 300.
- timer management is performed for each port secured when the mobile device 300 performs communication.
- FIG. 4 is an explanatory diagram showing timer management in the timer unit 105. As shown in FIG.
- the timer unit 105 includes a user indicating the mobile device 300, a use port used by the user, an uplink non-communication time indicating a non-detection time of response data from the mobile device 300, and a server 400.
- the downlink no-communication time indicating the non-detection time of the response data from is stored in association with each other.
- the timer unit 105 manages the uplink no-communication time for each user, that is, for each mobile device 300, without managing for each port, and manages the downlink no-communication time for each port. This is because the management target of the uplink no-communication time is a mobile device, and communication is not interrupted for each port. That is, when the mobile device moves out of service area or the like, all ports are disconnected.
- the downlink non-communication time management target is a communication partner such as each content server connected to each port, and communication may be interrupted for each port. Therefore, the timer unit 105 distinguishes for each port. Managing no communication time.
- the control unit 104 performs processing for closing the port that has timed out.
- the control unit 104 since the downlink no-communication time of port 1 of user 1 has exceeded 60 seconds, the control unit 104 controls the gateway unit 101 to close this port D.
- the gateway unit 106 is controlled so as to close all the ports used by the user.
- the gateway device 120 includes a gateway unit 106 and a detection unit 107.
- the gateway device 120 connects the gateway device 110 and the server 400 arranged on the Internet, transfers the data transmitted from the server 400 to the gateway device 110, and transmits the data transmitted from the gateway device 110. This is the part that is sent to the server 400.
- the detection unit 107 is a part that detects the presence / absence of data that has undergone transfer processing in the gateway unit 106.
- data is transmitted from the server 400 to the mobile device 300, that is, when data is transmitted in the downlink direction.
- the presence / absence of response data from the mobile device 300 is detected.
- the gateway unit 106 detects that response data is input from the gateway device 110 (mobile device 300), it outputs that fact to the control unit 104.
- the processing configuration is the same as that of the detection unit 103.
- control unit 104 does not receive a notification that the response data has been detected within a predetermined time according to the timer unit 105 in the detection unit 107, the data has not reached the mobile device 300 normally. For example, it is determined that the service has shifted to the outside of the communication range, and control is performed to stop the billing processing for the billing processing unit 102 and the reception port is closed so that the gateway unit 106 does not accept data from the server 400. Do.
- FIG. 5 is a flowchart showing a schematic operation in the proxy device 100 when data is flowing in the downstream direction.
- the application uses a gateway unit with a protocol such as UDP. Therefore, ports for connecting the mobile device 300 and the server 400 are secured in the gateway units 101 and 106, respectively (S102).
- the port securing process is performed, data is transmitted from the server 400 to the mobile device 300, and the data is received by the gateway unit 106 and the gateway unit 101 (S103). Then, when data is received in the proxy device 100, the timer unit 105 starts the time counting process of the uplink no-communication time in the mobile device 300 (S104).
- the received data is sequentially relayed to the server 400 by the gateway units 101 and 106 (S105).
- the gateway units 101 and 106 On the other hand, when relay processing is performed in the gateway unit 101, billing processing according to the amount of data is performed by the billing processing unit 102 (S106).
- the control unit 104 determines whether the gateway unit 106 receives response data from the mobile device 300 according to the detection result of the detection unit 107 (S107).
- the mobile device 300 that is, the application in the mobile device
- the mobile device 300 is configured to transmit response data for notifying that the content data is being downloaded to the server 400 when the content data is being downloaded. If the response data is detected by the detection unit 107 within a predetermined time, the timer value in the timer unit 105 is reset (S108), the time counting process is started from the initial value, and the data in the downstream direction is again displayed. Reception processing, transfer processing, and billing processing are performed.
- the port of the gateway unit 106 is closed, the time counting process of the uplink no-communication time in the timer unit 105 is stopped, and the accounting process is stopped (S110). ).
- the detection point set by the detection unit 107 set in the device that closes the port that is, the presence or absence of response data is detected by the gateway unit 106, and the response is made at the detection point. If the data cannot be detected, the charging process is stopped and the port for receiving data from the server 400 in the gateway unit 106 is closed.
- an appropriate accounting process for data transmitted by a connectionless protocol That is, it is possible to prevent the mobile device 300 from being out of service area and performing only the billing process when data has not arrived.
- FIG. 6 is a schematic diagram thereof.
- data is transmitted from the server 400 to the mobile device 300 as indicated by an arrow Y1. Since the data transmitted from the server 400 is transmitted using a connectionless protocol such as UDP, the gateway device 110, which is a charging processing point, performs charging processing regardless of whether the mobile device 300 is in or out of the communication range. I do.
- a connectionless protocol such as UDP
- the mobile device 300 When the mobile device 300 is within the communication range, the data can be normally received, and thus the mobile device 300 can generate and transmit response data for the data. On the other hand, when the mobile device 300 is outside the communication range, the data cannot be received normally. Therefore, the mobile device 300 cannot recognize the data, does not perform the response data generation process, and is out of the service area, and cannot transmit the response data for the data.
- the proxy device 100 cannot receive response data.
- the gateway device 120 detection unit 107
- the gateway device 120 detects response data from the mobile device 300 within a predetermined time at the data detection point P1
- the mobile device 300 is out of the communication area or the like and receives the response data. It can be determined that the transmission is impossible.
- the control unit 104 cannot receive notification from the detection unit 107 that detection has been made within a predetermined time, and therefore instructs the charging processing unit 102 to stop the charging processing and also gateways.
- the unit 106 is instructed to close the reception port for receiving data from the server 400. In FIG. 6, the port indicated by the close point P2 is closed.
- data does not pass through the network on the downstream side (mobile device 300 side) from the proxy device 100, so that no charging process is performed and no use is required because the data is not used.
- the gateway device 120 is configured to include the data detection point P1 and the close point P2 as in the present embodiment, the occurrence of time lag is extremely small because of processing in the same device, and unnecessary charging is effective. Can be stopped automatically.
- FIG. 7 is a flowchart showing a schematic operation of the proxy device 100 at that time.
- data is transmitted to the server 400, but the present invention is not limited to this, and may be transmitted to a terminal such as a mobile device via the server 400.
- the application when the mobile device 300 makes a request for uploading data (for example, posted data) to the server 400 (S201), for example, when making a content upload request, the application connects to the gateway unit using a protocol such as UDP. Therefore, ports for connecting the mobile device 300 and the server 400 are secured in the gateway units 101 and 106, respectively (S202).
- the port securing process is performed, data is transmitted from the server 400 to the mobile device 300, and the data is received by the gateway unit 106 and the gateway unit 101 (S203).
- the timer unit 105 starts time-counting processing for the no-communication time in the mobile device 300 (S204).
- the source address and the destination address are described in the header of the data, and the gateway unit 106 recognizes the source address, so that the control unit 104 is downloading the data, that is, the data flows in the downstream direction. I can recognize that.
- the received data is sequentially relayed to the server 400 by the gateway units 101 and 106 (S205).
- the gateway units 101 and 106 On the other hand, when relay processing is performed in the gateway unit 101, billing processing according to the amount of data is performed by the billing processing unit 102 (S206).
- the control unit 104 determines whether or not the gateway unit 101 receives response data from the server 400 according to the detection result of the detection unit 107 (S207). If it is detected within a predetermined time, the count value in the timer unit 105 is reset (S208), the time counting process is started from the initial value, and the uplink data reception process, transfer process, and accounting are performed again. Processing is performed. If the response data is not received within the predetermined time (S209: YES), the port of the gateway unit 101 is closed, the timer unit 105 stops the no-communication time counting process, and the accounting process is stopped (S210). ).
- the detection point set in the device that closes the port that is, the gateway unit 101 detects the presence or absence of response data, and detects the response data at the detection point. If not, the accounting process is stopped and the port for receiving data from the mobile device 300 in the gateway unit 101 is closed. As a result, it is possible to perform an appropriate accounting process for data transmitted by a connectionless protocol. That is, it is possible to prevent the server 400 from being charged only when the data has not arrived, such as when the data cannot be received due to a failure or the like.
- FIG. 8 is a schematic diagram thereof.
- data is transmitted from the mobile device 300 to the server 400 as indicated by an arrow Y2. Since the data transmitted from the server 400 is transmitted by a connectionless protocol such as UDP, the gateway device 110 that is a charging processing point performs the charging process regardless of whether the server 400 can communicate. .
- a connectionless protocol such as UDP
- the server 400 When the server 400 is normal, the data can be received normally. Therefore, the server 400 can generate and transmit response data for the data. On the other hand, if the server 400 cannot communicate due to a failure or the like, the data cannot be received normally, so a trigger for generating response data cannot be obtained, and communication is impossible. You cannot send data.
- the proxy device 100 cannot receive response data.
- the gateway device 110 detection unit 103 cannot detect response data from the server 400 within a predetermined time at the data detection point P4
- the server 400 cannot transmit response data due to a failure or the like. Can be determined.
- the control unit 104 since the control unit 104 cannot receive a notification from the detection unit 107 that detection has been made within a predetermined period of time, the control unit 104 instructs the charging processing unit 102 to stop the charging process and the gateway.
- the unit 101 is instructed to close the reception port for receiving data from the mobile device 300. In FIG. 8, the port indicated by the close point P3 is closed. As a result, no data passes through the proxy device 100, so that no charging process is performed.
- the gateway device 110 is configured to include the data detection point P4 and the close point P3 as in the present embodiment, the occurrence of time lag is extremely small because of processing in the same device, and unnecessary billing is effective. Can be stopped automatically.
- FIG. 9 is a schematic diagram showing a schematic operation at that time.
- the proxy device 100 and the proxy device 100a have the same configuration, and the proxy device 100 manages the downlink no-communication state with respect to uplink data (data flowing through the arrow Y2). This manages the downstream no-communication state for data (data flowing through the arrow Y1).
- the present embodiment is not limited to one-to-one communication as described above, and can also be applied to one-to-N communication.
- proxy apparatus 100 when a connection request is received from mobile device 300 and a port is secured in accordance with the processing shown in FIG. 7, the relay processing of uplink data to mobile device 300a and the charging for mobile device 300 are performed. Processing is executed (arrow Y2: FIG. 7, S201 to S206).
- the presence or absence of response data from the mobile device 300a is detected at the downlink data detection point P4 defined in the gateway device 110.
- the response data is not detected within a predetermined time, it can be determined that the mobile device 300a is in a state where communication is not possible, such as being out of the communication range, and the gateway device 110 stops charging processing for the mobile device 300.
- the port is closed at the close point P3.
- the proxy device 100a detects the presence or absence of response data from the mobile device 300a. If the proxy device 100a cannot detect response data within a predetermined time, it can be determined that the mobile device 300a is out of communication, such as being out of communication range, and the gateway device 110a stops charging processing for the mobile device 300a. Then, the process of closing the port of the close point P2 set in the gateway device 120a is performed.
- FIG. 10 is a flowchart showing detailed processing of the proxy device 100 of this embodiment.
- FIG. 5 or FIG. 7 shows the schematic processing for each data in the upstream and downstream directions
- FIG. 10 shows the management of the timer set for each port, the processing according to the upstream data and downstream data. Is described in detail.
- the proxy device 100 When the proxy device 100 receives a connection request from the mobile device 300 (S301), a port securing process is performed in the gateway unit 101 and the gateway unit 106, respectively (S302). When there is a connection request or a communication request, a port is secured for each request. Then, the timer unit 105 starts the uplink / downlink no-communication timing for the port (S303). Specifically, as shown in FIG. 4, the timer unit 105 measures and manages the uplink no-communication time and the downlink no-communication time for each reserved port.
- control unit 104 determines whether the data is uplink data (S305). If it is determined that the data is upstream data (S305: upstream data), the gateway units 101 and 106 perform data relay processing (S306), and also according to the data amount of data relayed by the billing processing unit 102 A billing process is performed (S307). Then, the control unit 104 resets the timer value of the uplink no-communication time of all ports among the timer values clocked by the timer unit 105, and measures the no-communication time from the initial value again (S308).
- control unit 104 determines which port the data is for (S309). If it is determined that the data is downlink data for port A (S309: port A), the data relay process (S310), billing process (S311), and the timer value corresponding to port A in the downlink no-communication time is reset. Then, the process (S312) for starting the timing process is performed again.
- control unit 104 determines that the data is downlink data for port B (S309: port B), data relay processing (S313), accounting processing (S314), and corresponding to port B in the downlink no-communication time.
- the timer value is reset, and the process (S315) for starting the timing process is performed again.
- control unit 104 determines that the data is downlink data for the port C (S309: port C), the data relay process (S316), the accounting process (S317), and the timer corresponding to the port A in the downlink no-communication time.
- the process of resetting the value and starting the clocking process is performed again (S318).
- any one of the timer values corresponding to the uplink / downlink no-communication time at each port by the timer unit 105 is up (S319). )
- the time counting process of the timer unit 105 for the no-communication time that has timed out ends, and the control unit 104 performs a charging stop process and a port close process. That is, when the uplink no-communication time expires, the timer unit 105 finishes timing for the uplink / downlink no-communication time (S320). The port is closed.
- the gateway unit 101 and the gateway unit 106 transfer data transmitted and received between the mobile device 300 and the server 400 using the mobile device 300 or the server 400 as a transfer destination, and a charging processing unit 102 performs charging processing according to the amount of data transferred by the gateway unit 101 and the gateway unit 106.
- the detection unit 103 detects that response data has been transmitted from the transfer destination.
- the detection unit 103 detects data itself, and determines uplink data or downlink data.
- the control unit 104 instructs the timer unit 105 to set one of the timer values for the uplink / downlink communication time of the received port. Control to perform reset processing.
- control unit 104 stops the transfer processing for the gateway unit 101 or the gateway unit 106 when the timer value of the no-communication time exceeds a predetermined time and the response data from the transfer destination is not detected by the detection unit 103. In other words, it is possible to control to close the port and to stop the charging process for the charging processing unit 102.
- the proxy device 100 of the present embodiment when no response data is detected within a predetermined time after the transfer process is started, that is, the no-communication time counted by the timer unit 105 has exceeded the predetermined time.
- the transfer process is stopped by controlling the ports of the gateway unit 101 and the gateway unit 106 to be closed, and the charging process is stopped. , The connection state can be confirmed more accurately.
- the control unit 104 uses the timer unit 105 to manage the uplink no-communication time and the downlink no-communication time in units of ports, and the detection unit 103 receives the uplink from the mobile device 300. If the direction data cannot be detected, the timer unit 105 stops the counting processing of the uplink no-communication time of all the ports and stops the charging processing unit 102 charging processing. If the detection unit 103 cannot detect the downlink data from the server 400, the timing processing of the downlink non-communication time corresponding to the port to which the server 400 is connected is stopped and the charging process in the charging processing unit 102 is performed. Stop.
- the uplink no-communication time indicates the state between the mobile device 300 and the proxy device 100, and the mobile device is only connected to one port. Since 300 is out of the communication range and the mobile device 300 is not in the communication range for the other ports, it is appropriate to perform stop processing for all ports.
- the downlink no-communication time indicates a state between the server 400 and the proxy device 100 connected through one target port, and the server 400 connected through one port. In some cases, a server connected through another port may be in a communicable state even if the communication is not possible due to a failure or the like. Therefore, in this case, management is performed so that communication connection processing and billing processing for servers connected via other ports can be continuously performed.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims (4)
- 移動機とサーバとの間で送受信されるデータを、前記移動機または前記サーバを転送先にして転送する転送手段と、
前記転送手段により転送されたデータのデータ量に応じて課金処理を行う課金手段と、
前記転送手段の転送先から応答データが発信されたことを検出する検出手段と、
前記検出手段により前記転送先からの応答データが検出されない場合に、前記転送手段による転送処理を停止させる転送停止手段と、
前記検出手段により前記転送先からの応答データが検出されない場合に、前記課金手段の課金処理を停止させる課金停止手段と、
を備えるデータ中継装置。 - 前記転送停止手段は、前記転送手段による転送処理が開始されてから所定時間内に応答データが検出されない場合に、前記転送手段による転送処理を停止させ、
前記課金停止手段は、前記転送手段による転送処理が開始されてから所定時間内に応答データが検出されない場合に、前記課金手段による課金処理を停止させることを特徴とする請求項1に記載のデータ中継装置。 - ポート単位に、移動機からの応答データの無検出時間である上り無通信時間およびサーバからの応答データの無検出時間である下り無通信時間を計測する計測手段をさらに備え、
前記検出手段により、各ポートにおいて移動機からの応答データを所定時間検出できない場合には、
前記計測手段は、前記移動機により確保されている全ポートに対応する上り無通信時間の計測処理を停止し、
前記課金停止手段は、全ポートを介して前記所定時間以降に受信されたデータの前記課金手段による課金処理を停止させ、
前記転送停止手段は、全ポートをクローズする処理を行うことで前記転送手段による転送処理を停止させ、
確保されている全ポートのうち一のポートを介して接続されているサーバからの応答データを所定時間検出できない場合には、
前記計測手段は、当該一のポートに対応する下り無通信時間の計測処理を停止し、
前記課金停止手段は、当該一のポートを介して前記所定時間以降に受信されたデータの前記課金手段による課金処理を停止させ、
前記転送停止手段は、当該一のポートをクローズする処理を行うことで前記転送手段による転送処理を停止させることを特徴とする請求項2に記載のデータ中継装置。 - 移動機とサーバとの間で送受信されるデータを、前記移動機および前記サーバを転送先にして転送する転送ステップと、
前記転送ステップにより転送されたデータのデータ量に応じて課金処理を行う課金ステップと、
前記転送ステップの転送先から応答データが発信されたことを検出する検出ステップと、
前記検出ステップにより前記転送先からの応答データが検出されない場合に、前記転送ステップによる転送処理を停止させる転送停止ステップと、
前記検出ステップにより前記転送先からの応答データが検出されない場合に、前記課金ステップの課金処理を停止させる課金停止ステップと、
を備えるデータ中継方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2010505976A JP5139513B2 (ja) | 2008-04-03 | 2009-04-01 | データ中継装置およびデータ中継方法 |
CN2009801117857A CN101981877B (zh) | 2008-04-03 | 2009-04-01 | 数据中继装置和数据中继方法 |
EP09729181.9A EP2273731B1 (en) | 2008-04-03 | 2009-04-01 | Data relay device and data relay method |
US12/934,891 US8477612B2 (en) | 2008-04-03 | 2009-04-01 | Data relay device and data relay method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2008-097336 | 2008-04-03 | ||
JP2008097336 | 2008-04-03 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009123265A1 true WO2009123265A1 (ja) | 2009-10-08 |
Family
ID=41135632
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2009/056820 WO2009123265A1 (ja) | 2008-04-03 | 2009-04-01 | データ中継装置およびデータ中継方法 |
Country Status (5)
Country | Link |
---|---|
US (1) | US8477612B2 (ja) |
EP (1) | EP2273731B1 (ja) |
JP (1) | JP5139513B2 (ja) |
CN (1) | CN101981877B (ja) |
WO (1) | WO2009123265A1 (ja) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012086785A1 (ja) * | 2010-12-24 | 2012-06-28 | 株式会社エヌ・ティ・ティ・ドコモ | 交換機及び通信管理方法 |
WO2015093587A1 (ja) * | 2013-12-20 | 2015-06-25 | 株式会社Nttドコモ | ネットワーク装置、無線基地局、ユーザ装置及び移動通信方法 |
JP2017526277A (ja) * | 2014-08-11 | 2017-09-07 | 華為技術有限公司Huawei Technologies Co.,Ltd. | データ・サービスを実装するためのデバイス及び方法 |
JP2021511718A (ja) * | 2018-01-17 | 2021-05-06 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | サービスデータフロー処理方法および関連デバイス |
CN115767779A (zh) * | 2022-11-11 | 2023-03-07 | 格睿通智能科技(深圳)有限公司 | 包含Mesh组网的高实时性无线中继器多路径通讯方法 |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013078558A1 (en) * | 2011-11-28 | 2013-06-06 | Jigsee Inc. | Method of determining transport parameters for efficient data transport across a network |
US9621667B2 (en) * | 2012-08-27 | 2017-04-11 | Adobe Systems Incorporated | Streaming media with a server identified at runtime |
JP5929890B2 (ja) * | 2013-12-26 | 2016-06-08 | 横河電機株式会社 | 無線中継装置、無線通信システム、及び情報設定方法 |
US10069785B2 (en) * | 2015-06-05 | 2018-09-04 | Apple Inc. | Network messaging for paired devices |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH02142245A (ja) * | 1988-11-24 | 1990-05-31 | Mitsubishi Electric Corp | パケット交換網における課金方式 |
JPH1070530A (ja) * | 1996-08-28 | 1998-03-10 | Oki Electric Ind Co Ltd | 情報転送システム、情報蓄積提供装置及び情報被提供装置 |
JP2000124900A (ja) * | 1998-10-16 | 2000-04-28 | Nec Corp | 課金徴収方法とその装置及び通信システム |
JP2001512926A (ja) * | 1997-07-14 | 2001-08-28 | ノキア ネットワークス オサケ ユキチュア | アクセスサービスの遂行 |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5978775A (en) * | 1993-12-08 | 1999-11-02 | Lucent Technologies Inc. | Information distribution system using telephone network and telephone company billing service |
EP0827093A3 (en) * | 1996-08-28 | 1999-01-07 | Oki Electric Industry Co., Ltd. | Information transmission system, information storing and providing apparatus, and information receiving apparatus |
FI104667B (fi) | 1997-07-14 | 2000-04-14 | Nokia Networks Oy | Liittymäpalvelun toteuttaminen |
JP2000049774A (ja) | 1998-07-29 | 2000-02-18 | Nippon Telegr & Teleph Corp <Ntt> | 課金情報収集方式 |
FI20000761A0 (fi) * | 2000-03-31 | 2000-03-31 | Nokia Mobile Phones Ltd | Laskutus pakettidataverkossa |
DE10332558B4 (de) * | 2003-07-11 | 2006-06-01 | Siemens Ag | Verfahren zum Erkennen von Abrechnungsdatensätzen |
US7831247B2 (en) * | 2002-11-12 | 2010-11-09 | Nokia Corporation | Method of communication and communication system |
KR100509935B1 (ko) | 2003-02-11 | 2005-08-24 | 주식회사 케이티프리텔 | 이동 통신망에서 데이터 과금 세분화를 위한 방법 및 시스템 |
EP1656770B1 (en) * | 2003-08-19 | 2007-01-10 | NTT DoCoMo INC. | Accurate control of transmission information in ad hoc networks |
US20070189219A1 (en) * | 2005-11-21 | 2007-08-16 | Mruthyunjaya Navali | Internet protocol tunneling on a mobile network |
JP4423304B2 (ja) | 2007-03-19 | 2010-03-03 | 株式会社エヌ・ティ・ティ・ドコモ | 通信制御システム、通信制御方法、これらに用いて好適なルーティング制御装置及びルータ装置 |
-
2009
- 2009-04-01 EP EP09729181.9A patent/EP2273731B1/en not_active Not-in-force
- 2009-04-01 WO PCT/JP2009/056820 patent/WO2009123265A1/ja active Application Filing
- 2009-04-01 CN CN2009801117857A patent/CN101981877B/zh not_active Expired - Fee Related
- 2009-04-01 US US12/934,891 patent/US8477612B2/en not_active Expired - Fee Related
- 2009-04-01 JP JP2010505976A patent/JP5139513B2/ja not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH02142245A (ja) * | 1988-11-24 | 1990-05-31 | Mitsubishi Electric Corp | パケット交換網における課金方式 |
JPH1070530A (ja) * | 1996-08-28 | 1998-03-10 | Oki Electric Ind Co Ltd | 情報転送システム、情報蓄積提供装置及び情報被提供装置 |
JP2001512926A (ja) * | 1997-07-14 | 2001-08-28 | ノキア ネットワークス オサケ ユキチュア | アクセスサービスの遂行 |
JP2000124900A (ja) * | 1998-10-16 | 2000-04-28 | Nec Corp | 課金徴収方法とその装置及び通信システム |
Non-Patent Citations (1)
Title |
---|
See also references of EP2273731A4 * |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012086785A1 (ja) * | 2010-12-24 | 2012-06-28 | 株式会社エヌ・ティ・ティ・ドコモ | 交換機及び通信管理方法 |
JP2012138704A (ja) * | 2010-12-24 | 2012-07-19 | Ntt Docomo Inc | 交換機及び通信管理方法 |
CN103109551A (zh) * | 2010-12-24 | 2013-05-15 | 株式会社Ntt都科摩 | 交换机和通信管理方法 |
WO2015093587A1 (ja) * | 2013-12-20 | 2015-06-25 | 株式会社Nttドコモ | ネットワーク装置、無線基地局、ユーザ装置及び移動通信方法 |
JP2017526277A (ja) * | 2014-08-11 | 2017-09-07 | 華為技術有限公司Huawei Technologies Co.,Ltd. | データ・サービスを実装するためのデバイス及び方法 |
US10225412B2 (en) | 2014-08-11 | 2019-03-05 | Huawei Technologies Co., Ltd. | Device and method for implementing data service |
US10798251B2 (en) | 2014-08-11 | 2020-10-06 | Huawei Technologies Co., Ltd. | Device and method for implementing data service |
JP2021511718A (ja) * | 2018-01-17 | 2021-05-06 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | サービスデータフロー処理方法および関連デバイス |
US11303761B2 (en) | 2018-01-17 | 2022-04-12 | Huawei Technologies Co., Ltd. | Service data flow processing method and related device |
JP7207764B2 (ja) | 2018-01-17 | 2023-01-18 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | サービスデータフロー処理方法および関連デバイス |
CN115767779A (zh) * | 2022-11-11 | 2023-03-07 | 格睿通智能科技(深圳)有限公司 | 包含Mesh组网的高实时性无线中继器多路径通讯方法 |
Also Published As
Publication number | Publication date |
---|---|
CN101981877A (zh) | 2011-02-23 |
US20110090801A1 (en) | 2011-04-21 |
JPWO2009123265A1 (ja) | 2011-07-28 |
CN101981877B (zh) | 2013-06-05 |
EP2273731A1 (en) | 2011-01-12 |
EP2273731A4 (en) | 2012-06-20 |
EP2273731B1 (en) | 2013-06-12 |
JP5139513B2 (ja) | 2013-02-06 |
US8477612B2 (en) | 2013-07-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5139513B2 (ja) | データ中継装置およびデータ中継方法 | |
US7668560B2 (en) | Method and apparatus for accessing network isolated devices | |
US20090112742A1 (en) | Communication control method in connection-oriented communication, related transfer device, and billing management device | |
US7640297B2 (en) | Protocol optimization for wireless networks | |
TW200605577A (en) | Providing roaming status information for service control in a packet data based communication network | |
WO2011021875A3 (en) | Server for control plane at mobile communication network and method for controlling local ip access service | |
CN105493449A (zh) | 速率控制 | |
US8848579B1 (en) | Methods and systems for using transport-layer source ports to identify sources of packet payloads in mixed tethering and non-tethering environments | |
CN100484142C (zh) | 一种通过网络时间协议对客户端校时的方法及设备 | |
JP5887761B2 (ja) | 通信システム、パケット中継装置、ユーザ端末及び通信方法 | |
KR20150042942A (ko) | 컨텐츠 전송 시스템에서의 과금 처리 방법, 이를 위한 장치 | |
JP2005528017A (ja) | 通信端末装置間の通信リンクの決済方法 | |
KR100598974B1 (ko) | 네트워크 장비 감시 장치 및 방법 | |
KR20060087241A (ko) | 통신 시스템에서 미러링 서비스를 제공하기 위한 방법 및장치와 그 통신시스템 | |
JP4834565B2 (ja) | 通信システム、および移動通信システムにおけるサービス提供方法 | |
JP2005267014A (ja) | サーバ装置 | |
WO2016056614A1 (ja) | パケット使用量算出装置及びパケット使用量算出方法 | |
JP2010171852A (ja) | 課金データ生成方法、呼制御方法、通信システム、情報処理装置および中継用セッション制御サーバ | |
KR100631695B1 (ko) | 휴대단말기의 아엠피에스 서비스 운용장치 및 방법 | |
KR102406213B1 (ko) | 이동단말기의 데이터 전송 방법 | |
KR20100119415A (ko) | 인스턴트 메시징 서비스 제공 서버 및 그 방법. | |
JP2004064448A (ja) | 移動体パケット通信システムおよびそのパケットデータ量通知方法ならびにプログラム | |
KR20070050176A (ko) | 한도 초과 승인 서비스를 제공하는 방법 및 시스템 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200980111785.7 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09729181 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010505976 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009729181 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 12934891 Country of ref document: US |