file_name stringlengths 12 116 | answer stringclasses 16 values | question stringlengths 1.25k 6.07k | input stringlengths 1.24k 6.06k | output stringclasses 16 values |
|---|---|---|---|---|
S5-196873.txt | {"WORKING GROUP": "SA5"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 . NPN Non-Public Network; SNPN Stand-alone Non-Public Network; 4 Concepts and background: General: A Non-Public Network (NPN) is a 5GS deployed for non-public use, see TS 23.501 . In contrast to public networks that offer mobile network services to the general public, non-public networks are intended for the sole use of a private entity such as a college or an enterprise. Non-public networks may be deployed on the entity’s defined premises such as a campus or a factory to provide coverage within a specific geographic area. Non-public networks may be deployed in a variety of configurations, utilising both virtual and physical network functions, see TS 22.261 . Specifically, see TS 23.501 , an NPN may be deployed as: - a Stand-alone Non-Public Network (SNPN), i.e. operated by an NPN operator and not relying on network functions provided by a PLMN, or - a Public network integrated NPN, i.e. a non-public network deployed with the support of a PLMN. From the view of 5G-ACIA, non-public networks can be desirable for several reasons, see clause 4 of : - High quality-of-service requirements - High security requirements, met by dedicated security credentials - Isolation from other networks, as a form of protection against malfunctions in the public mobile network. Also, isolation may be desirable for reasons of performance, security, privacy, and safety - Accountability. A non-public network makes it easier to identify responsibility for availability, maintenance, and operation Management of stand-alone non-public networks: An SNPN is deployed as an independent, isolated network. As shown in figure 4.2-1, all SNPN network functions are located inside the logical perimeter of the defined premises (e.g.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 . NPN Non-Public Network; SNPN Stand-alone Non-Public Network; 4 Concepts and background: General: A Non-Public Network (NPN) is a 5GS deployed for non-public use, see TS 23.501 . In contrast to public networks that offer mobile network services to the general public, non-public networks are intended for the sole use of a private entity such as a college or an enterprise. Non-public networks may be deployed on the entity’s defined premises such as a campus or a factory to provide coverage within a specific geographic area. Non-public networks may be deployed in a variety of configurations, utilising both virtual and physical network functions, see TS 22.261 . Specifically, see TS 23.501 , an NPN may be deployed as: - a Stand-alone Non-Public Network (SNPN), i.e. operated by an NPN operator and not relying on network functions provided by a PLMN, or - a Public network integrated NPN, i.e. a non-public network deployed with the support of a PLMN. From the view of 5G-ACIA, non-public networks can be desirable for several reasons, see clause 4 of : - High quality-of-service requirements - High security requirements, met by dedicated security credentials - Isolation from other networks, as a form of protection against malfunctions in the public mobile network. Also, isolation may be desirable for reasons of performance, security, privacy, and safety - Accountability. A non-public network makes it easier to identify responsibility for availability, maintenance, and operation Management of stand-alone non-public networks: An SNPN is deployed as an independent, isolated network. As shown in figure 4.2-1, all SNPN network functions are located inside the logical perimeter of the defined premises (e.g.}
| {"ANSWER": "SA5"} |
R4-1804285.txt | {"WORKING GROUP": "RAN4"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{In this contribution, we propose a band combination, interference analysis, insertion loss and MSD between 3A-5A-7A-7A and n78A-n257A. 2. Text Proposal ----- Unchanged sections omitted ----- 9.X DC_3A-5A-7A-7A_n78A-n257A 9.X.1 Operating bands for DC Table 9.X.1-1: DC band combination of one LTE 4DL/1UL + NR 2DL/1UL 9.X.2 Channel bandwidths per operating band for DC Table 9.X.2-1: Supported bandwidths per DC band combination of one LTE 4DL/1UL + NR 2DL/1UL 9.X.3 Co-existence studies Co-existence studies of this 6DL/2UL DC configuration are already covered by those of the 2DL/2UL and 3DL/2UL captured in TR 37.863-01-01 and TR 37.863-02-01 respectively. Furthermore, harmonics and IMD issues are covered by constituent fallback modes in TR 37.864-41-21. Therefore, additional analysis is not needed.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{In this contribution, we propose a band combination, interference analysis, insertion loss and MSD between 3A-5A-7A-7A and n78A-n257A. 2. Text Proposal ----- Unchanged sections omitted ----- 9.X DC_3A-5A-7A-7A_n78A-n257A 9.X.1 Operating bands for DC Table 9.X.1-1: DC band combination of one LTE 4DL/1UL + NR 2DL/1UL 9.X.2 Channel bandwidths per operating band for DC Table 9.X.2-1: Supported bandwidths per DC band combination of one LTE 4DL/1UL + NR 2DL/1UL 9.X.3 Co-existence studies Co-existence studies of this 6DL/2UL DC configuration are already covered by those of the 2DL/2UL and 3DL/2UL captured in TR 37.863-01-01 and TR 37.863-02-01 respectively. Furthermore, harmonics and IMD issues are covered by constituent fallback modes in TR 37.864-41-21. Therefore, additional analysis is not needed.}
| {"ANSWER": "RAN4"} |
C1-192183.txt | {"WORKING GROUP": "CT1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{2. Discussion 2.1 Current situation in stage 3 In EPC, there is a mechanism defined in TS 24.501 subclause 4.5 on disabling and re-enabling of UE's E-UTRA capability in case of the UE is not allowed to access EPC via E-UTRAN (e.g. due to E-UTRAN access restriction, or no EPC subscription). Typically, the network will reject the attach and TAU request with EMM cause value #15 "no suitable cells in tracking area" together with an extended EMM cause value "E-UTRAN not allowed". However, this mechanism has no functionality to steer and redirect the UE to access 5GC for CIoT optimisations. Once the UE disabled its E-UTRA capability, the UE should firstly try to select another RAT (GERAN, UTRAN, or NG-RAN) of the current PLMN, no guarantee that the UE shall only perform a CN type selection to access 5GC for CIoT optimisations. In EPC, there is another mechanism defined in TS 24.301 subclause 4.9 on disabling and re-enabling of UE's NB-IoT capability in case of the UE access the network via NB-IoT is not allowed (e.g. due to NB-IoT access restriction, or no NB-IoT subscription). Typically, the network will reject the attach and TAU request with EMM cause value #15 together with an extended EMM cause value "NB-IoT not allowed". However, this mechanism also has no functionality to steer and redirect the UE to access 5GC for CIoT optimisations. Once the UE disabled its NB-IoT capability, the UE should firstly try to select a WB-E-UTRAN cell of the current PLMN, and as UE’s NB-IoT capability was disabled, actually the UE cannot access 5GC via NB-IoT for CIoT optimisations. In EPC, there is another mechanism defined in TS 24.301 subclause 5.5.1.2.5 and 5.5.3.2.5 on incompatibility between the CIoT EPS optimizations supported by the UE and what the network supports.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{2. Discussion 2.1 Current situation in stage 3 In EPC, there is a mechanism defined in TS 24.501 subclause 4.5 on disabling and re-enabling of UE's E-UTRA capability in case of the UE is not allowed to access EPC via E-UTRAN (e.g. due to E-UTRAN access restriction, or no EPC subscription). Typically, the network will reject the attach and TAU request with EMM cause value #15 "no suitable cells in tracking area" together with an extended EMM cause value "E-UTRAN not allowed". However, this mechanism has no functionality to steer and redirect the UE to access 5GC for CIoT optimisations. Once the UE disabled its E-UTRA capability, the UE should firstly try to select another RAT (GERAN, UTRAN, or NG-RAN) of the current PLMN, no guarantee that the UE shall only perform a CN type selection to access 5GC for CIoT optimisations. In EPC, there is another mechanism defined in TS 24.301 subclause 4.9 on disabling and re-enabling of UE's NB-IoT capability in case of the UE access the network via NB-IoT is not allowed (e.g. due to NB-IoT access restriction, or no NB-IoT subscription). Typically, the network will reject the attach and TAU request with EMM cause value #15 together with an extended EMM cause value "NB-IoT not allowed". However, this mechanism also has no functionality to steer and redirect the UE to access 5GC for CIoT optimisations. Once the UE disabled its NB-IoT capability, the UE should firstly try to select a WB-E-UTRAN cell of the current PLMN, and as UE’s NB-IoT capability was disabled, actually the UE cannot access 5GC via NB-IoT for CIoT optimisations. In EPC, there is another mechanism defined in TS 24.301 subclause 5.5.1.2.5 and 5.5.3.2.5 on incompatibility between the CIoT EPS optimizations supported by the UE and what the network supports.}
| {"ANSWER": "CT1"} |
S5-161028.txt | {"WORKING GROUP": "SA5"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{If it is to be supported, it needs a contribution to propose it to 28.500. It was commented to include the NS PM flow between NFVO and NM in the Figure. But, NS PM data is not in the scope of the PM-MAMO-VNF WID. EM does not report PM data. It only sends notification to indicate the availability of PM data. The diagram should not use PM job in 3GPP side. 2. The group discuss the VNF related VR PM use case. The group agreed to define the requirements on the reference point for clause 6.1.3 Requirements for Ve-Vnfm-em. The requirements are to be written from the point of view of producer. EM does not report PM data. It only sends notification to indicate the availability of PM data. 3. The group discussed business level and specification level use case of updating performance Threshold Monitor in virtualized network Need an example to justify the need to change the threshold for auto-scaling Need to clarify if these UCs are intended for VNF in 3GPP, or VR in IFA. 3 Minutes: The session was held on Q4 Wednesday January 27, 2016.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{If it is to be supported, it needs a contribution to propose it to 28.500. It was commented to include the NS PM flow between NFVO and NM in the Figure. But, NS PM data is not in the scope of the PM-MAMO-VNF WID. EM does not report PM data. It only sends notification to indicate the availability of PM data. The diagram should not use PM job in 3GPP side. 2. The group discuss the VNF related VR PM use case. The group agreed to define the requirements on the reference point for clause 6.1.3 Requirements for Ve-Vnfm-em. The requirements are to be written from the point of view of producer. EM does not report PM data. It only sends notification to indicate the availability of PM data. 3. The group discussed business level and specification level use case of updating performance Threshold Monitor in virtualized network Need an example to justify the need to change the threshold for auto-scaling Need to clarify if these UCs are intended for VNF in 3GPP, or VR in IFA. 3 Minutes: The session was held on Q4 Wednesday January 27, 2016.}
| {"ANSWER": "SA5"} |
RT-000006.txt | {"WORKING GROUP": "RAN_AH1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Figure 5.4 gives the physical layer transmission chain for the user plane data, i.e., from the level of transport channels down to the level of physical channel. The figure shows how several transport channels can be multiplexed onto one or more dedicated physical data channels (DPDCH). The cyclic redundancy check (CRC) provides for error detection of the transport blocks for the particular transport channel. The CRC can take the length zero (no CRC), 8, 16 or 24 bits depending on the service requirements. The transport block concatenation and code block segmentation functionality performs serial concatenation of those transport blocks that will be sent in one transport time interval and any code block segmentation if necessary. The types of channel coding defined are convolutional coding, turbo coding and no coding. Real‑time services use only FEC encoding while non real-time services uses a combination of FEC and ARQ. The ARQ functionality resides in the RLC layer of Layer 2. The convolutional coding rates are ½ or 1/3 while the rate is 1/3 for turbo codes. The possible interleaving depths are 10, 20, 40 or 80 milliseconds. The radio frame segmentation performs padding of bits. The rate matching adapts any remaining differences of the bit rate so the number of outgoing bits fit to the available bit rates of the physical channels.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Figure 5.4 gives the physical layer transmission chain for the user plane data, i.e., from the level of transport channels down to the level of physical channel. The figure shows how several transport channels can be multiplexed onto one or more dedicated physical data channels (DPDCH). The cyclic redundancy check (CRC) provides for error detection of the transport blocks for the particular transport channel. The CRC can take the length zero (no CRC), 8, 16 or 24 bits depending on the service requirements. The transport block concatenation and code block segmentation functionality performs serial concatenation of those transport blocks that will be sent in one transport time interval and any code block segmentation if necessary. The types of channel coding defined are convolutional coding, turbo coding and no coding. Real‑time services use only FEC encoding while non real-time services uses a combination of FEC and ARQ. The ARQ functionality resides in the RLC layer of Layer 2. The convolutional coding rates are ½ or 1/3 while the rate is 1/3 for turbo codes. The possible interleaving depths are 10, 20, 40 or 80 milliseconds. The radio frame segmentation performs padding of bits. The rate matching adapts any remaining differences of the bit rate so the number of outgoing bits fit to the available bit rates of the physical channels.}
| {"ANSWER": "RAN_AH1"} |
S1-143125.txt | {"WORKING GROUP": "SA1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Interworking between the MCPTT service and TETRA shall support interoperable MCPTT Group Calls between MCPTT Users and TETRA mobile stations and consoles. Interworking between the MCPTT service and TETRA shall support interoperable MCPTT Emergency Group Calls and TETRA emergency calls. Interworking between the MCPTT service and TETRA shall support end-to-end encrypted MCPTT Group Calls between MCPTT Users supporting TETRA codec and encryption and TETRA mobile stations and consoles. Interworking between the MCPTT service and TETRA shall provide a means for an authorized user to initiate an override of a PTT Group call between MCPTT Users and TETRA mobile stations and consoles. Interworking between the MCPTT service and TETRA shall provide a means for an authorized TETRA mobile station or console to initiate an override of a PTT Group call between MCPTT Users and TETRA mobile stations and consoles. Interworking between the MCPTT service and TETRA shall support Group Regrouping that includes both MCPTT Groups and TETRA groups. Interworking between the MCPTT service and TETRA shall support User Regrouping that includes both MCPTT Users and TETRA mobile stations. Interworking between the MCPTT service and TETRA shall support interoperable Talker IDs and TETRA Talker IDs. Interworking between the MCPTT service and TETRA shall support interoperable PTT Private Calls between an MCPTT User and a TETRA mobile station or console. Interworking between the MCPTT service and TETRA shall support end-to-end encrypted PTT Private Calls between an MCPTT User supporting TETRA codec and encryption and a TETRA mobile station or console.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Interworking between the MCPTT service and TETRA shall support interoperable MCPTT Group Calls between MCPTT Users and TETRA mobile stations and consoles. Interworking between the MCPTT service and TETRA shall support interoperable MCPTT Emergency Group Calls and TETRA emergency calls. Interworking between the MCPTT service and TETRA shall support end-to-end encrypted MCPTT Group Calls between MCPTT Users supporting TETRA codec and encryption and TETRA mobile stations and consoles. Interworking between the MCPTT service and TETRA shall provide a means for an authorized user to initiate an override of a PTT Group call between MCPTT Users and TETRA mobile stations and consoles. Interworking between the MCPTT service and TETRA shall provide a means for an authorized TETRA mobile station or console to initiate an override of a PTT Group call between MCPTT Users and TETRA mobile stations and consoles. Interworking between the MCPTT service and TETRA shall support Group Regrouping that includes both MCPTT Groups and TETRA groups. Interworking between the MCPTT service and TETRA shall support User Regrouping that includes both MCPTT Users and TETRA mobile stations. Interworking between the MCPTT service and TETRA shall support interoperable Talker IDs and TETRA Talker IDs. Interworking between the MCPTT service and TETRA shall support interoperable PTT Private Calls between an MCPTT User and a TETRA mobile station or console. Interworking between the MCPTT service and TETRA shall support end-to-end encrypted PTT Private Calls between an MCPTT User supporting TETRA codec and encryption and a TETRA mobile station or console.}
| {"ANSWER": "SA1"} |
R1-2002264.txt | {"WORKING GROUP": "RAN1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{(RRC impact) Agreements: Adopt the following TP to TS 38.212, Sec. 7.3.1.1.2 (changes in red): Agreements: For Type 2 CG PUSCH activated by a DCI format configured with PUSCH repetition Type B, the frequency hopping enabling/disabling and the frequency offset follows the indication in the activation DCI, and the frequency hopping scheme follows the corresponding RRC parameter for the activation DCI format. Agreements: The semi-static and dynamic indication of invalid symbols (related to InvalidSymbolPattern) for DG PUSCH repetition Type B in case dynamic SFI is not configured follows the same behaviour as for DG PUSCH repetition Type B in case dynamic SFI is configured. For Type 1 CG PUSCH with repetition Type B, regardless of whether dynamic SFI is configured or not, if InvalidSymbolPattern is configured, the configured pattern is applied (that is, segmentation occurs around semi-static DL symbols and invalid symbols indicated by InvalidSymbolPattern). For the first Type 2 CG PUSCH with repetition Type B (including all repetitions) after activation, regardless of whether dynamic SFI is configured or not, if InvalidSymbolPattern is configured, whether the configured pattern is applied follows the same procedure as specified for DG PUSCH according to the activation DCI. For Type 2 CG PUSCH with repetition Type B (excluding the first Type 2 CG PUSCH, with all repetitions, after activation), regardless of whether dynamic SFI is configured or not, if InvalidSymbolPattern is configured, whether the configured pattern is applied follows the activation DCI. Agreements: For PUSCH repetition Type B, a UE is not expected to be indicated with an antenna port configuration that is invalid for the duration of any actual repetition. For PUSCH with repetition Type B, an actual repetition with a single symbol is not transmitted. In this contribution, we provide detailed discussion on the remaining issues of PUSCH enhancements. 2. Discussion: Repetition number of PUSCH carrying A-CSI/SP-CSI only: One remaining issue is the number of repetition for PUSCH with repetition Type B carrying A-CSI/SP-CSI only. To keep consistence with Rel-15 behaviour, we support to confirm the FFS below: Proposal 2.3-1a: Introduce reportSlotOffsetList-r16-ForDCIFormat0_1and reportSlotOffsetList-r16-ForDCIFormat0_2 and update TS 38.214 accordingly. (RRC impact) FFS whether to always assume the number of nominal repetitions is equal to 1 for PUSCH with repetition Type B carrying A-CSI/SP-CSI only. Proposal 1: The number of nominal repetitions is equal to 1 for PUSCH with repetition Type B carrying A-CSI/SP-CSI only. Impact to UCI on PUSCH repetitions: One remaining issue is that when UCI transmission collides PUSCH, which actual PUSCH repetition(s) should UCI be piggybacked, and how the timeline condition should be defined. To keep the Rel-15 rule as much as possible, it is fine to multiplex UCI on one or more overlapping actual repetitions that satisfies the timeline conditions defined in Section 9.2.5 of TS 38.213. Proposal 2: UCI can be multiplexed on all overlapped nominal repetitions, and for each nominal repetition with multiple segmented actual repetitions, UCI can only be piggybacked on one or more actual repetitions with largest number of symbols. Regarding the issue of UCI resource determination, the number of coded modulation symbols for HARQ-ACK on PUSCH transmission is given by the following equation: where is the total number of OFDM symbols of the PUSCH and denotes the TBS of the PUSCH. For the left part of the min function, since the PUSCH TBS is calculation based on length of nominal repetition, it is reasonable that the number of REs for UCI is calculated based on nominal repetition to maintain the decoding performance of UCI. For the UCI resource upper in the right part, it is appropriate to use the length of the actual repetition carrying the UCI due to the reason that UCI can be piggybacked on actual repetitions with various lengths. Proposal 3: For equation to determine UCI resources when multiplexing on PUSCH repetition Type B, the calculation is based on the nominal repetition, and the upper bound resources is constrained by the actual repetition carrying UCI. Whether to have a limit on the number of nominal repetitions for PUSCH repetition Type B: For PUSCH transmission with repetition type B, gNB may configure quite a few repetitions transmitting in a slot through setting small L and large K. In this case, UE needs to separately modulate and code these transmission blocks on different repetitions, which cause large implementation burden to UE. Considering this, we support to have a limit on the number of nominal repetitions for PUSCH repetition Type B, and it can be a UE capability optionally. Proposal 4: Limit on the number of nominal repetitions for PUSCH repetition Type B, and it can be a UE capability optionally. Whether to specially handle actual repetitions with 2-symbol length: Agreements: For PUSCH repetition Type B, a UE is not expected to be indicated with an antenna port configuration that is invalid for the duration of any actual repetition.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{(RRC impact) Agreements: Adopt the following TP to TS 38.212, Sec. 7.3.1.1.2 (changes in red): Agreements: For Type 2 CG PUSCH activated by a DCI format configured with PUSCH repetition Type B, the frequency hopping enabling/disabling and the frequency offset follows the indication in the activation DCI, and the frequency hopping scheme follows the corresponding RRC parameter for the activation DCI format. Agreements: The semi-static and dynamic indication of invalid symbols (related to InvalidSymbolPattern) for DG PUSCH repetition Type B in case dynamic SFI is not configured follows the same behaviour as for DG PUSCH repetition Type B in case dynamic SFI is configured. For Type 1 CG PUSCH with repetition Type B, regardless of whether dynamic SFI is configured or not, if InvalidSymbolPattern is configured, the configured pattern is applied (that is, segmentation occurs around semi-static DL symbols and invalid symbols indicated by InvalidSymbolPattern). For the first Type 2 CG PUSCH with repetition Type B (including all repetitions) after activation, regardless of whether dynamic SFI is configured or not, if InvalidSymbolPattern is configured, whether the configured pattern is applied follows the same procedure as specified for DG PUSCH according to the activation DCI. For Type 2 CG PUSCH with repetition Type B (excluding the first Type 2 CG PUSCH, with all repetitions, after activation), regardless of whether dynamic SFI is configured or not, if InvalidSymbolPattern is configured, whether the configured pattern is applied follows the activation DCI. Agreements: For PUSCH repetition Type B, a UE is not expected to be indicated with an antenna port configuration that is invalid for the duration of any actual repetition. For PUSCH with repetition Type B, an actual repetition with a single symbol is not transmitted. In this contribution, we provide detailed discussion on the remaining issues of PUSCH enhancements. 2. Discussion: Repetition number of PUSCH carrying A-CSI/SP-CSI only: One remaining issue is the number of repetition for PUSCH with repetition Type B carrying A-CSI/SP-CSI only. To keep consistence with Rel-15 behaviour, we support to confirm the FFS below: Proposal 2.3-1a: Introduce reportSlotOffsetList-r16-ForDCIFormat0_1and reportSlotOffsetList-r16-ForDCIFormat0_2 and update TS 38.214 accordingly. (RRC impact) FFS whether to always assume the number of nominal repetitions is equal to 1 for PUSCH with repetition Type B carrying A-CSI/SP-CSI only. Proposal 1: The number of nominal repetitions is equal to 1 for PUSCH with repetition Type B carrying A-CSI/SP-CSI only. Impact to UCI on PUSCH repetitions: One remaining issue is that when UCI transmission collides PUSCH, which actual PUSCH repetition(s) should UCI be piggybacked, and how the timeline condition should be defined. To keep the Rel-15 rule as much as possible, it is fine to multiplex UCI on one or more overlapping actual repetitions that satisfies the timeline conditions defined in Section 9.2.5 of TS 38.213. Proposal 2: UCI can be multiplexed on all overlapped nominal repetitions, and for each nominal repetition with multiple segmented actual repetitions, UCI can only be piggybacked on one or more actual repetitions with largest number of symbols. Regarding the issue of UCI resource determination, the number of coded modulation symbols for HARQ-ACK on PUSCH transmission is given by the following equation: where is the total number of OFDM symbols of the PUSCH and denotes the TBS of the PUSCH. For the left part of the min function, since the PUSCH TBS is calculation based on length of nominal repetition, it is reasonable that the number of REs for UCI is calculated based on nominal repetition to maintain the decoding performance of UCI. For the UCI resource upper in the right part, it is appropriate to use the length of the actual repetition carrying the UCI due to the reason that UCI can be piggybacked on actual repetitions with various lengths. Proposal 3: For equation to determine UCI resources when multiplexing on PUSCH repetition Type B, the calculation is based on the nominal repetition, and the upper bound resources is constrained by the actual repetition carrying UCI. Whether to have a limit on the number of nominal repetitions for PUSCH repetition Type B: For PUSCH transmission with repetition type B, gNB may configure quite a few repetitions transmitting in a slot through setting small L and large K. In this case, UE needs to separately modulate and code these transmission blocks on different repetitions, which cause large implementation burden to UE. Considering this, we support to have a limit on the number of nominal repetitions for PUSCH repetition Type B, and it can be a UE capability optionally. Proposal 4: Limit on the number of nominal repetitions for PUSCH repetition Type B, and it can be a UE capability optionally. Whether to specially handle actual repetitions with 2-symbol length: Agreements: For PUSCH repetition Type B, a UE is not expected to be indicated with an antenna port configuration that is invalid for the duration of any actual repetition.}
| {"ANSWER": "RAN1"} |
C6-200618.txt | {"WORKING GROUP": "CT6"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{3GPP TS 31.130 and ETSI TS 102 241 usually define events not dedicated to test purposes, but events dedicated to applications that implement services required on the field by operators or third parties. Defining new events as standard events implies that the UICC has to introduce and manage the events in operational phase at operating system level, not only limited to testing phase. For the requested event GET IDENTITY EVENT, a mechanism to trigger an applet when the UICC receives a GET IDENTITY COMMAND already exists, as defined in TS 31.130 in the package uicc.usim.suci. Defining a new event is a duplication of this mechanism. For the requested events READ BINARY EVENT, READ RECORD EVENT it would be more appropriate to ask ETSI TC SCP for an evolution of TS 102 241 as these events are out of the scope of 3GPP CT WG6. However, 3GPP CT WG6 believes it is necessary to evaluate how many times an applet that has registered to such events would be triggered and what is the timing process of these applets. Indeed, the number of times files are read could wake up several applets, generating delay on card performance, especially at initialization and activation time.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{3GPP TS 31.130 and ETSI TS 102 241 usually define events not dedicated to test purposes, but events dedicated to applications that implement services required on the field by operators or third parties. Defining new events as standard events implies that the UICC has to introduce and manage the events in operational phase at operating system level, not only limited to testing phase. For the requested event GET IDENTITY EVENT, a mechanism to trigger an applet when the UICC receives a GET IDENTITY COMMAND already exists, as defined in TS 31.130 in the package uicc.usim.suci. Defining a new event is a duplication of this mechanism. For the requested events READ BINARY EVENT, READ RECORD EVENT it would be more appropriate to ask ETSI TC SCP for an evolution of TS 102 241 as these events are out of the scope of 3GPP CT WG6. However, 3GPP CT WG6 believes it is necessary to evaluate how many times an applet that has registered to such events would be triggered and what is the timing process of these applets. Indeed, the number of times files are read could wake up several applets, generating delay on card performance, especially at initialization and activation time.}
| {"ANSWER": "CT6"} |
R1-1713164.txt | {"WORKING GROUP": "RAN1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{With interleaving (bundle size: 3) Without interleaving (a) with EPDCCH-like approach(b) without EPDCCH-like approach 258 0369 147 28 06 1 2 1 8 39 17 28 06 1 2 39 1 5 t f 17 Blocking!!Blocking!! 258 0369 147 CCE 0CCE 1 CCE0CCE1CCE2CCE3 With interleaving (bundle size: 3) Without interleaving (a) with EPDCCH-like approach(b) without EPDCCH-like approach 258 0369 147 Blocking!!Blocking!! 258 0369 147 Figure 1: An example of decreasing the blocking probability in 3-symbol CORESET Observation 1: EPDCCH-like approach is needed to form a higher aggregation level candidate in the CORESET with interleaving in order to decrease the blocking probability when the CORESETs which have different mapping type are overlapped. REG bundle set based interleaver can be used to implement the EPDCCH-like approach mentioned above. Basically, CCEs and REGs would be sequentially indexed in the logical domain. Then, logical-to-physical mapping would be determined according to the interleaving which distributes the REGs comprising CCE into physical domain. The interleaving can be conducted with the unit of REG bundle set which consists of multiple REG bundles from different CCEs. In Figure 2, two REG bundles from different CCEs correspond to a REG bundle set and the block interleaver is applied to the REG bundle set index. With this approach, REG bundle set can be evenly distributed within the CORESET in physical domain. (If we apply a column permutation for the block interleaver, REG bundle set can be randomly distributed within the CORESET in physical domain.) By adapting REG bundle set size, it can adapt frequency diversity and reduction of blocking between interleaving and non-interleaving case. Furthermore, if REG bundle set is supported, it can be also desirable to indicate to the UE such that a UE can assume same precoder within the REG bundle set for better channel estimation.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{With interleaving (bundle size: 3) Without interleaving (a) with EPDCCH-like approach(b) without EPDCCH-like approach 258 0369 147 28 06 1 2 1 8 39 17 28 06 1 2 39 1 5 t f 17 Blocking!!Blocking!! 258 0369 147 CCE 0CCE 1 CCE0CCE1CCE2CCE3 With interleaving (bundle size: 3) Without interleaving (a) with EPDCCH-like approach(b) without EPDCCH-like approach 258 0369 147 Blocking!!Blocking!! 258 0369 147 Figure 1: An example of decreasing the blocking probability in 3-symbol CORESET Observation 1: EPDCCH-like approach is needed to form a higher aggregation level candidate in the CORESET with interleaving in order to decrease the blocking probability when the CORESETs which have different mapping type are overlapped. REG bundle set based interleaver can be used to implement the EPDCCH-like approach mentioned above. Basically, CCEs and REGs would be sequentially indexed in the logical domain. Then, logical-to-physical mapping would be determined according to the interleaving which distributes the REGs comprising CCE into physical domain. The interleaving can be conducted with the unit of REG bundle set which consists of multiple REG bundles from different CCEs. In Figure 2, two REG bundles from different CCEs correspond to a REG bundle set and the block interleaver is applied to the REG bundle set index. With this approach, REG bundle set can be evenly distributed within the CORESET in physical domain. (If we apply a column permutation for the block interleaver, REG bundle set can be randomly distributed within the CORESET in physical domain.) By adapting REG bundle set size, it can adapt frequency diversity and reduction of blocking between interleaving and non-interleaving case. Furthermore, if REG bundle set is supported, it can be also desirable to indicate to the UE such that a UE can assume same precoder within the REG bundle set for better channel estimation.}
| {"ANSWER": "RAN1"} |
R3-184086.txt | {"WORKING GROUP": "RAN3"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{The reason for that could be that either the NG-RAN node contacted is the wrong one or the short MAC-I delivered does not match and probably many others. The new NG-RAN node would then reject resumption of the UE and the UE would need to perform fallback to RRC_IDLE and setup the NAS and AS connection anew. Releasing UEs in RRC_INACTIVE by RAN paging: The latest discussion is captured in R3-183447, where the serving/old NG-RAN node provides Release Assistance information to the new NG-RAN node, allowing the new node to release the RRC connection and send the UE to IDLE. With the information from RAN2, we could change this approach and simply provide the already ciphered and integrity protected RRC Release message to the new node. This would go along the approach outlined for the third case. Observation 1 Releasing UEs in RRC_INACTIVE could follow the same approach as for RNAU w/o path switch. RNAU w/o path switch: Discussions on RNAU w/o path switch has been started in RAN3 mainly having periodic RNAU signalling in mind. The LS from RAN2 contains implicitly the assumption that this approach could be applicable also for mobility triggered RNAU signalling.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{The reason for that could be that either the NG-RAN node contacted is the wrong one or the short MAC-I delivered does not match and probably many others. The new NG-RAN node would then reject resumption of the UE and the UE would need to perform fallback to RRC_IDLE and setup the NAS and AS connection anew. Releasing UEs in RRC_INACTIVE by RAN paging: The latest discussion is captured in R3-183447, where the serving/old NG-RAN node provides Release Assistance information to the new NG-RAN node, allowing the new node to release the RRC connection and send the UE to IDLE. With the information from RAN2, we could change this approach and simply provide the already ciphered and integrity protected RRC Release message to the new node. This would go along the approach outlined for the third case. Observation 1 Releasing UEs in RRC_INACTIVE could follow the same approach as for RNAU w/o path switch. RNAU w/o path switch: Discussions on RNAU w/o path switch has been started in RAN3 mainly having periodic RNAU signalling in mind. The LS from RAN2 contains implicitly the assumption that this approach could be applicable also for mobility triggered RNAU signalling.}
| {"ANSWER": "RAN3"} |
S5-080353.txt | {"WORKING GROUP": "SA5"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{2) Subscriber may switch on and off home NodeB frequently. 3) Operator may not be able to access home NodeB physically as it is located in subscriber’s place. Changes since last presentation to TSG SA#xy Meeting : New Outstanding Issues: None Contentious Issues: None Contents Foreword This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction: 3GPP SA5 has agreed to accept Self-Organizing Networks (SON) in studying LTE&SAE OAM architecture, and 3GPP RAN has agreed to study UMTS home NodeB and LTE home NodeB.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{2) Subscriber may switch on and off home NodeB frequently. 3) Operator may not be able to access home NodeB physically as it is located in subscriber’s place. Changes since last presentation to TSG SA#xy Meeting : New Outstanding Issues: None Contentious Issues: None Contents Foreword This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction: 3GPP SA5 has agreed to accept Self-Organizing Networks (SON) in studying LTE&SAE OAM architecture, and 3GPP RAN has agreed to study UMTS home NodeB and LTE home NodeB.}
| {"ANSWER": "SA5"} |
C1-121101.txt | {"WORKING GROUP": "CT1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Non-NMO=1 05 April 2012 Analysis Correct relationships between MME/SGSNs and VLRs are assumed in the specification: the SGs/Gs association state is per UE, not per UE and remote VLR. Ambiguous when another VLR than the ”correct VLR” makes use of the Gs/SGs interface. Stage 3 should resolve such problems. The IMSI hash VLR selection method is flawed: as the MME shall always select the VLR1 based on the IMSI hash, even if the UE is registered in a different VLR (NRI and SGs association point to VLR2 in the Dual VLR problem before the MME or SGSN changes VLRs). as when a VLR receives Location Updating from a MME or SGSN it cannot determine that a previous VLR holds the registration for the UE (within the same MSC Pool area). 2012-04-03 Possible solutions the MME/SGSN attempts to only select the VLR that has allocated the TMSI to the UE. Selection would be using SGs/Gs association’s VLR name: only works for intra-RAT/intra NMO=1 mobility, in the same MME or same SGSN. The reason that SGs/Gs check does not work in all cases is that it relies on a single MME or SGSN having an SGs/Gs association (SGs/Gs change is a case where it will not work). Transferring VLR identities between SGSNs and MMEs as part of EMM/GMM context transfer? It fails at mobility involving non-NMO=1 2012-04-03 SGs association Possible solutions Introduce ”Excessive HLR signalling” VLR could do Update Location for every received LAU over Gs/SGs Would mean HSS update at inter-RAT mobility (e.g. after all CSFB calls) 2012-04-03 Update Location always hash Possible solutions MME/SGSN aided dual VLR detection At certain events it would be possible for an MME or SGSN to indicate to the ”correct” VLR that there is another VLR that holds the UE registration. TAU when the IMSI hash points to a different VLR compared to the one pointed to by the SGs/Gs association. Paging from a different VLR than the VLR pointed to by the SGs association. Relies on the same MME/SGSN detecting the event as the one having the SGs/Gs association to the VLR Solution could be for the MME to send LAU with a ”dual VLR” indicator, or to set the old LAC to 0 or FFFE, or both indicator and old LAC = 0/FFFE. 2012-04-03 LAU (with Flag and old LAC=0/FFFE) Update Location SGs association Possible solutions TMSI based dual VLR detection: Adding TMSI to combined TAU/RAU and using NRI to select VLR would solve the dual VLR problem. In case the VLR would not be the current VLR it would be detected by TMSI verification that another VLR holds the UE registration. 2012-04-03 LAU (with TMSI or NRI) Update Location Conclusion Long term solution TMSI-solution would solve the dual VLR problem. The solution does not address legacy Ues. The MSC in pool solution would work the same for all network modes of operation, and CSFB; considering load distribution, and load re-balancing. 2012-04-03 Conclusion Network only solution, without UE impact thus attempt to prevent the dual VLR problem from happening, Only works at intra-RAT at next inter-RAT mobility dual VLR occurs. (Actually works also at intra-NMO=1 mobility when both RATs support Gs). Excessive HLR signalling method would work, but isn’t regarded as feasible as it is not in line with basic mobility concepts. The MME or SGSN aided detection method solution is where the VLR receives an indication that there is a change of VLR, when location updating occurs with change of VLRs using the same SGSN or the same MME (or the same combined MME/SGSN). in case where global paging over all MMEs and SGSNs is performed. Works at intra-RAT/intra-NMO=1 mobility only, but after detection the problem is solved.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Non-NMO=1 05 April 2012 Analysis Correct relationships between MME/SGSNs and VLRs are assumed in the specification: the SGs/Gs association state is per UE, not per UE and remote VLR. Ambiguous when another VLR than the ”correct VLR” makes use of the Gs/SGs interface. Stage 3 should resolve such problems. The IMSI hash VLR selection method is flawed: as the MME shall always select the VLR1 based on the IMSI hash, even if the UE is registered in a different VLR (NRI and SGs association point to VLR2 in the Dual VLR problem before the MME or SGSN changes VLRs). as when a VLR receives Location Updating from a MME or SGSN it cannot determine that a previous VLR holds the registration for the UE (within the same MSC Pool area). 2012-04-03 Possible solutions the MME/SGSN attempts to only select the VLR that has allocated the TMSI to the UE. Selection would be using SGs/Gs association’s VLR name: only works for intra-RAT/intra NMO=1 mobility, in the same MME or same SGSN. The reason that SGs/Gs check does not work in all cases is that it relies on a single MME or SGSN having an SGs/Gs association (SGs/Gs change is a case where it will not work). Transferring VLR identities between SGSNs and MMEs as part of EMM/GMM context transfer? It fails at mobility involving non-NMO=1 2012-04-03 SGs association Possible solutions Introduce ”Excessive HLR signalling” VLR could do Update Location for every received LAU over Gs/SGs Would mean HSS update at inter-RAT mobility (e.g. after all CSFB calls) 2012-04-03 Update Location always hash Possible solutions MME/SGSN aided dual VLR detection At certain events it would be possible for an MME or SGSN to indicate to the ”correct” VLR that there is another VLR that holds the UE registration. TAU when the IMSI hash points to a different VLR compared to the one pointed to by the SGs/Gs association. Paging from a different VLR than the VLR pointed to by the SGs association. Relies on the same MME/SGSN detecting the event as the one having the SGs/Gs association to the VLR Solution could be for the MME to send LAU with a ”dual VLR” indicator, or to set the old LAC to 0 or FFFE, or both indicator and old LAC = 0/FFFE. 2012-04-03 LAU (with Flag and old LAC=0/FFFE) Update Location SGs association Possible solutions TMSI based dual VLR detection: Adding TMSI to combined TAU/RAU and using NRI to select VLR would solve the dual VLR problem. In case the VLR would not be the current VLR it would be detected by TMSI verification that another VLR holds the UE registration. 2012-04-03 LAU (with TMSI or NRI) Update Location Conclusion Long term solution TMSI-solution would solve the dual VLR problem. The solution does not address legacy Ues. The MSC in pool solution would work the same for all network modes of operation, and CSFB; considering load distribution, and load re-balancing. 2012-04-03 Conclusion Network only solution, without UE impact thus attempt to prevent the dual VLR problem from happening, Only works at intra-RAT at next inter-RAT mobility dual VLR occurs. (Actually works also at intra-NMO=1 mobility when both RATs support Gs). Excessive HLR signalling method would work, but isn’t regarded as feasible as it is not in line with basic mobility concepts. The MME or SGSN aided detection method solution is where the VLR receives an indication that there is a change of VLR, when location updating occurs with change of VLRs using the same SGSN or the same MME (or the same combined MME/SGSN). in case where global paging over all MMEs and SGSNs is performed. Works at intra-RAT/intra-NMO=1 mobility only, but after detection the problem is solved.}
| {"ANSWER": "CT1"} |
S1-174305.txt | {"WORKING GROUP": "SA1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{The decision where to store and execute 3GPP UICC applications (USIM and ISIM) is within the responsibility of 3GPP. From the security perspective of ETSI TC SCP, storage and execution outside of the secure element will decrease the security of applications as a separate hardware based secure element provides a tamper resistant secure execution environment. The UICC as well as the new SSP enable to support multiple applications. ETSI TC SCP would like to inform 3GPP TSG SA WG6 that the following secure elements are maintained or under development: (e)UICC and SSP. 2. Actions: To 3GPP TSG SA WG6: ETSI TC SCP kindly asks 3GPP TSG SA WG6 to take the above information into account and, if more information is required from ETSI TC SCP, provide a more detailed description of the use case. 3. Date of Next ETSI TC SCP Meetings: ETSI TC SCP #82 08– 09 February 2017, tbd (Europe)}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{The decision where to store and execute 3GPP UICC applications (USIM and ISIM) is within the responsibility of 3GPP. From the security perspective of ETSI TC SCP, storage and execution outside of the secure element will decrease the security of applications as a separate hardware based secure element provides a tamper resistant secure execution environment. The UICC as well as the new SSP enable to support multiple applications. ETSI TC SCP would like to inform 3GPP TSG SA WG6 that the following secure elements are maintained or under development: (e)UICC and SSP. 2. Actions: To 3GPP TSG SA WG6: ETSI TC SCP kindly asks 3GPP TSG SA WG6 to take the above information into account and, if more information is required from ETSI TC SCP, provide a more detailed description of the use case. 3. Date of Next ETSI TC SCP Meetings: ETSI TC SCP #82 08– 09 February 2017, tbd (Europe)}
| {"ANSWER": "SA1"} |
C3-195177.txt | {"WORKING GROUP": "CT3"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{On the other hand, even though from a technical perspective CT4/CT3 have not detected any major problem with defining new services for the Nudr SBI, it was mentioned that defining new services creates an overhead in terms of standardization effort, even when a number of design patterns might be reused for the different APIs. So, defining a large number of services is not desirable. A technical implication that could result from a potential definition of a large number of Nudr services is related to the fact that the "service name" (specific to each API/service) must be included in the Oauth2 access token used to get access to a given service; therefore, an NF consumer that would need to access a large number of Nudr services needs to include all of them in the access token request towards NRF, and need to manage it accordingly as long as new services are added. It is CT4's view that this may be fine for a moderate number of services, but it gets harder to manage as the amount of new defined services grow. Question 2: "If only a small subset of service operations of Nudr_DM is to be used for a data set, is it preferable to define a new service or reuse the existing Nudr_DM service?" Answer: The number of operations to be used of an existing service does not favour or penalize the reuse of the service to have access to new data.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{On the other hand, even though from a technical perspective CT4/CT3 have not detected any major problem with defining new services for the Nudr SBI, it was mentioned that defining new services creates an overhead in terms of standardization effort, even when a number of design patterns might be reused for the different APIs. So, defining a large number of services is not desirable. A technical implication that could result from a potential definition of a large number of Nudr services is related to the fact that the "service name" (specific to each API/service) must be included in the Oauth2 access token used to get access to a given service; therefore, an NF consumer that would need to access a large number of Nudr services needs to include all of them in the access token request towards NRF, and need to manage it accordingly as long as new services are added. It is CT4's view that this may be fine for a moderate number of services, but it gets harder to manage as the amount of new defined services grow. Question 2: "If only a small subset of service operations of Nudr_DM is to be used for a data set, is it preferable to define a new service or reuse the existing Nudr_DM service?" Answer: The number of operations to be used of an existing service does not favour or penalize the reuse of the service to have access to new data.}
| {"ANSWER": "CT3"} |
R5-095302.txt | {"WORKING GROUP": "RAN5"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Accordingly, 3 CRs were agreed during RAN5#44 (R5-094992, R5-094993 & R5-094994) that impacts, in particular, sub test 5 and the corresponding test procedures in each of the following previously validated test cases: 5.2B Maximum Output Power with HS-DPCCH and E-DCH 5.9B Spectrum Emission Mask with E-DCH 5.10B Adjacent Channel Leakage Power Ratio (ACLR) with E-DCH To ensure that the subsequent practical implementations are stable, sub test 5 of these tests will not be considered applicable until 28 Feb 10; in effect, from a RAN5 point of view, these particular sub tests are suspended until then. This date will be reviewed at RAN5#45 & RAN5#46, but unless further guidance is provided, the date will not be changed. It is emphasised that the applicability status of sub tests 1 – 4 of these tests is unaffected. It is expected that the CRs mentioned above will be approved at RAN Plenary#45 (15 – 18 Sep 10) and the updated version of TS 34.121-1 will be available within 3 weeks of that meeting. The RAN5 Interim Working Document (iWD) 003 has been updated accordingly and will be available at the end of RAN5#44.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Accordingly, 3 CRs were agreed during RAN5#44 (R5-094992, R5-094993 & R5-094994) that impacts, in particular, sub test 5 and the corresponding test procedures in each of the following previously validated test cases: 5.2B Maximum Output Power with HS-DPCCH and E-DCH 5.9B Spectrum Emission Mask with E-DCH 5.10B Adjacent Channel Leakage Power Ratio (ACLR) with E-DCH To ensure that the subsequent practical implementations are stable, sub test 5 of these tests will not be considered applicable until 28 Feb 10; in effect, from a RAN5 point of view, these particular sub tests are suspended until then. This date will be reviewed at RAN5#45 & RAN5#46, but unless further guidance is provided, the date will not be changed. It is emphasised that the applicability status of sub tests 1 – 4 of these tests is unaffected. It is expected that the CRs mentioned above will be approved at RAN Plenary#45 (15 – 18 Sep 10) and the updated version of TS 34.121-1 will be available within 3 weeks of that meeting. The RAN5 Interim Working Document (iWD) 003 has been updated accordingly and will be available at the end of RAN5#44.}
| {"ANSWER": "RAN5"} |
R3-091425.txt | {"WORKING GROUP": "RAN3"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{The agreed requirements related to SON are listed in TR 36.902 . Following a discussion at the meeting on the need of automated negotiation of HO settings, this paper proposes changes to the TR. 2 Proposed text changes in TR 36.902: *** Omitted part, kept unchanged *** 4.6.2 Required functionality General features of the solution are as follows: Functionality: An algorithm decides to distribute the UEs camping on or having a connection to a cell, in order to balance the traffic load. This may be achieved by delaying or advancing the handing over of the UEs between cells. Actions: 1) An eNB monitors the load in the controlled cell and exchanges related information over X2 or S1 with neighbouring node(s). 2) An algorithm identifies the need to distribute the load of the cell towards either adjacent or co-located cells, including cells from other RATs, e.g. by comparing the load among the cells, the type of ongoing services, the cell configuration, etc. 3) An algorithm estimates if the HO parameter settings (details of the parameters are FFS) need to be modified; if so, it indicates/requests (the actual mechanism is FFS) the change of the HO parameter settings to the neighbour eNB (it is FFS if it is done via O&M or direct over X2/S1) and provides information on the new values of the parameters.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{The agreed requirements related to SON are listed in TR 36.902 . Following a discussion at the meeting on the need of automated negotiation of HO settings, this paper proposes changes to the TR. 2 Proposed text changes in TR 36.902: *** Omitted part, kept unchanged *** 4.6.2 Required functionality General features of the solution are as follows: Functionality: An algorithm decides to distribute the UEs camping on or having a connection to a cell, in order to balance the traffic load. This may be achieved by delaying or advancing the handing over of the UEs between cells. Actions: 1) An eNB monitors the load in the controlled cell and exchanges related information over X2 or S1 with neighbouring node(s). 2) An algorithm identifies the need to distribute the load of the cell towards either adjacent or co-located cells, including cells from other RATs, e.g. by comparing the load among the cells, the type of ongoing services, the cell configuration, etc. 3) An algorithm estimates if the HO parameter settings (details of the parameters are FFS) need to be modified; if so, it indicates/requests (the actual mechanism is FFS) the change of the HO parameter settings to the neighbour eNB (it is FFS if it is done via O&M or direct over X2/S1) and provides information on the new values of the parameters.}
| {"ANSWER": "RAN3"} |
S5-216024.txt | {"WORKING GROUP": "SA5"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{For example, the application layer entity responsible for the reporting may no longer be running at the time of the indicated restart, since the RAN overload event which triggered the temporary stop may be accompanied by poor service quality causing the user to terminate the service and its associated application. Possibly, SA4 is able to address this in the future release. In light of the above issue, and before SA4 is able to decide on our preference among the three options described in your LS, SA4 kindly asks RAN2 to respond to the following questions: 1. What is the expected typical duration of a temporary stop – e.g., in the order of minutes or perhaps much longer, say hours? As per-session QoE reports are typically sent relatively seldom (at the end of each session or say every few minutes for longer sessions), we would expect that a temporary stop lasting about half an hour should not require additional AS layer storage beyond the supported buffer size limitation, e.g., 64 kB as indicated for Option 2. 2. In case a temporary stop can last for a very long time (e.g., hours), are there any mechanisms already defined or being considered at the RAN side to ensure that subsequent resumption of delivery of potentially a large volume of buffered QoE reports, upon recovery from RAN overload, will not trigger RAN overload recurrence?}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{For example, the application layer entity responsible for the reporting may no longer be running at the time of the indicated restart, since the RAN overload event which triggered the temporary stop may be accompanied by poor service quality causing the user to terminate the service and its associated application. Possibly, SA4 is able to address this in the future release. In light of the above issue, and before SA4 is able to decide on our preference among the three options described in your LS, SA4 kindly asks RAN2 to respond to the following questions: 1. What is the expected typical duration of a temporary stop – e.g., in the order of minutes or perhaps much longer, say hours? As per-session QoE reports are typically sent relatively seldom (at the end of each session or say every few minutes for longer sessions), we would expect that a temporary stop lasting about half an hour should not require additional AS layer storage beyond the supported buffer size limitation, e.g., 64 kB as indicated for Option 2. 2. In case a temporary stop can last for a very long time (e.g., hours), are there any mechanisms already defined or being considered at the RAN side to ensure that subsequent resumption of delivery of potentially a large volume of buffered QoE reports, upon recovery from RAN overload, will not trigger RAN overload recurrence?}
| {"ANSWER": "SA5"} |
C1-061711-LS_out.txt | {"WORKING GROUP": "CT1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{CT1 sees no possibility within the specifications produced by IETF, 3GPP, 3GPP2, ETSI TISPAN, OMA and other standardization bodies, to use the 200 (OK) response to the INVITE request as an appropriate indication for the network, to start charging. Media can be available to both parties already before the 200 (OK) is sent or may not be available at all, e.g. in cases of interworking with non-IMS capable equipment. CT1 therefore understands the paradigm outlined by SA5, to start charging for media upon receipt of the 200 (OK) response for the INVITE request can only be understood as an approximation. 2. In a more general manner, the time when early media is made available in an end-to-end manner is not reflected at all in the SIP signalling. 3. Information available in the IMS network entities, based on which charging of media could be started at the moment when the media is available end-to-end to all involved parties, is related to the access technology used to the IMS, for example when GPRS is used the indication from the GGSN, when the gates for media connections are opened.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{CT1 sees no possibility within the specifications produced by IETF, 3GPP, 3GPP2, ETSI TISPAN, OMA and other standardization bodies, to use the 200 (OK) response to the INVITE request as an appropriate indication for the network, to start charging. Media can be available to both parties already before the 200 (OK) is sent or may not be available at all, e.g. in cases of interworking with non-IMS capable equipment. CT1 therefore understands the paradigm outlined by SA5, to start charging for media upon receipt of the 200 (OK) response for the INVITE request can only be understood as an approximation. 2. In a more general manner, the time when early media is made available in an end-to-end manner is not reflected at all in the SIP signalling. 3. Information available in the IMS network entities, based on which charging of media could be started at the moment when the media is available end-to-end to all involved parties, is related to the access technology used to the IMS, for example when GPRS is used the indication from the GGSN, when the gates for media connections are opened.}
| {"ANSWER": "CT1"} |
S1-113186.txt | {"WORKING GROUP": "SA1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{The terms of use may control the behavior of a customer by certain parameters like for example the number of calls per time interval, the number of international calls per time interval or the total duration of international calls per time interval. Additionally the operator can restrict the usage of its services to ‘only private and non-commercial’ and rate calls contravening these conditions another price making misuse by SPITters unattractive. In worst case, if the operator identifies a specific customer as a permanent source of malicious usage, the operator may reserve the right to terminate the contract with this user. However with the rising of VoIP and with the interconnection of the currently existing VoIP islands it is no longer guaranteed that all VoIP users will have a contract with an operator at all. Nevertheless it is interesting to see that today also well-known VoIP providers that offer free communication over the Internet behave operator-like (charging of small fees; terms of use restricting the capabilities of a user), if they connect to existing PSTN networks. But even the contracts of the different operators may differ in their conditions so that the trust into an operator may range from high to low. On the other hand these varying levels of trust give trusted operators also the opportunity to differentiate from their competitors. Today it is not clear whether the majority of users is willing to accept a large number of nuisances like SPIT/UC for the benefit of a lower price. Therefore the trust level of the operator will perhaps also have consequences for a differentiation between the kinds of customers joining the network: ‘normal’ customers may perhaps accept an additional charge for a network, almost clean of nuisances like SPIT/UC, while customers with a restricted budget and happy with ‘trying out new things’ may choose an operator with lower price and lower trust level. But trusted operators carry then the responsibility to which other operator networks they connect under which terms to protect their own network against external nuisances. This is usually regulated by contractual agreements between different operators, usually called Service Level Agreements (SLAs; see next sub-section). Generally even the non-operator centric part of the VoIP community in IETF acknowledges in RFC 5039, section 3.13 that today’s operator controlled networks experience relatively little SPIT/UC and takes this as proof that this kind of arrangement can work.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{The terms of use may control the behavior of a customer by certain parameters like for example the number of calls per time interval, the number of international calls per time interval or the total duration of international calls per time interval. Additionally the operator can restrict the usage of its services to ‘only private and non-commercial’ and rate calls contravening these conditions another price making misuse by SPITters unattractive. In worst case, if the operator identifies a specific customer as a permanent source of malicious usage, the operator may reserve the right to terminate the contract with this user. However with the rising of VoIP and with the interconnection of the currently existing VoIP islands it is no longer guaranteed that all VoIP users will have a contract with an operator at all. Nevertheless it is interesting to see that today also well-known VoIP providers that offer free communication over the Internet behave operator-like (charging of small fees; terms of use restricting the capabilities of a user), if they connect to existing PSTN networks. But even the contracts of the different operators may differ in their conditions so that the trust into an operator may range from high to low. On the other hand these varying levels of trust give trusted operators also the opportunity to differentiate from their competitors. Today it is not clear whether the majority of users is willing to accept a large number of nuisances like SPIT/UC for the benefit of a lower price. Therefore the trust level of the operator will perhaps also have consequences for a differentiation between the kinds of customers joining the network: ‘normal’ customers may perhaps accept an additional charge for a network, almost clean of nuisances like SPIT/UC, while customers with a restricted budget and happy with ‘trying out new things’ may choose an operator with lower price and lower trust level. But trusted operators carry then the responsibility to which other operator networks they connect under which terms to protect their own network against external nuisances. This is usually regulated by contractual agreements between different operators, usually called Service Level Agreements (SLAs; see next sub-section). Generally even the non-operator centric part of the VoIP community in IETF acknowledges in RFC 5039, section 3.13 that today’s operator controlled networks experience relatively little SPIT/UC and takes this as proof that this kind of arrangement can work.}
| {"ANSWER": "SA1"} |
C6-170464.txt | {"WORKING GROUP": "CT6"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{To provide a solution within the timeframe requested by 3GPP WG SA3, ETSI TC SCP REQ had held several additional dedicated meetings and scheduled conference calls and a further plenary meeting for the end of September. ETSI TC SCP REQ expects to finalize the requirement specification at that meeting and present it to the additional plenary of ETSI TC SCP (TC SCP#80) for approval. Furthermore, ETSI TC SCP TEC has begun with the technical realization based on the current set of accepted requirements. ETSI TC SCP will keep 3GPP WG SA3 updated on the further progress of this work. 2. Actions:: To 3GPP WG SA3: Please take the above information into account. 3. Dates of next ETSI TC SCP and TC SCP REQ Meetings:: SCP REQ #65 25 -27 September 2017 San Diego, USA SCP #80 28 -29 September 2017 San Diego, USA}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{To provide a solution within the timeframe requested by 3GPP WG SA3, ETSI TC SCP REQ had held several additional dedicated meetings and scheduled conference calls and a further plenary meeting for the end of September. ETSI TC SCP REQ expects to finalize the requirement specification at that meeting and present it to the additional plenary of ETSI TC SCP (TC SCP#80) for approval. Furthermore, ETSI TC SCP TEC has begun with the technical realization based on the current set of accepted requirements. ETSI TC SCP will keep 3GPP WG SA3 updated on the further progress of this work. 2. Actions:: To 3GPP WG SA3: Please take the above information into account. 3. Dates of next ETSI TC SCP and TC SCP REQ Meetings:: SCP REQ #65 25 -27 September 2017 San Diego, USA SCP #80 28 -29 September 2017 San Diego, USA}
| {"ANSWER": "CT6"} |
S1-211216.txt | {"WORKING GROUP": "SA1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{When network condition turns bad, packet loss may occur in media flow and haptic information flow, which may cause game lag and affecting the game experience. 5.3.2 Pre-conditions Alice and Bob are playing a VR game together. They need to cover each other’s back, find weapons and fight with zombies. 5.3.3 Service Flows 1. Alice and Bob both joined this VR games, and they can see each other’s character in the view. 2. Alice found two stones on the ground, she picks up both the stones. 3. Bob has nothing to arm himself. So he asks Alice to throw him a stone. 4. Alice heard Bob and throws one of the stone to Bob. 5. Bob catches the stone can feel the weight of the stone. 6. Network is in bad condition. Bob tries to throw the stone back to Alice, but the screen got stuck in where he did not throw the stone. 7. Alice see the stone and try to catch it. But the haptic feedback device was delayed and didn’t catch it. 5.3.4 Post-conditions Alice and Bob can feel the things in the game as they are in the real world.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{When network condition turns bad, packet loss may occur in media flow and haptic information flow, which may cause game lag and affecting the game experience. 5.3.2 Pre-conditions Alice and Bob are playing a VR game together. They need to cover each other’s back, find weapons and fight with zombies. 5.3.3 Service Flows 1. Alice and Bob both joined this VR games, and they can see each other’s character in the view. 2. Alice found two stones on the ground, she picks up both the stones. 3. Bob has nothing to arm himself. So he asks Alice to throw him a stone. 4. Alice heard Bob and throws one of the stone to Bob. 5. Bob catches the stone can feel the weight of the stone. 6. Network is in bad condition. Bob tries to throw the stone back to Alice, but the screen got stuck in where he did not throw the stone. 7. Alice see the stone and try to catch it. But the haptic feedback device was delayed and didn’t catch it. 5.3.4 Post-conditions Alice and Bob can feel the things in the game as they are in the real world.}
| {"ANSWER": "SA1"} |
RT-000035.txt | {"WORKING GROUP": "RAN_AH1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{_______________ Subject: Question ITU-R 229/8 (Recommendation ITU-R M.1457 - RSPC) [ITU Member] FUTURE UPDATES OF WCDMA (ds-CDMA) 3GPP TSG RAN notes with interest the recent work within ITU-R WP8F on the update procedure for revisions of Recommendation ITU-R M.1457. In a previous response to ITU-R WP 8F’s Liaison Statement on the updating of Recommendation ITU-R M.1457, 3GPP TSG RAN drew particular attention to some of its work items , that proposes enhancements to WCDMA. This work is now at a stage where it is considered appropriate to propose it for incorporation in Recommendation ITU-R M.1457, as an enhancement to the WCDMA (DS-CDMA) radio interface. Annexes 1-5 contain high level descriptions of some significant 3GPP TSG RAN work items 3GPP TSG RAN believes there is no need for any further technical evaluation against the “Requirements and Objectives of IMT-2000” and the “Minimum Performance Capabilities for IMT-2000” since the proposed material constitutes enhancements to the IMT-2000 CDMA DS and IMT-2000 CDMA TDD that already proved their compliance with the above mentioned requirements. For further comments on the procedure proposed by ITU-R WP 8F for the Revision of Recommendation ITU-R M.1457, please refer to Doc 8F/XXX-E. For completeness, Annex 6 contains the dates of the future meetings of TSG RAN that may be considered by ITU-R WP 8F when further developing its workplan, including revision or enhancement of Recommendation ITU-R M.1457. 3GPP TSG RAN would like to continue its fruitful liaison with ITU-R WP 8F on the future development of IMT-2000 and in particular Recommendation ITU-R M.1457. Proposal It is proposed that High Speed Downlink Packet Access should be considered by ITU-R WP8F for incorporation in Recommendation ITU-R M.1457, as an enhancement to the WCDMA (DS-CDMA) radio interface Annexes: 6 3GPP TSG RAN Work Item – Terminal Power saving features: Gated DPCCH transmission scheme ("Gating”) is basically reduced power control rate operation to get power saving and interference reduction by turning off transmission intermittently. Gating can be applied during DSCH (downlink shared channel transmission) and implies that the UL and DL DPCCH are only transmitted intermittently. UTRAN initiate and terminate the gating by higher layer signalling. During gating, limited amount of data can be transmitted without terminating gating. With the gated DPCCH transmission scheme, UE battery life can be extended by turning off the transmitter intermittently, and also , if desired, by utilising the possibility to turn off the receiver , if 'RX gating DRX cycle' is defined to be greater than one. Furthermore, by means of gated transmission, uplink and downlink interference may be reduced leading to improved uplink and downlink capacity.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{_______________ Subject: Question ITU-R 229/8 (Recommendation ITU-R M.1457 - RSPC) [ITU Member] FUTURE UPDATES OF WCDMA (ds-CDMA) 3GPP TSG RAN notes with interest the recent work within ITU-R WP8F on the update procedure for revisions of Recommendation ITU-R M.1457. In a previous response to ITU-R WP 8F’s Liaison Statement on the updating of Recommendation ITU-R M.1457, 3GPP TSG RAN drew particular attention to some of its work items , that proposes enhancements to WCDMA. This work is now at a stage where it is considered appropriate to propose it for incorporation in Recommendation ITU-R M.1457, as an enhancement to the WCDMA (DS-CDMA) radio interface. Annexes 1-5 contain high level descriptions of some significant 3GPP TSG RAN work items 3GPP TSG RAN believes there is no need for any further technical evaluation against the “Requirements and Objectives of IMT-2000” and the “Minimum Performance Capabilities for IMT-2000” since the proposed material constitutes enhancements to the IMT-2000 CDMA DS and IMT-2000 CDMA TDD that already proved their compliance with the above mentioned requirements. For further comments on the procedure proposed by ITU-R WP 8F for the Revision of Recommendation ITU-R M.1457, please refer to Doc 8F/XXX-E. For completeness, Annex 6 contains the dates of the future meetings of TSG RAN that may be considered by ITU-R WP 8F when further developing its workplan, including revision or enhancement of Recommendation ITU-R M.1457. 3GPP TSG RAN would like to continue its fruitful liaison with ITU-R WP 8F on the future development of IMT-2000 and in particular Recommendation ITU-R M.1457. Proposal It is proposed that High Speed Downlink Packet Access should be considered by ITU-R WP8F for incorporation in Recommendation ITU-R M.1457, as an enhancement to the WCDMA (DS-CDMA) radio interface Annexes: 6 3GPP TSG RAN Work Item – Terminal Power saving features: Gated DPCCH transmission scheme ("Gating”) is basically reduced power control rate operation to get power saving and interference reduction by turning off transmission intermittently. Gating can be applied during DSCH (downlink shared channel transmission) and implies that the UL and DL DPCCH are only transmitted intermittently. UTRAN initiate and terminate the gating by higher layer signalling. During gating, limited amount of data can be transmitted without terminating gating. With the gated DPCCH transmission scheme, UE battery life can be extended by turning off the transmitter intermittently, and also , if desired, by utilising the possibility to turn off the receiver , if 'RX gating DRX cycle' is defined to be greater than one. Furthermore, by means of gated transmission, uplink and downlink interference may be reduced leading to improved uplink and downlink capacity.}
| {"ANSWER": "RAN_AH1"} |
S2-2301436.txt | {"WORKING GROUP": "SA2"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{The location of the hosting networks can also be included as part of the additional information. - Location of the hosting network represented in the human readable format (e.g. civic address) can be displayed to the end user, so that the end user knows where to gain for access to the hosting network. - Location of the hosting network represented in the format of the UE's current serving network location ID (e.g. TAIs, cell IDs) can be also useful for both manual selection and automatic selection. Since, if the UE is in the range of the specific serving network area where hosting network is available, the UE can use such serving network location information as a trigger to start the scan of hosting network if time validity condition is also met. Then if hosting network is found, the hosting network can be either presented to the end user for manual selection, or the hosting network can be selected automatically. Otherwise, when the time validity condition of hosting network is met, the UE may need to scan for the hosting network continuously when the UE is not in the coverage of the hosting network. After registered in the hosting network, the UE is provisioned with information (e.g. Allowed NSSAI, URSP rule) by the hosting network. From the UE point of view, it knows which Route Selection Descriptor (e.g. S-NSSAI/DNN) is associated with which Traffic Descriptor from the URSP rules.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{The location of the hosting networks can also be included as part of the additional information. - Location of the hosting network represented in the human readable format (e.g. civic address) can be displayed to the end user, so that the end user knows where to gain for access to the hosting network. - Location of the hosting network represented in the format of the UE's current serving network location ID (e.g. TAIs, cell IDs) can be also useful for both manual selection and automatic selection. Since, if the UE is in the range of the specific serving network area where hosting network is available, the UE can use such serving network location information as a trigger to start the scan of hosting network if time validity condition is also met. Then if hosting network is found, the hosting network can be either presented to the end user for manual selection, or the hosting network can be selected automatically. Otherwise, when the time validity condition of hosting network is met, the UE may need to scan for the hosting network continuously when the UE is not in the coverage of the hosting network. After registered in the hosting network, the UE is provisioned with information (e.g. Allowed NSSAI, URSP rule) by the hosting network. From the UE point of view, it knows which Route Selection Descriptor (e.g. S-NSSAI/DNN) is associated with which Traffic Descriptor from the URSP rules.}
| {"ANSWER": "SA2"} |
S5-111678.txt | {"WORKING GROUP": "SA5"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Detailed notes taken by Nigel as comments in Tdoc 099 (updated version in S5vTMFa109) On the paragraph about “…need to provide information model input in UML format”: Agreement: To define two separate sets of outputs (e.g. UML model and Word tables) for TMF and 3GPP respectively, which need to be semantically identical. On the next paragraph (“The proposal recognizes that…”) it was requested that “wireless specific model” is replaced by something more relevant for 3GPP (since the SA5 models cover both radio networks as well as core networks, IMS, subscription management etc.). During the meeting, and updated wording was agreed and included in 109. The last five bullets of section 1 were also discussed and some updates were agreed. References: Agreed with some minor updates recorded by Nigel. Definitions in 3.1.We discussed the proposal by Ciena. Discussion on whether the Information Model definition would also cover the SS/encoding level. Result: Quite extensive rewording of the definitions on Information Model, Data Model, Process Model. Converged Information Model: Should be moved to a separate document about “FNM governance and Working procedures”. End of Day 1 discussions; to be continued later. Updates to be captured in doc 109.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Detailed notes taken by Nigel as comments in Tdoc 099 (updated version in S5vTMFa109) On the paragraph about “…need to provide information model input in UML format”: Agreement: To define two separate sets of outputs (e.g. UML model and Word tables) for TMF and 3GPP respectively, which need to be semantically identical. On the next paragraph (“The proposal recognizes that…”) it was requested that “wireless specific model” is replaced by something more relevant for 3GPP (since the SA5 models cover both radio networks as well as core networks, IMS, subscription management etc.). During the meeting, and updated wording was agreed and included in 109. The last five bullets of section 1 were also discussed and some updates were agreed. References: Agreed with some minor updates recorded by Nigel. Definitions in 3.1.We discussed the proposal by Ciena. Discussion on whether the Information Model definition would also cover the SS/encoding level. Result: Quite extensive rewording of the definitions on Information Model, Data Model, Process Model. Converged Information Model: Should be moved to a separate document about “FNM governance and Working procedures”. End of Day 1 discussions; to be continued later. Updates to be captured in doc 109.}
| {"ANSWER": "SA5"} |
C6-110150.txt | {"WORKING GROUP": "CT6"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{IARI SIP Routing to the UICC: The initial SIP REGISTER request sent by the ME contains the IARIs associated with active applications hosted on the UICC along with the active applications hosted on the ME. If the list of IARIs associated with active applications on the UICC changes, the UICC indicates this change to the ME. The ME then sends the necessary SIP REGISTER request containing the UICC hosted IARIs and ME hosted IARIs to reflect this change. The ME sends the list of registered IMPUs as received from the IM CN Subsystem in response to the IMS registration as an indication to the UICC that the IMS registration has been completed successfully and that the UICC IARIs have been registered associated with these IMPUs. After the successful registration the ME forwards to the UICC all SIP requests containing an Accept-Contact header field containing the IARIs associated with the active applications hosted on the UICC. The ME also forwards to the UICC any SIP responses or subsequent SIP requests received that are part of the same dialog or standalone transaction as an initial SIP request forwarded to the UICC or received from the UICC. Message flow: Message flow for IMPU explicit registration based solution: Registration: Upon reception of OPEN CHANNEL for IMS command, the ME will initiate a registration process with the parameters provided by the UICC. 1. Open Channel for IMS 2.Register(UICC_IMPU) IMS home network 3.Registration information flow – User not registered,as defined inTS24.229 5 Terminal Response OK (ME IP address used) De-Registration: Initiated by the user: UICCMEP-CSCF 2 – Register (UICC_IMPU, Period=0) IMS home network 3.De-Registration information flow, as defined in TS24.229 4. 200 OK 6 Event Channel Status (IMS de-registration) 1 CloseChannelforIMS (UICC_IMPU) 5 TerminalResponse(OK) 2 – Register (UICC_IMPU, Period=0) IMS home network 3.De-Registration information flow, as defined in TS24.229 6 Event Channel Status (IMS de-registration) 1 CloseChannelforIMS 5 TerminalResponse(OK) Initiated by the Network (i.e. administrative de-registration). In this case UICCMEP-CSCF 1 – De-Register (IMPU1) IMS home network 2. UE inform 4 Event Channel Status (IMS de-registration) 3. 200 OK 1 – De-Register (IMPU1) IMS home network 2.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{IARI SIP Routing to the UICC: The initial SIP REGISTER request sent by the ME contains the IARIs associated with active applications hosted on the UICC along with the active applications hosted on the ME. If the list of IARIs associated with active applications on the UICC changes, the UICC indicates this change to the ME. The ME then sends the necessary SIP REGISTER request containing the UICC hosted IARIs and ME hosted IARIs to reflect this change. The ME sends the list of registered IMPUs as received from the IM CN Subsystem in response to the IMS registration as an indication to the UICC that the IMS registration has been completed successfully and that the UICC IARIs have been registered associated with these IMPUs. After the successful registration the ME forwards to the UICC all SIP requests containing an Accept-Contact header field containing the IARIs associated with the active applications hosted on the UICC. The ME also forwards to the UICC any SIP responses or subsequent SIP requests received that are part of the same dialog or standalone transaction as an initial SIP request forwarded to the UICC or received from the UICC. Message flow: Message flow for IMPU explicit registration based solution: Registration: Upon reception of OPEN CHANNEL for IMS command, the ME will initiate a registration process with the parameters provided by the UICC. 1. Open Channel for IMS 2.Register(UICC_IMPU) IMS home network 3.Registration information flow – User not registered,as defined inTS24.229 5 Terminal Response OK (ME IP address used) De-Registration: Initiated by the user: UICCMEP-CSCF 2 – Register (UICC_IMPU, Period=0) IMS home network 3.De-Registration information flow, as defined in TS24.229 4. 200 OK 6 Event Channel Status (IMS de-registration) 1 CloseChannelforIMS (UICC_IMPU) 5 TerminalResponse(OK) 2 – Register (UICC_IMPU, Period=0) IMS home network 3.De-Registration information flow, as defined in TS24.229 6 Event Channel Status (IMS de-registration) 1 CloseChannelforIMS 5 TerminalResponse(OK) Initiated by the Network (i.e. administrative de-registration). In this case UICCMEP-CSCF 1 – De-Register (IMPU1) IMS home network 2. UE inform 4 Event Channel Status (IMS de-registration) 3. 200 OK 1 – De-Register (IMPU1) IMS home network 2.}
| {"ANSWER": "CT6"} |
R3-101980.txt | {"WORKING GROUP": "RAN3"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{In particular, RAN WG1 has arrived at the following agreements: A Rel-10 3C/4C-HSDPA UE, when configured with single or dual cells with or without MIMO should use the legacy HS-DPCCH physical layer design (channel coding, spreading factor, modulation, CQI reporting) as specified in previous releases (Rel-5 through Rel-9). With regard to the configuration of parameters that are relevant to the PCI/CQI feedback information that is carried on HS-DPCCH: The minimum CQI feedback cycle is 4 ms for all cases when 3 or 4 carriers are configured. The following parameters are common to all carriers: CQI feedback cycle N_cqi_transmit CQI_DTX_Priority CQI_DTX_Timer ΔCQI as signaled today to the UE via RRC signaling Note that the actual CQI power offset that will be applied on the HS-DPCCH will depend on the activation/deactivation status of the secondary serving HS-DSCH cells and will be derived from ΔCQI. 2. Action for RAN2: RAN WG1 kindly asks RAN WG2 to take the agreements into account in the definition of the RAN2 specifications for 4C-HSDPA.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{In particular, RAN WG1 has arrived at the following agreements: A Rel-10 3C/4C-HSDPA UE, when configured with single or dual cells with or without MIMO should use the legacy HS-DPCCH physical layer design (channel coding, spreading factor, modulation, CQI reporting) as specified in previous releases (Rel-5 through Rel-9). With regard to the configuration of parameters that are relevant to the PCI/CQI feedback information that is carried on HS-DPCCH: The minimum CQI feedback cycle is 4 ms for all cases when 3 or 4 carriers are configured. The following parameters are common to all carriers: CQI feedback cycle N_cqi_transmit CQI_DTX_Priority CQI_DTX_Timer ΔCQI as signaled today to the UE via RRC signaling Note that the actual CQI power offset that will be applied on the HS-DPCCH will depend on the activation/deactivation status of the secondary serving HS-DSCH cells and will be derived from ΔCQI. 2. Action for RAN2: RAN WG1 kindly asks RAN WG2 to take the agreements into account in the definition of the RAN2 specifications for 4C-HSDPA.}
| {"ANSWER": "RAN3"} |
C6-220267.txt | {"WORKING GROUP": "CT6"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{The following areas of work are expected to be covered (non-exhaustive): 1) Enhancement of the NAS protocol to support NR RedCap devices. 2) Potential update of the PLMN selection to support NR RedCap devices. 3) Update of related eDRX parameters and UE configuration parameters. Update the definition of 3GPP-RAT-Type sub-attribute to support NR RedCap. 1) Update the definition of RAT type in common data types for service based interfaces to support NR RedCap. 2) Potential update of SMS service and SM service to support NR RedCap devices. 3) Update of Namf_Communication service to support NR RedCap devices. 4) Potential update of TS 23.008 to enable access restriction for NR RedCap RAT. 5) Update of UDM services to enable eDRX parameter for NR RedCap devices. 1) Potential uUpdate of TS 31.102 to support NR RedCap devices and eDRX for RedCap. 2) Potential update of the USAT specifications to support NR RedCap devices. 5 Expected Output and Time scale: 6 Work item Rapporteur(s): Chen Xu, China Mobile, chenxu@chinamobile.com 7 Work item leadership: 8 Aspects that involve other WGs: 9 Supporting Individual Members:}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{The following areas of work are expected to be covered (non-exhaustive): 1) Enhancement of the NAS protocol to support NR RedCap devices. 2) Potential update of the PLMN selection to support NR RedCap devices. 3) Update of related eDRX parameters and UE configuration parameters. Update the definition of 3GPP-RAT-Type sub-attribute to support NR RedCap. 1) Update the definition of RAT type in common data types for service based interfaces to support NR RedCap. 2) Potential update of SMS service and SM service to support NR RedCap devices. 3) Update of Namf_Communication service to support NR RedCap devices. 4) Potential update of TS 23.008 to enable access restriction for NR RedCap RAT. 5) Update of UDM services to enable eDRX parameter for NR RedCap devices. 1) Potential uUpdate of TS 31.102 to support NR RedCap devices and eDRX for RedCap. 2) Potential update of the USAT specifications to support NR RedCap devices. 5 Expected Output and Time scale: 6 Work item Rapporteur(s): Chen Xu, China Mobile, chenxu@chinamobile.com 7 Work item leadership: 8 Aspects that involve other WGs: 9 Supporting Individual Members:}
| {"ANSWER": "CT6"} |
RT-080045.txt | {"WORKING GROUP": "RAN_AH1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{22.022 Personalization of GSM ME mobile functionality specification – Stage 1 This specification describes functional specifications of five features to personalize UE. These features are called: – network personalization; – network subset personalization; – service provider (SP) personalization; – corporate personalization; – UMTS subscriber identity module (USIM) personalization. This specification describes requirements for UE, which provide these personalization features. 22.024 Description of charge advice information (CAI) This specification describes an overall view of how the charging advice supplementary service shall operate both in the network and within the UE. The charging supplementary service is described in TS 22.086. 22.030 Man-machine interface (MMI) of the mobile station This specification describes the requirements for and gives guidelines on the MMI for calls on the 3G UE. This includes the requirements of the user procedures for call control and supplementary service control, the requirements on the physical input media and the output, such as indications and displayed information. 22.034 High speed circuit switched data (HSCSD) – Stage 1 This specification describes the Stage 1 description of HSCSD. HSCSD is a feature that allows users subscribing to the general bearer services to access user rates that can be achieved with one or more traffic channel. HSCSD also defines a flexible use of air interface resources, which makes efficient and flexible use of higher user rates feasible. 22.038 SIM application toolkit (SAT) – Stage 1 This specification describes the Stage 1 description of the SAT primarily from the subscriber’s and serving environment’s points of view, and does not deal with the details of the human interface itself. It includes information applicable to network operators, serving environments and terminal, switch and database manufacturers and contains the core requirements for a SAT which are sufficient to provide a complete service.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{22.022 Personalization of GSM ME mobile functionality specification – Stage 1 This specification describes functional specifications of five features to personalize UE. These features are called: – network personalization; – network subset personalization; – service provider (SP) personalization; – corporate personalization; – UMTS subscriber identity module (USIM) personalization. This specification describes requirements for UE, which provide these personalization features. 22.024 Description of charge advice information (CAI) This specification describes an overall view of how the charging advice supplementary service shall operate both in the network and within the UE. The charging supplementary service is described in TS 22.086. 22.030 Man-machine interface (MMI) of the mobile station This specification describes the requirements for and gives guidelines on the MMI for calls on the 3G UE. This includes the requirements of the user procedures for call control and supplementary service control, the requirements on the physical input media and the output, such as indications and displayed information. 22.034 High speed circuit switched data (HSCSD) – Stage 1 This specification describes the Stage 1 description of HSCSD. HSCSD is a feature that allows users subscribing to the general bearer services to access user rates that can be achieved with one or more traffic channel. HSCSD also defines a flexible use of air interface resources, which makes efficient and flexible use of higher user rates feasible. 22.038 SIM application toolkit (SAT) – Stage 1 This specification describes the Stage 1 description of the SAT primarily from the subscriber’s and serving environment’s points of view, and does not deal with the details of the human interface itself. It includes information applicable to network operators, serving environments and terminal, switch and database manufacturers and contains the core requirements for a SAT which are sufficient to provide a complete service.}
| {"ANSWER": "RAN_AH1"} |
S3-020303.txt | {"WORKING GROUP": "SA3"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{As one solution the alias can be passed on from terminal to the LCS Client application when the subscriber invokes a request e.g. to a specific service type. As another solution some secured network proxy may allocate the anonymous ID (alias) to replace MSISDN. The LCS client will use alias as an identifier for the target subscriber instead of the true MSISDN identity. GMLC will in response use the same alias. It should be possible to define both permanent and temporary alias. The service requirements for anonymity are to be discussed and agreed in SA1 and specified in TS 22.071 . Related privacy issues in Presence and Location services: Location information is an important part of the Presence information used in the Presence service. The subscriber should be able to set privacy requirements also for the location information used in the Presence service. Preferably the privacy settings and control mechanisms that the subscriber has defined for location services should be applicable as such also for the location information in Presence services. Privacy settings for presence could possibly be shared with LCS, but it need further discussion is needed between presence and LCS people. The relations between privacy issues in presence and in LCS should be discussed in SA1 and SA3. 6.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{As one solution the alias can be passed on from terminal to the LCS Client application when the subscriber invokes a request e.g. to a specific service type. As another solution some secured network proxy may allocate the anonymous ID (alias) to replace MSISDN. The LCS client will use alias as an identifier for the target subscriber instead of the true MSISDN identity. GMLC will in response use the same alias. It should be possible to define both permanent and temporary alias. The service requirements for anonymity are to be discussed and agreed in SA1 and specified in TS 22.071 . Related privacy issues in Presence and Location services: Location information is an important part of the Presence information used in the Presence service. The subscriber should be able to set privacy requirements also for the location information used in the Presence service. Preferably the privacy settings and control mechanisms that the subscriber has defined for location services should be applicable as such also for the location information in Presence services. Privacy settings for presence could possibly be shared with LCS, but it need further discussion is needed between presence and LCS people. The relations between privacy issues in presence and in LCS should be discussed in SA1 and SA3. 6.}
| {"ANSWER": "SA3"} |
R4-123510.txt | {"WORKING GROUP": "RAN4"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{- For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”. R4-112429, “Information on band usage plan in 900 MHz band in Japan” , RAN4#59 RP-110901, “New Study item proposal for 900MHz UMTS/LTE operation”, RAN#52 “Report of technical conditions for mobile communications in 900 MHz band” (In Japanese, May, 2011) RP-110447, “Study Item proposal for 800~900MHz interference issue”, RAN#51 R4-113677: “Japanese 900 MHz: A-MPR study and whether to create new band or re-use band 8”, Nokia R4-113792: “Band 5 and Band 8 coexistence”, Qualcomm R4-113678: “A-MPR study for 905-915 MHz uplink in Korea”, Nokia R4-113328: “LTE A-MPR Consideration for Band 8 in Japan”, SOFTBANK MOBILE R4-113525 “Coexistence in 900 MHz bands for UMTS”, Qualcomm Incorporated R4-113506 “Band XIX DL protection from UMTS Band VIII UEs in Japan”, NTT DOCOMO, NEC, Fujitsu, Panasonic R4-121387 “Way Forward Proposal for Japanese 900MHz”, SOFTBANK MOBILE R4-122134 “Updated WF for Japanese 900MHz”, SOFTBANK MOBILE R4-122508 “Coexistence Study for LTE 900MHz”, LG Electronics R4-122825 “UL emissions study for Band 8 in Japan”, Nokia R4-122915 “Japanese LTE900 study”, Renesas Mobile Europe R4-123012 “Band 8 UE in Japan", Ericsson, ST-Ericsson R4-123231 “Spurious Emission Simulation Results”, Intel R4-123284 “900 MHz UE coexistence in Japan”, Qualcomm [Unchanged Portions Skipped] 9.2 Definition of a new band for Japanese and/or Korean 900 MHz bands 9.2.1 900MHz band with Band 8 duplex filter There are a couple of RF frontend configurations possible for defining a new band for Japanese/Korean 900MHz. One approach is to reuse Band 8 RF components to minimize diversity with the introduction of the new band. This scheme will be advantageous from economical standpoint, i.e. merit of scale of UE or RF parts. Apparently this scheme will inherit the same RF issues discussed in 9.1 but is considered easier to introduce new capabilities than reusing Band 8. The discussion in 9.1 can be applied directly in terms of A-MPR. 9.2.2 900MHz band with dedicated duplex filter An alternative approach is to provide RF frontend tuned for Japan/Korea spectrum arrangement. While this approach promises the best possible RF performance, concerns are beyond technical aspects, such as UE/parts supply. So far no technical evaluation has been done for this scheme but further study and conclusion are expected. 9.3 Finalized spectrum allocation and relevant studies for Japan 9.3.1 Finalized spectrum allocation In February 2012, SOFTBANK MOBILE was awarded for full 15MHz. Spectrum usage plan was proposed in , which assumed the reuse of Band 8 UE. For E-UTRA, spectrum is divided into 5MHz (900 – 905MHz) and 10 MHz (905 – 915MHz) for compatibility with the existing Band 8 specification and 15MHz is to be realized with intra-band carrier aggregation (out of the scope of the SI). The arrangement is shown in Figure 9.3.1. SLEEP LTE(5MHz) 900905 910 915 LTE(10MHz) SLEEP LTE(5MHz) 945950 955 960 LTE(10MHz) W-CDMA 900905 910 915 LTE(10MHz) SLEEP W-CDMA 945950 955 960 LTE(10MHz) Intra-Band Carrier Aggregation (Rel.10UE) Intra-Band Carrier Aggregation (Rel.10UE) LTE(5MHz) 900905 910 915 LTE(10MHz) LTE(5MHz) 945950 955 960 LTE(10MHz) 900905 910 915 LTE(10MHz) 945950 955 960 LTE(10MHz) Intra-Band Carrier Aggregation (Rel.10UE) Intra-Band Carrier Aggregation (Rel.10UE) Figure 9.3.1: Spectrum Allocation Plan for Japanese 900MHz 9.3.2 UE evaluation results A number of evaluation results for UE performance were presented in in response to the spectrum allocation proposal in the previous section. Note that, in the course of discussion, it was confirmed impossible to introduce a newly defined A-MPR to Band 8. Instead, evaluations are conducted for the necessity of RB allocation limitation and PUCCH over-provisioning for both 5MHz and 10MHz cases. Proposed results are summarized in Table 9.3.2. Note that the following results are based on Rel-8 performance assumptions, i.e. -25dBc for I/Q impairment and LO leakage. Table 9.3.2: UE evaluation results for Band 8 for Japan While there is some diversity observed among results, it can be understood that the diversity reflects possible different implementations, esp. on the performance of power amplifiers.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{- For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”. R4-112429, “Information on band usage plan in 900 MHz band in Japan” , RAN4#59 RP-110901, “New Study item proposal for 900MHz UMTS/LTE operation”, RAN#52 “Report of technical conditions for mobile communications in 900 MHz band” (In Japanese, May, 2011) RP-110447, “Study Item proposal for 800~900MHz interference issue”, RAN#51 R4-113677: “Japanese 900 MHz: A-MPR study and whether to create new band or re-use band 8”, Nokia R4-113792: “Band 5 and Band 8 coexistence”, Qualcomm R4-113678: “A-MPR study for 905-915 MHz uplink in Korea”, Nokia R4-113328: “LTE A-MPR Consideration for Band 8 in Japan”, SOFTBANK MOBILE R4-113525 “Coexistence in 900 MHz bands for UMTS”, Qualcomm Incorporated R4-113506 “Band XIX DL protection from UMTS Band VIII UEs in Japan”, NTT DOCOMO, NEC, Fujitsu, Panasonic R4-121387 “Way Forward Proposal for Japanese 900MHz”, SOFTBANK MOBILE R4-122134 “Updated WF for Japanese 900MHz”, SOFTBANK MOBILE R4-122508 “Coexistence Study for LTE 900MHz”, LG Electronics R4-122825 “UL emissions study for Band 8 in Japan”, Nokia R4-122915 “Japanese LTE900 study”, Renesas Mobile Europe R4-123012 “Band 8 UE in Japan", Ericsson, ST-Ericsson R4-123231 “Spurious Emission Simulation Results”, Intel R4-123284 “900 MHz UE coexistence in Japan”, Qualcomm [Unchanged Portions Skipped] 9.2 Definition of a new band for Japanese and/or Korean 900 MHz bands 9.2.1 900MHz band with Band 8 duplex filter There are a couple of RF frontend configurations possible for defining a new band for Japanese/Korean 900MHz. One approach is to reuse Band 8 RF components to minimize diversity with the introduction of the new band. This scheme will be advantageous from economical standpoint, i.e. merit of scale of UE or RF parts. Apparently this scheme will inherit the same RF issues discussed in 9.1 but is considered easier to introduce new capabilities than reusing Band 8. The discussion in 9.1 can be applied directly in terms of A-MPR. 9.2.2 900MHz band with dedicated duplex filter An alternative approach is to provide RF frontend tuned for Japan/Korea spectrum arrangement. While this approach promises the best possible RF performance, concerns are beyond technical aspects, such as UE/parts supply. So far no technical evaluation has been done for this scheme but further study and conclusion are expected. 9.3 Finalized spectrum allocation and relevant studies for Japan 9.3.1 Finalized spectrum allocation In February 2012, SOFTBANK MOBILE was awarded for full 15MHz. Spectrum usage plan was proposed in , which assumed the reuse of Band 8 UE. For E-UTRA, spectrum is divided into 5MHz (900 – 905MHz) and 10 MHz (905 – 915MHz) for compatibility with the existing Band 8 specification and 15MHz is to be realized with intra-band carrier aggregation (out of the scope of the SI). The arrangement is shown in Figure 9.3.1. SLEEP LTE(5MHz) 900905 910 915 LTE(10MHz) SLEEP LTE(5MHz) 945950 955 960 LTE(10MHz) W-CDMA 900905 910 915 LTE(10MHz) SLEEP W-CDMA 945950 955 960 LTE(10MHz) Intra-Band Carrier Aggregation (Rel.10UE) Intra-Band Carrier Aggregation (Rel.10UE) LTE(5MHz) 900905 910 915 LTE(10MHz) LTE(5MHz) 945950 955 960 LTE(10MHz) 900905 910 915 LTE(10MHz) 945950 955 960 LTE(10MHz) Intra-Band Carrier Aggregation (Rel.10UE) Intra-Band Carrier Aggregation (Rel.10UE) Figure 9.3.1: Spectrum Allocation Plan for Japanese 900MHz 9.3.2 UE evaluation results A number of evaluation results for UE performance were presented in in response to the spectrum allocation proposal in the previous section. Note that, in the course of discussion, it was confirmed impossible to introduce a newly defined A-MPR to Band 8. Instead, evaluations are conducted for the necessity of RB allocation limitation and PUCCH over-provisioning for both 5MHz and 10MHz cases. Proposed results are summarized in Table 9.3.2. Note that the following results are based on Rel-8 performance assumptions, i.e. -25dBc for I/Q impairment and LO leakage. Table 9.3.2: UE evaluation results for Band 8 for Japan While there is some diversity observed among results, it can be understood that the diversity reflects possible different implementations, esp. on the performance of power amplifiers.}
| {"ANSWER": "RAN4"} |
S1-020294.txt | {"WORKING GROUP": "SA1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Since the user’s network profile is part of the Generic User Profile a relation to GUP exists. From the OSA point of view potential work in this area is already delivered and should be carefully reviewed from SWG GUP. Relation of OSA to Multimedia Broadcast and Multicast Service (MBMS) No relation identified. Relation of OSA to Multimedia Messaging Service (MMS) OSA provides facilities to notify a user. This facility is currently limited to either a SMS or USSD. However, this facility could be used for a MMS relay server (external to the Network) to notify a user of existing Multimedia Messages. It is planned to enhance OSA functionality to support the control communication between a MMS relay server and a VASP Multimedia Messaging Server. Relation of OSA to Location Service (LCS) OSA provides an application with information concerning the user's location. Location, accuracy and age of location are currently provided. There is a relation between OSA and LCS. For the time being the OSA work to provide Location Information is closed. Relation of OSA to Presence The OSA provides an application access to presence capabilities within the network. Presence related information may be requested or supplied by an OSA application and may include, but not limited to presence information pertaining to the presence service or user availability. There is a clear relation from OSA to Presence. Relation of OSA to Priority No relation (yet) identified.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Since the user’s network profile is part of the Generic User Profile a relation to GUP exists. From the OSA point of view potential work in this area is already delivered and should be carefully reviewed from SWG GUP. Relation of OSA to Multimedia Broadcast and Multicast Service (MBMS) No relation identified. Relation of OSA to Multimedia Messaging Service (MMS) OSA provides facilities to notify a user. This facility is currently limited to either a SMS or USSD. However, this facility could be used for a MMS relay server (external to the Network) to notify a user of existing Multimedia Messages. It is planned to enhance OSA functionality to support the control communication between a MMS relay server and a VASP Multimedia Messaging Server. Relation of OSA to Location Service (LCS) OSA provides an application with information concerning the user's location. Location, accuracy and age of location are currently provided. There is a relation between OSA and LCS. For the time being the OSA work to provide Location Information is closed. Relation of OSA to Presence The OSA provides an application access to presence capabilities within the network. Presence related information may be requested or supplied by an OSA application and may include, but not limited to presence information pertaining to the presence service or user availability. There is a clear relation from OSA to Presence. Relation of OSA to Priority No relation (yet) identified.}
| {"ANSWER": "SA1"} |
R1-040941.txt | {"WORKING GROUP": "RAN1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Therefore, with static allocation, maximum number of E-DPDCH is 4. In figure 2, we show an example of dynamic allocation. We assume that the sum of legacy DPDCH and E-DPDCH is 6. As shown in figure 2, the maximum number of E-DPDCHs is 6. Therefore, resource utilization point of view, dynamic allocation has advantage over static allocation. In joint session in ad-hoc meeting at Cannes, 2 ms TTI was decided to be supported with 10 ms TTI. There was a concern that dynamic allocation may be required to signal which channelisation codes are used for E-DPDCH with 2 ms TTI since Node B does not know the number of legacy DPDCHs before TFCI information for DPDCH is obtained. A possible solution is to allocate the channelisation code for E-DPDCH in reverse order from that of Release 5 as shown in figure 3. That is, DPDCH code starts from C(4,1) in I branch and E-DPDCH code starts from C(4,2) in Q branch. With this allocation rule, the signalling for E-DPDCH channelisation code is not required even in 2 ms TTI. I Note: Maximum number of E - DPDCH = 4 DPDCH (4,1) Q DPCCH (256,0) E - DPDCH (4, 2 ) E - DPDCH (4,3) E - DPDCH (4,3) E - DPDCH (4,2) HS - DPCCH (256, 64 ) Note: Maximum number of E Figure 1. Static allocation of E-DPDCH.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Therefore, with static allocation, maximum number of E-DPDCH is 4. In figure 2, we show an example of dynamic allocation. We assume that the sum of legacy DPDCH and E-DPDCH is 6. As shown in figure 2, the maximum number of E-DPDCHs is 6. Therefore, resource utilization point of view, dynamic allocation has advantage over static allocation. In joint session in ad-hoc meeting at Cannes, 2 ms TTI was decided to be supported with 10 ms TTI. There was a concern that dynamic allocation may be required to signal which channelisation codes are used for E-DPDCH with 2 ms TTI since Node B does not know the number of legacy DPDCHs before TFCI information for DPDCH is obtained. A possible solution is to allocate the channelisation code for E-DPDCH in reverse order from that of Release 5 as shown in figure 3. That is, DPDCH code starts from C(4,1) in I branch and E-DPDCH code starts from C(4,2) in Q branch. With this allocation rule, the signalling for E-DPDCH channelisation code is not required even in 2 ms TTI. I Note: Maximum number of E - DPDCH = 4 DPDCH (4,1) Q DPCCH (256,0) E - DPDCH (4, 2 ) E - DPDCH (4,3) E - DPDCH (4,3) E - DPDCH (4,2) HS - DPCCH (256, 64 ) Note: Maximum number of E Figure 1. Static allocation of E-DPDCH.}
| {"ANSWER": "RAN1"} |
R1-2104193.txt | {"WORKING GROUP": "RAN1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Determining UE-A and UE-B at the higher layer can reduce the design complexity reduced and the impact to specification. It is clear that as the intended receiver, a UE can be UE A to provide coordination information to the transmitting UE, UE B, for resource (re)-selection. Also, in the groupcast scenario, as one of the receivers, a UE can provide the coordination information to UE B. In this scenario, it is not necessary that all intended receivers in the groupcast need to provide coordination information. For example, in truck platooning, the leading truck may only request one or several furthest trailing trucks to provide coordination information for the leading truck to select resources for the groupcast. Therefore, UE A can be one of the intended receivers. On the other hand, the inter-UE coordination process can be used either for pedestrian UEs or public safety UEs. For instance, if RSUs are deployed, a RSU can be located at an area where pedestrians are likely to be present (e.g., intersection, traffic, light, pedestrian crossway, etc.) and use inter-UE coordination as follows: after sensing, the RSU reserves some resources for pedestrian usage for UEs in its vicinity. V2P UEs with SCI detection or data reception capability can obtain the configuration of the reserved resources from the RSU. The V2P UEs can then select the resource from the resources reserved for the V2Ps by the RSU (UE B takes this into account in the resource selection for its own transmission). For the public safety case, a similar solution can be used, with the incident commander as the leader UE, reserving resources for other UEs.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Determining UE-A and UE-B at the higher layer can reduce the design complexity reduced and the impact to specification. It is clear that as the intended receiver, a UE can be UE A to provide coordination information to the transmitting UE, UE B, for resource (re)-selection. Also, in the groupcast scenario, as one of the receivers, a UE can provide the coordination information to UE B. In this scenario, it is not necessary that all intended receivers in the groupcast need to provide coordination information. For example, in truck platooning, the leading truck may only request one or several furthest trailing trucks to provide coordination information for the leading truck to select resources for the groupcast. Therefore, UE A can be one of the intended receivers. On the other hand, the inter-UE coordination process can be used either for pedestrian UEs or public safety UEs. For instance, if RSUs are deployed, a RSU can be located at an area where pedestrians are likely to be present (e.g., intersection, traffic, light, pedestrian crossway, etc.) and use inter-UE coordination as follows: after sensing, the RSU reserves some resources for pedestrian usage for UEs in its vicinity. V2P UEs with SCI detection or data reception capability can obtain the configuration of the reserved resources from the RSU. The V2P UEs can then select the resource from the resources reserved for the V2Ps by the RSU (UE B takes this into account in the resource selection for its own transmission). For the public safety case, a similar solution can be used, with the incident commander as the leader UE, reserving resources for other UEs.}
| {"ANSWER": "RAN1"} |
RT-99089.txt | {"WORKING GROUP": "RAN_AH1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{A Common Pilot Channel (CPICH) is defined. It is an unmodulated downlink channel, that is the phase reference for other downlink physical channels. There is always one primary CPICH in each cell. There may also be additional secondary CPICHs in a cell. To be able to support inter-frequency handover as well as measurements on other carrier frequencies or carriers of other systems, like GSM, a compressed mode of operation is defined. The function is implemented by having some slots empty, but without deleting any user data. Instead the user data is transmitted in the remaining slots. The number of slots that is not used can be variable with a minimum of three slots (giving minimum idle lengths of at least 1.73 milliseconds). The slots can be empty either in the middle of a frame or at the end and in the beginning of the consecutive frame. If and how often is controlled by the RRC functionality in Layer 3. Uplink Spreading consists of two operations. The first is the channelisation operation, which transforms every data symbol into a number of chips, thus increasing the bandwidth of the signal. The number of chips per data symbol is called the Spreading Factor (SF). The second operation is the scrambling operation, where a scrambling code is applied to the spread signal. In the channelisation operation, data symbol on so-called I- and Q-branches are independently multiplied with a code. The channelisation codes are Orthogonal Variable Spreading Factor (OVSF) codes that preserve the orthogonality between a user’s different physical channels. With the scrambling operation, the resultant signals on the I- and Q-branches are further multiplied by complex-valued scrambling code, where I and Q denote real and imaginary parts, respectively. Note that before complex multiplication binary values 0 and 1 are mapped to +1 and -1, respectively. Figure 8 illustrates the spreading and modulation for the case of multiple uplink DPDCHs. Note that this figure only shows the principle, and does not necessarily describe an actual implementation. Modulation is dual-channel QPSK (i.e. ; separate BPSK on I- and Q-channel), where the uplink DPDCH and DPCCH are mapped to the I and Q branch respectively.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{A Common Pilot Channel (CPICH) is defined. It is an unmodulated downlink channel, that is the phase reference for other downlink physical channels. There is always one primary CPICH in each cell. There may also be additional secondary CPICHs in a cell. To be able to support inter-frequency handover as well as measurements on other carrier frequencies or carriers of other systems, like GSM, a compressed mode of operation is defined. The function is implemented by having some slots empty, but without deleting any user data. Instead the user data is transmitted in the remaining slots. The number of slots that is not used can be variable with a minimum of three slots (giving minimum idle lengths of at least 1.73 milliseconds). The slots can be empty either in the middle of a frame or at the end and in the beginning of the consecutive frame. If and how often is controlled by the RRC functionality in Layer 3. Uplink Spreading consists of two operations. The first is the channelisation operation, which transforms every data symbol into a number of chips, thus increasing the bandwidth of the signal. The number of chips per data symbol is called the Spreading Factor (SF). The second operation is the scrambling operation, where a scrambling code is applied to the spread signal. In the channelisation operation, data symbol on so-called I- and Q-branches are independently multiplied with a code. The channelisation codes are Orthogonal Variable Spreading Factor (OVSF) codes that preserve the orthogonality between a user’s different physical channels. With the scrambling operation, the resultant signals on the I- and Q-branches are further multiplied by complex-valued scrambling code, where I and Q denote real and imaginary parts, respectively. Note that before complex multiplication binary values 0 and 1 are mapped to +1 and -1, respectively. Figure 8 illustrates the spreading and modulation for the case of multiple uplink DPDCHs. Note that this figure only shows the principle, and does not necessarily describe an actual implementation. Modulation is dual-channel QPSK (i.e. ; separate BPSK on I- and Q-channel), where the uplink DPDCH and DPCCH are mapped to the I and Q branch respectively.}
| {"ANSWER": "RAN_AH1"} |
C1-184905.txt | {"WORKING GROUP": "CT1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{This makes unnecessary changes in comparison to the authentication in EPS. 2. A side effect of changing the protocol is that there will be impacts to RAN5 test cases and to field and inter-operability testing. CT1 considers this will delay deployment of 5GS. 3. RFC 4187, RFC 5448 and TS 33.402 subclause 6.2, indicates that the UE can start key generation - and thus start creation of a (partial) security context – at EAP-Request. UE vendors wish to maintain this possibility and reuse, not change, existing implementation of EAP authentication. Thus CT1 kindly request SA3 to consider that also for EAP AKA' authentication, the ngKSI is provided to the UE in AUTHENTICATION REQUEST , just as it was before S3-181990. CT1 is aware that SA3 has introduced ABBA, which is used as part of security key generation. If SA3 feels that ABBA must be provided along with ngKSI. CT1 can accept that ABBA is also provided at start of EAP primary authentication. In fact, for 5G-AK, ABBA is provided at start of authentication procedure and this is another reason not to diverge.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{This makes unnecessary changes in comparison to the authentication in EPS. 2. A side effect of changing the protocol is that there will be impacts to RAN5 test cases and to field and inter-operability testing. CT1 considers this will delay deployment of 5GS. 3. RFC 4187, RFC 5448 and TS 33.402 subclause 6.2, indicates that the UE can start key generation - and thus start creation of a (partial) security context – at EAP-Request. UE vendors wish to maintain this possibility and reuse, not change, existing implementation of EAP authentication. Thus CT1 kindly request SA3 to consider that also for EAP AKA' authentication, the ngKSI is provided to the UE in AUTHENTICATION REQUEST , just as it was before S3-181990. CT1 is aware that SA3 has introduced ABBA, which is used as part of security key generation. If SA3 feels that ABBA must be provided along with ngKSI. CT1 can accept that ABBA is also provided at start of EAP primary authentication. In fact, for 5G-AK, ABBA is provided at start of authentication procedure and this is another reason not to diverge.}
| {"ANSWER": "CT1"} |
C4-111842.txt | {"WORKING GROUP": "CT4"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Title * : CT aspects of single radio voice call continuity from UTRAN/GERAN to E-UTRAN/HSPA: Acronym * : rSRVCC-CT: Unique identifier *: 1 3GPP Work Area *: 2 Classification of WI and linked work items: Primary classification *: This work item is a … * Study Item: Go to §3. Feature: Go to §3. Building Block: This work item is … * Stage 1: Go to §3. Stage 2 *: If no identified source of stage 1 information, justify: * Go to §3. Stage 3 *: If no identified source of stage 2 information, justify: * Go to §3. Test spec *: Go to §3. Other *: Go to §3. Work task *: 3 Justification *: TS 22.278 has contained stage-1 requirements for single radio voice call continuity between UTRAN/GERAN and E-UTRAN/HSPA in both directions since Rel-8. The single radio voice call continuity from E-UTRAN/HSPA to UTRAN/GERAN CS access has been specified in Rel-8 in the stage-3 specifications. However, the single radio voice call continuity from UTRAN/GERAN CS access to E-UTRAN/HSPA is not specified yet in the stage-3 specifications.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Title * : CT aspects of single radio voice call continuity from UTRAN/GERAN to E-UTRAN/HSPA: Acronym * : rSRVCC-CT: Unique identifier *: 1 3GPP Work Area *: 2 Classification of WI and linked work items: Primary classification *: This work item is a … * Study Item: Go to §3. Feature: Go to §3. Building Block: This work item is … * Stage 1: Go to §3. Stage 2 *: If no identified source of stage 1 information, justify: * Go to §3. Stage 3 *: If no identified source of stage 2 information, justify: * Go to §3. Test spec *: Go to §3. Other *: Go to §3. Work task *: 3 Justification *: TS 22.278 has contained stage-1 requirements for single radio voice call continuity between UTRAN/GERAN and E-UTRAN/HSPA in both directions since Rel-8. The single radio voice call continuity from E-UTRAN/HSPA to UTRAN/GERAN CS access has been specified in Rel-8 in the stage-3 specifications. However, the single radio voice call continuity from UTRAN/GERAN CS access to E-UTRAN/HSPA is not specified yet in the stage-3 specifications.}
| {"ANSWER": "CT4"} |
C1-051455_Reassignment%20of%20S-CSCF%20during%20the%20registration%20procedure%20in%20the%20Early%20IMS%20system.txt | {"WORKING GROUP": "CT1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{HSS will not able to record which S-CSCF maybe error. And also if the S-CSCF is unavailable, the S-CSCF maybe also unable to send Cx-SAR message to notify HSS deregister related IMPU. HSS maybe still record the IMPU as registered. If the user found that it can not do re-registration, he may choose to initiate a new initial-registration in the FULL IMS environment. That may help network to reselect a new S-CSCF. Then the new selected S-CSCF will notify HSS to do correction. If we forbidden that function, that also means user maybe not get service until the recorded S-CSCF recover. For every registration time HSS can only return the recorded S-CSCF in the Cx-UAA message. That means if user found that he can’t do periodic registration then nothing he can do until S-CSCF recover. He also can not get any IMS service during that period time. That we think is not user or operator would like. From our view we think we should give network flexibility to recover from the error, and not introduce that error to user and make them feel not convenience to use.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{HSS will not able to record which S-CSCF maybe error. And also if the S-CSCF is unavailable, the S-CSCF maybe also unable to send Cx-SAR message to notify HSS deregister related IMPU. HSS maybe still record the IMPU as registered. If the user found that it can not do re-registration, he may choose to initiate a new initial-registration in the FULL IMS environment. That may help network to reselect a new S-CSCF. Then the new selected S-CSCF will notify HSS to do correction. If we forbidden that function, that also means user maybe not get service until the recorded S-CSCF recover. For every registration time HSS can only return the recorded S-CSCF in the Cx-UAA message. That means if user found that he can’t do periodic registration then nothing he can do until S-CSCF recover. He also can not get any IMS service during that period time. That we think is not user or operator would like. From our view we think we should give network flexibility to recover from the error, and not introduce that error to user and make them feel not convenience to use.}
| {"ANSWER": "CT1"} |
R1-167604.txt | {"WORKING GROUP": "RAN1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Companding Techniques: We study the OFDM system with the following companding techniques: Airy function based compander: The companding function is given by : The decompanding/expander function is given by Piecewise-linear: Here we choose a piecewise-linear companding function with 2 points of non-linearity. The expander function will be another piecewise-linear function with 2 points of non-linearity. µ-law compander: Here the companding function is given by: And the expander is given by: ACLR performance: We study the ACLR performance of the companding schemes and compare against the performance of SC-FDM. The setup for simulation study is as follows for the OFDM system. In this study we optimised the compander parameters so that the input power () to PA is maximized while achieving 30 dB ACLR. The piecewise linear model was not optimized due to the large number of parameters to be optimized. The PA model used in the study is a polynomial PA model. The results are tabulated below: Demodulation loss: The simulation setup for the demodulation loss is illustrated in the following figures. We use a SISO system. The transmitter side setup is as follows: The receiver side setup is as: Note that the power amplifier is not included in the simple simulation setup, we offset the SNR axis of the codeblock error rate (CBER) curves by the power back off obtained in [Table 1: Power back-off for 30 dB ACLR], to take into account the effect of ACLR. The simulations also include the cases with using compander at the transmitter, but not using expander at the receiver. Conclusions: Based on the above observations, we have the following observation and proposal: Observation 1: SC-FDM provides 2 dB improvement in link budget for coverage limited users compared to OFDM with companding. Proposal 1: NR should support SC-FDM for uplink in order to meet the same coverage as current LTE deployment. More detailed comparison of OFDM vs. SC-FDM is provided in . References: 3GPP RP-160351 “New SID proposal: study on next generation new radio access technology”, NTT Docomo, CMCC, Ericsson, Huawei, Intel, Nokia Networks, Qualcomm, Samsung. Sweden, March 7-11, 2016 3GPP R1-162199 “Waveform candidates”, Qualcomm. 3GPP R1-162177 “Waveform and multiple access for 5G new radio interface”, Samsung. 3GPP RAN1 “Chairman’s notes RAN1_85”, Nanjing, May, 2016. Abdoli, Javad, Ming Jia, and Jianglei Ma. "Filtered OFDM: A new waveform for future wireless systems." Signal Processing Advances in Wireless Communications (SPAWC), 2015 IEEE 16th International Workshop on. IEEE, 2015. Vakilian, Vida, et al. "Universal-filtered multi-carrier technique for wireless systems beyond LTE." Globecom Workshops (GC Wkshps), 2013 IEEE.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{Companding Techniques: We study the OFDM system with the following companding techniques: Airy function based compander: The companding function is given by : The decompanding/expander function is given by Piecewise-linear: Here we choose a piecewise-linear companding function with 2 points of non-linearity. The expander function will be another piecewise-linear function with 2 points of non-linearity. µ-law compander: Here the companding function is given by: And the expander is given by: ACLR performance: We study the ACLR performance of the companding schemes and compare against the performance of SC-FDM. The setup for simulation study is as follows for the OFDM system. In this study we optimised the compander parameters so that the input power () to PA is maximized while achieving 30 dB ACLR. The piecewise linear model was not optimized due to the large number of parameters to be optimized. The PA model used in the study is a polynomial PA model. The results are tabulated below: Demodulation loss: The simulation setup for the demodulation loss is illustrated in the following figures. We use a SISO system. The transmitter side setup is as follows: The receiver side setup is as: Note that the power amplifier is not included in the simple simulation setup, we offset the SNR axis of the codeblock error rate (CBER) curves by the power back off obtained in [Table 1: Power back-off for 30 dB ACLR], to take into account the effect of ACLR. The simulations also include the cases with using compander at the transmitter, but not using expander at the receiver. Conclusions: Based on the above observations, we have the following observation and proposal: Observation 1: SC-FDM provides 2 dB improvement in link budget for coverage limited users compared to OFDM with companding. Proposal 1: NR should support SC-FDM for uplink in order to meet the same coverage as current LTE deployment. More detailed comparison of OFDM vs. SC-FDM is provided in . References: 3GPP RP-160351 “New SID proposal: study on next generation new radio access technology”, NTT Docomo, CMCC, Ericsson, Huawei, Intel, Nokia Networks, Qualcomm, Samsung. Sweden, March 7-11, 2016 3GPP R1-162199 “Waveform candidates”, Qualcomm. 3GPP R1-162177 “Waveform and multiple access for 5G new radio interface”, Samsung. 3GPP RAN1 “Chairman’s notes RAN1_85”, Nanjing, May, 2016. Abdoli, Javad, Ming Jia, and Jianglei Ma. "Filtered OFDM: A new waveform for future wireless systems." Signal Processing Advances in Wireless Communications (SPAWC), 2015 IEEE 16th International Workshop on. IEEE, 2015. Vakilian, Vida, et al. "Universal-filtered multi-carrier technique for wireless systems beyond LTE." Globecom Workshops (GC Wkshps), 2013 IEEE.}
| {"ANSWER": "RAN1"} |
R1-131047.txt | {"WORKING GROUP": "RAN1"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{2) CDM-F based pattern, which consumes only one OFDM symbol (the 2nd symbol) per slot . Comparing to Rel-10 DMRS pattern, this proposal results in the similar number of OFDM symbols within the range of extrapolation of channel estimation, and meanwhile requires UE to implement two fundamentally different sets of hardware for DMRS-based channel estimation. The proposal seems to aim at only the solution for collision between DMRS and PSS/SSS. This contribution does not include this proposed pattern into performance evaluation. This contribution focuses on the performance evaluations based on the four DMRS patterns in Figure 1. DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 l =0 l =0 DM-RS for port 9/10 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 l =0 l =0 DM-RS for port 9/10 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 DM-RS for port 9/10 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 DM-RS for port 9/10 Pattern-1 Pattern-2 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 l =0 l =0 DM-RS for port 9/10 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 l =0 l =0 DM-RS for port 9/10 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 DM-RS for port 9/10 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 DM-RS for port 9/10 Pattern-3 (pattern 5 in ) Pattern-4 (pattern 6 in ) 3. Evaluation results: The simulation assumptions are listed in Appendix, most of which follow except the performance metric. .}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{2) CDM-F based pattern, which consumes only one OFDM symbol (the 2nd symbol) per slot . Comparing to Rel-10 DMRS pattern, this proposal results in the similar number of OFDM symbols within the range of extrapolation of channel estimation, and meanwhile requires UE to implement two fundamentally different sets of hardware for DMRS-based channel estimation. The proposal seems to aim at only the solution for collision between DMRS and PSS/SSS. This contribution does not include this proposed pattern into performance evaluation. This contribution focuses on the performance evaluations based on the four DMRS patterns in Figure 1. DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 l =0 l =0 DM-RS for port 9/10 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 l =0 l =0 DM-RS for port 9/10 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 DM-RS for port 9/10 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 DM-RS for port 9/10 Pattern-1 Pattern-2 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 l =0 l =0 DM-RS for port 9/10 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 l =0 l =0 DM-RS for port 9/10 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 DM-RS for port 9/10 DM-RS for port 7/8 even-numbered slotsodd-numbered slots 123456123456 DM-RS for port 9/10 Pattern-3 (pattern 5 in ) Pattern-4 (pattern 6 in ) 3. Evaluation results: The simulation assumptions are listed in Appendix, most of which follow except the performance metric. .}
| {"ANSWER": "RAN1"} |
C4-184008.txt | {"WORKING GROUP": "CT4"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{hSEPPhNF-1vSEPPvNFInternal {apiRoot} for hNF: {apiRoot} for hNF-1/2: {hnfRoutePath}hNF-2Internal {apiRoot} for hNF: hSEPPhNF-1vSEPPvNFInternal {apiRoot} for hNF: {apiRoot} for hNF-1/2: {hnfRoutePath}hNF-2Internal {apiRoot} for hNF: Though this is a valid deployment scenario, there are other possible deployment options as shown in Figure#2 as well. hSEPPhNF-1 cluster (reverse proxy)vSEPPvNFhNF-2Cluster (reverse proxy)External {apiRoot} for hNF Cluster 2: {apiRoot} for hNF Cluster 1: proxy address = hSEPP for any URI with pattern *.5gc.mnc123.mcc34.3gppnetwork.orgBackend inst1Backend instnBackend inst1Backend instn hSEPPhNF-1 cluster (reverse proxy)vSEPPvNFhNF-2Cluster (reverse proxy)External {apiRoot} for hNF Cluster 2: {apiRoot} for hNF Cluster 1: proxy address = hSEPP for any URI with pattern *.5gc.mnc123.mcc34.3gppnetwork.orgBackend inst1Backend instnBackend inst1Backend instn In the above model, the NFs in the VPLMN discover the FQDN of the NFs in the HPLMN via NRF. For inter PLMN routing the URI used for accessing the APIs offered by the NF in the HPLMN shall use the format http(s)://hnf2.5gc.mnc123.mcc34.3gppnetwork.org/v1/ E.g: http(s)://hnf2.5gc.mnc123.mcc34.3gppnetwork.org/nsmf-pdusession/v1/pdu-sessions/{pduSessionRef}. The hSEPP and vSEPP purely act as HTTP proxies. The vNF is configured with Proxy address for pattern *.5gc. mnc123.mcc34.3gppnetwork.org = vSEPP The vSEPP is configured with Proxy address for pattern *.5gc. mnc123.mcc34.3gppnetwork.org = hSEPP The hSEPP then routes the request internally within the HPLMN based on the URI of the API. A reverse proxy can be deployed one level below the hSEPP to load balance requests coming to that cluster across multiple instances. Multiple clusters can be deployed for the same NF service to offer geographical redundancy and to provide resiliency against cluster failures. For this deployment model, just exposing one FQDN / URI for the NF in HPLMN to VPLMN is not sufficient. The NF in the VPLMN (e.g V-SMF) shall be provided with multiple cluster addresses (FQDN) of the NF in HPLMN (e.g H-SMF). The NF in VPLMN shall be able to route the request to one of the NF clusters in HPLMN via the SEPP as proxies. If the request fails due to time out, the NF in the VPLMN shall be able to reach alternate clusters in the HPLMN. In one of the offline discussions it was questioned how the certificate negotiation in TLS connection from NFs in VPLMN to the vSEPP will succeed if Host header in HTTP/2 request carries FQDN of NF in HPLMN while the TLS certificate is presented by vSEPP? For this it was suggested that instead of NF in VPLMN trying to contact NF in HPLMN, let the NF be presented with the FQDN of SEPP itself.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{hSEPPhNF-1vSEPPvNFInternal {apiRoot} for hNF: {apiRoot} for hNF-1/2: {hnfRoutePath}hNF-2Internal {apiRoot} for hNF: hSEPPhNF-1vSEPPvNFInternal {apiRoot} for hNF: {apiRoot} for hNF-1/2: {hnfRoutePath}hNF-2Internal {apiRoot} for hNF: Though this is a valid deployment scenario, there are other possible deployment options as shown in Figure#2 as well. hSEPPhNF-1 cluster (reverse proxy)vSEPPvNFhNF-2Cluster (reverse proxy)External {apiRoot} for hNF Cluster 2: {apiRoot} for hNF Cluster 1: proxy address = hSEPP for any URI with pattern *.5gc.mnc123.mcc34.3gppnetwork.orgBackend inst1Backend instnBackend inst1Backend instn hSEPPhNF-1 cluster (reverse proxy)vSEPPvNFhNF-2Cluster (reverse proxy)External {apiRoot} for hNF Cluster 2: {apiRoot} for hNF Cluster 1: proxy address = hSEPP for any URI with pattern *.5gc.mnc123.mcc34.3gppnetwork.orgBackend inst1Backend instnBackend inst1Backend instn In the above model, the NFs in the VPLMN discover the FQDN of the NFs in the HPLMN via NRF. For inter PLMN routing the URI used for accessing the APIs offered by the NF in the HPLMN shall use the format http(s)://hnf2.5gc.mnc123.mcc34.3gppnetwork.org/v1/ E.g: http(s)://hnf2.5gc.mnc123.mcc34.3gppnetwork.org/nsmf-pdusession/v1/pdu-sessions/{pduSessionRef}. The hSEPP and vSEPP purely act as HTTP proxies. The vNF is configured with Proxy address for pattern *.5gc. mnc123.mcc34.3gppnetwork.org = vSEPP The vSEPP is configured with Proxy address for pattern *.5gc. mnc123.mcc34.3gppnetwork.org = hSEPP The hSEPP then routes the request internally within the HPLMN based on the URI of the API. A reverse proxy can be deployed one level below the hSEPP to load balance requests coming to that cluster across multiple instances. Multiple clusters can be deployed for the same NF service to offer geographical redundancy and to provide resiliency against cluster failures. For this deployment model, just exposing one FQDN / URI for the NF in HPLMN to VPLMN is not sufficient. The NF in the VPLMN (e.g V-SMF) shall be provided with multiple cluster addresses (FQDN) of the NF in HPLMN (e.g H-SMF). The NF in VPLMN shall be able to route the request to one of the NF clusters in HPLMN via the SEPP as proxies. If the request fails due to time out, the NF in the VPLMN shall be able to reach alternate clusters in the HPLMN. In one of the offline discussions it was questioned how the certificate negotiation in TLS connection from NFs in VPLMN to the vSEPP will succeed if Host header in HTTP/2 request carries FQDN of NF in HPLMN while the TLS certificate is presented by vSEPP? For this it was suggested that instead of NF in VPLMN trying to contact NF in HPLMN, let the NF be presented with the FQDN of SEPP itself.}
| {"ANSWER": "CT4"} |
S4-232045.txt | {"WORKING GROUP": "SA4"} | As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"WORKING GROUP": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{This is the reason why since August 2022, further work in MeCAR has been carried out to fulfil those requirements from the SR_MSE work item. In particular, one technical solution to carry those components (depth an alpha) was progressed in the MeCAR PD based on a multi-stream approach. That is, texture, depth and alpha would be encoded as part of independent video bitstreams. Other approaches were also documented in the MeCAR PD 6.8.1.5 Carriage of RGBD content over RTP with a single stream, texture and depth stitched together, and carriage with MIV encapsulation over RTP. The key issue in the context of Rel-18 work of MeCAR is the ability to send depth and alpha information using existing compressors – this is fully aligned how deployed systems operate, they use an install base of video decoders on SOC platforms. Existing 3GPP video codec capabilities are well aligned with the referred install base. 3GPP video codecs as available in Rel-18 exclusively support input signals being YUV 4:2:0. This is also aligned with install base of codecs. Hence, it is of relevance that depth and alpha information (referred to as “signal” in the Figure below) can be compressed using YUV 4:2:0-based codecs.}
| As a distinguished expert in telecommunication domain you are skilled in understanding and classifying 3GPP techincal documents. Please help user to classify text into 3GPP working group. Give answer in this format: {"ANSWER": "working group name"}. Do not include any other information.
Classify the following text, extracted from a 3GPP technical document, into one of the 3GPP working groups. You MUST select ONE working group name from this list: {'CT1', 'CT3', 'CT4', 'CT6', 'RAN1', 'RAN2', 'RAN3', 'RAN4', 'RAN5', 'RAN_AH1', 'SA1', 'SA2', 'SA3', 'SA4', 'SA5', 'SA6'}.
###TEXT:
{This is the reason why since August 2022, further work in MeCAR has been carried out to fulfil those requirements from the SR_MSE work item. In particular, one technical solution to carry those components (depth an alpha) was progressed in the MeCAR PD based on a multi-stream approach. That is, texture, depth and alpha would be encoded as part of independent video bitstreams. Other approaches were also documented in the MeCAR PD 6.8.1.5 Carriage of RGBD content over RTP with a single stream, texture and depth stitched together, and carriage with MIV encapsulation over RTP. The key issue in the context of Rel-18 work of MeCAR is the ability to send depth and alpha information using existing compressors – this is fully aligned how deployed systems operate, they use an install base of video decoders on SOC platforms. Existing 3GPP video codec capabilities are well aligned with the referred install base. 3GPP video codecs as available in Rel-18 exclusively support input signals being YUV 4:2:0. This is also aligned with install base of codecs. Hence, it is of relevance that depth and alpha information (referred to as “signal” in the Figure below) can be compressed using YUV 4:2:0-based codecs.}
| {"ANSWER": "SA4"} |
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 14