Device for configuring Wireless Transmit / Receive Unit (WTRU)

Abstract

This disclosure relates to frame structures in NR (Radio Radio). This application describes at least a frame structure in a novel radio. The frame structure includes a self-contained transmission time interval. The transmission time interval includes a control information area containing multiple beams. The interval also includes a downlink transmission channel area containing multiple beams. The frame structure is configured to scan downlink control information over the time interval. The frame structure is also configured to subsequently scan uplink or downlink licensed resources over the time interval. This application also relates to a method for configuring user equipment.

Description

[0001] This application is a divisional application of Chinese patent application 201780067896.7, entitled "Frame Structure in NR", filed on April 30, 2019.

[0002] Cross-reference to related applications

[0003] This application claims priority to U.S. Provisional Application No. 62 / 416,902, filed November 4, 2016, entitled “Reference Signals and Control Channels in NR,” the contents of which are incorporated herein by reference in their entirety. Background Technology

[0004] The control channels for New Radio (NR) for both uplink (UL) and downlink (DL) have a beam-centric architecture. DL control signaling on multiple beams is currently undefined when NR downlink control information (DCI) is pre-coded. A protocol supporting channel estimation for DL ​​control signals is required in NR.

[0005] At high carrier frequencies, phase noise becomes a significant problem. Tracking RS (TRS) helps estimate and compensate for phase noise. Resource allocation for the demodulation reference signal (DMRS) and TRS has not yet been finalized in NR.

[0006] SRS design for UL, especially in beam-centric architectures, has not yet been addressed in NR. A technique is needed to assign SRS resources across multiple beams and multiple digitizations.

[0007] Currently in LTE, Channel State Information Interference Channel Measurement (CSI-ICM) is used to measure the interference power configured in RRC signaling. Interference can be caused by MIMO transmissions or beams from similar or different transmit and receive points (TRPs). As the number of interference sources increases, the number of interference hypotheses grows exponentially. Because each interference hypothesis requires a CSI-ICM resource, this results in significant overhead for DL ​​transmissions. This potentially limits the flexibility of NR nodes in scheduling MU-MIMO. Summary of the Invention

[0008] This summary is provided to introduce some concepts in a simplified form, which will be further described in the detailed description below. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to addressing any or all of the shortcomings mentioned in any part of this disclosure.

[0009] In one aspect of this application, a frame structure in a novel radio is described. The frame structure includes a self-contained transmission time interval. The transmission interval includes a control information region comprising multiple beams, and a downlink transmission channel region comprising multiple beams. Downlink control information is scanned over this time interval. Subsequently, uplink or downlink licensed resources are scanned over this time interval.

[0010] In another aspect of this application, a frame structure for operation in a novel radio is described. The frame structure includes a transmission bandwidth comprising time slots for control and data signaling. Each time slot has a first digit and a second digit. The first digit supports a first subcarrier spacing. The second digit supports a second subcarrier spacing. Additionally, a fixed time slot includes a beam with a probe reference signal.

[0011] In another aspect, a method for configuring user equipment (UEs) is provided. The method includes configuring a set of "K" Channel State Information Interference Channel Measurement (CSI-ICM) and Channel State Information Reference Signal (CSI-RS) resources for a group of UEs. The method further includes the steps of: for one of the UEs in the group, indicating at least "N" of the "K" CSI-ICM resources via interference-based dynamic signaling. The method also includes sending downlink control information including CSI-ICM to the group; and sending CSI-RS (and CSI Interference Channel Measurement) protocols to the UEs. The method further includes receiving feedback from UEs in the group regarding CSI and CSI-ICM for interfering channels. The method even includes scheduling MU-MIMO transmissions for the UEs. The method even includes determining the cancellation of interference transmitted from one UE to other co-scheduled UEs. Therefore, certain embodiments of the invention have been outlined rather extensively to facilitate a better understanding of their detailed description and to facilitate a better understanding of the contribution to the art. Attached Figure Description

[0012] To facilitate a more robust understanding of this application, reference is now made to the accompanying drawings, in which like elements are designated by like reference numerals. These drawings are not to be construed as limiting of this application, but are intended to be illustrative only.

[0013] Figure 1 This is a diagram illustrating the concept of flexible frame structure in NR.

[0014] Figure 2 The first diagram shows control information transmitted on the beam, followed by a diagram of shared channel transmission.

[0015] Figure 3 is a diagram illustrating how some NR-DCI can be repeated on a beam. Figure 3A This is a diagram illustrating the repetition of NR-DCI for the UE across all beams. Figure 3BThe diagram illustrates how the UE transmits NR-DCI to only 2 out of 4 beams.

[0016] Figure 4 This is a diagram showing each beam transmitted via the shared channel following the control area.

[0017] Figure 5 This is a diagram illustrating how control RS or beam RS can be used to estimate the channel.

[0018] Figure 6 This is a diagram illustrating how DMRS is used to decode NR-DCI in a UE-specific manner.

[0019] Figure 7 This diagram illustrates the control DMRS shared between the control and data areas if the control DMRS are precoded in the same way.

[0020] Figure 8 This is a diagram illustrating a beam scanned through the same digital control symbols.

[0021] Figure 9 This is a diagram illustrating the beam scanning through different digital control signals.

[0022] Figure 10 This is a diagram illustrating the subband allocation for the UE to limit the search space used for control signaling.

[0023] Figure 11 This is a diagram illustrating the subband allocation for common control signaling.

[0024] Figure 12 This is a diagram illustrating subband operations for a shared channel.

[0025] Figure 13 This is a diagram illustrating the UL operation of the UE within its assigned subband.

[0026] Figure 14 This diagram illustrates the ability to use OCC to support multiple ports in front-load DM-RS mode.

[0027] Figure 15 This is a diagram showing the DM-RS arrangement in the center symbol of the transmission time.

[0028] Figure 16 This diagram illustrates how DM-RS should be distributed over time for scenarios with higher mobility.

[0029] Figure 17 is a diagram illustrating DM-RS sharing between two subframes for low mobility, high throughput scenarios. Figure 17A The illustration shows sharing between two subframes belonging to the same user. Figure 17BThe illustration shows the sharing of subframes between two different users that are precoded in the same way.

[0030] Figure 18 This is a diagram illustrating how two bundled PRBs that have undergone the same precoding can have different DM-RS modes.

[0031] Figure 19 This is a diagram illustrating the TRS assigned to specific resources on the available bandwidth.

[0032] Figure 20 is a diagram illustrating the tracking RS configured independently for each UE. Figure 20A The diagram shows that no TRS has been assigned. Figure 20B The diagram illustrates the multiple resources allocated to TRS in terms of frequency. Figure 20C The diagram illustrates a higher density of TRS assigned in time.

[0033] Figure 21 This is a diagram illustrating subband support with different digital codes and the corresponding NR-SRS resources.

[0034] Figure 22 This is a diagram illustrating the fixed digital representation of NR-SRS resources.

[0035] Figure 23 This is a diagram illustrating NR-SRS that uses reserved resources to send signals using different digital signals during a duration T.

[0036] Figure 24 This is a diagram illustrating NR-SRS in different beams.

[0037] Figure 25 This is a diagram illustrating antenna virtualization and port mapping.

[0038] Figure 26 This is a diagram illustrating the NR-SRS transmission port mapping.

[0039] Figure 27 This is a diagram illustrating the NR SRS beam scan block and bursts.

[0040] Figure 28 This is a diagram illustrating an example of the CSI-ICM configuration process.

[0041] Figure 29 This is a diagram illustrating an 8-bit CSI-RS measurement activation / deactivation MAC control element.

[0042] Figure 30 This is a diagram illustrating the activation / deactivation of the MAC control element for k (k=4) octet CSI-RS measurements.

[0043] Figure 31This is a diagram illustrating the scheduling of one or more NR-PUSCHs for CSI measurement reports.

[0044] Figure 32 This is a diagram illustrating the scheduling of one NR-PUSCH and / or several NR-PUCCHs for a CSI measurement report.

[0045] Figure 33 This is a diagram illustrating the scheduling of several NR-PUCCHs for CSI measurement reports.

[0046] Figure 34 This is a diagram illustrating the scheduling of several NR-PUCCHs for CSI measurement reports.

[0047] Figure 35 This is an illustration of a graphical user interface of one embodiment.

[0048] Figure 36A An embodiment of an example communication system is illustrated, in which the methods and apparatus described and claimed herein may be implemented.

[0049] Figure 36B This is a block diagram of an example apparatus or device configured for wireless communication according to embodiments shown herein.

[0050] Figure 36C This is a system diagram of the RAN and core network according to an embodiment.

[0051] Figure 36D This is a system diagram of the RAN and core network according to another embodiment.

[0052] Figure 36E This is a system diagram of the RAN and core network according to yet another embodiment.

[0053] Figure 36F This is a block diagram of an exemplary computing system in which implementations can be performed. Figure 36A , Figure 36C , Figure 36D and Figure 36E One or more devices of the communication network shown. Detailed Implementation

[0054] A detailed description of illustrative embodiments will be discussed with reference to the various figures, examples, and aspects herein. While this description provides detailed examples of possible implementations, it should be understood that the details are intended to be illustrative and therefore do not limit the scope of this application.

[0055] References to "an embodiment," "an embodiment," "one or more embodiments," "aspects," etc., in this specification mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment of this disclosure. Furthermore, the term "embodiment" throughout the specification does not necessarily refer to the same embodiment. That is, various features that may be presented by some embodiments but not by others are described.

[0056] Generally, this application relates to methods and systems for reference signal design and control channel design for NR systems. Enhancements related to the design of reference signals and control channels for NR can be employed to meet the requirements of NR systems. This application also addresses mechanisms for control channel design, including techniques for allocating resources for NR-DCI and waveforms for UL signaling. Mechanisms for assisting control channel estimation and the allocation of UL and DL resources within subbands can limit the computational burden on the UE.

[0057] Another aspect of this application addresses a mechanism for reference signal design. It employs a solution designed for NR using DMRS and TRS. The mechanism can support resource allocation and cell / beamwidth RS allocation, as well as UE-specific RS allocation.

[0058] Describe the resource allocation for NR-SRS across multiple beams and multiple digitizers. Precoded SRS can be supported. Describe the mechanism for CSI-based measurements. The following methods can enable CSI ICM and make it more efficient: (i) new RRC signaling that informs the UE of the necessary configuration information, such as RS location and codebook information; (ii) a CSI-ICM resource set, where CSI-ICM resources within the set can be dynamically shared among UEs. Two-step CSI-ICM configuration to support CSI-ICM and reduce latency. Step 1 pre-configures a set of K CSI-ICM resources for all UEs via RRC signaling. In Step 2, for a given UE, N (N>=1) CSI-ICM resources are dynamically indicated from a total of K CSI-ICM resources based on interference assumptions to enable CSI-ICM measurements via dynamic signaling via DCI or via MAC CE.

[0059] According to another embodiment, group-based CSI-ICM configuration via DCI enables multiple UEs to measure interfering channels. UEs can be grouped by experiencing the same interference assumptions. According to yet another embodiment, a new NR PUCCH format supporting CSI-ICM reporting is envisioned. In yet another embodiment, a new NR DCI design is envisioned to achieve UE interference cancellation for MU-MIMO. In yet another embodiment, a process for interfering channel measurement and interference cancellation for NR MU-MIMO is described.

[0060] According to another aspect, a mechanism for dynamic CSI-RS resource allocation is described. Two methods for RRC-based configuration of CSI-RS pooled resources are envisioned. In the first technique, a UE-specific CSI-RS resource configuration is used without configuring a group of UEs sharing the same CSI-RS resource pool. In the second technique, a UE-specific CSI-RS resource configuration is used together with the configuration of a group of UEs sharing the same CSI-RS resource pool.

[0061] Describes several signaling designs for dynamically indicating CSI-RS resources and reporting for UEs: (i) CSI measurement commands signaled in the MAC CE; and (ii) CSI measurement commands signaled in the DCI, including: (a) CSI measurement commands piggybacked on the DCI; (b) independent CSI measurement commands for a specific UE (sent on a separate DCI); and (c) group-based DCIs to schedule CSI-RS measurements and feedback for multiple UEs.

