Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 29.571  Word version:  17.3.0

Top   Top   None   None   Next
1…   5…

 

1  ScopeWord‑p. 9

The present document specifies the stage 3 protocol and data model for common data types that are used or may be expected to be used by multiple Service Based Interface APIs supported by the same or different Network Function(s).
The Principles and Guidelines for Services Definition are specified in TS 29.501.

2  References

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 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[3]
OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
[4]
RFC 1166:  "Internet Numbers".
[5]
RFC 5952:  "A recommendation for IPv6 address text representation".
[6]
RFC 3986:  "Uniform Resource Identifier (URI): Generic Syntax".
[7]
TS 23.003: "Numbering, addressing and identification".
[8]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[9]
RFC 7807:  "Problem Details for HTTP APIs".
[10]
RFC 3339:  "Date and Time on the Internet: Timestamps".
[11]
TS 38.413: "NG-RAN; NG Application Protocol (NGAP) ".
[12]
RFC 6901:  "JavaScript Object Notation (JSON) Pointer".
[13]
TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[14]
RFC 6902:  "JavaScript Object Notation (JSON) Patch".
[15]
RFC 4122:  "A Universally Unique IDentifier (UUID) URN Namespace".
[16]
TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[17]
RFC 7042:  "IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters".
[18]
RFC 6733:  "Diameter Base Protocol".
[19]
TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management".
[20]
TS 24.501: "Non-Access-Stratum (NAS) Protocol for 5G System (5GS); Stage 3".
[21]
TS 29.002: "Mobile Application Part (MAP) specification".
[22]  Void.
[23]
TS 23.032: "Universal Geographical Area Description (GAD)".
[24]
ITU-T Recommendation Q.763 (1999): "Specifications of Signalling System No.7; Formats and codes".
[25]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[26]
TS 23.015: "Technical Realization of Operator Determined Barring".
[27]
TR 21.900: "Technical Specification Group working methods".
[28]
TS 23.502: "Procedures for the 5G System; Stage 2".
[29]
TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[30]
TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".
[31]
IEEE Std 802.11-2012: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications".
[32]
CableLabs WR-TR-5WWC-ARCH: "5G Wireless Wireline Converged Core Architecture".
[33]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access; Stage 2".
[34]
BBF TR-069: "CPE WAN Management Protocol".
[35]
BBF TR-369: "User Services Platform (USP)".
[36]
TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
[37]
BBF TR-470: "5G Wireless Wireline Convergence Architecture".
[38]
IEEE "Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)": https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/tutorials/eui.pdf
[39]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[40]
RFC 5580:  "Carrying Location Objects in RADIUS and Diameter".
[41]
BBF TR-456: "AGF Functional Requirements".
[42]
TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
Up

3  Definitions and abbreviationsWord‑p. 11

3.1  Definitions

For the purposes of the present document, the terms and definitions 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  Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905 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.
5GC
5G Core Network
DNAI
Data Network Access Identifier
EUI
Extended Unique Identifier
GEO
Geosynchronous Orbit
GPSI
Generic Public Subscription Identifier
GUAMI
Globally Unique AMF Identifier
HFC
Hybrid Fiber Coax
LEO
Low Earth Orbit
MEO
Medium Earth Orbit
N5GC
Non-5G Capable
NSSAA
Network Slice- Specific Authentication and Authorization
PEI
Permanent Equipment Identifier
SBI
Service Based Interface
SUPI
Subscription Permanent Identifier
Up

4  Overview

For the different 5GC SBI API, data types shall be defined. Data types identified as common data types shall be defined in this Technical specification and should be referenced from individual 5GC SBI API specifications.
Data types applicable or intended to be applicable to several 5GC SBI API specifications should be interpreted as common data types.

Up   Top   ToC