hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.27.2 Description | This solution proposes to enable differentiating handling for transport level marking for e2e encrypted XRM traffic. The assumption of this solution is as follows:
- The end-to-end encrypted XRM traffic uses RTP over QUIC, IETF draft-ietf-avtcore-rtp-over-quic [8].
- The in-band metadata for the encrypted QUIC packet w... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.27.3 Procedures | The Nnef_AFsessionWithQoS_Create request or Nnef_AFsessionWithQoS_Update request as defined in clause 4.15.6.6 of TS 23.502 [3] can be enhanced accordingly. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.27.4 Impacts on services, entities and interfaces | Editor's note: This clause captures impacts on existing 3GPP nodes, protocols and functional elements. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.28 Solution #28: QoS Flow Mapping Considering the PSI for Multiplexed Data Flows | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.28.1 Key Issue mapping | This solution addresses KI#4: study traffic detection and QoS Flow mapping in 5GS for different media streams multiplexed within a single end-to-end transport connection. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.28.2 Description | In TS 26.522 [20], RTP Header Extension and the guidelines for PDU Set Marking is detailed specified. In the PDU Set Importance field, the importance marking can across bitstreams when a 5-tuple corresponds to more than one bitstream, i.e. Multiplexed streams.
PDU Sets that contain audio data should be assigned a lower... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.28.3 Procedures | The exist procedures can be reused for the interactions between the NFs, e.g. setting up an AF session with required QoS and the PDU Session Modification procedures, as described in clause 4.15.6.6 and clause 4.3.3 of TS 23.502 [3]. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.28.4 Impacts on services, entities and interfaces | AF:
- The AF can provide indicated PSI values in the Packet Filter Set and the protocol description to the PCF during the AF session setup or update with required QoS. Optionally, the mapping assistant information (e.g. the mapping relationship) is provided.
PCF:
- The PCF generates the PCC Rules with SDF filters consi... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.29 Solution #29: KI#4 Support for multiplexed media traffic using RTP header inspection | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.29.1 Key Issue mapping | This solution is for Key Issue #4, which addresses the situation where multiple media streams of the same or different type with potentially different QoS requirements are multiplexed within the same transport layer (L4) traffic flow, meaning they all share the same IP 5-tuple. Applying different QoS treatment to diffe... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.29.2 Description | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.29.2.1 Background | Many XRM applications exchange multiple media streams of various types (video, audio, pose or other sensory information) which may have different QoS requirements. It has become a common practice to multiplex all the streams along with other application traffic into a single (UDP/IP) transport layer traffic flow, i.e. ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.29.2.2 Solution Description | In this solution, the AF can request specific ordinary QoS or PDU Set QoS treatment for traffic flow components (sub-streams) in multiplexed stream it deems require a specified QoS treatment. The sub-streams that require dedicated QoS treatment are mapped into separate QoS Flows. All other PDUs are mapped to a QoS flow... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.29.2.3 Detection of protocols and media streams | This clause explains the protocol and media stream identification rules standardized in the IETF RFCs cited above. The AF may request that one or more of these be detected in the SDF and provide associated QoS or PDU Set QoS requirements. The PCF reflects the AF request in PCC rules provided to the SMF which then deter... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.29.2.4 Extensions needed to 3GPP specifications | This clause outlines the enhancements needed in the 3GPP specifications to support the identification and differentiated QoS treatment for the different media streams and protocols multiplexed into the same transport layer (UDP/IP) traffic flow. The principle in the solution is to map the multiplexed sub-streams that r... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.29.3 Procedures | Figure 6.29.3-1: Procedure for providing traffic flow identification information and QoS requirements for individual media streams or protocols in case several media streams and protocols are multiplexed within the same UDP/IP traffic flow
1. AF requests QoS for specific traffic flows using the Nnef_AFSessionWithQoS se... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.29.4 Impacts on services, entities and interfaces | The main impacts are:
AF:
- Provides the QoS requirements and optionally Protocol Descriptions for the specific protocols or RTP media streams using AFSessionWithQoS by applying the extended Flow Description information.
NEF:
- Receives the extended Flow Description and optionally Protocol Descriptions information from... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.30 Solution #30: Support of dynamic change of traffic burst size | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.30.1 Key Issue mapping | The solution addresses Key Issue #5: QoS Handling when Traffic Characteristics Change Dynamically. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.30.2 Description | For XR or other interactive media services with traffic bursts (e.g. Media streaming, cloud gaming services), the application layer's network requirements could be quite dynamic. Typically, the size of data burst in XRM services could vary in a wide range. To ensure the occasionally big bursts can be transferred within... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.30.3 Procedures | The existing AF Session with required QoS procedure in clauses 4.15.6.6 and 4.15.6.6a of TS 23.502 [3] can be reused to provision the protocol description and the indication that the traffic burst size can change dynamically by AF. The PCC rule is provided by PCF to the SMF using the existing PCF initiated SM Policy As... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.30.4 Impacts on services, entities and interfaces | AF:
- provides an indication which indicates the traffic burst size can change dynamically.
PCF:
- based on the AF input and/or local configuration, generates the PCC rule.
SMF:
- indicates the UPF to identify and mark the burst size and provides the protocol description if available.
UPF:
- identifies the burst size a... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.31 Solution #31: Identifying Traffic Flows from the Tethered Devices | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.31.1 Key Issue mapping | This solution addresses Key Issue #8, "Enhancement for UE with the tethered devices". |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.31.2 Description | In some XR services, the end device(s) used for consuming XRM services may not be the UE but the device(s) that are tethered to the UE. For example, AR glasses may be tethered to the UE for sending orientation related traffic.
Differentiated QoS handling is required for traffic from these tethered devices, not only acc... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.31.3 Procedures | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.31.3.1 AF/AS Based Procedure | Figure 6.31.3-1 is a procedure that is initiated based on an API invocation from the AF/AS.
Figure 6.31.3.1-1: Setting up QoS for Tethered Devices Based on AS/AF API Invocation
1. The Application in the UE (e.g. the RTC endpoint) sends an SDP message to the AS with information related to delay values associated with tr... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.31.4 Impacts on services, entities and interfaces | - UE Application:
- Provides delay values and device identifiers that are associated with flows that belong to tethered devices to the AS in an SDP message.
- AS:
- Receives the delay values and device identifiers that are associated with flows that belong to tethered devices to the AS in an SDP message.
- PCF:
- Recei... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.32 Solution #32: Tethered traffic handling by reusing N5CW and trusted WLAN access | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.32.1 Key Issue mapping | This solution addresses KI#8. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.32.2 Description | For cloud gaming and XR services, tethering is very important to support the WiFi-capable devices into 5G network as shown in Figure 6.32.2-1.
Figure 6.32.2-1 Scenario of Tethering for XR and Media Services
In this scenario, the tethering UE establish PDU session toward UPF using the NG-RAN and 5GC resources for both u... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.32.3 Proposed architecture reusing N5CW access | This solution intends to reuse and extend the existing architecture specified in TS 23.501 [2] as shown with the following functional assumptions as shown in Figure 6.32.3-1. The major impacts is that the tethering UE needs to implement the TWAP and TWIF function which has already been specified.
Figure 6.32.3-1: Propo... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.32.4 Procedures | Figure 6.32.4-1: Procedure of Tethering for XR and Media Services reusing trusted WLAN access
0. Tethering UE is pre-configured to be able to provide trusted WLAN access to XRM device.
1. Tethering UE switches on its hotspot.
2. Tethering UE carries out authentication and authorization with 5GC NF, and the hotspot WLAN... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.32.5 Impacts on services, entities and interfaces | Tethering UE (includes SIM):
- Need to implement the TWAP and TWIF functions specified in 3GPP and identify the uplink XRM traffic and also performs QoS mapping between N5CW access and 5GS QoS flow.
Editor's note: The impacts of UE terminating N2/N3 interfaces to AMF and UPF need to be evaluated by SA WG3.
5GC:
- Need ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.33 Solution #33: Available Data Rate Monitoring and Exposure | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.33.1 Key Issue mapping | This solution is for KI #9 Enhancement for XR related network information exposure. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.33.2 Description | The monitoring data rate defined in clause 5.45.4 of TS 23.501 [2] is the data rate currently used by the QoS Flow. This monitoring data rate is not useful for the XRM AS (Application Server) in the DN), since the XRM AS can measure such used data rate by itself.
However, the available data rate of the QoS Flow is bene... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.33.3 Procedures | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.33.3.1 Exposure of Available Data Rate via User Plane | Figure 6.33.3.1-1: Quick Exposure of Available Data Rate via User Plane
0. The PDU Session for the XRM service is established.
1. If the XRM AF does not locate at trusted domain, the AF sends the Nnef_AFsessionwithQoS_Create Request to the NEF. If the XRM AF is located at trusted domain, the AF sends the Npcf_PolicyAut... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.33.3.2 Available Data Rate Exposure via Control Plane | Figure 6.33.3.2-1: Quick Available Data Rate Exposure via Control Plane
0. The PDU Session for the XRM service is established. A QoS Flow is established for the XRM service stream and UL and or DL available data rate monitoring (i.e. produce and report) is requested from the AF to NG-RAN via NEF, PCF and SMF as describ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.33.4 Impacts on services, entities and interfaces | AF:
- Provides the available data rate monitoring and exposure requirements associated with the QoS requirements for the service data flow.
- Change its following near future codec based on the received available data rate exposed from the 5G network.
PCF:
- Generates the PCC rules including available data rate monitor... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.34 Solution #34: PDU Set Performance exposure | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.34.1 Key Issue mapping | The solution addresses KI#9: Enhancement for XR related network information exposure. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.34.2 Description | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.34.2.1 General | For rel-18, the granularity of PDU Set and PDU Set QoS are introduced, however, the real PDU Set performance is not estimated and exposed to the Application, e.g. PDU Set Delay and/or PDU Set Loss Rate suffered for a data stream in 5GS. For a data stream which request PDU Set QoS before, the server also cares the real ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.34.2.1 PDU Set Delay | The PDU Set delay is a different measure dimension with the packet delay.
- In legacy, the packet delay refers to the time that a packet delayed between the UE and the N6 termination point at the UPF. It is a combination of the RAN part of UL/DL packet delay and UL/DL packet delay between NG-RAN and PSA UPF. The NG-RAN... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.34.2.3 PDU Set Loss Rate Measurement and Reporting | For each PDU Set sent by the NG-RAN, the NG-RAN starts to record how many PDUs within the PDU set are sent to the UE successfully and/or how many PDUs in the PDU set are lost (not sent to the UE successfully):
- If the NG RAN uses a default criterion that if any PDU of the PDU Set is lost, the PDU Set is considered los... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.34.3 Procedures | Figure 6.34.3-1: PDU Set Performance exposure
1. AF requests to subscribe the event notification for DL PDU Set Delay and/or PDU Set loss rate, which is a part of QoS Monitoring parameter(s).
2. Based on QoS monitoring request from AF or based on PCF local policy, the PCF generates the QoS Monitoring policy for the cor... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 6.34.4 Impacts on services, entities and interfaces | <For PDU Set Delay exposure>
AF:
- Requests of DL PDU Set Delay monitoring via NEF or directly to PCF.
PCF:
- Generates the QoS Monitoring policy for DL PDU Set Delay based on AF request.
- Exposures the measured result of DL PDU Set Delay.
SMF:
- Sends QoS monitoring request for DL PDU Set Delay NG-RAN and PSA UPF bas... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 7 Overall Evaluation | Editor's note: This clause provides evaluations of different solutions. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8 Conclusions | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.1 Conclusions for Key Issue #1 | |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.1.1 Conclusion for KI#1_other PDU Set handling | The following agreement is considered for #1 for other PDU Set handling:
1. In the case of no DL PDU Set QoS parameters provided by the AF, according to the Protocol Description and PSA UPF supports of PDU Set Information marking, the SMF sends NG-RAN a new indicator indicating the DL PDU Set Information Marking is sup... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.1.2 Conclusion for KI#1_QoS Notification without AQP | The following interim agreement is considered for #1_PDU Set handling support or not indications in UL and/or DL and QoS notification:
1. In order to support QoS Notification Control "GFBR cannot be guaranteed or can be guaranteed again" (see clause 5.7.2.4 of TS 23.501 [2]), for a GBR QoS flow with the QoS profile con... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.1.3 Conclusion for KI#1_AQP | The following conclusion principles are agreed for key issue #1_AQP.
1. The AF may provide Alternative Service requirements to 5GC which may contain the UL and/or DL PDU Set QoS Parameters (i.e. UL PSDB, DL PSDB, UL PSER and/or DL PSER).
2. Based on the Alternative Service Requirements from AF, the PCF generates PCC ru... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.1.4 Conclusion for KI#1_AL-FEC | Normative work for AL-FEC awareness at NG-RAN will be based on the following principles:
- When requesting or updating QoS for a DL flow, an AF may provide to PCF/NEF - together with PDU Set QoS parameters - the content ratio for the flow. An AF may provide either PSIHI or content ratio for a flow.
- If a PCF receives ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.2 Conclusions for Key Issue #2 | The following principles are recommended to be included in the conclusions:
- The normative R19 work will apply to UE to XRM server communication not to UE-UE XRM communication.
- The XRM metadata shall be encrypted and integrity protected between the UPF and the AS.
- The PSA UPF supporting the below functionality cou... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.3 Conclusions for Key Issue #3 | Leverage PDU Set QoS information for DSCP marking over N3/N9 in the transport network: the following conclusions are agreed for the baseline functionality:
- For every QoS Flow, the SMF shall determine the transport level packet marking value (e.g. the DSCP in the outer IP header) based on the 5QI, the Priority Level (... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.4 Conclusions for Key Issue #4 | The following aspects are concluded as principles for normative work:
1. The AF may provide QoS requirements for media flows and additional packet filters as part of "AF session with required QoS". The detectable media flows that require different QoS treatment are mapped to distinct QoS Flows. If the AF does not provi... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.5 Conclusions for Key Issue #5 | The following aspects are concluded as principles for the normative work:
- Support the provision of the DL traffic characteristics information changed dynamically to the RAN in-band for the DL resource scheduling.
1. The AF may indicate to the NEF/PCF to mark the Burst size.
2. Based on the PCC rule and/or local confi... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.6 Conclusions for Key Issue #6 | The following aspects are concluded as principles for the normative work:
1. Dedicated 5G QoS Flow(s) and non-3GPP access resources (e.g. IPsec Child SAs) are used for carrying L4S enabled IP traffic.
2. For wireline access:
a. ECN marking for L4S is supported in W-AGF. It is controlled via N2 signalling (Indication of... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.7 Conclusions for Key Issue #7 | The following aspects are concluded as principles for the normative work:
1. For wireline access:
a. W-AGF:
i. In addition to PDU QoS parameters, uses the PDU Set QoS parameter(s) sent by SMF over N2 to determine W-UP resources.
ii. Uses PDU Set Information received in the GTP-U header over N3 to identify PDU Sets.
b. ... |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.8 Conclusions for Key Issue #8 | There will be no normative work for this key issue. |
69b445c06689b3757ef2091eeb35eb80 | 23.700-70 | 8.9 Conclusions for Key Issue #9 | The following aspects are concluded for the normative work: - For GBR QoS Flow, exposure of available data rate: - Based on the AF requests, the PCF instructs SMF to enable the available data rate report and exposure for a GBR QoS Flow. - Following the instruction of SMF: - The NG-RAN reports the available data rate to... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 1 Scope | The present document is a technical report which identifies the SA1 requirements and the potential vertical requirements for location services and proposes the application architecture requirements, key issues, and solutions to address the enhanced location capabilities based on the current vertical application enabler... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 3 Definitions of terms, symbols and abbreviations | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 3.1 Terms | For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
A-ADRF Application layer - Analytical Data Repository Function
AD... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 4 Architectural assumption and requirements | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 4.1 Architectural assumption | [AA-4.1-a] The application enabled layer architecture for the enhanced location services should take the location management which is specified in clause 9 of 3GPP TS 23.434 [9] as the baseline.
[AA-4.1-b] The location capabilities and the positioning methods used in the application enabled layer should follow the one ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 4.2 Architectural requirements | This sub-clause specifies the functional requirements for any application enablers referred in the TR.
[AR-4.2-a] The SEAL-LM shall enable collecting target UE location via other UEs close to the target UE.
[AR-4.2-b] The SEAL-LM shall support Geofencing request from the VAL server.
[AR-4.2-c] The SEAL-LM shall support... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 5 Key Issues | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 5.1 Key Issue #1: Support of Geofencing | Geofencing is a type of location-based marketing and advertising. A mobile app or software uses e.g. the Global Positioning System (GPS), radio frequency identification (RFID), Wi-Fi or cellular data to define a virtual geographical boundary and trigger a specific alert or push notification when a device enters or exit... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 5.2 Key Issue #2: Support of history tracing request or playback | Activity history can help keep track of the things you do on your device, such as the apps and services you use, the files you open, and the websites you browse.
In the enterprise, the role of history tracing is mainly reflected in management and event backtracking. In the current positioning system for personnel safet... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 5.3 Key Issue #3: Location QoS improvement | The 3GPP TS 22.261 [2] has specified low latency and high accuracy positioning requirements of 5G for the support of V2X, Rail communication, etc. And the 3GPP TS 22.104[13] also has specified low power, high accuracy positioning use cases and example scenarios for Industrial IoT devices. These applications all request... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 5.4 Key Issue #4: Enhancement to support location information exposure | In Rel-17 and Rel-18, the Location Management architecture and functional model in SEAL has introduced to support the “Monitoring Location Deviation” and “Location area monitoring” functions and procedures. Utilizing these functions, the LM server could monitor the VAL UE's location information periodically and notify ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 5.5 Key Issue #5: Support for ranging/sidelink positioning services | Ranging-based services are the applications utilizing the distance between two UEs and/or the direction of one UE from the other one. In 3D case, direction includes horizontal direction and elevation direction. Ranging-based services can apply to a variety of verticals, such as smart home, smart city, smart transportat... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 5.6 Key Issue #6: Support of location services for multiple USIMs/UEs sharing the same location | There are several scenarios about multiple UEs with standalone USIMs may share the same location. Such as a multi-USIM UE, a vehicle with multiple vehicle-mounted devices, wearable devices belonging to a person, etc.
There is a common characteristic for these scenarios that these multiple UEs with standalone USIMs coul... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6 Solutions | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.0 Mapping of solutions to key issues | Table 6.0-1: Mapping of solutions to key issues
KI # 1
KI # 2
KI # 3
KI # 4
KI # 5
KI # 6
Sol #1
X
Sol #2
X
Sol #3
X
Sol #4
X
Sol #5
X
Sol #6
X
Sol #7
X
Sol #8
X
Sol #9
X
Sol #10
X
Sol #11
X
Sol #12
X |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.1 Solution #1: Target UE Location provided by surrounding UEs. | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.1.1 Description | In a vertical case like V2X, UEs can move fast and obtained UE location information from SEAL LM service can be further enhanced with more data source to improve accuracy. If a UE is temporarily out of RAN coverage or served by congested RAN, indirect location retrieval via surrounding UEs via D2D methods is also benef... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.1.2 Solution evaluation | This solution addresses KI#3 about how to provide more accurate UE location exposure by additionally collecting target UE location via other UEs close to the target UE.
NOTE: Different technology (e.g. BT, WiFi, RAN) has different accuracy in positioning. The LM server can, based on its internal algorithm, consolidate ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.2 Solution #2: Application enabled Geofencing | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.2.1 Description | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.2.1.1 General | This solution addresses the key issue #1: Support of Geofencing. The clause 6.2.1.2-1 describes the procedure of Geofencing subscription/unsubscribe request/response and the clause 6.2.1.3-1 describes the procedure of Geofencing UE(s) information request/response. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.2.1.2 Procedure of Geofencing subscription/unsubscribe request | The figure 6.2.1.2-1 describes the Geofencing subscription/unsubscribe procedure which could reuse the procedure as defined in clause 9.3.12 of TS 23.434 [9] with some clarification and enhancements for Geofencing requirements (e.g. support Geofencing criteria based on LCS QoS and/or time/area/space/amount granularity)... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.2.1.3 Procedure of Geofencing UE(s) Information request/response | The figure 6.2.1.3-1 describes the Geofencing UE(s) information request/response procedure based on the procedure defined in clause 9.3.10 of 3GPP TS 23.434 [9].
Figure 6.2.1.3-1: Procedure of Geofencing UE(s) information request/response
1. The VAL server (i.e., Vertical Application Server) sends Geofencing UE(s) info... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.2.2 Solution evaluation | The solution addresses KI#2 to support Geofencing requests from VAL server based on current SEAL-LM architecture and functional model.
The Geofencing subscription/unsubscribe procedure can reuse the one as defined in clause 9.3.12 of 3GPP TS 23.434 [9] with some clarification and enhancements. The Geofencing UE(s) info... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.3 Solution #3: Application enabled history tracing | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.3.1 Description | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.3.1.1 General | This solution addresses the key issue #2: Support of history tracing request or playback.
The figure 6.3.1.2-1 describes the procedure of querying for location history in application enabled layer. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.3.1.2 Procedure of querying for history location | Figure 6.3.1.2-1: Procedure of querying for history location
1. The specific application server sends a location tracing configuration request to the SEAL-LM Server to configure the service in advance. The location tracing configuration request may contain the geographical area for history tracing, events or conditions... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.3.2 Solution evaluation | This solution addresses KI#2 to provide the location history tracing query in application enabled layer to support more value-added location services to the VAL servers via introducing the procedure of location tracing configuration request, location history request, and location tracing configuration cancel, etc.
The ... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.4 Solution #4: Support dynamic Geofencing | |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.4.1 Description | The following procedure is an example of LM provided service to monitor UE location in relation to Area of Interest (AoI), it supports the following additional functions comparing to clause 9.3.11.2 of 3GPP TS 23.434 [9]:
- the AoI consists of a reference UE and proximity range from the reference UE.
NOTE 1: The proxim... |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.4.2 Solution evaluation | This solution enhances LM function described in clause 9.3.11.2 of 3GPP TS 23.434 [9], it addresses KI#1 about how to support dynamic Geofencing and how to provide more UE status in Geofencing.
The impacted entities are VAL server and LM server. |
23aecfe5b8a390666732c3896e7ce3aa | 23.700-72 | 6.5 Solution #5: Location information exposure enhancement |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.