[0062] The mechanisms discussed in this article can be implemented at an NR-Node, Transmit and Receive Point (TRP), or Remote Radio Head (RRH). Therefore, even though NR-Node is used in most exemplary descriptions or illustrations, it is assumed that NR-Node, TRP, and RRH are interchangeable.

[0063] The time interval, including DL and / or UL transmissions, is flexible for different digital and RAN slices and can be configured statically or semi-statically. The time interval structure can be used for slots or mini-slots within a subframe. Even though the exemplary descriptions and / or illustrative diagrams use slots or mini-slots, the mechanisms used for this time interval structure can be applied to slots and / or mini-slots.

[0064] Abbreviations

[0065] The following abbreviations are used for the following terms and phrases:

[0066] Augmented Reality (AR)

[0067] AS Access Layer

[0068] BF-RS Beamforming Reference Signal

[0069] BT-RS beamforming training reference signal

[0070] CE control elements

[0071] CoMP coordinates multiple points

[0072] CP loop prefix

[0073] CQI Channel Quality Indicator

[0074] CRS cell-specific reference signal

[0075] CSI Channel Status Information

[0076] CSI-RS Channel State Information Reference Signal

[0077] CSI-ICM Channel State Information - Interference Channel Measurement

[0078] DCI downlink control information

[0079] DL downlink

[0080] DM-RS demodulation reference signal

[0081] eMBB Enhanced Mobile Broadband

[0082] eNB evolution node B

[0083] ePDCCH Enhanced Physical Downlink Control Channel

[0084] FD full dimensions

[0085] FDD Frequency Division Duplex

[0086] FFS for further research

[0087] GUI (Graphical User Interface)

[0088] HARQ Hybrid Automatic Repeat Request

[0089] ID identifier

[0090] IMT International Mobile Telecom

[0091] KPKronecker

[0092] KPIs (Key Performance Indicators)

[0093] LTE Long Term Evolution

[0094] MAC Media Access Control

[0095] MCL maximum coupling loss

[0096] MCS modulation and coding scheme

[0097] MME Mobility Management Entity

[0098] MIMO (Multiple Input Multiple Output)

[0099] NAS Non-Access Layer

[0100] NB narrow beam

[0101] New NDI data indicators

[0102] NEO Network Operations

[0103] NR-Node New Radio Node

[0104] OCC Orthogonal Cover Code

[0105] OFDM (Orthogonal Frequency Division Multiplexing)

[0106] PDCCH Physical Downlink Control Channel

[0107] PDSCH Physical Downlink Shared Channel

[0108] PMI precoder matrix indication

[0109] PRS positioning reference signal

[0110] PUSCH Physical Uplink Shared Channel

[0111] PUCCH (Physical Uplink Control Channel)

[0112] RAT radio access technology

[0113] RB resource blocks

[0114] RE Resource Elements

[0115] RI rank indication

[0116] RRC Radio Resource Control

[0117] RRH Remote Radio Header

[0118] RS reference signal

[0119] RSSI Received Signal Strength Indicator

[0120] RSRP reference signal received power

[0121] RSRQ reference signal reception quality

[0122] RV Redundant Version

[0123] SC-FDMA Single-Carrier Frequency Division Multiple Access

[0124] SI System Information

[0125] SIB System Information Block

[0126] SISO Single Input and Single Output

[0127] SRS detection reference signal

[0128] 2D

[0129] 3D

[0130] TDD Time Division Duplex

[0131] TPC transmit power control

[0132] TRP Transmit and Receive Points

[0133] TRS Tracking Reference Signal

[0134] TTI Transmission Time Interval

[0135] TXSS sends sector scan

[0136] UAV drones

[0137] UE User Equipment

[0138] UL uplink

[0139] URLLC ultra-reliable and low latency communication

[0140] VR Virtual Reality

[0141] WB wide beam

[0142] WRC Wireless Planning Coordination

[0143] Reference signal in LTE

[0144] DL Reference Signal (RS) is a predefined signal that occupies a specific resource element (RE) within the downlink time-frequency RE grid. The LTE specification includes several types of DL RS transmitted in different ways for different purposes [E. Dahlman, S. Parkvall, J. Skold, “4G LTE / LTE-Advanced for Mobile Broadband”, 2nd edition, 2014].

[0145] Cell-specific reference signal (CRS): CRS: (1) Channel estimation by the user equipment (UE) for coherent demodulation of the DL physical channel; and (2) Channel state information (CSI) by the UE; and (3) Measurement by the UE for cell selection and handover.

[0146] Demodulation Reference Signal (DM-RS): The DM-RS is referred to as the UE-specific reference signal and (1) is used for channel estimation by a particular UE and is transmitted only within an RB specifically assigned for PDSCH / ePDCCH transmission to that UE, and (2) is associated with the data signal and precoded before transmission using the same precoder as the data.

[0147] Channel State Information Reference Signal (CSI-RS): CSI-RS is intended for use by the UE to obtain CSI for channel-related scheduling, link adaptation, and multi-antenna transmission.

[0148] Uplink reference signal

[0149] Similar to LTE DL, reference signals are also used in LTE UL. Two types of reference signals are defined for LTE UL [“4G LTE / LTE-Advanced for Mobile Broadband”].

[0150] UL Demodulation Reference Signal (DM-RS): The DM-RS is used by the base station for channel estimation in order to perform coherent demodulation of the Physical Uplink Shared Channel (PUSCH) and Physical Uplink Control Channel (PUCCH). The DM-RS is transmitted only within the RBs specifically assigned for PUSCH / PUCCH transmission and spans the same frequency range as the corresponding physical channels.

[0151] UL Sounding Reference Signal (SRS): The SRS is used by the base station for CSI estimation to support uplink channel-dependent scheduling and link adaptation. In the case of channel reciprocity, the SRS is also used by the base station to obtain CSI estimates for the DL.

[0152] CSI feedback in LTE

[0153] DL channel-dependent scheduling is a key feature of LTE, which selects DL transmission configurations and related parameters based on instantaneous DL channel conditions, including interference. To support DL channel-dependent scheduling, the UE provides the CSI (Content Specific Information) to the evolved Node B (eNB). The eNB uses this information for its scheduling decisions.

[0154] CSI consists of one or more messages [“4G LTE / LTE-Advanced for MobileBroadband”], including:

[0155] Rank Indication (RI): Provides a recommendation on the transmission rank to be used, or the number of preferred layers that should be used for PDSCH transmissions to the UE.

[0156] Precoder Matrix Indication (PMI): Indicates the preferred precoder for PDSCH transmission.

[0157] Channel Quality Indicator (CQI): Indicates the highest modulation and coding scheme to achieve a block error probability of up to 10%.

[0158] The combination of RI, PMI, and CQI forms the CSI feedback report sent to the eNB. The content included in the CSI report depends on the reporting mode configured by the UE. For example, unless the UE is in spatial multiplexing multi-antenna transmission mode, RI and PMI do not need to be reported.

[0159] Downlink control information

[0160] Downlink Control Information (DCI) is a predefined format formed and transmitted in the Physical Downlink Control Channel (PDCCH). The DCI format informs the UE how to obtain the data it transmits on the Physical Downlink Shared Channel (PDSCH) in the same subframe. It carries UE-specific details such as the number of resource blocks, resource allocation type, modulation scheme, redundancy version, coding rate, etc., which help the UE locate and decode the PDSCH from the resource grid. Various DCI formats are used in LTE within the PDCCH.

[0161] New Radio (NR) Frame Structure

[0162] Currently, 3GPP standardization work is underway to define the NR frame structure. The consensus is to establish so-called "self-contained" time intervals for NR. For example... Figure 1 As shown, a self-contained time interval is understood to include all control information, data and acknowledgments (i.e., ACK / NACK) for licensing within the time interval, and is expected to have configurable UL / DL / sidelink allocation and reference signals within its resources [3GPP R1-164694 Frame Structure Requirements, Qualcomm, May 2016].

[0163] New radio requirements

[0164] 3GPP TR 38.913 [3GPP TR 38.913 Study on Scenarios and Requirements for Next Generation Access Technologies; (Version 14), V0.2.0] defines the scenarios and requirements for new radio (NR) technologies. Key performance indicators (KPIs) for eMBB, URLLC, and mMTC devices are summarized in Table 1 below.

[0165]

[0166] Table 1

[0167] Reference signal definition for NR

[0168] The following consensus has been reached at the 3GPP RAN1 #86bis meeting regarding downlink-supported NR reference signals (RS):

[0169] CSI-RS: A reference signal with the main functions of CSI acquisition and beam management.

[0170] FFS: RRM Measurement

[0171] DM-RS: A reference signal that performs primary functions of data and control demodulation.

[0172] FFS: Channel State Information Estimation and Interference Estimation

[0173] FFS: Beam Management

[0174] Reference signal for phase tracking

[0175] FFS: Can DM-RS extensions be applied?

[0176] FFS: Can a new RS or RS be used for other functions?

[0177] Reference signal for time / frequency tracking

[0178] FFS: Can a new RS or RS be used for other functions?

[0179] Reference signal for radio link monitoring

[0180] FFS: Can a new RS or RS be used for other functions?

[0181] RS for RRM measurement

[0182] FFS: Can a new RS or RS be used for other functions?

[0183] For NR uplink, at least the following RSs must be supported:

[0184] SRS: Reference signal with primary functions including CSI acquisition and beam management.

[0185] FFS: RRM Measurement

[0186] DM-RS: A reference signal that performs primary functions of data and control demodulation.

[0187] FFS: Beam Management

[0188] Reference signal for phase tracking

[0189] FFS: Can DM-RS extensions be applied?

[0190] FFS: Can a new RS or RS be used for other functions?

[0191] FFS: Reference signal used for RRM measurement

[0192] FFS: Can a new RS or RS be used for other functions?

[0193] CSI feedback in LTE

[0194] DL channel-dependent scheduling is a key feature of LTE, which selects DL transmission configurations and related parameters based on instantaneous DL channel conditions, including interference. To support DL channel-dependent scheduling, the UE provides the CSI (Content Specific Information) to the evolved Node B (eNB). The eNB uses this information for its scheduling decisions.

[0195] CSI consists of one or more pieces of information: (i) Rank Indicator (RI); (ii) Precoder Matrix Indicator (PMI); and (iii) Channel Quality Indicator (CQI). The combination of RI, PMI, and CQI forms the CSI feedback report to the eNB. The content included in the CSI report depends on the reporting mode configured for the UE. CSI reporting can be configured to be periodic or aperiodic via RRC signaling.

[0196] Non-periodic CSI reports using PUSCH

[0197] Aperiodic reporting is triggered by the DCI format and can be used to provide more detailed reports via the PUSCH. The UE is semi-statically configured by a higher layer to feed back CQI and PMI, along with the corresponding RI, on the same PUSCH using one of the following CSI reporting modes given in Table 1 below. In subframe n, CSI requests can be sent in DCI formats 0 and 4, which are scheduled to carry the PUSCH transmission of the aperiodic CSI report in subframe n+k.

[0198]

[0199] Table 2

[0200] For each transmission mode in Table 2 above, different reporting modes are defined and supported on PUSCH.

[0201] Use PUCCH for periodic CSI reporting

[0202] For periodic CSI reporting, the UE is semi-statically configured by higher layers to periodically report different CSI components (CQI, PMI, and / or RI) on the PUCCH using the reporting patterns given in Table 3. Periodic CSI reporting is configured by higher-layer signaling (RRC).

[0203]

[0204] Table 3

[0205] For each transmission mode defined in Table 3 above, different periodic CSI reporting modes are defined and supported on the PUCCH.

[0206] Mechanisms for control channel design

[0207] According to one aspect of this application, an architecture and technology for DL ​​and UL control signals for NR are provided. This document describes solutions for resource allocation and reference signal design for NR-DCI.

[0208] In one embodiment, NR-DCI resource allocation in a beam-centric architecture is described. Here, 3GPP specifications can support NR-DCI transmission across multiple beams to improve coverage and reliability. It should be noted that LTE only supports PDCCH broadcasting. Beams can scan through different spatial locations carrying NR-DCI, such as... Figure 2 As shown in the image.

[0209] In this proposal, a beam carrying control information scans through the space before UL / DL-licensed resources become available, such as Figure 2 As shown in the diagram, DL permission is available N symbols after the control signaling. The advantage of this scheme is reduced latency when decoding critical control signaling related to paging, RACH, etc.

