Beam-based downlink control signaling
By configuring the multi-beam PDCCH transmission mechanism in the new radio (NR) and optimizing the DMRS design, the challenge of UE receiving control signaling and reference signals in a multi-beam environment is solved, the channel quality and robustness are improved, and NR-PDSCH is realized valid channel estimation and user equipment access.
Patent Information
- Application Number
- CN201880039369.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2017-06-15
- Filing Date
- 2018-06-15
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2038-06-15
AI Technical Summary
In the new radio (NR), there are challenges in the implementation of multi-beam NR-PDCCH transmission, authorization-free transmission and PBCH mechanisms, especially the problem of how UEs can effectively receive and decode control signaling and reference signals on multi-beams.
By configuring public and user-proprietary downlink control information monitoring timing, a multi-beam PDCCH transmission mechanism is designed to support semi-persistent scheduling and beam-pair link changes, and adopting DMRS and CSI-RS designs based on gold sequences to optimize the frequency band of PBCH Edge channel estimation and subcarrier allocation realize multi-beam PDSCH channel estimation.
The UE's control signaling reception robustness and channel quality estimation accuracy in a multi-beam environment are improved, and the anti-interference ability of NR-PDCCH and PBCH is enhanced, ensuring the channel quality of NR-PDSCH and effective access of user equipment.
Smart Images

