Method and apparatus for early SRS triggering in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Apparatuses and methods for early sounding reference signal (SRS) triggering. A method performed by a user equipment includes receiving a system information block (SIB) and initiating a Type-1 random access (RA) procedure to transition from an idle state to a connected state. The SIB includes N groups of SRS resource sets for antenna switching. The N groups of SRS resource sets correspond to N antenna switching capabilities, respectively. The method further includes transmitting, in a message 3 (msg3) of the RA procedure, information indicating an antenna switching capability from the N antenna switching capabilities supported by the UE, receiving, in a message 4 (msg4) of the RA procedure, signaling that triggers transmission of an SRS resource set from the N groups of SRS resource sets, and transmitting SRS resources from the SRS resource set. The SRS resource set corresponds to the antenna switching capability.

Description

METHOD AND APPARATUS FOR EARLY SRS TRIGGERING IN A WIRELESS COMMUNICATION SYSTEM

[0001] The present disclosure relates generally to wireless communication systems and, more specifically, the present disclosure is related to early sounding reference signal (SRS) triggering.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] The present disclosure relates to method and apparatus for early SRS triggering in a wireless communication system.

[0009] According to an aspect of an exemplary embodiment, there is provided a communication method in a wireless communication system.

[0010] Aspects of the present disclosure provide efficient communication methods in a wireless communication system.

[0011] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

[0012] FIG. 1 illustrates an example wireless network according to embodiments of the present disclosure;

[0013] FIG. 2 illustrates an example BS according to embodiments of the present disclosure;

[0014] FIG. 3 illustrates an example UE according to embodiments of the present disclosure;

[0015] FIG. 4A illustrates an example of a wireless transmit and receive paths according to embodiments of the present disclosure;

[0016] FIG. 4B illustrates an example of a wireless transmit and receive paths according to embodiments of the present disclosure;

[0017] FIG. 5A illustrates an example beam operation in a wireless communication system according to embodiments of the present disclosure;

[0018] FIG. 5B illustrates an example multi-beam operation in a wireless communication system according to embodiments of the present disclosure;

[0019] FIG. 6 illustrates an example of a transmitter structure for beamforming according to embodiments of the present disclosure;

[0020] FIG. 7 illustrates an SSB according to embodiments of the present disclosure;

[0021] FIG. 8 illustrates a type-1 random access procedure also known as four-step random access procedure (4-step RACH) according to embodiments of the present disclosure;

[0022] FIG. 9 illustrates a type-2 random access procedure, also known as 2-step random access procedure (2-step RACH) according to embodiments of the present disclosure;

[0023] FIG. 10A illustrates an example of random access response (RAR) media access control (MAC) control elements (CEs) according to embodiments of the present disclosure;

[0024] FIG. 10B illustrates an example of random access response (RAR) media access control (MAC) control elements (CEs) according to embodiments of the present disclosure;

[0025] FIG. 10C illustrates an example of random access response (RAR) media access control (MAC) control elements (CEs) according to embodiments of the present disclosure;

[0026] FIG. 11 illustrates an example procedure for SRS triggering according to embodiments of the present disclosure;

[0027] FIG. 12 illustrates an example of SRS instances in a band according to embodiments of the present disclosure;

[0028] FIG. 13A illustrates an example of fields related to a UE ID and SRS resource ID (and / or SRS resource set ID) in a message triggering SRS transmission according to embodiments of the present disclosure;

[0029] FIG. 13B illustrates an example of fields related to a UE ID and SRS resource ID (and / or SRS resource set ID) in a message triggering SRS transmission according to embodiments of the present disclosure;

[0030] FIG. 13C illustrates an example of fields related to a UE ID and SRS resource ID (and / or SRS resource set ID) in a message triggering SRS transmission according to embodiments of the present disclosure;

[0031] FIG. 13D illustrates an example of fields related to a UE ID and SRS resource ID (and / or SRS resource set ID) in a message triggering SRS transmission according to embodiments of the present disclosure;

[0032] FIG. 13E illustrates an example of fields related to a UE ID and SRS resource ID (and / or SRS resource set ID) in a message triggering SRS transmission according to embodiments of the present disclosure;

[0033] FIG. 14A illustrates an example of fields in a message triggering SRS transmission according to embodiments of the present disclosure;

[0034] FIG. 14B illustrates an example of fields in a message triggering SRS transmission according to embodiments of the present disclosure;

[0035] FIG. 14C illustrates an example of fields in a message triggering SRS transmission according to embodiments of the present disclosure;

[0036] FIG. 15A illustrates an example of an SRS configuration according to embodiments of the present disclosure;

[0037] FIG. 15B illustrates an example of an SRS transmission according to embodiments of the present disclosure;

[0038] FIG. 15C illustrates an example of an SRS transmission according to embodiments of the present disclosure;

[0039] FIG. 16 illustrates an example procedure for early SRS triggering for idle mode according to embodiments of the present disclosure;

[0040] FIG. 17 illustrates an example procedure for early SRS triggering for an inactive mode according to embodiments of the present disclosure;

[0041] FIG. 18 illustrates an example method performed by a UE in a wireless communication system according to embodiments of the present disclosure;

[0042] FIG. 19 is a block diagram of a terminal or user equipment (UE) according to an embodiment of the disclosure;

[0043] FIG. 20 is a block diagram of a base station (BS) according to an embodiment of the disclosure; and

[0044] FIG. 21 is a block diagram of a network entity according to an embodiment of the disclosure.

[0045] The present disclosure relates to a method and apparatus for early SRS triggering.

[0046] In one embodiment, a user equipment (UE) is provided. The UE includes a transceiver configured to receive a system information block (SIB). The SIB includes N groups of SRS resource sets for antenna switching. The N groups of SRS resource sets correspond to N antenna switching capabilities, respectively. The UE further includes a processor operably coupled to the transceiver. The processor is configured to initiate a Type-1 random access (RA) procedure to transition from an idle state to a connected state. The transceiver is further configured to transmit, in a message 3 (msg3) of the RA procedure, information indicating an antenna switching capability from the N antenna switching capabilities supported by the UE, receive, in a message 4 (msg4) of the RA procedure, signaling that triggers transmission of an SRS resource set from the N groups of SRS resource sets that corresponds to the antenna switching capability, and transmit SRS resources from the SRS resource set.

[0047] In another embodiment, a base station (BS) is provided. The BS includes a processor and a transceiver operably coupled to the processor. The transceiver is configured to transmit a SIB that includes N groups of SRS resource sets for antenna switching and that correspond to N antenna switching capabilities, respectively, receive a physical random access channel (PRACH) preamble from a UE for a Type-1 RA procedure to transition from an idle state to a connected state, receive, in msg3 of the RA procedure, information indicating an antenna switching capability from the N antenna switching capabilities supported by the UE, transmit, in msg4 of the RA procedure, signaling that triggers transmission, from the UE, of an SRS resource set from the N groups of SRS resource sets that corresponds to the antenna switching capability, and receive SRS resources from the SRS resource set.

[0048] In yet another embodiment, a method of operating a UE is provided. The method includes receiving a SIB and initiating a Type-1 RA procedure to transition from an idle state to a connected state. The SIB includes N groups of SRS resource sets for antenna switching. The N groups of SRS resource sets correspond to N antenna switching capabilities, respectively. The method further includes transmitting, in a msg3 of the RA procedure, information indicating an antenna switching capability from the N antenna switching capabilities supported by the UE, receiving, in a msg4 of the RA procedure, signaling that triggers transmission of an SRS resource set from the N groups of SRS resource sets, and transmitting SRS resources from the SRS resource set. The SRS resource set corresponds to the antenna switching capability.

[0049] Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

[0050] Before undertaking the DETAILED DESCRIPTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms “transmit,” “receive,” and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, meaning and / or. The phrase “associated with,” as well as derivatives thereof, means to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0051] Moreover, various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms “application” and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase “computer readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer readable medium” includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

[0052] Definitions for other certain words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many if not most instances, such definitions apply to prior as well as future uses of such defined words and phrases.

[0053] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0054] In describing the embodiments, while numerous details are set forth for the purpose of illustration, it is understood that some aspects of the disclosure may be practiced with less than all of these details. Numerous variations and alternatives to the details provided herein are possible and are considered within the scope of the disclosure. In some instances, descriptions related to technical contents well-known in the art may be omitted so as to not obscure an understanding of the disclosure, and such omitted descriptions are understood to be within the scope of the disclosure.

[0055] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. Further, the size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals or different reference numerals.

[0056] The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described herein in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth herein, but may be implemented in various different forms. Other features, aspects, and advantages of the subject matter described herein will become apparent from the disclosure. The following embodiments are merely examples to aid in an understanding of the disclosure and should not be construed to narrow the scope or spirit of the subject matter described herein in any way, but on the contrary, the disclosure covers all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims and equivalents thereof. Throughout the specification, the same or like reference numerals designate the same or like elements. Furthermore, terms which will be described herein are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the operators, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

[0057] Herein, it will be understood that each block of flowchart illustrations, and combinations of blocks in the flowchart illustrations, may be performed based on computer program instructions. These computer program instructions may be loaded collectively onto at least one processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which perform through any one of, or in any combination of, the at least one processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer usable or computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that perform the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer executed process such that the instructions that perform on the computer or other programmable data processing apparatus provide steps for executing the functions specified in the flowchart block(s).

[0058] Further, each block may represent a module, segment, or portion of code, which includes one or more executable instructions for executing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks(or functions) shown in succession may in fact be performed substantially concurrently or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved.

[0059] As used in embodiments of the disclosure, a “~unit / module” may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the term including the word “~unit / module” does not always have a meaning limited to software or hardware. The “~unit / module” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “~unit / module” includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The components and functions provided by the “~unit / module” may be either combined into a smaller number of components and a “~unit / module,” or divided into additional components and a “~unit / module.” Moreover, the components and “~units / modules” may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the “~unit / module” may include one or more processors.

[0060] The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0061] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and includes circuitry like an application processor (AP, e.g. a CPU), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, microprocessors, microcontrollers, digital signal processors, FPGA, ASIC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like. The one processor or the combination of processors executes instructions that can be stored in a memory, such as the operating system, in order to control the overall operation of the device. Also, the one processor or the combination of processors is also capable of executing other processes and programs resident in the memory, such as processes for the disclosure.

[0062] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0063] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure. Additionally, or alternatively, such software may be a computer program [product] comprising instructions which, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0064] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0065] Hereinafter, the determination of priority between A and B in the present disclosure may refer to various actions such as selecting the one having a higher priority based on a predefined priority rule and performing an operation corresponding thereto, or omitting or dropping an operation corresponding to the one having a lower priority.

[0066] Hereinafter, "A or B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0067] In addition, "at least one of A, B, and C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0068] In addition, "at least one of A, B, or C" as described in the present disclosure may be understood to include A, or B, or C, or any combination of A, B, and C.

[0069] Furthermore, "A / B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0070] Furthermore, "A, B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0071] Furthermore, "A and B" as described in the present disclosure may be understood as "A and / or B," which may include A, or B, or both A and B.

[0072] Furthermore, “if condition A and condition B are satisfied,” as described in the present disclosure, may not be limited to a case where both condition A and condition B are satisfied, but may be understood to include a case where either condition A or condition B is individually satisfied, both condition A and condition B are satisfied, or one or more additional conditions are satisfied in combination.

[0073] Furthermore, throughout this disclosure, ordinal terms such as "first," "second," "third," etc., (and similar qualifiers) are used merely to distinguish between different instances, occurrences, configurations, messages, stages, elements or aspects of elements, operations, or information as described herein. Unless the context clearly dictates otherwise, the use of such ordinal terms does not itself require that the elements, operations, or information distinguished by these terms be structurally different, numerically distinct, or substantively dissimilar. For example, a "first signal" and a "second signal" may refer to instances of the same signal transmitted at different times or containing the same core information despite minor variations, or they may refer to signals with different content or characteristics, depending on the specific context. Similarly, a "first value" and a "second value" may represent the same magnitude but measured or applied in different circumstances, or they may represent different magnitudes. The interpretation should be guided by the specific technical context, function, and relationship described in the relevant portion of the specification and claims.

[0074] Furthermore, the terms “first ~”, “second ~”, etc., as described in the present disclosure with respect to various elements (e.g., information, objects, operation, sequences, or the like), should not limit those elements. These terms may only be intended to distinguish one element from another, and may not be intended to indicate a specific order. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element.

[0075] Furthermore, even if “first ~” and “second ~” are described in the present disclosure, it may be understood that element(s) referred to by “first ~” and “second ~” may be the same or different. For example, in case of element(s) being information, first information and second information may both be same information and, in some cases, are separate and different information.

[0076] In addition, the terms “if ~” and “in case that ~” as used in the disclosure or claims may be interpreted to include the meanings of “when (or upon) ~,” “in response to ~,” “based on ~,” or “according to ~,” and may be used interchangeably with these expressions. In addition, expressions other than those exemplified herein may also be used, as long as they have substantially the same meaning and do not impair the technical features of the present disclosure. If a method step (e.g. transmit a signal) is performed according to the disclosure of the application in connection with one of the above terms (such as “in case that ~” or the like), it may be interpreted to include the meanings (disclosure) of a prior determination that a feature has a specific state “~” (e.g. a bit length is above X), and then perform the method step in response to said determination.

[0077] For example, the physical layer signaling may be referred to as Layer 1 (L1) signaling and may include downlink control information (DCI). In addition, the higher layer signaling may include a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (layer 3) signaling. It should be noted, however, that the higher layer signaling is not limited to the aforementioned examples.

[0078] In addition, the term "not perform" as used in the present disclosure or claims may, in context, be understood to mean that the corresponding step is omitted or skipped. Such a term may be replaced with other terms having the same or substantially equivalent meaning.

[0079] In addition, "transmitting a message including A and B" as described in the present disclosure, may be understood as encompassing both (i) transmitting A and B in a single message, and (ii) transmitting A and B separately via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply to messages that include two or more items (e.g., A, B, C), transmitted either together or separately.

[0080] In addition, "transmitting a message including A and transmitting a message including B" may also be interpreted as transmitting a message including A and B in a single message.

[0081] In the embodiments of the present disclosure described herein, terms or components included in the disclosure may be expressed in singular or plural form depending on the specific embodiments presented. However, such singular or plural expressions are selected appropriately for convenience of description, and the present disclosure is not limited to a singular or plural number of components. A component expressed in the plural form may be implemented as a single component, and a component expressed in the singular form may be implemented as multiple components.

[0082] The drawings or flowcharts described herein illustrate example methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in a different order, or be repeated. In other examples, any step may be omitted or replaced with another step.

[0083] The process of the flowchart may be performed by a device. One or more of the steps of the flowchart can be implemented by one or more processors / computer programs executing instructions to perform the noted functions.

[0084] The methods and apparatuses proposed in the embodiments of the present disclosure may be disclosed in connection with drawings disclosing flowcharts to illustrate example methods that may be implemented according to the principles of the present disclosure. Such flowcharts may contain different branches and / or sub-branches. It is understood that the principles of the present disclosure do not only contain the combination of all branches / sub-branches disclosed in the embodiment, but the present disclosure also contains at least one isolated branch / isolated sub-branch, in particular to a single branch / single sub-branch.

[0085] The methods and apparatuses proposed in the embodiments of the present disclosure are not limited to each embodiment individually, but may also be applied in combination of all or some of the embodiments proposed in the disclosure. Therefore, the embodiments of the present disclosure may be modified and applied without significantly departing from the scope of the present disclosure, as would be understood by those skilled in the art.

[0086] In this case, even if certain wordings are described differently across embodiments, they may be used interchangeably or in substitution or in combination if their underlying concepts are equivalent. For example, for the same or equivalent concept, even if one embodiment uses the expression "A" and another embodiment uses the expression "B", such expressions may be understood interchangeably, in substitution, or in combination.

[0087] The terms used in the following description to refer to access nodes, network entities, messages, interfaces between network entities, various types of identification information, and the like, are provided merely for the convenience of explanation by way of example. Therefore, the present disclosure is not limited to the terms describedherein, and other terms having equivalent technical meanings may also be used. Such terms may also be interchangeable with terms defined in any 3rd generation partnership project (3GPP) technical specifications (TS) or similar technical specifications, e.g., from the European telecommunications standards institute (ETSI), where appropriate.

[0088] Hereinafter, a base station (BS) is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a wireless access unit, a BS controller, or a node on a network.

[0089] Furthermore, the base station of the present disclosure may include a split architecture comprising a central unit (CU) and a distributed unit (DU). In this structure, the CU is configured to process the higher layers of the control and user planes, while the DU is configured to process lower-layer radio resource functions. The embodiments of the present disclosure may be equally applicable to 5th generation (5G) base station architectures in which such CU and DU functional splits are implemented.

[0090] A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing communication functions.

[0091] In the disclosure, a downlink (DL) refers to a radio link through which a BS transmits a signal to a terminal, and an uplink (UL) refers to a radio link through which a terminal transmits a signal to a BS.

[0092] Furthermore, hereinafter, 5G mobile communication technologies (e.g., 5G new radio (NR)), 6th generation (6G) mobile communication technologies may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, newly evolved mobile communication systems developed after 5G and 6G may be included. Furthermore, based on determinations by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems (e.g., Wi-Fi systems) through some modifications without significantly departing from the scope of the present disclosure

[0093] In the following description, the terms physical channel and signal may be used interchangeably with data or control signal. For example, the term physical downlink shared channel (PDSCH) refers to a physical channel through which data is transmitted, but the term PDSCH may also be used to refer to the data itself. That is, in the present disclosure, the expression "transmit a physical channel" may be interpreted as being equivalent to the expression "transmit data or a signal via a physical channel."

[0094] Hereinafter, in the context of the present disclosure, higher layer signaling may refer to signaling corresponding to at least one or any combination of the following: master information block (MIB), system information block (SIB) or SIB M (M = 1, 2, ...), RRC, or MAC control element (CE), or a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as Layer 3 (L3) signaling.

[0095] In addition, L1 signaling may refer to signaling corresponding to at least one or any combination of signaling techniques using the at least one or any combination of the following physical layer channels or signaling: physical downlink control channel (PDCCH), DCI, UE-specific DCI, group-common DCI, common DCI, scheduling DCI (e.g., DCI used for scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not used for scheduling downlink or uplink data) physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling message may be referred to as a physical layer signaling.

[0096] Hereinafter, the expression that information is configured by the BS, as used in the present disclosure or claims, may, in context, be understood to mean that the terminal receives the corresponding information from the BS via a physical layer signaling or a higher layer signaling. Such an expression may be replaced with other terms having the same or substantially equivalent meaning.

[0097] Hereinafter, the operational principle of the present disclosure will be described in detail with reference to the accompanying drawings.

[0098] The present application claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application No. 63 / 746,098 filed on January 16, 2025; U.S. Provisional Patent Application No.　63 / 747,762 filed on January 21, 2025; U.S. Provisional Patent Application No. 63 / 749,314 filed on January 24, 2025; and U.S. Provisional Patent Application No. 63 / 858,065 filed on August 5, 2025, which are hereby incorporated by reference in their entirety.

[0099] Wireless communication has been one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services exceeded five billion and continues to grow quickly. The demand of wireless data traffic is rapidly increasing due to the growing popularity among consumers and businesses of smart phones and other mobile data devices, such as tablets, “note pad” computers, net books, eBook readers, and machine type of devices. In order to meet the high growth in mobile data traffic and support new applications and deployments, improvements in radio interface efficiency and coverage are of paramount importance.

[0100] FIGS. 1-21 discussed below, and the various, non-limiting embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0101] To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. The 5G / NR communication system is implemented in higher frequency (mmWave) bands, e.g., 28 GHz or 60 GHz bands, so as to accomplish higher data rates or in lower frequency bands, such as 6 GHz, to enable robust coverage and mobility support. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G / NR communication systems.

[0102] In addition, in 5G / NR communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancelation and the like.

[0103] The discussion of 5G systems and frequency bands associated therewith is for reference as certain embodiments of the present disclosure may be implemented in 5G systems.　 However, the present disclosure is not limited to 5G systems, or the frequency bands associated therewith, and embodiments of the present disclosure may be utilized in connection with any frequency band. For example, aspects of the present disclosure may also be applied to deployment of 5G communication systems, 6G, or even later releases which may use terahertz (THz) bands.

[0104] The following documents and standards descriptions are hereby incorporated by reference into the present disclosure as if fully set forth herein: 3GPP TS 38.211 v18.1.0, “Physical channels and modulation” (herein, “REF 1”); 3GPP TS 38.212 v18.1.0, “NR; Multiplexing and Channel coding” (herein, “REF 2”); 3GPP TS 38.213 v18.1.0, “NR; Physical Layer Procedures for Control” (herein, “REF 3”); 3GPP TS 38.214 v18.1.0, “NR; Physical Layer Procedures for Data” (herein, “REF 4”); 3GPP TS 38.321 v18.0.0, “NR; Medium Access Control (MAC) protocol specification” (herein, “REF 5”); 3GPP TS 38.331 v18.0.0, and “NR; Radio Resource Control (RRC) Protocol Specification” (herein, “REF 6”).

[0105] FIGS. 1-3 below describe various embodiments implemented in wireless communications systems and with the use of orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. The descriptions of FIGS. 1-3 are not meant to imply physical or architectural limitations to how different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

[0106] FIG. 1 illustrates an example wireless network 100 according to embodiments of the present disclosure. The embodiment of the wireless network 100 shown in FIG. 1 is for illustration only. Other embodiments of the wireless network 100 could be used without departing from the scope of the present disclosure.

[0107] As shown in FIG. 1, the wireless network 100 includes a BS 101, a BS 102, and a BS 103. The BS 101 communicates with the BS 102 and the BS 103. The BS 101 also communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

[0108] The BS 102 provides wireless broadband access to the network 130 for a first plurality of user equipments (UEs) within a coverage area 120 of the BS 102. The first plurality of UEs includes a UE 111, which may be located in a small business; a UE 112, which may be located in an enterprise; a UE 113, which may be a WiFi hotspot; a UE 114, which may be located in a first residence; a UE 115, which may be located in a second residence; and a UE 116, which may be a mobile device, such as a cell phone, a wireless laptop, a wireless PDA, or the like. The BS 103 provides wireless broadband access to the network 130 for a second plurality of UEs within a coverage area 125 of the BS 103. The second plurality of UEs includes the UE 115 and the UE 116. In some embodiments, one or more of the BS 101-103 may communicate with each other and with the UEs 111-116 using 5G / NR, long term evolution (LTE), long term evolution-advanced (LTE-A), WiMAX, WiFi, or other wireless communication techniques.

[0109] Depending on the network type, the term “base station” or “BS” can refer to any component (or collection of components) configured to provide wireless access to a network, such as transmit point (TP), transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., 5G / NR 3rdgeneration partnership project (3GPP) NR, long term evolution (LTE), LTE advanced (LTE-A), high speed packet access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For the sake of convenience, the terms “BS” and “TRP” are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Also, depending on the network type, the term “user equipment” or “UE” can refer to any component such as “mobile station,” “subscriber station,” “remote terminal,” “wireless terminal,” “receive point,” or “user device.” For the sake of convenience, the terms “user equipment” and “UE” are used in this patent document to refer to remote wireless equipment that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile telephone or smartphone) or is normally considered a stationary device (such as a desktop computer or vending machine).

[0110] The dotted lines show the approximate extents of the coverage areas 120 and 125, which are shown as approximately circular for the purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with BSs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending upon the configuration of the BSs and variations in the radio environment associated with natural and man-made obstructions.

[0111] As described in more detail below, one or more of the UEs 111-116 include circuitry, programing, or a combination thereof for early SRS triggering. In certain embodiments, one or more of the BS 101-103 include circuitry, programing, or a combination thereof to support early SRS triggering.

[0112] Although FIG. 1 illustrates one example of a wireless network, various changes may be made to FIG. 1. For example, the wireless network 100 could include any number of BSs and any number of UEs in any suitable arrangement. Also, the BS 101 could communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network 130. Similarly, each BS 102-103 could communicate directly with the network 130 and provide UEs with direct wireless broadband access to the network 130. Further, the BSs 101, 102, and / or 103 could provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0113] FIG. 2 illustrates an example BS 102 according to embodiments of the present disclosure. The embodiment of the BS 102 illustrated in FIG. 2 is for illustration only, and the BSs 101 and 103 of FIG. 1 could have the same or similar configuration. However, BSs come in a wide variety of configurations, and FIG. 2 does not limit the scope of the present disclosure to any particular implementation of a BS.

[0114] As shown in FIG. 2, the BS 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0115] The transceivers 210a-210n receive, from the antennas 205a-205n, incoming radio frequency (RF) signals, such as signals transmitted by UEs in the wireless network 100. The transceivers 210a-210n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuitry in the transceivers 210a-210n and / or controller / processor 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The controller / processor 225 may further process the baseband signals.

[0116] Transmit (TX) processing circuitry in the transceivers 210a-210n and / or controller / processor 225 receives analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. The transceivers 210a-210n up-converts the baseband or IF signals to RF signals that are transmitted via the antennas 205a-205n.

[0117] The controller / processor 225 can include one or more processors or other processing devices that control the overall operation of the BS 102. For example, the controller / processor 225 could control the reception of UL channels or signals and the transmission of downlink (DL) channels or signals by the transceivers 210a-210n in accordance with well-known principles. The controller / processor 225 could support additional functions as well, such as more advanced wireless communication functions. For instance, the controller / processor 225 could support beam forming or directional routing operations in which outgoing / incoming signals from / to multiple antennas 205a-205n are weighted differently to effectively steer the outgoing signals in a desired direction. As another example, the controller / processor 225 could support methods for early SRS triggering. Any of a wide variety of other functions could be supported in the BS 102 by the controller / processor 225.

[0118] The controller / processor 225 is also capable of executing programs and other processes resident in the memory 230, such as processes to support early SRS triggering. The controller / processor 225 can move data into or out of the memory 230 as required by an executing process.

[0119] The controller / processor 225 is also coupled to the backhaul or network interface 235. The backhaul or network interface 235 allows the BS 102 to communicate with other devices or systems over a backhaul connection or over a network. The interface 235 could support communications over any suitable wired or wireless connection(s). For example, when the BS 102 is implemented as part of a cellular communication system (such as one supporting 5G / NR, LTE, or LTE-A), the interface 235 could allow the BS 102 to communicate with other BSs over a wired or wireless backhaul connection. When the BS 102 is implemented as an access point, the interface 235 could allow the BS 102 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface 235 includes any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or transceiver.

[0120] The memory 230 is coupled to the controller / processor 225. Part of the memory 230 could include a RAM, and another part of the memory 230 could include a Flash memory or other ROM.