[0210] If the UE's location is known prior to the signal, then its UE-specific NR-DCI can be transmitted only within a subset of the beam. If the NR-Node does not know the UE's location, then its NR-DCI can be transmitted in every beam. This concept is... Figure 3A and 3B The diagram shows that the control area is covered by four beam scans, each covering a symbol of the beam. Figure 3A Repeat the UE-specific NR-DCI in all beams, but in Figure 3B It is transmitted only in beam 1 and beam 2. NR-DCI can be located in different subcarriers in different beams.

[0211] Similarly, NR-DCI for common control signaling can be carried in each beam. The common control search space uses the same subcarriers in all beams carrying control information—minimizing the overhead of different common control signaling resources for each beam.

[0212] In another embodiment, each beam may carry multiple symbols, including control and data, such as Figure 4 As shown, NR-DCI within a beam can allocate resources for UL and / or DL ​​licenses within the same beam. The advantage of this approach is minimal latency between control and data transmission. Generally, for the above approach, control and data transmission can occur in different beams. For example, the beam used for control signaling can be wider than the beam used for data signaling.

[0213] According to another embodiment, a solution for RS design for NR is proposed. Certain types of NR-DCI, such as common control signals, can be transmitted for beamwidth reception. NR-DCI can fully utilize beam RS designed for beam identification, beam measurement, and channel estimation.

[0214] If NR-DCI is transmitted through multiple ports (as in transmit diversity), a new form of “control RS” with appropriate density can be introduced to assist in channel estimation for NR-DCI. This control RS will be transmitted for each port supported by the NR-DCI transmission. The control RS can be cell / beam specific, and its location and resources can depend on one or more of the following: (i) cell ID; and (ii) beam ID.

[0215] Control RS can be transmitted to cover channel estimation for the entire frequency range used for DCI symbols, or control RS can be transmitted over a limited area of ​​frequency mapping for DCI transmitted using these ports.

[0216] Figure 5 The diagram illustrates the beam RS and control RS ports. Control RSs can be defined for more than one port. Resources for multiple ports can be defined using orthogonal coverage codes (OCCs) similar to those used for DMRS ports in LTE.

[0217] Certain types of NR-DCI, especially UE-specific signals, can be pre-coded to improve spatial separation and coverage. For such use cases, a "control DMRS" can be introduced to aid in channel estimation.

[0218] Figure 6The diagram illustrates a UE-specific approach to decoding NR-DCI using control DMRS. NR-DCI can be transmitted on multiple ports (transmit diversity or beamforming), and correspondingly, the control DMRS will be pre-coded similarly to the pre-coded NR-DCI and will be supported on the port used for data transmission. If data and control are transmitted on the same beam, they can share control RS or control DMRS resources.

[0219] Figure 7 The diagram illustrates the control DMRS shared between the control and data areas if they are precoded in the same manner. The beam RS, control RS, and control DMRS can be located adjacent to the control area to provide high control channel reliability.

[0220] According to yet another embodiment, NR-DCI can use a fixed number of control signals or a fixed duration for control signaling in each transmission interval. This can be a time slot, a mini-time slot, or a subframe. For such a design, NR does not need to transmit a channel similar to PCFICH because the control signaling resources are fixed. The control signaling resources can be indicated by key system information such as MIB or SIB1 / SIB2, or can be set to fixed values ​​in the specification.

[0221] Figure 8 An example is shown where the number of control signals is the same in each transmission interval. Figure 9 An example is shown where the duration of control signaling is the same for all digits multiplexed in FDM / TDM within a resource grid. Therefore, a transmission interval using a 60kHz subcarrier spacing uses 4 symbols for control signaling, while a transmission interval operating at 15kHz uses 1 symbol for control signaling within that transmission interval. This solution ensures that the beam scans the same time period in each direction.

[0222] Alternatively, the specification may specify the number of symbols for each digitization. The number of symbols may depend on one or more of the following: (i) the center frequency; (ii) the bandwidth; and (iii) the number of supported beams.

[0223] According to another embodiment, NR supports large bandwidths exceeding 80MHz. If the UE is required to blindly decode NR-DCI across the entire bandwidth, it will experience significant latency and battery consumption. Therefore, NR must allow NR-DCI to be transmitted to the UE in specific subbands. The UE must be configured to be aware of the resources of these subbands.

[0224] UE-specific NR-DCI can be indicated within a limited number of resources (subbands) known a priori at the UE. Subbands can be configured semi-statically via RRC and MAC CE updates. Figure 10An example of carrying NR-DCI in a UE-specific subband is shown. Subbands can be allocated based on UE capabilities; that is, the UE can inform the network of the maximum bandwidth it can handle at a time. It is important to note that the subbands allocated to the UE do not need to be frequency-contiguous.

[0225] The search space used for common control signaling can carry NR-DCI, such as NR-DCI for paging, RACH response, etc., which is limited to specific subbands so that the UE does not have to blindly decode all resources in the common control signaling search space.

[0226] The common control signaling search space can be divided into multiple search spaces, and the UE can be assigned to search for common NR-DCI only in subsets of those search spaces. Figure 11 An example is shown where the public signaling search space is divided into four search spaces and the UE is configured to search its public NR-DCI only in two of those search spaces.

[0227] Similar to the solution described above for UE-specific and public NR-DCI subband operation, the physical DL shared channel (NR-PDSCH) carrying data can also be limited to a subband. This limits the number of times the UE's front end must retune to a new frequency for reception. The NR-PDSCH subband can be semi-statically configured via RRC and MAC CE updates. Figure 12 An example of NR-PDSCH for a UE being transmitted via a pre-configured subband is shown; thus, the UE is tuned to perform data reception only within the frequency range covering the subband.

[0228] According to another embodiment, the UE can be configured to transmit within a subband instead of across the entire bandwidth to limit the amount of data processed by the front-end and receiver. Thus, UL resources will be constrained to the subband. The subband can be pre-configured semi-statically via RRC or MAC CE updates, or dynamically specified via UL licensing.

[0229] Figure 13 An example of resource allocation for UL transmissions of CP-OFDM or DFTS-OFDM within a subband is shown. Here, one or more subbands are allocated to the UE, within which the UE is provided with its UL license. Similarly, for UL unlicensed transmissions, a subband of a frequency can be indicated to the UE to transmit its unlicensed signal. When using resource hopping, the UE can transmit within one or more subbands, and the hopping resources do not necessarily occupy the entire bandwidth.

[0230] In this embodiment, the waveform (CP-OFDM or DFT-S-OFDM) is assumed to be assigned to the UE by the network. Here, the NR-Node makes the decision about which waveform to use for the UE. The NR-Node can determine the UE's waveform based on feedback from the UE (such as beam or cell measurements or CQI) or feedback from SRS or other RS ​​on the UL. Waveform configuration can be accomplished as follows:

[0231] 1. Dynamically via DL control signaling (DCI / PDCCH) (DCI can support multiple waveform formats that can be explicitly indicated, or DCI can perform blind decoding for any possibility of the waveform); and

[0232] 2. Semi-static via RRC and MAC CE

[0233] Mechanisms for reference signal design

[0234] According to another aspect of this application, it is envisioned that supporting a wide range of user mobility scenarios with low latency in NR can enhance reference signaling in DL NR. The DM-RS location within a time slot / mini-time slot or subframe should be flexible and adaptable to scenario-specific performance requirements. For example, Figure 2 This demonstrates that DM-RS can be front-loaded, offering dual advantages. First, the proximity of the DM-RS to the control data allows for accurate channel estimation at the control data resource, resulting in accurate demodulation / decoding of the control data. Second, the earlier delivery of the DM-RS minimizes latency in demodulation / decoding by delivering the channel estimate earlier. These two advantages make it well-suited for URLL use cases.

[0235] Figure 14 This demonstrates support for two ports via OCC. Generally, support for Layer N can be implemented through appropriate code. Figure 3 to... Figure 5 Three examples of recommended placement for DM-RS are further shown. Figure 15 This demonstrates that the DM-RS can be placed in the middle of the transmission interval, resulting in more accurate channel estimation over the entire duration of the interval compared to having a preceding DM-RS. Although the latency for decoding control information is higher, mMTC and eMBB can tolerate this latency.

[0236] Figure 16 The diagram illustrates a DMRS allocated at a high density within the transmission interval. For example, in high Doppler scenarios, DMRS can be allocated across multiple symbols that spread over time to achieve accurate channel estimation.

[0237] For scenarios with low UE mobility, the DM-RS can be placed at the end of mini-slot "i" and used to provide channel estimation to subframes "i" and "i+1". Similarly, the DM-RS can be shared among multiple UEs. For UE 1 and UE 2, which have subsequent RBs in the same frequency band, the DM-RS can be placed at the end of subframe "1" and used to provide channel estimation to the two subframes belonging to different users. Figure 17 illustrates the scenario mentioned above.

[0238] In Figure 17, for low mobility, high throughput scenarios, DM-RS is shared between two subframes: (a) sharing between two subframes of the same user; and (b) sharing between subframes of two different users that are precoded in the same way.

[0239] NR can support PRB bundling and allows for flexible placement of DMRS resources within the bundled PRB. Figure 18 In this context, two bundled PRBs with different DM-RS modes undergo the same precoding. PRB1 can allocate DMRS in a manner where DMRS can be shared with adjacent UEs. PRB2, on the other hand, can have a lower DMRS allocation density.

[0240] DM-RS resource assignment can be either dynamic or semi-static. Dynamic signaling can be accomplished via DCI. The specification can define a list of possible DM-RS modes (locations and sequences), one of which can be assigned to the UE. The assigned resource can be indicated by an index in the list. When using semi-static signaling, RRC or MAC CE updates will indicate the DM-RS configuration. It is envisioned that DM-RS will generally have the same numeric characteristics as the data.

[0241] In this embodiment, a tracking reference signal (TRS) for phase tracking in an NR is described. Here, phase noise increases with increasing carrier frequency, making it a significant problem to be addressed in NRs. The following solution addresses phase tracking in NRs.

[0242] TRS is not sent continuously. Tracking RS is only sent when needed, not all the time. This is important to avoid the costly transmission overhead associated with TRS. One or more of the following factors will influence the choice to turn TRS on or off:

[0243] Modulation order: When data is modulated at a higher order, the absence of phase tracking RS will have a more detrimental effect on BLER.

[0244] Carrier frequency: Increasing the carrier frequency will require enabling the tracking RS.

[0245] UE speed: Increasing UE speed will increase Doppler, implying that tracking RS needs to be enabled.

[0246] Subcarrier spacing: Increasing the subcarrier spacing will increase the system’s inherent immunity to carrier frequency offset, thereby reducing the need for tracking RS.

[0247] The Tracking System (TRS) can be UE-specific or cell-specific. The on / off signaling used to track the RS can be accomplished via different signaling depending on whether it is UE-specific or cell-specific. If it is UE-specific, it can be configured via RRC signaling and updated to be on / off via RRC signaling / MAC CE or dynamically on / off via DCI. If the TRS is cell / beamwidth, system information can be used to signal its presence and resources.

[0248] Figure 19 The cell / beamwidth scenario is illustrated, where the specific location of TRS resources within the grid is assigned. Sufficient TRS resources can be reserved so that UEs that can operate only in certain subbands of the available spectrum can access TRS. Figure 20 illustrates a UE-specific scenario where each UE can be assigned TRS resources based on its SNR, modulation, digitization, etc.

[0249] In the case of a UE-specific TRS, the tracking RS can be precoded. Furthermore, the location and sequence of the tracking RS can depend on one or more of the beam ID, cell ID, and UE-specific resources, such as, for example, the root / shift of the sequence assigned to the UE or the location of DL resources for the UE.

[0250] In the case of cell / beamwidth TRS, TRS is transmitted across all UE-known resources. TRS can be a function of one or more of the following: (a) cell ID; and (b) beam ID. TRS transmission can be configured on one or more ports. In some cases, tracking phase by transmitting TRS on a single port may be sufficient. Therefore, TRS on a single port can be supported by default. However, the NR must also support more ports for TRS. Resources for ports can be configured via DCI or RRC signaling for cell / beamwidth and UE-specific use cases.

