Right, 29.522 is the Service Based Interface (SBI) used in 5G Core.
You mention TMF640 Service Activation and Configuration API however a better match here would be TMF664 Resource Function Activation and Configuration API as SBI is dealing with Resource Domain entities. The 3GPP uses the term "Communications Service" for what we have in the Service Domain (e.g. eMBB, URLLC). It's a constant source of confusion, "Network Services" (e.g. VNF Forwarding Graph, Network Slice) are Resource Domain entities best modelled as Resource Function. You are probably interested in the UDR SBI where subscription data would be simple Logical Resources.
You might want to expose a northbound TMF640 from a Service Orchestrator and use TMF664/TMF702/TMF639 southbound from it to a Resource Orchestrator which uses SBIs on it's southbound.
------------------------------
Vance Shipley
SigScale
------------------------------
Original Message:
Sent: May 15, 2020 01:49
From: Chio Chuan Ooi
Subject: mapping 3GPP to TMF640 activation
Hi Vance,
I looking at the TS29.522, 5G API.
Would you mind to share what is the major challenge for the mapping?
Thanks.
------------------------------
Chio Chuan Ooi
SingTel Optus
------------------------------
Original Message:
Sent: May 11, 2020 13:58
From: Vance Shipley
Subject: mapping 3GPP to TMF640 activation
Chio,
I've done quite a bit of this sort of mapping. It's hard to provide any specific advice without knowing which specifications you are working with. The 3GPP TS 29 series covers 3G, 4G and 5G. Is it the 5G Service Based Interface (SBI) APIs you are targeting?
------------------------------
Vance Shipley
SigScale