For your use case of fetching Broadband session history details from a RADIUS server and translating it into a TMF API, it's important to distinguish between the types of data and objectives each TMF API supports:
Key Differences Between TMF 677 (Usage Consumption) and TMF 635 (Usage Management):
1. TMF 677 - Usage Consumption API:
- This API is primarily focused on usage consumption against a quota or bucket, typically used for things like data consumption limits (e.g., 3GB out of 5GB).
- It is more aligned with quota management scenarios (such as prepaid/postpaid consumption, remaining balance) rather than detailed session-level data.
- If the primary requirement of the use case is to track how much data a subscriber has consumed out of a given allowance, this API would fit.
2. TMF 635 - Usage Management API:
- This API is broader and more generic, focusing on retrieving detailed usage records.
- It is suitable for pulling detailed session/connection information, such as start/end times, session duration, data volumes (upstream/downstream), IP addresses, circuit IDs, and other static data.
- It is ideal for cases where you need a complete history of network usage sessions, such as in your scenario involving session history details from a RADIUS server.
- TMF 635 is generally used when detailed **usage reporting** is required, without linking the data to a consumption quota or bucket.
Specific to Your Broadband Session History Use Case:
Your use case involves fetching detailed **Broadband session history details**, which includes:
- Session date/time
- Session length
- Upstream/Downstream bytes
- Static details like IP address, Circuit ID, etc.
Since the goal is to get session-level details and static information that describe each individual broadband session, TMF 635 (Usage Management API) is the better fit for your scenario. It allows you to fetch detailed usage records without being constrained by consumption tracking as in TMF 677.
Why TMF 635 Is the Right Fit:
- Granular session data: TMF 635 provides more flexibility in terms of getting detailed information like session start/end times, data volumes, and other session-specific attributes.
- Static info support: It supports the retrieval of static data like IP addresses and Circuit IDs, which are important in broadband sessions but not a part of usage consumption models (TMF 677).
- Not linked to quotas: Since you're more focused on historical session details and not on consumption tracking against a quota, TMF 635 aligns better with your needs.
### Conclusion:
For fetching Broadband session history details from a RADIUS server, which includes information like session times, data volumes (upstream/downstream), IP addresses, Circuit IDs, etc., TMF 635 - Usage Management API is the most appropriate choice. TMF 677 (Usage Consumption) is more relevant to tracking data consumption within predefined quotas and doesn't offer the detailed session-level granularity you're looking for.
If you need to integrate this with middleware for the translation of RADIUS data into TMF API responses, TMF 635 will offer the flexibility and structure needed to represent broadband session details effectively.
Kind regards,
Evgenii
------------------------------
Evgenii Kozinchenko
TO BE VERIFIED
------------------------------