We are seeking some guidance on a requirement to block the calling from A party (Any number ) to B party (OpertaorsMSISDN ) based on the identified list of MSISDN on different time schedule. We would like to know which is the best system to fulfil this requirement (eg converge billing system or HLR etc..)Regards
These sort of questions are great to illustrate the interactions between domains.In the Product domain we could have Product Offerings (PO) which allow, or do not allow, subscribers to call other operator networks, presumably with different Prices (POP). You could control the set of Operators with Characteristics defined in a Product Specification allowing the PO designer flexibility in creating offers. This would be a Product Catalog driven solution as demonstrated in the 5G Chargers Catalyst project.In the Service domain we could control the set of Operators with Characteristics defined in a Service Specification. This is a more typical approach than above. Either way a Service Orchestration system shall have to arrange for provisioning towards whatever systems implement the operator barring features. By modeling as Service Characteristics however we can manage different technology domain implementations consistently.In the Resource domain we manage the network functions which implement features such as required here. You will find that Operator Determined Barring (3GPP TS 22.041) is part of subscriber data held in an HLR, HSS, UDM and transferred to the service nodes where barring occurs. Subscriber data may be represented in Resource Specifications and captured in Resource Inventory.So we could manage this feature using Product, Service and Resource APIs in ODA.
As colleagues already suggested, answer is heavily dependant on network configuration you're talking about and some more detail on requirements.
The main question - is your requirements on a "per subscriber" base (for some given any "A" number to block "a given set of Operators" on "given schedule")
or it is "per network" - For every calling subscriber to block this set.
If first, than you need to think about implementing this Service in either way. - as Service of blocking calls or you may have it as a service for allowing calls - depending on
number of your subscribers using this feature. As @Vance Shipley suggested - it could be defined on a service or level.
The service itself implementation and provisioning (or fulfilment) scheme itself depends on the network architecture.
in typical 2G/3G SS7 - based environment I would recommend to implement the feature using OCS (Online charging system) SS7 interface - assuming 3GPP CAP is available and users are subscribed. If not - you may choose a way to implement custom Operator Defined Barring (ODB) with help of your MSC/VLR vendor.
in 4/5G IMS-based environment the same could be implemented using Application server (ISC) interface. Once again, depending on capabilities of your network by reusing existing AS (or SCIM) or building an additional one.