[{"name":"R4-2008014","title":"Beam correspondence","source":"Keysight Technologies UK Ltd","contact":"Flores Fernandez Martos","contact-id":47301,"tdoctype":"CR","for":"Agreement","abstract":"For beam correspondence capability [bit-0] DUTs, in TR 38.810 section 5.1.2.3.7 \u201cTX Beam Peak direction search and EIRP Spherical Coverage\u201d it is required to use up to 8 SRS resources. However, it is not explicit the \u2018usage\u2019 to be set for those resources. According to 38.331 Section 6.3.2 for SRS-Config IE, \u2018usage\u2019 can have 4 different values: beamManagement, codebook or nonCodebook based transmission or antenna switching. Based on the beam correspondence procedure goal, \u2018usage\u2019 should be set to \u2018beamManagement\u2019.\nIn the beam correspondence procedure defined in the above-mentioned section in TR 38.810, it is also indicated that \u201cSS chooses the best SRS beam which is indicated in the field of SRS Resource Indicator (SRI) in the scheduling grant for PUSCH\u201d. However, in TS 38.212 section 7.3.1.1.2, SRI definition only considers \u2018codeBook\u2019 or \u2018non-codeBook\u2019 values for usage:  \u201cSRS resource set associated with the higher layer parameter usage of value 'codeBook' or 'nonCodeBook'\u201d, i.e. \u2018beamManagement\u2019 resource set cannot be directly used for best beam reporting pruposes.\nIn addition, TS 38.214, section 6.2.1 specifies that \u201cWhen the higher layer parameter usage is set to 'beamManagement', only one SRS resource in each of multiple SRS sets may be transmitted at a given time instant, but the SRS resources in different SRS resource sets with the same time domain behaviour in the same BWP may be transmitted simultaneously.\u201d\nFor that reason, in order to perform Tx beam peak direction search procedure defined in TR 38.810 section 5.2.1.3.7 for beam correspondence capability [bit-0] DUTs, it is required to create 2 SRS resource sets, one with 8 SRS resources with \u2018usage\u2019 set to \u2018beamManagement\u2019 and another resource set with \u2018usage\u2019 set to \u2018codebook\u2019 (default value used in TS 38.508-1).\nThe new SRS resource set shall be semi-persistent as, according to TS 38.321, section 6.1.3.17, and 38.214, section 6.2.1, it is the only one that can be controlled by the network to change dynamically the spatial relationship for a given SRS resource via a MAC CE during the semi-persistent SRS activation. When setting the spatial relation for the target semi-persistent SRS resource, the reference RS to be set can be an \u201cSRS resource configured on serving cell and uplink bandwidth part indicated by Resource Serving Cell ID field and Resource BWP ID field in the activation command if present, same serving cell and bandwidth part as the SRS resource set otherwise.\u201d.\nTo sum up, the SRS Resource Indicator (SRI) field in the scheduling grant\nfor PUSCH will indicate the semi-persistent SRS \u2018codebook\u2019 resource whose spatial relationship information has been set, via the MAC CE activation, to refer to the best \u2018beamManagement\u2019 SRS resource measured and selected by the SS.","secretary_remarks":"","agenda_item_sort_order":67,"ainumber":"4.13","ainame":"Testability Maintenance (38.810) [FS_NR_test_methods]","tdoc_agenda_sort_order":7530,"status":"postponed","reservation_date":"2020-05-15 16:34:30","uploaded":"2020-05-15 16:43:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":"38.810","crspecversion":"16.5.0","workitem":[{"winame":"FS_NR_test_methods"}],"crnumber":12.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG4_Radio\/TSGR4_95_e\/Docs\/R4-2008014.zip","group":"R4","meeting":"R4-ah-38108","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]