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.
This clause specifies 3GPP procedure for the port number allocation based on the solution#6 (see
clause 4.4 in TR 29.941).
-
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):
-
The request should be for a protocol, which is supported by intra-domain interface(s).
-
The request should indicate that the request cannot meet IANA/IETF requirements for the port number allocation (see Annex C in TR 29.941).
-
The request should indicate that solution#6 is preferable and selected after evaluating other solutions specified in TR 29.941.
-
LS request to 3GPP CT4 shall also contain the following information:
-
The service name, e.g. x2-ctrl.
b. Applicable transport protocol(s).
c. Short description, e.g. X2-CP.
d. A statement that the new port number will be used across intra-domain interface <name> between nodes <name> and <name>.
-
Work Item Code (WIC) used by the request sender (both the abbreviation and the numerical value).
-
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).