[0251] According to yet another embodiment, an NR probe reference signal (NR-SRS) over UL is described. Since the NR will support different digitizations, NR-SRS digitizations and resources must be allocated in a manner compatible with all supported data and control signal digitizations and TDM / FDM multiplexing for multiple users. When multiple digitizations are supported simultaneously in a carrier, the following solutions can handle the NR-SRS signaling aspects. NR-SRS resource signaling can fall into one of the categories described below, where the NR node can allocate any of the following resources for NR-SRS transmission:

[0252] 1. Certain OFDM symbols or portions of OFDM symbols can be reserved in a cell-width or beamwidth manner to transmit NR-SRS in each supported digitization. Figure 21 In this architecture, the network divides the transmission bandwidth (BW) into two digits. Digit 1 supports a 15kHz subcarrier spacing, and digit 2 supports a 60kHz subcarrier spacing. Within the bandwidth assigned to each digit, NR-SRS transmission will have the same digit.

[0253] 2. Certain OFDM symbols or portions of OFDM symbols may be preserved in reference numerals in the form of cell width or beamwidth, which may be associated with the carrier frequency or indicated by system information. This concept is... Figure 22 As shown, SRS is always sent in a fixed number, but other signaling can occur in other numbers. Figure 22 This illustrates NR-SRS transmission on one symbol corresponding to digit 1. Specific digits can be assigned via semi-static configuration such as RRC signaling or dynamically assigned by DL DCI.

[0254] Alternatively, SRS resources can be defined in units of time and can be configured to support any numeral. In this case, the retained time can carry different numbers of NR-SRS symbols for different numerals. This concept is... Figure 23 As shown, NR-SRS resources are reserved for a fixed duration T. Different numbers can be used within this duration, for example, one symbol of NR-SRS with a subcarrier spacing of 15 kHz (number 1), or two symbols of NR-SRS with a subcarrier spacing of 60 kHz (number 2).

[0255] In this embodiment, the UE can transmit NR-SRS on multiple beams within reserved SRS resources. This concept is... Figure 24 As shown in the diagram, each NR-SRS symbol is reserved for a specific beamforming direction. It is envisioned that these solutions could also be applied to self-contained subframes.

[0256] In another embodiment, SRS port mapping technology can be used to support non-precoding, precoding, and beamforming. NR-SRS port mapping methods for non-precoding, precoding, and beamforming scenarios are described.

[0257] In an exemplary embodiment, the UE can transmit the maximum number of ports it can support and feed back to the NR-NB. The maximum number of available, supported ports can depend on the UE's capabilities. Here, a unified approach to NR-SRS port mapping for non-precoding, precoding, and beamforming can be employed. Port mapping can work in conjunction with UL antenna virtualization. The antenna virtualization method is described below. Figure 25 The diagram shows that antenna virtualization can be divided into four stages. The first stage involves generating... To perform digital precoding or beamforming. After applying antenna virtualization. Figure 25 The effective precoding / beamforming matrix / vector V in the equation can be represented as:

[0258] Equation 1

[0259] in It is a codebook that can be defined or specified in the numeric field. It is a codeword-to-port mapping matrix, and It is a port-to-TXRU mapping matrix, and It is a mapping from TXRU to physical antenna.

[0260] If no precoding or beamforming is applied to the NR SRS, then the NR SRS can be transmitted directly via a port configured / assigned from the NR gNB. In other words, it can be... and Set as a recognition matrix, and This depends on the NR-SRS port configuration settings. For example, if the UE can support up to 8 ports and the RRC configuration parameter srs-TxAntennaPorts is set to {1, 2, 3, 4}, then the UE can send NR-SRS to ports 1, 2, 3, and 4. The active port number can be dynamically signaled via DL DCI. In an example, if the configuration parameter srs-TxAntennaPorts is set to {1, 2, 3, 4} and the NR configures the active ports to {1, 3, 4} at some SRS transmission subframe, then the UE only sends NR-SRS on ports {1, 3, 4}. If DL DCI is not involved in the transmission port configuration, then the UE can send NR-SRS based on the RRC configuration port settings. NR-SRS transmission at different ports can be sent with the same or different CP-OFDM / DFT-S-OFDM symbols and can be associated with specific numerals. Figure 26 In this process, NR-SRS established at different transmission ports are configured to transmit using different CP-OFDM / DFT-S-OFDM symbols.

[0261] Similarly, when precoding or beamforming is involved in NR-SRS, appropriate design can be employed. , and To meet precoding or beamforming requirements. This can be determined based on the SRS port mapping configuration. In short, the following NR-SRS port mapping methods can be used:

[0262] 1. NR-SRS established at different transmission ports can be configured to transmit with different CP-OFDM / DFT-S-OFDM symbols and can be associated with specific digitization.

[0263] 2. Port mapping can be configured semi-statically via RRC or dynamically via DL control.

[0264] Here, and It can be left to the UE to implement and there is no standardization effort.

[0265] According to yet another embodiment, NR-SRS beam scanning can be considered as a unit of beam scanning time used to transmit NR-SRS. Each NR-SRS beam scan block may include at least one or more CP-OFDM / DTF-S-OFDM symbols and is associated with a specific digitization. Multiple beam scan blocks can form a beam scan burst. This is in Figure 27As shown in the diagram, NR-SRS beam scan bursts can be configured for periodic or aperiodic transmission either via semi-static RRC signaling or dynamically configured via DLDCI. SRS beam scan blocks can be associated with a single beam or multiple beams.

[0266] NR CSI Interference Channel Measurement

[0267] According to another aspect of this application, a solution supporting CSI-ICM in NR is envisioned. In one embodiment, a new RRC signaling is employed to signal to CSI-ICM. In another embodiment, two-step dynamic signaling is described. In yet another embodiment, group-based CSI-ICM configuration via DCI is described. In yet another embodiment, the PUCCH format for CSI-ICM reporting is described. In yet another embodiment, the DCI design enables UE interference cancellation against MU-MIMO. In a further embodiment, the interference channel measurement and interference cancellation process is described below.

[0268] Accordingly, the new information element CSI-ICM-Config is used as the sole signaling to indicate all the necessary information describing the configuration. For example, the NR node uses RRC signaling with CSI-RS / ICM location to configure the UE. This can be based on one or more of the following: (i) UE interference assumptions, (ii) the number of interfering channels, and (iii) multi-user MIMO scheduling. Simultaneously, information indicating the precoding matrix used in the CSI-ICM transmission is also required. This is because the UE wants to measure the actual interfering channels, therefore the precoding matrix needs to be removed from the effective channels, and the interfering channel information can be fed back to the NR node. Below is an example of the CSI-ICM configuration information element CSI-ICM-Config in the RRC configuration message:

[0269]

[0270] Alternatively, this technique can achieve CSI-ICM configuration via two-step signaling through NR DCI, avoiding the large latency introduced by the RRC-only signaling method. The steps are as follows:

[0271] Step 1: Initial resource set configuration via RRC signaling. Here, a set of K CSI-ICM resources is pre-configured for all UEs via the RRC information element CSI-ICMset-Config to indicate all available CSI-RS / ICM locations for CSI_ICM. An example of the CSI-ICMset-Config information element in the RRC message is listed below.

[0272]

[0273] Step 2: Dynamic CSI-ICM Configuration Signaling via NR DCI. Here, for a given UE, the NR node indicates N out of K CSI-ICM resources (where N>=1) from the set based on the interference assumption to enable CSI-ICM via dynamic signaling via configurable DCI or via dynamic signaling via MAC CE. The value of N increases as the number of interference sources increases. By introducing this second step, it reduces the latency in CSI-ICM configuration compared to RRC signaling alone. For each UE under different interference assumptions, the DCI information can differ in terms of the number of CSI-ICM resources and locations, the CSI-ICM feedback configuration, and the UL resources used to send CSI-ICM feedback when applicable. Examples of configurable fields for the DCI scheme are listed in Table 4 below. DCI can be configured using one or more or all fields.

[0274]

[0275] Table 4

[0276] As an alternative, dynamic CSI-ICM configuration can also be achieved through a MAC control element (CE) once the resource set has been pre-configured. The following defines a new MAC control element, a CSI-ICM configuration MAC control element carrying information similar to that defined in Table 1:

[0277] CSI-ICM configuration MAC control elements can be defined over a fixed number of n octets. A CSI-ICM configuration MAC control element can be identified using a Logical Channel Identifier (LCID), which can be one of the existing reserved values ​​for LTE downlink logical channels in the range of 01011 and 10111 (binary encoding). Alternatively, the range of LTE logical channel values ​​can be extended using newly defined values ​​assigned to the CSI-ICM configuration MAC CE.

[0278] As discussed above, DCIs need to be sent separately to each UE to indicate the CSI-ICM configuration requiring a large number of DCI transmissions when there are many UEs. To reduce this overhead, a group-based CSI-ICM configuration can be used via DCIs to enable multiple UEs to measure interference channels. UEs with the same interference source or sharing some resources during CSI-ICM can be grouped in a single DCI containing common and individual information and sent to all UEs in that group. Common information consists of shared fields that are identical to all UEs in the group in terms of group ID, CSI-ICM configuration, CSI-RS / ICM structure, etc. Individual information indicates that the UE ID, UL resources used to send CSI-ICM feedback, and all other signaling cannot be shared between UEs within the group, where each UE has its own unique information. Examples of configurable fields for a group-based CSI-ICM configuration DCI scheme are listed in Table 5 below.

[0279]

[0280] Table 5

[0281] According to another embodiment, after measuring the interference channel, the UE needs to feed back the interference channel estimate to the NR node / TRP. This will be used in MU-MIMO scheduling. The interference channel feedback can be implicit, explicit, or a combination of implicit and explicit feedback. For example, only implicit feedback is needed when the maximum eigenvalue is less than a predetermined threshold; otherwise, the UE needs to feed back the explicit channel measurement based on eigenvalues ​​greater than the threshold. Implicit feedback can contain information such as CQI, PMI, or RI for the interference channel, and explicit feedback can take the form of: (i) the exact interference channel measurement; (ii) the eigenvector of the interference channel based on the maximum eigenvalue; and (iii) the covariance matrix of the interference channel.

[0282] To reduce the overhead of explicit interference feedback, it can be quantized using a predefined codebook or converted into a dimensionality-reduced form. Compared to explicit CSI feedback, CSI-ICM feedback can tolerate higher quantization or transformation errors.

[0283] The UE is configured by a higher layer or NR DCI to send CSI-ICM feedback periodically, aperiodically, or semi-persistently via NR PUCCH. New NR PUCCH report types can be defined for CSI-ICM feedback. For periodic CSI-ICM feedback, the periodicity and relative offset are configured by higher layer signaling. For aperiodic or semi-persistent CSI-ICM, the resources for sending CSI-ICM feedback are configured by NR DCI.

[0284] According to yet another embodiment, after receiving CSI and CSI-ICM feedback, the NR node can schedule MU-MIMO transmissions. For UEs scheduled for MU-MIMO, in addition to general transmission information such as resource allocation, modulation and coding schemes, and HARQ process numbers, the NR DCI should also include the following information:

[0285] 1. Antenna Port Index: The antenna port index can be implicitly or explicitly signaled to the UE. For implicit signaling, the limited set of configurations for these parameters can be predefined in the standard specification or configured by higher-layer signaling, and then the selected configuration index is signaled only in the NRDCI format.

[0286] 2. Precoding / Decoding Matrix Information: This can include information such as the codebook index for the precoding matrix, the PMI, or the index of the proposed decoding matrix. With this information, the UE can cancel interference sent to other co-scheduled UEs or interference from other beams / TRPs.

[0287] According to another embodiment, the process of interference channel measurement and interference cancellation is described. These include, for example:

[0288] 1. The NR node first configures CSI-RS and CSI-ICM for the UE via RRC signaling or NR DCI / MAC CE.

[0289] 2. Based on CSI-RS and CSI-ICM configuration, the UE measures the desired channel and interfering channels.

[0290] 3. The UE sends CSI and CSI-ICM feedback to the NR node, where the feedback can be implicit, explicit, or a combination of implicit and explicit feedback.

[0291] 4. The NR node schedules MU-MIMO transmissions based on CSI and CSI-ICM feedback, and sends scheduling decisions and transmission information to the UE via NR DCI, including information such as antenna port index and precoding / decoding matrix information.

[0292] Based on information from its NR DCI, the UE is able to cancel interference sent to other co-scheduled UEs or interference from other beams / TRPs.

