Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.434  Word version:  18.0.0

Top   Top   Up   Prev   Next
0…   4…   6…   6.4…   6.5…   7…   8…   8.2.2…   9…   9.3…   9.3.6…   9.4…   10…   10.3…   10.3.2.22…   10.3.3…   10.3.7…   10.4…   11…   11.3…   12…   13…   14…   14.3…   14.3.3…   14.3.3.3…   14.3.4…   14.3.4.6…   14.4…   15…   A…

 

6.5  Reference points descriptionWord‑p. 31

6.5.1  General reference point principleWord‑p. 31

The protocols on any reference point that is exposed for VAL service interoperability with other SIP core or other IMS entities in other systems shall be compatible with the protocols defined for the corresponding reference point defined in TS 23.002.

6.5.2  Application planeWord‑p. 31

6.5.2.1  GeneralWord‑p. 31

The reference points for the generic functional model for SEAL are described in the following subclauses.

6.5.2.2  VAL-UUWord‑p. 31

The interactions related to vertical application layer support functions between VAL client and VAL server are supported by VAL-UU reference point. This reference point is an instance of Uu reference point as described in TS 23.401 and TS 23.501.

6.5.2.3  VAL-PC5Word‑p. 31

The interactions related to vertical application layer support functions between the VAL clients of two UEs are supported by VAL-PC5 reference point. This reference point is an instance of PC5 reference point as described in TS 23.303.

6.5.2.4  SEAL-UUWord‑p. 31

The interactions between a SEAL client and the corresponding SEAL server are generically referred to as SEAL-UU reference point. The specific SEAL service reference point corresponding to SEAL-UU is specified in the specific SEAL service functional model.

6.5.2.5  SEAL-PC5Word‑p. 31

The interactions between the SEAL clients of two VAL UEs are generically referred to as SEAL-PC5 reference point. The specific SEAL service reference point corresponding to SEAL-PC5 is specified in the specific SEAL service functional model.

6.5.2.6  SEAL-CWord‑p. 31

The interactions between the VAL client(s) and the SEAL client(s) within a VAL UE are generically referred to as SEAL C reference point. The specific SEAL service reference point corresponding to SEAL-C is specified in the specific SEAL service functional model.

6.5.2.7  SEAL-SWord‑p. 31

The interactions between the VAL server and the SEAL server are generically referred to as SEAL S reference point. The specific SEAL service reference point corresponding to SEAL-S is specified in the specific SEAL service functional model.

6.5.2.8  SEAL-EWord‑p. 32

The interactions between the SEAL servers of the same type are generically referred to as SEAL E reference point. The specific SEAL service reference point corresponding to SEAL-E is specified in the specific SEAL service functional model.

6.5.2.9  SEAL-XWord‑p. 32

6.5.2.9.1  GeneralWord‑p. 32
The interactions between the SEAL servers of different type are generically referred to as SEAL X reference point. The specific SEAL server interactions corresponding to SEAL-X are described in the following subclauses.
6.5.2.9.2  Reference point SEAL-X1 (between the key management server and the group management server)Word‑p. 32
The SEAL-X1 reference point, which exists between the key management server and the group management server, provides a means for the key management server to provide security related information (e.g. encryption keys) to the group management server.
The SEAL-X1 reference point shall use the HTTP-1 and HTTP-2 reference points and may use the HTTP-3 reference point for transport and routing of security related information to the group management server.
6.5.2.9.3  Reference point SEAL-X2 (between the group management server and the location management server)Word‑p. 32
The SEAL-X2 reference point enables the group management server to interact with the location management server.
The SEAL-X2 reference point supports:
  • the group management server to create a location-based group with the help from the location management server.
6.5.2.9.4  Reference point SEAL-X3 (between the group management server and the configuration management server) |R18|Word‑p. 32
The SEAL-X3 reference point enables the group management server to interact with the configuration management server.
The SEAL-X3 reference point supports:
  • the group management server to retrieve VAL service data from the configuration management server.

6.5.2.10  Reference point VAL-UDB (between the VAL user database and the SEAL server)Word‑p. 32

The VAL-UDB reference point, which exists between the VAL user database and the SEAL server, is used for:
  • storing the user profile data in the specific VAL user database; and
  • obtaining the user profile from the specific VAL user database for further configuration in the UE.

6.5.3  Signalling control planeWord‑p. 32

6.5.3.1  GeneralWord‑p. 32

The reference points for the SIP and HTTP signalling are described in the following subclauses.

6.5.3.2  Reference point SIP-1(between the signalling user agent and the SIP core)Word‑p. 33

