US20090055298A1 - Method for configuring billing processes in network elements - Google Patents
Method for configuring billing processes in network elements Download PDFInfo
- Publication number
- US20090055298A1 US20090055298A1 US11/664,941 US66494104A US2009055298A1 US 20090055298 A1 US20090055298 A1 US 20090055298A1 US 66494104 A US66494104 A US 66494104A US 2009055298 A1 US2009055298 A1 US 2009055298A1
- Authority
- US
- United States
- Prior art keywords
- network element
- configuration message
- network elements
- data path
- terminal
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 230000008569 process Effects 0.000 title claims abstract description 10
- 230000005540 biological transmission Effects 0.000 claims abstract description 18
- 238000004891 communication Methods 0.000 claims abstract description 18
- 101000708874 Homo sapiens Zinc finger protein ubi-d4 Proteins 0.000 description 5
- 102100032701 Zinc finger protein ubi-d4 Human genes 0.000 description 5
- 102100029859 Zinc finger protein neuro-d4 Human genes 0.000 description 3
- 230000011664 signaling Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
Images
Classifications
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- 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/1403—Architecture for metering, charging or billing
-
- 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
Definitions
- the invention relates to a method for configuring billing processes in network elements of a data path for the transmission of packet data in a communications.
- Packet data services are known which use what is known as “IP Layer 3” of the “Open Systems Interconnection Reference, OSI” model within a communications network for example.
- IP Layer 3 of the “Open Systems Interconnection Reference, OSI” model within a communications network for example.
- OSI Open Systems Interconnection Reference
- This model serves as a reference model of the international Standards Organization ISO for networks in order to define an open communication using interface standards.
- Billing data recording for a data service is based in this case on an independent and non-synchronized detection by network elements which are used to execute the data service.
- the network elements involved in the transmission of a data service in such cases each have assigned billing processes which are used for recording billing data.
- the billing data is collected in network elements provided especially for the purpose in order to create a service-oriented or service-specific billing.
- the network elements involved in billing data recording have a unique correlation identifier to allow them identify all billing data pertaining to a concrete service usage.
- the correlation identifier is entered in the billing data so that billing data can be linked together by a central entity and processed together for billing.
- a central problem of this type of billing is the distribution of the unique correlation identifier to the respective network elements.
- the network elements involved in executing a service generally operate on different network layers, for example on layers of the OSI model—Layer 2, Layer 3 or Layer 7.
- Network elements are arranged in different areas of the network, for example if they are arranged in a “Packet Switched, PS” domain or in an “IP Multimedia Subsystem, IMS”.
- the network elements involved in the execution of a packet data service can be separated from each other by technology boundaries.
- some of the network elements can be based on the “Universal Mobile Telecommunication system, UMTS” whereas others can be based on the “Wireless Local Area Network, WLAN”.
- One possible object of the present invention is to implement a simple and quick-to-execute method for configuration of billing processes at network elements, to enable billing data to be recorded for a packet data service in a communications network.
- the packet data is transmitted between a terminal, for example a radio communication terminal on one side, and an application host on the other side, in two directions, and thereby over two data paths.
- a billing control function which is held in a central network element is used for configuring the network elements of a data path.
- this central network element is not a component of the data path, i.e. the packet data transmission in question is not undertaken via the central network element.
- the billing control function forms a configuration message for configuration of the network elements and is started for example when a service is requested.
- the configuration message is transmitted via the application host as the first network element to the network element of the data path to be configured.
- Those network elements which are to be configured evaluate the configuration message for an initialization, whereas other network elements of the data path forward the configuration message.
- the “Network Link Services Protocol, NLSP”, known per se, is preferably, but not exclusively used with the communications network to transmit the configuration message together with further signaling messages to the network elements.
- the configuration message is formed by the central network element and not by the application host used as a further ingress node for the data path.
- a central billing control function is implemented with the aid of the method for storage of configuration rules.
- FIG. 1 shows a method with reference to a communications network, in accordance with one possible embodiment of the invention.
- the communications network features network elements NE 1 to NE 6 , a central network element NEZ and a terminal T, with a first network element NE 1 being embodied as an application host and a second network element NE 2 as a Radio Network Controller RNC.
- a billing control function GKF is stored or implemented on the central network element NEZ.
- a configuration message KN is formed by the billing control function GKF, which is used for configuration of the network elements NE 3 , NE 4 , NE 5 and NE 6 .
- the configuration message KN is transmitted to network element NEx of a first data path DPF 1 , with the first data path DPF 1 including network elements NE 1 , NE 3 , NE 4 and NE 2 .
- An assigned first packet data transmission PKD 1 is undertaken along the first data path DPF 1 from first network element NE 1 via the network elements NE 3 and NE 4 and via the second network element NE 2 to terminal T, with terminal T being assigned to the second network element NE 2 .
- the configuration message KN uses an IP address or a port address of the terminal T as its destination address, which also defines the first packet data transmission PKD 1 from the first network element NE 1 to terminal T.
- a receive function is implemented on the second network element NE 2 which makes it possible to send back the configuration message KN from the second network element NE 2 to the first network element NE 1 via a further second data path DPF 2 within the framework of a second packet data transmission PKD 2 .
- the configuration message KN is transmitted to network element NEx of the second data path DPF 2 , with the second data path DPF 2 including the network elements NE 2 , NE 5 , NE 6 and NE 2 .
- the configuration message KN is assigned by the terminal an IP address or port address of the first network element NE 1 , with which the second packet data transmission PKD 2 from terminal T via the second network element NE 2 and via the second data path DPF 2 to the first network element NE 1 is defined.
- the second packet data transmission PKD 2 is undertaken along the second data path DPF 2 from terminal T via the second network element NE 2 and the network elements NE 5 and NE 6 to the first network element NE 1 .
- the network elements NE 3 to NE 6 receive the respective configuration message KN and evaluate this for initialization and configuration. However in such cases it is also possible for a few network elements—not shown here—to simply forward the configuration message KN.
- the respective data paths are defined using a number of what are referred to as session identities.
- the protocol NLSP is used for transmission of the configuration message KN.
- the Radio Network Controller RNC forms an NSIS Receiver NR and the central network element NEZ an NSIS Initiator NI.
Abstract
Description
- This application is based on and hereby claims priority to PCT Application No. PCT/EP2004/011296 filed on Oct. 8, 2004, the contents of which are hereby incorporated by reference.
- The invention relates to a method for configuring billing processes in network elements of a data path for the transmission of packet data in a communications.
- Packet data services are known which use what is known as “IP Layer 3” of the “Open Systems Interconnection Reference, OSI” model within a communications network for example. This model serves as a reference model of the international Standards Organization ISO for networks in order to define an open communication using interface standards.
- Billing data recording for a data service, for example for a packet data service, is based in this case on an independent and non-synchronized detection by network elements which are used to execute the data service. The network elements involved in the transmission of a data service in such cases each have assigned billing processes which are used for recording billing data. The billing data is collected in network elements provided especially for the purpose in order to create a service-oriented or service-specific billing.
- The network elements involved in billing data recording have a unique correlation identifier to allow them identify all billing data pertaining to a concrete service usage.
- The correlation identifier is entered in the billing data so that billing data can be linked together by a central entity and processed together for billing.
- A central problem of this type of billing is the distribution of the unique correlation identifier to the respective network elements. The network elements involved in executing a service generally operate on different network layers, for example on layers of the OSI model—Layer 2, Layer 3 or Layer 7.
- Additional problems during billing data recording are caused if the network elements are arranged in different areas of the network, for example if they are arranged in a “Packet Switched, PS” domain or in an “IP Multimedia Subsystem, IMS”.
- Furthermore it is possible for the network elements involved in the execution of a packet data service to be separated from each other by technology boundaries. Thus for example some of the network elements can be based on the “Universal Mobile Telecommunication system, UMTS” whereas others can be based on the “Wireless Local Area Network, WLAN”.
- In these outlined cases a mechanism for distribution of the respective correlation identifier must be defined and standardized, which means that rapid introduction of new services involves great expense. Thus for example the known “Multi Media Service, MMS” for prepaid subscribers has for a long time not been able to be provided because the required billing data recording methods are not offered. The method for distribution of the correlation identifiers for billing data recording are thus only able to be implemented at great expense, since billing data is collected in the network elements involved and resulting billing data records must be forwarded to a central entity. The central entity for its part must determine from an incoming flood of data those billing data records which belong together, and needs a great deal of time to evaluate them.
- Methods for billing data recording or methods for configuration of billing processes at the network elements involved are discussed for example by the “Internet Engineering Task Force, IETF” within the framework of the project “Next Steps in Signaling, NSIS”, in which case underlying Internet routing methods are used to find network elements of a data path.
- One possible object of the present invention is to implement a simple and quick-to-execute method for configuration of billing processes at network elements, to enable billing data to be recorded for a packet data service in a communications network.
- The inventor recognized that different routes or data paths are used for the packet data transmission for the routing which is typically to be executed asymmetrically for a packet data service. In general the packet data is transmitted between a terminal, for example a radio communication terminal on one side, and an application host on the other side, in two directions, and thereby over two data paths.
- Since the current routing methods can only address the respective network element of a data path in one direction, a configuration for billing data recording is not possible from the network element side between the two end points—terminal on one side and application host on the other side. Configuration from the terminal side is excluded for reasons of security. A configuration by the application host is not able to be easily implemented for reasons of cost and time.
- These problems are avoided in the proposed method. In accordance with the proposed method, a billing control function which is held in a central network element is used for configuring the network elements of a data path. In such cases this central network element is not a component of the data path, i.e. the packet data transmission in question is not undertaken via the central network element.
- The billing control function forms a configuration message for configuration of the network elements and is started for example when a service is requested. The configuration message is transmitted via the application host as the first network element to the network element of the data path to be configured. Those network elements which are to be configured evaluate the configuration message for an initialization, whereas other network elements of the data path forward the configuration message.
- The “Network Link Services Protocol, NLSP”, known per se, is preferably, but not exclusively used with the communications network to transmit the configuration message together with further signaling messages to the network elements.
- Not the terminal but an upstream network element assigned to the terminal is used as the ingress node for the data path. Accordingly the configuration message is formed by the central network element and not by the application host used as a further ingress node for the data path. These measures guarantee both the security of the billing data recording and also the high processing speed of the application host.
- A central billing control function is implemented with the aid of the method for storage of configuration rules.
- These and other objects and advantages of the present invention will become more apparent and more readily appreciated from the following description of the preferred embodiments, taken in conjunction with the accompanying drawing of which:
-
FIG. 1 shows a method with reference to a communications network, in accordance with one possible embodiment of the invention. - In this diagram the communications network features network elements NE1 to NE6, a central network element NEZ and a terminal T, with a first network element NE1 being embodied as an application host and a second network element NE2 as a Radio Network Controller RNC.
- Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to like elements throughout.
- A billing control function GKF is stored or implemented on the central network element NEZ. For a requested packet data transmission PKD1, PKD2 between the first network element NE1 and the terminal T which is undertaken via the second network element NE2, a configuration message KN is formed by the billing control function GKF, which is used for configuration of the network elements NE3, NE4, NE5 and NE6. The configuration message KN is transmitted to network element NEx of a first data path DPF1, with the first data path DPF1 including network elements NE1, NE3, NE4 and NE2.
- An assigned first packet data transmission PKD1 is undertaken along the first data path DPF1 from first network element NE1 via the network elements NE3 and NE4 and via the second network element NE2 to terminal T, with terminal T being assigned to the second network element NE2.
- The configuration message KN uses an IP address or a port address of the terminal T as its destination address, which also defines the first packet data transmission PKD1 from the first network element NE1 to terminal T.
- A receive function is implemented on the second network element NE2 which makes it possible to send back the configuration message KN from the second network element NE2 to the first network element NE1 via a further second data path DPF2 within the framework of a second packet data transmission PKD2.
- The configuration message KN is transmitted to network element NEx of the second data path DPF2, with the second data path DPF2 including the network elements NE2, NE5, NE6 and NE2.
- For this purpose the configuration message KN is assigned by the terminal an IP address or port address of the first network element NE1, with which the second packet data transmission PKD2 from terminal T via the second network element NE2 and via the second data path DPF2 to the first network element NE1 is defined.
- The second packet data transmission PKD2 is undertaken along the second data path DPF2 from terminal T via the second network element NE2 and the network elements NE5 and NE6 to the first network element NE1.
- In the case depicted here, the network elements NE3 to NE6 receive the respective configuration message KN and evaluate this for initialization and configuration. However in such cases it is also possible for a few network elements—not shown here—to simply forward the configuration message KN.
- Subsequently collected billing data RM is notified back to the central network element NEZ.
- For the case of a number of parallel transmissions, known as sessions, between the first network element NE1 embodied as an application on the one side and the terminal T on the other side, the respective data paths are defined using a number of what are referred to as session identities.
- Advantageously the protocol NLSP is used for transmission of the configuration message KN. In this case, in accordance with the NSIS terminology, the Radio Network Controller RNC forms an NSIS Receiver NR and the central network element NEZ an NSIS Initiator NI.
- The invention has been described in detail with particular reference to preferred embodiments thereof and examples, but it will be understood that variations and modifications can be effected within the spirit and scope of the invention covered by the claims which may include the phrase “at least one of A, B and C” as an alternative expression that means one or more of A, B and C may be used, contrary to the holding in Superguide v. DIRECTV, 69 USPQ2d 1865 (Fed. Cir. 2004).
Claims (17)
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2004/011296 WO2006039934A1 (en) | 2004-10-08 | 2004-10-08 | Method for configuring billing processes in network elements |
Publications (2)
Publication Number | Publication Date |
---|---|
US20090055298A1 true US20090055298A1 (en) | 2009-02-26 |
US9397843B2 US9397843B2 (en) | 2016-07-19 |
Family
ID=34959006
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/664,941 Active 2032-11-17 US9397843B2 (en) | 2004-10-08 | 2004-10-08 | Method for configuring billing processes in network elements |
Country Status (10)
Country | Link |
---|---|
US (1) | US9397843B2 (en) |
EP (1) | EP1807969B1 (en) |
JP (1) | JP4399500B2 (en) |
KR (1) | KR101099034B1 (en) |
CN (1) | CN101124776B (en) |
AT (1) | ATE429101T1 (en) |
BR (1) | BRPI0419089A (en) |
CA (1) | CA2583288C (en) |
DE (1) | DE502004009374D1 (en) |
WO (1) | WO2006039934A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11392911B2 (en) * | 2018-04-06 | 2022-07-19 | Orange | Method for processing a transaction between a source terminal and a destination terminal, corresponding banking services system, terminal and computer program |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013048440A1 (en) * | 2011-09-30 | 2013-04-04 | Siemens Aktiengesellschaft | Tool and method for dynamic configuration and implementation of device firmware utilizing defined components |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020188562A1 (en) * | 2001-06-07 | 2002-12-12 | Yoichiro Igarashi | Billing system, and device constituting same |
US20040025018A1 (en) * | 2002-01-23 | 2004-02-05 | Haas Zygmunt J. | Secure end-to-end communication in mobile ad hoc networks |
US6697103B1 (en) * | 1998-03-19 | 2004-02-24 | Dennis Sunga Fernandez | Integrated network for monitoring remote objects |
US20040090955A1 (en) * | 2002-11-13 | 2004-05-13 | International Business Machines Corporation | System and method for routing IP datagrams |
US20050039212A1 (en) * | 2001-12-27 | 2005-02-17 | Paul Baran | Method and apparatus for constructing a set-top box to protect cryptographic capabilities |
US6952836B1 (en) * | 2000-09-26 | 2005-10-04 | At&T Corp. | Method and apparatus for managing the provisioning of client devices connected to an interactive TV network |
US20070201702A1 (en) * | 1992-12-09 | 2007-08-30 | Discovery Communications, Inc. | Electronic book security and copyright protection system |
US20070280235A1 (en) * | 2006-06-01 | 2007-12-06 | Qualcomm Incorporated | System and method for acquisition and delivery of services to devices in a wireless multicast communication system |
US20080049623A1 (en) * | 2006-08-22 | 2008-02-28 | Chaoxin Charles Qiu | Methods and apparatus to provide service assurance for communication networks |
US20080183641A1 (en) * | 2007-01-25 | 2008-07-31 | Chang Bin Tang | Generalized application virtualization method for business use on the web and the mini server using this method |
US20090319596A1 (en) * | 2008-06-18 | 2009-12-24 | Time Warner Cable Inc | System and method for billing system interface failover resolution |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FI113224B (en) * | 1996-11-11 | 2004-03-15 | Nokia Corp | Implementation of invoicing in a data communication system |
KR100393424B1 (en) | 2001-05-14 | 2003-08-02 | 이삼일 | Charging system and method used sniffing technology for network communication |
DE10146891C2 (en) * | 2001-09-24 | 2003-08-14 | Infineon Technologies Ag | Method for transmitting charge determination signals via a data transmission path and device for voltage level generation |
-
2004
- 2004-10-08 EP EP04790228A patent/EP1807969B1/en not_active Not-in-force
- 2004-10-08 CA CA2583288A patent/CA2583288C/en not_active Expired - Fee Related
- 2004-10-08 JP JP2007535026A patent/JP4399500B2/en not_active Expired - Fee Related
- 2004-10-08 WO PCT/EP2004/011296 patent/WO2006039934A1/en active Application Filing
- 2004-10-08 DE DE502004009374T patent/DE502004009374D1/en active Active
- 2004-10-08 KR KR1020077006709A patent/KR101099034B1/en not_active IP Right Cessation
- 2004-10-08 US US11/664,941 patent/US9397843B2/en active Active
- 2004-10-08 AT AT04790228T patent/ATE429101T1/en not_active IP Right Cessation
- 2004-10-08 CN CN2004800441969A patent/CN101124776B/en not_active Expired - Fee Related
- 2004-10-08 BR BRPI0419089-0A patent/BRPI0419089A/en not_active IP Right Cessation
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070201702A1 (en) * | 1992-12-09 | 2007-08-30 | Discovery Communications, Inc. | Electronic book security and copyright protection system |
US6697103B1 (en) * | 1998-03-19 | 2004-02-24 | Dennis Sunga Fernandez | Integrated network for monitoring remote objects |
US6952836B1 (en) * | 2000-09-26 | 2005-10-04 | At&T Corp. | Method and apparatus for managing the provisioning of client devices connected to an interactive TV network |
US20020188562A1 (en) * | 2001-06-07 | 2002-12-12 | Yoichiro Igarashi | Billing system, and device constituting same |
US20050039212A1 (en) * | 2001-12-27 | 2005-02-17 | Paul Baran | Method and apparatus for constructing a set-top box to protect cryptographic capabilities |
US20040025018A1 (en) * | 2002-01-23 | 2004-02-05 | Haas Zygmunt J. | Secure end-to-end communication in mobile ad hoc networks |
US20040090955A1 (en) * | 2002-11-13 | 2004-05-13 | International Business Machines Corporation | System and method for routing IP datagrams |
US20070280235A1 (en) * | 2006-06-01 | 2007-12-06 | Qualcomm Incorporated | System and method for acquisition and delivery of services to devices in a wireless multicast communication system |
US20080049623A1 (en) * | 2006-08-22 | 2008-02-28 | Chaoxin Charles Qiu | Methods and apparatus to provide service assurance for communication networks |
US20080183641A1 (en) * | 2007-01-25 | 2008-07-31 | Chang Bin Tang | Generalized application virtualization method for business use on the web and the mini server using this method |
US20090319596A1 (en) * | 2008-06-18 | 2009-12-24 | Time Warner Cable Inc | System and method for billing system interface failover resolution |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11392911B2 (en) * | 2018-04-06 | 2022-07-19 | Orange | Method for processing a transaction between a source terminal and a destination terminal, corresponding banking services system, terminal and computer program |
Also Published As
Publication number | Publication date |
---|---|
BRPI0419089A (en) | 2007-12-18 |
US9397843B2 (en) | 2016-07-19 |
EP1807969B1 (en) | 2009-04-15 |
KR20070072498A (en) | 2007-07-04 |
CN101124776B (en) | 2010-10-06 |
EP1807969A1 (en) | 2007-07-18 |
WO2006039934A1 (en) | 2006-04-20 |
CA2583288A1 (en) | 2006-04-20 |
KR101099034B1 (en) | 2011-12-26 |
JP2008516485A (en) | 2008-05-15 |
ATE429101T1 (en) | 2009-05-15 |
CN101124776A (en) | 2008-02-13 |
DE502004009374D1 (en) | 2009-05-28 |
JP4399500B2 (en) | 2010-01-13 |
CA2583288C (en) | 2012-08-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Hancock et al. | Next steps in signaling (NSIS): Framework | |
US7760640B2 (en) | Electronic message delivery system including a network device | |
EP1564930B1 (en) | Method of transporting a multipoint stream in a local area network and device for connection implementing the method | |
EP3934183B1 (en) | Service function chain sfc-based communication methods, and apparatuses | |
US8081611B2 (en) | Mobility label-based networks | |
CN109218201A (en) | A kind of method, controller and network equipment generating forwarding-table item | |
US20070286185A1 (en) | Control of Mobile Packet Streams | |
CN109644190A (en) | Multipath UDP communication means between two terminals | |
US20220182321A1 (en) | Apparatus, method and computer program for group communication | |
US7567562B2 (en) | Content based secure rendezvous chaotic routing system for ultra high speed mobile communications in ad hoc network environment | |
CN101563949A (en) | Management of seamless handover between different communication systems in an IP dual-mode terminal | |
TW200401541A (en) | Flow-based selective reverse tunneling in wireless local area network (WLAN)-cellular systems | |
EP1665598A2 (en) | Method and apparatus for managing multicast delivery to mobile devices involving a plurality of different networks | |
CN111869248B (en) | Method for managing traffic flows through an IPX network, network routing node | |
Rico et al. | A survey of end-to-end solutions for reliable low-latency communications in 5G networks | |
Daniel Wong et al. | Simultaneous mobility: analytical framework, theorems and solutions | |
Yang et al. | SIP multicast-based mobile quality-of-service support over heterogeneous IP multimedia subsystems | |
US7536187B2 (en) | Supporting communication sessions at a mobile node | |
US9397843B2 (en) | Method for configuring billing processes in network elements | |
US9426186B2 (en) | Methods and systems for load balancing call sessions over a dual ring internet protocol (IP) network | |
US8027343B2 (en) | Communication system, computer, and method for determining a communication protocol to be used in a communication system | |
Karl et al. | Transparent multi-hop protocol termination | |
JP4431173B2 (en) | Source-specific multicast routing method | |
CN112187551A (en) | Software-defined wide area network-based edge equipment capability benchmark test method and device | |
US20030126290A1 (en) | Context filter in a mobile node |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SIEMENS AKTIENGESELLSCHAFT;REEL/FRAME:020431/0830 Effective date: 20071213 Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG,GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SIEMENS AKTIENGESELLSCHAFT;REEL/FRAME:020431/0830 Effective date: 20071213 |
|
AS | Assignment |
Owner name: SIEMENS AKTIENGESELLSCHAFT, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FOELL, UWE;REEL/FRAME:020896/0083 Effective date: 20070601 |
|
AS | Assignment |
Owner name: NOKIA SOLUTIONS AND NETWORKS GMBH & CO. KG, GERMANY Free format text: CHANGE OF NAME;ASSIGNOR:NOKIA SIEMENS NETWORKS GMBH & CO. KG;REEL/FRAME:034294/0675 Effective date: 20130912 Owner name: NOKIA SOLUTIONS AND NETWORKS GMBH & CO. KG, GERMAN Free format text: CHANGE OF NAME;ASSIGNOR:NOKIA SIEMENS NETWORKS GMBH & CO. KG;REEL/FRAME:034294/0675 Effective date: 20130912 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |