Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 32.257  Word version:  17.2.0

Top   Top   None   None   Next
1…   4…

 

1  Scopep. 8

The present document is part of a series of documents that specify charging functionality and charging management in 3GPP networks. The 3GPP core network charging architecture and principles are specified in TS 32.240, which provides an umbrella for other charging management TSs that specify:
  • the content of the CDRs per domain / subsystem / service (offline charging);
  • the content of real-time charging messages per domain / subsystem / service (online charging);
  • the functionality of online and offline charging for those domains / subsystems / services;
  • the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for these TSs is defined in TS 32.240.
The present document specifies the converged offline and online charging description for the Edge Computing domain based on the functional stage 2 description in TS 23.501 and TS 23.558.
Edge computing in 5G environment involves the services or capabilities provided by multiple service providers and entities in the form of following business roles:
  • ASP providing edge application service to the subscribers;
  • ECSP providing edge enabling infrastructure and edge enabling services to ASP;
  • MNO providing 5GS capabilities supporting edge computing.
The present document specifies following charging aspects for Edge Computing:
  • Subscriber charging:
    • MNO charges the subscribers for usage of 5GS capabilities supporting edge computing.
  • Service-provider charging:
    • MNO charges the industry consumer (e.g. ECSP, ASP) for 5GS capabilities provided to support edge computing in total instead of for each individual subscriber;
    • ECSP charges the ASP for the edge enabling infrastructure and services.
Up

2  Referencesp. 9

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[3]
TS 32.298: "Telecommunication management; Charging management; Charging Data Record (CDR) parameter description".
[4]
TS 32.297: "Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer".
[5]
TS 32.295: "Telecommunication management; Charging management; Charging Data Record (CDR) transfer".
[6]
TS 32.290: "Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI)".
[7]
TS 32.291: "Telecommunication management; Charging management; 5G system, charging service; Stage 3".
[8]
TS 23.501: "System architecture for the 5G System (5GS)".
[9]
TS 23.558: "Architecture for enabling Edge Applications".
[10]
TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[11]
TS 32.255: "Telecommunication management; Charging management; 5G Data connectivity domain charging; stage 2".
[12]
TS 28.538: "Management and orchestration; Edge Computing Management".
[13]
TS 28.552: "Management and orchestration; 5G performance measurements".
[14]
TS 28.550: "Management and orchestration; Performance assurance".
[15]
TS 28.532: "Management and orchestration; Generic management services".
[16]
TS 32.254: "Telecommunication management; Charging management; Exposure function Northbound Application Program Interfaces (APIs) charging".
[17]
TS 29.558: "Enabling Edge Applications; Application Programming Interface (API) specification; Stage 3".
Up

3  Definitions of terms, symbols and abbreviationsp. 10

3.1  Termsp. 10

For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

3.2  Symbolsp. 10

For the purposes of the present document, the following symbols apply:
Bee
Reference point for the CDR file transfer from the EDGE CGF to the BD.
Ga
Reference point for CDR transfer between a CDF and CGF.
Nchf
Service based interface exhibited by CHF.
N49
Reference point between EES and CHF.

3.3  Abbreviationsp. 10

For the purposes of the present document, the abbreviations given in TR 21.905, TS 23.501, TS 23.558, TS 23.548 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905, TS 23.501, TS 23.558 and TS 23.548.
ASP
Application Service Provider
CEF
Charging Enablement Function
CHF
Charging Function
EAS
Edge Application Server
ECSP
Edge Computing Service Provider
EES
Edge Enabler Server
MNO
Mobile Network Operator
MnS
Management Service
MOI
Managed Object Instance
Up

Up   Top   ToC