Figure CN110892664B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 520,203, filed on June 15, 2017, entitled “Beam Based Downlink Control Signaling in New Radio,” the contents of which are incorporated herein by reference. Technical Field
[0003] The present application relates to beam-based downlink control signaling. Background Art
[0004] In the context of New Radio (NR), the following are generally considered: 1) NR-PDCCH (Physical Downlink Control Channel) transmissions; 2) Ungranted transmissions; and 3) Demodulation Reference Signal (DMRS) for Physical Broadcast Channel (PBCH) mechanism (DMRS for PBCH).
[0005] NR-PDCCH transmission supports robustness against beam pair link blocking. Therefore, the UE can be configured to monitor NR-PDCCH on M beam pair links simultaneously, where 1) M ≥ 1, and the maximum value of M may depend on at least the UE capability; and 2) the UE may select at least one beam from the M beams for NR-PDCCH reception. In addition, the UE can be configured to monitor NR-PDCCH on (one or more) different beam pair links in different NR-PDCCH orthogonal frequency division multiplexing (OFDM) symbols, wherein further consideration is given to 1) the NR-PDCCH on one beam pair link is monitored with a shorter duty cycle compared to (one or more) other beam pair links; 2) the time granularity of the configuration, such as slot-level configuration, symbol-level configuration; and 3) this configuration is applicable to scenarios where the UE may not have multiple radio frequency (RF) chains.
[0006] There may be grant-free transmission in NR. It may operate as follows: if the network configures UL data transmission without UL, then grant may be performed after semi-static resource configuration in radio resource control (RRC) without LI signaling. And, if the network configures LI signaling for activating / deactivating and / or modifying parameters of UL data transmission without UL, then grant may be applied.
[0007] DMRS for PBCH can exist in NR. For NR-PBCH transmission, NR only supports a single antenna port based transmission scheme. The same antenna port is defined for NR-Primary Synchronization Signal (NR-PSS), NR-SSS, and NR-PBCH within the SS block. The single antenna port based transmission scheme for NR-PBCH is transparent to the UE. Note that frequency domain PC is excluded.
[0008] The DMRS for NR-PBCH is mapped on each NR-PBCH symbol. For NR, the frequency domain resource element (RE) density of DMRS can also be considered.
[0009] Considering the number of REs required for NR-PBCH, there may be a downward selection RE mapping scheme for DMRS. Option 1, DMRS sequences are mapped on subcarriers at equal intervals. Option 2, DMRS sequences are mapped on subcarriers at unequal intervals (e.g., less or no mapping within the NR-SSS transmission bandwidth).
[0010] The DMRS sequence depends at least on the cell ID. Summary of the invention
[0011] The present invention discloses methods, systems and devices associated with downlink (DL) control, grant-free (GF) transmission or initial access. In particular, the present invention discloses a multi-beam physical downlink control channel (PDCCH) transmission mechanism, a grant-free transmission mechanism, a demodulation reference signal (DMRS) for a physical broadcast channel (PBCH) mechanism, and a DMRS sequence design for a new radio channel state information reference signal (NR-CSI-RS) and a new radio physical downlink shared channel (PDSCH) (NR-PDSCH), etc.
[0012] In an example, a multi-beam PDCCH transmission mechanism may include: 1) configuring monitoring timings for common and user equipment (UE)-specific downlink control information (DCI); 2) configuring CORESET (a common resource set defined by NR) for different beams; 3) indicating changes in monitoring timings due to changes in beam pair links (BPLs) for situations such as semi-persistent scheduling (SPS); 4) a slot structure with both PDCCH and SS blocks appearing in the same slot; or 5) configuring a quasi-co-location (QCL) assumption and indication between PDCCH and SS blocks.
[0013] In an example, the unlicensed transmission mechanism may include: 1) enabling identification of GF uplink (UL) transmissions using GF transmissions in discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) and cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) scenarios; 2) enabling identification of UEs; 3) configuring GF UL control information; or 4) supporting DCI for dynamically configuring GFUL resources.
[0014] In an example, DMRS for PBCH mechanisms may include: 1) configuring DMRS for PBCH decoding while maintaining low intra-beam and intra-cell / inter-cell interference; 2) improving band edge channel estimation for PBCH through unequal DMRS distribution; or 3) PBCH DMRS sequence design and subcarrier allocation methods (e.g., using a golden sequence).
[0015] In addition, a mechanism for the gold sequence based design of DMRS and NR-CSI-RS for NR-PDSCH is disclosed.
[0016] 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 neither intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. In addition, the claimed subject matter is not subject to limitations that solve any or all disadvantages noted in any part of this disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which:
[0018] Figure 1 An exemplary UE monitoring DCI on multiple beams is illustrated;
[0019] Figure 2 illustrates an exemplary BPL for a UE being updated within a monitored resource;
[0020] Figure 3 illustrates an exemplary update in a BPL resulting in a change in a monitored resource;
[0021] Figure 4A illustrates exemplary different monitoring occasions for common search space DCI and UE-specific search space DCI;
[0022] Figure 4B An exemplary method for detecting control information is illustrated;
[0023] Figure 5 illustrates exemplary monitoring opportunities within a mini-slot;
[0024] Fig. 6A illustrates an exemplary CORESET configuration for multi-beam control signaling with control symbol scanning - same CORESET and DCI locations;
[0025] Figure 6B illustrates an exemplary CORESET configuration for multi-beam control signaling with control symbol scanning - same CORESET but different DCI locations;
[0026] Figure 6C illustrates an exemplary CORESET configuration for multi-beam control signaling with control symbol scanning - different CORESET and DCI locations;
[0027] Fig. 7A illustrates an exemplary E CORESET configuration for multi-beam control signaling across time slots - same CORESET and DCI location;
[0028] Figure 7B illustrates an exemplary E CORESET configuration for multi-beam control signaling across time slots - same CORESET but different DCI locations;
[0029] Figure 7C illustrates an exemplary E CORESET configuration for multi-beam control signaling across time slots - different CORESET and DCI locations;
[0030] Figure 8 illustrates exemplary DCIs on different beams for DL grants;
[0031] Fig. 9 illustrates exemplary DCI repetition, which may be robust to blocking; multiple DCI points point to the same grant;
[0032] Fig.10 illustrates an exemplary subframe structure with SS blocks;
[0033] Fig.11A illustrates an exemplary time slot structure for SS block location design;
[0034] Fig. 11B illustrates an exemplary time slot structure for SS block location design;
[0035] Fig. 11C illustrates an exemplary time slot structure for SS block location design;
[0036] Fig.11D illustrates an exemplary time slot structure for SS block location design;
[0037] Fig.11Eillustrates an exemplary time slot structure for SS block location design;
[0038] Fig.11F illustrates an exemplary time slot structure for SS block location design;
[0039] Fig. 12A illustrates an exemplary time slot structure with different DL / UL symbol allocations;
[0040] Fig. 12B illustrates an exemplary time slot structure with different DL / UL symbol allocations;
[0041] Fig. 12C illustrates an exemplary time slot structure with different DL / UL symbol allocations;
[0042] Fig.13A illustrates an exemplary QCL assumption between SS blocks and PDCCH;
[0043] Fig. 13B illustrates an exemplary QCL assumption between SS blocks and PDCCH;
[0044] Fig. 13C illustrates an exemplary QCL assumption between SS blocks and PDCCH;
[0045] Fig.14A illustrates an exemplary GF-RS configuration for DFT-S-OFDM UL continuation;
[0046] Fig. 14B illustrates an exemplary GF-RS configuration for a DFT-S-OFDM UL-comb GF-RS;
[0047] Fig.15 illustrates an exemplary payload area for GF operations that may be shared among multiple users;
[0048] Fig.16 illustrates an exemplary Cp-OFDM-based GF-RS configuration supporting non-contiguous frequency resource allocation;
[0049] Fig.17A illustrates an exemplary GF control region configuration - multiplexed with GF-RS in CP-OFDM;
[0050] Fig. 17B An exemplary GF control region configuration is illustrated - configured in the symbol following the GF-RS in CP-OFDM;
[0051] Fig. 17CAn exemplary GF control region configuration is illustrated - following the GF-RS in DFT-s-OFDM, (D) multiplexed with the payload in DFT-s-OFDM;
[0052] Fig.17D illustrates an exemplary GF control region configuration - multiplexed with payload in DFT-s-OFDM;
[0053] Fig.18 illustrates an exemplary transmission chain for a UL GF control signal;
[0054] Fig.19 An exemplary DMRS RE resource is illustrated as a function of the cell ID;
[0055] Fig. 20A An exemplary DMRS density for PBCH signaling per PRB interleaved between PBCH symbols is illustrated - 1 RE / PRB / symbol;
[0056] Fig. 20B An exemplary DMRS density for PBCH signaling per PRB interleaved between PBCH symbols is illustrated - 1.5 RE / PRB / symbol;
[0057] Fig. 20C An exemplary DMRS density for PBCH signaling per PRB without interleaving between PBCH symbols is illustrated - 1.5 RE / PRB / symbol;
[0058] Fig.20D An exemplary DMRS density for PBCH signaling per PRB interleaved between PBCH symbols is illustrated - 2 REs / PRB / symbol;
[0059] Fig.20E An exemplary DMRS density for PBCH signaling per PRB without interleaving between PBCH symbols is illustrated - 3 REs / PRB / symbol;
[0060] Fig.20F An exemplary DMRS density for PBCH signaling per PRB interleaved between PBCH symbols is illustrated - 3 REs / PRB / symbol;
[0061] Fig.21 illustrates an exemplary OCC for a DMRS pair across PBCH symbols;
[0062] Fig.22A An exemplary DMRS configuration for PBCH is illustrated - DMRS is allocated within the PRBs of PBCH and is evenly distributed among the PRBs;
[0063] Fig. 22BAn exemplary DMRS configuration for PBCH is illustrated - the DMRS extends beyond the PBCH across 1 PRB and is evenly distributed among the PRBs;
[0064] Fig. 22C An exemplary DMRS configuration for PBCH is illustrated - DMRS is allocated within the PRBs of PBCH, but is denser in PRBs near the edge of PBCH;
[0065] Fig.22D An exemplary DMRS configuration for PBCH is shown - DMRS extends beyond PBCH across 1 PRB and is denser at the edge; DMRS in the extended PRB is distributed only in REs close to the edge;
[0066] Fig.22E An exemplary DMRS configuration for PBCH is illustrated - the DMRS in the extended PRBs are less dense than the edge PRBs, but distributed throughout the PRBs;
[0067] Fig.23 An exemplary A SS burst is shown, which consists of N ss_Blk =64, each time slot contains 2 SS blocks;
[0068] Fig.24 illustrates an exemplary display (e.g., a graphical user interface) that may be generated according to methods and systems for beam-based DL control signaling;
[0069] Fig.25A An exemplary communication system is illustrated;
[0070] Fig.25B is a block diagram of an exemplary apparatus or device configured for wireless communications such as a wireless transmit / receive unit (WTRU);
[0071] Fig.25C is a system diagram of a first example radio access network (RAN) and core network;
[0072] Fig.25D is a system diagram of a second example radio access network (RAN) and core network;
[0073] Fig.25E is a system diagram of a third example radio access network (RAN) and core network; and
[0074] Fig.25F is a block diagram of an exemplary computing system in which one or more devices of a communication network, such as certain nodes or functional entities in a RAN, a core network, a public switched telephone network (PSTN), the Internet, or other networks, may be implemented. DETAILED DESCRIPTION
[0075] As discussed in the background, general use of NR-PDCCH transmission, GF transmission, and PBCH design has been considered, but certain issues regarding implementation should be addressed. Regarding multi-beam NR-PDCCH transmission, the UE should be configured to support certain beams and time intervals in which it can receive its NR-PDCCH. This document discloses a way to configure the UE with the correct set of beams to ensure DCI reception. Regarding UL GF transmission, the gNB should detect the presence of GF transmission and correctly identify the corresponding UE. This document discloses a mechanism for robustly identifying the UE ID. Regarding PBCH, unlike LTE, CRS may not exist in NR, so after acquiring the primary synchronization signal (PSS) and the secondary synchronization signal (SSS), some form of DMRS can be used to decode the PBCH. This document discloses a mechanism for channel estimation of auxiliary PBCH. In addition, regarding PDSCH, this document discloses a design for a reference signal sequence to use NR-CSI-RS to assist channel estimation of PDSCH and channel quality estimation.
[0076] Figure 1 is an exemplary illustration of a UE (also referred to herein as a WTRU) monitoring DCI on multiple beams. Slots 1 and 2 carry a first beam (e.g., beam 201), while slots 3 and 4 carry a second beam (e.g., beam 202). The first beam and the second beam point to different spatial directions. There may be multiple beams and each slot may be different, or there may be multiple beams and the beams may appear in the same slot (e.g., slot #0) but on different symbols. The DCI may be carried in a single beam in a slot (a slot of a frame), or on multiple beams in a slot. Different symbols may carry different beams, but a given DCI may be restricted to a single beam or multiple beams. When multiple beams are used, a beam appears on one or more symbols carrying the DCI. There may be different numbers of slots in a frame depending on the numerology. A frame may be 10 ms long. For a 15 KHz parameter set, there are 10 slots. A beam may be defined as a transmission in a certain spatial direction. The DCI in a time slot may be transmitted on one beam (one spatial direction), or alternatively, the DCI in a time slot may be transmitted on multiple beams (different spatial directions), where a certain number of symbols in a time slot corresponds to a given beam (spatial direction).
[0077] Continue to refer Figure 1 , UE (e.g., Fig.25A The WTRU 102c) may monitor multiple beams to receive a PDCCH, wherein the PDCCH includes a DCI. The monitored beams may be from the same or different transmit receive points (TRPs), for example, Fig.25AThe UE may monitor different beams according to a schedule (e.g., a configured monitoring opportunity). The monitoring opportunity defines the time resources when the UE may look for its control information (e.g., DCI in certain time resources). Figure 1 An example is shown in which a UE monitors NR-PDCCH on two beams (e.g., beam 201 and beam 202 in slot #0), which transmit on specific symbols in different slots. The UE can receive DL or UL grants for the link through these two beams.
[0078] The number of monitored control symbols for each beam may be different - some beams carrying NR-PDCCH may be signaled more frequently than other beams, but the UE may be configured to be aware of the occurrence of the beams and the corresponding time and frequency resources. As disclosed herein, the monitoring opportunities, for example, the timing of the beam occurrence pattern and resources, may be configured by one or more of RRC, MAC CE, and DCI updates. This may be accomplished in one of the following example ways. Resources correspond to time resources. DCI may be monitored in a certain spatial direction on certain time resources (such as the first 2 symbols of every other time slot, etc.). Thus, we monitor DCI in a certain direction at a certain time. The spatial direction of the beam may be indicated by a QCL relationship to the direction of a known reference signal (such as an SSB). Thus, the UE may monitor DCI in the same direction as it may monitor the associated reference signal.
[0079] In a first exemplary manner, the time resource may be signaled through RRC. When the beam may be frequently updated due to mobility, blocking, etc., the monitored beam may be notified through DCI or MAC CE. Figure 2 An example is shown where the UE is configured for the following PDCCH monitoring occasions: the first symbols of slots #0, 1, 4, 5, 6, 7, 8, 9 of a frame. In frame #N, the symbol carries beam 201 and beam 202, such as Figure 2 When beam 201 is dropped and beam 203 is configured for the UE, the PDCCH signaling time for the UE remains the same, but the beam changes to beam 203 in slot #5 and slot #8 of the subsequent frame (frame #N+1). If semi-persistent scheduling is used to schedule resources to the UE, and for a given frame, resources have been assigned to the UE, then when a change occurs in the BPL, the DCI can indicate an update to the beam. For example, in Figure 2 , the DCI in slot #4 indicates changes to beam 203 in slot #5 and slot #8 and future frames.
[0080] In the second exemplary embodiment, the beam used for monitoring is configured through RRC, and the time resource is updated through MAC CE or DCI. Here, if the beam is updated, the timing of PDCCH can be updated for the UE. Figure 3 As seen in Figure 1, in frame #N+1, the UE starts monitoring beam 203 in slot #7 and drops beam 201 from slot #5 and onwards. If semi-persistent scheduling is used, then the DCI in slot #4 may indicate the transition to beam 203. Although slot 4 is discussed, other earlier slots are possible. If a beam is blocked (e.g., dropped), then it may be desirable to have some kind of dynamic indication. If there is concern about blocking during this time, then you may want to update the timing resources more dynamically.
[0081] In a third exemplary embodiment, for scenarios that can tolerate more delays (such as mobility), both time resources and beams can be indicated through RRC and MAC CE.
[0082] As disclosed herein, for different types of CORESETs, the monitoring occasions may be different. For example, a UE-specific search space DCI and a common search space DCI may have different configured monitoring occasions, for example, the time position and beam may be different. For example, Figure 4A As shown, the DCI carrying paging can be configured on more beams and more frequently, while the UE-specific search space DCI can be transmitted on fewer beams. The frequency or time or beam direction can be different for different types of DCI. For example, a preemption indication as a set of common PDCCHs can be transmitted with a lower periodicity than UE-specific DCI. The DCI for paging is in a common search space. The CORESET can be flexibly configured to include common or UE-specific search spaces. As shown in FIG. Figure 4AAs seen in the example, some CORESETs may contain only common control search spaces, since paging DCI may require more frequent resources. The UE may decode the CORESET at each opportunity corresponding to whether it is configured to detect UE-specific search space DCI or common search space DCI. In this example, time slots #0, #1, and #2 may be specifically configured to signal common search space DCI to the UE of interest, but they may carry UE-specific search space DCI to other UEs. Other symbols configured within the frame may carry both common search space DCI and UE-specific search space DCI to the UE of interest. It should be understood that the disclosed method allows the number of locations that the UE needs to monitor to be configurable. In addition, each CORESET is configurable, such as the location of the CORESET, the temporal appearance mask of the CORESET, and even the frequency of the CORESET (e.g., not occupying the entire carrier bandwidth). In addition, the UE may receive a control region (e.g., a CORESET) on multiple beams, and have different appearance patterns in time due to different beams.
[0083] Figure 4B An exemplary method for detecting control information is illustrated. At step 121, the UE may acquire one or more RRCs. RRCs are examples of high-level (e.g., not physical layer) signaling that may be used to provide configuration information. RRCs may come from one or more TRPs. At step 122, based on the one or more received RRCs of step 121, the UE may determine one or more monitoring opportunities for a CORESET for one or more beams. As disclosed herein, a beam may be considered as signaling from a certain / certain ports of a TRP in certain spatial directions, and may have a spatial direction similar to that of a known reference signal, for example, the beam may have a spatial QCL relative to the reference signal, so that a receiver receiving the reference signal with a certain antenna configuration may also receive a beam having a spatial QCL with the reference signal using the same receiver antenna configuration. At step 123, based on the monitoring opportunities of step 122, the UE may be configured to monitor one or more beams to obtain control information. The CORESET has a temporal occurrence pattern that may be indicated by the RRC. Information is transmitted on a beam. The UE may be able to receive multiple beams. DCI is sent on multiple beams for redundancy, i.e. if one beam is blocked then another beam can reach the UE. Also, spatial multiplexing increases throughput, so multiple beams are used to signal the DCI. Once the control information is received, the UE acts on it - if it is a grant, then the UE receives the PDSCH or sends the PUSCH. If it is a group common PDCCH such as SFI, then adjust its slot format, if it is a power control command, then the UE adjusts its power, and so on.
[0084] At step 124, at some subsequent time, the UE may receive one or more updated RRCs. At step 124, based on the one or more updated RRCs, the UE may determine one or more updated monitoring opportunities for the CORESET for one or more beams. At step 125, the UE monitors using the updated (one or more) monitoring opportunities. It is contemplated that the updated RRCs may result in different monitoring opportunities being configured compared to those provided at step 122. It should also be understood that the monitoring opportunities may be different for different types of CORESETs (e.g., different types may mean UE-specific search spaces, common search spaces, types of DCTs, etc.). There may be multiple types of search spaces within a CORESET. Different types of DCI may be carried in different search spaces. Different search spaces may carry DCI with different RNTIs, for example, preemption DCI may be carried in a certain search space, while RACH-related DCI may be carried in a different search space. Even if they are all common search spaces, different monitoring opportunities may be configured for these search spaces. Additionally, the UE may have different RNTIs in different CORESETs, and those CORESETs may be configured to have different monitoring occasions; they do not all have to be present at the same time. This exemplary method for detecting control information may allow for flexibility in configuration, enabling the UE to handle different types of DCI differently. Unlike LTE where the CORESET resources are fixed, this provides the flexibility to allocate CORESET resources on the beam that best suits the UE, with appropriate periodicity depending on the DCI type (some DCIs may need to be monitored more frequently than others, e.g., preemptive DCIs may be monitored less frequently than DCIs providing UE-specific grants). The UE may be configured to monitor a CORESET that has a spatial QCL with the SSB.
[0085] Figure 5 An exemplary monitoring opportunity within a mini-slot is illustrated. CORESET resources may be configured within a mini-slot, so a single slot may contain multiple CORESETs for the UE to monitor. In general, PDCCH transmission and monitoring opportunities may also occur in a mini-slot (e.g., smaller than a slot and having anywhere between 2-7 symbols).
[0086] A CORESET for multi-beam PDCCH transmission is disclosed below. The CORESET may be configured in the following manner as shown for the following exemplary case. FIG. 6 shows an example in which the PDCCH is scanned immediately before the PDSCH and other signals are transmitted. The PDCCH may be repeated, and the PDSCH may be transmitted after the scanning of the PDCCH. FIG. 7 shows an example in which the beam scans through the time slots of the PDCCH and the PDSCH / PUSCH / PUCCH. In FIG. 6 , the CORESET may include multiple symbols signaled on different beams. The CORESET may be followed by the PDSCH / PUSCH / PUCCH. In FIG. 7 , only one beam may be used to signal the CORESET. Each beam may be transmitted on a different CORESET.
[0087] like Fig. 6A and Fig. 7A As shown in , for the monitored beams, the CORESET can be the same and the DCI can appear in the same position. The frequency position of the DCI is the same, but the timing of beams 201 and 202 is different.
[0088] like Figure 6B and Figure 7B As shown in , for the monitored beams, the CORESET can be the same, but the DCI can appear at different locations within the CORESET. Note that when the CORESET is the same, the CORESET configuration overhead is smaller.
[0089] like Figure 6C and Figure 7C As shown in , the CORESETs are on different resources of the beams. This is particularly applicable when the UE may operate on different frequency regions for different beams. The UE may be configured with the CORESET resources as well as the periodicity and spatial QCL information to monitor the DCI. The configuration process is similar to the previously discussed case (e.g., Figure 4B ). The UE monitors the received signal accordingly for its DCI. After receiving a valid DCI after blind decoding the monitored resources, the UE operates according to the control information.
[0090] Different ways of configuring the CORESET have the following technical effects. In FIG. 6 , it is possible to scan the DCI with less latency compared to FIG. 7 because the monitoring opportunities of the UE in the CORESET occur one after another. In FIG. 7 , the configuration of the CORESET is simpler and may require less overhead compared to FIG. 6 . Reference Figure 6B , 7B , the CORESET is the same between beams. This can be particularly useful when the CORESET tends to be wideband and occupies most of the UE's receive bandwidth. Figure 6C and Figure 7C ,On different beams, the CORESET (especially the frequency region) can be different to adapt to the channel characteristics of the UE.
[0091] Figure 8 The figure shows exemplary DCIs on different beams for DL granting. The DCIs on different beams may be different, for example, they may perform different PDSCH grants. Figure 8 As shown in , the UE monitors beam 201 and beam 202 and receives different DL grants on the corresponding DCI. Here, the DL assignments can be for different hybrid automatic repeat request (HARQ) processes, or different redundancy versions (RVs) for HARQ processes, or the same RV for HARQ processes (e.g., for robustness or reliability). Reliability can mean a lower BLER, and robustness can be considered with respect to having a link (e.g., not being blocked).
[0092] Fig. 9 An exemplary DCI repetition is illustrated, which can be robust to blocking; multiple DCIs point to the same grant. DCI can be repeated on different beams to improve robustness to blocking and greater reliability. Therefore, if the UE cannot correctly decode the DCI on one beam, it can still successfully decode the DCI on another beam. For example, DCI is repeated on beam 201 and beam 202, and both indicate cross-slot DL grants, such as Fig. 9 Here, the UE is configured to monitor the PDCCH on beam 201 and beam 202. Beam 201 and beam 202 perform the same grant. In addition, refer to Fig. 9 It will be appreciated that repeating DCIs (especially on different beams) gives the UE a high chance of receiving at least one DCI. When repeated DCIs provide grants, the DCIs may all indicate the same set of resources for the grant. A possible benefit is that the UE may be guaranteed to receive at least one DCI.
[0093] Fig.10 FIG. 1 shows an exemplary subframe structure with SS blocks. Here, the detailed structure of the time slot may include SS blocks. In one subframe, both time slots may include SS blocks, or only one may include SS blocks, such as Fig.10. In this example, slot 2 in subframe 2 contains no SS blocks and can be PDSCH, PUSCH, etc. Each SS block can include transmissions that the UE should look for for its initial synchronization. A typical use of SS blocks is that each SS block is a beam. Therefore, if the UE scans these different SS blocks and determines that it can listen on one or two or other subsets of the SS blocks, then the UE knows that with a certain receiver configuration it can listen in certain directions in space.
[0094] In NR, the length of the time slot can be 7 symbols or 14 symbols. The front-loaded PDCCH can be 1-3 symbols. The SS block occupies 4 symbols, including one symbol PSS, one symbol SSS and two symbols PBCH. The position of the SS block in the time slot can be: 1) fixed position: in the 4th-7th symbol; or 2) after the front-loaded (one or more) PDCCH symbols.
[0095] For the case of 7 symbol slots, Figures 11A-11F The time slot structure is shown in Fig.11A , Fig. 11B and Fig. 11C In the case of PDCCH loaded 1-3 symbols ahead, the SS block is located in the 4th to 7th symbols. Fig.11A , Fig.11D , Fig.11E and Fig.11F In the case of 14-symbol slots, the SS block is located at the symbol next to the front-loaded PDCCH. The same position principle applies to the 14-symbol slot case.
[0096] The usage of symbols next to the SS block depends on the number of remaining symbols (N). For example, if N<2, then the remaining symbols can only be used for DL, for example Fig.11D as shown in .
[0097] If N=2, then symbols may be used for DL-only and UL-only. Fig.11D An example of a DL-only use case is shown. Fig.11F An example of a UL-only use case is shown.
[0098] If N>2, then the symbol can be used for DL only, UL only, and DL+UL. (The N>2 case occurs in a 14-symbol slot). Fig. 12A An example of a DL-only use case is shown. Fig. 12B An example of a DL+UL use case is shown. Fig. 12C An example of a UL-only use case is shown.
[0099] In NR, the PDCCH and SS blocks within a slot can be transmitted on the same beam or on different beams. Even for each symbol of the PDCCH, different symbols can be transmitted on different beams. Therefore, no QCL assumption can be made between the PDCCH and SS blocks. Within one slot carrying the SS block and PDCCH, the relationship may be unknown for the spatial direction. However, in similar scenarios, the QCL relationship between the PDCCH and SS blocks can be exploited to reduce overhead and computational complexity. Figures 13A-13C An exemplary QCL assumption between SS blocks and PDCCH is illustrated. In FIG13 , a QCL relationship may exist between PDCCH and SS blocks within a block, which is applicable to both the case of 7-symbol slots and the case of 14-symbol slots.
[0100] Taking the 7-symbol time slot as an example, Fig.13A In this case, the spatial QCL parameters and the QCL of the large-scale parameters about {delay spread, Doppler spread, Doppler shift, average gain or average delay} can be established between the SS block and the PDCCH. Fig. 13B In the example, an SS block is transmitted on one beam and a PDCCH, which can be 1-3 symbols, is transmitted on another beam. For this example, the two beams are transmitted to the same direction and can be QCLed with respect to spatial QCL parameters. Symbols 1-3 (#0-#2 are PDCCH) can be on a narrower beam than symbols 4-7 (#3-#6). As shown in the figure, QCL can be performed based on spatial parameters and non-spatial (e.g., large-scale) parameters. Fig. 13CIn the example, two or three symbols may be used to transmit the PDCCH. In this example, the two or three symbols are transmitted on different beams (slightly different angles) pointing in the same direction and different from the beams used for the SS blocks. In this case, the beams used for the PDCCH can be QCLed with each other with respect to the spatial QCL parameters, and all beams can be QCLed with the beams used for the SS blocks with respect to the spatial QCL parameters. Knowing these QCL relationships between the PDCCH and the SS blocks, the UE can use the same beam as used for the SS blocks to receive the PDCCH, or the UE can reuse information collected from the SS blocks for channel estimation for the PDCCH, etc. Since there are many different scenarios and no default QCL assumption can be made in NR, the QCL relationship between the PDCCH and the SS blocks can be indicated to the UE via RRC signaling or MAC-CE from the TRP. The indication can be explicit or implicit. Explicit can be considered as configuring the QCL information to the UE. For example, a UE-specific CORESET is configured with certain QCL relationships with reference signals. Therefore, the UE uses this information to receive the corresponding DCI. Implicit can be considered as the QCL information is known a priori. For example, the RMSI CORESET is implicitly QCL with the SSB detected by the UE.
[0101] NR can use control signaling on DL and UL to facilitate UL unlicensed transmission. This article discloses a method for identifying unlicensed UL transmission and identifying a UE that performs unlicensed transmission. A reference signal (RS) sequence can be used to identify the presence of unlicensed transmission. In the following, this RS is referred to as a unlicensed reference signal (GF-RS). The GF-RS can be assigned to each unlicensed UE. In general, the sequence can be orthogonal or quasi-orthogonal to minimize cross-correlation between UEs. A specific GF-RS with certain time-frequency resources and cyclic shifts can correspond to certain time-frequency resources used for GF payloads. GF-RS can be used for channel estimation as much as possible.
[0102] For DFT-s-OFDM-based UL, GF-RS can take the form of Zadoff-Chu (ZC) sequences. They can be assigned in a comb-like manner on frequency resources in symbols with a repetition factor N to keep the peak-to-average power ratio (PAPR) bounded. When N=1, the sequence uses consecutive resource elements (REs).
[0103] Figure 14A-14B An exemplary GF-RS configuration for DFT-S-OFDM UL is shown. Fig.14AIn , N=1 is used, and the UE's GF-RS can occupy all allocated frequency resources in that symbol. Multiple GF-RS sequences with different cyclic shifts can be signaled simultaneously in those resources, and each sequence corresponds to a preconfigured set of resources in which a payload is carried. Fig. 14B In , N=2 is used and the GF-RS sequence is interleaved. When some GF-RS are not transmitted, the corresponding payload resources are empty.
[0104] In general, the GF payload may have reserved resources corresponding to each cyclic shift so that no collision occurs if the GF-RS overlap. Fig.15 An exemplary payload area for GF operation that can be shared among multiple users is illustrated, wherein GF payloads can collide with each other within a specific resource set. Fig.15 In , payload resources are shared by multiple GF UEs, and orthogonal spreading codes or low-rate codes can be used to make the UEs orthogonal.
[0105] For UL unlicensed operation based on cyclic prefix-OFDM (CP-OFDM), the GF-RS may be non-contiguous in frequency to allow frequency diversity of the payload. The RS is front-loaded to enable fast detection of unlicensed transmissions. Fig.16 An example is shown in . The payload region may be frequency multiplexed with GF-RS.
[0106] Because there may be situations where the number of UEs may be very large compared to the number of available sequences or resources, the same resources may be assigned to multiple UEs. Therefore, UE identification should be performed after identification of the presence of a grant-free transmission. A UE ID, such as a C-RNTI (16 bits), may be transmitted with the payload. Alternatively, the network may assign a grant-free RNTI (GF-RNTI) of less than 16 bits (e.g., 8 bits) to the UE, and this GF-RNTI may be transmitted with the payload. Figures 17A-17D An exemplary GF control region configuration is illustrated. Fig.17A and Fig. 17B An example of CP-OFDM with UE's GF UL control resources in the leading symbols of the payload region is shown. Fig. 17C and Fig.17D An example of DFTS-S-OFDM is shown where the GF UL control resources are contiguous with full symbols or partial symbol resources multiplexed with payload circuits.
[0107] UL GF control information (such as payload size, MCS, HARQ process ID, RV, etc.) can be encoded together. The UE ID can be applied as a mask to the CRC attached to the control information. Depending on the size of the payload, reedmuller (RM) or polar coding can be applied to the control information. Fig.18 An example of how the UE ID may be sent along with the payload is shown. Quadrature Phase Shift Keying (QPSK) may be used for control information. Rate matching may depend on the amount of available GF resources, the MCS for the data payload, and the target block error rate (BLER) for the payload and UL control. Fig.18 , which can be considered to show the encoding of DL control information. The UE can transmit UL control information in a similar manner as for GF transmission. At step 251, the payload may include MCS, TBS (size of the transport block), etc. At step 252, the CRC applied to the payload may be masked with the GF-RNTI. These bits of the masked CRC may be attached to the payload. These bits may be encoded (step 253), rate matched (step 254), modulated and multiplexed with other signals (such as PUSCH) (step 255) and transmitted in the UL. The gNB can rely on successfully decoding the GF-RNTI to detect the UL control information.
[0108] DL Control Signaling in Grant-Unlicensed Transmissions. The following is a list of possible contents of the DCI. Dynamic signaling via the DCI may be used to configure one or more of the following parameters for grant-unlicensed signaling: 1) enabling or disabling grant-unlicensed transmissions in one or more time slots; 2) configuring the UL time and frequency resources available for grant-unlicensed signaling in one or more time slots; 3) indicating a single set of DMRS resources or a pool of DMRS resources that may be used for grant-unlicensed signaling; or 4) indicating possible modulation and coding schemes that the UE may use for grant-unlicensed signaling. For example, with respect to the fourth parameter, the gNB may indicate a limited set of valid MCSs that may be used for grant-unlicensed transmissions (depending on the perceived UL interference in the grant-unlicensed resources). And, the gNB may blindly decode the received grant-unlicensed signal to obtain a valid list of MCSs. An explicit indication of the MCS is not required on the UL. Alternatively, since the set of valid MCSs may be small, the UE may use a few bits to indicate the MCS. The fifth parameter may include an indication of a power level or an equivalent metric to enable the UE to select an appropriate MCS for transmission. For example, with respect to the fifth parameter, if unlicensed transmissions can occur in resources carrying eMBB transmissions, then the level of interference due to eMBB transmissions can be communicated by the gNB to the unlicensed UEs so that they can adjust their modulation and coding accordingly.
[0109] The DMRS design for PBCH may include: 1) the DMRS sequence is a function of the cell ID; 2) the DMRS position is a function of the cell ID (e.g., Fig.19 As shown, the RE of DMRS within a symbol can vary with the cell ID); or 3) the DMRS sequence or resource can be a function of the SS block timing.
[0110] NR may specify a DMRS density between 8% and 33% of the PBCH resources. Simulations show that densities within that range are useful. Figure 20 shows examples of different RS densities ranging from 1 RE per RB per symbol to 3 REs per RB per symbol. In addition, by distributing the DMRS REs evenly between the 2 PBCH symbols, the desired DMRS density can be achieved. The DMRS REs in the 2 symbols can be staggered relative to each other ( Fig. 20A , Fig. 20B , Fig.20D , Fig.20F ) or can occupy the same frequency resources ( Fig. 20C , Fig.20E ).
[0111] In addition, if Fig.21 As shown in , the same DMRS sequence can be used in two symbols, and OCC can be used on the DMRS pair across 2 symbols to reduce inter-beam interference, intra-cell interference or inter-cell interference. In this example, OCC with a weight of [1, -1] is applied to the DMRS REs in the two symbols.
[0112] Figures 22A-22E FIG. 4 shows an exemplary DMRS configuration for PBCH. PBCH may occupy 24 RBs per symbol. Fig.22A As shown in , due to the discontinuity of PBCH-DMRS, the channel estimation may be poor at the edge of this 24 RB area. Figure 22B-Figure 22E ) is an implementation method that can enhance channel estimation at the band edge of PBCH.
[0113] exist Fig. 22B In the PBCH, DMRS can extend beyond PBCH across 1 PRB and be evenly distributed between PRBs. The DMRS resources for PBCH can exceed 24 RBs. The signals in these extended RBs can be rate matched or punctured to accommodate the PBCH DMRS. Fig. 22B Such an example is shown. The DMRS resources may be partially or fully extended by additional RBs.
[0114] exist Fig. 22CIn , DMRS can be allocated within the PRB of PBCH, but more densely in the PRB near the edge of PBCH. Fig. 22C As seen in Figure 1, DMRS resources can be denser in RBs near the edge, where RBs in the edge have 3 DMRS REs / RB / symbol, while RBs not at the edge carry only 2 DMRS REs / RB / symbol. DMRS are denser in RBs at the edge compared to RBs in non-edge areas. The density can be measured by the number of DMRS REs per RN per symbol.
[0115] Both variable density and extended DMRS allocation can be applied, such as Fig.22D and Fig.22E As shown in Fig.22D In , the DMRS in the extension region has a lower density (on a per RB basis) than the band edge RBs and partially occupies the DMRS REs in that RB. Fig.22E In the example, the DMRS in the extension region has a lower density (on a per RB basis) than the band edge RBs, but occupies REs that span the bandwidth of the RBs. Note that the wider the DMRS REs in the extension region, the better the suppression of band edge ringing in the channel estimation.
[0116] In an SS burst block, PBCH-DMRS can be used for PBCH data demodulation.
[0117] The DMRS sequence r(m) for PBCH is defined by
[0118]
[0119] Where c(i), i=1, ..., Q is the basic sequence used for PBCH-DMRS, Q is the PBCH DMRS length, n s is the SS block ID within the SS burst set. The base sequence c(i) can be constructed from the golden sequence or the m-sequence. The pseudo-random sequence generator can be initialized by the following function
[0120]
[0121] in is the cell ID derived from PSS and SSS, and n s is the SS block timing index (or offset) within the SS burst set. s It can be defined in the following formula:
[0122] n s =0,...N SS_Blk -1,
[0123] Where NSS_Blk is the number of SS blocks in the SS burst set. SS burst set design, SS blocks and indication n S The timing is Fig.23 Given in (assuming SCS = 120KHz):
[0124] exist Fig.23 In the SS burst set, the number of SS blocks in the SS burst set is set to 64, for example, N SS_Blk =64, and there are 2 SS blocks in each time slot. Fig.23 In this example, the SS burst set has completed scanning 64 beams within 4ms. The pseudo-random sequence generator can be initialized using the following formula:
[0125]
[0126] n′ s =n s
[0127]
[0128] where δ = 2 r -1, r is a positive integer and may depend on the parameter set. For example, when r = 4, δ = 15. The value τ is greater than A positive integer, where N PN Indicates the length of the golden or PN sequence polynomial, such as N PN =31 or 63. The value n in PBCH DMRS s Can be used as a timing indication of an SS block (SS Block ID) within an SS burst.
[0129] The DMRS sequence to resource element can be described by the following method:
[0130]
[0131] in is between the kth subcarrier (RE) and the nth s SS block, p is the port ID (e.g., p=0), and m′ is the mapping function of the DMRS sequence index m. For example, the subcarrier mapping can be defined in the following formula:
[0132] k=Δ·m+mod(v shift , Δ),
[0133] where mod(·) is the modular operation, Δ is the DMRS interval, for example, Δ=2 to Δ=4, v shift is a shift variable, defined as
[0134]
[0135] In addition, with the power boost option, the PBCH DMRS can have a different power allocation than the PBCH data. The power boost indication can be signaled via the SSS. The SSS can carry 1 or 2 bits of information (via PBSK or QPSK on the SSS) to indicate the power boost of the PBCH DMRS. The power boost (or power offset) indication can depend on the information bit. For example, if BPSK is used, then 0 may indicate no power boost, while 1 may indicate the presence of a power boost. The power boost value should be known to the UE, such as a predefined value.
[0136] Sequence design for NR-CSI-RS, DMRS for PDSCH - In NR, the PN sequence is defined by a golden sequence of length 31. This golden sequence can be used for NR-RS (which is PBCH-DMRS, PDCCH-DMRS, PDSCH-DMRS, and CSI-RS).
[0137] Assume that the length of the output golden sequence c(n) is N PN ={31}, where n=0, 1, ..., N PN -1, then the PN sequence design can be specified as follows
[0138] c(n)=(x1(n+N c )+x2(n+N c ))mod 2
[0139] x1(n+31)=(x1(n+3)+x1(n))mod 2
[0140] x2(n+31)=(x2(n+3)+x2(n+2)+x2(n+1)+x2(n))mod 2
[0141] Where N C is a scaler, for example N C = 1600, and the first m sequence should use x1(0) = 1, x1(n) = 1, n = 1, 2, ..., N PN -1. x2 is initialized by indicates that its value depends on the application of the sequence.
[0142] For NRCSI-RS, the reference signal sequence Defined by:
[0143]
[0144] where n sis the slot number within the radio frame, and l is the OFDM symbol number within the slot. The pseudo-random sequence c(i) is defined above, and μ is the number of ports allocated for CSI-RS in a subframe, which is a function of the parameter set. The pseudo-random sequence generator should be used at the beginning of each OFDM symbol. Initialization, where
[0145]
[0146]
[0147]
[0148] For a PDSCH-DMRS antenna port p∈{P, P+1, ..., P+N p -1}, where N p is the maximum number of PDSCH-DMRS ports, and the reference signal sequence r(m) is defined by
[0149]
[0150] Where μ1 is the number of ports allocated for PDSCH-DMRS in a subframe for a normal cyclic prefix and μ2 is the number of ports allocated for PDSCH-DMRS in a subframe for an extended cyclic prefix. Both μ1 and μ2 are functions of the parameter set. For example, the value of μ1 in a 120kHz parameter set will be different from the value of μ1 in a 60kHz parameter set. The pseudo-random sequence c(i) is as described above. The pseudo-random sequence generator shall be initialized at the beginning of each subframe using the following formula
[0151]
[0152] Table 1 provides exemplary abbreviations used herein.
[0153] Table 1: Abbreviations
[0154]
[0155]
[0156]
[0157]
[0158] Fig.24An exemplary display (e.g., a graphical user interface) that can be generated based on the methods and systems for beam-based DL control signaling as disclosed herein is illustrated. A display interface 901 (e.g., a touch screen display) can provide text associated with beam-based DL control signaling in box 902, such as parameters related to GF control regions, indications of changes in monitoring opportunities, and identification of GF UL transmissions using GF-RS in DFT-s-PFDM and CP-OFDM scenarios, etc., as disclosed herein. The progress of any step discussed herein (e.g., messages sent or success of the step) can be displayed in box 902. In addition, graphical output 902 can be displayed on display interface 901. Graphic output 903 can be a topology of devices implementing the methods and systems for beam-based DL control signaling, a graphical output of the progress of any method or system discussed herein, time slots in use, etc.
[0159] The Third Generation Partnership Project (3GPP) develops technical standards for cellular telecommunication 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 standards. 3GPP has begun work on the standardization of the next generation of cellular technology, known as New Radio (NR), also referred to as "5G". The development of the 3GPP NR standards is expected to include the definition of the next generation radio access technology (new RAT), which is expected to include the provision of new flexible radio access below 6 GHz, and the provision of new ultra-mobile broadband radio access above 6 GHz. Flexible radio access is expected to include new, non-backwards compatible radio access in new spectrum below 6 GHz, and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a wide set of 3GPP NR use cases with different requirements. Ultra-mobile broadband is expected to include cmWave and mmWave spectrum, which will provide opportunities for ultra-mobile broadband access for, for example, indoor applications and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with sub-6 GHz flexible radio access, with cmWave- and mmWave-specific design optimizations.
[0160] 3GPP has identified a variety of use cases that NR is expected to support, resulting in various user experience requirements for data rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, ultra-high broadband access indoors, broadband access in crowds, ubiquitous 50+Mbps, ultra-low-cost broadband access, in-vehicle mobile broadband), critical communications, massive machine-type communications, network operations (e.g., network slicing, routing, migration and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communications. Specific services and applications in these categories include, for example, surveillance and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connectivity, car e-calling, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile Internet, and virtual reality, among others. All of these use cases and others are contemplated herein.
[0161] Fig.25A An example communication system 100 is illustrated in which methods and apparatus for beam-based DL control signaling, such as those described and claimed herein, may be implemented. Figures 1 to 23 Systems and methods shown. As shown, the example communication system 100 may include a wireless transmit / receive unit (WTRU) 102a, 102b, 102c, or 102d (generally or loosely referred to as WTRU 102), a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, but it should be appreciated that the disclosed examples contemplate any number of WTRUs, base stations, networks, or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e may be any type of device or apparatus configured to operate or communicate in a wireless environment. Although each WTRU 102a, 102b, 102c, 102d, 102e may be configured to communicate in a wireless environment, the WTRU 102a, 102b, 102c, 102d, 102e may be configured to communicate in a wireless environment, such as a wireless communication network, a wireless communication network, or a wireless communication network. Fig.25A , Fig.25B , Fig.25C , Fig.25D and Fig.25E, but it should be understood that for the various use cases envisioned for 5G wireless communications, each WTRU may include or be implemented in any type of device or apparatus configured to transmit or receive wireless signals, including, by way of example only, a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a consumer electronics product, a wearable device (such as a smart watch or smart clothing), a medical or e-health device, a robot, an industrial equipment, a drone, a vehicle (such as a car, truck, train or airplane, etc.).
[0162] The communication system 100 may also include a base station 114a and a base station 114b. The base station 114a may be any type of device configured to wirelessly connect to at least one of the WTRUs 102a, 102b, 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, or other networks 112. The base station 114b may be any type of device configured to wirelessly connect to at least one of the RRHs (remote radio heads) 118a, 118b or TRPs (transmit receive points) 119a, 119b to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, or other networks 112. The RRHs 118a, 118b may be any type of device configured to wirelessly connect to at least one of the WTRUs 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, or other networks 112. The TRPs 119a, 119b may be any type of device configured to wirelessly connect to at least one of the WTRUs 102d to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, or other networks 112. The base stations 114a, 114b may be, for example, base transceiver stations (BTS), Node-Bs, eNode Bs, Home Node Bs, Home eNode Bs, site controllers, access points (APs), wireless routers, etc. Although the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations or network elements.
[0163] The base station 114a may be part of the RAN 103 / 104 / 105, which may also include other base stations or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114b may be part of the RAN 103b / 104b / 105b, which may also include other base stations or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. For the methods and systems of beam-based DL control signaling disclosed herein, the base station 114a may be configured to send or receive wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The base station 114b may be configured to send or receive wired or wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an example, the base station 114a may include three transceivers, for example, one transceiver for each sector of the cell. In an example, the base station 114a may employ multiple-input multiple-output (MIMO) technology and, therefore, may use multiple transceivers for each sector of the cell.
[0164] The base station 114a may communicate with one or more of the WTRUs 102a, 102b, 102c over an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).
[0165] The base station 114b may communicate with one or more of the RRHs 118a, 118b and / or TRPs 119a, 119b via a wired or air interface 115b / 116b / 117b, which may 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.). The air interface 115b / 116b / 117b may be established using any suitable radio access technology (RAT).
[0166] The RRH 118a, 118b or TRP 119a, 119b may communicate with one or more WTRUs 102c, 102d via an air interface 115c / 116c / 117c, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115c / 116c / 117c may be established using any suitable radio access technology (RAT).
[0167] More specifically, as described above, the communication system 100 may be a multiple-access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b and TRPs 119a, 119b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink Packet Access (HSDPA) or High Speed Uplink Packet Access (HSUPA).
[0168] In an example, the base station 114a and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b and TRPs 119a, 119b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively, using Long Term Evolution (LTE) or LTE-Advance (LTE-A). In the future, the air interface 115 / 116 / 117 may implement 3GPP NR technology.
[0169] In an example, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b and TRPs 119a, 119b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d may implement radio technologies such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.
[0170] For example, Fig.25A The base station 114c in the example may be a wireless router, a Home NodeB, a Home eNodeB, a gNB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area (such as a business location, a home, a vehicle, a campus, etc.) for implementing the methods and systems for beam-based DL control signaling as disclosed herein. In an example, the base station 114c and the WTRU 102e may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an example, the base station 114c and the WTRU 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In another example, the base station 114c and the WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or a femtocell. Fig.25A As shown in FIG, base station 114b may have a direct connection to the Internet 110. Therefore, base station 114c may not be required to access the Internet 110 via core network 106 / 107 / 109.
[0171] The RAN 103 / 104 / 105 or the RAN 103b / 104b / 105b may be in communication with a core network 106 / 107 / 109, which may be any type of network configured to provide voice, data, applications, or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., or perform high-level security functions (such as user authentication).
[0172] Although not in Fig.25A 105b or RAN 103b / 104b / 105b or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 or RAN 103b / 104b / 105b or a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105 or RAN 103b / 104b / 105b, which may utilize an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) that employs a GSM radio technology.
[0173] The core network 106 / 107 / 109 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired or wireless communication networks owned or operated by other service providers. For example, the networks 112 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 103 / 104 / 105 or the RAN 103b / 104b / 105b or a different RAT.
[0174] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, 102d, and 102e may include multiple transceivers for communicating with different wireless networks over different wireless links. Fig.25A The WTRU 102e shown in FIG. 1 may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114c, which may employ an IEEE 802 radio technology.
[0175] Fig.25B 1 is a block diagram of an example apparatus or device (such as, for example, WTRU 102) configured for wireless communication according to the examples described herein. Fig.25BAs shown in , the example WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It should be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the example. Moreover, the example contemplates that the base stations 114a and 114b or the nodes that the base stations 114a and 114b may represent (such as but not limited to transceiver stations (BTS), node Bs, site controllers, access points (APs), home node-Bs, evolved home node-Bs (eNodeBs), home evolved node-Bs (HeNBs), home evolved node-B gateways, and proxy nodes, etc.) may include Fig.25B Some or all of the elements described in and described herein.
[0176] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of 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. The processor 118 may perform signal coding, data processing, power control, input / output processing, or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Fig.25B The processor 118 and the transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0177] The transmit / receive element 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via the air interface 115 / 116 / 117. For example, in an example, the transmit / receive element 122 may be an antenna configured to transmit or receive RF signals. Fig.25A Although not shown in the figure, it will be appreciated that the RAN 103 / 104 / 105 or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT or a different RAT as the RAN 103 / 104 / 105. For example, in addition to being connected to the RAN 103 / 104 / 105, which may employ an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) employing a GSM radio technology.
[0178] The core network 106 / 107 / 109 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired or wireless communication networks owned or operated by other service providers. For example, the networks 112 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 103 / 104 / 105 or a different RAT.
[0179] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks over different wireless links, for implementing the methods and systems for beam-based DL control signaling as disclosed herein. For example, Fig.25A The WTRU 102c shown in FIG. 1 may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
[0180] Fig.25B 1 is a block diagram of an example apparatus or device, such as, for example, a WTRU 102 (eg, a UE involving multi-beam PDCCH transmission or UE 104), configured for wireless communication according to the methods and systems for beam-based DL control signaling disclosed herein. Fig.25BAs shown in , the example WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the example. Moreover, the examples herein contemplate that the base stations 114a and 114b or nodes that the base stations 114a and 114b may represent (such as, but not limited to, transceiver stations (BTS), Node Bs, site controllers, access points (APs), home node Bs, evolved home node Bs (eNodeBs), home evolved node Bs (HeNBs), gNBs, home evolved node B gateways, and proxy nodes, etc.) may be included in Fig.25B Some or all of the elements depicted in the drawings may be exemplary implementations of the disclosed systems and methods for device triggering described herein.
[0181] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of 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. The processor 118 may perform signal coding, data processing, power control, input / output processing, or any other function that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Fig.25B The processor 118 and transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.
[0182] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from a base station (e.g., base station 114a) via an air interface 115 / 116 / 117. For example, in an example, the send / receive element 122 may be an antenna configured to send or receive an RF signal. In an example, the send / receive element 122 may be a transmitter / detector configured to, for example, send or receive an IR, UV, or visible light signal. In yet another example, the send / receive element 122 may be configured to send and receive RF and light signals. It should be appreciated that the send / receive element 122 may be configured to send or receive any combination of wireless signals.
[0183] In addition, although the transmit / receive element 122 is Fig.25B Although depicted as a single element in the figure, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in an example, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117.
[0184] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (e.g., such as UTRA and IEEE 802.11).
[0185] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, or the display / touchpad / indicator 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other examples, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown). The processor 118 may be configured to control a lighting pattern, image, or color on the display or indicator 128 in response to whether a setup associated with a multi-beam PDCCH transmission is successful or failed in some examples described herein, or otherwise indicate the status of beam-based DL control signaling and related components. Controlling the lighting pattern, image, or color on the display or indicator 128 may reflect the figures illustrated or discussed herein (e.g., Figures 1 to 23The message and process of beam-based DL control signaling are disclosed herein. The message and process can be extended to provide an interface / API for a user to request resources related to resources via an input source (e.g., speaker / microphone 124, keypad 126, or display / touchpad / indicator 128), and to request, configure, or query information related to beam-based DL control signaling and other content that can be displayed on the display 128.
[0186] The processor 118 may receive power from the power source 134 and may be configured to distribute or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.
[0187] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 115 / 116 / 117 or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method, while remaining consistent with the examples.
[0188] The processor 118 may also be coupled to other peripherals 138, which may include one or more software or hardware modules that provide additional features, functionality, or wired or wireless connectivity. For example, the peripherals 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, modules, FM radio units, digital music players, media players, video game player modules, internet browsers, etc.
[0189] The WTRU 102 may be implemented in other devices or equipment, such as sensors, consumer electronics, wearable devices (such as smart watches or smart clothing), medical or e-health equipment, robots, industrial equipment, drones, vehicles (such as cars, trucks, trains or airplanes), etc. The WTRU 102 may be connected to other components, modules or systems of such devices or equipment via one or more interconnect interfaces (such as an interconnect interface that may include one of the peripheral devices 138).
[0190] Fig.25C 1 is a system diagram of the RAN 103 and the core network 106 that may implement the methods and systems for beam-based DL control signaling as disclosed herein. As described above, the RAN 103 may employ a UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 115. The RAN 103 may also be in communication with the core network 106. Fig.25C As shown in FIG. 1 , the RAN 103 may include Node-Bs 140a, 140b, 140c, each of which may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 115. The Node-Bs 140a, 140b, 140c may each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and RNCs while remaining consistent with the example.
[0191] like Fig.25C As shown, Node B 140a, 140b can communicate with RNC 142a. In addition, Node B 140c can communicate with RNC 142b. Node B 140a, 140b, 140c can communicate with corresponding RNC 142a, 142b via Iub interface. RNC142a, 142b can communicate with each other via Iur interface. Each of RNC 142a, 142b can be configured to control the corresponding Node B 140a, 140b, 140c connected thereto. In addition, each of RNC 142a, 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, data encryption, etc.
[0192] Fig.25C The core network 106 shown in FIG. 1 may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, or a gateway GPRS support node (GGSN) 150. Although each of the foregoing elements is depicted as part of the core network 106, it should be appreciated that any of these elements may be owned or operated by an entity other than the core network operator.
[0193] The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
[0194] The RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0195] As described above, core network 106 may also be connected to networks 112, which may include other wired or wireless networks owned or operated by other service providers.
[0196] Fig.25D 1 is a system diagram of the RAN 104 and the core network 107 that may implement the methods and systems for beam-based DL control signaling as disclosed herein. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the core network 107.
[0197] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with the example. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an example, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
[0198] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in uplink or downlink, etc. Fig.25DAs shown in FIG. , the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.
[0199] Fig.25D The core network 107 shown in FIG. 1 may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. Although each of the foregoing elements is depicted as part of the core network 107, it should be appreciated that any of these elements may be owned or operated by an entity other than the core network operator.
[0200] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.
[0201] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface. The serving gateway 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The serving gateway 164 may also perform other functions, such as anchoring the user plane during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing the contexts of the WTRUs 102a, 102b, 102c, and the like.
[0202] The serving gateway 164 may also be connected to the PDN gateway 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0203] The core network 107 may facilitate communications with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the core network 107 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the core network 107 and the PSTN 108. In addition, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned or operated by other service providers.
[0204] Fig.25E 1 is a system diagram of the RAN 105 and the core network 109 that may implement the methods and systems for beam-based DL control signaling as disclosed herein. The RAN 105 may be an access service network (ASN) that employs IEEE 802.16 radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 117. As discussed further below, the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, the RAN 105, and the core network 109 may be defined as reference points.
[0205] like Fig.25E As shown in the figure, the RAN 105 may include base stations 180a, 180b, 180c and an ASN gateway 182, but it should be appreciated that the RAN 105 may include any number of base stations and ASN gateways while remaining consistent with the example. The base stations 180a, 180b, 180c may each be associated with a specific cell in the RAN 105 and may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 117. In the example, the base stations 180a, 180b, 180c may implement MIMO technology. Thus, the base station 180a, for example, may use multiple antennas to send wireless signals to the WTRU 102a and receive wireless signals from the WTRU 102a. The base stations 180a, 180b, 180c may also provide mobility management functions, such as handover triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy implementation, etc. The ASN gateway 182 may serve as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 109, and the like.
[0206] The air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as an R1 reference point that implements the IEEE 802.16 specification. In addition, each of the WTRUs 102a, 102b, and 102c may establish a logical interface (not shown) with the core network 109. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, or mobility management.
[0207] The communication link between each of the base stations 180a, 180b, and 180c may be defined as an R8 reference point, which includes protocols for facilitating WTRU handovers and data transfer between the base stations. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 may 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 the WTRUs 102a, 102b, 102c.
[0208] like Fig.25E As shown in , the RAN 105 may be connected to a core network 109. The communication link between the RAN 105 and the core network 109 may be defined as an R3 reference point, which includes protocols for facilitating, for example, data transfer and mobility management capabilities. The core network 109 may include a mobile IP home agent (MIP-HA) 184, an authentication, authorization, accounting (AAA) server 186, and a gateway 188. While each of the foregoing elements is depicted as part of the core network 109, it will be appreciated that any of these elements may be owned or operated by an entity other than the core network operator.
[0209] The MIP-HA may be responsible for IP address management and may enable the WTRUs 102a, 102b, and 102c to roam between different ASNs or different core networks. The MIP-HA 184 may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, and 102c and IP-enabled devices. The AAA server 186 may be responsible for user authentication and supporting user services. The gateway 188 may facilitate interworking with other networks. For example, the gateway 188 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communication devices. In addition, the gateway 188 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and operated by other service providers.
[0210] Although in Fig.25E Not shown, but it will be appreciated that the RAN 105 may be connected to other ASNs, and the core network 109 may be connected to other core networks. The communication link between the RAN 105 and the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 105 and the other ASNs. The communication link between the core network 109 and the other core networks may be defined as an R5 reference, which may include protocols for facilitating interworking between a home core network and a visited core network.
[0211] This article describes and Fig.25A , Fig.25C , Fig.25D and Fig.25E The core network entities shown in are identified by the names given to those entities in certain existing 3GPP specifications, but it should be recognized that in the future, those entities and functions may be identified by other names, and that certain entities or functions may be combined in future specifications published by 3GPP (including future 3GPP NR specifications). Fig.25A , Fig.25B , Fig.25C , Fig.25D and Fig.25E The specific network entities and functionality described and illustrated in the present disclosure are provided by way of example only, and it should be understood that the subject matter disclosed and claimed herein may be implemented or realized in any similar communication system, whether currently defined or defined in the future.
[0212] Fig.25Fis a block diagram of an exemplary computing system 90 in which Fig.25A , Fig.25C , Fig.25D and Fig.25E 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, wherever or in any manner such software is stored or accessed. Such computer-readable instructions may be executed within the processor 91 to enable the computing system 90 to operate. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of 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. The processor 91 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables the computing system 90 to operate in a communication network. The coprocessor 81 is an optional processor different from the main processor 91, which may perform additional functions or assist the processor 91. The processor 91 or the coprocessor 81 may receive, generate, and process data related to the methods and apparatus for beam-based DL control signaling disclosed herein, such as a change in monitoring opportunity due to a change in BPL.
[0213] In operation, processor 91 fetches, decodes and executes instructions, and transfers information to and from other resources via the computing system's main data transfer path (system bus 80). Such a system bus connects components in computing system 90 and defines a medium for data exchange. System bus 80 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the bus. An example of such a system bus 80 is a PCI (Peripheral Component Interconnect) bus.
[0214] The memory coupled to the system bus 80 includes a random access memory (RAM) 82 and a read-only memory (ROM) 93. Such memory includes a circuit system that allows information to be stored and retrieved. ROM 93 generally contains stored data that is not easily modified. The data stored in RAM 82 can be read or changed by a processor 91 or other hardware device. Access to RAM 82 or ROM 93 can be controlled by a memory controller 92. The memory controller 92 can provide an address translation function that translates a virtual address into a physical address when an instruction is executed. The memory controller 92 can also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Therefore, a program running in the first mode can only access memory mapped by its own process virtual address space; unless memory sharing between processes has been set up, it cannot access memory within the virtual address space of another process.
[0215] In addition, the computing system 90 may include a peripheral device controller 83 that 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 .
[0216] The display 86 controlled by the display controller 96 is used to display the visual output generated by the computing system 90. Such 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 with a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch pad. The display controller 96 includes the electronic components required to generate the video signal sent to the display 86.
[0217] Additionally, computing system 90 may include communications circuitry, such as a network adapter 97, which may be used to connect computing system 90 to an external communications network, such as a Fig.25A , Fig.25B , Fig.25C , Fig.25D and Fig.25E The RAN 103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110 or other network 112) of the present invention can be used to enable the computing system 90 to communicate with other nodes or functional entities of those networks. Alone or in combination with the processor 91, the communication circuit system can be used to perform the sending and receiving steps of certain devices, nodes or functional entities described herein.
[0218] It should be understood that any or all of the devices, 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), causes the processor to perform 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 executed on a processor of a device or computing system configured for wireless or wired network communication. Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented in 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 technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, cassette, tape, disk storage or other magnetic storage device, or any other tangible or physical medium that can be used to store desired information and can be accessed by a computing system.
[0219] In describing the preferred methods, systems or apparatus of the subject matter of the present disclosure (such as beam-based DL control signaling as shown in the accompanying drawings), specific terminology is used for clarity. However, the claimed subject matter is not intended to be limited to the specific terminology so selected, and it is to be understood that each specific element includes all technical equivalents that operate in a similar manner to achieve a similar purpose.
[0220] Various techniques described herein can be implemented in combination with hardware, firmware, software or in combination thereof when appropriate. Such hardware, firmware and software can reside in the device at each node of the communication network. The device can be operated individually or in combination with each other to implement the method described herein. As used herein, the terms "device", "network device", "node", "equipment", "network node" etc. can be used interchangeably. In addition, unless otherwise provided herein, the word "or" is generally used inclusively.
[0221] This written description uses examples to disclose the invention, including the best mode, and also enables any person skilled in the art to practice the invention, including making and using any device or system and performing any combined method. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art (e.g., skipping steps, combining steps, or adding steps between the exemplary methods disclosed herein). If such other examples have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements that do not differ substantially from the literal language of the claims, then it is intended that these other examples be included within the scope of the claims.
[0222] A base station performing wireless communication has a means for sending a message to a device via RRC, MAC CE or DCI update, wherein the message to the device includes an instruction to configure a monitoring opportunity. A device, method or computer-readable storage medium may provide a means for detecting control information as disclosed herein. The method, system, computer-readable storage medium or device has a device for determining one or more monitoring opportunities for control information of multiple beams, wherein one or more monitoring opportunities are configured by one or more first multiple radio resource controls (RRCs), and wherein the control information has a temporal occurrence pattern; and based on the monitoring opportunity, multiple beams are monitored. The control information may include time resources for multiple beams or frequency resources for multiple beams. Multiple beams may come from one or more transmit-receive points (TRPs). For different types of common resource sets, one or more monitoring opportunities may be different. Monitoring may be for a common resource set having a spatial quasi-co-location with an SS block. Monitoring may be for a common resource set configured by a transmit-receive point as quasi-co-location with an SS block. Monitoring may be for a common resource set configured by a transmit-receive point as quasi-co-location with an SS block based on RRC. The device may be a user equipment or a TRP. All combinations in this paragraph (including removal or addition of steps) are contemplated in a manner consistent with the rest of the detailed description.
Claims
1. A method for detecting control information, the method comprising: monitoring, by a wireless transmit / receive unit (WTRU), control information during one or more monitoring occasions, wherein the control information is received using a first beam, wherein the first beam is based on a physical downlink control channel (PDCCH) transmission quasi-co-located with a synchronization signal block (SSB); and receiving, by the WTRU, downlink control channel spatial information using the first beam based on the one or more monitoring occasions, wherein the SSB is received using a second beam and the PDCCH transmission is received using the first beam, wherein the first beam and the second beam are received in the same direction and the SSB and PDCCH transmissions are quasi-co-located with respect to a spatial quasi-co-location parameter, and wherein the WTRU adjusts the receiver antenna configuration based on the quasi-co-location of the SSB and the PDCCH transmissions.
2. The method of claim 1, wherein: The one or more monitoring occasions are different for different types of common resource sets.
3. The method of claim 1, wherein: The one or more monitoring occasions are configured using radio resource control (RRC) signaling.
4. The method of claim 1, further comprising obtaining a plurality of downlink control information (DCI), wherein: Each of the plurality of DCIs indicates a respective physical downlink shared channel grant, wherein each of the plurality of DCIs indicates the same respective frequency resource for the respective physical downlink shared channel grant. The method of claim 1 , further comprising activating or deactivating the grant-free resources based on downlink control information.
6. The method of claim 1, further comprising obtaining time and frequency resources for grant-free transmission based on downlink control information.
7. The method of claim 1, further comprising transmitting control signaling for the unlicensed resources in uplink control information, wherein the transmission includes a user equipment identifier.
8. A device for detecting control information, the device comprising: processor; as well as A memory coupled to the processor, the memory including executable instructions stored thereon, the executable instructions, when executed by the processor, causing the processor to perform operations including: monitoring the control information at one or more monitoring opportunities, wherein the control information is received using a first beam, wherein the first beam is based on a physical downlink control channel (PDCCH) transmission quasi-co-located with a synchronization signal block (SSB); and receiving downlink control channel spatial information using the first beam based on the one or more monitoring occasions, wherein the SSB is received using a second beam and the PDCCH transmission is received using the first beam, wherein the first beam and the second beam are received in the same direction and the SSB and PDCCH transmissions are quasi-co-located with respect to a spatial quasi-co-location parameter, and wherein the device adjusts the receiver antenna configuration based on the quasi-co-location of the SSB and the PDCCH transmissions.
9. The apparatus of claim 8, wherein the apparatus is a wireless transmit / receive unit (WTRU).
10. The apparatus of claim 8, the operations further comprising obtaining time and frequency resources for grant-free transmission based on downlink control information.
11. The apparatus of claim 8, the operations further comprising transmitting control signaling for the unlicensed resources in uplink control information, wherein the transmission includes a user equipment identifier.
12. The apparatus of claim 8, the operations further comprising encoding a payload size, a modulation coding scheme, and a redundancy version together in the control information.
13. The apparatus of claim 8, the operations further comprising obtaining a plurality of downlink control information (DCI), wherein: Each of the plurality of DCIs indicates a respective physical downlink shared channel grant, wherein each of the plurality of DCIs indicates the same respective frequency resource for the respective physical downlink shared channel grant.
14. The apparatus of claim 8, the operations further comprising activating or deactivating the grant-free resources based on downlink control information.
15. The device of claim 8, wherein: The one or more monitoring occasions are configured using radio resource control (RRC) signaling.
16. A computer-readable storage medium storing computer-executable instructions, which when executed by a computing device cause the computing device to perform operations comprising: monitoring the control information at one or more monitoring opportunities, in, The control information is received using a first beam, wherein the first beam is based on a physical downlink control channel (PDCCH) transmission quasi-co-located with a synchronization signal block (SSB); as well as receiving downlink control channel spatial information using the first beam based on the one or more monitoring occasions, wherein the SSB is received using a second beam and the PDCCH transmission is received using the first beam, wherein the first beam and the second beam are received in the same direction and the SSB and PDCCH transmissions are quasi-co-located with respect to a spatial quasi-co-location parameter, and wherein the computing device adjusts the receiver antenna configuration based on the quasi-co-location of the SSB and the PDCCH transmissions.
17. The computer-readable storage medium of claim 16, wherein: The one or more monitoring occasions are configured using radio resource control (RRC) signaling.
18. The computer-readable storage medium of claim 16, the operations further comprising activating or deactivating the grant-exempt resources based on downlink control information.
19. The computer-readable storage medium of claim 16, the operations further comprising obtaining time and frequency resources for grant-free transmission based on downlink control information.
20. The computer-readable storage medium of claim 16, the operations further comprising transmitting control signaling for the unlicensed resources in uplink control information, wherein the transmission includes a user equipment identifier.