[0293] exist Figure 28 The diagram illustrates the call flow that depicts the CSI-ICM process.

[0294] Dynamic CSI Measurement and Reporting

[0295] According to another aspect of this application, a semi-static RRC configuration for CSI measurements and a pooling of CSI-RS resource elements for the UE are described, along with dynamic signaling for scheduling CSI measurements. Two methods for RRC-based configuration of CSI-RS pooled resources are also described.

[0296] Method 1: UE-specific CSI-RS resource configuration, without configuring a group of UEs sharing the same CSI-RS resource pool. The NR node (e.g., gNB) configures a set of K CSI-RS resources to the UE using a dedicated RRC message (e.g., similar to an RRCConnectionReconfiguration message or an NR RRC equivalent). The UE uses the CSI-RS configuration to identify the CSI-RS resources used for channel state measurements. The NR node can signal the exact CSI-RS to be used from the configured set to the UE via MAC CE signaling or DCI signaling. The configuration set configured by the NR node for the UE may include one or more parameters:

[0297] A. Antenna port count, i.e., the number of antenna ports used for CSI-RS transmission. The antenna port count used for CSI-RS can be numeric-specific.

[0298] B. CSI RS mapping to resource element configuration. The CSI RS mapping to resource elements can be numeric-specific.

[0299] C. CSI-RS transmission interval configuration (e.g., in terms of subframe configuration) can indicate the period and time interval (e.g., subframe) offset for the occurrence of the CSI reference signal (within the CSI-RS period). The time interval offset specifies the exact time interval of the subframe within the CSI-RS transmission periodicity for CSI-RS transmission. The CSI-RS transmission time interval of the subframe configuration can be digitally specific.

[0300] D. Beam configuration in DL and beam configuration in UL are used to report measurements performed by CSI-RS.

[0301] E. For each of the above configuration parameters, the configuration can be predefined (e.g., in the specification), and the index for these predefined configurations is only signaled to the UE.

[0302] F. It should be noted that even if each terminal is provided with dedicated RRC signaling with terminal-specific CSI-RS resource configuration, the network can still configure more than one UE with the same set of CSI-RS resources.

[0303] G. By default, the CSI-RS set pre-configured in the UE by the NR node via RRC signaling is not activated; that is, the UE does not perform measurements on these CSI-RS. The UE performs measurements on these CSI-RS via MAC CE signaling of physical layer DCI signaling after receiving a CSI-RS measurement activation command from the NR node.

[0304] Method 2: UE-specific CSI-RS resource configuration, where a group of UEs share the same CSI-RS resource pool. In this embodiment, the NR node can limit the signaling overhead associated with CSI-RS configuration by using group configuration. In addition to the parameters used in Method 1, the NR node's configuration set for UEs may include one or more parameters:

[0305] A. UE Group Identity

[0306] B. The UE's position or index within this group.

[0307] C. For example, when a UE is configured with a dedicated signaling bearer (e.g., SRB1 or SRB2 or an NR equivalent) or a dedicated radio bearer, the NR node can configure each UE with a UE group identity for, for example, a group RNTI (Radio Network Temporary Identifier). The group RNTI is used to address resources / locations of CSI-RS configurations for a specific UE group configured with that group RNTI. The group RNTI can be mapped to a DL-SCH (Downlink Shared Channel) transport channel, a multicast logical channel, or a similar NR transport channel. The UE monitors the transmission of this group RNTI from the NR node. Upon detecting the group RNTI, the UE uses the group RNTI to search for and decode the associated CSI-RS configuration.

[0308] D. For each configured group, all UEs in that group are arranged sequentially. The position or index of a UE within this group is essentially its order within the group, which can be used by group-based DCI (using group RNTI) to identify the UE in a signaling-efficient manner. For example, consider group #3 with UE 2, UE 77, UE 105, and UE 269. Then, the position or index of the UEs within group 3 for UE 2, UE 77, UE 105, and UE 269 are 1, 2, 3, and 4, respectively.

[0309] In one embodiment, the NR node can initially signal the CSI-RS configuration to the UE in dedicated UE RRC signaling, as described in the embodiments above, and then use group signaling to configure the UE group with the CSI-RS resources in the common pool.

[0310] According to another embodiment, a detailed design for CSI-RS pooled DCI or MAC CE signaling is described. Several signaling designs include: (i) CSI measurement commands signaled in the DCI; and (ii) CSI measurement commands signaled in the MAC CE.

[0311] Signaling based on the MAC CE. In an embodiment, the following method can be used to signal CSI measurement commands within the MAC CE. Specifically, the NR node dynamically signals the transmission of CSI-RS, pre-configured by RRC signaling, to the UE within the MAC CE. The indication of CSI-RS transmission in the MAC CE may include (e.g., via RRC signaling) a CSI-RS configuration index previously pre-configured in the UE. The UE uses this index to locate CSI-RS configuration information stored in its internal database. The UE can then perform CSI-RS measurements using CSI-RS configuration parameters (e.g., antenna port count, resource information, CSI-RS transmission interval information, beam configuration) identified by the information received in the MAC CE (e.g., the CSI-RS configuration index).

[0312] In an exemplary embodiment, in addition to the CSI-RS configuration index, the MAC CE may also carry a measurement time window. The measurement time window can be predefined in the specification. It can be expressed as an integer number of CSI-RS transmission time intervals (e.g., CSI transmission periodic time values), such as 1, 2, 3, 4, etc. For example, if the measurement time window is 1, then the UE measures CSI-RS over one CSI-RS transmission time interval and stops. Similarly, if the measurement time window is k, then the UE measures CSI-RS over k CSI-RS transmission time intervals. In this embodiment, the NR node does not signal to the MAC CE to terminate the CSI-RS measurement. The UE implicitly terminates the measurement using the received transmission time window.

[0313] In another embodiment, the NR node can explicitly signal to the UE in the MAC CE to terminate (or deactivate) or previously activated CSI-RS measurements. This may be the case if the NR node did not include measurement time window information in the MAC CE activation for previous CSI-RS measurements. Examples of CSI-RS measurement activation and deactivation of the MAC CE are shown in Figure 17 and... Figure 18 The MAC CE can be defined over a fixed number of n octets. The transport MAC CE can be identified by a MAC PDU subheader with a Logical Channel Identifier (LCID), as defined below.

[0314] The following are two examples of MAC CE. A CSI RS measurement activation / deactivation MAC control element with one octet is defined in Figure 17. It has a fixed size and consists of a single octet containing an RS field portion and a TW field, where the TW encodes the measurement time window, and the RS field encodes the activation or deactivation of the CSI-RS measurement. Similarly, in Figure 18 The code defines an example of a k-octet MAC control element for activation / deactivation, assuming k=4. It has a fixed size and consists of k octets containing an RS field and a TW field. The RS field is set to "1" to indicate that the CSI-RS configuration identified by configuration index i will be activated. The RSi field is set to "0" to indicate that the CSI-RS configuration identified by configuration index i will be deactivated.

[0315] The MAC CE shown in the figure includes only one measurement time window (TW). This means that the measurement time window is common to all CSI-RS configurations included in the MAC CE. However, the MAC CE can also be a structure that includes more than one TW. For example, assuming that each CSI RS included in the MAC CE has a different TW, then there will be as many TWs as the RSs in the MCA CE.

[0316] Figure 29 The diagram illustrates an 8-bit CSI-RS measurement activation / deactivation MAC control element. Figure 30 The diagram illustrates the MAC control element for activating / deactivating CSI-RS measurements using k (k=4) octets.

[0317] The logical channel ID associated with the CSI-RS measurement activation / deactivation of the MAC CE can be one of the existing reserved values ​​for LTE downlink logical channels in the range of 01011 and 10111 (binary encoding). Alternatively, the range of LTE logical channel values ​​can be expanded using newly defined values ​​assigned to the CSI-RS measurement activation / deactivation of the MAC CE. The logical channel ID should uniquely identify the MAC CE. For example, the MAC CEs in the two figures above should have different logical channel IDs. The signaling described for the MAC CE can also be applied to DCI-based signaling.

[0318] According to another embodiment, the following DCI-based signaling method may include: (i) carrying CSI measurement commands on the DCI; (ii) independent CSI measurement commands for a specific UE (sent on a separate DCI); and (iii) group-based DCI to schedule CSI-RS measurements and feedback for multiple UEs.

[0319] In signaling method 1, use one or both of the following options to load CSI measurement commands onto another DCI:

[0320] 1. The CSI measurement command is signaled in the DCI used for scheduling NR-PUSCH. Furthermore, this DCI can schedule one or more PUSCHs in different subframes, carrying UL control information for CSI measurements.

[0321] 2. The CSI measurement command is signaled in the DCI used to schedule NR-PDSCH. This DCI can schedule one or more PUCCHs in different subframes to carry UL control information for CSI measurements.

[0322] According to option 1, the CSI measurement command is signaled in the DCI (so-called UL-licensed DCI) used to schedule the NR-PUSCH. It will carry (explicitly or implicitly) the following information:

[0323] A. CSI Request: For example, a 1-bit field to indicate whether CSI measurements and reports are set to be triggered.

[0324] B. CSI-RS Resource Indication. This is an indication of N (where N>=1) of the K CSI-RS resources in the resource set configured by RRC signaling. This can be signaled via bitmaps or other methods.

[0325] C. Antenna port to CSI-RS resource element mapping:

[0326] 1. The information can be signaled in various ways, or it can be signaled implicitly.

[0327] 2. If the CSI-RS design allows for different densities of CSI-RS for antenna ports at different measurement instances, then the number of antenna ports should be signaled. For example, if the indicated subset of CSI-RS resources can be interpreted as being for either 4 or 8 CSI-RS ports, then a 1-bit signaling should be used to indicate the number of antenna ports.

[0328] 3. If the CSI-RS design only allows a fixed density of CSI-RS for antenna ports at different measurement instances, then the UE can infer the number of antenna ports from the set of CSI-RS resources.

[0329] D. RB location / index, where the UE should receive its CSI-RS and perform channel or interference measurements.

[0330] 1. If this field is omitted, the UE will receive CSI-RS from all RBs in the cell.

[0331] 2. The indication of CSI-RS resources will be applied to all indicated RB locations.

[0332] E. CSI measurement configuration for UE.

[0333] 1. Each CSI measurement configuration includes a set of CSI measurement / feedback reporting parameters: measurement / feedback metrics (RI, PMI, CQI, etc.), whether the metric is a broadband or subband measurement, the reporting frequency of each feedback metric, and the relative time offset.

[0334] 2. Indicate one of the CSI measurement configurations in the DCI. Alternatively, the UE can configure a subset of allowed CSI measurement configurations in the standard via higher-layer signaling (such as RRC signaling). Then, indicate one of the CSI measurement configuration subsets in the DCI.

[0335] F. CSI measurement report, physical uplink channel, and start time

[0336] 1. The number of CSI measurement reports to be sent in the uplink can be explicitly signaled or implicitly inferred from the CSI measurement configuration. For example, CSI measurement report signaling can indicate two report instances for CSI measurement type 3. If CSI measurement type 3 is carried on NR-PUSCH, only one report is needed; if carried on NR-PUCCH, J NR-PUCCHs are needed to carry a complete CSI report.

[0337] 2. DCI can schedule several NR-PUSCHs in subsequent subframes, each subframe carrying a complete CSI report (or a portion thereof). Alternatively, this DCI can explicitly schedule one NR-PUSCH and several NR-PUCCHs in subsequent subframes. The indices of these subframes will be signaled.

[0338] 3. NR-PUSCH resource allocation is already included in the uplink license DCI. If several subsequent NR-PUSCHs are scheduled, they may have the same or different resource allocations (additional signaling); if several subsequent NR-PUCCHs are scheduled, the NR-PUCCH index can be implicitly signaled from either the search space index of the uplink license DCI or the starting RB index of the RB sending the uplink license DCI.

[0339] 4. CSI Measurement Report Start Time: Signals the timing offset from the current subframe, where the offset value ranges from 0 to H subframes. The default value for the timing offset is zero. As shown in the figure below, when the offset is set to zero, CSI measurements can be reported as early as the end of the NR-PUSCH scheduled by the uplink permitted DCI at the start of the subframe (or flexible time interval).

