hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5 Reference points description
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.1 General reference point principle
| 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 3GPP TS 23.002 [14].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2 Application plane
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.1 General
| The reference points for the generic functional model for SEAL are described in the following subclauses.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.2 VAL-UU
| 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 3GPP TS 23.401 [9] and 3GPP TS 23.501 [10].
NOTE: The details of VAL-UU reference point is out of... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.3 VAL-PC5
| 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 3GPP TS 23.303 [12].
NOTE: The details of VAL-PC5 reference point is out of scope of the prese... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.4 SEAL-UU
| 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.5 SEAL-PC5
| 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.6 SEAL-C
| 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.7 SEAL-S
| 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.8 SEAL-E
| 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.
NOTE: The functions enabled over SEAL-E reference point are specified in each S... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.9 SEAL-X
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.9.1 General
| 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.9.2 Reference point SEAL-X1 (between the key management server and the group management server)
| 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 referenc... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.9.3 Reference point SEAL-X2 (between the group management server and the location management server)
| 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.9.4 Reference point SEAL-X3 (between the group management server and the configuration management server)
| 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.2.10 Reference point VAL-UDB (between the VAL user database and the SEAL server)
| 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;
- obtaining the user profile from the specific VAL user database for further configuration in the UE;
- updating the user profile data in the sp... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3 Signalling control plane
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.1 General
| The reference points for the SIP and HTTP signalling are described in the following subclauses.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.2 Reference point SIP-1(between the signalling user agent and the SIP core)
| 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 3GPP TS 23.002 [14] (with necessary enhancements to support VAL service requirements and profiled to meet the minimum requiremen... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.3 Reference point SIP-2 (between the SIP core and the SIP AS)
| 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 3GPP TS 23.002 [14]. The SIP-2 reference point is used for:
- notification to the VAL service server(s) of SIP registration by the VA... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.4 Reference point SIP-3 (between the SIP core and SIP core)
| 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 3GPP TS 23.002 [14]. The SIP-3 reference point is used for:
- event subscription and event notification;
- session management;... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.5 Reference point HTTP-1 (between the HTTP client and the HTTP proxy)
| 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 3GPP TS 23.002 [14] (with necessary enhancements to support specific VAL service requirements). The HTTP-1 reference point is bas... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.6 Reference point HTTP-2 (between the HTTP proxy and the HTTP server)
| 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).
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.7 Reference point HTTP-3 (between the HTTP proxy and HTTP proxy)
| 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).
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.8 Reference point AAA-1 (between the SIP database and the SIP core)
| 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 3GPP TS 23.002 [14].
In some deployment scenarios the registrar and SIP database ar... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.9 Reference point AAA-2 (between the SIP core and Diameter proxy)
| 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 3GPP TS 23.002 [14]. The AAA-2 reference point is used for:
- authentication and security to the service layer for migration;
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.10 Reference point LWP-1 (between the LWP client and the LWP proxy)
| The LWP-1 reference point exists between the LWP client and the LWP proxy.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.11 Reference point LWP-2 (between the LWP proxy and the LWP server)
| The LWP-2 reference point exists between the LWP proxy and the LWP server.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.12 Reference point LWP-3 (between the LWP proxy and LWP proxy)
| The LWP-3 reference point exists between the LWP proxy and another LWP proxy in a different network.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.13 Reference point LWP-HTTP-2 (between the LWP proxy and the HTTP server)
| 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.5.3.14 Reference point LWP-HTTP-3 (between the LWP proxy and the HTTP proxy)
| 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.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 7 Identities
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 7.1 User identity (User ID)
| The VAL user presents the user identity to the identity management server during a user authentication transaction, to provide the identity management client a means for VAL service authentication. In general, since identity management is a common SEAL service, it uses a set of credentials (e.g. biometrics, secureID, u... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 7.2 VAL user identity (VAL user ID)
| The VAL user ID is a unique identifier within the VAL service that represents the VAL user. For example, the VAL user ID may be a URI. The VAL user ID is used for authentication and authorization purposes for providing the VAL service towards the VAL user via the VAL UE. The VAL user ID also indicates the VAL service p... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 7.3 VAL UE identity (VAL UE ID)
| The VAL UE ID is a unique identifier within the VAL service that represents the VAL UE. For example, the VAL UE ID for V2X service is mapped to the StationID as specified in ETSI TS 102 894-2 [25]. The VAL UE ID is used to address the VAL UE in order to send VAL messages or to access SEAL services.
Based on the servic... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 7.4 VAL service identity (VAL service ID)
| The VAL service ID is a unique identifier that represents the VAL service. A VAL server provides a list of VAL services towards the VAL users or VAL UE. Each VAL service is uniquely identified by a VAL service ID, which is an identifier of the VAL application providing that VAL service. The VAL service ID can be used f... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 7.5 VAL group identity (VAL group ID)
| The VAL group ID is a unique identifier within the VAL service that represents a set of VAL users or VAL UE according to the VAL service. The set of VAL users may belong to the same or different VAL service providers. It indicates the VAL application server where the group is defined.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 7.6 VAL system identity (VAL system ID)
| The VAL system ID is a globally unique identifier representing a VAL system.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 7.7 VAL Stream ID
| A VAL Stream ID is an identity used by the VAL server to identify a VAL stream.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 8 Application of functional model to deployments
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 8.1 General
| This clause describes deployments of the functional model specified in clause 6.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 8.2 Deployment of SEAL server(s)
| The SEAL server(s) may be deployed either in the PLMN operator domain or deployed in the VAL service provider domain. The SEAL server(s) connects with the 3GPP network system in one or more PLMN operator domain. The SEAL server(s) may be supporting multiple VAL servers.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 8.2.1 SEAL server(s) deployment in PLMN operator domain
| Figure 8.2.1-1 illustrates deployment of the SEAL server(s) in a single PLMN operator domain and the VAL server(s) in the VAL service provider domain.
Figure 8.2.1-1: SEAL server(s) deployed in a single PLMN operator domain
Figure 8.2.1-2 illustrates the deployment of SEAL server(s) in multiple PLMN operator domain... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 8.2.2 SEAL server(s) deployment in VAL service provider domain
| Figure 8.2.2-1 illustrates deployment of the SEAL server(s) and the VAL server(s) in VAL service provider domain.
Figure 8.2.2-1: Deployment of SEAL server(s) with connections to 3GPP network system in a single PLMN operator domain
Figure 8.2.2‑2 illustrates deployment of the SEAL server(s) which connects to the 3... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 8.2.3 SEAL server(s) deployment outside of VAL service provider domain and PLMN operator domain
| Figure 8.2.3-1 illustrates deployment of the SEAL server(s) outside of both the VAL service provider domain and PLMN operator domain i.e. in SEAL provider domain.
Figure 8.2.3-1: Deployment of SEAL server(s) outside of VAL service domain and PLMN operator domain
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 8.3 Deployment of SEAL client(s)
| 8.3.1 General description
SEAL provider may provide SEAL Client(s) as UE SDK on top of UE OS. SEAL Client(s) may be implemented in UE vendor domain.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 8.3.2 Deployment of SEAL Client(s) in the same provider domain of SEAL server(s)
| Figure 8.3.2-1 illustrates deployment of the SEAL client(s) in the same domain of SEAL server(s). In this case, SEAL server(s) can be deployed in any of the domain described in clause 8.2.1 or 8.2.2, or 8.2.3.
Figure 8.3.2-1: SEAL client(s) deployed in the same domain of SEAL server
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 8.3.3 Deployment of SEAL Client(s) in UE vendor domain
| Figure 8.3.3-1 and Figure 8.3.3-2 illustrates deployment of the SEAL client(s) in UE Vendor domain, which is different with the domain of SEAL server. In this case, SEAL server(s) can be deployed in any of the domain described in clause 8.2.1 or 8.2.2, or 8.2.3.
Figure 8.3.3-1: SEAL client(s) deployed in UE vendor... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9 Location management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.1 General
| The location management is a SEAL service that offers the location management related capabilities to one or more vertical applications.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2 Functional model for location management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.1 General
| The functional model for the location management is based on the generic functional model specified in clause 6. It is organized into functional entities to describe a functional architecture which addresses the support for location management aspects for vertical applications. The on-network and off-network functional... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.2 On-network functional model description
| Figure 9.2.2-1 illustrates the generic on-network functional model for location management.
Figure 9.2.2-1: On-network functional model for location management
The location management client communicates with the location management server over the LM-UU reference point. The location management client provides the ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.3 Off-network functional model description
| Figure 9.2.3-1 illustrates the off-network functional model for location management.
Figure 9.2.3-1: Off-network functional model for location management
The location management client of the UE1 communicates with the location management client of the UE2 over the LM-PC5 reference point.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.4 Functional entities description
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.4.1 General
| The functional entities for location management SEAL service are described in the following subclauses.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.4.2 Location management client
| The location management client functional entity acts as the application client for location management functions. It interacts with the location management server and may provide UE-based positioning and location-related information. The location management client also supports interactions with the corresponding loca... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.4.3 Location management server
| The location management server is a functional entity that receives and stores user location information and provides user location information to the vertical application server. The location management server may also acquire location information provided by PLMN operator via T8, N33, or Le reference points. The loca... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.5 Reference points description
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.5.1 General
| The reference points for the functional model for location management are described in the following subclauses.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.5.2 LM-UU
| The interactions related to location management functions between the location management client and the location management server are supported by LM-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.401 [9] and 3GPP TS 23.501 [10].
LM-UU reference point provides a means... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.5.3 LM-PC5
| The interactions related to location management functions between the location management clients located in different VAL UEs are supported by LM-PC5 reference point. This reference point utilizes PC5 reference point as described in 3GPP TS 23.303 [12].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.5.4 LM-C
| The interactions related to location management functions between the VAL client(s) and the location management client within a VAL UE are supported by LM-C reference point.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.5.5 LM-S
| The interactions related to location management functions between the VAL server(s) and the location management server are supported by LM-S reference point. This reference point is an instance of CAPIF-2 reference point as specified in 3GPP TS 23.222 [8].
LM-S reference point is used by the VAL server to request and ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.5.6 LM-E
| The interactions related to location management functions between the location management servers in a distributed deployment are supported by LM-E reference point.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.5.7 T8
| The reference point T8 supports the interactions between the location management server and the SCEF and is specified in 3GPP TS 23.682 [13]. The functions related to location management of T8 are supported by the location management server.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.5.8 Le
| The reference point Le supports the interactions between the location management server and the GMLC and is specified in 3GPP TS 23.273 [50].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.5.9 LM-3P
| The reference point LM-3P is used for location retrieval of the target UE from a third-party location server.
NOTE: Further definition of LM-3P is out of scope of this specification.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.2.5.10 N33
| The reference point N33 supports the interactions between the location management server and the NEF and is specified in 3GPP TS 23.501 [10] and 3GPP TS 23.502 [11]. The functions related to location management of N33 are supported by the location management server.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3 Procedures and information flows for Location management (on-network)
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.1 General
| Location information of VAL service user shall be provided by the location management client to the location management server. The location information reporting triggers are based on the location reporting configuration. Different type of location information can be provided.
NOTE: The security and privacy aspects r... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2 Information flows for location information
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.0 Location reporting configuration request
| Table 9.3.2.0-1 describes the information flow from the location management client to the location management server for requesting the location reporting configuration.
Table 9.3.2.0-1: Location reporting configuration request
Information element
Status
Description
Identity
M
Identity of the VAL user or identit... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.1 Location reporting configuration response
| Table 9.3.2.1-1 describes the information flow from the location management server to the location management client for the location reporting configuration. This information flow may be sent individually addressed or group addressed on unicast or multicast.
Table 9.3.2.1-1: Location reporting configuration response
... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.2 Location information report
| Table 9.3.2.2-1 describes the information flow from the location management client to the location management server for the location information reporting or from the location management server to the requesting location management client or VAL server to report location information.
Table 9.3.2.2-1: Location informa... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.3 Location information request
| Table 9.3.2.3-1 describes the information flow from the VAL server to the location management server and/or from the location management server to the location management client for requesting an immediate location information report.
Table 9.3.2.3-1: Location information request
Information element
Status
Descript... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.4 Location reporting trigger
| Table 9.3.2.4-1 describes the information flow from the location management client or VAL server to the location management server for triggering a location reporting procedure.
Table 9.3.2.4-1: Location reporting trigger
Information element
Status
Description
Requestor Identity
M
(see NOTE 1)
Identity of the r... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.5 Location information subscription request
| Table 9.3.2.5-1 describes the information flow from the VAL server or location management client to the location management server for location information subscription request or for updating an existing location information subscription.
Table 9.3.2.5-1: Location information subscription request
Information element... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.6 Location information subscription response
| Table 9.3.2.6-1 describes the information flow from the location management server to the VAL server or location management client for location information subscription response or location information subscription update response.
Table 9.3.2.6-1: Location information subscription response
Information element
Statu... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.7 Location information notification
| Table 9.3.2.7-1 describes the information flow from the location management server to the VAL server or the location management client.
Table 9.3.2.7-1: Location information notification
Information element
Status
Description
Identities list
M
List of the VAL users or VAL UEs whose location information needs to ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.8 Location reporting configuration cancel request
| Table 9.3.2.8-1 describes the location reporting configuration cancel request information flow from the location management client or VAL server to the location management server or from the location management server to the location management client.
Table 9.3.2.8-1: Location reporting configuration cancel request
... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.9 Get UE(s) information request
| Table 9.3.2.9-1 describes the information flow for a VAL server to get UE(s) information at the location management server.
Table 9.3.2.9-1: Get UE(s) information request
Information element
Status
Description
Location information
M
Location information around which the UE(s) information is requested (e.g. geogr... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.10 Get UE(s) information response
| Table 9.3.2.10-1 describes the information flow for a LM server to respond with UE(s) information to the VAL server.
Table 9.3.2.10-1: Get UE(s) information response
Information element
Status
Description
Result
M
Result from the VAE server in response to subscription request indicating success or failure
List... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.11 Monitor Location Subscription Request
| Table 9.3.2.11-1 describes the information flow from the VAL server to the location management server for monitoring the location deviation of the VAL UE(s) or for updating an existing monitor location subscription.
Table 9.3.2.11-1: Monitor Location Subscription Request
Information element
Status
Description
Targ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.12 Monitor Location Subscription Response
| Table 9.3.2.12-1 describes the information flow from location management server to the VAL server for Monitor Location Subscription Response or monitor location subscription update response.
Table 9.3.2.12-1: Monitor Location Subscription Response
Information element
Status
Description
Subscription status
M
It ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.13 Notify Location Monitoring Event
| Table 9.3.2.13-1 describes the information flow from location management server to the VAL server for notification of location monitoring events.
Table 9.3.2.13-1: Notify Location Monitoring Event message
Information element
Status
Description
Event
M
Information of the event to be reported. The event shall be ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.14 Location area monitoring subscription request
| Table 9.3.2.14-1 describes the information flow from the VAL server to the location management server for location area monitoring subscription request.
Table 9.3.2.14-1: Location area monitoring subscription request
Information element
Status
Description
Identity
M
Identity of the requesting VAL server, VAL UE ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.15 Location area monitoring subscription response
| Table 9.3.2.15-1 describes the information flow from the location management server to the VAL server for location area monitoring subscription response.
Table 9.3.2.15-1: Location area monitoring subscription response
Information element
Status
Description
Subscription status
M
It indicates the subscription res... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.16 Location area monitoring notification
| Table 9.3.2.16-1 describes the information flow from the location management server to the VAL server.
Table 9.3.2.16-1: Location area monitoring notification
Information element
Status
Description
Subscription identity
M
Identity of the subscription
UEs currently present
(see NOTE)
O
List of the identities ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.17 Location area monitoring subscription modify request
| Table 9.3.2.17-1 describes the information flow from the VAL server to the location management server for location area monitoring subscription modify request.
Table 9.3.2.17-1: Location area monitoring subscription modify request
Information element
Status
Description
Identity
M
Identity of the requesting VAL s... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.18 Location area monitoring subscription modify response
| Table 9.3.2.18-1 describes the information flow from the location management server to the VAL server for location area monitoring subscription modify response.
Table 9.3.2.18-1: Location area monitoring subscription modify response
Information element
Status
Description
Subscription modification status
M
It ind... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.19 Location area monitoring unsubscribe request
| Table 9.3.2.19-1 describes the information flow from the VAL server to the location management server for location area monitoring unsubscribe request.
Table 9.3.2.19-1: Location information monitoring unsubscribe request
Information element
Status
Description
Identity
M
Identity of the requesting VAL server, VA... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.20 Location area monitoring unsubscribe response
| Table 9.3.2.20-1 describes the information flow from the location management server to the VAL server for location area monitoring unsubscribe response.
Table 9.3.2.20-1: Location area monitoring unsubscribe response
Information element
Status
Description
Request status
M
It indicates the request result
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.21 VAL service area configuration request
| Table 9.3.2.21-1 describes the information flow from the VAL server to the location management server for VAL service area configuration request.
Table 9.3.2.21-1: VAL service area configuration request
Information element
Status
Description
Identity
M
Identity of the requesting VAL server
List of VAL service a... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.22 VAL service area configuration response
| Table 9.3.2.22-1 describes the information flow from the location management server to the VAL server for VAL service area configuration response.
Table 9.3.2.22-1: VAL service area configuration response
Information element
Status
Description
VAL Service area configuration status
M
It indicates the result of VA... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.23 Location service registration request
| Table 9.3.2.23-1 describes the information flow from the location management client to the location management server for registration of the location service.
Table 9.3.2.23-1: Location service registration request
Information element
Status
Description
Identity
M
Identity of the VAL user or identity of the VAL... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.24 Location service registration response
| Table 9.3.2.24-1 describes the information flow from the location management server to the location management client for the location service registration response.
Table 9.3.2.24-1: Location service registration response
Information element
Status
Description
Registration status
M
It indicated the registration... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.25 Location reporting configuration cancel response
| Table 9.3.2.25-1 describes the location reporting configuration cancel response information flow from the location management server to the location management client or from the location management client to the location management server.
Table 9.3.2.25-1: Location reporting configuration cancel response
Informatio... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 9.3.2.26 VAL service area obtain request
| Table 9.3.2.26-1 describes the information flow from a VAL server to a location management server for obtain VAL service area identifiers at the location management server.
Table 9.3.2.26-1: Obtain VAL service area request
Information element
Status
Description
Identity
M
Indicates the VAL server identity.
VAL ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.