WO2015166102A1 - Architecture de configuration et de facturation - Google Patents

Architecture de configuration et de facturation Download PDF

Info

Publication number
WO2015166102A1
WO2015166102A1 PCT/EP2015/059626 EP2015059626W WO2015166102A1 WO 2015166102 A1 WO2015166102 A1 WO 2015166102A1 EP 2015059626 W EP2015059626 W EP 2015059626W WO 2015166102 A1 WO2015166102 A1 WO 2015166102A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
service provider
cellular network
service
provider network
Prior art date
Application number
PCT/EP2015/059626
Other languages
English (en)
Inventor
Daniel AZZOPARDI
Original Assignee
Vodafone Ip Licensing Limited
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from GB201407848A external-priority patent/GB201407848D0/en
Priority claimed from GB201408770A external-priority patent/GB201408770D0/en
Application filed by Vodafone Ip Licensing Limited filed Critical Vodafone Ip Licensing Limited
Publication of WO2015166102A1 publication Critical patent/WO2015166102A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • 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/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
    • 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/51—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for resellers, retailers or service providers
    • 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/70—Administration or customization aspects; Counter-checking correct charges
    • 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/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/715—Activating new subscriber or card
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems

Definitions

  • External service providers may be granted access to some parts of a cellular network in order to provide their service.
  • subscription provisioning, activation and billing functionalities can be provided by interfacing one or more cellular network entities with external entities (such as servers) managed by the service provider.
  • a service provider can be a Mobile Virtual Network Operator (MVNO), a corporate network service or an emergency communications service provider.
  • MVNO Mobile Virtual Network Operator
  • the cellular network entities of interest may be part of the core network, the Operations and Management (O&M) system or a combination of such entities.
  • O&M Operations and Management
  • an MVNO can provision a standard 2G (GSM) or 3G (UMTS) subscription. This can provide standardised subscriptions for circuit-switched (such as voice) and/or packet-switched (data) services.
  • GSM 2G
  • UMTS 3G
  • a mobile terminal is provisioned at a cellular network so that the mobile terminal can receive a communications service from a service provider network through the cellular network.
  • the service provider network is logically separate from the cellular network (and optionally physically separate and/or separately controlled).
  • a provisioning message is communicated (typically, through an interface) from the service provider network to a provisioning system of the cellular network.
  • the provisioning message causes direct (and/or immediate) adjustment of one or more service parameters of a subscription for the mobile terminal in the cellular network.
  • Direct adjustment allows the provisioning (adjustment of one or more service parameters of an existing subscription, also called re-provisioning in this context) of the mobile terminal to be effected without complex interactions or negotiation and preferably in an immediate way.
  • This adjustment may be immediate in that the cellular network receives the instruction immediately, especially directly to the core network.
  • the instruction is not necessarily effected immediately (although in embodiments, it can be), depending on the core network architecture. This may be especially advantageous for critical communications services, such as emergency services.
  • the communicating may be sending (that is from the service provider network) and/or receiving (that is, at the provisioning system of the cellular network).
  • the one or more service parameters of the subscription may be adjusted in correspondence with (to match or to change in one or more of the same: direction, or an opposite direction; proportion; and absolute magnitude) one or more parameters of the service set at the service provider network.
  • the provisioning message may provide information to allow this adjustment.
  • the one or more service parameters comprise one or more of: a data rate or bandwidth; a data volume allowance; a priority; and a Quality of Service (QoS) parameter.
  • QoS Quality of Service
  • These parameters may allow effective re-provisioning of the subscription within the cellular network.
  • the service provider wishes to provide a service with one or more of: high QoS, high priority, high volume, high speed
  • the cellular network may be adapted quickly to provide this service.
  • the cellular network beneficially provides network connectivity, based on at least one lower layer of a networking protocol stack, comprising one or more of: a physical layer; a link layer; a network layer; a transport layer; and a session layer.
  • the service provider network may provide a service based on at least one higher layer of a networking protocol stack, comprising one or more of: a session layer; a presentation layer; and an application layer.
  • a service provider may effect service-level adjustments to meet user requirements or demands and also effect connectivity-level adjustments by direct interface with the cellular network.
  • the communicating is through an integration gateway in the cellular network, which may be a network entity used for provisioning, but
  • the integration gateway may provide an XML data over HTTPS protocol interface, which can allow communication of the provisioning message. This may particularly provide flexibility and may not require significant processing resource.
  • the step of communicating comprises communicating between a priority management function in the service provider network and the integration gateway.
  • the integration gateway may interface with a policy database for configuring or controlling the core network to allow priority settings for one or more subscribers to be set by the service provider network. This may allow the service provider to effect direct and/or instantaneous changes to the service parameters in the core network of the cellular network.
  • the step of interfacing may comprise communication between an Application
  • the step of interfacing comprises interfacing of billing entities between one or both of: an Enterprise Data Warehouse (EDW); and a billing function in the cellular network and a billing / finance function in the service provider network.
  • the interfacing of billing entities is provided through a Managed File Transfer (MFT) system.
  • MFT Managed File Transfer
  • the step of interfacing comprises remotely accessing one or more entities of the cellular network from a remote access function in the service provider network.
  • the one or more entities of the cellular network may comprise a Customer Relationship Management (CRM) / Billing function for activating subscriptions by applying a price plan on a billing system of the cellular network.
  • CRM Customer Relationship Management
  • Figure 1 shows a schematic diagram of a network architecture in accordance with a first embodiment
  • Figure 2 shows a schematic diagram of a network architecture in accordance with a second embodiment
  • Figure 3 shows a schematic diagram of a network architecture in accordance with a third embodiment
  • Figure 4 shows a schematic diagram of a network architecture in accordance with a modified version of the embodiment of Figure 1 ;
  • Figure 5 shows a schematic diagram of a network architecture in accordance with a modified version of the embodiment of Figure 2.
  • FIG. 1 there is shown a schematic diagram of a network architecture in accordance with a first embodiment.
  • the network architecture is divided into two parts: a cellular network 10; and a service provider network 20.
  • This division is a logical split and not necessarily a physical split.
  • the cellular network 10 and a service provider network 20 are managed separately, although this need not be the case.
  • the cellular network 10 provides network connectivity, which may include lower layers of the networking protocol stack. For example, this may include one or more of: a physical layer; a link layer; a network layer; and a transport layer. Optionally, it may also include a session layer.
  • the network connectivity typically involves control-plane traffic. User-plane traffic is normally transparent to the service provider network 20.
  • the network connectivity provided by the cellular network 10 may allow the service provider network 20 to provide a service.
  • the service may be considered at the higher layers of the protocol stack, which may comprise one or more of: a session layer; a presentation layer; and an application layer.
  • the service may comprise one or more of: voice traffic; video traffic; other types of conversational-class traffic; streaming traffic; interactive class (browsing-type) data traffic; and background-class traffic.
  • the service typically comprises the user-plane traffic.
  • the service may be dependent on at least one Quality of Service (QoS) parameter, which may be set in accordance with the type of service. Adjustment to the QoS parameter or another service parameter may be desirable, for example based on the service requirements to change data rate, priority or other characteristic.
  • QoS Quality of Service
  • Some systems integrate the service provider network 10 and cellular network 20 completely, such that the distinction between the service (higher protocol stack layers) and the network connectivity (lower protocol stack layers) cannot be distinguished.
  • the service and the network connectivity are distinguishable and are preferably provided using separate network entities, as noted above and detailed (in the form of some examples) below.
  • the cellular network 10 comprises: a Radio Access Network (RAN) 120; and a core network 130; a Charging Data Record (CDR) mediation function 140; and a billing function 150.
  • RAN Radio Access Network
  • CDR Charging Data Record
  • the configuration of the RAN 120 is shown as a conventional E-UTRAN Long Term Evolution (LTE) arrangement.
  • LTE Long Term Evolution
  • the configuration of the core network 130 is also shown as a conventional System Architecture Evolution (SAE) Long Term Evolution (LTE) arrangement, comprising: a Mobility Management Entity (MME); a Service GPRS Support Node (SGSN); a Serving Gateway; a Packet Data Network (PDN) Gateway; a Home Subscriber Server (HSS); a Policy and Charging Rules Function (PCRF); and other operator IP services, which may include a Voice over LTE (VoLTE) Application Server (AS) 160.
  • SAE System Architecture Evolution
  • LTE Long Term Evolution
  • MME Mobility Management Entity
  • SGSN Service GPRS Support Node
  • PDN Packet Data Network
  • HSS Home Subscriber Server
  • PCRF Policy and Charging Rules Function
  • other operator IP services which may include a Voice over LTE (VoLTE) Application Server (AS) 160.
  • VoIP Voice over LTE
  • AS Application Server
  • the Serving Gateway and PDN Gateway generate data service CDRs 141 for data services.
  • the VoLTE AS 160 generates voice CDRs 142. These are provided to the CDR mediation function 140.
  • ASN1 normalised CDRs 143 are provided to
  • EDW Enterprise Data Warehouse
  • the service provider network 20 comprises: a provisioning function 200; a billing / finance function 210; and a service AS 220.
  • the provisioning function 200 is used to provision a new network subscriber (user) and may be a software system for receiving and storing the subscriber details. This interfaces with the service AS 220 for service provisioning.
  • An interface is provided between the cellular network 10 and the service provider network 20.
  • This interface uses an integration gateway 100.
  • the integration gateway links to a cellular network provisioning function 1 10.
  • the cellular network provisioning function 1 10 then effects provisioning of subscriptions, services or both.
  • the service provider network 20 provides input, which may comprise one or more requests, to the cellular network 10 and the provisioning is based on these.
  • This provisioning is achieved through interfaces with one or more entities of the core network 130, such as the HSS, PCRF and AS 160.
  • the AS 160 can then provide a VoLTE service in this way.
  • the service provider network 20 uses the provisioning function 200 to provide an interface 201 with the cellular network 10.
  • this interface provides low latency and/or high security. This may be desirable for efficient and effective service provision.
  • interface 201 provides XML data over HTTPS protocol to the integration gateway 100. Other protocols or types of interface may be used instead.
  • the AS 160 may interface with the service AS 220. This may allow specific services to be set up or configured. Such services may be conventional in the cellular network 10 or specific to the service provided by the service provider network 20.
  • the billing function 150 For charging purposes, the billing function 150 performs billing at a first rating (typically, a wholesale rating).
  • the CDRs are provided over billing interface 151 to the billing / finance function 210 in the service provider network 20.
  • the EDW 145 can provide reports 146 to the service provider network 20.
  • this architecture can be reduced to a cellular network having a core network (preferably comprising a HSS or equivalent, a PCRF or equivalent, a service AS or a combination of such entities); an external service provider system configured to provide a service to a service provider subscriber over the cellular network; and an integration gateway system, configured to interface between the external service provider system and the cellular network, in order to provision and/or configure a subscription, a service or a combination thereof within the core network.
  • a core network preferably comprising a HSS or equivalent, a PCRF or equivalent, a service AS or a combination of such entities
  • an external service provider system configured to provide a service to a service provider subscriber over the cellular network
  • an integration gateway system configured to interface between the external service provider system and the cellular network, in order to provision and/or configure a subscription, a service or a combination thereof within the core network.
  • the integration gateway system may interface with a provisioning system of the cellular network (which may be a part of a O&M system of the cellular network) to effect provisioning and/or configuration.
  • the provisioning system may interface with the core network.
  • the integration gateway system may be configured to interface with an Application Server in order to provide a voice over packet-switched (such as IP or LTE) service. Configuration aspects may be discussed below.
  • the integration gateway system may be configured to effect adjustment of one or more service parameters of a subscription.
  • the service parameters may comprise one or more of: data rate or bandwidth; data volume allowance; priority; or one or more other QoS parameter. A method of operation of this architecture may also be understood.
  • FIG. 2 there is shown a schematic diagram of a network architecture in accordance with a second embodiment. Where the same elements or entities are shown as in a previous drawing, identical reference numerals have been used.
  • the billing function 150 of Figure 1 is replaced with a cellular network Customer Relationship Management (CRM) / Billing function 155. This generates billing at a rating and preferably in a format suitable for the service provider to use directly.
  • CRM Customer Relationship Management
  • the service provider network 20 comprises: a remote access function 205; and the billing / finance function 210.
  • the remote access function 205 is configured to allow remote access into one or more entities of the cellular network 10, particularly the CRM / Billing function 155 to allow provisioning.
  • the remote interfacing may be web-based, for example using a HTTP or HTTPS protocol.
  • the CRM / Billing function 155 activates subscriptions by applying the correct price plan on the billing system.
  • the billing system then triggers off a command to the provisioning function 1 10 to activate the subscription on the cellular network 10.
  • the cellular network now retains significant technical functionality in respect of the subscription and/or service provision and charging aspects.
  • the service provider network 20 simply accesses these functionalities remotely, without the need for dedicated network entities to provide inputs to these functionalities. Complex integration of the cellular network 10 and the service provider network 20 and the layers that they each control is not required. This solution is therefore significantly simpler. Control and security of the technical charging reporting system is also improved in this way.
  • Provisioning and configuring of services at the cellular network is also envisioned.
  • the service provider network 20 adjusts one or more service or QoS parameters. As an example, this type of adjustment may be of benefit to emergency service-type communication services.
  • a user may demand an increase in data rate, for example in order to go from a voice-based call to share realtime video in addition. This may be useful for immediate response to an emergency and allow the other party (or parties) in the call to see the situation for information and possibly to advise.
  • a similar scenario may exist when a high-priority service is demanded, for example to send an urgent message by voice and/or data.
  • the service provider network 20 can adjust the service parameters accordingly (at the higher layers of the protocol stack) to meet the new QoS
  • the service provider network 20 may inform the cellular network 10 of the service requirement or parameter changes.
  • the cellular network 10 is then configured to respond accordingly.
  • FIG. 3 there is shown a schematic diagram of a network architecture in accordance with a third embodiment.
  • This embodiment is intended to provide management of one or more of: priority; data rate; and special instantaneous services (for example proximity-based or group / multicast services).
  • Some of the functionality in the cellular network 10 for charging has therefore been omitted from the drawing.
  • some or all of the features of this embodiment may optionally be combined with either of the two earlier-described embodiments.
  • a priority management function 206 is provided in the service provider network 20. This interfaces with the service provider AS 220 for service provisioning. The priority management function 206 also interfaces with the integration gateway 100 through an interface 202. As discussed above, the priority management function 206 may provide XML data over HTTPS protocol to the integration gateway 100 over the interface 202.
  • the cellular network 10 comprises a policy database 170, which interfaces with the integration gateway 100.
  • the policy database 170 is able to configure or control parts of the core network 130, especially the PCRF. This allows priority settings for individual or groups of subscribers to be set by the service provider network 20. For instance, a mechanism may trigger an action from the priority management function 206 to the policy database 170.
  • the service provider 20 may be provided with remote access to one or more entities of the cellular network 10. This may be used to configure a subscription, a service or a combination thereof within the core network, as discussed herein. This may be achieved whilst still maintaining the split of control between service and network connectivity.
  • the cellular network 10 and the service provider network 20 can remain logically (and preferably physically) distinct and may be controlled
  • a Managed File Transfer (MFT) system can optionally be additionally provided. This can provide a further interface between the cellular network 10 and the service provider network 20.
  • MFT Managed File Transfer
  • all billing records (whether rated by the billing systems or not) can be transferred using the MFT.
  • the MFT can further improve security of the interface between the two networks.
  • the number of interface points between the cellular network 10 and the service provider network 20 can be reduced using the MFT.
  • FIG 4 there is shown a schematic diagram of such a network architecture in accordance with a modified version of the embodiment of Figure 1 .
  • Much of the architecture is the same as shown in Figure 1 and where the same elements or entities are shown as in this drawing, identical reference numerals have been used.
  • An MFT 310 is provided for interfacing between the cellular network 10 and the service provider network 20.
  • the MFT 310 provides a central interface for the EDW 145 and billing function 150 in the cellular network 10 with the billing / finance function 210 in the service provider network 20 and to provide reports 146 to the service provider network 20.
  • FIG. 5 there is shown a schematic diagram of a network architecture in accordance with a modified version of the embodiment of Figure 2.
  • An MFT 31 1 is provided for interfacing between the cellular network 10 and the service provider network 20.
  • the MFT 31 1 provides a central interface for the EDW 145 and CRM / Billing function 155 in the cellular network 10 with the billing / finance function 210 in the service provider network 20 and to provide reports 146 to the service provider network 20.