[0340] Figure 31 The illustration shows one or more NR-PUSCHs being scheduled for CSI measurement reporting.

[0341] Figure 32 The illustration shows one NR-PUSCH and / or several NR-PUCCHs being scheduled for CSI measurement reporting.

[0342] According to Option 2, the CSI measurement command is signaled in the DCI used for scheduling NR-PDSCH, and this DCI is a DL-licensed DCI. It will carry (explicitly or implicitly) the following information similar to that in Option 1 and will include the following additional fields.

[0343] G. CSI measurement report, physical uplink channel, and start time

[0344] H. The number of CSI measurement reports to be sent in the uplink can be explicitly signaled or implicitly inferred from the CSI measurement configuration.

[0345] I. DCI can schedule several NR-PUCCHs in subsequent subframes, each subframe carrying a complete CSI report (or a portion thereof). The index of these subframes will be signaled.

[0346] J. The NR-PUCCH index can be implicitly signaled from either the search space index of the uplink license DCI or the starting RB index of the RB that sends the uplink license DCI.

[0347] K. CSI Measurement Report Start Time: Signals the timing offset from the current subframe, where the offset value ranges from 0 to H subframes. The default value for the timing offset is zero. As shown in the figure below, when the offset is set to zero, CSI measurements can be reported by PUCCH as early as the end of the current subframe after the NR-PDSCH scheduled by the DL-licensed DCI.

[0348] Figure 33 The diagram illustrates several NR-PUCCHs scheduled for CSI measurement reports. The UE procedures for signaling method 1 (including options 1 and 2) are described below:

[0349] Step 1: A UE with CSI-RS pooled resources configured by higher-layer signaling will monitor the downlink NR-PDCCH search space to detect DCI.

[0350] Step 2: If it successfully detects a UL or DL ​​licensed DCI addressing its C-RNTI or other format UE ID, and the CSI request field is set to "Trigger" or "On", then the UE will process the received CSI measurement command information.

[0351] Step 3: The UE will perform CSI measurements by processing the CSI-RS received in the resources indicated in the CSI measurement command, based on the parameters in the CSI-RS resource allocation field and the location of the RBs of these CSI-RS (optionally). The CSI measurement type (such as broadband CQI / PMI, etc.) will be determined according to the CSI measurement configuration parameters.

[0352] Step 4: The UE will report its CSI measurements to the gNB using the parameters in the "CSI Measurement Report, Physical Uplink Channel and Timing" field. For example, the UE will send its CSI measurements on the NR-PUSCH or NR-PUCCH scheduled by the UL or DL-licensed DCI.

[0353] According to another embodiment, an independent CSI measurement command can be sent on a separate DCI, which can be used to activate CSI measurements for the UE. This independent CSI measurement command DCI will carry the following information (explicitly or implicitly) as in Option 1 of signaling method 1, and includes the following additional fields:

[0354] A. UE ID, which can be implicitly signaled using the UE's C-RNTI or other IDs to scramble the DCI's CRC.

[0355] B. It is not necessary to send the "CSI Request" field as in option 1 of signaling method 1.

[0356] C. CSI measurement report, physical uplink channel, and start time

[0357] 1. The number of CSI measurement reports to be sent in the uplink can be explicitly signaled or implicitly inferred from the CSI measurement configuration.

[0358] 2. DCI can schedule several NR-PUCCHs in subsequent subframes, each subframe carrying a complete CSI report (or a portion thereof). The index of these subframes will be signaled.

[0359] 3. The NR-PUCCH index can be implicitly signaled from either the search space index of the DCI measured independently by CSI or by sending the starting RB index of the RB of the DCI measured independently by CSI.

[0360] 4. CSI Measurement Report Start Time: Signals the timing offset from the current subframe, where the offset value ranges from 0 to H subframes. The default value for the timing offset is zero. As shown in the figure below, when the offset is set to zero, CSI measurements can be reported as CSI Measurement DCI as early as the PUCCH in the current subframe.

[0361] Figure 34 The diagram illustrates several NR-PUCCHs scheduled for CSI measurement reports.

[0362] According to yet another embodiment, the UE procedure for signaling method 2 is as follows:

[0363] Step 1: A UE with CSI-RS pooling resources configured by higher-layer signaling will monitor the downlink NR-PDCCH search space to detect DCI with independent CSI measurement DCI format.

[0364] Step 2: If it detects a standalone CSI measurement DCI addressed to its C-RNTI or other format UE ID, then the UE will process the received CSI measurement command information.

[0365] Step 3: The UE will perform CSI measurements by processing the CSI-RS received in the resources indicated in the CSI measurement command according to the parameters in the CSI-RS resource allocation field and the RB location of these CSI-RS (optional). The CSI measurement type (such as broadband CQI / PMI, etc.) will be determined according to the CSI measurement configuration parameters.

[0366] Step 4: The UE will report its CSI measurements to the gNB using the parameters in the "CSI Measurement Report, Physical Uplink Channel and Timing" fields. For example, the UE will send its CSI measurements on the NR-PUCCH scheduled by the independent CSI measurement DCI.

[0367] Signaling method 3 is described according to another embodiment. Here, group-based CSI measurement DCI can be used to schedule CSI-RS measurements and feedback for multiple UEs. When these UEs have the same CSI reporting configuration and share the same CSI-RS resource pool configured by higher-level signaling, group-based CSI measurement DCI can achieve reduced signaling overhead. In addition to the following different fields, this group-based CSI measurement DCI will (explicitly or implicitly) carry the following information similar to that in option 1 of signaling method 1:

[0368] A. Group ID: As described, multiple UEs have been configured to be in a group by higher-level signaling (such as RRC). They can then address their group ID or group RNTI in the group-based CSI measurement DCI.

[0369] B. Which UEs need to perform CSI measurements: This can be done via a bitmap in the order of the UEs' indices / positions within the group configured by higher-layer signaling. For each UE that needs to perform CSI measurements, the corresponding position in the bitmap will be set to "1" otherwise set to "0".

[0370] C. CSI-RS Resource Indication.

[0371] 1. UEs indicated in the same CSI measurement DCI can have the same or different CSI-RS resource allocations. Both can be signaled via bitmaps or other methods.

[0372] D. Antenna port to CSI-RS resource element mapping, which will be the same for all UEs in SCI measurement DCI.

[0373] E. The signaling method can be the same as that in option 1 of signaling method 1.

[0374] F. Wherein the UE should receive its CSI-RS and perform channel or interference measurements of the RB location / index, this will be the same for all UEs in the SCI measurement DCI.

[0375] 1. If this field is omitted, the UE will receive CSI-RS on all RBs in the cell.

[0376] 2. The indication of CSI-RS resources will be applied to all indicated RB locations.

[0377] G. The CSI measurement configuration used for the UE will be the same for all UEs in the SCI measurement DCI.

[0378] 1. The signaling method can be the same as option 1 of signaling method 1.

[0379] H. CSI measurement report, physical uplink channel and start time

[0380] 1. The number of CSI measurement reports to be sent in the uplink can be explicitly signaled or implicitly inferred from the CSI measurement configuration.

[0381] 2. DCI can schedule several NR-PUCCHs in subsequent subframes, each subframe carrying a complete CSI report (or a portion thereof). The number of NR-PUCCHs scheduled will be the same for all UEs in the CSI measurement DCI. The indices of these subframes, which will be signaled, can be the same for all UEs in the SCI measurement DCI, or they can be different but scheduled in the time domain according to a predefined pattern. For example, the NR-PUCCHs of the first UE are scheduled in subframes 1, 5, and 9; and the NR-PUCCHs of the second UE are scheduled in subframes 2, 6, and 10; and so on.

[0382] 3. If different UEs' NR-PUCCHs are scheduled in different subframes, then the NR-PUCCH index for each UE can be the same. For example, it can be implicitly signaled by either measuring the search space index of the DCI based on the group's CSI or sending the starting RB index of the RB for the DCI based on the group's CSI. If different UEs' NR-PUCCHs are scheduled in the same subframe, then the NR-PUCCH index for each UE should be different. For example, it can be implicitly signaled by either measuring the search space index of the DCI based on the group's CSI plus an offset equal to the UE's index or position within the group, or sending the starting RB index of the RB for the DCI based on the group's CSI plus an offset equal to the UE's index or position within the group.

[0383] 4. CSI Measurement Report Start Time: Signals the timing offset from the current subframe, where the offset value ranges from 0 to H subframes. The default value for the timing offset is zero. As shown in the figure below, when the offset is set to zero, CSI measurements can be reported as a group-based CSI measurement DCI as early as the PUCCH in the current subframe. The CSI measurement report start time can be the same for all UEs in the CSI measurement DCI, or it can be different but scheduled in the time domain according to a predefined pattern. For example, the UE's offset can be 1, 3, 5, etc.

[0384] The UE procedure for signaling method 2 is described below according to another embodiment:

[0385] Step 1: A UE with CSI-RS pooling resources configured by higher-layer signaling will monitor the downlink NR-PDCCH search space to detect DCIs with group-based CSI measurement DCIs.

[0386] Step 2: If it detects a group-based CSI measurement DCI addressed to (configured by higher-layer signaling) its group RNTI or group Id, then the UE will process the received CSI measurement command information.

[0387] Step 3: The UE will perform CSI measurements by processing the CSI-RS received in the resources indicated in the CSI measurement command according to the parameters in the CSI-RS resource allocation field and the location of the RB of these CSI-RS (optionally). The CSI measurement type (such as broadband CQI / PMI, etc.) will be performed according to the CSI measurement configuration parameters.

[0388] Step 4: The UE will report its CSI measurements to the gNB using the parameters in the "CSI Measurement Report, Physical Uplink Channel and Timing" fields. For example, the UE will send its CSI measurements on the NR-PUCCH scheduled by the independent CSI measurement DCI.

[0389] The signaling described in this section for DCI-based signaling can also be applied to MAC CE-based signaling.

[0390] It should be understood that, Figures 1-34 The functions, steps, and configurations shown may be implemented or generated by software (i.e., computer-executable instructions) stored in the memory of a wireless device or other apparatus (e.g., a server, gateway, device, or other computer system) and executed on its processor, such as those described below. Figure 36B and Figure 36F One of those shown.

[0391] Interfaces such as graphical user interfaces (GUIs) can be used to help users control and / or configure functions related to reference signals and control channels in NR. Figure 35 This is a diagram illustrating an interface 3502 that allows users to input and view parameters corresponding to reference signals and control channels in the NR. It should be understood that interface 3502 can be used in ways such as those described below. Figure 36B and Figure 36F The display shown is used to generate it.

[0392] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities—including work on codecs, security, and quality of service. Recent Radio Access Technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), and LTE-Advanced. 3GPP has begun working on the standardization of next-generation cellular technologies, known as New Radio (NR), also referred to as “5G.” The development of the 3GPP NR standard is expected to include the definition of next-generation radio access technologies (new RATs), which is expected to include new flexible radio access below 6 GHz and new ultra-mobile broadband radio access above 6 GHz. Flexible radio access is expected to consist of new, non-backward-compatible radio access in the new spectrum below 6 GHz, and it is expected to include different operating modes that can be multiplexed together in the same spectrum to address a broad set of 3GPP NR use cases with varying requirements. Ultra-mobile broadband is expected to include cmWave and mmWave spectrum, which will provide opportunities for ultra-mobile broadband access for applications such as indoor spaces and hotspots. In particular, Ultra Mobile Broadband is expected to share a common design framework with flexible radio access below 6 GHz, featuring design optimizations specific to cmWave and mmWave.

[0393] 3GPP has identified a variety of use cases that NR is expected to support, resulting in diverse user experience requirements regarding data rates, latency, and mobility. These use cases fall into the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, ultra-high-bandwidth indoor access, broadband access in crowds, 50+ Mbps everywhere, ultra-low-cost broadband access, vehicular mobile broadband), critical communications, large-scale machine-type communications, network operations (e.g., network slicing, routing, migration and interaction, energy saving), and enhanced vehicle-to-everything (eV2X) communications. Specific services and applications within these categories include, for example, surveillance and sensor networks, remote device control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connectivity, car ecalls, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, haptic internet, and virtual reality. This document anticipates all of these use cases, as well as others.

