hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.5 Reference points description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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].
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.5.2 Application plane
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.5.2.1 General
|
The reference points for the generic functional model for SEAL are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 scope of the present document.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 present document.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 SEAL service.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.5.2.9 SEAL-X
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 reference points and may use the HTTP-3 reference point for transport and routing of security related information to the group management server.
NOTE: SEAL-X1 is specified in subclause 5.1.1.1 of 3GPP TS 33.434 [29].
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 specific VAL user database; and
- deleting the user profile data from the specific VAL user database.
NOTE: The details of the VAL-UDB reference point is out of scope of the present document.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.5.3 Signalling control plane
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
6.5.3.1 General
|
The reference points for the SIP and HTTP signalling are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 requirements for support of VAL service). The SIP-1 reference point fulfils the requirements of the GC1 reference point specified in 3GPP TS 23.468 [16]. 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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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; and
- media negotiation.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 based on HTTP (which may be secured using e.g. SSL, TLS).
|
d23d1b9504aafd6c2e98868ecaffb278
|
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).
|
d23d1b9504aafd6c2e98868ecaffb278
|
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).
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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;
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
7 Identities
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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, username/password) that may not necessarily be tied to a single VAL service. The user credentials uniquely identifies the VAL user to the identity management server.
NOTE: The specific security and authentication mechanisms required in order to use the user ID is specified in 3GPP TS 33.434 [29].
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 provider with whom the VAL user has a VAL service agreement. The VAL user may have VAL service agreement with several VAL service providers and thus will have obtained unique VAL user ID per VAL service provider. The VAL user ID can be used to access any SEAL service.
Based on the service agreement, VAL user ID may be mapped to a VAL UE ID.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 service agreement, GPSI (as specified in 3GPP TS 23.003 [38]) may be used as VAL UE identity.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 for policy mapping, QoS handling for VAL communication and VAL message distribution. For example, an identifier of a V2X service, e.g. ITS-AID or PSID specified in ETSI TS 102 965 [26] and ISO TS 17419 [27], can be used as a V2X service ID.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
7.6 VAL system identity (VAL system ID)
|
The VAL system ID is a globally unique identifier representing a VAL system.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
7.7 VAL Stream ID
|
A VAL Stream ID is an identity used by the VAL server to identify a VAL stream.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
8 Application of functional model to deployments
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
8.1 General
|
This clause describes deployments of the functional model specified in clause 6.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 and provides SEAL services to the VAL server(s) deployed in the VAL service provider domain. SEAL servers deployed in multiple PLMN operator domain are not interconnected.
Figure 8.2.1-2: SEAL server(s) deployed in multiple PLMN operator domain without interconnection between SEAL servers
Figure 8.2.1-3 illustrates the deployment of SEAL servers in multiple PLMN operator domain and provides SEAL services to the VAL server(s) deployed in the VAL service provider domain. SEAL servers deployed in multiple PLMN operator domain are interconnected.
Figure 8.2.1-3: SEAL server(s) deployed in multiple PLMN operator domain with interconnection between SEAL servers
Figure 8.2.1-4 illustrates the deployment of SEAL servers in a single PLMN operator domain and provides SEAL services to the VAL server(s) deployed in the VAL service provider domain. SEAL servers deployed in a single PLMN operator domain are interconnected.
Figure 8.2.1-4: SEAL server(s) deployed in a single PLMN operator domain with interconnection between SEAL servers
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 3GPP network system in multiple PLMN operator domain.
Figure 8.2.2‑2: Deployment of SEAL server(s) with connections to 3GPP network system in multiple PLMN operator domains
Figure 8.2.2‑3 illustrates the deployment of multiple SEAL servers in the VAL service provider domain where SEAL server 1 and SEAL server 2 connect with 3GPP network system of PLMN operator domain 1 and PLMN operator domain 2 respectively. The SEAL servers interconnect via SEAL-E and support the VAL service provider domain applications for the VAL UEs connected via both the PLMN operator domains.
Figure 8.2.2‑3: Distributed deployment of SEAL servers in VAL service provider domain
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9 Location management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.2 Functional model for location management
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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 model is specified in this clause.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 support for location management functions to the VAL client(s) over LM‑C reference point. The VAL server(s) communicate with the location management server over the LM-S reference point. The VAL client communicates with the VAL server over the VAL-UU reference point which is outside the scope of this document.
The location management server communicates with the SCEF via T8 reference point to obtain location information from the underlying 3GPP network system. The location management server obtains location information from the NEF via N33 reference point by mechanism defined in clause 5.2.6.2 of 3GPP TS 23.502 [11]. The location management server may obtain location information from the GMLC via Le reference point defined in clause 4.4.1 of 3GPP TS 23.273 [50]. The location management server may optionally obtains location information from the 3rd party location server via LM-3P reference point.
When the fused location function is present, the location management server, may use the location information from multiple sources to determine a more accurate UE location. The fused location function may select one or more location sources and location methods based on the requested location QoS which obtained from the location management server.
The location management server supports to report the requested value-added location information (e.g. Geofencing monitoring events, history location data, prediction related to UE location, etc.) to the VAL server over LM-S reference point.
NOTE 1: Location information from LCS of 4G system is not exposed by SCEF.
NOTE 2: Non-3GPP access used by the UE is out of scope of the present document.
Figure 9.2.2-2 exhibits the service-based interfaces for providing and consuming location management services. The location management server could provide service to VAL server and location management client through interface Slm.
Figure 9.2.2-2: Architecture for location management – Service based representation
Figure 9.2.2-3 illustrates the service-based representation for utilization of the 5GS network services based on the 5GS SBA specified in 3GPP TS 23.501 [10].
Figure 9.2.2-3: Architecture for location management utilizing the 5GS network services based on the 5GS SBA – Service based representation
Figure 9.2.2-4 illustrates the service-based representation for utilization of the Core Network (5GC, EPC) northbound APIs via CAPIF.
Figure 9.2.2-4: Utilization of Core Network Northbound APIs via CAPIF – service based representation
The Location management server acts as authorized API invoker to consume services from the Core Network (5GC, EPC) northbound API entities like SCEF, NEF, SCEF+NEF which act as API Exposing Function as specified in 3GPP TS 23.222 [6].
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.2.4 Functional entities description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.2.4.1 General
|
The functional entities for location management SEAL service are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 location management client between the two UEs.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 location management service may optionally obtain location information from 3rd party location servers via LM-3P reference point. The LM-3P reference point is out of scope of this specification.
The location management server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 [8]. The location management server also supports interactions with the corresponding location management server in distributed SEAL deployments. The location management server, with the fused location function, may combine/aggregate location information from multiple sources to provide a more accurate UE location. The location management server also supports to report the value-added location information (e.g. Geofencing monitoring events, history location data, prediction related to UE location, etc.) to the VAL server.
NOTE: The accuracy of location information acquired from 4G system via T8 reference point is not higher than cell level (ECGI) for E-UTRAN.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.2.5 Reference points description
| |
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.2.5.1 General
|
The reference points for the functional model for location management are described in the following subclauses.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 for the location management server to receive location information report from the location management client. The LM-UU reference point shall use SIP-1 and SIP-2 reference points for subscription/notification related signalling. And for transport and routing of location management related signalling LM-UU reference point uses the HTTP-1 and HTTP-2 signalling control plane reference points.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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].
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 receive location information from location management server. The LM-S reference point shall use SIP-1 and SIP-2 reference points for subscription/notification related signalling. And for transport and routing of location management related signalling LM-S reference point uses the HTTP-1 and HTTP-2 signalling control plane reference points.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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].
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3 Procedures and information flows for Location management (on-network)
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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 related to location management (e.g. VAL server obtains UE’s location information or LM-Uu and LM-S in relation to the VAL service ID) are out of scope of this specification.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2 Information flows for location information
| |
d23d1b9504aafd6c2e98868ecaffb278
|
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 identity of the VAL UE.
VAL service ID
O
Identity of the VAL service for which the location reporting configuration is requested.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
Information element
Status
Description
Identity
M
Identity of the VAL user or VAL group to which the location reporting configuration is targeted or identity of the VAL UE.
Requested location information
O
(see NOTE 1)
Identifies what location information is requested
Requested location access type (see NOTE 2)
O
(see NOTE 1)
Identifies the location access type for which the location information is requested, e.g. as described in TS 23.273 [50] and TS 29.572 [51].
Requested positioning method
O
(see NOTE 1)
Identifies the positioning method for which the location information is requested, e.g. as described in TS 23.273 [50] and TS 29.572 [51].
Requested velocity information
O
(see NOTE 1)
It indicates the velocity of the requested VAL users/UEs is needed to report.
Triggering criteria
O
(see NOTE 1)
Identifies when the location management client will send the location report as specified in table 9.3.2.4-2. The triggering may be e.g., SAI changes, ECGI changes, RAT changes.
Minimum time between consecutive reports
O
(see NOTE 1)
Defaults to 0 if absent otherwise indicates the time interval between consecutive reports
NOTE 1: If none of the information element is present, this represents a cancellation for location reporting.
NOTE 2: The non-3GPP access as defined in 23.273[50] and TS 29.572 [51] is out of scope of the present specification.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 information report
Information element
Status
Description
Set of identities
M
Set of identities of the reporting VAL users or VAL UEs
Triggering event
M
Identity of the event that triggered the sending of the report. The triggering event may be e.g., SAI changes, ECGI changes, RAT changes.
Location Information
M
Location information. For LM-UU reference point, it may include UE location information via non-3GPP positioning technologies (e.g. GNSS, Sensor, TBS, WLAN, Bluetooth) as described in 3GPP TS 37.355 [53].
Velocity information
O
(NOTE 1)
Velocity information of the reporting VAL users or VAL UEs.
Failure Reason
O
(NOTE 2)
Indicates the failure reason when the LM Client cannot obtain the requested UE’s location information (e.g. the target VAL UE has moved away, or required positioning method is not supported by target VAL UE)
Timestamp
O
Timestamp of the location report
NOTE 1: The definition of the velocity refers to 3GPP TS 23.271 [60].
NOTE 2: This element is only applicable when the Location information IE is null.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
Description
Identity list
M
List of VAL users or VAL UEs whose location information is requested
VAL service ID
O
Identity of the VAL service for which the location information is requested.
Requested location information
O
Identifies what location information is requested
Requested location access type
(NOTE 4)
O
(NOTE 1)
Identifies the location access type for which the location information is requested, e.g. as described in TS 23.273[50] and TS 29.572[51].
Requested positioning method
O
(NOTE 1)
Identifies the positioning method for which the location information is requested, e.g. as described in TS 23.273[50] and TS 29.572[51].
If the requested VAL user/UE is not the receiving VAL user/UE hosting the location management client, the UE positioning method includes PC5 SEAL LM, BT, WiFi.
Location QoS
O
(NOTE 3)
Definition of the location Quality of Service for which the location information is requested (see NOTE 2).
Requested velocity indication
O
(NOTE 5)
It indicates whether the velocity of the requested VAL users/UEs is needed.
List of association IDs
O
(NOTE 6)
Identifies list of associations with other UEs may share the location information when they are at the same location.
NOTE 1: This e element is only applicable for request sent from the location management server to the location management client.
NOTE 2: The definition of location QoS has been defined in clause 4.1b of TS 23.273 [50] and the clause 6.1.6.2.13 of TS 29.572 [51].
NOTE 3: The element is only applicable for the information flow from the VAL server to the location management server.
NOTE 4: The non-3GPP access as defined in TS 23.273[50] and TS 29.572[51] is out of scope of the present specification.
NOTE 5: The definition of the velocity refers to 3GPP TS 23.271 [60].
NOTE 6: The association IDs are known to the UE based on offline methods and are out of scope of this specification. The requestor can be part of multiple associations and one association can have two or more UEs.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 requesting authorized VAL user or VAL UE or VAL server
Identity
M
(see NOTE 1)
Identity of the requested VAL user or VAL UE
VAL service ID
O
Identity of the VAL service for which the location reporting trigger is set.
Immediate Report Indicator
O
(see NOTE 2)
Indicates whether an immediate location report is required
Requested location information
O
(see NOTE 2)
Identifies what location information is requested. This information element may be represented as VAL service area ID(s) when this information flow from VAL server to the location management server.
Triggering criteria
O
(see NOTE 2)
Identifies when the requesting client/VAL server is expecting to receive the location report from the requested VAL user/ VAL UE as specified in table 9.3.2.4-2.
Minimum time between consecutive reports
O
(see NOTE 2)
Defaults to 0 if absent otherwise indicates the interval time between consecutive reports
Endpoint information
O
Information of the endpoint of the requesting VAL server to which the location report notification has to be sent. It is provided if Immediate Report Indicator is set to required.
Adaptive reporting
O
It indicates the request for an adaptive location reporting by dynamically adjusting the configuration. Following are possible values:
- "DIRECT UPDATE", indicates the SEAL LMS to directly update the SEAL LM client once configuration is adjusted; or
- "SUGGESTIVE UPDATE", indicates that the VAL Server subscribes to receive the suggested configurations from the SEAL LMS. The related notifications shall be sent by SEAL LMS before updating to the SEAL LM client.
NOTE 1: The identity of the requesting VAL user/UE/VAL server and the requested VAL user/UE should belong to the same VAL service.
NOTE 2: At least one of these rows shall be present.
Table 9.3.2.4-2: Location reporting Triggering criteria
Information element
Status
Description
Frequency of reporting
O
It indicates the requested frequency of reporting. The reporting frequency may be periodic or event-triggered.
Reporting periodicity
O
If the Frequency of reporting is periodic, the reporting periodicity shall be provided.
Location change condition
O
(see NOTE)
It indicates the location change condition when the reporting shall occur, e.g., VAL user or VAL UE changes a cell, NodeB, TA, RA, WLAN access network, civic address, GPS coordinates, SAI, ECGI, RAT, VAL service area.
If the Frequency of reporting is event-triggered, this IE shall be provided.
Inside or outside indication
O
(see NOTE)
It indicates the condition when the reporting shall occur, i.e., the VAL user or VAL UE is inside or outside the locations represented by the VAL service area ID(s).
Reporting schedule
O
It indicates the requested reporting schedule, e.g., days of the week and/or time period for the location reporting.
NOTE: Triggering criteria based on the VAL service area represented by the VAL service area ID(s) may be provided when this information flow is from the VAL server to the location management server.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
Status
Description
Identity
M
Identity of the requesting VAL server/VAL user or VAL UE (see NOTE 3)
Identities list
M
List of VAL users or VAL UEs whose location information is requested.
VAL service ID
O
Identity of the VAL service for which the location information is subscribed.
Time between consecutive reports
M
It indicates the interval time between consecutive reports
Supplementary location information indication
O
Indicates that supplementary location information is required.
Location QoS
O
(NOTE 2).
Definition of the location Quality of Service for which the location information is requested (see NOTE 1).
Indication for the location data statistic
O
It indicates whether the statistic/calculation of target UE location data is needed per e.g. time/location.
Requested time information
O
(NOTE 4)
It indicates the time information when the target UE location data is calculated per time.
Requested location information
O
(NOTE 4)
It indicates the location information when the target UE location data is calculated per location.
Requested velocity indication
O
It indicates whether the velocity of the requested VAL users/UEs is needed.
NOTE 1: The definition of location QoS has been defined in clause 4.1b of TS 23.273 [50] and the clause 6.1.6.2.13 of TS 29.572 [51].
NOTE 2: The element is only applicable for the information flow from the VAL server to the location management server.
NOTE 3: This information element shall not be updated via location information subscription update procedure in clause 9.3.7a.
NOTE 4: This information element only applies when the indication for the statistic of target UE location data is included.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
Status
Description
Identity
M
Identity of the requesting VAL server/VAL user or VAL UE
Subscription status
M
It indicates the subscription result
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 be notified
Identity (see NOTE 2)
O
Identity of the VAL user or VAL UE subscribed to location of another VAL user or VAL UE (see NOTE 1)
Subscription ID (see NOTE 2)
O
Subscription identity related to VAL server subscription with location management server for location information notification.
Triggering event
M
Identity of the event that triggered the sending of the notification
Location Information
M
Location information
Velocity information
O
Indicates the velocity of the target UE for which the location information is requested.
Statistic of location data
O
Indicates the statistic result of target UE location data per temporal/spatial granularity as requested.
Timestamp
O
Timestamp of the location report
NOTE 1: This is only used for location management server sends location information notification to the VAL user or VAL UE who has subscribed the location.
NOTE 2: Either Identity or Subscription ID shall be included.
9.3.2.7a Void
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
Information element
Status
Description
Identity
M
Identity of the requesting authorized VAL user or VAL UE or VAL server
Identity
M
Identity of the requested VAL user or VAL UE
VAL service ID
O
Identity of the VAL service for which the location reporting configuration is requested to be cancelled.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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. geographic area or VAL service area ID). The information is also used for Geofencing service.
> Shape type
O
It includes the Geofencing location area represented by different types of shape (e.g., polygon or circle) as defined in 3GPP TS 29.572 [51].
> Area Coordinates
O
Geographical coordinates of shape as defined in 3GPP TS 29.572 [51].
Application defined proximity range information
M
Description of the range information over which the UE(s) information is required.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 of UEs information (see NOTE)
O
The information of the UEs which were detected in the application defined proximity range. The list can be empty.
>UE ID
M
The identifier of VAL UE or VAL user.
>Location information
M
Location information of UE within the application defined proximity range
> VAL service ID
O
Indicates the VAL service identified associated with UE ID information flow.
NOTE: This IE shall be included when the Result indicates success.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
Target Identity
M
Identifier of the target VAL users or VAL UEs whose location monitoring is requested to be monitored in a given location (see NOTE).
Area of Interest
M
Geographic area location information where the VAL server wishes to monitor the VAL UE's location adherence. This could be geographical co-ordinates or VAL service area identified by the VAL service area ID.
Alternatively, it includes identifier of the reference VAL user or VAL UE and its proximity range.
Notify Interval
M
Periodic time interval in which the location management server needs to notify the target VAL UE's location information to the VAL server.
Notification Target URI
M
Target URI where the VAL server wishes to receive the notifications about target VAL UE's location.
Timeout
O
A timeout period when subscription response is not received.
Interested notification information
O
One or more interested notification events (e.g. Notify Absence, Notify Presence, Notify Mismatch Location and Notify Unknown) the VAL server can subscribe to.
Dynamic geofencing conditions
O
Temporal, connectivity and/or spatial conditions for the reference VAL UE.
NOTE: This information element shall not be updated via monitor location subscription update procedure in clause 9.3.2.12a.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 indicates the subscription result
9.3.2.12a Monitor location subscription update procedure
Figure 9.3.2.12a -1 illustrates the high level procedure for allowing a VAL server update an existing monitor location subscription at the location management server.
Pre-conditions:
- the VAL server has an active monitor location subscription at the location management server.
Figure 9.3.2.12a -1: Monitor location subscription update procedure
1. When the VAL server decides to update an active monitor location subscription, it sends a monitor location subscription update request to the location management server including the information specified in table 9.3.2.11.
2. The location management server shall check if the VAL server is authorized to update the subscription.
3. If the VAL server is authorized to update the subscription, the location management server updates the monitor location subscription.
4. The location management server sends a monitor location subscription update response to the VAL server including the information as specified in table 9.3.2.12.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 one of the following:
"Notify_Mismatch_Location" – When the location information of the target VAL UE, from the location management client and the core network do not match, or when the location management server determined area of interest result based on location management client location and the core network reported area of interest result do not match.
"Notify_Absence" – When the target VAL UE's current location is deviating from the VAL server's area of interest information.
"Notify_Presence" – When the target VAL UE's current location is within the VAL server's area of interest information.
"Notify_Unknown" – When the location management server cannot determine whether the target VAL UE's current location is within the VAL server's dynamic area of interest information or not.
Identity
M
Identifier of the VAL UE whose location information is reported.
Location
M
Current location of the target VAL UE.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 or SEAL Server
VAL service ID
O
Identity of the VAL service for which the VAL server requests (e.g.Geofencing).
Location Information criteria
M
Location information to be monitored.
It includes the geographic location information or a VAL service area identified by the VAL service area ID or a reference UE along with the application defined proximity range from the reference UE. This information also applies for Geofencing service.
Triggering events
O
It indicates the triggering events to be monitored and identifies when the server will send the notification (e.g. distance travelled). This information also applies for Geofencing service.
> UEs moved in/out
O
It indicates to monitor the UE(s) moving in/out of the area as defined in location information criteria,
> Numbers of UEs moved in/out
O
Indicates the numbers of UE(s) moving in/out of the area as defined in location information criteria are to be monitored,
> Time of UEs moved in/out
O
Indicates the time stamp/time duration of UE(s) moving in/out of the area as defined in location information criteria is to be monitored,
Time between consecutive reports
O
It indicates the interval time between consecutive reports
Immediate Report Indicator
O
Indicates whether an immediate location report is required
Notification Target URI
M
Target URI where the VAL server wishes to receive the notifications about location area monitoring.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 result
Subscription identity
O
(see NOTE)
If subscription is successful, identifies the subscription
NOTE: This IE shall be present if subscription status is set to success.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 of all VAL UEs who are currently present in the given location area
UEs moved in/out
(see NOTE)
O
List of UEs either moved in to the location area or moved out of the location area
> UEs moved in
O
List of the identities of the VAL UEs who moved in to the given location area since previous notification.
> UEs moved out
O
List of the identities of the VAL UEs who moved out of the given location area since previous notification.
Number of UEs moved in/out
O
Number of the VAL UE(s) who moved in/out the given location area in a given time period.
> Number of UEs moved in
O
Number of the VAL UE(s) who moved in the given location area in a given time period.
> Number of UEs moved out
O
Number of the VAL UE(s) who moved out the given location area in a given time period.
Time of UEs moved in/out
O
The timestamp and time period of UEs either moved in the location area or moved out of the location area.
>Time stamp and time duration of UE moved in
O
The timestamp and time period of UEs who moved in the given location area since previous notification.
>Time stamp and time duration of UE moved out
O
The timestamp and time period of UEs who moved out the given location area since previous notification.
Triggering event
O
Identity of the event that triggered the sending of the notification
Reason
O
It indicates the failure reason for the notification report (e.g., "UE cannot be connected") when the location management server can’t obtain the UE location data.
NOTE: Any one of these shall be present.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 server, VAL UE or SEAL Server
VAL service ID
O
Identity of the VAL service for which the VAL server requests (e.g., Geofencing).
Subscription identity
M
Identifies the subscription
Location Information criteria
M
Location information to be monitored.
It includes the geographic location information or a VAL service area ID or a reference UE along with the application defined proximity range from the reference UE.
This information also applies for Geofencing service.
Triggering events
O
It indicates the triggering events to be monitored and identifies when the server will send the notification (e.g. distance travelled). This information also applies for Geofencing service.
> UEs moved in/out
O
It indicates to monitor the UE(s) moving in/out of the area as defined in location information criteria,
> Numbers of UEs moved in/out
O
Indicates the numbers of UE(s) moving in/out of the area as defined in location information criteria are to be monitored,
> Time of UEs moved in/out
O
Indicates the time stamp/time duration of UE(s) moving in/out of the area as defined in location information criteria is to be monitored,
Time between consecutive reports
O
It indicates the interval time between consecutive reports
Immediate Report Indicator
O
Indicates whether an immediate location report is required
Notification Target URI
O
Target URI where the VAL server wishes to receive the notifications about location area monitoring.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 indicates the request result
|
d23d1b9504aafd6c2e98868ecaffb278
|
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, VAL UE or SEAL Server
Subscription identity
M
Identifies the subscription
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 area information
M
List of one or more VAL service area identifiers.
> VAL service area ID
M
The VAL service area identifier.
> Geographical location list
M
List of one more geographical locations (e.g., co-ordinates) corresponding to the VAL service area ID
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 VAL service area configuration request.
List of VAL service area IDs
O
List of VAL service area IDs
NOTE: This IE shall be present only if the configuration status is set to success.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 UE.
VAL service ID
O
Identity of the VAL service for which the location service is registered.
Location capability
O
The information of location capability of VAL UE for which the location service is registered.
> Location access type
(NOTE 2)
O
(NOTE 1)
Identifies the available location access type of the VAL UE. E.g. as described in TS 23.273[50] and TS 29.572[51].
>Positioning method
O
(NOTE 1)
Identifies the available positioning methods of the VAL UE. E.g. as described in TS 23.273[50] and TS 29.572[51].
List of association IDs
O
(NOTE 3)
Identifies list of associations with other UEs may share the location information when they are at the same location.
NOTE 1: At least one of these rows shall be present.
NOTE 2: The non-3GPP access as defined in TS 23.273[50] and TS 29.572 [51] is out of scope of the present specification.
NOTE 3: The association IDs are known to the UE based on offline methods and are out of scope of this specification. The requestor can be part of multiple associations and one association can have two or more UEs.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 result.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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
Information element
Status
Description
Cancel status
M
It indicates the cancelled result.
|
d23d1b9504aafd6c2e98868ecaffb278
|
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 service area IDs
M
Indicates the list of the requested VAL service area identifiers.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.27 VAL service area obtain response
|
Table 9.3.2.27-1 describes the information flow from a location management server to the VAL server for obtain VAL service area identifiers at the location management server.
Table 9.3.2.27-1: Obtain VAL service area response
Information element
Status
Description
Result
M
Indicates the success or failure for the operation.
List of VAL service area information
O
(see NOTE)
List of one or more VAL service area identifiers.
> VAL service area ID
M
The VAL service area identifier.
> Geographical locations list
M
List of one more geographical locations (e.g., co-ordinates) corresponding to the VAL service area ID.
NOTE: This information element shall be present only if the obtain VAL service area identifier(s) is successful.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.28 VAL service area update request
|
Table 9.3.2.28-1 describes the information flow from a VAL server to a location management for update VAL service area identifiers at the location management server.
Table 9.3.2.28-1: Update VAL service area request
Information element
Status
Description
Identity
M
Indicates the VAL server identity.
List of VAL service area information
M
List of one or more VAL service area identifiers that shall be updated.
> VAL service area ID
M
Indicates the VAL service area identifier.
> Geographical locations
M
Indicates the list of the updated geographical locations (e.g., the geographical coordinates) corresponding to the VAL service area ID.
|
d23d1b9504aafd6c2e98868ecaffb278
|
23.434
|
9.3.2.29 VAL service area update response
|
Table 9.3.2.29-1 describes the information flow from a location management server to the VAL server for update VAL service area identifiers at the location management server.
Table 9.3.2.29-1: Update VAL service area response
Information element
Status
Description
Result
M
Indicates the success or failure for the operation.
VAL service area IDs
O
(see NOTE)
Indicates the list of the updated VAL service area identifiers.
NOTE: This information element shall be present only if the update VAL service area identifier(s) is successful.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.