[0121] Although FIG. 2 illustrates one example of BS 102, various changes may be made to FIG. 2. For example, the BS 102 could include any number of each component shown in FIG. 2. Also, various components in FIG. 2 could be combined, further subdivided, or omitted and additional components could be added according to particular needs.

[0122] FIG. 3 illustrates an example UE 116 according to embodiments of the present disclosure. The embodiment of the UE 116 illustrated in FIG. 3 is for illustration only, and the UEs 111-115 of FIG. 1 could have the same or similar configuration. However, UEs come in a wide variety of configurations, and FIG. 3 does not limit the scope of the present disclosure to any particular implementation of a UE.

[0123] As shown in FIG. 3, the UE　116 includes antenna(s) 305, a transceiver(s) 310, and a microphone 320. The UE　116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0124] The transceiver(s) 310 receives from the antenna(s) 305, an incoming RF signal transmitted by a BS of the wireless network 100. The transceiver(s) 310 down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry in the transceiver(s) 310 and / or processor 340, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry sends the processed baseband signal to the speaker 330 (such as for voice data) or is processed by the processor 340 (such as for web browsing data).

[0125] TX processing circuitry in the transceiver(s) 310 and / or processor 340 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceiver(s) 310 up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna(s) 305.

[0126] The processor 340 can include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 in order to control the overall operation of the UE 116. For example, the processor 340 could control the reception of DL channels or signals and the transmission of UL channels or signals by the transceiver(s) 310 in accordance with well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0127] The processor 340 is also capable of executing other processes and programs resident in the memory 360. For example, the processor 340 may execute processes for early SRS triggering as described in embodiments of the present disclosure. The processor 340 can move data into or out of the memory 360 as required by an executing process. In some embodiments, the processor 340 is configured to execute the applications 362 based on the OS 361 or in response to signals received from BSs or an operator. The processor 340 is also coupled to the I / O interface 345, which provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. The I / O interface 345 is the communication path between these accessories and the processor 340.

[0128] The processor 340 is also coupled to the input 350, which includes, for example, a touchscreen, keypad, etc., and the display 355. The operator of the UE 116 can use the input 350 to enter data into the UE 116. The display 355 may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and / or at least limited graphics, such as from web sites.

[0129] The memory 360 is coupled to the processor 340. Part of the memory 360 could include a random-access memory (RAM), and another part of the memory 360 could include a Flash memory or other read-only memory (ROM).

[0130] Although FIG. 3 illustrates one example of UE 116, various changes may be made to FIG. 3. For example, various components in FIG. 3 could be combined, further subdivided, or omitted and additional components could be added according to particular needs. As a particular example, the processor 340 could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, the transceiver(s) 310 may include any number of transceivers and signal processing chains and may be connected to any number of antennas. Also, while FIG. 3 illustrates the UE 116 configured as a mobile telephone or smartphone, UEs could be configured to operate as other types of mobile or stationary devices.

[0131] FIG. 4A and FIG. 4B illustrate an example of wireless transmit and receive paths 400 and 450, respectively, according to embodiments of the present disclosure. For example, a transmit path 400 may be described as being implemented in a BS (such as BS 102), while a receive path 450 may be described as being implemented in a UE (such as UE 116). However, it will be understood that the receive path 450 can be implemented in a BS and that the transmit path 400 can be implemented in a UE. In some embodiments, the transmit path 400 and / or the receive path 450 is configured for supporting early SRS triggering as described in embodiments of the present disclosure.

[0132] As illustrated in FIG. 4A, the transmit path 400 includes a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, a size N Inverse Fast Fourier Transform (IFFT) block 415, a parallel-to-serial (P-to-S) block 420, an add cyclic prefix block 425, and an up-converter (UC) 430. The receive path 450 includes a down-converter (DC) 455, a remove cyclic prefix block 460, a S-to-P block 465, a size N Fast Fourier Transform (FFT) block 470, a parallel-to-serial (P-to-S) block 475, and a channel decoding and demodulation block 480.

[0133] In the transmit path 400, the channel coding and modulation block 405 receives a set of information bits, applies coding (such as a low-density parity check (LDPC) coding), and modulates the input bits (such as with Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of frequency-domain modulation symbols. The serial-to-parallel block 410 converts (such as de-multiplexes) the serial modulated symbols to parallel data in order to generate N parallel symbol streams, where N is the IFFT / FFT size used in the BS and the UE. The size N IFFT block 415 performs an IFFT operation on the N parallel symbol streams to generate time-domain output signals. The parallel-to-serial block 420 converts (such as multiplexes) the parallel time-domain output symbols from the size N IFFT block 415 in order to generate a serial time-domain signal. The add cyclic prefix block 425 inserts a cyclic prefix to the time-domain signal. The up-converter 430 modulates (such as up-converts) the output of the add cyclic prefix block 425 to a RF frequency for transmission via a wireless channel. The signal may also be filtered at a baseband before conversion to the RF frequency.

[0134] As illustrated in FIG. 4B, the down-converter 455 down-converts the received signal to a baseband frequency, and the remove cyclic prefix block 460 removes the cyclic prefix to generate a serial time-domain baseband signal. The serial-to-parallel block 465 converts the time-domain baseband signal to parallel time-domain signals. The size N FFT block 470 performs an FFT algorithm to generate N parallel frequency-domain signals. The (P-to-S) block 475 converts the parallel frequency-domain signals to a sequence of modulated data symbols. The channel decoding and demodulation block 480 demodulates and decodes the modulated symbols to recover the original input data stream.

[0135] Each of the BSs 101-103 may implement a transmit path 400 that is analogous to transmitting in the downlink to UEs 111-116 and may implement a receive path 450 that is analogous to receiving in the uplink from UEs 111-116. Similarly, each of UEs 111-116 may implement a transmit path 400 for transmitting in the uplink to the BSs 101-103 and may implement a receive path 450 for receiving in the downlink from the BSs 101-103.

[0136] Each of the components in FIGS. 4A and 4B can be implemented using only hardware or using a combination of hardware and software / firmware. As a particular example, at least some of the components in FIGS. 4A and 4B may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. For instance, the FFT block 470 and the IFFT block 415 may be implemented as configurable software algorithms, where the value of size N may be modified according to the implementation.

[0137] Furthermore, although described as using FFT and IFFT, this is by way of illustration only and should not be construed to limit the scope of the present disclosure. Other types of transforms, such as Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, can be used. It will be appreciated that the value of the variable N may be any integer number (such as 1, 2, 3, 4, or the like) for DFT and IDFT functions, while the value of the variable N may be any integer number that is a power of two (such as 1, 2, 4, 8, 16, or the like) for FFT and IFFT functions.

[0138] Although FIGS. 4A and 4B illustrate examples of wireless transmit and receive paths 400 and 450, respectively, various changes may be made to FIGS. 4A and 4B. For example, various components in FIGS. 4A and 4B can be combined, further subdivided, or omitted, and additional components can be added according to particular needs. Also, FIGS. 4A and 4B are meant to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architectures can be used to support wireless communications in a wireless network.

[0139] In this disclosure, a beam can be determined by any of:

[0140] -A TCI state, that establishes a quasi-colocation (QCL) relationship or spatial relation between a source reference signal (e.g. SSB and / or CSI-RS) and a target reference signal, and

[0141] -A spatial relation information that establishes an association to a source reference signal, such as SSB or CSI-RS or SRS.

[0142] In either case, the ID of the source reference signal identifies the beam.

[0143] The TCI state and / or the spatial relation reference RS can determine a spatial Rx filter for reception of downlink channels at the UE, or a spatial Tx filter for transmission of uplink channels from the UE. The TCI state and / or the spatial relation reference RS can determine a spatial Tx filter for transmission of downlink channels from the gNB, or a spatial Rx filter for reception of uplink channels at the gNB.

[0144] FIG. 5A illustrates an example beam operation 500 in a wireless communication system according to embodiments of the present disclosure. For example, beam operation 500 can be implemented by BS 102 and / or any of the UEs 111-116 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0145] As illustrated in FIG. 5A, in a wireless system, a beam (501), for a device (504), can be characterized by a beam direction (502) and a beam width (503). For example, a device (504) transmits radio frequency (RF) energy in a beam direction and within a beam width. A device (504) receives RF energy in a beam direction and within a beam width. As illustrated in FIG. 5A, a device at point A (505) can receive from and transmit to device (504) as Point A is within a beam width and direction of a beam from device (504). As illustrated in FIG. 5A, a device at point B (506) cannot receive from and transmit to device (504) as Point B is outside a beam width and direction of a beam from device (504). While FIG. 5A, for illustrative purposes, shows a beam in 2-dimensions (2D), it should be apparent to those skilled in the art, that a beam can be in 3-dimensions (3D), where the beam direction and beam width are defined in space.

[0146] FIG. 5B illustrates an example multi-beam operation 550 in a wireless communication system according to embodiments of the present disclosure. For example, multi-beam operation 550 can be implemented by BS 102 and / or any of the UEs 111-116 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0147] As illustrated in FIG. 5B, in a wireless system, a device can transmit and / or receive on multiple beams. This is known as “multi-beam operation.” While FIG. 5B, for illustrative purposes, shows beams in 2D, it should be apparent to those skilled in the art that beams can be 3D, where the beams can be transmitted to or received from any direction in space.

[0148] FIG. 6 illustrates an example of a transmitter structure 600 for beamforming according to embodiments of the present disclosure. In certain embodiments, one or more of BS 102 or UE 56 includes the transmitter structure 600. For example, one or more of antenna 205 and its associated systems or antenna 305 and its associated systems can be included in transmitter structure 600. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0149] Accordingly, embodiments of the present disclosure recognize that Rel-14 LTE and Rel-15 NR support up to 32 CSI reference signal (CSI-RS) antenna ports which enable an eNB or a BS to be equipped with a large number of antenna elements (such as 64 or 128). A plurality of antenna elements can then be mapped onto one CSI-RS port. For mmWave bands, although a number of antenna elements can be larger for a given form factor, a number of CSI-RS ports, that can correspond to the number of digitally precoded ports, can be limited due to hardware constraints (such as the feasibility to install a large number of analog-to-digital converters (ADCs) / digital-to-analog converters (DACs) at mmWave frequencies) as illustrated in FIG. 6. Then, one CSI-RS port can be mapped onto a large number of antenna elements that can be controlled by a bank of analog phase shifters 601. One CSI-RS port can then correspond to one sub-array which produces a narrow analog beam through analog beamforming 605. This analog beam can be configured to sweep across a wider range of angles 620 by varying the phase shifter bank across symbols or slots / subframes. The number of sub-arrays (equal to the number of RF chains) is the same as the number of CSI-RS portsNCSI-PORT. A digital beamforming unit 610 performs a linear combination acrossNCSI-PORTanalog beams to further increase a precoding gain. While analog beams are wideband (hence not frequency-selective), digital precoding can be varied across frequency sub-bands or resource blocks. Receiver operation can be conceived analogously.

[0150] Since the transmitter structure 600 of FIG. 6 utilizes multiple analog beams for transmission and reception (wherein one or a small number of analog beams are selected out of a large number, for instance, after a training duration that is occasionally or periodically performed), the term “multi-beam operation” is used to refer to the overall system aspect. This includes, for the purpose of illustration, indicating the assigned DL or UL TX beam (also termed “beam indication”), measuring at least one reference signal for calculating and performing beam reporting (also termed “beam measurement” and “beam reporting”, respectively), and receiving a DL or UL transmission via a selection of a corresponding RX beam.

[0151] The system of FIG. 6 is also applicable to higher frequency bands such as >52.6GHz. In this case, the system can employ only analog beams. Due to the O2 absorption loss around 60 GHz frequency (~10 dB additional loss per 100 m distance), a larger number and narrower analog beams (hence a larger number of radiators in the array) are essential to compensate for the additional path loss.

[0152] Rel-17 introduced the unified TCI framework, where a unified or master or main or indicated TCI state is signaled to the UE. The unified or master or main or indicated TCI state can be one of:

[0153] 1. In case of joint TCI state indication, wherein a same beam is used for DL and UL channels, a joint TCI state that can be used at least for UE-dedicated DL channels and UE-dedicated UL channels.

[0154] 2. In case of separate TCI state indication, wherein different beams are used for DL and UL channels, a DL TCI state that can be used at least for UE-dedicated DL channels.

[0155] 3. In case of separate TCI state indication, wherein different beams are used for DL and UL channels, a UL TCI state that can be used at least for UE-dedicated UL channels.

[0156] The unified (master or main or indicated) TCI state is TCI state of UE-dedicated reception on PDSCH / PDCCH or dynamic-grant / configured-grant based PUSCH and all of dedicated PUCCH resources.

[0157] The unified TCI framework applies to intra-cell beam management, wherein, the TCI states have a source RS that is directly or indirectly associated, through a quasi-co-location relation, e.g., spatial relation, with an SSB of a serving cell (e.g., the TCI state is associated with a TRP of a serving cell). The unified TCI state framework also applies to inter-cell beam management, wherein a TCI state can have a source RS that is directly or indirectly associated, through a quasi-co-location relation, e.g., spatial relation, with an SSB of cell that has a physical cell identity (PCI) different from the PCI of the serving cell (e.g., the TCI state is associated with a TRP of a cell having a PCI different from the PCI of the serving cell).

[0158] Quasi-co-location (QCL) relation, can be quasi-location with respect to one or more of the following relations [38.214 - section 5.1.5]:

[0159] - Type A, {Doppler shift, Doppler spread, average delay, delay spread}

[0160] - Type B, {Doppler shift, Doppler spread}

[0161] - Type C, {Doppler shift, average delay}

[0162] - Type D, {Spatial Rx parameter}

[0163] In addition, quasi-co-location relation and source reference signal can also provide a spatial relation for UL channels, e.g., a DL source reference signal provides information on the spatial domain filter to be used for UL transmissions, or the UL source reference signal provides the spatial domain filter to be used for UL transmissions, e.g., same spatial domain filter for UL source reference signal and UL transmissions.

[0164] The unified (master or main or indicated) TCI state applies at least to UE dedicated DL and UL channels. The unified (master or main or indicated) TCI can also apply to other DL and / or UL channels and / or signals e.g. non-UE dedicated channel and sounding reference signal (SRS).

[0165] A UE is indicated a TCI state by MAC CE when the MAC CE activates one TCI state code point. The UE applies the TCI state code point after a beam application time from the corresponding HARQ-ACK feedback. A UE is indicated a TCI state by a DL related DCI format (e.g., DCI Format 1_1, or DCI format 1_2), wherein the DCI format includes a “transmission configuration indication” field that includes a TCI state code point out of the TCI state code points activated by a MAC CE. A DL related DCI format can be used to indicate a TCI state when the UE is activated with more than one TCI state code points. The DL related DCI format can be with a DL assignment for PDSCH reception or without a DL assignment. A TCI state can also be indicated in a purpose designed channel or DCI Format for TCI state indication. A TCI state (TCI state code point) indicated in a DL related DCI format or purpose design channel or DCI Format for TCI state indication is applied after a beam application time from the corresponding HARQ-ACK feedback.

[0166] FIG. 7 illustrates an SSB 700 according to embodiments of the present disclosure. The SSB 700 is for example, and other implementations can be used in the present disclosure. In 5G / NR, a UE performs the cell search procedure to acquire time and frequency synchronization with a cell and to detect the physical layer Cell ID of the cell. To perform cell search, the UE receives the following signals and channel: (1) the primary synchronization signal (PSS), (2) the secondary synchronization signal (SSS) and (3) the physical broadcast channel (PBCH). A PSS / SSS / PBCH block (SS / PBCH block) is referred to as SSB and includes 4 consecutive symbols, and 20 resource blocks (RBs) (240 subcarriers), as illustrated in FIG. 7.

[0167] SSBs are organized in groups or bursts of up to N SSBs, transmitted within half a frame, each SSB within the group or burst has an index where within each group or burst of SSBs, the SSBs are time-division multiplexed and arranged in increasing order of with increasing time. For carrier frequencies less than or equal to 3 GHz, For carrier frequencies in FR1 that are larger than 3GHz, For carrier frequencies in FR2, The SSB indices actually transmitted are provided byssb-PositionsInBurstin system information block one (SIB1) or inServingCellConfigCommonorinSSB-MTC-AdditionalPCIor inLTM-SSB-Config.

[0168] SSBs are transmitted periodically, wherein the allowed periodicities are {5, 10, 20, 40, 80, 160} ms. In addition to cell search, SSBs can also be used for beam management related procedures, such as new beam acquisition, beam measurements, and beam failure detection and recovery. Each SSB with index can be associated with a spatial domain filter (or beam).

[0169] NR introduced a physical random access channel (PRACH) to be used, among other cases, when the UE wants to communicate with the network and doesn't have uplink resources. For example, the physical random access channel can be used during initial access. The PRACH includes a preamble format comprising one or more preamble sequences transmitted in a PRACH Occasion (RO).

[0170] NR supports four different preamble sequence lengths:

[0171] - Sequence length 839 used with sub-carrier spacings 1.25 kHz and 5 kHz with unrestricted or restricted sets.

[0172] - Sequence length 139 used with sub-carrier spacings 15 kHz, 30 kHz, 60 kHz and 120 kHz with unrestricted sets.

[0173] - Sequence length 571 used with sub-carrier spacing 30 kHz with unrestricted sets.

[0174] - Sequence length 1151 used with sub-carrier spacing 15 kHz with unrestricted sets.

[0175] RACH preambles are transmitted in time-frequency resources PRACH Occasions (ROs). Each RO determines the time and frequency resources in which a preamble is transmitted, the resources allocated to an RO in the frequency domain (e.g., number of RBs) and the resource allocated to an RO in the time domain (e.g., number of OFDMA symbols or number of slots), depend on the preamble sequence length, sub-carrier spacing of the preamble, sub-carrier spacing of the PUSCH in the UL BWP, and the preamble format. Multiple PRACH Occasions can be FDMed in one time instance. This is indicated by higher layer parametermsg1-FDM. The time instances of the PRACH Occasions are determined by the higher layer parameterprach-ConfigurationIndex, and Tables 6.3.3.2-2, 6.3.3.2-3, and 6.3.3.2-4 of TS 38.211 v18.1.0.

[0176] SSBs are associated with ROs. The number of SSBs associated with one RO can be indicated by higher layer parameters such asssb-perRACH-OccasionAndCB-PreamblesPerSSBandssb-perRACH-Occasion. The number of SSBs per RO can be When the number of SSBs per RO is less than 1, multiple ROs are associated with the same SSB index. SS / PBCH block indexes provided byssb-PositionsInBurstin SIB1 or inServingCellConfigCommonorinSSB-MTC-AdditionalPCIor inLTM-SSB-Configare mapped to valid PRACH occasions in the following order [38.213 v18.1.0]:

[0177] - First, in increasing order of preamble indexes within a single PRACH occasion.

[0178] - Second, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions.

[0179] - Third, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot.

[0180] - Fourth, in increasing order of indexes for PRACH slots.

[0181] The association period starts from frame 0 for mapping SS / PBCH block indexes to PRACH Occasions.

[0182] A random access procedure can be initiated by a PDCCH order, by the MAC entity, or by RRC.

[0183] There are two types of random access procedures, type-1 random access procedure and type-2 random access procedure.

[0184] FIG. 8 illustrates a type-1 random access procedure 800 also known as four-step random access procedure (4-step RACH) according to embodiments of the present disclosure. The procedure 800 is for example, and other implementations can be used in the present disclosure.

[0185] As illustrated, the procedure 800 includes the following:

[0186] - In step 1, the UE transmits a random access preamble, also known as Msg1, to the gNB. The gNB attempts to receive and detect the preamble.

[0187] - In step 2, the gNB upon receiving the preamble transmits a RAR, also known as Msg2, to the UE including, among other fields, a time adjustment (TA) command and a RAR uplink grant for a subsequent PUSCH transmission.

[0188] - In step 3, the UE after receiving the RAR, transmits a PUSCH transmission scheduled by the grant included in the RAR and time adjusted according to the TA received in the RAR. Msg3 or the PUSCH scheduled by the RAR UL grant can include the RRC reconfiguration complete message or RRC setup request.

[0189] - In step 4, the gNB upon receiving the RRC reconfiguration complete message or RRC setup request, allocates downlink and uplink resources that are transmitted in a downlink PDSCH transmission to the UE.

[0190] After the last step, the UE can proceed with reception and transmission of data traffic.

[0191] Type-1 random access procedure (4-step RACH) can be contention based random access (CBRA) or contention free random access (CFRA). The CFRA procedure ends after the random access response, the following messages are not part of the random access procedure. For CFRA, in step 0, the gNB indicates to the UE the preamble to use.

[0192] FIG. 9 illustrates a type-2 random access procedure, also known as 2-step random access procedure 900 (2-step RACH) according to embodiments of the present disclosure. The procedure 900 is for example, and other implementations can be used in the present disclosure.

[0193] Rel-16, introduced a new random access procedure the type-2 random access procedure, also known as 2-step random access procedure (2-step RACH). The procedure 900 combines the preamble and PUSCH transmission into a single transmission from the UE to the gNB, which is known as MsgA. Similarly, the RAR and the PDSCH transmission (e.g. Msg4) are combined into a single downlink transmission from the gNB to the UE, which is known as MsgB.

[0194] A random access procedure can be triggered for initial access from the RRC_IDLE state. During this procedure, a UE identifies an SS / PBCH block with index and with an RSRP that exceeds a threshold. The RSRP threshold for SSB selection for RACH resource association is indicated by the network. The UE selects a RO and a preamble within the RO associated with SS / PBCH block index The UE transmits a PRACH using the selected RO / preamble. The UE monitors and receives the random access response (RAR), by attempting to detect a DCI format 1_0 with CRC scrambled by a corresponding RA-RNTI during a window controlled by higher layers. If the UE does not detect the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the RAR window, the UE may retransmit PRACH. If the UE detects the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI, the UE receives a RAR UL grant for the scheduling of a PUSCH. The UE transmits the PUSCH according to the RAR UL grant. In response to the PUSCH transmission scheduled by a RAR UL grant, when a UE has not been provided a C-RNTI, the UE attempts to detect a DCI format 1_0 with CRC scrambled by a corresponding TC-RNTI scheduling a PDSCH that includes a UE contention resolution identity. The spatial domain filters (beams) identified during initial access, are used for subsequent transmissions and receptions to / from the UE until a single TCI state is configured or activated or indicated to the UE. For downlink receptions when a UE does not have the TCI state, the spatial domain filter is that associated with the SS / PBCH block index identified during initial access. For uplink transmissions when a UE does not have the TCI state, the spatial domain filter is that used for PUSCH scheduled by the RAR UL grant.

[0195] FIG. 10A illustrates a MAC RAR 1000 according to embodiments of the present disclosure. The MAC RAR 1000 is for example, and other implementations can be used in the present disclosure.

[0196] For example, the MAC RAR 1000 may be used for the MAC RAR (for Type 1 random access procedure) (TS 38.321 Figure 6.2.3-1), where:

[0197] - R: Reserved bit, set to 0

[0198] - TI: If two TAGs are configured for the Serving Cell in which the Random Access procedure is being performed, this field indicates one of the two TAGs to which the Timing Advance Command is applied

[0199] FIG. 10B illustrates a fallback RAR 1050 according to embodiments of the present disclosure. The fallback RAR 1050 is for example, and other implementations can be used in the present disclosure. For example, the fallback RAR 1050 may be used for the fallback RAR (for Type 2 random access procedure), which is used when MSGA PRACH is successfully received but MSGA PUSCH is not decoded correctly (38.321 Figure 6.2.3a-1), where:

[0200] - R: Reserved bit, set to 0

[0201] - TI: If two TAGs are configured for the SpCell, this field indicates one of the two TAGs to which the Timing Advance Command is applied

[0202] FIG. 10C illustrates a success RAR 1070 according to embodiments of the present disclosure. The success RAR 1070 is for example, and other implementations can be used in the present disclosure. For example, the success RAR 1070 may be used for the success RAR (for Type 2 random access procedure), which is used when MSGA PRACH is successfully received and MSGA PUSCH is decoded correctly (38.321 Figure 6.2.3a-2).

[0203] In one example, the UL grant in the MAC RAR or fallbackRAR is given by Table 1 below.

[0204]

[0205] SRS is an uplink reference signal that is used for sounding (i.e., channel quality estimation) the uplink channel between the UE and the gNB. In case of reciprocity between UL and DL, the channel sounding of the uplink channel can also be used for link adaptation and precoding on the downlink channel from the gNB to the UE. SRS is transmitted independent of data transmissions on the uplink. The SRS usage can be one of: beamManagement, codebook, nonCodebook, antennaSwitching, this is in addition to SRS for positioning.

[0206] In NR SRS resources are configured by the network, for example, as part of RRC setup or RRC reconfiguration. SRS resources are configured in SRS resource set. An SRS resource set includes a set of SRS resources, and defines the following parameters: (1) resourceType, which determine the time domain behavior of SRS, SRS can be aperiodic, semi-persistent or periodic. (2) usage, which can be one of: beamManagement, codebook, nonCodebook or antennaSwitching. (3) information related to power control and TCI state.

[0207] The configuration of the SRS resource includes the following: (1) information related to the transmission comb, including comb size, comb offset and cyclic shift. (2) Information related to time domain resource mapping including starting symbol within a slot, number of SRS symbols and repetition factor. (3) information related to frequency domain including freqDomainPosition N_RRC, freqDomainShift n_shift, and frequency hopping parameters c-SRS, b-SRS, and b-hop. (4) Information related to group or sequence hopping, whether one of them or neither is enabled. (5) for periodic and semi-persistent SRS, the periodicity and offset of the SRS resource. (6) Sequence ID. (7) Information related to the TCI state or spatial relation info.

[0208] In 5G NR, a UE can transmit a sounding reference signal (SRS). A SRS resource is configured by higher layer IESRS-Resource.

[0209] The SRS sequence is a low PAPR sequence of length given by:

[0210]

[0211] where with being the transmission comb number is provided in higher layer IEtransmissionComb, is the SRS symbol within a SRS resource of a slot, is the number of SRS symbols in a slot. The cyclic shift for antenna port is given by and with being provided by higher layer in IEtransmissionComb, depends on as illustrated in Table 2.

[0212]

[0213] is the group number is the base sequence number, with if and if The base sequence, is generated as follows:

[0214] 1. For with is given by Tables 5.2.2.2-1 to 5.2.2.2-4 of TS 38.211.

[0215] 2. For with

[0216] 3. For is the largest prime number less than

[0217] The sequence group is given by: Where, is provided by higher layer parametersequenceID, with Higher layer parametergroupOrSeqeunceHoppingdetermines the values of and

[0218] - ifgroupOrSequenceHoppingequals 'neither', neither group, nor sequence hopping shall be used and and

[0219] - ifgroupOrSequenceHoppingequals 'groupHopping', group hopping but not sequence hopping is used and and is the number of symbols in a slots, is the first SRS symbols in the slot, and a length-31 Gold sequence defined as with the first m-sequence is initialized with and for The second m-sequence is initialized with where