[0394] Figure 36AAn embodiment of an example communication system 100 is illustrated, in which the methods and apparatus described and claimed herein can be implemented. As shown, the example communication system 100 may include wireless transceiver units (WTRUs) 102a, 102b, 102c and / or 102d (generally or commonly referred to as WTRU 102), radio access networks (RANs) 103 / 104 / 105 / 103b / 104b / 105b, core networks 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of apparatus or device configured to operate and / or communicate in a wireless environment. Although each WTRU 102a, 102b, 102c, 102d is in Figures 36A-36E While described as a handheld wireless communication device, it should be understood that for the various use cases anticipated for 5G wireless communication, each WTRU may include or be implemented in any type of device or apparatus configured to transmit and / or receive wireless signals. As an example only, such devices or apparatus include user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, tablets, netbooks, notebook computers, personal computers, wireless sensors, consumer electronics, wearable devices (such as smartwatches or smart clothing), medical or e-health devices, robots, industrial equipment, drones, and vehicles (such as cars, trucks, trains, or airplanes).

[0395] The communication system 100 may also include base station 114a and base station 114b. Base station 114a may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c to facilitate access to one or more communication networks (such as core networks 106 / 107 / 109, the Internet 110, and / or other networks 112). Base station 114b may be any type of device configured to wired and / or wirelessly interface with at least one of RRHs (Remote Radio Headers) 118a, 118b and / or TRPs (Transmit and Receive Points) 119a, 119b to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, and / or other networks 112. RRH 118a and 118b can be any type of device configured to interface wirelessly with at least one of the WTRU 102c to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, and / or other networks 112. TRP 119a and 119b can be any type of device configured to interface wirelessly with at least one of the WTRU 102d to facilitate access to one or more communication networks, such as core networks 106 / 107 / 109, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b can be base transceiver stations (BTS), node-B, eNode B, home node B, home eNode B, site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are both depicted as single elements, it should be understood that base stations 114a and 114b can include any number of interconnected base stations and / or network elements.

[0396] Base station 114a may be part of RAN 103 / 104 / 105, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114b may be part of RAN 103b / 104b / 105b, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a may be configured to transmit and / or receive radio signals within a specific geographical area, which may be referred to as a cell (not shown). Base station 114b may be configured to transmit and / or receive wired and / or radio signals within a specific geographical area, which may be referred to as a cell (not shown). Cells may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in an embodiment, base station 114a may include three transceivers, for example, one transceiver for each sector of the cell. In an embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology, thus allowing multiple transceivers to be used for each sector of the cell.

[0397] Base station 114a can communicate with one or more of WTRUs 102a, 102b, and 102c via air interfaces 115 / 116 / 117. Air interfaces 115 / 116 / 117 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). Any suitable radio access technology (RAT) can be used to establish air interfaces 115 / 116 / 117.

[0398] Base station 114b can communicate with one or more of RRH 118a, 118b and / or TRP 119a, 119b via wired or air interfaces 115b / 116b / 117b. The wired or air interfaces 115b / 116b / 117b can be any suitable wired (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). Any suitable radio access technology (RAT) can be used to establish air interfaces 115b / 116b / 117b.

[0399] RRH 118a, 118b and / or TRP 119a, 119b can communicate with one or more WTRU 102c, 102d via air interface 115c / 116c / 117c. Air interface 115c / 116c / 117c can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 115c / 116c / 117c.

[0400] More specifically, as described above, the communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base station 114a in RAN 103 / 104 / 105 and WTRU 102a, 102b, 102c, or RRH 118a, 118b and TRP 119a, 119b in RAN 103b / 104b / 105b and WTRU 102c, 102d can implement radio technologies, such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can use Wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c respectively. WCDMA can include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed ​​Downlink Packet Access (HSDPA) and / or High-Speed ​​Uplink Packet Access (HSUPA).

[0401] In the embodiments, base station 114a and WTRUs 102a, 102b, 102c or RANs 103b / 104b / 105b, specifically RRH118a, 118b and TRPs 119a, 119b and WTRUs 102c, 102d, can implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can establish air interfaces 115 / 116 / 117 or 115c / 116c / 117c using Long Term Evolution (LTE) and / or LTE-Advance (LTE-A), respectively. In the future, air interfaces 115 / 116 / 117 can implement 3GPP NR technology.

[0402] In the embodiments, base station 114a and WTRU 102a, 102b, 102c or RAN 103b / 104b / 105b RRH118a, 118b and TRP 119a, 119b and WTRU 102c, 102d can implement radio technologies such as IEEE 802.16 (e.g., Global Microwave Access Interoperability (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0403] For example, Figure 36A Base station 114c can be a wireless router, home node B, home eNode B, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area (such as a business location, home, vehicle, campus, etc.). In one embodiment, base station 114c and WTRU 102e can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 114c and WTRU 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114c and WTRU 102e can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish picocells or femtocells. Figure 4 As shown in Figure A, base station 114b can have a direct connection to the Internet 110. Therefore, base station 114c is not required to access the Internet 110 via core networks 106 / 107 / 109.

[0404] RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b can communicate with core networks 106 / 107 / 109, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU 102a, 102b, 102c, and 102d. For example, core networks 106 / 107 / 109 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, and / or perform advanced security functions such as user authentication.

[0405] Although not in Figure 36AAs shown, but it should be recognized that RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b and / or core network 106 / 107 / 109 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b. For example, in addition to being connected to RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b which can utilize E-UTRA radio technology, core network 106 / 107 / 109 can also communicate with another RAN (not shown) that uses GSM radio technology.

[0406] Core networks 106 / 107 / 109 can also serve as gateways for WTRUs 102a, 102b, 102c, 102d, and 102e to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another core network connected to one or more RANs, which may use the same RAT as RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105 or a different RAT.

[0407] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multi-mode capability. For example, WTRUs 102a, 102b, 102c, 102d, and 102e may include multiple transceivers for communicating with different wireless networks via different wireless links. Figure 4 The WTRU 102e shown in A can be configured to communicate with a base station 114a that can employ cellular-based radio technology and with a base station 114c that can employ IEEE 802 radio technology.

[0408] Figure 36B This is a block diagram of an example apparatus or device (such as, for example, WTRU 102) configured for wireless communication according to the embodiments shown herein. Figure 36BAs shown, the example WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and other peripheral devices 138. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments. Furthermore, the embodiments contemplate that base stations 114a and 114b, and / or base stations 114a and 114b may represent nodes (such as, but not limited to, transceiver stations (BTS), node-B, site controllers, access points (APs), home node-B, evolved home node-B (eNodeB), home evolved node-B (HeNB), home evolved node-B gateways, and proxy nodes, etc.), which may include... Figure 36B Some or all of the elements described herein.

[0409] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, and transceiver 120 can be coupled to transmitting / receiving element 122. Although Figure 36B The processor 118 and transceiver 120 are depicted as separate components, but it should be recognized that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0410] The transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 115 / 116 / 117. For example, in an embodiment, the transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. Although not explicitly stated in the text... Figure 36AAs shown, but it should be recognized that RAN 103 / 104 / 105 and / or core network 106 / 107 / 109 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 103 / 104 / 105. For example, in addition to being connected to RAN 103 / 104 / 105 which can utilize E-UTRA radio technology, core network 106 / 107 / 109 can also communicate with another RAN (not shown) that uses GSM radio technology.

[0411] Core networks 106 / 107 / 109 can also serve as gateways for WTRUs 102a, 102b, 102c, and 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another core network connected to one or more RANs, which may use the same RAT as RAN 103 / 104 / 105 or a different RAT.

[0412] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multi-mode capability. For example, WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks via different wireless links. Figure 36A The WTRU 102c shown can be configured to communicate with base station 114a, which can employ cellular-based radio technology, and with base station 114b, which can employ IEEE 802 radio technology.

[0413] Figure 36B This is a block diagram of an example apparatus or device (such as, for example, WTRU 102) configured for wireless communication according to the embodiments shown herein. Figure 36BAs shown, the example WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and other peripheral devices 138. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments. Furthermore, the embodiments contemplate that base stations 114a and 114b, and / or base stations 114a and 114b may represent nodes (such as, but not limited to, transceiver stations (BTS), node-B, site controllers, access points (APs), home node-B, evolved home node-B (eNodeB), home evolved node-B (HeNB), home evolved node-B gateways, and proxy nodes, etc.), which may include... Figure 36B Some or all of the elements described in the document.

[0414] Processor 118 can be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 can perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 can be coupled to transceiver 120, and transceiver 120 can be coupled to transmitting / receiving element 122. Although Figure 36B The processor 118 and transceiver 120 are depicted as separate components, but it should be recognized that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0415] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 115 / 116 / 117. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In another embodiment, transmitting / receiving element 122 can be a transmitter / detector configured to, for example, transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and receive both RF and optical signals. It should be appreciated that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0416] Furthermore, although the transmitting / receiving element 122 is in Figure 36BWhile depicted as a single element, WTRU 102 may include any number of transmitting / receiving elements 122. More specifically, WTRU 102 may employ MIMO technology. Therefore, in embodiments, WTRU 102 may include two or more transmitting / receiving elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interfaces 115 / 116 / 117.

[0417] Transceiver 120 can be configured to modulate signals to be transmitted by transmitting / receiving element 122 and demodulate signals to be received by transmitting / receiving element 122. As described above, WTRU 102 can have multimode capability. Therefore, transceiver 120 can include multiple transceivers for enabling WTRU 102 to communicate via multiple RATs (e.g., such as UTRA and IEEE 802.11).

[0418] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad / indicator 128. Furthermore, the processor 118 can access and store data from any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory 132 may include a subscriber identity module (SIM) card, memory stick, secure digital storage (SD) card, etc. In embodiments, the processor 118 can access and store information from memory that is not physically located on WTRU 102 (such as on a server or home computer (not shown)).

[0419] The processor 118 may receive power from the power supply 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0420] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to or instead of the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via air interfaces 115 / 116 / 117 and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method, while remaining consistent with the embodiments.

[0421] The processor 118 can also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules that provide additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, electronic compasses, satellite transceivers, digital cameras (for photos or videos), Universal Serial Bus (USB) ports or other interconnect interfaces, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, etc.

[0422] WTRU 102 can be implemented in other devices or equipment, such as sensors, consumer electronics, wearable devices (such as smartwatches or smart clothing), medical or e-health devices, robots, industrial equipment, drones, and vehicles (such as cars, trucks, trains, or airplanes). WTRU 102 can be connected to other components, modules, or systems of such devices or equipment via one or more interconnect interfaces (such as interconnect interfaces that may include one of the peripheral devices 138).

[0423] Figure 36C This is a system diagram of RAN 103 and core network 106 according to an embodiment. As described above, RAN 103 can communicate with WTRUs 102a, 102b, and 102c via air interface 115 using UTRA radio technology. RAN 103 can also communicate with core network 106. Figure 36CAs shown, RAN 103 may include nodes-B 140a, 140b, and 140c, each node may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 115. Nodes-B 140a, 140b, and 140c may each be associated with a specific cell (not shown) within RAN 103. RAN 103 may also include RNCs 142a and 142b. It should be understood that RAN 103 may include any number of nodes-B and RNCs while remaining consistent with the embodiments.

[0424] like Figure 4 As shown in Figure C, nodes B 140a and 140b can communicate with RNC 142a. Additionally, node B 140c can communicate with RNC 142b. Nodes B 140a, 140b, and 140c can communicate with their respective RNCs 142a and 142b via the Iub interface. RNCs 142a and 142b can communicate with each other via the Iur interface. Each of RNCs 142a and 142b can be configured to control its connected node B 140a, 140b, or 140c. Furthermore, each of RNCs 142a and 142b can be configured to perform or support other functions, such as outer-loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, and data encryption.

[0425] Figure 4 The core network 106 shown in C may include a Media Gateway (MGW) 144, a Mobile Switching Center (MSC) 146, a Serving GPRS Support Node (SGSN) 148, and / or a Gateway GPRS Support Node (GGSN) 150. While each of the foregoing elements is depicted as part of the core network 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0426] RNC 142a in RAN 103 can be connected to MSC 146 in core network 106 via IuCS interface. MSC 146 can be connected to MGW 144. MSC 146 and MGW 144 can provide WTRU 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRU 102a, 102b, and 102c and traditional landline communication equipment.

[0427] RNC 142a in RAN 103 can also be connected to SGSN 148 in core network 106 via IuPS interface. SGSN 148 can be connected to GGSN 150. SGSN 148 and GGSN 150 can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices.

[0428] As described above, core network 106 can also be connected to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0429] Figure 36D This is a system diagram of RAN 104 and core network 107 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with core network 107.

[0430] RAN 104 may include eNode-Bs 160a, 160b, and 160c; however, it should be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In the embodiments, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, eNode-B 160a may, for example, use multiple antennas to transmit and receive radio signals from WTRU 102a.

[0431] Each of eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, and user scheduling in the uplink and / or downlink, etc. Figure 4 As shown in Figure D, eNode-B 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0432] Figure 4The core network 107 shown in D may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the foregoing elements is depicted as part of the core network 107, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0433] The MME 162 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, activating / deactivating bearers, and selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c. The MME 162 can also provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM or WCDMA.

[0434] Serving Gateway 164 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. Serving Gateway 164 can generally route and forward user data packets to / from WTRUs 102a, 102b, and 102c. Serving Gateway 164 can also perform other functions, such as anchoring the user plane during inter-eNode B handovers, triggering paging when downlink data is available to WTRUs 102a, 102b, and 102c, managing and storing the context of WTRUs 102a, 102b, and 102c, etc.

[0435] Service gateway 164 can also connect to PDN gateway 166, which can provide WTRUs 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0436] Core network 107 can facilitate communication with other networks. For example, core network 107 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional landline communication equipment. For example, core network 107 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between core network 107 and PSTN 108, or can communicate with it. Furthermore, core network 107 can provide WTRUs 102a, 102b, and 102c with access to network 112, which may include other wired or wireless networks owned and / or operated by other service providers.

[0437] Figure 36E This is a system diagram of RAN 105 and core network 109 according to an embodiment. RAN 105 may be an access service network (ASN) that communicates with WTRUs 102a, 102b, and 102c via air interface 117 using IEEE 802.16 radio technology. As will be discussed further below, communication links between different functional entities of WTRUs 102a, 102b, 102c, RAN 105, and core network 109 can be defined as reference points.

[0438] like Figure 36E As shown, RAN 105 may include base stations 180a, 180b, 180c and ASN gateway 182; however, it should be understood that RAN 105 may include any number of base stations and ASN gateways while remaining consistent with the embodiment. Base stations 180a, 180b, and 180c may each be associated with a specific cell in RAN 105 and may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 117. In the embodiment, base stations 180a, 180b, and 180c may implement MIMO technology. Therefore, base station 180a may, for example, use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a. Base stations 180a, 180b, and 180c may also provide mobility management functions such as handover triggering, tunnel establishment, radio resource management, traffic classification, and Quality of Service (QoS) policy enforcement. ASN Gateway 182 can be used as a traffic aggregation point and can be responsible for paging, caching subscriber profiles, routing to the core network 109, etc.

[0439] The air interface 117 between WTRUs 102a, 102b, and 102c and RAN 105 can be defined as an R1 reference point implementing the IEEE 802.16 specification. Furthermore, each of WTRUs 102a, 102b, and 102c can establish a logical interface (not shown) with the core network 109. The logical interface between WTRUs 102a, 102b, and 102c and the core network 109 can be defined as an R2 reference point, which can be used for authentication, authorization, IP host configuration management, and / or mobility management.

[0440] The communication link between each of base stations 180a, 180b, and 180c can be defined as an R8 reference point, which includes protocols for facilitating WTRU handover and data transmission between the base stations. The communication link between base stations 180a, 180b, 180c, and ASN gateway 182 can be defined as an R6 reference point. The R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of WTRUs 102a, 102b, and 102c.

[0441] like Figure 36E As shown, RAN 105 can be connected to core network 109. The communication link between RAN 105 and core network 109 can be defined as an R3 reference point, which includes protocols for, for example, facilitating data delivery and mobility management capabilities. Core network 109 may include a Mobile IP Home Agent (MIP-HA) 184, an Authentication, Authorization, and Accounting (AAA) server 186, and a gateway 188. While each of the foregoing elements is depicted as part of core network 109, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0442] MIP-HA manages IP addresses and enables WTRUs 102a, 102b, and 102c to roam between different ASNs and / or different core networks. MIP-HA 184 provides WTRUs 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110) to facilitate communication between WTRUs 102a, 102b, and 102c and IP-enabled devices. AAA Server 186 handles user authentication and user support services. Gateway 188 facilitates interaction with other networks. For example, Gateway 188 provides WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and legacy terrestrial communication equipment. In addition, gateway 188 can provide access to network 112 to WTRU102a, 102b, 102c, which may include other wired or wireless networks owned and / or operated by other service providers.

[0443] Although not in Figure 36E As shown, but it should be recognized that RAN 105 can connect to other ASNs, and core network 109 can connect to other core networks. The communication link between RAN 105 and other ASNs can be defined as an R4 reference point, which may include protocols for coordinating the mobility of WTRUs 102a, 102b, and 102c between RAN 105 and other ASNs. The communication link between core network 109 and other core networks can be defined as an R5 reference, which may include protocols for facilitating interaction between the home core network and the visited core network.

[0444] The description in this article and Figure 36A , Figure 36C , Figure 36D and Figure 36E The core network entities shown are identified by the names given to those entities in certain existing 3GPP specifications; however, it should be recognized that in the future, those entities and functions may be identified by other names, and some entities or functions may be combined in future 3GPP specifications (including future 3GPP NR specifications). Therefore, Figure 36A , Figure 36B , Figure 36C , Figure 36D and Figure 36E The specific network entities and functions described and illustrated herein are provided as examples only, and it should be understood that the subject matter disclosed and claimed herein can be implemented or realized in any similar communication system, whether as currently defined or in the future.

[0445] Figure 36F This is a block diagram of an exemplary computing system 90, in which implementations can be performed. Figure 36A , Figure 36C , Figure 36D and Figure 36E One or more devices in the communication network shown, such as certain nodes or functional entities in RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, or other network 112. The computing system 90 may include a computer or server and may be primarily controlled by computer-readable instructions, which may be in the form of software, regardless of where or how such software is stored or accessed. These computer-readable instructions may be executed within processor 91 to enable the computing system 90 to function. Processor 91 may be a general-purpose processor, special-purpose processor, conventional processor, digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, controller, microcontroller, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), state machine, etc. Processor 91 may perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable the computing system 90 to operate within the communication network. Coprocessor 81 is an optional processor distinct from the main processor 91, which may perform additional functions or assist processor 91. Processor 91 and / or coprocessor 81 can receive, generate, and process data related to the methods and apparatus disclosed herein.

[0446] During operation, processor 91 fetches, decodes, and executes instructions, and transmits information to and from other resources via the main data transfer path of the computing system, system bus 80. This system bus connects components within the computing system 90 and defines the medium for data exchange. System bus 80 typically includes data lines for transmitting data, address lines for transmitting addresses, and control lines for transmitting interrupts and for the operating system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0447] The memory coupled to the system bus 80 includes random access memory (RAM) 82 and read-only memory (ROM) 93. This memory includes circuitry that allows for the storage and retrieval of information. ROM 93 generally contains stored data that is not easily modified. Data stored in RAM 82 can be read or changed by the processor 91 or other hardware devices. Access to RAM 82 and / or ROM 93 can be controlled by the memory controller 92. The memory controller 92 can provide address translation functionality, which translates virtual addresses into physical addresses during instruction execution. The memory controller 92 can also provide memory protection functionality, which isolates processes within the system and separates system processes from user processes. Therefore, a program running in first mode can only access memory mapped by its own process virtual address space; it cannot access memory in another process's virtual address space unless inter-process memory sharing is configured.

[0448] In addition, the computing system 90 may include a peripheral device controller 83, which is responsible for transmitting instructions from the processor 91 to peripheral devices such as a printer 94, a keyboard 84, a mouse 95, and a disk drive 85.

[0449] A display 86, controlled by a display controller 96, is used to display visual output generated by a computing system 90. This visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). The display 86 may be implemented using a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touchpad. The display controller 96 includes the electronic components required to generate the video signals sent to the display 86.

[0450] Additionally, the computing system 90 may include a communication circuit system, such as, for example, a network adapter 97, which can be used to connect the computing system 90 to an external communication network (such as...). Figure 36A , Figure 36B , Figure 36C , Figure 36D and Figure 36E The communication circuitry can be used to communicate with other nodes or functional entities of those networks (RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, or other networks 112). Alone or in combination with the processor 91, the communication circuitry can be used to perform the transmitting and receiving steps of certain means, nodes, or functional entities described herein.

[0451] It should be understood that any or all of the apparatuses, systems, methods, and processes described herein may be implemented in the form of computer-executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor (such as processor 118 or 91), cause the processor to perform and / or implement the systems, methods, and processes described herein. Specifically, any step, operation, or function described herein may be implemented in the form of such computer-executable instructions that execute on a processor of an apparatus or computing system configured for wireless and / or wired network communication. Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented using any non-transient (e.g., tangible or physical) method or technology for storing information, but such computer-readable storage media do not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, Digital Universal Disc (DVD) or other optical disc storage devices, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, or any other tangible or physical medium that can be used to store desired information and is accessible by a computing system.

Claims

1. An apparatus for configuring a Wireless Transmit / Receive Unit (WTRU), comprising: A processor operatively coupled to a non-transitory memory, the processor being configured to execute the following instructions: The configuration information of the set of CSI-ICM resources for interfering channel measurement is sent to the WTRU group via Radio Resource Control (RRC) signaling to indicate channel state information. Send downlink control information to one WTRU in the group, indicating a subset of CSI-ICM resources from the set of CSI-ICM resources; as well as Feedback on interference measurements based on a subset of CSI-ICM resources is received from one of the WTRUs in the group, wherein the number of CSI-ICM resources in the subset of CSI-ICM resources increases with the number of interference sources.

2. The apparatus of claim 1, wherein the CSI-ICM resources are based on at least one selected from group identifier ID, CSI-ICM resource indication, CSI-ICM feedback indication, channel state information reference signal CSI-RS resource indication, CSI-IM resource indication, CSI feedback configuration, index information of a WTRU in the group, and uplink resources of the WTRU.

3. The apparatus of claim 1, wherein the feedback is based on a channel quality indicator (CQI).

4. The apparatus of claim 3, wherein the feedback is based on rank indicator RI and / or precoder matrix indicator PMI.

5. The apparatus of claim 1, wherein the feedback includes one or more of the following information: an indication of interference measurement, an eigenvector of the interference channel based on the maximum eigenvalue, and a covariance matrix of the interference channel.

6. The apparatus of claim 1, wherein the configuration information indicates all available Channel State Information Reference Signals (CSI-RS) and CSI-ICM resources for interference measurement.

7. An apparatus for configuring a Wireless Transmit / Receive Unit (WTRU), comprising: A processor operatively coupled to a non-transitory memory, the processor being configured to execute instructions including: Receive from the base station channel state information indicating the group used for WTRU and configuration information of the set of interference channel measurement CSI-ICM resources; Receive downlink control information from the base station that indicates a subset of the set of CSI-ICM resources; Measure a subset of CSI-ICM resources; as well as Feedback on interference measurements based on a subset of CSI-ICM resources is sent to the base station, wherein the number of CSI-ICM resources in the subset of CSI-ICM resources increases with the number of interference sources.

8. The apparatus of claim 7, wherein the CSI-ICM resources are based on at least one selected from group identifier ID, CSI-ICM resource indication, CSI-ICM feedback indication, channel state information reference signal CSI-RS resource indication, CSI-IM resource indication, CSI feedback configuration, index information of a WTRU in the group, and uplink resources of the WTRU.

9. The apparatus of claim 7, wherein the feedback is based on a channel quality indicator (CQI).

10. The apparatus of claim 9, wherein the feedback is based on the precoder matrix indicator PMI and / or the rank indicator RI.

11. The apparatus of claim 7, wherein the feedback includes one or more of the following information: an indication of interference measurement, an eigenvector of the interference channel based on the maximum eigenvalue, and a covariance matrix of the interference channel.

12. The apparatus of claim 7, wherein the received downlink control information indicates all available Channel State Information Reference Signals (CSI-RS) and CSI-ICM resources for interference.

Images