Abstract

Un terminal mobile est configuré à un réseau cellulaire de sorte à recevoir un service de communications d'un réseau de fournisseur de services via le réseau cellulaire. Le réseau de fournisseur de services est séparé logiquement du réseau cellulaire. Un message de configuration est transmis, du réseau de fournisseur de services à un système de configuration du réseau cellulaire. Le message de configuration commande l'ajustement direct d'un ou plusieurs paramètres de service d'un abonnement du terminal mobile dans le réseau cellulaire.
PCT/EP2015/059626 2014-05-02 2015-05-01 Architecture de configuration et de facturation WO2015166102A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
GB201407848A GB201407848D0 (en) 2014-05-02 2014-05-02 Architecture for provisioning and billing
GB1407848.9 2014-05-02
GB1408770.4 2014-05-16
GB201408770A GB201408770D0 (en) 2014-05-16 2014-05-16 Architecture for provisioning and billing

Publications (1)

Publication Number Publication Date
WO2015166102A1 true WO2015166102A1 (fr) 2015-11-05

Family

ID=53055032

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2015/059626 WO2015166102A1 (fr) 2014-05-02 2015-05-01 Architecture de configuration et de facturation

Country Status (2)

Country Link
GB (1) GB2527913B (fr)
WO (1) WO2015166102A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002073944A1 (fr) * 2001-01-05 2002-09-19 Evoice, Inc. Approvisionnement automatique de services telephoniques
WO2003024139A2 (fr) * 2001-09-10 2003-03-20 Research In Motion Limited Systeme et procede d'auto-prestation en temps reel pour dispositif de communication mobile
US20040137890A1 (en) * 2002-11-01 2004-07-15 At&T Wireless Services, Inc. General purpose automated activation and provisioning technologies
EP1705872A1 (fr) * 2005-03-21 2006-09-27 Bitfone Corporation Dispositif client mobile et système supportant la gestion à distance de dispositif
US20070178895A1 (en) * 2006-01-31 2007-08-02 Nokia Corporation Method, network entity, system, mobile device and computer program product for automatic provisioning of a service

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2495639C (fr) * 2002-08-16 2011-03-08 Research In Motion Limited Systeme et procede de declenchement d'un evenement de fourniture
US7274943B2 (en) * 2003-01-31 2007-09-25 Nokia Corporation Service subscription in a communication system
CN105493525B (zh) * 2013-07-25 2019-05-07 康维达无线有限责任公司 服务层南向接口和服务质量
GB2525195A (en) * 2014-04-15 2015-10-21 Vodafone Ip Licensing Ltd Routing scheme switching

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002073944A1 (fr) * 2001-01-05 2002-09-19 Evoice, Inc. Approvisionnement automatique de services telephoniques
WO2003024139A2 (fr) * 2001-09-10 2003-03-20 Research In Motion Limited Systeme et procede d'auto-prestation en temps reel pour dispositif de communication mobile
US20040137890A1 (en) * 2002-11-01 2004-07-15 At&T Wireless Services, Inc. General purpose automated activation and provisioning technologies
EP1705872A1 (fr) * 2005-03-21 2006-09-27 Bitfone Corporation Dispositif client mobile et système supportant la gestion à distance de dispositif
US20070178895A1 (en) * 2006-01-31 2007-08-02 Nokia Corporation Method, network entity, system, mobile device and computer program product for automatic provisioning of a service

