Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TS 29.641
3GPP Registry for Service Names and Port Numbers

V17.0.0 (PDF)2022/03  9 p.
Rapporteur:
Mr. Gulbani, Giorgi
Huawei Technologies Sweden AB

Content for  TS 29.641  Word version:  17.0.0

Here   Top

1  ScopeWord‑p. 5

The present document defines 3GPP procedures for Service Name and Port Number registry management. These procedures should be followed by 3GPP WGs when requesting new port numbers for the 3GPP allocated port number solution#6, which is specified in clause 4.4 of TR 29.941.
The present document also maintains a database of the 3GPP allocated port numbers.

2  ReferencesWord‑p. 5

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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[3]
TR 29.941: "Study on Port Number Allocation Alternatives for New 3GPP Interfaces".
Up

3  Definitions of terms, symbols and abbreviationsWord‑p. 5

3.1  TermsWord‑p. 5

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.2Void

3.3Void

4  3GPP procedures for Service Name and Port Number registry managementWord‑p. 6

4.1  General PrinciplesWord‑p. 6

3GPP CT4 is responsible for the management and maintenance of service name and port number registry from the sub-range of 101 ports from 65400 to 65500. This sub-range belongs to the Dynamic/Private Port range [49152 - 65535] and IANA does not assign port numbers from this range.
Clause 4.4 in TR 29.941 specifies solution#6 for 3GPP allocated port numbers. Solution#6 requires 3GPP CT4 to maintain the 3GPP allocated port number repository.
Up

4.2  3GPP allocated Service Name and Port Number registryWord‑p. 6

This clause specifies 3GPP procedure for the port number allocation based on the solution#6 (see clause 4.4 in TR 29.941).
  1. If a 3GPP working group decides to utilize 3GPP allocated port number solution#6, the working group shall send an LS request to 3GPP CT4. CT4 accepts the request if it addresses the following matters (checklist):
    1. The request should be for a protocol, which is supported by intra-domain interface(s).
    2. The request should indicate that the request cannot meet IANA/IETF requirements for the port number allocation (see Annex C in TR 29.941).
    3. The request should indicate that solution#6 is preferable and selected after evaluating other solutions specified in TR 29.941.
  2. 3GPP CT4 shall inform the 3GPP WG that has requested new port number allocation and also may inform other, relevant 3GPP WGs about the decision. 3GPP CT4 creates respective CR. If CT plenary approves the CR, then the assigned port number will be added to the Table 5-1 (see clause 5).
Up

5  Port Number DatabaseWord‑p. 6

Table 5-1 represents 3GPP allocated service name and port number registry. 3GPP CT4 maintains the repository.
Service Name Port Number Transport Protocol Description Inter/Intra interface between entities Requesting WG Registration Date
<e.g. x2-ctrl><assigned port #><UDP/TCP/ SCTP><e.g. X2-CP><e.g. Intra eNB-eNB><e.g. RAN3><yyyy-mm-dd>
Up

$  Change historyWord‑p. 7


Up   Top