[0220] - ifgroupOrSequenceHoppingequals 'sequenceHopping', sequence hopping but not group hopping is used and and

[0221]

[0222] is the number of symbols in a slots, is the first SRS symbols in the slot, and a length-31 Gold sequence as previously defined.

[0223] The SRS sequence, is mapped to resource elements within a slot, where is the sub-carrier frequency, is the symbol number within the slot and is the antenna port, where for SRS there is one antenna port, by

[0224]

[0225]

[0226] Where:

[0227] is a scaling factor, is provided by Table 6.4.14.3-1 of TS 38.211, and

[0228] with the first SRS symbols in the slot, where

[0229] is the transmission comb number as previously described,

[0230]

[0231] is the transmission comb offset included within higher layer IEtransmissionComb, with is a symbol dependent sub-carrier offset given by Table 3, is given by higher layer parameterfreqDomainShiftand it adjust the frequency allocation with respect to a reference point. If the reference point for is sub-carrier 0 in common resource block 0, otherwise the reference point is the lowest subcarrier of the BWP. is a frequency positioning index. is given by:

[0232]

[0233] is given by higher layer parameterfreqDomainPosition, and and are determined by Table 6.4.14.3-1 of TS 38.211 with and the configured value of

[0234]

[0235] In NR paging is used to alert idle and inactive UEs of incoming calls, messages and data. Paging is used to trigger RRC setup (e.g., RRC setup request or RRC connection resumption).

[0236] Paging is transmitted over the paging channel (PCH). The paging message includes a paging record list, which is a list of UEs being paged, each identified by a TMSI or an I-RNTI. The 5G S-Temporary Mobile Subscription Identifier (5G-S-TMSI), a temporary UE identity provided by the 5GC which uniquely identifies the UE within the tracking area. The I-RNTI is used to identify the suspended UE context of a UE in RRC_INACTIVE.

[0237] The following messages describe the contents of a paging message:

[0238]

[0239] A UE may use Discontinuous Reception (DRX) in RRC_IDLE and RRC_INACTIVE state in order to reduce power consumption. The UE monitors one paging occasion (PO) per DRX cycle, Where, a PO is a set of PDCCH monitoring occasions and can include multiple time slots where paging DCI can be sent. A Paging Frame (PF) is one Radio Frame and may contain one or multiple PO(s) or starting point of a PO.

[0240] The PF and PO for paging are determined by the following equations:

[0241] - SFN of the PF is determined by: (SFN + PF_offset) mod T = (T div N)*(UE_ID mod N)

[0242] - The index i_s of the PO is determined by: i_s = floor (UE_ID / N) mod Ns

[0243] Where,

[0244] - T is the DRX cycle of the UE, determined by the shortest of the UE specific DRX value(s) and a default DRX value included in SIB1. (1) For CN-initiated paging, a default cycle is broadcast in system information. (2) For CN-initiated paging, a UE specific cycle can be configured via NAS signaling. (3) For RAN-initiated paging, a UE-specific cycle is configured via RRC signaling. A UE in RRC_IDLE uses the shortest of (1) and (2). A UE in RRC_INACTIVE uses the shortest of (1), (2) and (3).

[0245] - N is a number of total paging frames in T, provided by nAndPagingFrameOffset in SIB1.

[0246] - Ns is a number of paging occasions for a PF, provided by ns in SIB1

[0247] - PF_offset is an offset used for PF determination, provided by nAndPagingFrameOffset in SIB1.

[0248] - UE_ID: 5G-S-TMSI mod 1024

[0249] To minimize or reduce the probability of paging false alarms, which occur when a UE decodes the PCH due to another UE assigned to the same PO being paged, UEs assigned to the same PO are divided in into sub-groups, a DCI carrying a paging early indication (PEI) is transmitted before the corresponding PO to indicate the sub-groups with paging messages in the PO. A UE that is not in the indicated sub-groups indicated by the PEI doesn't decode the corresponding PO. There can be up to 8 sub-groups. The subgroups can be CN controlled sub-groups (determined by the access and mobility function (AMF)), and / or UE-ID based sub-groups.

[0250] DCI format 2_7 is used for notifying the paging early indication and TRS availability indication for one or more UEs. DCI Format 2_7 has a CRC scrambled by PEI_RNTI. DCI Format 2_7 includes: (1) a paging indication field of size where, is the number of paging occasions configured by higher layer parameterpo-NumPerPEI, and is the number of sub-groups of a paging occasion configured by higher layer parametersubgroupsNumPerPO. Each bit in the field indicates one UE subgroup of a paging occasion. (2) TRS availability indication, which can be of size 1 - 6 bits, where the number of bits is equal to one plus the highest value of all theindBitID(s) provided by thetrs-ResourceSetConfigif configured; 0 bits otherwise. Each TRS resource set is configured with an ID i for the association with (i+1)-th indication bit.

[0251] This disclosure provides for early triggering of SRS for UEs in RRC_IDLE or RRC_INACTIVE states when the network has data to send to the UE or the UE has data send to network. Early SRS transmission, can assist in determining the channel conditions and better link adaptation and better precoding for downlink and uplink transmissions. This disclosure provides for physical layer mechanisms as well as higher layer mechanisms for the network to trigger SRS transmission. The triggering of SRS can be during or associated with a random access procedure for RRC setup or RRC reconfiguration.

[0252] When a UE is in RRC_IDLE state or RRC_INACTIVE state, and data arrives at the network for the UE, or data arrives at the UE for the network, the UE through RRC setup procedure or RRC reconfiguration procedure transitions to the RRC_CONNECTED state. After transition to the RRC_CONNECTED state the network can trigger SRS transmission from the UE for channel quality estimation and the UE can start transmitting and receiving data. The SRS triggered can be wideband SRS or sub-band SRS, which would require several SRS transmission instances to provide an estimate of the channel quality of the full bandwidth. This process, i.e., the estimation of the channel quality, can take tens of milli-seconds, and even longer with sub-band SRS. Data transmission / reception can be delayed until the channel quality has been estimated using SRS, hence increasing latency. Alternatively, data transmission / reception can proceed in parallel with the SRS transmission and by the time the channel quality is estimated, the data (depending on the amount of data) has already or mostly been transmitted or received, hence rendering the channel quality estimation less useful while preceding transmissions / receptions from / to the UE are with reduced spectral efficiency due to the absence of a channel estimate at the gNB for the UE.

[0253] To mitigate this issue, it is beneficial to have the channel quality estimated in parallel with the RRC setup procedure, or RRC reconfiguration procedure such that when the UE is ready to transmit or receive data at the completion of the setup or reconfiguration procedures, the channel quality has already been estimated and link adaptation and precoding for uplink or downlink data is based on the estimated channel quality. Hence, there is a benefit for transmitting SRS in parallel with RRC setup procedure, or RRC reconfiguration procedure to reduce latency.

[0254] When the network initiates a communication session, the UE is first paged, and this is then followed by a random access (RA) or also referred to as RACH procedure. When the UE initiates a communication session, a RACH procedure is used. This disclosure also provides for signalling and methods for triggering SRS during a RACH procedure or associated with a RACH procedure. In one example, SRS can be triggered using a message separate from the RACH procedure messages. In another example, SRS can be triggered using a RACH procedure message, e.g., SRS can be triggered within RACH msg2 (RAR), or RACH msg4 (e.g., PDSCH message for contention resolution, e.g., containing contention resolution identity) for type-1 random access procedure, or RACH msgB for type-2 random access procedure. SRS transmission can be separate from the RACH procedure messages or can be transmitted in conjunction with the RACH procedure messages. In one example, the UE capability to support early SRS and / or SRS antenna switching capability can be indicated to the network in the RACH procedure messages (e.g., in Msg1, Msg3, or MsgA (in the PRACH part of MsgA and / or PUSCH part of MsgA). In one example, a UE context is stored in the network (e.g., when the UE is in the RRC_INACTIVE state), the UE context contains the UE capability to support early SRS and / or SRS antenna switching capability, when the network associates the UE triggering the random-access procedure with the UE context, the network can determine the UE capability.

[0255] The present disclosure relates to a 5G / NR and / or 6G communication system.

[0256] This disclosure provides for aspects related to design of early triggering of SRS for UEs in RRC_IDLE and RRC_INACTIVE states. This disclosure includes but is not limited the following asoects:

[0257] - Triggering container or message of early SRS.

[0258] - Timing of triggering of SRS in relation to random access procedure.

[0259] - Transmission of SRS in relation to RACH procedure transmissions.

[0260] - Signaling and determination of SRS resource.

[0261] - Signaling of UE capability to support early SRS and SRS antenna switching capability.

[0262] In the following, both FDD and TDD are provided as a duplex method for DL and UL signaling. In addition, full duplex (XDD) operation is possible, e.g., sub-band full duplex (SBFD) or single frequency full duplex (SFFD).

[0263] Although exemplary descriptions and embodiments to follow assume orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), this disclosure can be extended to other OFDM-based transmission waveforms or multiple access schemes such as filtered OFDM (F-OFDM).

[0264] This disclosure provides several components that can be used in conjunction or in combination with one another, or can operate as standalone schemes.

[0265] In this disclosure, RRC signaling (e.g., configuration by RRC signaling) includes (1) common information provided by common signaling, e.g., this can be system information block (SIB)-based RRC signaling (e.g., SIB1 or other SIB) or (2) RRC dedicated signaling that is sent to a specific UE wherein the information can be common / cell-specific information or dedicated / UE-specific information or (3) UE-group RRC signaling.

[0266] In this disclosure MAC CE signaling can be UE-specific e.g., to one UE or can be UE common (e.g., to a group of UEs or to all UEs in a cell). MAC CE signaling can be DL MAC CE signaling or UL MAC CE signaling.

[0267] In this disclosure L1 control signaling includes: (1) DL control information (e.g., DCI on PDCCH and / or DL control information on PDSCH), DCI can be one stage / part DCI or two-stage / part DCI and / or (2) UL control information (e.g., UCI on PUCCH or PUSCH). L1 control signaling be UE-specific e.g., to one UE and can be UE common (e.g., for a group of UEs or for all UEs in a cell).

[0268] In this disclosure, configuration can refer to configuration by semi-static signaling (e.g., RRC or SIB signaling). In one example, a configuration can be applicable to multiple transmission instances, until a configuration is received and applied.

[0269] In this disclosure, indication can refer to indication by dynamic signaling (e.g., L1 control (e.g., DCI Format) or MAC CE signaling). In one example, an indication can be for an associated occasion(s) (e.g., an occasion or multiple occasions associated with the indication).

[0270] In this disclosure a list with N elements can be denoted as where can take N values, and can correspond to the element associated with index In one example, can take N arbitrary values. In one example, In one example, In one example, is an identity of an element in the list.

[0271] In the present disclosure, the term “activation” describes an operation wherein a UE receives and decodes first information provided by a first signal from the network (or gNB) and based on the first information, the UE determines a starting point in time. The starting point can be a present or a future slot / subframe or symbol and the exact location is either implicitly or explicitly indicated, or is otherwise defined in the system operation or is configured by higher layers. Upon successfully decoding the first information, the UE responds according to an indication provided by the first information. The term “deactivation” describes an operation wherein a UE receives and decodes second information provided by a second signal from the network (or gNB) and based on the second information from the signal, the UE determines a stopping point in time. The stopping point can be a present or a future slot / subframe or symbol and the exact location is either implicitly or explicitly indicated, or is otherwise defined in the system operation or is configured by higher layers. Upon successfully decoding the second information, the UE responds according to an indication provided by the second information. The first signal can be same as the second signal or the first information can be same as the second information, wherein a first part of the information can be associated with an “activation” operation and with first UEs or with first parameters for transmissions / receptions by a UE, and a second part of the information can be associated with a “deactivation” operation and with second UEs or with second parameters for transmissions / receptions by the UE. For example, the second information can be absent, and deactivation can be implicitly derived. For example, when a UE has received an activation information in a previous indication, and is not included among UEs with activation information in a next indication, the UE can determine the latter indication as an implicit deactivation indication.

[0272] In this disclosure, a time unit, for example, can be a symbol or a slot or sub-frame or a frame. In one example, a time-unit can be multiple symbols, or multiple slots or multiple sub-frames or multiple frames. In one example, a time-unit can be a sub-slot (e.g., part of a slot). In one example, a time-unit can be specified in units of time, e.g., microseconds, or milliseconds or seconds, etc.

[0273] In this disclosure, a frequency-unit, for example, can be a sub-carrier or a resource block (RB) or a sub-channel, wherein a sub-channel is a group or RBs, or a bandwidth part (BWP). In one example, a frequency-unit can be multiple sub-carriers, or multiple RBs or multiple sub-channels. In one example, a frequency-unit can be a sub-RB (e.g., part of a RB). A frequency-unit can be specified in units of frequency, e.g., Hz, or kHz or MHz, etc.

[0274] In this disclosure Msg5 refers to the message transmitted by the UE in response to Msg4. For example, Msg5 can be connection setup complete or resume complete.

[0275] Terminology such as TCI, TCI states,SpatialRelationInfo, target RS, reference RS, Msg1, Msg2, Msg3, Msg4, Msg5, MsgA, MsgB and other terms is used for illustrative purposes and is therefore not normative. Other terms that refer to same functions can also be used.

[0276] A “reference RS” (e.g., reference source RS) corresponds to a set of characteristics of a DL beam or an UL TX beam, such as a direction, a precoding / beamforming, a number of ports, and so on. For instance, the UE can receive a source RS index / ID in a TCI state assigned to (or associated with) a DL transmission (and / or UL transmission), the UE applies the known characteristics of the source RS to the assigned DL transmission (and / or UL transmission). The source RS can be received and measured by the UE (in this case, the source RS is a downlink measurement signal such as NZP CSI-RS and / or SSB) with the result of the measurement used for calculating a beam report (e.g., including at least one L1-RSRP / L1-SINR accompanied by at least one CRI or SSBRI). As the NW / gNB receives the beam report, the NW can be better equipped with information to assign a particular DL (and / or UL) TX beam to the UE. Optionally or alternatively, the source RS can be transmitted by the UE (in this case, the source RS is an uplink measurement signal such as SRS). As the NW / gNB receives the source RS, the NW / gNB can measure and calculate the needed information to assign a particular DL (or / and UL) TX beam to the UE, for example in case of channel reciprocity.

[0277] In this disclosure, DCI Format is used for L1 control information in the DL direction from gNB to UE. DCI Format (i.e., L1 control information) can be signal stage / part control information or two stage / part control information. In one example, the DCI format can be carried on a physical downlink control channel (PDCCH). In one example, DCI format can be carried on a physical downlink shared channel (PDSCH). In one example, DCI can be split between PDCCH (e.g., for a first part) and PDSCH (e.g. for a second part).

[0278] In this disclosure, a higher layer message (e.g., SIB-based or RRC-based or MAC CE-based) can be carried by a physical downlink shared channel (PDSCH). In one example, the PDSCH can be scheduled by a DCI format.

[0279] In one example, the configuration of early SRS resources can be configured or updated, by RRC signaling and / or MAC CE signaling and / or L1 control signaling.

[0280] In one example, the configuration of the SRS resource(s) and SRS resource set(s) can include:

[0281] - SRS resource(s) in SRS resource set.

[0282] - SRS resource ID

[0283] - Time and frequency resources (e.g., symbols within a slot for SRS, starting symbol for SRS, number of repetitions, time slot for SRS, periodicity and offset of SRS (e.g., in case of periodic or semi-persistent SRS), starting RB for SRS, number of RBs for SRS, whether frequency hopping is enabled and if enabled frequency hopping pattern, etc.).

[0284] - Number of instances, K, of SRS transmitted when SRS is triggered.

[0285] - Comb size, comb offset and cycle shift.

[0286] - Sequence for reference signal.

[0287] - Power for reference signal.

[0288] - SRS usage, e.g., beamManagement, codebook, nonCodebook, antennaSwitching. In one example, SRS usage is antennaSwitching.

[0289] In this disclosure SRS antenna switching capability refers to the UE's SRS antenna switching capability or the UE's SRS antenna switching configuration or SRS antenna switching resource configuration.

[0290] In one example, SRS resource configuration can include supportedSRS-TxPortSwitch, wherein supportedSRS-TxPortSwitch can be {t1r2 for 1T2R, t1r4 for 1T4R, t2r4 for 2T4R, t1r4-t2r4 for 1T4R / 2T4R, t1r1 for 1T=1R, t2r2 for 2T=2R, t4r4 for 4T=4R, notSupported}. In one example, a UE can select SRS resources based on UE's antenna switching capability or capabilities. In one example, the antenna switching capability can be one of {"Not supported", "1T2R", "1T4R", "2T4R", "1T4R / 2T4R", "1T=1R", "2T=2R", "4T=4R"}. In one example, if a UE antenna switching capability is unknown at the time of triggering or of transmission of the early SRS a default capability can is used. In one example, the default capability is “antenna switching not supported”. In one example, the default capability is 1T2R. In one example, the default capability is 1T=1R. In one example, the default capability is configured by the SIB, e.g. SIB1. In one example, the resource used for early SRS are determined based on the antenna switching capability as described in TS 38.214 clause 6.2.1.2. For example,

[0291] - For 1T2R, two SRS resources transmitted in different symbols, each SRS resource in a given set including a single SRS port, and the SRS port of the second resource in the set is associated with a different UE antenna port than the SRS port of the first resource in the same set.

[0292] - For 2T4R, two SRS resources transmitted in different symbols, each SRS resource in a given set including two SRS ports, and the SRS port pair of the second resource is associated with a different UE antenna port pair than the SRS port pair of the first resource.

[0293] - For 1T4R, four SRS resources transmitted in different symbols of two different slots, and where the SRS port of each SRS resource in the given two sets is associated with a different UE antenna port.

[0294] - For 1T=1R, or 2T=2R, or 4T=4R, one SRS resource, where the number of SRS ports for each resource is equal to 1, 2, or 4 respectively.

[0295] In aforementioned examples, the configuration of early SRS can include multiple SRS (e.g., 2) resource sets for each antenna switching capability, wherein a first resource set is for type periodic or semi-persistent SRS, and a second resource set is for type aperiodic SRS.

[0296] In a variant example, SRS resource configuration can include supportedSRS-TxPortSwitch, wherein supportedSRS-TxPortSwitch can be ('t1r2' for 1T2R, 't1r1-t1r2' for 1T=1R / 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r1-t1r2-t1r4' for 1T=1R / 1T2R / 1T4R, 't1r4-t2r4' for 1T4R / 2T4R, 't1r1-t1r2-t2r2-t2r4' for 1T=1R / 1T2R / 2T=2R / 2T4R, 't1r1-t1r2-t2r2-t1r4-t2r4' for 1T=1R / 1T2R / 2T=2R / 1T4R / 2T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r1-t2r2' for 1T=1R / 2T=2R,'t4r4' for 4T=4R, or 't1r1-t2r2-t4r4' for 1T=1R / 2T=2R / 4T=4R), or the UE may be configured with only one of the following configurations depending on the indicated UE capability or capabilties supportedSRS-TxPortSwitchBeyond4Rx ('t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R) or the UE may be configured with the following configurations depending on the indicated UE capability (or capabilities) [e.g., newUECapabilitySupporting8T8R] ('t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, '[noTDM]' or '[TDM and noTDM]' for 8T8R). In one example, if a UE antenna switching capability is unknown at the time of triggering or of transmission of the early SRS a default capability can be used. In one example, the default capability is “antenna switching not supported”. In one example, the default capability is 1T2R. In one example, the default capability is 1T=1R. In one example, the default capability is configured by the SIB. In one example, the resource used for early SRS are determined based on the antenna switching capability as described in TS 38.214 clause 6.2.1.2.

[0297] FIG. 11 illustrates an example procedure 1100 for SRS triggering according to embodiments of the present disclosure. For example, procedure 1100 of FIG. 18 can be performed by any of the UEs 111-116 of FIG. 1, such as the UE 116 of FIG. 3, and a corresponding method can be performed by any of the BSs 101-103 of FIG. 1, such as BS 102 of FIG. 2. The method 1100 is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0298] As illustrated in FIG. 11, a UE can be configured with SRS resources and / or SRS resource sets by system information (e.g., system information block (SIB), e.g., SIB1 or other SIB) or by RRC configuration (1110). The UE can be indicated or determines to transmit SRS (1120). In one example, the indication / determination can be by a message associated with a random access (e.g., RACH) procedure. In one example, the indication can be by a message for triggering SRS transmission. The UE, based on the indication or determination of SRS transmission, and the configured SRS resources, transmits SRS in one or more SRS transmission instances (1130). In one example, the transmission is one-shot (e.g., one SRS transmission instance, or one SRS transmission instance per subband). In one example, the transmission is N-shot (e.g., N SRS transmission instances, or N SRS transmission instances per subband). In one example, the transmission is periodic. In one example, a UE can optionally determine or is indicated to stop SRS transmission (for example in case of periodic SRS transmission, or in case of N-shot SRS transmission) (1140).

[0299] In the examples, of this disclosure, the gNB or network sends a message to a UE (or to a group of UEs), and the message triggers a transmission of a SRS resource. In one example, the UE transmitting the SRS can be intended receiver of the message, for example this can be a random access response (RAR) to the UE that transmitted the preamble, or a MsgB to the UE that transmitted a MsgA for a type-2 random access procedure, or a contention resolution message or Msg4 to a UE that transmitted Msg3 of the random access procedure, or a message triggering SRS transmission.

[0300] In one example, resources used for SRS transmission, can be one of a set or group of resources configured by the network, e.g., by system information (e.g., SIB1 or other SIB) or RRC configuration. The SRS resource set ID and / or the SRS resource ID can be indicated or determined as described in this disclosure. In one example, when an SRS resource set ID and / or an SRS resource ID is indicated or determined, a subset of SRS resource sets or SRS resources is determined as described in this disclosure and a resource within the subset is indicated as described in this disclosure. In one example, when an SRS resource set ID and / or an SRS resource ID is indicated or determined, a subset of SRS resources is indicated as described in this disclosure and a resource within the subset is determined as described in this disclosure.

[0301] In one example, the configuration of the SRS resource parameters or a subset of the SRS resource parameters can be indicated to the UE in the message triggering the SRS transmission.

[0302] In one example, the time (slot / symbols) of the SRS transmission (e.g., the first instance of the SRS transmission) can be relative to the message or channel from the network triggering the SRS transmission. In one example, the time of the SRS transmission (e.g., the first instance of the SRS transmission) can be relative to a message or channel of the random access procedure. In one example, the time of the SRS transmission can be included in the information triggering the SRS transmission.

[0303] In one example, an SRS transmission triggered as described in this disclosure can be one of:

[0304] - A single instance SRS transmission. In one example, the single transmission instance is for the SRS resource. In one example, the single transmission instance is per sub-band of SRS.

[0305] - K instances of SRS transmissions. Wherein, K can be defined in the system specifications and / or configured or updated by system information and / or RRC signaling and / or MAC CE signaling and / or L1 control signaling. In one example, K can be indicated in the message triggering the SRS transmission. In one example, the K transmission instances are for the SRS resource (e.g., these can over a wideband or multiple sub-bands). In one example, the K transmission instances are per sub-band of SRS (e.g., each sub-band of SRS is transmitted in K transmission instances). Optionally, the UE can be indicated or determines to early terminate SRS transmissions.

[0306] - A periodical or semi-persistent transmission until a reconfiguration message or deactivation message is transmitted to the UE, e.g., to stop the SRS transmission.

[0307] FIG. 12 illustrates an example of SRS instances 1200 in a band according to embodiments of the present disclosure. The SRS instances 1200 are for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0308] In one example, SRS is sub-band SRS. The number of sub-bands within the full band is N. In one example, SRS is transmitted K times when triggered. In one example K = N, In one example, K >= N. In one example, a hopping pattern is used to sweep the SRS transmission in the different sub-bands, as illustrated in FIG. 12. As illustrated, the SRS instances are with 4 sub-bands in the full band (i.e., N=4). SRS is transmitted in 4 different SRS instances at different frequency locations to estimate the quality of the channel in the full band.

[0309] Various embodiments of the present disclosure provide for a standalone DL transmission to trigger SRS. In one example, the SRS is triggered by a DCI format. In one example, the DCI format includes a UE ID. In one example, the UE ID is a UE ID assigned or allocated by the core network, for example S-Temporary Mobile Subscription Identifier (S-TMSI or NG 5G S-TMSI). In one example, the UE ID is part of (or related to) the UE ID assigned by the core network, e.g. indicted UE ID is the n least significant bits of the UE ID, or indicted UE ID is the n most significant bits of the UE ID, or indicated ID is UE ID % N, or indicated ID is ceiling (UE ID / N). Where, % is the modulus function, where x % y is the remainder of dividing x by y. In one example, the UE ID is a UE ID assigned or allocated by the radio access network (RAN). In one example, UE ID is the I-RNTI. In one example, the UE-ID is a short I-RNTI (e.g., 24 bits of the I-RNTI). In one example, the UE ID is a long I-RNTI (e.g., 40 bits I-RNTI). In one example, the UE ID is part of (or related to) the UE ID assigned by the RAN, e.g. indicted UE ID is the n least significant bits of the UE ID, or indicted UE ID is the n most significant bits of the UE ID, or indicated ID is UE ID % N, or indicated ID is ceiling (UE ID / N).

[0310] FIGS. 13A-E illustrate examples of fields related to a UE ID and SRS resource ID (and / or SRS resource set ID) in a message triggering SRS transmission according to embodiments of the present disclosure. The fields in FIGS. 13A-E are for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0311] For example, the messages can be a DCI Format and / or a higher layer message as described in this disclosure. Other fields are not excluded from the messages of FIGS. 13A-E.

[0312] In one example, DCI Format includes 1 UE ID, for example as illustrated in FIG. 13A and FIG. 13C, wherein a UE-ID is as aforementioned. In one example, DCI format includes N UE-IDs, for example as illustrated in FIG. 13B, FIG. 13D and FIG. 13E, wherein a UE-ID is as aforementioned. In one example, N is defined in the system specifications, e.g., N=2 or N=3 or N=4, .... In one example, N is configured to the UE, for example, N can be in the system information e.g. SIB1 or configured by RRC signaling and / or MAC CE signaling and / or L1 control signaling. In one example, the DCI Format is a two-stage or two-part DCI Format, the first stage or part includes the number N of UE IDs, and the N UE IDs are included in the second stage or part.