The SIP-1 reference point, which exists between the signalling user agent and the SIP core for establishing a session in support of VAL service, shall use the Gm reference point as defined in TS 23.002 (with necessary enhancements to support VAL service requirements and profiled to meet the minimum requirements for support of VAL service). The SIP-1 reference point fulfils the requirements of the GC1 reference point specified in TS 23.468. The SIP-1 reference point is used for:
  • SIP registration;
  • authentication and security to the service layer;
  • event subscription and event notification;
  • communication of the TMGI for multicast operation;
  • overload control;
  • session management; and
  • media negotiation.
Up

6.5.3.3  Reference point SIP-2 (between the SIP core and the SIP AS)Word‑p. 33

The SIP-2 reference point, which exists between the SIP core and the SIP AS for establishing a session in support of VAL service, shall use the ISC and Ma reference points as defined in TS 23.002. The SIP-2 reference point is used for:
  • notification to the VAL service server(s) of SIP registration by the VAL UE;
  • authentication and security to the service layer;
  • event subscription and event notification;
  • communication of the TMGI for multicast operation;
  • session management; and
  • media negotiation.
Up

6.5.3.4  Reference point SIP-3 (between the SIP core and SIP core)Word‑p. 33

The SIP-3 reference point, which exists between one SIP core and another SIP core for establishing a session in support of VAL service, shall use the Mm and ICi reference points as defined in TS 23.002. The SIP-3 reference point is used for:
  • event subscription and event notification;
  • session management; and
  • media negotiation.

6.5.3.5  Reference point HTTP-1 (between the HTTP client and the HTTP proxy)Word‑p. 33

The HTTP-1 reference point exists between the HTTP client and the HTTP proxy. Between the VAL UE and the HTTP proxy, the HTTP-1 reference point shall use the Ut reference point as defined in TS 23.002 (with necessary enhancements to support specific VAL service requirements). The HTTP-1 reference point is based on HTTP (which may be secured using e.g. SSL, TLS).

6.5.3.6  Reference point HTTP-2 (between the HTTP proxy and the HTTP server)Word‑p. 34

The HTTP-2 reference point, which exists between the HTTP proxy and the HTTP server, is based on HTTP (which may be secured using e.g. SSL, TLS).

6.5.3.7  Reference point HTTP-3 (between the HTTP proxy and HTTP proxy)Word‑p. 34

The HTTP-3 reference point, which exists between the HTTP proxy and another HTTP proxy in a different network, is based on HTTP (which may be secured using e.g. SSL, TLS).

6.5.3.8  Reference point AAA-1 (between the SIP database and the SIP core)Word‑p. 34

The AAA-1 reference point, which exists between the SIP database and the SIP core, is used by the SIP core to retrieve signalling plane data from the SIP database. The AAA-1 reference point utilises the Cx reference point as defined in TS 23.002.
In some deployment scenarios the registrar and SIP database are located in the VAL service provider's network while the registrar finder is in the PLMN operator's network and the AAA-1 reference point is an inter-network interface.
Up

6.5.3.9  Reference point AAA-2 (between the SIP core and Diameter proxy)Word‑p. 34

The AAA-2 reference point, which exists between the SIP core / IMS and Diameter proxy for SIP registration during migration, shall use the Cx reference point as defined in TS 23.002. The AAA-2 reference point is used for:
  • authentication and security to the service layer for migration;

6.5.3.10  Reference point LWP-1 (between the LWP client and the LWP proxy) |R17|Word‑p. 34

The LWP-1 reference point exists between the LWP client and the LWP proxy.

6.5.3.11  Reference point LWP-2 (between the LWP proxy and the LWP server) |R17|Word‑p. 34

The LWP-2 reference point exists between the LWP proxy and the LWP server.

6.5.3.12  Reference point LWP-3 (between the LWP proxy and LWP proxy) |R17|Word‑p. 34

The LWP-3 reference point exists between the LWP proxy and another LWP proxy in a different network.

6.5.3.13  Reference point LWP-HTTP-2 (between the LWP proxy and the HTTP server) |R17|Word‑p. 34

The LWP-HTTP-2 reference point exists between the LWP proxy and the HTTP server. HTTP-2 and LWP-HTTP-2 reference points are equivalent.

6.5.3.14  Reference point LWP-HTTP-3 (between the LWP proxy and the HTTP proxy) |R17|Word‑p. 34

The LWP-HTTP-3 reference point exists between the LWP proxy and another HTTP proxy in a different network. HTTP-3 and LWP-HTTP-3 reference points are equivalent.

Up   Top   ToC