EP1723795A1 - Vorrichtung und verfahren zur vergeb hrung von ber ein pakentnetz gef hrten verbindungen - Google Patents
Vorrichtung und verfahren zur vergeb hrung von ber ein pakentnetz gef hrten verbindungenInfo
- Publication number
- EP1723795A1 EP1723795A1 EP05716851A EP05716851A EP1723795A1 EP 1723795 A1 EP1723795 A1 EP 1723795A1 EP 05716851 A EP05716851 A EP 05716851A EP 05716851 A EP05716851 A EP 05716851A EP 1723795 A1 EP1723795 A1 EP 1723795A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- packets
- connection
- gateway
- information
- quality standard
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims description 21
- 230000011664 signaling Effects 0.000 claims description 29
- 230000005540 biological transmission Effects 0.000 claims description 9
- 238000012546 transfer Methods 0.000 claims description 7
- 238000003908 quality control method Methods 0.000 claims 2
- 230000002457 bidirectional effect Effects 0.000 claims 1
- 238000012986 modification Methods 0.000 claims 1
- 230000004048 modification Effects 0.000 claims 1
- 238000004806 packaging method and process Methods 0.000 claims 1
- 230000001629 suppression Effects 0.000 claims 1
- 230000001960 triggered effect Effects 0.000 description 10
- 238000013459 approach Methods 0.000 description 3
- 238000002955 isolation Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000003111 delayed effect Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000007257 malfunction Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000012805 post-processing Methods 0.000 description 2
- 239000000969 carrier Substances 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 230000008030 elimination Effects 0.000 description 1
- 238000003379 elimination reaction Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000007789 sealing Methods 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
- H04N21/4363—Adapting the video stream to a specific local network, e.g. a Bluetooth® network
-
- 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/80—Rating or billing plans; Tariff determination aspects
- H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
- H04N21/2381—Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/24—Monitoring of processes or resources, e.g. monitoring of server load, available bandwidth, upstream requests
- H04N21/2402—Monitoring of the downstream path of the transmission network, e.g. bandwidth available
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/438—Interfacing the downstream path of the transmission network originating from a server, e.g. retrieving encoded video stream packets from an IP network
- H04N21/4381—Recovering the multiplex stream from a specific network, e.g. recovering MPEG packets from ATM cells
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/442—Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
- H04N21/44209—Monitoring of downstream path of the transmission network originating from a server, e.g. bandwidth variations of a wireless network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/61—Network physical structure; Signal processing
- H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
- H04N21/6125—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via Internet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
- H04N21/647—Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
- H04N21/64723—Monitoring of network processes or resources, e.g. monitoring of network load
- H04N21/64738—Monitoring network characteristics, e.g. bandwidth, congestion level
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/14—Billing aspects relating to the actual charge
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/22—Bandwidth or usage-sensitve billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/74—Rating aspects, e.g. rating parameters or tariff determination apects
- H04M2215/7414—QoS
Definitions
- Time-based billing is already widely known from TDM.
- TDM channels are provided here, which are routed to the exchange. There is then the charge z. B. channel by channel for the duration of the connection. Faults are recognized immediately and the affected connections are triggered immediately. The charge is also stopped when the connection is triggered. This approach would be suitable for audio and video via TDM (the number of channels determines the quality and fee), but it cannot be used in the packet network.
- the user data stream is preferably routed outside the switching center directly between the subscribers involved.
- Network failures that interrupt this user data stream are generally not immediately recognized in the packet-based switching centers that control the connection.
- the billing therefore continues even though the user data stream has already been interrupted.
- the connection can therefore only be triggered or the charging stopped, if the network fault is revealed by the signaling.
- a signaling path that is disturbed at the same time as the useful data path rarely occurs because signaling data and useful data are routed via different paths and connection sections.
- a loss of signaling in a stable conversation state cannot be recognized without further measures, since in this state i.a. no signaling messages are exchanged.
- the loss of the user data transmission leads to detection in the end devices or the devices close to the end devices, which then inform the packet-based switching center via signaling. However, this can be delayed and is not certain since the signaling path could also be disturbed.
- the charge is preferably provided via fiat rate or event-related (query of a proxy for establishing a connection).
- the invention has for its object to show a way how can be provided efficiently for a time-based billing in a packet network.
- the invention is achieved on the basis of the features specified in the preamble of claim 1 by the characterizing features.
- the particular advantage of the invention is that the user data stream transmitted between two subscribers is carried over an IP gateway.
- the user data streams of a connection comprising several user data streams are recorded separately in the IP gateway. This allows errors and network faults that lead to the interruption or termination of the user data stream to be recognized quickly and reliably and to be billed with the high accuracy known from conventional switching technology (e.g. Is or 500 ms). With this concept there is therefore an exact time-based charging of a packet-based
- IP IP Connection
- the outlay for such a configuration can be kept very low.
- existing charging interfaces and postprocessing methods e.g. connection-by-section identification of video / audio shares in the individual connection statement
- FIG. 1 shows a network configuration with media gateways and media gateway controllers, and an IP gateway
- media gateways MG A (media gateway on the A side) and MG B (media gateway on the B side) are provided.
- both media gateways should be designed as set-top boxes, which are connected on the subscriber side to the subscriber terminals A, B.
- the two media gateways or set-top boxes MG A and MG B are each controlled by call control servers or media gateway controllers MGC A, MGC B using a protocol P.
- a protocol known per se, such as the MGCP, H.323 or SIP protocol, can be used as the control protocol P here. Both controllers exchange information via a known interoffice signaling protocol.
- the signaling information relevant for the connection between the two subscriber terminals A, B integrated into the connection is routed via the two set-top boxes and the two media gateway controllers (signaling connection).
- two media gateway controllers are shown. However, this number is not a mandatory requirement for the invention, several media gateway controllers can be used in the same way as a single media gateway controller.
- the bearer connection Carrying user data (bearer connection) via an IP gateway IPGW (looping in).
- the bearer connection carries audio useful data in the case of a pure audio connection and audio and video useful data in the case of a video connection. In the latter case it is e.g. B. two user data streams in the context of a connection, as indicated in Fig. 1.
- the user data stream is thus carried indirectly between the packet-based end points (set-top boxes) MG A and MG B.
- the user data is transmitted using the Real Time Protocol RTP and the Real Time Control Protocol RTCP.
- the IP gateway IPGW is also used by the charging media gateway controller MGC A using a protocol known per se, e.g. B. H.248 controlled.
- the media gateway controller MGC A on the A side should preferably be assigned the function of the charging controller.
- CDR Chip Data Records
- CDR are generated here in the soapy controller for the undisturbed connection process. They contain the required accuracy (e.g. billing to the exact ls) and have a sequence of information elements that document the beginning, end and type (audio, video, possibly bandwidth, possibly codec) of the connection section. Additional information such as changing the type property (e.g. audio ⁇ -> video) during a connection is also recorded. Additional information about the quality of the connection, the specification of the connection time, bandwidth / volume of the audio and the video carrier can be provided in the IP gateway IPGW as CDR or via the signaling to the charging media gateway controller.
- a connection request originating from subscriber terminal A is communicated to subscriber terminal B via the two media gateway controllers MGC A and MGC B. If the subscriber terminal B accepts the call, the bearer connection is switched bidirectionally (ie back and forth) between the media gateway MG A and the IP gateway IPGW and between the IP gateway IPGW and the media gateway MG B.
- the billing is now started in the IP gateway.
- the two media gateways MG A and MG B and the IP gateway (IPGW) now ensure that regardless of the type of connection, the coding method and the packet length, RTP / RTCP packets with a specified minimum interval of z. B. 100 ms are transmitted. This minimum distance should be configurable.
- the MG A, MG B and the TP gateway thus determine the integrity of the user data stream as long as IP packets of the user data stream arrive at this minimum distance.
- RTP packets in a definable minimum time interval is for voice connections i. a. fulfilled and no additional requirement.
- a packet is generated even if this would not be necessary due to the "Silence Supression" feature in the audio stream, still image transmission in the video stream, missing input signal or also due to the coding method used or the packet length used.
- the media gateways MG A and MG B monitor the arrival of the aforementioned IP packets at a guaranteed minimum interval in order to check the quality of the through-connected RTP carriers.
- IP gateway IPGW now determines that there is no IP packet within the minimum distance, after waiting for a protection time Ti (eg 200 ms) the connection is defined as inactive and the packet transfer to the opposite side and in the reverse direction is set. In addition, a corresponding fee ticket is immediately written and handed over to the Media Gateway Controller MGC A.
- a protection time Ti eg 200 ms
- the absence of the IP packets can also be determined in the same way by the two media gateways MG A and MG B. In this case, the packet transfer in the reverse direction is stopped and the signaling to the assigned media gateway controller MGC A or MGC B is initiated. This initiates the termination of the connection concerned.
- the termination signaling can be defined by a defined amount
- Protection time ⁇ 2 is delayed in the media gateways (e.g. 2 s).
- the regular triggering of the connection from subscriber terminal A or B thus leads to the detection of the interruption of the RTP stream in the IP gateway IPGW and in the media gateways MG A and MG B.
- the protection time T 2 the usual procedure for disconnecting the connection takes place ( Call Flow), which is not associated with an increased signaling load.
- the Fee information can be specified online via signaling between IPGW and MGC A or offline during postprocessing in the billing center by directly including the information from the IP gateway.
- the charge information is specified with information identifying the connection and stored in the IP gateway. This information can also be transferred to a device different from the charging controller MGC A for evaluation.
- the configuration according to the invention tolerates the failure of various devices without major repercussions on the charging:
- the failure of one of the media gateways MG A or MG B leads to the termination of the RTP / RTCP packet transfer in the IP gateway IPGW.
- the termination is signaled by the opposite side, i.e. GW A, GW B.
- Exact charge information is available in the IP gateway. Since the charge information in the IP gateway can be determined very precisely, the charge information possibly recorded in parallel in the controller can be specified online by signaling or offline via separate CDRs of the IP gateway.
- the simultaneous failure of the two media gateways MG A and MG B also leads to the termination of the RTP / RTCP packet transfer in the IP gateway. In this case, too, exact charge information is determined in the IP gateway. After the A or B side is available again, the termination is revealed by signaling the media gateways and by immediately notifying the IP GW to the call control server. Since the charge information in the IP gateway can be determined very precisely, the charge information possibly recorded in parallel in the controller can be specified online by signaling or offline via separate CDRs of the IP gateway.
- Temporary isolation of the charging media gateway controller (regardless of whether MGC A or MGC B) does not result in the user data streams being interrupted. Even if it is triggered after the malfunction, it looks as if there had been no malfunction before. If the triggering occurs during the fault, the information is provided at the latest by the Media Gateway MG A or MG B or via the IP Gateway after availability by repeating the trigger signal or by another protocol-specific message. Precise charge information is available in the IP gateway. If necessary, the charge information can be specified online by signaling or offline via separate CDRs of the IP gateway.
- a loss of communication between the charging media gateway controller and the IP gateway leads to the triggering of the affected connections. This is necessary because the case could arise in which the charge information is no longer available in the IP gateway and the signaled "On Hook" messages from the media gateway controller MG A or MG B have been lost.
- IP gateway High-frequency monitoring via signaling exchange is only required for the IP gateway, but not for each of the media gateways. However, since the IP gateway is actually a larger gateway, i.a. no additional signaling and network load.
- FIG. 1 shows the configuration and method according to the invention in detail. It is assumed here, for example, that after subscriber input during a call made via TDM exchanges, the terminal controls a new call over the IP network. This second call continues the first call and allows further features, such as. B. Additional video phone sections of the connection.
- both a pure voice connection and a voice + video connection can be established.
- the subscriber can switch between audio and audio + video transmission as desired.
- exact billing as for the TDM call is mandatory.
- the operator should be able to charge the various services (eg audio, video) differently.
- SIP Session Initiation Protocol
- SIP devices SIP user A, SIP user B
- a media call control protocol is used to control the IP gateway.
- H.248 protocol should preferably be used here.
- the Call Control Server MGC A or MGC B Media Gateway Controller
- the signaling messages between the subscriber and the switching computer are routed via the SIP proxy server.
- the switching computers MGC A or MGC B have an upstream unit PCU which is responsible for the IP interface and the handling of the IP protocols. Furthermore, they have a switching core system that can control not only IP but also TDM switching technology and has an introduced charging interface. The interface between the PCU and the core system uses an internal protocol.
- a call is made according to the following procedure:
- a SIP Invite message with SDP information (audio codecs) is sent from the subscriber (SIP user A) to the PCU unit. After the A-side unit PCU has received an invite message, it creates the resources for the new call via Megaco in the IP gateway (add with two new ephemeral terminations). The SDP data on the A side are immediately transferred to the IP gateway. The IP gateway also receives a call reference, which it uses for fee tickets for this connection.
- the SDP data IP address and port
- IP gateway After determining the B side in the core system and accepting the
- the invite is acknowledged by the B side with a SIP: 200ok message.
- This 200ok message is used on the A-side as a criterion to start the audio charging.
- the PCU unit sends a corresponding internal message to the core system.
- the IP gateway IPGW is supplied with the SDP data on the B side and on the other hand it is set to Send — Receive. Monitoring of the RTP stream begins. If a further SIP: Invite message with SDP information (audio codecs plus video codecs) comes from a subscriber to the PCU unit and is acknowledged positively by the other side, this is again accepted with a SIP: 200ok message. The IP gateway is supplied with the new codec information. Simultaneously with the SIP: 200ok message, a message is sent on the A-side from the PCU unit to the core system, which indicates the use of the video service.
- SIP Invite message with SDP information (audio) is handled analogously by the PCU unit. If the other side acknowledges positively and with SIP: 200ok the switching off of the video transmission is accepted, the unit informs PCU the core system with a message indicating the use of the pure audio service. The IP gateway is then supplied with the new codec information.
- the billing is stopped on the A-side with the message SIP: Bye message from one side of the call.
- the call is also triggered in the IP gateway (subtract of the two terminations). If there are no network faults, a charging accuracy of 500ms can be achieved, as is usually required by the network operators.
- the failure of the A side in the RTP stream is noticed by the B side and reported to the PCU unit.
- the call is triggered there.
- the IP gateway also detects the absence of RTP packets from the A side and reports the exact duration of the connection to the PCU unit.
- the failure of the B side is treated symmetrically to the failure of the A side.
- Network faults that interrupt the communication of the PCU to the A and / or B side do not result in the call being triggered as long as the PCU unit is connected to the IP gateway and the latter reports no RTP fault. Any "on hook" messages are repeated by the end devices until the network error is remedied.
- the exact time data on the duration of the RTP connection are determined on the IP gateway, saved and signaled to the PCU unit.
- the IP gateway If the IP gateway detects a fault in the RTP current, it signals this to the PCU unit. The call is triggered and billed with sufficient accuracy.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102004011459 | 2004-03-09 | ||
PCT/EP2005/050878 WO2005086484A1 (de) | 2004-03-09 | 2005-03-01 | Vorrichtung und verfahren zur vergebührung von über ein pakentnetz geführten verbindungen |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1723795A1 true EP1723795A1 (de) | 2006-11-22 |
Family
ID=34917090
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP05716851A Withdrawn EP1723795A1 (de) | 2004-03-09 | 2005-03-01 | Vorrichtung und verfahren zur vergeb hrung von ber ein pakentnetz gef hrten verbindungen |
Country Status (5)
Country | Link |
---|---|
US (1) | US7680103B2 (de) |
EP (1) | EP1723795A1 (de) |
CN (1) | CN100566412C (de) |
BR (1) | BRPI0508498A (de) |
WO (1) | WO2005086484A1 (de) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3819019B1 (ja) * | 2005-06-08 | 2006-09-06 | シャープ株式会社 | 送受信方法およびプログラム並びに記録媒体 |
US7756052B2 (en) * | 2005-09-22 | 2010-07-13 | Itxc Ip Holdings S.A.R.L. | Determining quality of voice calls over a packet network |
CN101212316A (zh) * | 2006-12-25 | 2008-07-02 | 华为技术有限公司 | 一种多方会话中基于媒体流计费的方法及系统 |
US20080301053A1 (en) * | 2007-05-29 | 2008-12-04 | Verizon Services Organization Inc. | Service broker |
CZ303711B6 (cs) * | 2011-06-28 | 2013-03-27 | Ceské vysoké ucení technické v Praze Fakulta elektrotechnická | Systém pro rízení tarifikace v telekomunikacních sítích v návaznosti na kvalitu prenáseného hovoru |
EP2912804B1 (de) * | 2012-10-29 | 2019-04-10 | Telefonaktiebolaget LM Ericsson (publ) | Paketdatennetz-gatewayaufhängung für genaues laden in einem entwickelten paketsystem |
KR102090515B1 (ko) | 2013-01-18 | 2020-03-18 | 삼성전자주식회사 | 혼잡 상황에서 서비스 레벨을 조절하는 방법 및 장치 |
CN107431610A (zh) * | 2013-12-25 | 2017-12-01 | 华为技术有限公司 | 半双工频分双工的通信方法、基站和终端 |
US10148825B2 (en) * | 2015-09-09 | 2018-12-04 | Nokia Of America Corporation | Charging for rerouted packets in a heterogeneous wireless communication system |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001028219A2 (en) * | 1999-10-14 | 2001-04-19 | Motorola, Inc. | Quality-based billing system |
Family Cites Families (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5241534A (en) * | 1990-06-18 | 1993-08-31 | Fujitsu Limited | Rerouting and change-back systems for asynchronous transfer mode network |
GB2307138A (en) | 1995-11-09 | 1997-05-14 | Northern Telecom Ltd | Packet network tariffing |
US7028088B1 (en) * | 1996-04-03 | 2006-04-11 | Scientific-Atlanta, Inc. | System and method for providing statistics for flexible billing in a cable environment |
US5898668A (en) * | 1996-12-13 | 1999-04-27 | Siemens Information And Communication Networks, Inc. | Method and system for increasing quality of service at or below a threshold cost |
CA2285585A1 (en) | 1997-04-16 | 1998-10-22 | John Leonard Adams | Network testing |
FI104668B (fi) | 1997-07-14 | 2000-04-14 | Nokia Networks Oy | Liittymäpalvelun toteuttaminen |
US6285748B1 (en) * | 1997-09-25 | 2001-09-04 | At&T Corporation | Network traffic controller |
US6338046B1 (en) * | 1997-10-06 | 2002-01-08 | Nokia Telecommunications, Oy | System and method for determining charges for usage of a network connection |
DE19849540B4 (de) | 1998-07-06 | 2006-09-28 | Siemens Ag | Verfahren und Mobilfunknetz zur Behandlung eines Paketdatendienstes |
US6230144B1 (en) | 1998-07-07 | 2001-05-08 | Nokia Telecommunications Oy | Method and apparatus using an accounting bit for a SIMA network |
US6636487B1 (en) * | 1998-12-16 | 2003-10-21 | At&T Corp. | Apparatus and method for providing multimedia conferencing services with an unspecified bit rate quality of service class over an asynchronous transfer mode network |
US6445916B1 (en) * | 1999-01-07 | 2002-09-03 | Lucent Technologies Inc. | Wireless system and method for evaluating quality of service |
US6512761B1 (en) | 1999-02-02 | 2003-01-28 | 3Com Corporation | System for adjusting billing for real-time media transmissions based on delay |
US6625657B1 (en) | 1999-03-25 | 2003-09-23 | Nortel Networks Limited | System for requesting missing network accounting records if there is a break in sequence numbers while the records are transmitting from a source device |
WO2000072572A1 (en) | 1999-05-20 | 2000-11-30 | Motorola Inc. | Session based billing in a communication system |
US6449588B1 (en) | 1999-06-02 | 2002-09-10 | Accenture Llp | Customer-driven QOS in hybrid communication system |
US7251256B1 (en) * | 2000-05-18 | 2007-07-31 | Luminous Networks, Inc. | Synchronization of asynchronous networks using media access control (MAC) layer synchronization symbols |
JP4306098B2 (ja) * | 2000-06-30 | 2009-07-29 | 株式会社デンソー | 通信装置 |
JP3397759B2 (ja) | 2000-07-06 | 2003-04-21 | 日本電気株式会社 | インターネット電話通信システム及び課金方法 |
CA2417710C (en) * | 2000-08-09 | 2007-05-15 | British Telecommunications Public Limited Company | Telecommunications systems |
US6854014B1 (en) * | 2000-11-07 | 2005-02-08 | Nortel Networks Limited | System and method for accounting management in an IP centric distributed network |
US6721554B2 (en) | 2000-12-08 | 2004-04-13 | Lucent Technologies Inc. | Method and apparatus for policy-based charging for telecommunications services |
US20020122429A1 (en) * | 2001-03-05 | 2002-09-05 | Griggs Theodore Leon | Mechanism and method for user selection of dynamic quality of service in telephony |
ATE408968T1 (de) | 2001-06-15 | 2008-10-15 | Ascom Schweiz Ag | Bewertung der dienstgüte durch vergleich der aktuellen dienstgüte mit der zwischen dem benutzer und dem netz vereinbarten dienstgüte |
US6865159B2 (en) * | 2001-10-02 | 2005-03-08 | Hewlett-Packard Development Company, L.P. | System and method for comfort noise production |
KR100408525B1 (ko) * | 2001-10-31 | 2003-12-06 | 삼성전자주식회사 | 네트워크에 적응적인 실시간 멀티미디어 스트리밍 시스템및 방법 |
US7215666B1 (en) * | 2001-11-13 | 2007-05-08 | Nortel Networks Limited | Data burst scheduling |
DE10163530A1 (de) * | 2001-12-21 | 2003-07-03 | Siemens Ag | Verfahren zum Überwachen der Dienstgüte in paketorientierten Netzen |
CN1450749A (zh) * | 2002-04-10 | 2003-10-22 | 华为技术有限公司 | 一种分组数据业务的计费方法 |
US20030235214A1 (en) * | 2002-05-07 | 2003-12-25 | Andre Leroux | Service channel over the Ethernet inter-frame gap |
TWI237472B (en) * | 2003-12-16 | 2005-08-01 | Ind Tech Res Inst | Transmission system for packet switching network with communication quality displaying capability and the method of the same |
US7574594B2 (en) * | 2005-02-23 | 2009-08-11 | Dell Products Lp | Network authentication based on inter-packet gap characteristics |
-
2005
- 2005-03-01 CN CNB2005800075986A patent/CN100566412C/zh active Active
- 2005-03-01 EP EP05716851A patent/EP1723795A1/de not_active Withdrawn
- 2005-03-01 WO PCT/EP2005/050878 patent/WO2005086484A1/de not_active Application Discontinuation
- 2005-03-01 US US10/592,294 patent/US7680103B2/en active Active
- 2005-03-01 BR BRPI0508498-9A patent/BRPI0508498A/pt not_active IP Right Cessation
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001028219A2 (en) * | 1999-10-14 | 2001-04-19 | Motorola, Inc. | Quality-based billing system |
Also Published As
Publication number | Publication date |
---|---|
WO2005086484A1 (de) | 2005-09-15 |
US20070159972A1 (en) | 2007-07-12 |
US7680103B2 (en) | 2010-03-16 |
CN1930889A (zh) | 2007-03-14 |
BRPI0508498A (pt) | 2007-07-31 |
CN100566412C (zh) | 2009-12-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1723795A1 (de) | Vorrichtung und verfahren zur vergeb hrung von ber ein pakentnetz gef hrten verbindungen | |
DE60014234T2 (de) | System und Verfahren zum Ermöglichen von Fehlertolerante Systeme | |
EP0910201A2 (de) | Vorrichtung und Verfahren zum Aufbau einer Gesprächsverbindung | |
WO2003049367A2 (de) | Verfahren zum bereitstellen von leistungsmerkmalen für alternativ-verbindungen von primär-verbindungen | |
EP1480431A1 (de) | Verfahren zur Signalisierung von Anrufumleitungsparametern in einem SIP-Netz | |
WO2005079049A1 (de) | Aufbau einer paketorientierten multimediaverbindung unter mitwirkung eines interactive voice responce systems | |
EP1388996B1 (de) | Verfahren und Anordnung zum Steuern einer Konferenzschaltung in einem paketorientierten Kommunikationsnetz | |
DE10147164B4 (de) | Verfahren zur Ermittlung der Laufzeitverzögerung einer Verbindung mit Übertragung über ein paketbasiertes Netz | |
EP1779643B1 (de) | Verfahren und vorrichtung zum nutzdatenabgriff multimedialer verbindungen in einem paketnetz | |
EP1341357B1 (de) | Verfahren zur Dienstgütesicherung in einem Kommunikationsnetz sowie Anordnung und Einrichtungen zur Realisierung des Verfahrens | |
DE10135933A1 (de) | Verfahren zur Prüfung einer Nutzkanalverbindung in einem Telekommunikationssystem | |
EP1782607B1 (de) | Verfahren und vorrichtung zum nutzdatenabgriff multimedialer verbindungen in einem paketnetz | |
EP1658719B1 (de) | Verfahren zur Steuerung eines Media Gateways | |
EP2014069A1 (de) | Richterliches mithören bei peer-to-peer netzen | |
EP1398935B1 (de) | Verfahren zum Aufbau einer Nutzdatenverbindung zwischen Endpunkten in einer VoIP-Anordnung | |
WO2003088685A1 (de) | Call hold / terminal portability in h.323/isup-bicc-sip netzen | |
DE102004002680A1 (de) | Adaptereinheit und Verfahren | |
EP1981293B1 (de) | Verfahren zum Erfassen von Anrufen und zugehörige Einheiten | |
DE10241197A1 (de) | Verfahren zum Weiterleiten von Signalisierungsnachrichten und zugehörige Komponenten | |
DE10147873A1 (de) | Flexible und aufwandsarme Bereitstellung von Dienstmerkmalen für Sprachübertragung im Paketnetz | |
DE102009047784B4 (de) | Richterliches Mithören bei multimedialen Diensten | |
EP1521391A1 (de) | Verfahren zur Vergebührung von Verbindungen in einem Kommunikationsnetz | |
DE102004021698A1 (de) | Verfahren und Telekommunikationsanordnung zur Steuerung der Auslastung von Einwählpunkten in ein Paketvermittlungsnetz | |
EP1109392A1 (de) | Empfang ankommender Rufe über ein Fernspechnetz oder über das Internet |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20060728 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): DE FR GB |
|
DAX | Request for extension of the european patent (deleted) | ||
RBV | Designated contracting states (corrected) |
Designated state(s): DE FR GB |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG |
|
RAP3 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: NOKIA SIEMENS NETWORKS S.P.A. |
|
RAP3 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG |
|
17Q | First examination report despatched |
Effective date: 20120814 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: NOKIA SOLUTIONS AND NETWORKS GMBH & CO. KG |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20150106 |