[0313] In one example, SRS resource (or resource set) is configured by system information. In one example, M SRS resources (or resource sets) are configured by system information, wherein a UE can determine the SRS resources (or resource sets) to use when triggered to transmit SRS (e.g., by indication in the DCI Format). In one example, M SRS resources or resource sets are configured by system information, wherein a UE can determine the SRS resource or resource set to use when triggered to transmit SRS. In one example, SRS resource ID (and / or SRS resource set ID) is included in the configuration of the SRS resource or SRS resource set. In one example, the SRS resource ID is determined based on the order of the SRS resource (or SRS resource sets) in the list of M SRS resources (SRS resource sets). For a first SRS resource (or resource set) in the list has SRS resource (or resource set) ID 0 or SRS resource (or resource set) ID 1. A second SRS resource (or resource set) in the list has SRS resource (or resource set) ID 1 or SRS resource (or resource set) ID 2 respectively.

[0314] In one example, a SRS resource (or resource set) determination can be based on a mapping between UE-ID and the M configured SRS resources (or resource sets). In one example, a SRS resource (or resource set) determination can be based on a mapping between the resources used for the PDCCH reception providing the DCI Format (e.g., time and / or frequency resources, e.g., (e.g., starting) channel control elements (CCEs) or (e.g., starting) resource element groups (REGs) or (e.g., starting) resource blocks (RBs) or (e.g., starting) symbols or slots or subframes or frames etc.) and the M configured SRS resources (or resource sets). In one example, a SRS resource (or resource set) determination can be based on a mapping between UE-ID and resources used for PDCCH reception providing the DCI Format as aforementioned, and the M configured SRS resources (or resource sets).

[0315] In one example, the DCI format includes a SRS resource (or resource set) ID as illustrated in FIG. 13C, FIG. 13D and FIG. 13E. In one example, a SRS resource (or resource set) ID is included for each UE ID for example as illustrated in FIG. 13C and FIG. 13C, wherein UE ID0 triggers SRS ID0, UE ID1 triggers SRS ID1, etc. In a variant example, DCI Format includes one SRS ID as illustrated in FIG. 13E. In one example of FIG. 13E, the SRS ID is for the UE ID0, the SRS ID for another UE ID can be determined based on the SRS ID and a rule, for example, UE ID1 can use SRS ID +1, UE ID2 can use SRS ID + 2, etc. The rule can be a function of the SRS ID and the UE ID.

[0316] In one example, the CRC of the DCI Format is scrambled with a RNTI and the RNTI is associated with triggering SRS.

[0317] In one example, the DCI Format indicates the UE to trigger the SRS transmission. In one example, the DCI Format includes a bitmap, and there is mapping between a bit in the bitmap and the UE. In one example, this mapping is based on rule (e.g., derived based on the UE ID). In one example, this mapping is based on a network configuration. In one example, this mapping is based on a combination of a rule and network configuration. In one example, a UE is configured with a bit in the bitmap that corresponds to the UE.

[0318] In one example, the DCI Format indicated to the UE to trigger the SRS transmissions based on the time and / or frequency resources of the PDCCH providing the DCI Format, e.g., (e.g., starting) channel control elements (CCEs) or (e.g., starting) resource element groups (REGs) or (e.g., starting) resource blocks (RBs) or (e.g., starting) symbols or slots or subframes or frames, etc. In one example, this mapping is based on rule (e.g., derived based on the UE ID). In one example, this mapping is based on a network configuration. In one example, this mapping is based on a combination of a rule and network configuration. In one example, a UE is configured with the time and frequency resources of the DCI Format that correspond to the UE.

[0319] In one example, the DCI Format indicates to the UE to trigger the SRS transmissions based on the RNTI used to scramble the CRC of the DCI format. In one example, multiple RNTIs are configured for a DCI format triggering SRS. In one example, this mapping between RNTI and UE is based on a rule (e.g., derived based on the UE ID). In one example, this mapping between RNTI and UE is based on a network configuration. In one example, this mapping between RNTI and UE is based on a combination of a rule and network configuration. In one example, a UE is configured with a RNTI for SRS triggering that corresponds to the UE.

[0320] In one example, the DCI Format indicates to the UE to trigger the SRS based on one or more of bitmap and time / frequency resource for the PDCCH providing the DCI format and the RNTI for DCI Format as aforementioned.

[0321] In one example, the DCI Format triggering SRS transmission indicates to the UE to transmit the SRS transmission, and the SRS ID is determined. In one example, a determination can be based on a mapping between UE-ID and the M configured SRS resources (or resource sets). In one example, a determination can be based on a mapping between the resources used for the PDCCH providing the DCI Format (e.g., time and / or frequency resources, e.g., (e.g., starting) channel control elements (CCEs) or (e.g., starting) resource element groups (REGs) or (e.g., starting) resource blocks (RBs) or (e.g., starting) symbols or slots or subframes or frames etc.) and the M configured SRS resources (or resource set). In one example, a determination can be based on a mapping between UE-ID and resources used for reception of the PDCCH providing the DCI Format as aforementioned, and the M configured SRS resources (or resource set).

[0322] In one example, the DCI Format indicates to the UE to trigger the SRS transmission, and the SRS ID is indicated by information in the DCI Format for example as illustrated in FIG. 14A, FIG. 14B, and FIG. 14C.

[0323] FIGS. 14A-C illustrate examples of fields in a message triggering SRS transmission according to embodiments of the present disclosure. The messages in FIGS. 14A-C are for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0324] In one example, in FIG. 14A, the UE to transmit SRS is indicated to the UE e.g., by the DCI Format (e.g., based on time and / or frequency resources a PDCCH providing the of DCI Format and / or RNTI of the DCI Format), and SRS ID of the M configured SRS resources is included in the DCI Format.

[0325] In one example, in FIG. 14B, the UE(s) is indicated to transmit SRS by a bit map in a DCI Format and optionally based on time and / or frequency resources of a PDCCH providing the DCI Format and / or the RNTI of the DCI Format SRS ID(s) of the M configured SRS resources (or resource set) are included in the DCI Format. For example, the first SRS ID corresponds to the first non-zero bit of the bitmap, the second SRS ID corresponds to the second non-zero bit of the bitmap, and so on. The number of SRS IDs included in the DCI format can be equal to the number of non-zero bits in the bitmap. In one example, padding is included to make the size of the DCI Format constant and independent of the number of non-zero bits in the bitmap. In one example, the DCI format is a two stage or two-part DCI format, in one example, the bitmap is included in the first stage or part, and the SRS resource (or resource set) IDs corresponding to non-zero bits of the bitmap are included in the second stage or part.

[0326] In one example, in FIG. 14C, the UE(s) is indicated to transmit SRS by a bit map in a DCI Format and optionally based on time and / or frequency resources of a PDCCH providing the DCI Format and / or the RNTI of the DCI Format SRS ID(s) of the M configured SRS resources (or resource set) are included in the DCI Format. A SRS resource (or resource set) ID is included in the bit map, and the resource (or resource set) ID for each UE transmitting SRS can be determined based on the order of corresponding non-zero bits and the SRS ID. For example, the UE corresponding to the first non-zero bit transmits SRS resource (or resource set) with SRS ID, the UE corresponding to the second non-zero bit transmits SRS resource (or resource set) with SRS ID+1, and so on. The rule can be a function of the SRS ID and the non-zero-bit position relative to other non-zero bits or in the bitmap.

[0327] In one example, the slot or subframe or frame used by a UE to transmit SRS resource (or resource set) can be based on configuration of the corresponding SRS (e.g., using system information).

[0328] FIG. 15A illustrates an example of an SRS configuration 1500 according to embodiments of the present disclosure. The SRS configuration 1500 is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0329] In one example, the SRS resource can be transmitted by a UE a minimum time T from the end (or start) of a PDCCH reception providing the DCI Format triggering the SRS transmission or the start of end of the channel (e.g., PUCCH or PUSCH) carrying the acknowledgment to the DCI format. In one example, the slot or subframe or frame used by a UE to transmit SRS resource can be at or after a time T from the end (or start) of the PDCCH reception providing the DCI Format triggering the SRS transmission or at or after a time T from the end (or start) of the channel (e.g., PUCCH or PUSCH) carrying the acknowledgment to the DCI format. In one example, the slot or subframe or frame used by a UE to transmit SRS resource is that first slot or subframe or frame that starts at or after a time T from the end (or start) of a PDCCH reception providing the DCI Format triggering the SRS transmission and optionally based on an offset and a periodicity as illustrated in FIG. 15A. Wherein, the time T can be defined in the system specifications and / or configured or updated by network (e.g., using SIB signaling and / or RRC signaling and / or MAC CE signaling and / or L1 control signaling). In one example, the SRS transmission in FIG. 15A, can be one-shot, e.g., one instance of SRS, with a time T from the trigger of SRS as aforementioned. In one example, the SRS transmission in FIG. 15A, can be N-shots, e.g., N-instances of SRS, with a periodicity P between each two-consecutive instances, and a minimum time T from the trigger, for the first instance, as aforementioned. In one example, the SRS transmission corresponds to the resources of the triggered SRS resource set(s).

[0330] As illustrated in FIG. 15A, the SRS configuration 1500 includes where a SRS period is configured (e.g., 8 slots) and a SRS offset within the SRS period for the SRS slots is configured (e.g., 2 slots). The configuration of the SRS offset, and SRS period can be by SIB configuration or by RRC configuration. The SRS period and the SRS offset determine the potential (possible) SRS slots. A UE receives a SRS trigger, after a delay T from the SRS trigger the SRS can be transmitted. The UE transmits the first instance of SRS in the earliest (first) potential SRS slot (as determined by the period and offset) occurring after a time T (when SRS is periodic or semi-persistent) from the SRS trigger as illustrated in FIG. 15A. In FIG. 15A, SRS is transmitted in two instances.

[0331] FIGS. 15B-C illustrate examples of SRS transmissions 1550 and 1570 according to embodiments of the present disclosure. The SRS transmissions 1550 and 1570 are for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0332] In one example, a UE with SRS antenna switching capability xTyR, transmits N SRS resources per instance as illustrated in FIG. 15B, each SRS resource has M ports. SRS resource has index where In one example, each SRS resource of the N SRS resources corresponds to a different symbol within the same slot, or across multiple slots, or SRS resources of an SRS resource set. In example, In one example, In one example, the M ports of the SRS resource are different from the M ports of SRS resource where, and In one example, a UE with SRS antenna switching capability xTyR, transmits 1 SRS resources per instance across N instances, as illustrated in FIG. 15C, each SRS resource has M ports. SRS resource has index where In example, In one example, In one example, the M ports of the SRS resource are different from the M ports of SRS resource where, and In one example, the SRS repeats for N instances. In one example, the SRS can repeat for more than N instances and the N SRS resources cycle periodically through the SRS instances. In one example, SRS instance is used for SRS resource where and the first SRS instance after the trigger has

[0333] In one example, a UE can indicate a codepoint corresponding to a set of SRS antenna switching capabilities, e.g., {Tx1Ry1, Tx2Ry2, ... TxnRyn}, wherein The UE transmits N SRS resources per instance, where In one example, the number of SRS ports is determined based on xi of the UE SRS antenna switching capability supported by the UE. In one example, the number of SRS ports, is determined based on In one example, the number of SRS ports, is determined based on

[0334] In one example, the SRS is triggered by a message (e.g., higher layer message) in a PDSCH. In one example, this message is a SIB message. In one example, this message is a RRC message. In one example, this message is a MAC CE message. In one example, the PDSCH providing the message is scheduled by a corresponding DCI Format. In one example, the message part of a RACH procedure as described herein.

[0335] In one example, the higher layer message includes a UE ID. In one example, the UE ID is a UE ID assigned or allocated by the core network, for example S-Temporary Mobile Subscription Identifier (S-TMSI or NG 5G S-TMSI). In one example, the UE ID is part of (or related to) the UE ID assigned by the core network, e.g. indicted UE ID is the n least significant bits of the UE ID, or indicted UE ID is the n most significant bits of the UE ID, or indicated ID is UE ID % N, or indicated ID is ceiling (UE ID / N). Where, % is the modulus function, where x % y is the remainder of dividing x by y. In one example, the UE ID is a UE ID assigned or allocated by the radio access network (RAN). In one example, UE ID is the I-RNTI. In one example, the UE-ID is a short I-RNTI (e.g., 24 bits of the I-RNTI). In one example, the UE ID is a long I-RNTI (e.g., 40 bits I-RNTI). In one example, the UE ID is part of (or related to) the UE ID assigned by the RAN, e.g. indicted UE ID is the n least significant bits of the UE ID, or indicted UE ID is the n most significant bits of the UE ID, or indicated ID is UE ID % N, or indicated ID is ceiling (UE ID / N).

[0336] In one example, the higher layer message includes 1 UE ID, for example as illustrated in FIG. 13A and FIG. 13C, wherein a UE-ID is as aforementioned. In a variant example, the signaling of the UE ID is split between the DCI Format and the higher layer message. In one example, the higher layer message includes N UE-IDs, for example as illustrated in FIG. 13B, FIG. 13D and FIG. 13E, wherein a UE-ID is as aforementioned. In one example, N is defined in the system specifications, e.g., N=2 or N=3 or N=4, .... In one example, N is configured to the UE, for example, N can be in the system information e.g. SIB1 or configured by RRC signaling and / or MAC CE signaling and / or L1 control signaling. In a variant example, the signaling of the N UE IDs is split between the DCI Format and the higher layer message. In one example, the DCI format includes one part of the UE ID for each of the N UE IDs, and the higher layer message includes a second part for each of the N UE IDs. In one example, the DCI format includes one part of the UE ID that is common for the N UE IDs, and the higher layer message includes a second part for each of the N UE IDs. In one example, the DCI Format includes the number N of UE IDs, and the N UE IDs are included the message scheduled by the DCI Format.

[0337] In one example, SRS resource (or resource set) is configured by system information. In one example, M SRS resources (or resource sets) are configured by system information, wherein a UE can determine the SRS resources (or resource sets) to use when triggered to transmit SRS (e.g., by indication in the DCI Format). In one example, M SRS resources (or resource sets) are configured by system information, wherein a UE can determine the SRS resources (or resource sets) to use when triggered to transmit SRS. In one example, SRS resource ID is included in the configuration of the SRS resource (or resource set). In one example, the SRS resource (or resource set) ID is determined based on the order of the SRS resource (or resource set) in the list of M SRS resources (or resource sets). For a first SRS resource (or resource set) in the list has SRS resource (or resource set) ID 0 or SRS resource (or resource set) ID 1. A second SRS resource (or resource set) in the list has SRS resource (or resource set) ID 1 or SRS resource (or resource set) ID 2 respectively.

[0338] In one example, a SRS resource (or resource set) determination can be based on a mapping between UE-ID and the M configured SRS resources (or resource sets). In one example, a SRS resource (or resource set) determination can be based on a mapping between the resources used for the higher layer message and / or the PDCCH providing the corresponding DCI Format (e.g., time and / or frequency resources, e.g., (e.g., starting) channel control elements (CCEs) or (e.g., starting) resource element groups (REGs) or (e.g., starting) resource blocks (RBs) or (e.g., starting) symbols or slots or subframes or frames etc.) and the M configured SRS resources (or resource sets). In one example, a SRS resource (or resource set) determination can be based on a mapping between UE-ID and resources used for higher layer message and / or the PDCC providing the corresponding DCI Format as aforementioned, and the M configured SRS resources (or resource set).

[0339] In one example, the higher layer message and / or the corresponding DCI Format includes a SRS resource (or resource set) ID as illustrated in FIG. 13C, FIG. 13D, and FIG. 13E. In one example, a SRS resource (or resource set) ID is included for each UE ID for example as illustrated in FIG. 13C and FIG. 13D, wherein UE ID0 triggers SRS ID0, UE ID1 triggers SRS ID1, etc. In a variant example, higher layer message and / or the corresponding DCI Format includes one SRS ID as illustrated in FIG. 13E. In one example of FIG. 13E, the SRS ID is for the UE ID0, the SRS ID for another UE ID can be determined based on the SRS ID and a rule, for example, UE ID1 can use SRS ID +1, UE ID2 can use SRS ID + 2, etc. The rule can be a function of the SRS ID and the UE ID.

[0340] In one example, the CRC of the higher layer message and / or the corresponding DCI Format is scrambled with a RNTI and the RNTI is associated with triggering SRS.

[0341] In one example, the higher layer message and / or the corresponding DCI Format indicates to the UE to trigger the SRS transmission. In one example, the higher layer message and / or the corresponding DCI Format includes a bitmap, and there is mapping between a bit in the bitmap and the UE. In one example, this mapping is based on rule (e.g., derived based on the UE ID). In one example, this mapping is based on a network configuration. In one example, this mapping is based on a combination of a rule and network configuration. In one example, a UE is configured with a bit in the bitmap that corresponds to the UE.

[0342] In one example, the higher layer message and / or the corresponding DCI Format indicates to the UE to trigger the SRS transmission based on the time and / or frequency resources of the PDCCH providing the DCI Format, e.g., (e.g., starting) channel control elements (CCEs) or (e.g., starting) resource element groups (REGs) or (e.g., starting) resource blocks (RBs) or (e.g., starting) symbols or slots or subframes or frames, etc. In one example, this mapping is based on rule (e.g., derived based on the UE ID). In one example, this mapping is based on a network configuration. In one example, this mapping is based on a combination of a rule and network configuration. In one example, a UE is configured with the time and frequency resources of the higher layer message and / or the corresponding DCI Format that correspond to the UE.

[0343] In one example, the higher layer message and / or the corresponding DCI Format indicates to the UE to trigger the SRS transmission based on the RNTI used to scramble the CRC of the DCI format. In one example, multiple RNTIs are configured for a DCI format triggering SRS and / or a higher layer message. In one example, this mapping between RNTI and UE is based on a rule (e.g., derived based on the UE ID). In one example, this mapping between RNTI and UE is based on a network configuration. In one example, this mapping between RNTI and UE is based on a combination of a rule and network configuration. In one example, a UE is configured with a RNTI for SRS triggering that corresponds to the UE.

[0344] In one example, the higher layer message and / or the PDCCH providing the corresponding DCI Format indicates to the UE to trigger the SRS transmission based on one or more of bitmap and time / frequency resource for higher layer message and / or the PDCCH providing the corresponding DCI format and the RNTI for higher layer message and / or the corresponding DCI Format as aforementioned.

[0345] In one example, the higher layer message and / or the corresponding DCI Format trigger SRS transmission indicates to the UE to transmit the SRS transmission, and the SRS ID is determined from other parameters. In one example, the determination can be based on a mapping between UE-ID and the M configured SRS resources (or resource set). In one example, the determination can be based on a mapping between the resources used for the higher layer message and / or the corresponding PDCCH that provides the DCI Format (e.g., time and / or frequency resources, e.g., (e.g., starting) channel control elements (CCEs) or (e.g., starting) resource element groups (REGs) or (e.g., starting) resource blocks (RBs) or (e.g., starting) symbols or slots or subframes or frames etc.) and the M configured SRS resources (or resource set). In one example, the indication can be based on a mapping between UE-ID and resources used for the PDCCH providing the DCI Format as aforementioned, and the M configured SRS resources (or resource set).

[0346] In one example, the higher layer message and / or the corresponding PDCCH / DCI Format indicates to the UE to trigger the SRS transmission, and the SRS ID is indicated in the higher layer message and / or the corresponding PDCCH / DCI Format for example as illustrated in FIG. 14A, FIG. 14B, and FIG. 14C.

[0347] In one example, in FIG. 14A, the UE is indicated to transmit SRS by the higher layer message and / or the corresponding PDCCH / DCI Format (e.g., based on time and / or frequency resources of higher layer message and / or the corresponding PDCCH / DCI Format and / or RNTI of higher layer message and / or the corresponding DCI Format), and SRS ID of the M configured SRS resources (or resource set) is included in the higher layer message and / or the corresponding DCI Format.

[0348] In one example, in FIG. 14B, the UE(s) to transmit SRS are determined by bit map in the higher layer message and / or the corresponding DCI Format and optionally based on time and / or frequency resources of higher layer message and / or the corresponding PDCCH / DCI Format and / or RNTI of higher layer message and / or the corresponding DCI Format, and SRS ID(s) of the M configured SRS resources (or resource set) are included in the higher layer message and / or the corresponding DCI Format. For example, the first SRS ID corresponds to the first non-zero bit of the bitmap, the second SRS ID corresponds to the second non-zero bit of the bitmap, and so on. The number of SRS IDs included in higher layer message and / or the corresponding DCI Format can equal to the number of non-zero bits in the bitmap. In one example, padding is included to make the size of the DCI Format associated with the higher layer message constant and independent of the number of non-zero bits in the bitmap. In one example, the DCI format is a two stage or two-part DCI format, in one example, the bitmap is included in the first stage or part, and the SRS resource IDs corresponding to non-zero bits of the bitmap are included in the second stage or part and / or the higher layer message.

[0349] In one example, in FIG. 14C, the UE(s) to transmit SRS are determined by bit map in the higher layer message and / or the corresponding DCI Format and optionally based on time and / or frequency resources of higher layer message and / or the corresponding PDCCH / DCI Format and / or RNTI of higher layer message and / or the corresponding DCI Format, and SRS ID(s) of the M configured SRS resources (or resource set) are included in the higher layer message and / or the corresponding DCI Format. A SRS resource (or resource set) ID is included in the bit map, the resource (or resource set) ID for each UE transmitting SRS can be determined based on the order of corresponding non-zero bit and the SRS ID. For example, the UE corresponding to the first non-zero bit transmits SRS resource (or resource set) with SRS ID, the UE corresponding to the second non-zero bit transmits SRS resource (or resource set) with SRS ID+1, and so on. The rule can be a function of the SRS ID and the non-zero-bit position relative to other non-zero bits or in the bitmap.

[0350] In one example, the slot or subframe or frame used by a UE to transmit SRS resource (or resource set) can be based on configuration of the corresponding SRS (e.g., using system information).

[0351] In one example, the SRS resource can be transmitted at or after a time T from the end (or start) of a PDSCH reception providing the higher layer message or from the end (or start) of the PDCCH reception providing the corresponding DCI Format triggering the SRS transmission. In one example, the slot or subframe or frame used to transmit SRS resource can be at least a time T after the end (or start) of the PDSCH reception providing the higher layer message or of the PDCCH reception providing the corresponding DCI Format triggering the SRS transmission. In one example, the slot or subframe or frame used to transmit SRS resource is that first slot or subframe or frame that starts after a time T from the end (or start) of the PDSCH reception providing the higher layer message or from the end (or start) of the PDCCH reception providing the corresponding DCI Format triggering the SRS transmission and optionally based on an offset and a periodicity as illustrated in FIG. 15A. Wherein, the time T can be defined in the system specifications and / or configured or updated by network (e.g., using SIB signaling and / or RRC signaling and / or MAC CE signaling and / or L1 control signaling). In one example, the SRS transmission corresponds to the resources of the triggered SRS resource set(s).

[0352] In one example, the SRS resource can be transmitted at or after a time T after an end (or start) of a PUCCH or PUSCH transmission with acknowledgment information corresponding to the higher layer message triggering the SRS transmission. In one example, the slot or subframe or frame used to transmit SRS resource can be at or after a time T after the end (or start) of a PUCCH or PUSCH transmission with an acknowledgment information corresponding to the higher layer message triggering the SRS transmission. In one example, the slot or subframe or frame used to transmit SRS resource is that first slot or subframe or frame that starts at or after a time T after the end (or start) of a PUCCH or PUSCH transmission with an acknowledgment information corresponding to the higher layer message triggering the SRS transmission and optionally based on an offset and a periodicity as illustrated in FIG. 15A, where the SRS trigger is replaced by acknowledgment to SRS trigger. Wherein, the time T can be defined in the system specifications and / or configured or updated by network (e.g., using SIB signaling and / or RRC signaling and / or MAC CE signaling and / or L1 control signaling). In one example, the SRS transmission corresponds to the resources of the triggered SRS resource set(s).

[0353] In one example, there is no acknowledgment information for the higher layer message, and the transmission of SRS can be considered as acknowledgment information. For example, if the network doesn't receive or detect SRS, the higher layer message can be retransmitted.

[0354] In a variant of the aforementioned examples, the SRS configuration parameters (or a subset of them) for one or more SRS resources can be included in the higher layer message and / or the corresponding DCI format instead of or in addition to the SRS ID for the one or more SRS resources (or SRS resources). Wherein the configuration for the SRS resource (or SRS resource) can be as aforementioned.

[0355] Various embodiments of the present disclosure provide for SRS triggering associated with random access procedure. In the following examples, as described, a UE can indicate the support of early SRS by the preamble and / or RO used for the random access procedure. In one example a set of preambles and / or ROs are configured for the UE to indicate early SRS (UE can randomly select a preamble / RO from the set for early SRS support indication). The set of preambles and / or ROs can be per-SS / PBCH block, or can be common across SS / PBCH blocks.

[0356] In one example, preambles within existing RO configurations can be used to indicate that the UE supports early SRS (e.g., group ), legacy preambles are used to indicate that the UE doesn't support early SRS (e.g., group ). In one example, new ROs can be used to indicate that the UE supports early SRS, e.g., preambles in new ROs can be used to indicate that the UE supports early SRS (e.g., group ), legacy preambles (e.g., in legacy ROs) are used to indicate that the UE doesn't support early SRS (e.g., group ).

[0357] A UE can be configured with a set of preambles in group for indicating support of early SRS. A UE can be configured with a set of preambles in group (e.g., legacy preambles) for indicating non-support of early SRS, or UE doesn't prefer transmitting early SRS. In one example, a UE randomly selects a preamble from group if the UE supports early SRS (or if the UE supports and desires to transmit early SRS). A network / gNB receiving a preamble in group can indicate to or configure the UE, in a subsequent message or messages to transmit early SRS as described in this disclosure. In one example, a UE randomly selects a preamble from group if the UE doesn't support early SRS (or if the doesn't desire to transmit early SRS). A network / gNB receiving a preamble in group is expected not to indicate or configure the UE to transmit early SRS.

[0358] In one example, the preambles and / or ROs in group are configured for each SS / PBCH block.

[0359] In one example, the preambles and / or ROs in group are configured commonly for all SS / PBCH blocks.

[0360] In a variant of the above examples, a set of preambles and / or ROs can be configured for group e.g., separate from the legacy preambles and / or ROs. In one example, the preambles and / or ROs in group are configured for each SS / PBCH block. In one example, the preambles and / or ROs in group are configured commonly for all SS / PBCH blocks.

[0361] In the following examples, as described, a UE can indicate its SRS antenna switching xTyR capability for early SRS based on the preamble and / or RO used for the random access procedure. In one example a first set of preambles and / or ROs are configured for the UE to indicate support of a first xTyR capability, a second set of preambles and / or ROs are configured for the UE to indicate support of a second xTyR capability, ..., an Nth set of preambles and / or ROs are configured for the UE to indicate support of an Nth xTyR capability. Wherein, the UE can randomly select a preamble from a set, and the set corresponds to the UE's SRS antenna switching capability (or early SRS antenna switching capability). In one example, the selection of a preamble from any of the N sets indicates to the network that the UE supports early SRS (or supports and desires to transmit early SRS). In one example, the network upon receiving a preamble associated with an ith group, determines that the UE can transmit an SRS resource(s) corresponding to the ith group corresponding to a SRS antenna switching capability xTyR associated with the ith group.

[0362] In one example, the SRS antenna switching capability xTyR is indicated by a combination of signaling in preamble / RO (e.g., based on the preamble / TO group), and Msg3 or PUSCH MsgA.

[0363] In one example, an RO (e.g., per SS / PBCH block or across all SS / PBCH blocks) is configured for indicating the SRS antenna switching xTyR capability. In one example, the RO has M, e.g., 64 preambles, and the M preambles are split among N groups of preambles. In one example, an RO has M preambles per SSB, and the M preambles are split among N groups of preambles. In one example, the RO has M preambles per SSB per preamble group (group A and group B wherein group A and group B indicates different Msg3 / MsgA size), and the M preambles are split among N groups of preambles.

[0364] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of { 't1r2' for 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, or 't4r4' for 4T=4R}.

[0365] In one example, and the xTyR capability indicated by a preamble can be one of {'t1r2' for 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r4-t2r4' for 1T4R / 2T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, or 't4r4' for 4T=4R}.

[0366] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of { 't1r2' for 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, 't4r4' for 4T=4R, or not supported}.

[0367] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {'t1r2' for 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r4-t2r4' for 1T4R / 2T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, 't4r4' for 4T=4R, or not supported}.

[0368] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of { 't1r2' for 1T2R, 't1r1' for 1T=1R, or 't2r2' for 2T=2R}.

[0369] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {'t1r1' for 1T=1R, 't1r2' for 1T2R, or 't1r4' for 1T4R}.

[0370] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {1T4R, 1T2R / 2T4R, 1T=1R / 2T=2R / 4T=4R}. In one example, the number of SRS resources transmitted is one of {4, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T4R, 1T2R and 1T=1R, 2 ports for 2T4R and 2T=2R, and 4 ports for 4T=4R. In one example, the number of ports is indicated in Msg3 or MsgA PUSCH.

[0371] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R}.

[0372] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, or not supported}.

[0373] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {1T8R, 1T6R, 1T4R / 2T8R, 2T6R, 1T2R / 2T4R / 4T8R, 1T=1R / 2T=2R / 4T=4R}. In one example, the number of SRS resources transmitted is one of {8, 6, 4, 3, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T8R, 1T6R, 1T4R, 1T2R and 1T=1R, 2 ports for 2T8R, 2T6R, 2T4R and 2T=2R, and 4 ports for 4T8R and 4T=4R. In one example, the number of ports is indicated in Msg3 or MsgA PUSCH.

[0374] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 't8r8' for 8T8R}.

[0375] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 't8r8' for 8T8R, or not supported}.

[0376] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 'noTdm' or 'tdmAndNoTdm' for 8T8R}.

[0377] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 'noTdm' or 'tdmAndNoTdm' for 8T8R, or not supported}.

[0378] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {1T8R, 1T6R, 1T4R / 2T8R, 2T6R, 1T2R / 2T4R / 4T8R, 1T=1R / 2T=2R / 4T=4R / 8T8R}. In one example, the number of SRS resources transmitted is one of {8, 6, 4, 3, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T8R, 1T6R, 1T4R, 1T2R and 1T=1R, 2 ports for 2T8R, 2T6R, 2T4R and 2T=2R, 4 ports for 4T8R and 4T=4R and 8 ports for 8T8R. In one example, the number of ports is indicated in Msg3 or MsgA PUSCH.

[0379] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't3r3' for 3T=3R, 't3r6' for 3T / 6R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 't8r8' for 8T8R}.

[0380] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't3r3' for 3T=3R, 't3r6' for 3T / 6R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 't8r8' for 8T8R, or not supported}.

[0381] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't3r3' for 3T=3R, 't3r6' for 3T / 6R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 'noTdm' or 'tdmAndNoTdm' for 8T8R}.

[0382] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't3r3' for 3T=3R, 't3r6' for 3T / 6R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 'noTdm' or 'tdmAndNoTdm' for 8T8R, or not supported}.

[0383] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {1T8R, 1T6R, 1T4R / 2T8R, 2T6R, 1T2R / 2T4R / 3T6R / 4T8R, 1T=1R / 2T=2R / 3T=3R / 4T=4R / 8T8R}. In one example, the number of SRS resources transmitted is one of {8, 6, 4, 3, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T8R, 1T6R, 1T4R, 1T2R and 1T=1R, 2 ports for 2T8R, 2T6R, 2T4R and 2T=2R, 3ports for 3T6R and 3T=3R, 4 ports for 4T8R and 4T=4R and 8 ports for 8T8R. In one example, the number of ports is indicated in Msg3 or MsgA PUSCH.

[0384] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {1T8R, 1T6R, 1T4R, 1T2R, or 1T=1R}.

[0385] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {1T8R, 1T6R, 1T4R, 1T2R, 1T=1R or not supported}.

[0386] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {1T8R, 1T4R, 1T2R, or 1T=1R}.

[0387] In one example, and the xTyR capability indicated by a preamble (e.g., according to the set of the preamble) can be one of {1T8R, 1T4R, 1T2R, 1T=1R or not supported}.

[0388] In a variant of the aforementioned examples, there are N codepoints indicated by the preamble and / or RO, wherein each code-point can be a subset of {1T=1R, 1T2R, 1T4R, 1T6R, 1T8R, 2T=2R, 2T / 4R, 2T / 6R, 2T / 8R, 3T=3R, 3T / 6R, 4T=4R, 4T8R, 8T8R}. In a further example, an element of the subset is indicated by Msg3 or MsgA PUSCH.

[0389] In one example, configuration of the number of preamble groups for indication of SRS antenna switching capability, the preambles and / or ROs associated with each group (per SS / PBCH block or across SS / PBCH blocks), and xTyR capability (or set of capabilities) associated with each group can be configured and / or updated by SIB and / or RRC and / or MAC CE and / or L1 control (e.g., DCI Format) signaling.

[0390] In one example, for indication of N SRS antenna switching capability codepoints (or N SRS antenna switching capabilities), a set of preambles and / or ROs is configured for each codepoint of the N codepoints (or for each SRS antenna switching capability of the N SRS antenna switching capabilities). Each set of preambles and / or ROs can be per-SS / PBCH block, or can be common across SS / PBCH blocks.

[0391] In one example, M preambles (e.g., each preamble can be associated with index ) in one or more ROs (or M preambles per SSB in a RO or M preambles per SSB per preamble group (group A and group B wherein group A and group B indicates different Msg3 / MsgA size) in a RO) are allocated for early SRS indication, the M preambles are divided into N groups (e.g., each group can have index of preambles, for indication of N SRS antenna switching capability codepoints (or N SRS antenna switching capabilities). In one example, M is a multiple of N, and each group wherein has preambles. In one example, the preambles in group can have index where

[0392] In one example, the number of preambles per group is In one example, the preambles in group can have index where

[0393] In one example, the number of preambles per group is for group if and for group if where % is the modulo operator, that is the remainder of M divided by N. In one example, the preambles in group for can have index where In one example, the preambles in group for can have index where

[0394] In the following examples, as described, a UE can indicate the support of early SRS and / or the UE's SRS antenna switching xTyR capability for early SRS in Msg3 or MsgA PUSCH. In one example, the UE is configured with “groupBconfigured” random access preambles for group B. In one example, the Msg3 or MsgA PUSCH payload size when the UE transmits random access preamble for group B is larger than the Msg3 or MsgA PUSCH payload size when the UE transmits random access preamble for group A. In one example, the network allocates time and frequency resources and MCS for a payload size of RACH Msg3 or MsgA PUSCH that is large enough for the UE to report UE's early SRS capability and / or the UE's SRS antenna switching xTyR capability for early SRS.

[0395] In one example, UE reports in RACH Msg3 or MsgA PUSCH support or not support of early SRS. For example, a one-bit flag can indicate early SRS is not supported (e.g., value 0), or early SRS is supported (e.g., value 1). In a variant example, a one-bit flag can indicate early SRS is not supported (e.g., value 1), or early SRS is supported (e.g., value 0).

[0396] In one example, UE reports in RACH Msg3 or MsgA PUSCH UE's SRS antenna switching xTyR capability or UE does not support early SRS.

[0397] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of { 't1r2' for 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, 't4r4' for 4T=4R, or not early SRS not supported}

[0398] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {'t1r2' for 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r4-t2r4' for 1T4R / 2T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, 't4r4' for 4T=4R, or early SRS not supported}.

[0399] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of { 't1r2' for 1T2R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, or early SRS not supported}

[0400] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {'t1r1' for 1T=1R, 't1r2' for 1T2R, 't1r4' for 1T4R, or early SRS not supported}

[0401] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T4R, 1T2R / 2T4R, 1T=1R / 2T=2R / 4T=4R, or early SRS not supported}. In one example, the number of SRS resources transmitted is one of {4, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T4R, 1T2R and 1T=1R, 2 ports for 2T4R and 2T=2R, and 4 ports for 4T=4R.

[0402] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, or early SRS not supported}

[0403] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T8R, 1T6R, 1T4R / 2T8R, 2T6R, 1T2R / 2T4R / 4T8R, 1T=1R / 2T=2R / 4T=4R, or early SRS not supported}. In one example, the number of SRS resources transmitted is one of {8, 6, 4, 3, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T8R, 1T6R, 1T4R, 1T2R and 1T=1R, 2 ports for 2T8R, 2T6R, 2T4R and 2T=2R, and 4 ports for 4T8R and 4T=4R.

[0404] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of 't1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 't8r8' for 8T8R, or early SRS not supported}.

[0405] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 'noTdm' or 'tdmAndNoTdm' for 8T8R, or early SRS not supported}

[0406] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T8R, 1T6R, 1T4R / 2T8R, 2T6R, 1T2R / 2T4R / 4T8R, 1T=1R / 2T=2R / 4T=4R / 8T8R, or early SRS not supported}. In one example, the number of SRS resources transmitted is one of {8, 6, 4, 3, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T8R, 1T6R, 1T4R, 1T2R and 1T=1R, 2 ports for 2T8R, 2T6R, 2T4R and 2T=2R, 4 ports for 4T8R and 4T=4R and 8 ports for 8T8R.

[0407] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't3r3' for 3T=3R, 't3r6' for 3T / 6R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 't8r8' for 8T8R, or early SRS not supported}.

[0408] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't3r3' for 3T=3R, 't3r6' for 3T / 6R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 'noTdm' or 'tdmAndNoTdm' for 8T8R, or early SRS not supported}.

[0409] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T8R, 1T6R, 1T4R / 2T8R, 2T6R, 1T2R / 2T4R / 3T6R / 4T8R, 1T=1R / 2T=2R / 3T=3R / 4T=4R / 8T8R, or early SRS not supported}. In one example, the number of SRS resources transmitted is one of {8, 6, 4, 3, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T8R, 1T6R, 1T4R, 1T2R and 1T=1R, 2 ports for 2T8R, 2T6R, 2T4R and 2T=2R, 3ports for 3T6R and 3T=3R, 4 ports for 4T8R and 4T=4R and 8 ports for 8T8R.

[0410] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T8R, 1T6R, 1T4R, 1T2R, 1T=1R or early SRS not supported}.

[0411] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T8R, 1T4R, 1T2R, 1T=1R or early SRS not supported}.

[0412] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T=1R, 1T2R, 1T4R, 1T6R, 1T8R, 2T=2R, 2T / 4R, 2T / 6R, 2T / 8R, 3T=3R, 3T / 6R, 4T=4R, 4T8R, 8T8R, or early SRS not supported}.

[0413] - In a variant of the aforementioned examples, “early SRS not supported” is not included in corresponding sets.

[0414] In the following examples, as described, a UE can indicate the support of early SRS by the preamble and / or RO used for the random access procedure, and the UE can indicate the SRS antenna switching xTyR capability for early SRS in Msg3 or MsgA PUSCH. In one example a set of preambles and / or ROs are configured for the UE to indicate early SRS (UE can randomly select a preamble / RO from the set for early SRS support indication), as aforementioned. The set of preambles and / or ROs can be per-SS / PBCH block, or can be common across SS / PBCH blocks.

[0415] In one example, the Msg3 or MsgA PUSCH payload size when the UE transmits random access preamble indicating support of early SRS, is larger than the Msg3 or MsgA PUSCH payload size when the UE transmits random access preamble that doesn't indicate support of early SRS (e.g., legacy preamble). In one example, the network allocates time and frequency resources and MCS for a payload size of RACH Msg3 or MsgA PUSCH that is large enough for the UE to report UE's early SRS capability and / or the UE's SRS antenna switching xTyR capability for early SRS.

[0416] In one example, UE reports in RACH Msg3 or MsgA PUSCH UE's SRS antenna switching xTyR capability. In one example, UE reports that it does not support early SRS.

[0417] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of { 't1r2' for 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, or 't4r4' for 4T=4R}

[0418] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {'t1r2' for 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r4-t2r4' for 1T4R / 2T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, or 't4r4' for 4T=4R}.

[0419] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of { 't1r2' for 1T2R, 't1r1' for 1T=1R, or 't2r2' for 2T=2R}

[0420] In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {'t1r1' for 1T=1R, 't1r2' for 1T2R, or 't1r4' for 1T4R}

[0421] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T4R, 1T2R / 2T4R, or 1T=1R / 2T=2R / 4T=4R}. In one example, the number of SRS resources transmitted is one of {4, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T4R, 1T2R and 1T=1R, 2 ports for 2T4R and 2T=2R, and 4 ports for 4T=4R.

[0422] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, or 't1r8' for 1T8R}

[0423] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T8R, 1T6R, 1T4R / 2T8R, 2T6R, 1T2R / 2T4R / 4T8R, or 1T=1R / 2T=2R / 4T=4R}. In one example, the number of SRS resources transmitted is one of {8, 6, 4, 3, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T8R, 1T6R, 1T4R, 1T2R and 1T=1R, 2 ports for 2T8R, 2T6R, 2T4R and 2T=2R, and 4 ports for 4T8R and 4T=4R.

[0424] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of 't1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, or 't8r8' for 8T8R}.

[0425] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 'noTdm' or 'tdmAndNoTdm' for 8T8R}

[0426] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T8R, 1T6R, 1T4R / 2T8R, 2T6R, 1T2R / 2T4R / 4T8R, or 1T=1R / 2T=2R / 4T=4R / 8T8R}. In one example, the number of SRS resources transmitted is one of {8, 6, 4, 3, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T8R, 1T6R, 1T4R, 1T2R and 1T=1R, 2 ports for 2T8R, 2T6R, 2T4R and 2T=2R, 4 ports for 4T8R and 4T=4R and 8 ports for 8T8R.

[0427] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't3r3' for 3T=3R, 't3r6' for 3T / 6R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, or 't8r8' for 8T8R}.

[0428] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't3r3' for 3T=3R, 't3r6' for 3T / 6R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 'noTdm' or 'tdmAndNoTdm' for 8T8R}.

[0429] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T8R, 1T6R, 1T4R / 2T8R, 2T6R, 1T2R / 2T4R / 3T6R / 4T8R, or 1T=1R / 2T=2R / 3T=3R / 4T=4R / 8T8R}. - In one example, the number of SRS resources transmitted is one of {8, 6, 4, 3, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T8R, 1T6R, 1T4R, 1T2R and 1T=1R, 2 ports for 2T8R, 2T6R, 2T4R and 2T=2R, 3ports for 3T6R and 3T=3R, 4 ports for 4T8R and 4T=4R and 8 ports for 8T8R.

[0430] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T8R, 1T6R, 1T4R, 1T2R, or 1T=1R}.

[0431] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T8R, 1T4R, 1T2R, or 1T=1R}.

[0432] - In one example, the UE reports in RACH Msg3 or MsgA PUSCH one of {1T=1R, 1T2R, 1T4R, 1T6R, 1T8R, 2T=2R, 2T / 4R, 2T / 6R, 2T / 8R, 3T=3R, 3T / 6R, 4T=4R, 4T8R, or 8T8R}.

[0433] In the following examples, as described, a UE can indicate the support of early SRS and / or the UE's SRS antenna switching xTyR capability for early SRS in Msg3 or MsgA PUSCH. In one example, using a specific logical channel identifier (LCID) / extended LCID (eLCID) in MAC subheader of CCCH SDU included in Msg3 / MsgA MAC PDU can indicate the support of early SRS and / or the UE's SRS antenna switching xTyR capability for early SRS.

[0434] In one example, a same preamble is used whether or not the UE supports early SRS. The early SRS capability can be indicated in Msg3 or MsgA PUSCH / MAC PDU. In one example a set of preambles and / or ROs are configured for the UE to indicate early SRS (UE can randomly select a preamble / RO from the set for early SRS support indication), as aforementioned. The set of preambles and / or ROs can be per-SS / PBCH block, or can be common across SS / PBCH blocks.

[0435] In one example, LCID / eLCID codepoint (e.g. in MAC subheader of CCCH SDU included in Msg3 / MsgA) is configured for indicating the support of early SRS capability. In one example, the LCID / eLCID codepoint (e.g. in MAC subheader of CCCH SDU included in Msg3 / MsgA) can be configured separately for different CCCH SDU sizes (e.g. 48 bits and 64 bits) for indicating the support of early SRS capability. In one example LCID / eLCID codepoint for indicating the support of early SRS capability can be separately configured for one or more of the following: a) UE which is neither redCap UE nor eRedCap UE, b) UE which is redCap UE, c) UE which is eRedCap UE, d) UE which is neither redCap UE nor eRedCap UE and supports PUCCH repetition of Msg4 HARQ-ACK, e) UE which is redCap UE and supports PUCCH repetition of Msg4 HARQ-ACK, f) UE which is eRedCap UE and supports PUCCH repetition of Msg4 HARQ-ACK.

[0436] In one example, LCID / eLCIDs codepoints (e.g. in MAC subheader of CCCH SDU included in Msg3 / MsgA) are configured for indicating the SRS antenna switching xTyR capability. In one example, LCID / eLCIDs codepoints (e.g. in MAC subheader of CCCH SDU included in Msg3 / MsgA) can be configured separately for different CCCH SDU sizes (e.g. 48 bits and 64 bits) for indicating the SRS antenna switching xTyR capability. In one example LCID / eLCIDs codepoints for indicating the SRS antenna switching xTyR capability can be separately configured for one or more of the following: a) UE which is neither redCap UE nor eRedCap UE, b) UE which is redCap UE, c) UE which is eRedCap UE, d) UE which is neither redCap UE nor eRedCap UE and supports PUCCH repetition of Msg4 HARQ-ACK, e) UE which is redCap UE and supports PUCCH repetition of Msg4 HARQ-ACK, f) UE which is eRedCap UE and supports PUCCH repetition of Msg4 HARQ-ACK.

[0437] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of { 't1r2' for 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, or 't4r4' for 4T=4R}.

[0438] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {'t1r2' for 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r4-t2r4' for 1T4R / 2T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, or 't4r4' for 4T=4R}.

[0439] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of { 't1r2' for 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, 't4r4' for 4T=4R, or not supported}.

[0440] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {'t1r2' for 1T2R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't1r4-t2r4' for 1T4R / 2T4R, 't1r1' for 1T=1R, 't2r2' for 2T=2R, 't4r4' for 4T=4R, or not supported}.

[0441] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of { 't1r2' for 1T2R, 't1r1' for 1T=1R, or 't2r2' for 2T=2R}.

[0442] In one example, and the xTyR capability indicated by LCID / eLCID codepoint can be one of {'t1r1' for 1T=1R, 't1r2' for 1T2R, or 't1r4' for 1T4R}.

[0443] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {1T4R, 1T2R / 2T4R, 1T=1R / 2T=2R / 4T=4R}. In one example, the number of SRS resources transmitted is one of {4, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T4R, 1T2R and 1T=1R, 2 ports for 2T4R and 2T=2R, and 4 ports for 4T=4R. In one example, the number of ports is indicated in Msg3 or MsgA PUSCH.

[0444] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R}.

[0445] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, or not supported}.

[0446] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {1T8R, 1T6R, 1T4R / 2T8R, 2T6R, 1T2R / 2T4R / 4T8R, 1T=1R / 2T=2R / 4T=4R}. In one example, the number of SRS resources transmitted is one of {8, 6, 4, 3, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T8R, 1T6R, 1T4R, 1T2R and 1T=1R, 2 ports for 2T8R, 2T6R, 2T4R and 2T=2R, and 4 ports for 4T8R and 4T=4R. In one example, the number of ports is indicated in Msg3 or MsgA PUSCH.

[0447] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 't8r8' for 8T8R}.

[0448] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 't8r8' for 8T8R, or not supported}.

[0449] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 'noTdm' or 'tdmAndNoTdm' for 8T8R}.

[0450] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 'noTdm' or 'tdmAndNoTdm' for 8T8R, or not supported}.

[0451] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {1T8R, 1T6R, 1T4R / 2T8R, 2T6R, 1T2R / 2T4R / 4T8R, 1T=1R / 2T=2R / 4T=4R / 8T8R}. In one example, the number of SRS resources transmitted is one of {8, 6, 4, 3, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T8R, 1T6R, 1T4R, 1T2R and 1T=1R, 2 ports for 2T8R, 2T6R, 2T4R and 2T=2R, 4 ports for 4T8R and 4T=4R and 8 ports for 8T8R. In one example, the number of ports is indicated in Msg3 or MsgA PUSCH.

[0452] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't3r3' for 3T=3R, 't3r6' for 3T / 6R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 't8r8' for 8T8R}.

[0453] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't3r3' for 3T=3R, 't3r6' for 3T / 6R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 't8r8' for 8T8R, or not supported}.

[0454] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't3r3' for 3T=3R, 't3r6' for 3T / 6R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 'noTdm' or 'tdmAndNoTdm' for 8T8R}.

[0455] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {'t1r1' for 1T=1R, 't2r2' for 2T=2R, 't1r2' for 1T2R, 't3r3' for 3T=3R, 't3r6' for 3T / 6R, 't4r4' for 4T=4R, 't2r4' for 2T4R, 't1r4' for 1T4R, 't2r6' for 2T6R, 't1r6' for 1T6R, 't4r8' for 4T8R, 't2r8' for 2T8R, 't1r8' for 1T8R, 'noTdm' or 'tdmAndNoTdm' for 8T8R, or not supported}.

[0456] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {1T8R, 1T6R, 1T4R / 2T8R, 2T6R, 1T2R / 2T4R / 3T6R / 4T8R, 1T=1R / 2T=2R / 3T=3R / 4T=4R / 8T8R}. In one example, the number of SRS resources transmitted is one of {8, 6, 4, 3, 2, 1} respectively for each code point. In one example, the number of SRS ports per SRS resource is the number of Tx antennas, e.g., 1 port for 1T8R, 1T6R, 1T4R, 1T2R and 1T=1R, 2 ports for 2T8R, 2T6R, 2T4R and 2T=2R, 3ports for 3T6R and 3T=3R, 4 ports for 4T8R and 4T=4R and 8 ports for 8T8R. In one example, the number of ports is indicated in Msg3 or MsgA PUSCH.

[0457] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {1T8R, 1T6R, 1T4R, 1T2R, or 1T=1R}.

[0458] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {1T8R, 1T6R, 1T4R, 1T2R, 1T=1R or not supported}.

[0459] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {1T8R, 1T4R, 1T2R, or 1T=1R}.

[0460] In one example, and the xTyR capability indicated by a LCID / eLCID codepoint can be one of {1T8R, 1T4R, 1T2R, 1T=1R or not supported}.

[0461] In a variant of the aforementioned examples, there are N codepoints indicated by the LCID / eLCID codepoint, wherein each code-point can be a subset of {1T=1R, 1T2R, 1T4R, 1T6R, 1T8R, 2T=2R, 2T / 4R, 2T / 6R, 2T / 8R, 3T=3R, 3T / 6R, 4T=4R, 4T8R, 8T8R}.

[0462] In a variant of the aforementioned examples the following examples are provided:

[0463] - In one example, the early SRS capability and / or UE's SRS antenna switching xTyR capability can be indicated in Msg3 or MsgA PUSCH by including a MAC CE (e.g. SRS capability MAC CE) in Msg3 or MsgA MAC PDU wherein the MAC PDU include CCCH SDU and the MAC CE. One or more fields in the MAC CE indicate early SRS capability and / or UE's SRS antenna switching xTyR capability. In one example, UE can indicate that it supports early SRS through the PRACH preamble and in response network provides large enough grant in random access response to transmit Msg3 including UE's other SRS capabilities such as SRS antenna switching xTyR capability in MAC CE.

[0464] - In one example, the one or more early SRS capability can be indicated by LCID / eLCID of CCCH SDU in Msg3 or MsgA PUSCH / MAC PDU and other SRS capability can be indicated by a MAC CE in Msg3 or MsgA PUSCH / MAC PDU .

[0465] - In one example, the early SRS capability and / or UE's SRS antenna switching xTyR capability can be indicated in Msg3 or MsgA PUSCH / MAC PDU in LCID / eLCID of CCCH SDU.

[0466] - In one example, the early SRS capability and / or UE's SRS antenna switching xTyR capability can be indicated in Msg3 or MsgA PUSCH / MAC PDU by a combination of LCID / eLCID of CCCH SDU and MAC CE (e.g., using one or more new fields). In one example, indication of xTyR, y / x can be indicated by LCID / eLCID, and x can be indicated by a new field in MAC CE. In one example, indication of xTyR, y / x can be indicated by LCID / eLCID, and y can be indicated by a new field in MAC CE. In one example, indication of xTyR, x can be indicated by LCID / eLCID, and y / x can be indicated by a new field in MAC CE. In one example, indication of xTyR, y can be indicated by LCID / eLCID, and y / x can be indicated by a new field in MAC CE. In one example, indication of xTyR, y can be indicated by LCID / eLCID, and x can be indicated by a new field in MAC CE. In one example, indication of xTyR, x can be indicated by LCID / eLCID, and y can be indicated by a new field in MAC CE.

[0467] In one example, an SRS transmission is triggered in the random access response (RAR) (e.g., Msg2) to a preamble transmission. In one example, an SRS transmission is triggered in the random access response (RAR) (e.g., Msg2) to a preamble transmission for a contention based random access procedure. In one example, an SRS transmission is triggered in the random access response (RAR) (e.g., Msg2) to a preamble transmission for a contention free random access procedure. In one example, the SRS is triggered in a RAR if the UE supports early SRS. In one example, the indication of the support of early SRS is indicated by the preamble and / or PRACH Occasion (RO) used for the random access procedure. For example, the preambles and / or ROs can be partitioned into 2 groups if a UE doesn't support early SRS or doesn't request early SRS a preamble and / or RO in the first group is used (e.g. ), if a UE supports early SRS or supports and requests early SRS, a preamble and / or RO in the second group is used (e.g. ). In a variant example, there are groups of preambles and / or ROs, as aforementioned, wherein the groups can indicate the UE's capability to support or not support early SRS, and / or the capability of the UE in regard to SRS antennas switching as aforementioned.

[0468] In one example, a UE is configured e.g., by a field or flag in the system information to transmit SRS in response to receiving a RAR. The SRS transmission can be further conditioned on whether the UE transmits an associated PRACH preamble / RO from a first group of preambles / ROs or from a second group of preambles / ROs indicated in the system information. In one example, if a UE is configured by system information with a first set of preambles / ROs for “no early” SRS and a second of preambles / ROs for “early SRS”, the UE can:

[0469] - If the UE transmits a preamble / RO associated with “no early SRS”, the UE doesn't expect to receive a trigger for early SRS in the RAR. In a variant example, if a UE receives a trigger for early SRS in the RAR, the UE ignores the trigger.

[0470] - In one example, if the UE transmits a preamble / RO associated with “early SRS”, the RAR doesn't include a flag for early SRS trigger, the UE transmits the early SRS upon receiving the RAR.

[0471] - In one example, if the UE transmits a preamble / RO associated with “early SRS”, the RAR includes a flag for early SRS trigger, based on the flag the UE transmits or doesn't transmit the early SRS upon receiving the RAR.

[0472] In one example, a UE is indicated in the RAR to transmit a SRS. In one example, a flag or a field in the RAR can indicate whether the UE transmits SRS in response to receiving the RAR. In one example, a field in the MAC sub-header for Random Access Response, e.g., a reserved field in the MAC sub-header for the Random Access Response can be used to trigger the SRS, for example, a value of “1” triggers the SRS, and a value of “0” doesn't trigger the SRS on vice versa. In one example, a field in the MAC RAR, e.g., a reserved field in the MAC RAR can be used to trigger the SRS, for example, a value of “1” triggers the SRS, and a value of “0” doesn't trigger the SRS or vice versa.

[0473] In one example, a UE is indicated by a flag (e.g., one-bit flag) or a special bit pattern in the RAR to transmit SRS. In one example, the UE transmits SRS instead of or in place of PUSCH Msg3. In one example, the UE transmits SRS in addition to PUSCH Msg3 (before or after PUSCH Msg3). In one example, the flag (e.g., one-bit flag) is included in the MAC sub-header for the Random Access Response, e.g., for Type-1 Random Access Procedure. In one example, the flag (e.g., one-bit flag) is included in the MAC RAR, e.g., for Type-1 Random Access Procedure. In one example, the flag (e.g., one-bit flag) is included in the UL Grant of the MAC RAR, e.g., for Type-1 Random Access Procedure. In one example, a special bit pattern of fields in the UL Grant of the MAC RAR, e.g., for Type-1 Random Access Procedure, indicates transmission of SRS. In one example, the flag (e.g., one-bit flag) is included in the DCI scheduling PDSCH of the MAC RAR. In one example, a special bit pattern of fields in the DCI scheduling the PDSCH of the MAC RAR indicates transmission of SRS.

[0474] In one example, a UE is indicated by a SRS resource filed in the RAR to use for SRS transmission. In one example, the UE transmits SRS instead of or in place of PUSCH Msg3. In one example, the UE transmits SRS in addition to PUSCH Msg3 (before or after PUSCH Msg3). In one example, the SRS resource is included in the MAC RAR, e.g., for Type-1 Random Access Procedure. In one example, the SRS resource is included in the UL Grant of the MAC RAR, e.g., for Type-1 Random Access Procedure. In one example, the SRS resource is included in the DCI scheduling the PDSCH of the MAC RAR. In one example, the SRS resource is linked to (associated with) the preamble index. In one example, the SRS resource is linked to (associated with) the PRACH occasion. In one example, the SRS resource is linked to (associated with) the preamble index and the PRACH occasion. In one example, the preambles and / or ROs are portioned into N groups as aforementioned, the UE can determine the SRS resource based on the group of the preamble and / or RO, e.g., based on the antenna switching capability, in one example, one of the groups can be associated with no early SRS transmission. In one example, the SRS resource includes a SRS resource ID and / or SRS resource set ID configured to the UE from a list of SRS resources and / or a list of SRS resource sets configured to the UE, wherein the configuration can be by SIB signaling or by RRC signaling. In one example, the SRS resource includes configuration / scheduling parameters for the SRS, such as time domain resources (e.g., symbol(s) in a slot to use for SRS, time offset from the RAR, time offset from Msg3, or time offset within a period, SRS period, etc.), frequency domain resources (e.g., starting RB, number of RBs, frequency hopping pattern, etc.), comb parameters (e.g., comb size, comb offset, cyclic shift, etc.), sequence, sequence hopping (e.g., group hopping, sequence hopping or neither, etc.). In one example, the UL grant of the MAC RAR includes parameters to schedule the SRS resource.

[0475] In one example, a UE is indicated by a flag (e.g., one-bit flag) or a special bit pattern in the RAR to transmit SRS and is indicated an SRS resource in the RAR. In one example, the UE transmits SRS instead of or in place of PUSCH Msg3. In one example, the UE transmits SRS in addition to PUSCH Msg3 (before or after PUSCH Msg3). In one example, the SRS resource includes a SRS resource ID and / or SRS resource set ID configured to the UE from a list of SRS resources and / or a list of SRS resource sets configured to the UE, wherein the configuration can be by SIB signaling or by RRC signaling. In one example, the SRS resource includes configuration / scheduling parameters for the SRS, such as time domain resources (e.g., symbol(s) in a slot to use for SRS, time offset from the RAR, or time offset within a period, SRS period, etc.), frequency domain resources (e.g., starting RB, number of RBs, frequency hopping pattern, etc.), comb parameters (e.g., comb size, comb offset, cyclic shift, etc.), sequence, sequence hopping (e.g., group hopping, sequence hopping or neither, etc.). In one example, the UL grant of the MAC RAR includes parameters to schedule the SRS resource. The indication of the flag (e.g., one-bit flag) or special pattern and the SRS resource can follow one of the examples of Table 4.

[0476] In one example, the UE determines the early SRS resource or resources or SRS resource set to transmit based in the antenna switching capability if known. In one example, the antenna switching capability (e.g., xTyR or whether it is supported or not) is signaled based on a preamble and / or RO index or group as aforementioned. In one example, the antenna switching capability is signaled in Msg3, for an early SRS transmitted after Msg3, the network and UE can be aligned on the antenna switching capability and early SRS resource(s) used.

[0477]

[0478] In one example, M SRS resources or resource sets are configured by system information. In one example, the SRS resource set ID and / or the SRS resource ID transmitted by a UE is determined based on one or more of the following:

[0479] - Based on a TC-RNTI conveyed by the RAR, e.g. the n least significant bits of the TC-RNTI, or the n most significant bits of the TC-RNTI, or indicated ID is TC-RNTI % N, or indicated ID is ceiling (TC-RNTI / N).

[0480] - Based on a UE-ID indicated in or determined by a paging message that triggered the random access procedure associated with the RAR.

[0481] - Based on the C-RNTI (or UE-ID), in Msg3, the UE and the gNB can identify a SRS resource (e.g., SRS resource in a stored context associated with the C-RNTI or the UE-ID).

[0482] - Based on the preamble index associated with the RAR.

[0483] - Based on the PRACH occasion (RO) associated with the RAR.

[0484] - Based on the preamble index and PRACH occasion (RO) associated with the RAR.

[0485] - Based on the group of the preamble and / or RO associated with the RAR as aforementioned.

[0486] - Based on the antenna switching capability or a default antenna switching capability if antenna switching capability is unknown at the time of early SRS transmission or early SRS triggering.

[0487] - The time and / or frequency resources of a PDCCH reception providing a DCI format scheduling a RAR or of the PDSCH reception providing the RAR.

[0488] In one example, in case of antenna switching, with multiple SRS resources or SRS resource sets, an SRS resource ID (and / or SRS resource set ID) can be determined by or be linked or mapped to multiple SRS resources or SRS resource sets based on the antenna switching capability, and the corresponding number of SRS resources.

[0489] In one example, the network configures SRS resource(s) or SRS resource set(s) for each preamble-ID. In one example, the network configures SRS resource(s) or SRS resource set(s) for each RO within a frame. In one example, the network configures SRS resource(s) or SRS resource set(s) for each RO within an association period. In one example, the network configures SRS resource(s) or SRS resource set(s) for each RO within an association pattern period. In one example, the network configures SRS resource(s) or SRS resource set(s) for each RO within N frames, wherein N is configured and / or updated RRC and / or MAC CE and L1 control (e.g., DCI format) signaling, or N is specified in the system specifications, e.g., N = 16, or N = 8.

[0490] In one example, the network configures SRS resource(s) or SRS resource set(s) for each preamble-ID-RO pair. Wherein, RO can be:

[0491] - Within a frame.

[0492] - Within an association period.

[0493] - Within an association pattern period.

[0494] - Within N frames, wherein N is configured and / or updated RRC and / or MAC CE and L1 control (e.g., DCI format) signaling, or N is specified in the system specifications, e.g., N = 16, or N = 8.

[0495] In one example, this mapping between the SRS resource ID (and / or SRS resource set ID) and the aforementioned parameters is based on a rule. In one example, this mapping between the SRS resource ID (and / or SRS resource set ID) and the aforementioned parameters is based on a network configuration. In one example, this mapping between the SRS resource ID (and / or SRS resource set ID) and the aforementioned parameters is based on a combination of a rule and network configuration.

[0496] In one example, the SRS resource ID (and / or SRS resource set ID) transmitted by a UE is determined based on one or more of the following:

[0497] - A SRS ID of the M SRS resource IDs (and / or SRS resource set IDs) configured by system information, wherein the SRS resource ID (and / or SRS resource set ID) is included in the DCI Format scheduling the RAR and / or the RAR.

[0498] - In a variant, the SRS configuration parameters (or a subset of them) for the SRS resource can be included in the DCI Format scheduling the RAR and / or the RAR instead of or in addition to the SRS ID. Wherein the configuration parameters for the SRS resource can be as aforementioned.

[0499] In one example, the SRS resource can be transmitted at or after a time T after the end (or start) of the PDSCH reception providing the RAR or of end (or start) of the PDCCH reception providing the DCI Format scheduling the RAR associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource can be at or after a time T after the end (or start) or time unit (e.g., slot) of PDSCH reception providing the RAR or of end (or start) or time unit (e.g., slot) of the PDCCH reception providing the DCI Format scheduling the RAR associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource is that first slot or subframe or frame that starts at or after a time T after the end (or start) or time unit (e.g., slot) of PDSCH reception providing the RAR or of end (or start) or time unit (e.g., slot) of PDCCH reception providing the DCI Format scheduling the RAR associated with the UE transmitting SRS and optionally based on an offset and a periodicity as illustrated in FIG. 15A (the SRS instances can be one-shot, N-shots or semi-persistent), where SRS trigger can be replaced by the PDSCH providing the RAR or the PDCCH providing the DCI Format scheduling the RAR associated with the UE transmitting SRS. Wherein, the time T can be defined in the system specifications and / or configured or updated by network (e.g., using SIB signaling and / or RRC signaling and / or MAC CE signaling and / or L1 control signaling).

[0500] In one example, the RAR and / or DCI scheduling the RAR includes a flag to trigger SRS. The SRS is transmitted after RACH Msg3. In one example, the UE has a stored context, and the stored context is associated with a C-RNTI (or a UE ID), for example the UE is in INACTIVE state. In one example, the UE transmits a C-RNTI MAC CE (or UE ID) in the Msg3, based on the C-RNTI (or UE-ID) the UE and the gNB can identify a SRS resource (e.g., SRS resource in a stored context associated with the C-RNTI or the UE-ID).

[0501] In one example, the RAR and / or DCI scheduling the RAR includes a flag to trigger SRS. The SRS is transmitted after RACH Msg3. In one example, Msg3 can convey antenna switching capability, and the SRS resource(s) is determined based on the antenna switching capability as aforementioned. In a variant example, the antenna switching capability is conveyed by a combination of signaling in the preamble / RO (e.g., based on preamble and / or RO group as aforementioned) and signaling in Msg3. In one example, early SRS capability in Msg3 is indicated by 1 bit in RRC message or using a specific LCID / eLCID in MAC PDU.

[0502] In one example, if the RAR includes a trigger for early SRS transmission, Msg3 can further include an indication whether or not the UE is transmitting the early SRS.

[0503] In one example, the SRS resource can be transmitted at or after a time T after the end (or start) of the PUSCH transmission containing Msg3 associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource can be at or after a time T after the end (or start) or time unit (e.g., slot) of the PUSCH transmission containing Msg3 associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource is that first slot or subframe or frame that starts at or after a time T after the end (or start) or time unit (e.g., slot) of the PUSCH transmission containing Msg3 associated with the UE transmitting SRS and optionally based on an offset and a periodicity as illustrated in FIG. 15A (the SRS instances can be one-shot, N-shots or semi-persistent), where SRS trigger can be replaced by the PUSCH transmission containing Msg3 associated with the UE transmitting SRS. Wherein, the time T can be defined in the system specifications and / or configured or updated by network (e.g., using SIB signaling and / or RRC signaling and / or MAC CE signaling and / or L1 control signaling).

[0504] In one example, an SRS transmission is triggered in contention resolution message providing a C-RNTI for the UE, or in Msg4, of a random access procedure. In one example, an SRS transmission is triggered in contention resolution message or Msg4 of a contention-based random access procedure. In one example, the SRS is triggered in a Msg4 if the UE supports early SRS. In one example, the indication of the support of early SRS is indicated by the preamble and / or PRACH Occasion (RO) used for the random access procedure. For example, the preambles and / or ROs can be partitioned into 2 groups if a UE doesn't support early SRS or doesn't request early SRS a preamble and / or RO in the first group is used (e.g. ), if a UE supports early SRS or supports and requests early SRS, a preamble and / or RO in the second group is used (e.g. ). In a variant example, there are groups of preambles and / or ROs, as aforementioned, wherein the groups can indicate the UE's capability to support or not support early SRS, and / or the capability of the UE in regard to SRS antennas switching as aforementioned.

[0505] In one example, the indication of the support of early SRS is indicated by Msg3 (or MsgA) of the random access procedure. Support of early SRS can be indicated in MAC subheader (e.g. by using a pre-defined LCID or eLCID) or MAC CE or RRC message (e.g. RRC setup request or RRC resume request) included in Msg3 / MsgA MAC PDU. In a variant example, Msg3 can indicate the UE's capability to support or not support early SRS, and / or the capability of the UE in regard to SRS antennas switching as aforementioned. In a variant example, the UE's capability to support or not support early SRS, and / or the antenna switching capability is conveyed by a combination of signaling in the preamble / RO (e.g., based on preamble and / or RO group as aforementioned) and signaling in Msg3.

[0506] In one example, a UE is configured e.g., by a field or flag in the system information to transmit SRS in response to receiving a contention resolution message, or in Msg4, or in a DCI Format scheduling Msg4 or MsgB. The SRS transmission can be further conditioned on whether the UE transmits an associated PRACH preamble from a first group of preambles or from a second group of preambles indicated in the system information. In one example, if a UE is configured by system information with a first set of preamble for “no early” SRS and a second of preambles for “early SRS”, the UE can:

[0507] - If the UE transmits a preamble associated with “no early SRS”, the UE doesn't expect to receive a trigger for early SRS in a contention resolution message, or in Msg4, or in a DCI Format scheduling Msg4. In a variant example, if a UE receives a trigger for early SRS in a contention resolution message, or in Msg4, or in a DCI Format scheduling Msg4, the UE ignores the trigger.

[0508] - In one example, if the UE transmits a preamble associated with “early SRS”, the contention resolution message, or Msg4, or DCI Format scheduling Msg4 doesn't include a flag for early SRS trigger, the UE transmits the early SRS upon receiving the contention resolution message, or Msg4, or DCI Format scheduling Msg4.

[0509] - In one example, if the UE transmits a preamble associated with “early SRS”, the contention resolution message, or Msg4, or DCI Format scheduling Msg4 includes a flag for early SRS trigger, based on the flag the UE transmits or doesn't transmit the early SRS upon receiving the contention resolution message, or Msg4, or DCI Format scheduling Msg4.

[0510] In one example, a field in the DCI Format scheduling Msg4 can indicate whether or not the UE is triggered to transmit early SRS in response to Msg4. In one example, the field is 1-bit, “1” indicates that early SRS is triggered in response to Msg4, and “0” indicates that early SRS is not triggered in response to Msg4, or vice versa. In one example, the field is 2-bits (or in general n-bits), wherein a first value of the filed indicates that early SRS is not triggered in response to Msg4, and a second, third and fourth ... values of the field indicate one of respective first, second and third, ... configurations to use for early SRS. The first, second and third, ... configurations can be configured in the SIB (e.g., SIB1), or provided by a configuration in Msg4.

[0511] In one example, when the field for indicating early SRS trigger is one-bit, the field for indicating early SRS trigger is provided by a bit (e.g., the MSB or LSB bit) of downlink assignment index field in the DCI Format scheduling Msg4. In one example, the second bit of the downlink assignment index field in the DCI Format scheduling Msg4 is reserved. In one example, the second bit of the downlink assignment index field in the DCI Format scheduling Msg4 is used to indicate a number of repetitions, if any, of PUCCH. In one example, whether the second bit of the downlink assignment index field in the DCI Format scheduling Msg4 is reserved or is used to indicate a number of repetitions, if any, of PUCCH Msg4 can be configured in the SIB.

[0512] In one example, when the field for indicating early SRS trigger is one-bit, the field for indicating early SRS trigger is provided by a bit (e.g., the MSB or LSB bit) of one of the following fields, the remaining bits can be used for the intended purpose:

[0513] - Modulation and coding scheme (MCS) field, wherein the remaining bits (e.g., 4 bits) are used to indicate the MCS for Msg4.

[0514] - Redundancy version (RV) field, wherein the remaining bits (e.g., 1 bit) is used to indicate the RV for Msg4 (e.g., RV can be 0 and 1, or 0 and 2, or 0 and 3).

[0515] - HARQ process number (HPN) field, wherein the remaining bits (e.g., 3 bits) are used to indicate a HPN.

[0516] - TPC command field, wherein the remaining bits (e.g., 1 bit) is used to indicate TPC value for PUCCH carrying Msg4 HARQ-ACK (e.g., a bit to indicate whether to increase or decrease power by a power step size in dB, or a bit to indicate whether to increase the power by a power step size in dB, or keep unchanged, or a bit to indicate whether to decrease the power by a power step size in dB, or keep unchanged)

[0517] - PUCCH resource indicator (PRI) field, wherein the remaining bits (e.g., 2 bits) are used to indicate the PRI for Msg4 PUCCH.

[0518] - PDSCH-to-HARQ feedback timing indicator (PHFTI) field, wherein the remaining bits (e.g., 2 bits) are used to indicate the PHFTI for Msg4 PUCCH.

[0519] In one example, when the field for indicating early SRS trigger is two-bits, the field for indicating early SRS trigger is provided by the downlink assignment index field in the DCI Format scheduling Msg4. In one example, whether the downlink assignment index field in the DCI Format scheduling Msg4 is reserved or is used for early SRS triggering and / or is used to indicate a number of repetitions, if any, of PUCCH Msg4 can be configured by the SIB (e.g., SIB1) or dynamically indicated by another field in the DCI Format scheduling Msg4.

[0520] In one example, when the field for indicating early SRS trigger is two-bits, the field is provided by two bits (e.g., the two MSB or two LSB bits of a field - when the field has more than 2 bits) of one of the following fields, the remaining bits can be used for the intended purpose:

[0521] - Modulation and coding scheme (MCS) field, wherein the remaining bits (e.g., 3 bits) are used to indicate the MCS for Msg4.

[0522] - Redundancy version (RV) field, wherein the RV of Msg4 is 0, e.g., RV field has 2 bits.

[0523] - HARQ process number (HPN) field, wherein the remaining bits (e.g., 2 bits) are used to indicate a HPN.

[0524] - TPC command field, wherein the power of the Msg4 PUCCH remains unchanged, e.g., TPC field has 2 bits.

[0525] - PUCCH resource indicator (PRI) field, wherein the remaining bits (e.g., 1 bit) is used to indicate the PRI for Msg4 PUCCH.

[0526] - PDSCH-to-HARQ feedback timing indicator (PHFTI) field, wherein the remaining bit (e.g., 1 bit) is used to indicate the PHFTI for Msg4 PUCCH.

[0527] In one example, when the field for indicating early SRS trigger is two-bits, the field is provided by a first bit (e.g., the MSB or LSB bit of first field) of one of the following fields, and second bit (e.g., the MSB or LSB bit of a second field) of one of the following fields, the remaining bits can be used for the intended purpose:

[0528] - Modulation and coding scheme (MCS) field, wherein the remaining bits (e.g., 4 bits) are used to indicate the MCS for Msg4.

[0529] - Redundancy version (RV) field, wherein the remaining bits (e.g., 1 bit) is used to indicate the RV for Msg4 (e.g., RV can be 0 and 1, or 0 and 2, or 0 and 3).

[0530] - HARQ process number (HPN) field, wherein the remaining bits (e.g., 3 bits) are used to indicate a HPN.

[0531] - TPC command field, wherein the remaining bit (e.g., 1 bit) is used to indicate TPC value for PUCCH carrying Msg4 HARQ-ACK (e.g., a bit to indicated whether to increase or decrease power by a power step size in dB, or a bit to indicate whether to increase the power by a power step size in dB, or keep unchanged, or a bit to indicate whether to decrease the power by a power step size in dB, or keep unchanged)

[0532] - PUCCH resource indicator (PRI) field, wherein the remaining bits (e.g., 2 bits) are used to indicate the PRI for Msg4 PUCCH.

[0533] - PDSCH-to-HARQ feedback timing indicator (PHFTI) field, wherein the remaining bits (e.g., 2 bits) are used to indicate the PHFTI for Msg4 PUCCH.

[0534] In a variant example, a field is added to the DCI Format scheduling Msg4 for early SRS triggering. In one example, the field for early SRS triggering is 1-bit. In one example, the field for early SRS triggering is 2-bits. In one example, the field for early SRS triggering is n-bits. In one example, whether the field for early SRS triggering is added to the DCI Format scheduling Msg4, can be based on indication in Msg1 (PRACH preamble), or Msg3, e.g., based on whether or not the UE supports early SRS triggering. In one example, the size of the field added (e.g., n) can be based on configuration in SIB (e.g., SIB1 or SIB2), e.g., SIB can configure n, or SIB can configure a number of early SRS configurations, N, for early SRS transmission, and or

[0535] In the aforementioned examples, Msg4 can be replaced by MsgB, and DCI Format scheduling Msg4 can be replaced by DCI Format scheduling MsgB, and Msg4 PUCCH can be replaced by MsgB PUCCH, and Msg1 (PRACH preamble) can be replaced MsgA PRACH, and Msg3 can be replaced MsgA PUSCH.

[0536] In the aforementioned examples, early SRS triggering, can be replaced by early CSI-RS measurement and / or early CSI reporting, wherein the trigger can be for early measuring of CSI-RS (or SSB) using configured resources (e.g., in SIB1 or in Msg4) and / or early reporting of CSI on uplink resources (e.g., PUCCH or PUSCH) wherein the UL resources and report configuration are configured by SIB1 or in Msg4.

[0537] For brevity, only the contention resolution message is referred to in the following.

[0538] In one example, a UE is indicated in the contention resolution message or Msg4 to transmit a SRS. In one example, a flag or a field in the contention resolution message can indicate whether the UE transmits SRS in response to receiving the contention resolution message or Msg4.

[0539] In one example, a MAC CE in the contention resolution message or Msg4 can provide a configuration for SRS transmission by the UE.

[0540] In one example, the UE determines the early SRS resource or resources to transmit based in the antenna switching capability if known. In one example, the antenna switching capability (e.g., xTyR or whether it is supported or not) is signaled based on a preamble and / or RO index or group and / or signaling in Msg3 as aforementioned.

[0541] In one example, M SRS resources or SRS resource sets are configured by system information. In one example, the SRS resource ID (and / or SRS resource set ID) transmitted by a UE is determined based on one or more of the following:

[0542] - Based on a C-RNTI conveyed by the contention resolution, e.g. the n least significant bits of the C-RNTI, or the n most significant bits of the C-RNTI, or indicated ID is C-RNTI % N, or indicated ID is ceiling (C-RNTI / N).

[0543] - Based on the C-RNTI (or UE-ID) the UE and the gNB can identify a SRS resource (e.g., SRS resource in a stored context associated with the C-RNTI or the UE-ID).

[0544] - Based on a TC-RNTI used by the random access procedure, e.g. the n least significant bits of the TC-RNTI, or the n most significant bits of the TC-RNTI, or indicated ID is TC-RNTI % N, or indicated ID is ceiling (TC-RNTI / N).

[0545] - Based on a UE-ID indicated in a paging message that triggered the random access procedure associated with the contention resolution.

[0546] - Based on the preamble index associated with the random access procedure.

[0547] - Based on the PRACH occasion (RO) associated with the RAR.

[0548] - Based on the preamble index and PRACH occasion (RO) associated with the RAR.

[0549] - Based on the group of the preamble and / or RO associated with the RAR as aforementioned.

[0550] - Based on signaling in Msg3.

[0551] - Based on the antenna switching capability or a default antenna switching capability if antenna switching capability is unknown at the time of early SRS transmission or early SRS triggering.

[0552] - The time and / or frequency resources of a DCI format scheduling a contention resolution / Msg4 or of the contention resolution / Msg4.

[0553] - Based on the resource used for HARQ-ACK acknowledgment of contention resolution / Msg4.

[0554] - Based on an information provided by a MAC CE in the contention resolution message / Msg4.

[0555] In one example, in case of antenna switching, with multiple SRS resources or SRS resource sets, an SRS resource ID (and / or SRS resource set ID) can be determined by or be linked or mapped to multiple SRS resources or SRS resource sets based on the antenna switching capability, and the corresponding number of SRS resources.

[0556] In one example, the network configures SRS resource(s) or SRS resource set(s) for each preamble-ID. In one example, the network configures SRS resource(s) or SRS resource set(s) for each RO within a frame. In one example, the network configures SRS resource(s) or SRS resource set(s) for each RO within an association period. In one example, the network configures SRS resource(s) or SRS resource set(s) for each RO within an association pattern period. In one example, the network configures SRS resource(s) or SRS resource set(s) for each RO within N frames, wherein N is configured and / or updated RRC and / or MAC CE and L1 control (e.g., DCI format) signaling, or N is specified in the system specifications, e.g., N = 16, or N = 8.

[0557] In one example, the network configures SRS resource(s) or SRS resource set(s) for each preamble-ID-RO pair. Wherein, RO can be:

[0558] - Within a frame.

[0559] - Within an association period.

[0560] - Within an association pattern period.

[0561] - Within N frames, wherein N is configured and / or updated RRC and / or MAC CE and L1 control (e.g., DCI format) signaling, or N is specified in the system specifications, e.g., N = 16, or N = 8.

[0562] In one example, this mapping between the SRS resource ID (and / or SRS resource set ID) and the aforementioned parameters is based on a rule. In one example, this mapping between the SRS resource ID (and / or SRS resource set ID) and the aforementioned parameters is based on a network configuration. In one example, this mapping between the SRS resource ID (and / or SRS resource set ID) and the aforementioned parameters is based on a combination of a rule and network configuration.

[0563] In one example, the SRS resource ID (and / or SRS resource set ID) transmitted by a UE is determined based on one or more of the following:

[0564] - A SRS ID of the M SRS resource IDs (and / or SRS resource set IDs) configured by system information, wherein the SRS resource ID (and / or SRS resource set ID) is included in the DCI Format scheduling the contention resolution or Msg4 and / or in the contention resolution message or Msg4.

[0565] - In a variant, the SRS configuration parameters (or a subset of them) for the SRS resource can be included in the DCI Format scheduling the contention resolution message or Msg4 and / or in the contention resolution message or Msg4 instead of or in addition to the SRS ID. Wherein the configuration parameters for the SRS resource can be as aforementioned.

[0566] In one example, the SRS resource can be transmitted at or after a time T after the end (or start) of the PDSCH reception providing the contention resolution message or Msg4 or of the PDCCH reception providing the DCI Format scheduling the contention resolution message or Msg4 associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource can be at or after a time T after the end (or start) or time unit (e.g., slot) of the PDSCH reception providing the contention resolution message or Msg4 or of the PDCCH reception providing the DCI Format scheduling the contention resolution message or Mgs4 associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource is that first slot or subframe or frame that starts at or after a time T after the end (or start) or time unit (e.g., slot) of the PDSCH reception providing the contention resolution message or Msg4 or of the PDCCH reception providing the DCI Format scheduling the contention resolution message or Msg4 associated with the UE transmitting SRS and optionally based on an offset and a periodicity as illustrated in FIG.15A (the SRS instances can be one-shot, N-shots or semi-persistent), where SRS trigger can be replaced by the PDSCH providing the contention resolution message / Msg4 or the PDCCH providing the DCI Format scheduling the contention resolution message / Msg4 associated with the UE transmitting SRS transmission. Wherein, the time T can be defined in the system specifications and / or configured or updated by network (e.g., using SIB signaling and / or RRC signaling and / or MAC CE signaling and / or L1 control signaling).

[0567] In one example, an SRS transmission is triggered in MsgB of a Type-2 random access procedure. In one example, MsgB is for successRAR. In one example, MsgB is for a fallback RAR. In one example, an SRS transmission is triggered in MsgB successRAR of a contention-based random access procedure. In one example, an SRS transmission is triggered in MsgB fallbackRAR of a contention-free random access procedure. In one example, the SRS is triggered in a successRAR or fallbackRAR if the UE supports early SRS. In one example, the indication of the support of early SRS is indicated by the preamble and / or PRACH Occasion (RO) used for the Type-2 random access procedure. For example, the preambles and / or ROs of the MsgA PRACH can be partitioned into 2 groups if a UE doesn't support early SRS or doesn't request early SRS a preamble and / or RO in the first group is used (e.g. ), if a UE supports early SRS or supports and requests early SRS, a preamble and / or RO in the second group is used (e.g. ). In a variant example, there are groups of preambles and / or ROs, as aforementioned, wherein the groups can indicate the UE's capability to support or not support early SRS, and / or the capability of the UE in regard to SRS antennas switching as aforementioned.

[0568] In one example, the indication of the support of early SRS is indicated by MsgA PUSCH of the random access procedure. In a variant example, MsgA PUSCH can indicate the UE's capability to support or not support early SRS, and / or the capability of the UE in regard to SRS antennas switching as aforementioned. In a variant example, the UE's capability to support or not support early SRS, and / or the antenna switching capability is conveyed by a combination of signaling in the preamble / RO of MsgA PRACH (e.g., based on preamble and / or RO group as aforementioned) and signaling in MsgA PUSCH. In one example, early SRS capability in MsgA is indicated by 1 bit in RRC message or using a specific LCID / eLCID in MAC PDU.

[0569] In one example, a UE is configured e.g., by a field or flag in the system information to transmit SRS in response to receiving a MsgB. The SRS transmission can be further conditioned on whether the UE transmits an associated MsgA PRACH preamble / RO from a first group of preambles / ROs or from a second group of preambles / ROs indicated in the system information. In one example, if a UE is configured by system information with a first set of preamble for “no early” SRS and a second of preambles for “early SRS”, the UE can:

[0570] - If the UE transmits a preamble / RO associated with “no early SRS”, the UE doesn't expect to receive a trigger for early SRS in the successRAR or fallbackRAR or MsgB. In a variant example, if a UE receives a trigger for early SRS in the successRAR or fallbackRAR, the UE ignores the trigger.

[0571] - In one example, if the UE transmits a preamble / RO associated with “early SRS”, the successRAR or fallbackRAR or MsgB or DCI scheduling MsgB doesn't include a flag for early SRS trigger, the UE transmits the early SRS upon receiving the successRAR or fallbackRAR.

[0572] - In one example, if the UE transmits a preamble / RO associated with “early SRS”, the successRAR or fallbackRAR or MsgB or DCI scheduling MsgB includes a flag for early SRS trigger, based on the flag in the UE transmits or doesn't transmit the early SRS upon receiving the successRAR or fallbackRAR or MsgB or DCI scheduling MsgB.

[0573] In one example, a UE is indicated in the MsgB or DCI scheduling MsgB to transmit a SRS. In one example, a flag or a field in the MsgB can indicate whether the UE transmits SRS in response to receiving the MsgB. In one example, MsgB can include a fallback RAR. In one example, MsgB can include a success RAR. In one example, a field in the MAC sub-header for success RAR or the fallback RAR, e.g., a reserved field in the MAC sub-header for the success RAR or fallback RAR can be used to trigger the SRS, for example, a value of “1” triggers the SRS, and a value of “0” doesn't trigger the SRS or vice versa. In one example, a field in the success RAR or fallback RAR, e.g., a reserved field in the success RAR or fallback RAR can be used to trigger the SRS, for example, a value of “1” triggers the SRS, and a value of “0” doesn't trigger the SRS or vice versa.

[0574] In one example, a UE is indicated by a flag (e.g., one-bit flag) or a special bit pattern in the MsgB (e.g., fallbackRAR or successRAR) or DCI scheduling Msg4 to transmit SRS. In one example, the UE transmits SRS instead of or in place of PUSCH Msg3. In one example, the UE transmits SRS in addition to PUSCH Msg3, e.g., scheduled by fallbackRAR, (before or after PUSCH Msg3). In one example, the flag (e.g., one-bit flag) is included in the MAC sub-header for the success RAR or fallback RAR, e.g., for Type-2 Random Access Procedure. In one example, the flag (e.g., one-bit flag) is included in MsgB (e.g., fallbackRAR or successRAR), e.g., for Type-2 Random Access Procedure. In one example, the flag (e.g., one-bit flag) is included in the UL Grant of MsgB (e.g., fallbackRAR), e.g., for Type-2 Random Access Procedure. In one example, a special bit pattern of fields in the UL Grant of MsgB (e.g., fallbackRAR), e.g., for Type-2 Random Access Procedure, indicates transmission of SRS. In one example, the flag (e.g., one-bit flag) is included in the DCI scheduling PDSCH of MsgB (e.g., fallbackRAR or successRAR). In one example, a special bit pattern of fields in the DCI scheduling the PDSCH of MsgB (e.g., fallbackRAR or successRAR) indicates transmission of SRS.

[0575] In one example, a UE is indicated by a SRS resource in MsgB (e.g., fallbackRAR or successRAR) to use for SRS transmission. In one example, the UE transmits SRS instead of or in place of PUSCH Msg3. In one example, the UE transmits SRS in addition to PUSCH Msg3, e.g., scheduled by fallbackRAR, (before or after PUSCH Msg3). In one example, the SRS resource is included in MsgB (e.g., fallbackRAR or successRAR), e.g., for Type-2 Random Access Procedure. In one example, the SRS resource is included in the UL Grant of MsgB (e.g., fallbackRAR), e.g., for Type-2 Random Access Procedure. In one example, the SRS resource is included in the DCI scheduling the PDSCH of MsgB (e.g., fallbackRAR or successRAR). In one example, the SRS resource is linked to (associated with) the preamble index. In one example, the SRS resource is linked to (associated with) the PRACH occasion. In one example, the SRS resource is linked to (associated with) the preamble index and the PRACH occasion. In one example, the preambles and / or ROs of MsgA PRACH are portioned into N groups as aforementioned, the UE can determine the SRS resource based on the group of the preamble and / or RO, e.g., based on the antenna switching capability, in one example, one of the groups can be associated with no early SRS transmission. In one example, the SRS resource includes a SRS resource ID and / or SRS resource set ID configured to the UE from a list of SRS resources and / or a list of SRS resource sets configured to the UE, wherein the configuration can be by SIB signaling or by RRC signaling. In one example, the SRS resource includes configuration / scheduling parameters for the SRS, such as time domain resources (e.g., symbol(s) in a slot to use for SRS, time offset from MsgB (e.g., fallbackRAR or successRAR), or time offset within a period, SRS period, etc.), frequency domain resources (e.g., starting RB, number of RBs, frequency hopping pattern, etc.), comb parameters (e.g., comb size, comb offset, cyclic shift, etc.), sequence, sequence hopping (e.g., group hopping, sequence hopping or neither, etc.). In one example, the UL grant of the fallbackRAR includes parameters to schedule the SRS resource. In one example, the successRAR includes an UL grant with parameters to schedule the SRS resource.

[0576] In one example, a UE is indicated by a flag (e.g., one-bit flag) or a special bit pattern in MsgB (e.g., fallbackRAR or successRAR) to transmit SRS and is indicated an SRS resource in MsgB (e.g., fallbackRAR or successRAR). In one example, the UE transmits SRS instead of or in place of PUSCH Msg3, e.g., scheduled by fallbackRAR. In one example, the UE transmits SRS in addition to PUSCH Msg3 (before or after PUSCH Msg3). In one example, the SRS resource includes a SRS resource ID and / or SRS resource set ID configured to the UE from a list of SRS resources and / or a list of SRS resource sets configured to the UE, wherein the configuration can be by SIB signaling or by RRC signaling. In one example, the SRS resource includes configuration / scheduling parameters for the SRS, such as time domain resources (e.g., symbol(s) in a slot to use for SRS, time offset from MsgB (e.g., fallbackRAR or successRAR), or time offset within a period, SRS period, etc.), frequency domain resources (e.g., starting RB, number of RBs, frequency hopping pattern, etc.), comb parameters (e.g., comb size, comb offset, cyclic shift, etc.), sequence, sequence hopping (e.g., group hopping, sequence hopping or neither, etc.). In one example, the UL grant of the fallbackRAR includes parameters to schedule the SRS resource. In one example, the successRAR includes an UL grant with parameters to schedule the SRS resource. The indication of the flag (e.g., one-bit flag) or special pattern and the SRS resource can follow one of the examples of Table 5.

[0577] In one example, the UE determines the early SRS resource or resources to transmit based in the antenna switching capability if known. In one example, the antenna switching capability (e.g., xTyR or whether it is supported or not) is signaled based on a preamble and / or RO index or group of MsgA PRACH and / or signaling in MsgA PUSCH as aforementioned. Examples 1, 3, 7 and 9 of Table 5, can also apply to Msg4, as described herein.

[0578]

[0579] In one example, M SRS resources are configured by system information. In one example, the SRS resource ID (and / or SRS resource set ID) transmitted by a UE is determined based on one or more of the following:

[0580] - Based on a C-RNTI conveyed by the MsgB, e.g. the n least significant bits of the C-RNTI, or the n most significant bits of the C-RNTI, or indicated ID is C-RNTI % N, or indicated ID is ceiling (C-RNTI / N).

[0581] - Based on the C-RNTI (or UE-ID) the UE and the gNB can identify a SRS resource (e.g., SRS resource in a stored context associated with the C-RNTI or the UE-ID).

[0582] - Based on a TC-RNTI used by the random access procedure, e.g. the n least significant bits of the TC-RNTI, or the n most significant bits of the TC-RNTI, or indicated ID is TC-RNTI % N, or indicated ID is ceiling (TC-RNTI / N).

[0583] - Based on a UE-ID indicated in a paging message that triggered the random access procedure associated with the MsgB.

[0584] - Based on the preamble index associated with the random access procedure.

[0585] - Based on the PRACH occasion (RO) associated with the RAR.

[0586] - Based on the preamble index and PRACH occasion (RO) associated with the RAR.

[0587] - Based on the group of the preamble and / or RO of MsgA PRACH associated with the successRAR or fallbackRAR as aforementioned.

[0588] - Based on signaling in MsgB.

[0589] - Based on the antenna switching capability or a default antenna switching capability if antenna switching capability is unknown at the time of early SRS transmission or early SRS triggering.

[0590] - The time and / or frequency resources of a DCI format scheduling a MsgB or of the MsgB.

[0591] - Based on the resource used for HARQ-ACK acknowledgment of MsgB.

[0592] - Based on an information provided by a MAC CE of MsgB (e.g., success RAR or fallback RAR).

[0593] In one example, in case of antenna switching, with multiple SRS resources or SRS resource sets, an SRS resource ID (and / or SRS resource set ID) can be determined by or be linked or mapped to multiple SRS resources or SRS resource sets based on the antenna switching capability, and the corresponding number of SRS resources.

[0594] In one example, the network configures SRS resource(s) or SRS resource set(s) for each preamble-ID. In one example, the network configures SRS resource(s) or SRS resource set(s) for each RO within a frame. In one example, the network configures SRS resource(s) or SRS resource set(s) for each RO within an association period. In one example, the network configures SRS resource(s) or SRS resource set(s) for each RO within an association pattern period. In one example, the network configures SRS resource(s) or SRS resource set(s) for each RO within N frames, wherein N is configured and / or updated RRC and / or MAC CE and L1 control (e.g., DCI format) signaling, or N is specified in the system specifications, e.g., N = 16, or N = 8.

[0595] In one example, the network configures SRS resource(s) or SRS resource set(s) for each preamble-ID-RO pair. Wherein, RO can be:

[0596] - Within a frame.

[0597] - Within an association period.

[0598] - Within an association pattern period.

[0599] - Within N frames, wherein N is configured and / or updated RRC and / or MAC CE and L1 control (e.g., DCI format) signaling, or N is specified in the system specifications, e.g., N = 16, or N = 8.

[0600] In one example, this mapping between the SRS resource ID (and / or SRS resource set ID) and the aforementioned parameters is based on a rule. In one example, this mapping between the SRS resource ID (and / or SRS resource set ID) and the aforementioned parameters is based on a network configuration. In one example, this mapping between the SRS resource ID (and / or SRS resource set ID) and the aforementioned parameters is based on a combination of a rule and network configuration.

[0601] In one example, the SRS resource ID (and / or SRS resource set ID) transmitted by a UE is determined based on one or more of the following:

[0602] - A SRS ID of the M SRS resource IDs (and / or SRS resource set IDs) configured by system information, wherein the SRS resource ID (and / or SRS resource set ID) is included in the DCI Format scheduling the MsgB and / or the MsgB.

[0603] - In a variant, the SRS configuration parameters (or a subset of them) for the SRS resource can be included in the DCI Format scheduling the MsgB and / or the MsgB instead of or in addition to the SRS ID. Wherein the configuration parameters for the SRS resource can be as aforementioned.

[0604] In one example, the SRS resource can be transmitted at or after a time T after the end (or start) of the PDSCH reception providing MsgB or of the PDCCH reception providing the DCI Format scheduling the MsgB associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource can be at or after a time T after the end (or start) or time unit (e.g., slot) of the PDSCH reception providing MsgB or of the PDCCH reception providing the DCI Format scheduling the MsgB associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource is that first slot or subframe or frame that starts at or after a time T after the end (or start) or time unit (e.g., slot) of the PDSCH reception providing MsgB or of the PDCCH reception providing the DCI Format scheduling the MsgB associated with the UE transmitting SRS and optionally based on an offset and a periodicity as illustrated in FIG. 15A (the SRS instances can be one-shot, N-shots or semi-persistent), where SRS trigger can be replaced by the MsgB or the PDCCH reception providing the DCI Format scheduling the MsgB associated with the UE transmitting SRS. Wherein, the time T can be defined in the system specifications and / or configured or updated by network (e.g., using SIB signaling and / or RRC signaling and / or MAC CE signaling and / or L1 control signaling).

[0605] In the aforementioned examples,

[0606] - UE transmits a preamble for a Type-1 random access procedure or a Type-2 random access procedure. In one example, a Type-2 random access procedure includes a PRACH and a PUSCH.

[0607] - In one example, the preambles and / or ROs are partitioned into 2 groups or into groups, wherein the preamble and / or RO group used for the random access procedure can indicate whether or not the UE supports early SRS. In other examples, the preamble and / or RO group used for the random access procedure can indicate an SRS antenna switching capability (xTyR) or the UE doesn't support SRS antenna switching. In other examples, the preamble and / or RO group used for the random access procedure can indicate an SRS antenna switching capability (xTyR).

[0608] - In one example, for Type-2 random access procedure, MsgA PRACH (based on preamble and / or RO group) and / or MsgA PUSCH (based on signaling in MsgA PUSCH) can indicate capability of UE to support early SRS and / or SRS antenna switching capability (xTyR) and / or the UE doesn't support SRS antenna switching.

[0609] - The network responds to the preamble of the Type-1 random access procedure or the Type-2 random access procedure, with a RAR or a success RAR or a fallback RAR.

[0610] --In one example, the RAR or a success RAR or a fallback RAR includes a trigger for SRS,

[0611] --In one example, the RAR or a success RAR or a fallback RAR indicates a resource(s) for SRS, e.g., explicitly or based on preamble ID or RO or TC-RNTI or C-RNTI or antenna switching capability if known, or default antenna switching capability as aforementioned.

[0612] --In one example, the SRS resource(s) is transmitted before Msg3.

[0613] --In one example, the SRS resource(s) is transmitted after Msg3. In a further example, Msg3 can indicate capability of UE to support early SRS and / or SRS antenna switching capability (xTyR) or the UE doesn't support SRS antenna switching, transmission of early SRS and / or early SRS resource(s) can be based on signaling in Msg3,

[0614] --In one example, the SRS resource is transmitted with (or as part of) Msg3.

[0615] --In one example, the SRS resource is transmitted after Msg4.

[0616] --In one example, the SRS resource is transmitted after UE is in connected state.

[0617] - For type 1 random access procedure, the UE transmits Msg3. In one example, Msg3 includes C-RNTI MAC CE or CCCH SDU.

[0618] - In one example, for Type-1 random access procedure, Msg3 (based on preamble and / or RO group) and / or MsgA PUSCH (based on signaling in MsgA PUSCH) can indicate capability of UE to support early SRS and / or SRS antenna switching capability (xTyR) or the UE doesn't support SRS antenna switching.

[0619] - The network responds to the Msg3 of the Type-1 random access procedure with a Msg4

[0620] --In one example, the Msg4 or DCI scheduling Msg4 includes a trigger for SRS,

[0621] --In one example, the Msg4 indicates a resource for SRS, e.g., explicitly or based on preamble ID or RO or TC-RNTI or C-RNTI or antenna switching capability if known, or default antenna switching capability as aforementioned.

[0622] --In one example, the SRS resource is transmitted after UE is in connected state.

[0623] In the aforementioned examples, the early SRS is triggered in Msg2 or Msg4 or MsgB or DCI scheduling Msg2 or Msg4 or MsgB and the transmission of early SRS occurs after Msg5 (e.g., connection setup complete or resume setup complete).

[0624] In one example, the early SRS capability and / or SRS antenna switching capability is indicated in Msg5 (e.g., connection setup complete or resume setup complete). The examples in this disclosure for signaling the early SRS capability and / or SRS antenna switching capability in Msg3 can be extended to Msg5.

[0625] In one example, the early SRS capability and / or SRS antenna switching capability is indicated in a PUCCH and / or PUSCH message the UE transmits after Msg5 (e.g., connection setup complete or resume setup complete).

[0626] In one example, the early SRS capability and / or SRS antenna switching capability is indicated in a PUCCH and / or PUSCH message the UE transmits after UE capability exchange between UE and gNB.

[0627] In one example, the early SRS capability and / or SRS antenna switching capability is determined after network determines UE context associated with the UE triggering the random access procedure for a UE in the INACTIVE state. In one example, the early SRS capability and / or SRS antenna switching capability is determined after Resume Request message (e.g., Msg3) for a UE in the INACTIVE state.

[0628] FIG. 16 illustrates an example procedure 1600 for early SRS triggering for idle mode according to embodiments of the present disclosure. The procedure 1600 of FIG. 16 can be performed by any of the UEs 111-116 of FIG. 1, such as the UE 116 of FIG. 3, and any of the BSs 101-103 of FIG. 1, such as BS 102 of FIG. 2. The procedure 16 is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0629] For idle mode UEs, as illustrated in FIG. 16, the following is a summary of the aforementioned options. The dotted lines in FIG. 16 illustrated possible options for transmitting SRS or for triggering SRS by DCI.

[0630]

[0631]

[0632]

[0633]

[0634] FIG. 17 illustrates an example procedure 1700 for early SRS triggering for an inactive mode according to embodiments of the present disclosure. The procedure 1700 of FIG. 17 can be performed by any of the UEs 111-116 of FIG. 1, such as the UE 116 of FIG. 3, and any of the BSs 101-103 of FIG. 1, such as BS 102 of FIG. 2. The procedure 1700 is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0635] For inactive mode, as illustrated in FIG. 17, UEs the following is a summary of the aforementioned options. The dotted lines in FIG. 17 illustrated possible options for transmitting SRS or for triggering SRS by DCI.

[0636]

[0637]

[0638]

[0639]

[0640] Various embodiments of the present disclosure provide for SRS transmission associated with random access procedure transmissions. In one example, the SRS is transmitted associated with PRACH preamble. In one example, a UE can be configured by system information to transmit SRS associated with or after a PRACH preamble. In one example, a UE can be indicated by a PEI and / or a paging message to transmit SRS associated with or after a PRACH preamble as aforementioned. The SRS transmission can be further conditioned on whether the UE transmits an associated PRACH preamble / RO from a first group of preambles and / or ROs or from a second group of preambles and / or ROs indicated in the system information. The SRS transmission can be further conditioned on whether the UE transmits an associated PRACH preamble / RO from a group of preambles and / or ROs from N groups of preambles and / or ROs indicated in the system information.

[0641] In one example, the SRS resource can be transmitted at or after a time T after the end (or start) of the PRACH transmission associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource can be at or after a time T from the end (or start) or time-unit (e.g. slot) of the PRACH transmission associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource is that first slot or subframe or frame that starts at or after a time T from the end (or start) or time-unit (e.g., slot) of the PRACH transmission associated with the UE transmitting SRS. Wherein, the time T can be defined in the system specifications and / or configured or updated by network (e.g., using SIB signaling and / or RRC signaling and / or MAC CE signaling and / or L1 control signaling). In one example, a PRACH occasion is mapped to a SRS occasion where the UE can transmit SRS. In one example, a one or more PRACH occasions are mapped to a SRS occasion where the UE can transmit SRS. In one example, a PRACH occasion is mapped to one or more SRS occasions where the UE can transmit SRS, for example, one or more preambles of a PRACH occasion are mapped to a SRS occasion.

[0642] In one example, the transmission of SRS associated with PRACH is as illustrated in FIG. 15A (the SRS instances can be one-shot, N-shots or semi-persistent), where SRS trigger can be replaced by PRACH transmission.

[0643] In one example, the SRS is associated with a RACH scheduled transmission or a Msg3. In one example, a UE can be configured by system information to transmit SRS associated with or after a Msg3. In one example, a UE can be indicated by a PEI and / or a paging message to transmit SRS associated with or after a Msg3 as aforementioned. In one example, a UE can be indicated by a RAR to transmit SRS associated with or after a Msg3 as aforementioned. The SRS transmission can be further conditioned on whether the UE transmits an associated PRACH preamble / RO from a first group of preambles and / or ROs or from a second group of preambles and / or ROs indicated in the system information. The SRS transmission can be further conditioned on whether the UE transmits an associated PRACH preamble / RO from a group of preambles and / or ROs from N groups of preambles and / or ROs indicated in the system information. In one example, a UE can indicate in the Msg3 (e.g., by flag) whether or not there is an SRS transmission associated with Msg3. In one example, Msg3 indicates antenna switching capability (xTyR), or not being able to support antenna switching (e.g., for early SRS).

[0644] In one example, the SRS resource can be transmitted at or after a time T after the end (or start) of the PUSCH transmission providing Msg3 associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource can be at or after a time T after the end (or start) or time-unit (e.g., slot) of the Msg3 PUSCH transmission associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource is that first slot or subframe or frame that starts at or after a time T after the end (or start) or time-unit (e.g., slot) of the Msg3 PUSCH transmission associated with the UE transmitting SRS. Wherein, the time T can be defined in the system specifications and / or configured or updated by network (e.g., using SIB signaling and / or RRC signaling and / or MAC CE signaling and / or L1 control signaling).

[0645] In one example, the transmission of SRS associated with Msg3 is as illustrated in FIG.15A (the SRS instances can be one-shot, N-shots or semi-persistent), where SRS trigger can be replaced by PUSCH transmission providing Msg3.

[0646] In one example, the SRS is associated with a MsgA of Type-2 random access procedure. In one example, a UE can be configured by system information to transmit SRS associated with or after a MsgA. In one example, a UE can be indicated by a PEI and / or a paging message to transmit SRS associated with or after a MsgA as aforementioned. The SRS transmission can be further conditioned on whether the UE transmits an associated msgA PRACH preamble / RO from a first group of preambles and / or ROs or from a second group of preambles and / or ROs indicated in the system information. The SRS transmission can be further conditioned on whether the UE transmits an associated MsgA PRACH preamble / RO from a group of preambles and / or ROs from N groups of preambles and / or ROs indicated in the system information. In one example, a UE can indicate in the MsgA PUSCH (e.g., by flag) whether or not there is an SRS transmission associated with MsgA. In one example, MsgA PUSCH indicates antenna switching capability (xTyR), or not being able to support antenna switching (e.g., for early SRS).

[0647] In one example, the SRS resource can be transmitted at or after a time T from the end (or start) of the MsgA (MsgA PRACH or MsgA PUSCH) transmission associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource can be at or after a time T from the end (or start) or time-unit (e.g., slot) of the MsgA (e.g., MsgA PRACH or MsgA PUSCH) transmission associated with the UE transmitting SRS. In one example, the slot or subframe or frame used to transmit SRS resource is that first slot or subframe or frame that starts at or after a time T from the end (or start) or time-unit (e.g., slot) of the MsgA (e.g., MsgA PRACH or MsgA PUSCH) transmission associated with the UE transmitting SRS. Wherein, the time T can be defined in the system specifications and / or configured or updated by network (e.g., using SIB signaling and / or RRC signaling and / or MAC CE signaling and / or L1 control signaling). In one example, a PRACH occasion is mapped to a SRS occasion where the UE can transmit SRS. In one example, a one or more PRACH occasions are mapped to a SRS occasion where the UE can transmit SRS. In one example, a PRACH occasion is mapped to one or more SRS occasions where the UE can transmit SRS, for example, one or more preambles of a PRACH occasion are mapped to a SRS occasion.

[0648] In one example, the transmission of SRS associated with MsgA is as illustrated in FIG.15A (the SRS instances can be one-shot, N-shots or semi-persistent), where SRS trigger can be replaced by MsgA PRACH transmission.

[0649] In one example, the transmission of SRS associated with MsgA is as illustrated in FIG.15A (the SRS instances can be one-shot, N-shots or semi-persistent), where SRS trigger can be replaced by MsgA PUSCH transmission.

[0650] In the aforementioned examples, early SRS triggering, can be replaced by early CSI-RS measurement and / or early CSI reporting, wherein the trigger can be for early measuring of CSI-RS (or SSB) using configured resources (e.g., in SIB1 or in Msg4 or in MsgB) and / or early reporting of CSI on uplink resources (e.g., PUCCH or PUSCH) wherein the UL resources and report configuration are configured by SIB1 or in Msg4 or in MsgB.

[0651] FIG. 18 illustrates an example method 1800 performed by a UE in a wireless communication system according to embodiments of the present disclosure. The method 1800 of FIG. 18 can be performed by any of the UEs 111-116 of FIG. 1, such as the UE 116 of FIG. 3, and a corresponding method can be performed by any of the BSs 101-103 of FIG. 1, such as BS 102 of FIG. 2. The method 1800 is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0652] The method 1800 begins with the UE receiving a SIB (1810). For example, in 1810, the SIB includes N groups of SRS resource sets for antenna switching and the N groups of SRS resource sets correspond to N antenna switching capabilities, respectively. The UE then initiates a Type-1 RA procedure to transition from an idle state to a connected state (1820). The UE then transmits, in msg3 of the RA procedure, information indicating an antenna switching capability from the N antenna switching capabilities supported by the UE (1830). In various embodiments, the LCID / eLCID included in the msg 3 indicates the antenna switching capability supported by the UE.

[0653] The UE then receives, in msg4 of the RA procedure, signaling that triggers transmission of an SRS resource set from the N groups of SRS resource sets (1840). The SRS resource set corresponds to the antenna switching capability. In various embodiments, the msg4 is scheduled by DCI and the msg4 includes a flag indicating triggers for transmission of the SRS resource set. In various embodiments, the antenna switching capability corresponds to xTyR, x is a number of transmit antenna ports, and y is a number of receive antenna ports. In various embodiments, the SRS resource set includes y / x SRS resources and an SRS resource from the SRS resource set includes x antenna ports. In various embodiments, a number of resource sets in a group, of the N groups of SRS resource sets, associated with the antenna switching capability is M and the msg4 includes a field of size that indicates an identity of the SRS resource set. The UE then transmits SRS resources from the SRS resource set (1850). In various embodiments, the SRS resource set is an aperiodic SRS resource set.

[0654] FIG. 19 is a block diagram of a terminal or user equipment (UE) 1900 according to an embodiment of the disclosure. FIG. 19 corresponds to the example of the terminal or UE of FIG. 3.

[0655] The terminal is an electronic device capable of wireless communication and having various form factors, examples of the terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or any other device / system capable of performing wireless communication with a base station (BS) and / or another terminal through a wireless channel.

[0656] Referring to FIG. 19, the UE 1900 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 1901, at least one processor (hereinafter, referred to as simply “processor”) 1902, and at least one memory (hereinafter, referred to as simply “memory”) 1903. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 1901, the processor 1902, and the memory 1903 of the UE 1900 may operate. However, components of the UE 1900 are not limited to the example components illustrated in FIG. 19. In another embodiment, the UE 1900 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 1901, the processor 1902, or the memory 1903 may be integrated in the form of one component.

[0657] The transceiver 1901 may be a communication circuit or communication circuitry that enables the UE 1900 to perform wireless communication with a node or an entity of a network. For example, the transceiver 1901 may enable the UE 1900 to transmit or receive a signal to or from a BS through cellular communication, or to transmit or receive a signal to or from another UE through cellular communication. For example, the transceiver 1901 may support at least one of various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (1901) may include all subsequent generations of evolved wireless communications.

[0658] According to an embodiment, the UE 1900 may include a plurality of transceivers. For example, in the case of supporting evolved-universal terrestrial radio access-new radio (E-UTRA-NR) dual connectivity (EN-DC), the UE 1900 may include a first transceiver supporting the 4G LTE wireless communication and a second transceiver supporting the 5G NR wireless communication. According to another embodiment, in the case of supporting NR-dual connectivity (NR-DC), the UE 1900 may include a plurality of transceivers supporting the 5G NR wireless communication. According to still another embodiment, in the case of supporting near field wireless communication, the UE 1900 may separately include a transceiver supporting at least one standard in the group of wireless communication protocol standards as defined in the protocol standards for Bluetooth®, wireless local area network (WLAN) network (including institute of electrical and electronics engineers (IEEE) 802.11-2016 standard or its amendments, e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, without being limited thereto).

[0659] According to an embodiment, the transceiver 1901 may include various circuit structures used to transmit or receive signals to or from a BS through a wireless channel. The signals may include control information and data. For example, the transceiver 1901 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 1901 may output a signal received through a wireless channel to the processor 1902 and may transmit, through a wireless channel, a signal output from the processor 1902.

[0660] The processor 1902 may control general operations of the UE 1900 according to embodiments of the disclosure. The processor 1902 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 1902 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 1903, individually, collectively or in any combination thereof. Further, the processor 1902 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0661] The processor 1902 may be electrically, operatively, and / or communicatively coupled to the transceiver 1901 to control the transceiver 1901.

[0662] The processor 1902 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. For example, the processor 1902 may include a communication processor (CP) configured to control communication operations and an application processor (AP) configured to control execution of an upper layer (for example, an application layer). In a specific embodiment, at least a part of the processor 1902 may be included in one chip (or IC) and the other part of the processor 1902 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 1901 or the memory 1903.

[0663] The processor 1902 may perform or control or cause an operation of the UE 1900 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 1902 may control operations of the UE 1900 for processing a downlink signal received from a BS or generating and transmitting an uplink signal to a BS. To this end, the processor 1902 may execute a computer program, codes, or instructions stored in the memory 1903, so as to control other components of the UE 1900 to enable execution of various operations.

[0664] The memory 1903 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 1903 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0665] The memory 1903 may be electrically, operatively, and / or communicatively coupled to the processor 1902 and may be accessed by the processor 1902.

[0666] The memory 1903 may store a computer program, codes, or instructions executable by the processor 1902. According to an embodiment, a computer program, codes, or instructions executable by the processor 1902 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 1903, the processor 1902 may perform various functions according to an embodiment of the disclosure.

[0667] According to an embodiment of the disclosure, operations of the UE 1900 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 1903 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0668] FIG. 20 is a block diagram of a base station (BS) 2000 according to an embodiment of the disclosure. FIG. 20 corresponds to the example of the RAN node of FIG. 2.

[0669] The BS 2000 may perform wireless communication with at least one user equipment (UE) located within the area of the BS 2000 through a wireless channel. The BS 2000 may perform communication with a node or an entity of a network through wired or wireless communication.

[0670] Referring to FIG. 20, the BS 2000 may include at least one transceiver (hereinafter, referred to as simply “transceiver”) 2001, at least one processor (hereinafter, referred to as simply “processor”) 2002, and at least one memory (hereinafter, referred to as simply “memory”) 2003. According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the transceiver 2001, the processor 2002, and the memory 2003 of the BS 2000 may operate. However, components of the BS 2000 are not limited to the example components illustrated in FIG. 20. In another embodiment, the BS 2000 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in some embodiments, any combination of the transceiver 2001, the processor 2002, or the memory 2003 may be integrated in the form of one component.

[0671] The transceiver 2001 may be a communication circuit or communication circuitry that enables the BS 2000 to perform wireless communication with a node or an entity of a network. For example, the transceiver 2001 may enable the BS 2000 to transmit or receive a signal to or from the UE X00 through cellular communication, or to transmit or receive a signal to or from another network entity through wireless communication. For example, the transceiver 2001 may support various cellular communication technologies including 3rd generation (3G), 4th generation (4G), long term evolution (LTE), 5th generation (5G) NR, 6th generation (6G), and various cellular wireless communication technologies supported by the transceiver (2001) may include all subsequent generations of evolved wireless communications. According to an embodiment, the transceiver 2001 may include various circuit structures used to transmit or receive signals to or from a UE through a wireless channel. The signals may include control information and data. For example, the transceiver 2001 may include a radio frequency (RF) transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise-amplifying a received signal and down-converting the frequency thereof. The transceiver 2001 may output a signal received through a wireless channel to the processor 2002 and may transmit, through a wireless channel, a signal output from the processor 2002.

[0672] Meanwhile, according to an embodiment of the present disclosure, the BS 2000 may perform communication with a node or an entity of a network through wired or wireless communication. For example, the BS 2000 may perform wired or wireless communication with an adjacent BS, or a node or an entity of a core network through a backhaul network. Although not illustrated in FIG. 20, when the BS 2000 performs wired communication, the BS 2000 may further include a separate network interface for wired communication in addition to the transceiver 2001. The network interface may be referred to as network interface circuitry or communication interface circuitry.

[0673] The processor 2002 may control general operations of the BS 2000 according to embodiments of the disclosure. The processor 2002 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 2002 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 2003, individually, collectively or in any combination thereof. Further, the processor 2002 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme.

[0674] The processor 2002 may be electrically, operatively, and / or communicatively coupled to the transceiver 2001 to control the transceiver 2001.

[0675] The processor 2002 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 2002 may be included in one chip (or IC) and the other part of the processor 2002 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the transceiver 2001 or the memory 2003.

[0676] The processor 2002 may perform or control or cause an operation of the BS 2000 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 2002 may control operations of the BS 2000 for generating and transmitting a downlink signal to a UE or processing an uplink signal received from a UE. Otherwise, the BS 2000 may transmit or receive a signal to or from a neighboring BS, transfer a signal received from a UE to an upper node of the network, or transmit a signal transferred from an upper node of the network to a UE. To this end, the processor 2002 may execute a computer program, codes, or instructions stored in the memory 2003, so as to control other components of the BS 2000 to enable execution of various operations.

[0677] The memory 2003 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 2003 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0678] The memory 2003 may be electrically, operatively, and / or communicatively coupled to the processor 2002 and may be accessed by the processor 2002.

[0679] The memory 2003 may store a computer program, codes, or instructions executable by the processor 2002. According to an embodiment, a computer program, codes, or instructions executable by the processor 2002 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 2003, the processor 2002 may perform various functions according to an embodiment of the disclosure.

[0680] According to an embodiment of the disclosure, operations of the BS 2000 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 2003 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0681] The UE or the base station may perform various communication procedures related to the control plane or the user plane by cooperating with one or more network entities based on wireless communication. For example, the UE may communicate with a network entity (for example, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), rtc.) via the base station, or the base station may perform at least one communication procedure by directly transmitting and receiving signals to / from, or relaying signals between, the network entities.

[0682] The structure of the above-described network entity will be described in more detail with reference to the drawings.

[0683] FIG. 21 is a block diagram of a network entity 2100 according to an embodiment of the disclosure.

[0684] The network entity 2100 may include an entity (apparatus, device, or server, etc.) that performs one or more network functions (NFs) or a part of a network function constituting a core network (e.g., a 5th generation (5G) core (5GC)) in a communication system. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across a plurality of network entities. In addition, when an NF is implemented within the network entity, the NF may be implemented in the form of software, and in such a case, a program for operating the NF may be stored in memory of the network entity 2100.

[0685] A single NF may be implemented by one or more instances, which may be deployed on the same network entity or distributed across multiple network entities to operate. The instance may be a software unit that logically executes a specific network function, and may be implemented in a form that is decoupled from physical hardware resources. Further, one or more NFs may be implemented in the form of one network slice to operate to satisfy specifications required by a particular service.

[0686] The NF may include at least one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), a unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN), etc.

[0687] Referring to FIG. 21, the network entity 2100 may include at least one network interface 2101, at least one processor 2102 (hereinafter, “processor”), and at least one memory 2103 (hereinafter, “memory”). As described above, a NF may be implemented in the form of a physical device such as the network entity 2100, or may be virtualized and executed in the form of an instance. When implemented as an instance, the NF need not necessarily include physical components as illustrated in FIG. 21. In such a case, the instance may be logically represented as comprising one or more logical functional elements.

[0688] According to at least one or a combination of methods corresponding to the embodiments described in the present disclosure, the network interface 2101, the processor 2102, and the memory 2103 of the network entity 2100 may operate. However, components of the network entity 2100 are not limited to the example components illustrated in FIG. 21. In another embodiment, the network entity 2100 may further include additional components in addition to the above-mentioned components, or some components may be omitted. Further, in an embodiment, the network interface 2101, the processor 2102, or the memory 2103 may be integrated in the form of one component.

[0689] The network interface 2101 is a collective term for a transmitter part of the network entity 2100 and a receiver part of the network entity 2100, and may be a communication circuit for transmitting or receiving a signal to or from a user equipment (UE), a base station (BS), or another network entity. Here, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for a wired communication. For example, the network interface 2101 may include a circuit, logic, hardware, etc., configured to exchange a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless communication or wired communication. The network interface 2101 may operate using various protocols (e.g., non-access stratum (NAS) protocol). The network interface 2101 may also be referred to, for convenience of description or depending on implementation, as communication circuitry, network interface circuitry, or a communication interface circuitry.

[0690] The processor 2102 may control general operations of the network entity 2100 according to embodiments of the disclosure. The processor 2102 may be implemented by one or more integrated circuit (or circuitry) (IC) chips and may execute various data processing operations. The processor 2102 may include at least one electric circuit, and may execute instructions (or a program, codes, data, etc.) stored in the memory 2103, individually, collectively or in any combination thereof. Further, the processor 2102 may include a single-core processor or multi-core processor, and may include a processor assembly including a plurality of processing circuits (circuitry) according to a specific implementation scheme. Further, it should be noted that, according to another embodiment, in a case where NF is implemented in the form of an instance, the network function may be not necessarily configured by physical hardware.

[0691] According to an embodiment, the processor 2102 may be electrically, operatively, and / or communicatively coupled to the network interface 2101 to control the network interface 2101.

[0692] The processor 2102 may include at least one processor (or processing circuitry), and the at least one processor may perform the following operations individually, collectively or in any combination thereof. In a specific embodiment, at least a part of the processor 2102 may be included in one chip (or IC) and the other part of the processor 2102 may be included in another chip (or IC). Otherwise, at least one processor may be included in another component, for example, the network interface 2101 or the memory 2103.

[0693] The processor 2102 may perform or control or cause an operation of the network entity 2100 for executing at least one or a combination of methods according to embodiments of the disclosure. For example, the processor 2102 may control operations of the network entity 2100 for exchanging a control plane message or a user plane message with a UE, a BS, or other core network entities through wireless or wired communication, using various protocols (e.g., NAS protocol). To this end, the processor 2102 may execute a computer program, codes, or instructions stored in the memory 2103, so as to control other components of the network entity 2100 to enable execution of various operations.

[0694] The memory 2103 corresponds to a hardware storage device capable of temporarily or permanently storing information and may include one or more storage media. For example, the memory 2103 may include a memory assembly including one or more storage media. For example, the one or more storage media may include permanent memory, such as a hard drive, flash memory, or read-only memory (ROM), semipermanent memory, such as random access memory (RAM), cache memory, or a combination thereof.

[0695] The memory 2103 may be electrically, operatively, and / or communicatively coupled to the processor 2102 and may be accessed by the processor 2102.

[0696] The memory 2103 may store a computer program, codes, or instructions executable by the processor 2102. According to an embodiment, a computer program, codes, or instructions executable by the processor 2102 may be either stored in a single memory device or separated and distributedly stored in two or more memory devices. By executing the instructions stored in the memory 2103, the processor 2102 may perform various functions according to an embodiment of the disclosure.

[0697] According to an embodiment of the disclosure, operations of the network entity 2100 may be caused to be performed based on execution of instructions (or a computer program or codes) stored in the memory 2103 by at least one processor (or processing circuitry) configured to execute the same individually, collectively, or in any combination thereof, based on processing circuitry that is not configured to execute instructions, and / or based on components of processing circuitry that is not configured to execute instructions.

[0698] In one embodiment, a user equipment (UE) is provided. The UE comprises a transceiver configured to receive a system information block (SIB), wherein the SIB includes N groups of sounding reference signal (SRS) resource sets for antenna switching and wherein the N groups of SRS resource sets correspond to N antenna switching capabilities, respectively; and a processor operably coupled to the transceiver, the processor configured to initiate a Type-1 random access (RA) procedure to transition from an idle state to a connected state, wherein the transceiver is further configured to: transmit, in a message 3 (msg3) of the RA procedure, information indicating an antenna switching capability from the N antenna switching capabilities supported by the UE, receive, in a message 4 (msg4) of the RA procedure, signaling that triggers transmission of an SRS resource set from the N groups of SRS resource sets, wherein the SRS resource set corresponds to the antenna switching capability, and transmit SRS resources from the SRS resource set.

[0699] In another embodiment, the antenna switching capability corresponds to xTransmityReceive (xTyR), x is a number of transmit antenna ports, and y is a number of receive antenna ports.

[0700] In another embodiment, the SRS resource set includes y / x SRS resources, and an SRS resource from the SRS resource set includes x antenna ports.

[0701] In another embodiment, the SRS resource set is an aperiodic SRS resource set.

[0702] In another embodiment, a number of resource sets in a group, of the N groups of SRS resource sets, associated with the antenna switching capability is M, and the msg4 includes a field of size that indicates an identity of the SRS resource set.

[0703] In another embodiment, wherein a logical channel identifier (LCID) / extended LCID (eLCID) included in the msg3 indicates the antenna switching capability supported by the UE.

[0704] In another embodiment, the msg4 is scheduled by downlink control information (DCI), and the msg4 includes a flag indicating triggers for transmission of the SRS resource set.

[0705] In one embodiment, a base station (BS) is provided. The BS comprises a processor; and a transceiver operably coupled to the processor, the transceiver configured to: transmit a system information block (SIB), wherein the SIB includes N groups of sounding reference signal (SRS) resource sets for antenna switching and wherein the N groups of SRS resource sets correspond to N antenna switching capabilities, respectively, receive a physical random access channel (PRACH) preamble from a UE for a Type-1 random access (RA) procedure to transition from an idle state to a connected state, receive, in a message 3 (msg3) of the RA procedure, information indicating an antenna switching capability from the N antenna switching capabilities supported by the UE, transmit, in a message 4 (msg4) of the RA procedure, signaling that triggers transmission, from the UE, of an SRS resource set from the N groups of SRS resource sets, wherein the SRS resource set corresponds to the antenna switching capability, and receive SRS resources from the SRS resource set.

[0706] In another embodiment, the antenna switching capability corresponds to xTransmityReceive (xTyR), x is a number of transmit antenna ports at the UE, and y is a number of receive antenna ports at the UE.

[0707] In another embodiment, the SRS resource set includes y / x SRS resources, and an SRS resource from the SRS resource set includes x antenna ports.

[0708] In another embodiment, the SRS resource set is an aperiodic SRS resource set.

[0709] In another embodiment, a number of resource sets in a group, of the N groups of SRS resource sets, associated with the antenna switching capability is M, and the msg4 includes a field of size that indicates an identity of the SRS resource set.

[0710] In another embodiment, a logical channel identifier (LCID) / extended LCID (eLCID) included in the msg3 indicates the antenna switching capability supported by the UE.

[0711] In another embodiment, the msg4 is scheduled by downlink control information (DCI), and the msg4 includes a flag indicating triggers for transmission of the SRS resource set.

[0712] In one embodiment, a method of operating a user equipment (UE) is provided. The method comprises receiving a system information block (SIB), wherein the SIB includes N groups of sounding reference signal (SRS) resource sets for antenna switching and wherein the N groups of SRS resource sets correspond to N antenna switching capabilities, respectively; initiating a Type-1 random access (RA) procedure to transition from an idle state to a connected state; transmitting, in a message 3 (msg3) of the RA procedure, information indicating an antenna switching capability from the N antenna switching capabilities supported by the UE; receiving, in a message 4 (msg4) of the RA procedure, signaling that triggers transmission of an SRS resource set from the N groups of SRS resource sets, wherein the SRS resource set corresponds to the antenna switching capability; and transmitting SRS resources from the SRS resource set.

[0713] In another embodiment, the antenna switching capability corresponds to xTransmityReceive (xTyR), x is a number of transmit antenna ports, y is a number of receive antenna ports, the SRS resource set includes y / x SRS resources, and an SRS resource from the SRS resource set includes x antenna ports.

[0714] In another embodiment, the SRS resource set is an aperiodic SRS resource set.

[0715] In another embodiment, a number of resource sets in a group, of the N groups of SRS resource sets, associated with the antenna switching capability is M, and the msg4 includes a field of size that indicates an identity of the SRS resource set.

[0716] In another embodiment, a logical channel identifier (LCID) / extended LCID (eLCID) included in the msg3 indicates the antenna switching capability supported by the UE.

[0717] In another embodiment, the msg4 is scheduled by downlink control information (DCI), and the msg4 includes a flag indicating triggers for transmission of the SRS resource set.

[0718] Although the figures illustrate different examples of user equipment, various changes may be made to the figures. For example, the user equipment can include any number of each component in any suitable arrangement. In general, the figures do not limit the scope of the present disclosure to any particular configuration(s). Moreover, while figures illustrate operational environments in which various user equipment features disclosed in this patent document can be used, these features can be used in any other suitable system.

[0719] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the descriptions in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claims scope. The scope of patented subject matter is defined by the claims.

[0720] Meanwhile, although specific embodiments of the present disclosure have been described in detail, various modifications may be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims and equivalents thereof.

Claims

A user equipment (UE) comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the UE to:receive a system information block (SIB), wherein the SIB includes N groups of sounding reference signal (SRS) resource sets for antenna switching and wherein the N groups of SRS resource sets correspond to N antenna switching capabilities, respectively,initiate a Type-1 random access (RA) procedure to transition from an idle state to a connected state,transmit, in a message 3 (msg3) of the RA procedure, information indicating an antenna switching capability from the N antenna switching capabilities supported by the UE,receive, in a message 4 (msg4) of the RA procedure, signaling that triggers transmission of an SRS resource set from the N groups of SRS resource sets, wherein the SRS resource set corresponds to the antenna switching capability, andtransmit SRS resources from the SRS resource set.The UE of claim 1, wherein:the antenna switching capability corresponds to xTransmityReceive (xTyR),x is a number of transmit antenna ports, andy is a number of receive antenna ports.The UE of claim 2, wherein:the SRS resource set includes y / x SRS resources, andan SRS resource from the SRS resource set includes x antenna ports.The UE of claim 1, wherein the SRS resource set is an aperiodic SRS resource set.The UE of claim 1, whereina number of resource sets in a group, of the N groups of SRS resource sets, associated with the antenna switching capability is M, andthe msg4 includes a field of sizethat indicates an identity of the SRS resource set.The UE of claim 1, wherein a logical channel identifier (LCID) / extended LCID (eLCID) included in the msg3 indicates the antenna switching capability supported by the UE.The UE of claim 1, wherein:the msg4 is scheduled by downlink control information (DCI), andthe msg4 includes a flag indicating triggers for transmission of the SRS resource set.A base station (BS) comprising:at least one transceiver;at least one processor communicatively coupled to the at least one transceiver; andat least one memory, communicatively coupled to the at least one processor, storing instructions executable by the at least one processor individually or in any combination to cause the base station to:transmit a system information block (SIB), wherein the SIB includes N groups of sounding reference signal (SRS) resource sets for antenna switching and wherein the N groups of SRS resource sets correspond to N antenna switching capabilities, respectively,receive a physical random access channel (PRACH) preamble from a UE for a Type-1 random access (RA) procedure to transition from an idle state to a connected state,receive, in a message 3 (msg3) of the RA procedure, information indicating an antenna switching capability from the N antenna switching capabilities supported by the UE,transmit, in a message 4 (msg4) of the RA procedure, signaling that triggers transmission, from the UE, of an SRS resource set from the N groups of SRS resource sets, wherein the SRS resource set corresponds to the antenna switching capability, andreceive SRS resources from the SRS resource set.The BS of claim 8, wherein:the antenna switching capability corresponds to xTransmityReceive (xTyR),x is a number of transmit antenna ports at the UE, andy is a number of receive antenna ports at the UE.The BS of claim 9, wherein:the SRS resource set includes y / x SRS resources, andan SRS resource from the SRS resource set includes x antenna ports.The BS of claim 8, wherein, the SRS resource set is an aperiodic SRS resource set.The BS of claim 8, whereina number of resource sets in a group, of the N groups of SRS resource sets, associated with the antenna switching capability is M, andthe msg4 includes a field of sizethat indicates an identity of the SRS resource set.The BS of claim 8, wherein a logical channel identifier (LCID) / extended LCID (eLCID) included in the msg3 indicates the antenna switching capability supported by the UE.The UE of claim 8, wherein:the msg4 is scheduled by downlink control information (DCI), andthe msg4 includes a flag indicating triggers for transmission of the SRS resource set.A method of operating a user equipment (UE), the method comprising:receiving a system information block (SIB), wherein the SIB includes N groups of sounding reference signal (SRS) resource sets for antenna switching and wherein the N groups of SRS resource sets correspond to N antenna switching capabilities, respectively;initiating a Type-1 random access (RA) procedure to transition from an idle state to a connected state;transmitting, in a message 3 (msg3) of the RA procedure, information indicating an antenna switching capability from the N antenna switching capabilities supported by the UE;receiving, in a message 4 (msg4) of the RA procedure, signaling that triggers transmission of an SRS resource set from the N groups of SRS resource sets, wherein the SRS resource set corresponds to the antenna switching capability; andtransmitting SRS resources from the SRS resource set.

Images