Also Published As

Publication number Publication date
GB201507577D0 (en) 2015-06-17
GB2527913B (en) 2020-05-20
GB2527913A (en) 2016-01-06

Similar Documents

Publication Publication Date Title
US11005765B2 (en) System and method for managing and distributing packet flow descriptions in a telecommunications network
US9026100B2 (en) Policy and charging control method, network entities, communication system and computer program therefor
US10863387B2 (en) System and method for orchestrating policy in a mobile environment
US8989047B2 (en) Rules system versions
EP2693777B1 (fr) Système et procédé pour commander des opérations de déclenchement avancé dans un réseau de télécommunication
US8813168B2 (en) Methods, systems, and computer readable media for providing nested policy configuration in a communications network
US8640188B2 (en) Methods, systems, and computer readable media for providing group policy configuration in a communications network using a fake user
KR102378846B1 (ko) 전자 통신 디바이스의 정책 규제를 위한 방법 및 장치
EP3580964A1 (fr) Sélection de tranche de réseau dans des réseaux de télécommunication sans fil
EP2898653B1 (fr) Procédé et noeud pour controler des ressources pour un service multimédia, ainsi que système et programme informatique correspondants
US10470084B2 (en) Service processing method, PCRF, and service processing system
WO2015033580A1 (fr) Dispositif de communications, dispositif de commande, procédé de communications, procédé de commande et programme associé
WO2020155048A1 (fr) Fonction de désactivation de données de commutateur de paquets (ps) déclenchée dans un réseau
JP2014155096A (ja) 通信ポリシルール動的変更システムおよび通信ポリシルールの動的変更方法
EP3101926B1 (fr) Procédé de gestion de facturation, noeud de commande de réseau centralisé et noeud de fonction
WO2015033579A1 (fr) Dispositif de communications, dispositif de commande, système de communications, procédé de communications, procédé de commande et programme associé
WO2015166102A1 (fr) Architecture de configuration et de facturation
US10594499B1 (en) Default data session for a wireless communication network
US9832129B1 (en) Reducing reauthorization request messages in communications networks

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15720961

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15720961

Country of ref document: EP

Kind code of ref document: A1