Control channels for Uplink (UL) and Downlink (DL) New Radio (NR) have a beam centric architecture. While the NR Downlink Control Information (DCI) is precoded, the DL control signaling on multiple beams is currently undefined. Protocols to support channel estimation for DL control signals are needed in NR.
In high carrier frequencies, phase noise becomes a significant problem. Tracking RS (TRS) aids in estimating and compensating for phase noise. Resource allocations for Demodulation Reference Signals (DMRS) and TRS have not been finalized in NR.
SRS design for UL, especially in a beam centric architecture, has not been addressed in NR. Techniques for assigning SRS resources on multiple beams and in multiple numerologies is needed.
Currently in LTE, Channel State Information Interference Channel Measurement (CSI-ICM) is used to measure the interference power configured in RRC signaling. Interference may be caused by MIMO transmissions or beams from similar or different Transmission and Reception Points (TRP)s. As the number of interference sources increase, the number of interference hypotheses exponentially increase in turn. Because one CSI-ICM resource is required for each interference hypothesis, a large overhead for DL transmission is realized. This potentially limits a NR node's flexibility for scheduling MU-MIMO.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not 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. Furthermore, the claimed subject matter is not limited to limitations that solve any or all disadvantages noted in any part of this disclosure.
In one aspect of the application, a frame structure in new radio is described. The frame structure includes a self-contained transmission time interval. The transmission interval includes a control information region including plural beams, and a downlink transmission channel region including plural beams. The downlink control information is swept through the time interval. Subsequently, an uplink or downlink grant resource is swept through the time interval.
In another aspect of the application, a frame structure operating in new radio is described. The frame structure includes a transmission bandwidth, which includes a timeslot for control and data signaling. The timeslot has a first numerology and a second numerology. The first numerology supports a first subcarrier spacing. The second numerology supports a second subcarrier spacing. Further, a fixed time slot includes a beam having a sounding reference signal.
In yet another aspect, a method for configuring user equipment. The method includes a step of configuring a set of ‘K’ channel state information interference channel measurement (CSI-ICM) and channel state interference reference signal (CSI-RS) resources for a group of user equipment. The method also includes a step of indicating, for one of the user equipment in the group, at least ‘N’ of the ‘K’ CSI-ICM resources via dynamic signaling based on interference. The method also includes a step of transmitting downlink control information including the CSI-ICM to the group; a CSI-RS (and CSI-interference channel measurement) protocol to the user equipment. The method further includes a step of receiving, from the UE in the group, feedback of the CSI and CSI-ICM for the interference channel. The method even further includes a step of scheduling a MU-MIMO transmission for the user equipment. The method yet even further includes a step of determining a cancelation of interference transmitted from one user equipment to other co-scheduled UEs. There has thus been outlined, rather broadly, certain embodiments of the invention in order that the detailed description thereof may be better understood, and in order that the present contribution to the art may be better appreciated.
In order to facilitate a more robust understanding of the application, reference is now made to the accompanying drawings, in which like elements are referenced with like numerals. These drawings should not be construed to limit the application and are intended only to be illustrative.
A detailed description of the illustrative embodiment will be discussed in reference to various figures, embodiments and aspects herein. Although this description provides detailed examples of possible implementations, it should be understood that the details are intended to be examples and thus do not limit the scope of the application.
Reference in this specification to “one embodiment,” “an embodiment,” “one or more embodiments,” “an aspect” or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. Moreover, the term “embodiment” in various places in the specification is not necessarily referring to the same embodiment. That is, various features are described which may be exhibited by some embodiments and not by the other.
Generally, the application is directed to methods and systems for reference signal designs and control channel designs for NR systems. In order to meet the requirements of the NR systems, enhancements related to reference signal and control channel design for NR can be employed. The application is also directed to mechanisms for control channel designs including techniques to assign resources for NR-DCI and waveforms for UL signaling. Mechanisms to aid control channel estimation and allocation of UL and DL resources within sub-bands can limit the computational burden on the UE.
Another aspect of the application is directed to mechanisms for reference signal designs. Solutions for DMRS and TRS design for NR are employed. Mechanisms can support resource allocation and cell/beam wide RS allocation and UE-specific RS allocation.
Resource allocation for NR-SRS in multiple beams and across multiple numerologies are described. Precoded SRS can be supported. Mechanisms for CSI based measurements are described. The following methods can enable CSI ICM and can make it more efficient: (i) A new RRC signaling, informs the UE about necessary information of configuration, such as RS location, code book information; (ii) a CSI-ICM resource set where CSI-ICM resources within the set may be dynamically shared among UEs. A two-step CSI-ICM configuration to support CSI-ICM and reduce the latency. Step 1 is to pre-configure a set of K CSI-ICM resources for all the UEs through RRC signaling. In step 2, for a given UE, dynamically indicate N (N>=1) CSI-ICM resources from a total of K based on the interference hypothesis to enable CSI-ICM measurement by dynamic signaling through DCI or dynamic signaling through MAC CE.
According to another embodiment, group-based CSI-ICM configuration through DCI is used to enable multiple UEs measuring the interference channel. The UEs can be grouped by experiencing the same interference hypothesis. According to yet another embodiment, a new NR PUCCH format to support CSI-ICM reporting is envisaged. In yet another embodiment, a new NR DCI design is envisaged to enable UE interference cancellation for MU-MIMO. In yet another embodiment, a procedure of interference channel measurement and interference cancellation for NR MU-MIMO is described.
According to another aspect, mechanisms for dynamic CSI-RS resource allocation are described. Two methods for RRC based configuration of CSI-RS pooling resources are envisaged. In the first technique, a UE-specific CSI-RS resources configuration is employed without configuration of a group of UEs sharing the same CSI-RS resource pool. In a second technique, a UE-specific CSI-RS resources configuration is employed with configuration of a group of UEs sharing the same CSI-RS resource pool.
Several signaling designs to dynamically indicate UE's CSI-RS resource and reporting are described (i) CSI measurement command signaled in MAC CE; and (ii) CSI measurement command signaled in DCI including: (a) CSI measurement command piggyback on DCI; (b) Standalone CSI measurement command (sent on a separate DCI) for a specific UE; and (c) Group-based DCI to schedule multiple UEs' CSI-RS measurement and feedback.
The mechanisms discussed herein may be conducted at the NR-node, Transmission and Reception Point (TRP) or Remote Radio Head (RRH). Accordingly, it is envisaged that the NR-node, TRP and RRH are interchangeable even though the NR-node is used in most exemplary descriptions or illustrations.
The time interval contains DL and/or UL transmissions are flexible for different numerologies and RAN slices and may be statically or semi-statically configured. The time interval structure may be used for a slot or a mini-slot within a subframe. The mechanisms for this time interval structure may be applicable to slot and/or mini-slot even though the exemplary descriptions and/or illustration figures use slot or mini-slot.
The following acronyms are used for the terms and phrases below:
DL Reference Signals (RS)s are predefined signals occupying specific Resource Elements (RE)s within the downlink time-frequency RE grid. The LTE specification includes several types of DL RSs transmitted in different ways for different purposes [E. Dahlman, S. Parkvall, J. Skold, “4G LTE/LTE-Advanced for Mobile Broadband,” second edition, 2014].
Cell-specific Reference Signals (CRS): CRS are used: (1) by User Equipments (UEs) for channel estimation for coherent demodulation of DL physical channels; and (2) by UEs to acquire Channel State Information (CSI); (3) by UEs for measurements of cell-selection and handover.
Demodulation Reference Signals (DM-RS): DM-RS are referred to as UE-specific reference signals, and are (1) used for channel estimation by a specific UE and only transmitted within the RBs specifically assigned for PDSCH/ePDCCH transmission to that UE, and (2) associated with data signals and precoded prior to the transmission with the same precoder as data.
Channel State Information Reference Signals (CSI-RS): CSI-RS are intended to be used by UEs to acquire CSI for channel-dependent scheduling, link adaptation and multi-antenna transmissions.
Uplink Reference Signals
Similar to LTE DL, reference signals are also used in LTE UL. Two types of reference signals are defined for LTE UL [“4G LTE/LTE-Advanced for Mobile Broadband”].
UL Demodulation Reference Signals (DM-RS): DM-RS is used by the base station for channel estimation for coherent demodulation of Physical Uplink Shared Channel (PUSCH) and Physical Uplink Control CHannel (PUCCH). DM-RS are only transmitted within the RBs specifically assigned for PUSCH/PUCCH transmission and are spanning the same frequency range as the corresponding physical channel.
UL Sounding Reference Signals (SRS): SRS is used by the base station for CSI estimation for supporting uplink channel-dependent scheduling and link adaptation. SRS are also used for the base station to obtain CSI estimation for DL under the case of channel reciprocity.
CSI Feedback in LTE
DL channel-dependent scheduling is a key feature of LTE, which selects the DL transmission configuration and related parameters depending on the instantaneous DL channel condition, including the interference situation. To support the DL channel-dependent scheduling, a UE provides the CSI to the evolved Node B (eNB). The eNB uses the information for its scheduling decisions.
The CSI consists of one or several pieces of information [“4G LTE/LTE-Advanced for Mobile Broadband”] including:
Rank Indication (RI): provide a recommendation on the transmission rank to use or, number of preferred layers that should be used for PDSCH transmission to the UE.
Precoder Matrix Indication (PMI): indicate a preferred precoder to use for PDSCH transmission.
Channel-Quality Indication (CQI): represent the highest modulation-and-coding scheme to achieve a block-error probability of at most 10%.
Together, a combination of the RI, PMI, and CQI forms a CSI feedback report to eNB. What is included in the CSI report depends on the UE's configured reporting mode. For example, RI and PMI do not need to be reported unless the UE is in a spatial multiplexing multi-antenna transmission mode.
Downlink Control Information
The Downlink Control Information (DCI) is a predefined format in which the DCI is formed and transmitted in Physical Downlink Control Channel (PDCCH). The DCI format tells the UE how to get its data which is transmitted on Physical Downlink Shared Channel (PDSCH) in the same subframe. It carries the details for the UE such as number of resource blocks, resource allocation type, modulation scheme, redundancy version, coding rate, etc., which help UE find and decode PDSCH from the resource grid. There are various DCI formats used in LTE in PDCCH.
New Radio (NR) Frame Structure
Currently, 3GPP standardization efforts are underway to define the NR frame structure. Consensus is to build the so called ‘self-contained’ time intervals for NR. As illustrated in
New Radio Requirements
3GPP TR 38.913 [3GPP TR 38.913 Study on Scenarios and Requirements for Next Generation Access Technologies; (Release 14), V0.2.0] defines scenarios and requirements for Radio (NR) technologies. The Key Performance Indicators (KPIs) for eMBB, URLLC and mMTC devices are summarized in Table 1 below.
Reference Signal Definition for NR
The following has been agreed upon at the 3GPP RAN1 #86bis meeting for the NR Reference Signal (RS) supported for downlink:
CSI-RS: Reference signal with main functionalities of CSI acquisition, beam management.
FFS: RRM measurement
DM-RS: Reference signal with main functionalities of data and control demodulation
Reference signal for phase tracking
Reference signal for time/freq. tracking
Reference signal for Radio link monitoring
RS for RRM measurement
At least the following RSs are supported for NR uplink:
SRS: Reference signal with main functionalities of CSI acquisition, beam management
DM-RS: Reference signal with main functionalities of data and control demodulation
Reference signal for phase tracking
FFS: Reference signal for RRM measurement
DL channel-dependent scheduling is a key feature of LTE, which selects the DL transmission configuration and related parameters depending on the instantaneous DL channel condition, including the interference situation. To support the DL channel-dependent scheduling, UE provides the CSI to the evolved Node B (eNB). The eNB uses the information for its scheduling decisions.
The CSI consists of one or several pieces of information: (i) Rank Indication (RI); (ii) Precoder Matrix Indication (PMI); (iii) Channel-Quality Indication (CQI). Together, a combination of the RI, PMI, and CQI forms a CSI feedback report to eNB. What is included in the CSI report depends on the UE's configured reporting mode. CSI report could be configured to be periodic or aperiodic by RRC signaling.
Aperiodic CSI Reporting Using PUSCH
Aperiodic reporting is triggered by DCI formats, and could be used to provide more detailed reporting via PUSCH. A UE is semi-statically configured by higher layer to feedback CQI and PMI and corresponding RI on the same PUSCH using one of the following CSI reporting modes given in Table 1 below. In sub-frame n, a CSI request can be transmitted in DCI format 0 and DCI format 4, which schedule a PUSCH transmission that carry aperiodic CSI report in sub-frame n+k.
For each of the transmission modes in Table 2 above, different reporting modes are defined and supported on PUSCH.
Periodic CSI Reporting Using PUCCH
For periodic CSI reporting, UE is semi-statically configured by higher layers to periodically feedback different CSI components (CQI, PMI, and/or RI) on the PUCCH using the reporting modes given in Table 3. The periodic CSI reporting is configured by higher layer signaling (RRC).
For each of the transmission modes defined in Table 3 above, different periodic CSI reporting modes are defined and supported on PUCCH.
Mechanisms for Control Channel Designs
According to an aspect of the application, architectures and techniques for DL and UL control signals for NR are provided. Solutions are described herein for resource allocation and reference signal design for NR-DCI.
In one embodiment, NR-DCI resource allocation in a beam centric architecture is described. Here, the 3GPP spec can support transmission of NR-DCI on multiple beams to improve coverage and reliability. Note that LTE supported only broadcast of the PDCCH. The beams may sweep through different spatial locations carrying NR-DCI as shown in
In this proposal, the beams carrying control information sweep through the space before the UL/DL grant resources are made available as shown in
If the UE location is known a-priori, its UE-specific NR-DCI can be transmitted only in a subset of the beams. If the UE location is not known to the NR-Node, its NR-DCI may be transmitted in every beam. This concept in illustrated in
Similarly, NR-DCI for common control signaling may be carried in every beam. The common control search space uses the same subcarriers in all the beams carrying the control information—minimizes the overhead to indicate different common control signaling resources for each beam.
In another embodiment, each beam may carry multiple symbols including control and data as shown in
According to another embodiment, solutions for RS design for NR are proposed. Certain types of NR-DCI such as common control signals may be transmitted for beam-wide reception. The NR-DCI can leverage the beam-RS which is intended for identifying a beam and for measurements of a beam for also estimating the channel.
If NR-DCI is transmitted through multiple ports (as in transmit diversity) a new form of “Control-RS” with appropriate density may be introduced to aid channel estimation of NR-DCI. This control-RS would be transmitted for each port that is supported for NR-DCI transmission. This control-RS may be cell/beam specific and its location and resources may depend on one or more of the following: (i) Cell ID; and (ii) Beam ID.
The control-RS may be transmitted to cover channel estimation for the entire frequency range of the DCI symbols or may be transmitted in a limited region where DCIs transmitted with those ports are mapped in frequency.
Certain types of NR-DCI, especially UE-specific signals may be precoded to improve spatial separation and coverage. For such use cases, “control-DMRS” may be introduced to aid in channel estimation.
According to yet another embodiment, the NR-DCI may use a fixed number of control signals or fixed duration for control signaling in every transmission interval. This could be a slot or mini-slot or subframe. For such a design, NR does not need to transmit a PCFICH-like channel as the control signaling resource is fixed. The control signaling resource may be indicated through critical system information such as the MIB or SIB1/SIB2 or may be set to fixed values in the spec.
Alternatively, the spec may specify the number of symbols for each numerology. The number of symbols may depend on one or more of the following: (i) center frequency; (ii) bandwidth; and (iii) number of beams supported.
According to a further embodiment, NR has support for large bandwidths exceeding 80 MHz. If a UE is required to blindly decode the NR-DCI across the entire bandwidth it will experience significant latency and battery drain. As a result, NR must allow transmission of the NR-DCI to a UE in specific subbands. The UE must be configured to have knowledge of the resources of these subbands.
The UE-specific NR-DCI may be indicated within a limited number of resources (subbands) which are known apriori at the UE. The subbands may be configured semi-statically through RRC and MAC CE updates.
The search space for common control signaling may carry NR-DCI such as those for paging, RACH response, etc. be limited to specific subbands so that UEs do not have to blindly decode all the resources in the common control signaling search space.
The common control signaling search space may be partitioned into multiple search spaces and UE may be assigned to search for the common NR-DCI only within a subset of those search spaces.
Similar to the solution described above for subband operation for UE-specific and common NR-DCI, Physical DL shared channel (NR-PDSCH) carrying the data may also be restricted to subbands. This limits the number of times the UE's front end has to be re-tuned to a new frequency for reception. The subbands for NR-PDSCH may be semi-statically configured through RRC and MAC CE updates.
According to a further embodiment, the UE may be configured to transmit within a subband rather than the entire bandwidth to limit the amount of front end and receiver processing. Accordingly the UL resources would be constrained within a subband. The subband may be preconfigured semi-statically through RRC or MAC CE updates or specified dynamically through the UL grant.
In an embodiment, it is envisaged that the waveform (CP-OFDM or DFT-S-OFDM) is assigned to a UE by the network. Here, the NR-Node makes the decision for the UE on which waveform to use. NR-Node can decide the waveform for the UE based on feedback from UE (such as beam or cell measurements or CQI) or from SRS or other RS on the UL. The configuration of the waveform may be done in the following ways:
According to another aspect of the application, it is envisaged to support a wide range of user mobility scenarios with low-latency in NR, reference signaling may be enhanced in DL NR. DM-RS location within a slot/mini-slot or subframe should be flexible and adaptive to scenario-specific performance requirements. For example,
For a scenario where the UEs have low mobility, the DM-RS could be placed at the end of a minislot ‘i’, and be used to provide channel estimates to subframes ‘i’ and ‘i+1’. Similarly, DM-RS can be shared between multiple UEs. For UEs 1 and 2 that have consequent RBs in the same band, the DM-RS could be placed at the end of subframe ‘1’, and be used to provide channel estimates to two subframes belonging to different users.
In
NR can support PRB bundling and allow flexible location of DMRS resources in the bundled PRBs. In
The resource assignment of DM-RS can be either dynamic or semi-static. Dynamic signaling can be done through DCI. The specification may specify a list of possible DM-RS patterns (locations and sequences) out of which one may be assigned to a UE. The assigned resource may be indicated through an index into the list. When semi-static signaling is used, RRC or MAC CE updates will indicate the DM-RS configurations. It is envisaged the DM-RS will in general have same numerology as data.
In an embodiment, Tracking Reference Signals (TRS) for phase tracking in NR is described. Here, phase noise increases with increasing carrier frequency, thereby making it an important issue to solved in NR. The following solutions address phase tracking in NR.
TRS may not be sent all the time. Tracking RS need only be sent when needed and not always. This is important to avoid costly transmission overhead brought by TRS transmission. One or more of the following factors may influence the choice of switching TRS on or off:
Modulation order: The absence of phase tracking RS will have a much more deteriorating effect on BLER when data is higher order modulated compared to when it is lower order modulated.
Carrier frequency: Increasing carrier frequency will necessitate the need turn on Tracking RS.
UE speed: Increasing UE speed will increase the Doppler implying the need to turn on Tracking RS.
Sub-carrier Spacing: Increased sub-carrier spacing will increase inherent immunity of system to carrier frequency offset, thereby reducing the need for Tracking RS.
TRS may be UE specific or cell specific. On/Off signaling for tracking RS may be done via distinct signaling depending on whether it is UE specific or cell-specific. If it is UE specific then it may be configured via RRC signaling and turned on/off through RRC signaling/MAC CE updates or dynamically through the DCI. If TRS is cell/beam wide then system information may be used to signal its presence and resources.
In case of UE specific TRS, tracking RS may be precoded. In addition, location and sequence of Tracking RS may depend on one or more of beam ID, cell ID, and UE specific resources, such as for example, a root/shift of a sequence assigned to the UE or location of the DL resources for the UE.
In case of cell/beam wide TRS, TRSs are transmitted in resources that are known to all UEs. TRSs could be a function of one or more of: (a) Cell ID; and (b) Beam ID. TRS transmission could be configured on one or more ports. In some instances, it may be sufficient to track phase by transmitting TRS on a single port. As a result, TRS on a single port may be supported by default. However, NR must also support more ports for TRS. The resources for the ports maybe configured for both cell/beam wide and UE specific use cases through DCI or RRC signaling.
According to yet another embodiment, NR Sounding reference signal on UL (NR-SRS) is described. Since NR will support different numerologies, NR-SRS numerology and resources must allocated in a manner compatible with all supported data and control signal numerologies and TDM/FDM multiplexing of multiple users. The following solutions can address NR-SRS signaling aspects when multiple numerologies are supported simultaneously in a carrier. NR-SRS resource signaling may fall into one of the categories described below where the NR-Node can allocate any of the following resources for NR-SRS transmission:
1. Certain OFDM symbols or portions of the OFDM symbols may be reserved in a cell-wide or beam-wide manner for transmitting NR-SRS in each supported numerology. In
2. Certain OFDM symbols or portions of the OFDM symbols may be reserved in a cell-wide or beam-wide manner in a reference numerology that may be associated to the carrier frequency or indicated by the system information. This concept is illustrated in
Alternatively, the SRS resources may be defined in units of time and may be configured to support any numerology. In this case, the reserved time may carry a different number of NR-SRS symbols for different numerologies. This concept is illustrated in
In an embodiment, a UE may transmit NR-SRS on multiple beams in a reserved SRS resource. This concept is illustrated in
In another embodiment, SRS port mapping techniques may be used to support non-precoded, precoded and beamforming. The NR-SRS port mapping methods for non-precoded, precoded, and beamforming cases are described.
In an exemplary embodiment, the UE may transmit a maximum number of ports that it can support and feedback to NR-NB. The maximum number of available, supported ports may be dependent on UE capability. Here, a unified method for NR-SRS port mapping for non-precoded, precoded and beamforming can be employed. The porting mapping can work with the UL antenna virtualization. The antenna virtualization method is depicted in the following
V=VTVPVAVD, Eq. 1
where the VD is the codebook that can be defined or specified in the digital domain, VA is the codewords to port mapping matrix, the VP is the port to TXRU mapping matrix and VT is the TXRU to physical antenna mapping.
If there is no precoding or beamforming applied on the NR SRS, then the NR SRS can be directly transmitted via the port configured/assigned from NR gNB. In other words, the VD VP and the VT can be set as an identify matrix, and the VA is dependent on the NR-SRS port configuration setting. For example, if a UE can support up to 8 ports and the RRC configuration parameters srs-TxAntennaPorts is set to {1, 2, 3, 4}, then UE can transmit NR-SRS to ports 1, 2, 3 and 4. The active port number may be dynamic signaling via DL DCI. In an instance, if the configuration parameter srs-TxAntennaPorts is set to {1, 2, 3, 4} and NR configure the transmission active port as {1, 3, 4} at a certain SRS transmission subframe then the UE transmit the NR-SRS on port {1, 3, 4} only. If there is no DL DCI is involved in the transmission port configuration then the UE can transmit the NR-SRS based on the RRC configuration ports setup. The NR-SRS transmit at the different port may be transmitted at the same or different CP-OFDM/DFT-S-OFDM symbol and can be associated with a specific numerology. In
Similarly, when there is a precoded or beamforming involved in the NR-SRS, the VD, VP and VT can be properly design to meet the precoding or beamforming requirement. The VA can be decided from the SRS port mapping configuration. In short, the following NR-SRS port mapping methods can be used:
Here, the VP and the VT can leave to UE implementation and without standardization effort.
According to yet a further embodiment, NR-SRS beam sweeping can be treated as a unit of beam sweeping time for transmitting NR-SRS. Each NR-SRS beam sweeping block may include at least one or more CP-OFDM/DTF-S-OFDM symbols and be associated with a specific numerology. Multiple beam sweeping blocks can form a beam sweeping burst. This is shown in
NR CSI Interference Channel Measurement
According to yet another aspect of the application, solutions to support CSI-ICM in NR are envisaged. In one embodiment, a new RRC signaling is employed to signal to the CSI-ICM. In another embodiment, two-step dynamic signaling is described. In yet another embodiment, a group based CSI-ICM configuration through DCI is described. In yet a further embodiment, the PUCCH format for CSI-ICM reporting is described. In yet even a further embodiment, the DCI design enables UE interference cancellation for MU-MIMO. In even a further embodiment, procedures of interference channel measurement and interference cancellation is described below.
According to this aspect, a new information element CSI-ICM-Config is used as the only signaling to indicate all the necessary information of the configuration is described. For example, the NR node configured the UE using the RRC signaling with the CSI-RS/ICM location. This could be based on one or more of the following: (i) UE interference hypotheses, (ii) the number of interference channel; and (iii) multiuser MIMO scheduling. Meanwhile, the information of precoding matrix used in the CSI-ICM transmission also need to be indicated. This is because the UE want to measure the real interference channel, so the precoding matrix need to be removed from the effective channel and the interference channel information can be feedback to the NR node. An example of CSI-ICM configuration information element CSI-ICM-Config in the RRC configuration message is listed below as follows:
Alternatively, the technique may implement the CSI-ICM configuration by two steps signaling via NR DCI to avoid the large latency issue introduced by the RRC only signaling method. The steps are as follows:
As an alternative method, the dynamic CSI-ICM configuration can be also done through MAC Control Element (CE) once the resources set is pre-configured. A new MAC Control Element, CSI-ICM configuration MAC control element which carries the similar information as that defined in Table 1 is defined below:
The CSI-ICM configuration MAC control element may be defined over a fixed number n of octets. The CSI-ICM configuration MAC control element may be identified with Logical Channel Identifier (LCID), which may be one of the existing reserved value of LTE downlink logical channels between the range 01011 and 10111 (binary coding) or alternatively the LTE logical channel value ranges may be extended with new defined values assigned to CSI-ICM configuration MAC CE.
As discussed above, the DCI needs to be transmitted to every UE separately to indicate the CSI-ICM configuration which requires a large number of DCI transmission when there are a lot of UEs. To reduce this overhead, group-based CSI-ICM configuration can be used through DCI to enable multiple UEs measuring the interference channel. The UEs that have the same interference sources or share some resources when doing the CSI-ICM can be grouped and transmitted in one DCI containing the common information and the individual information to all the UEs in the group. The common information is the shared fields that are the same to all UEs in the group, in terms of group ID, CSI-ICM configuration, CSI-RS/ICM structure and etc. The individual information indicates the UE ID, UL resources to transmit the CSI-ICM feedback and all the other signaling cannot be shared among the UEs within the group which each UE has its unique information. An example of the configurable fields for group-base CSI-ICM configuration DCI scheme are listed in Table 5 below.
According to another embodiment, upon measuring the interference channel, the UE needs to feedback the interference channel estimation to NR node/TRP. This will be used in MU-MIMO scheduling. The interference channel feedback could be implicit, explicit or a combination of implicit and explicit feedbacks. For example, when the largest eigenvalue is less than a pre-defined threshold, only the implicit feedback is required, and otherwise, the UE needs to feedback the explicit channel measurement according to the eigenvalues greater than the threshold. The implicit feedback may contain information such as CQI, PMI or RI for the interference channel, and explicit feedback may be in the following forms: (i) The exact interference channel measurement; (ii) The eigenvectors of the interference channel according to the largest eigenvalues; and (iii) The covariance matrix of the interference channel.
To reduce the overhead of the explicit interference feedback, it could be quantized by a pre-defined codebook or transformed to a reduced-dimension form. The CSI-ICM feedback may be tolerant to a higher quantization error or a transforming error comparing to explicit CSI feedback.
A UE is configured by higher layer or NR DCI to periodically or aperiodically or semi-persistently send CSI-ICM feedback via NR PUCCH. A new NR PUCCH reporting type could be defined for CSI-ICM feedback. For periodic CSI-ICM feedback, the periodicity and relative offset are configured by higher layer signaling. For aperiodic or semi-persistent CSI-ICM, the resource to transmit CSI-ICM feedback is configured by NR DCI.
According to yet another embodiment, after receiving the CSI and CSI-ICM feedbacks, the NR node could be able to schedule MU-MIMO transmission. For the UE scheduled for MU-MIMO, beside the general transmission information such as resource allocation, Modulation and coding scheme, and HARQ process number, the NR DCI should also include the following information:
According to another embodiment, procedures of interference channel measurement and interference cancellation are described. These include, for example:
Based on the information from its NR DCI, the UE is able to cancel the interference transmitted to other co-scheduled UEs or from other beams/TRPs.
A call flow to portray the CSI-ICM procedure is illustrated in
Dynamic CSI Measurement and Report
According to a further aspect of the application, a semi-static RRC configuration of CSI measurement and the pool of CSI-RS resource element for the UE, and dynamic signaling to schedule CSI measurement are described. Two methods for RRC based configuration of CSI-RS pooling resources.
In one embodiment, the NR node may initially signals the CSI-RS configuration to the UE in dedicated UE RRC signaling as described in the embodiment above and then subsequently uses the group signaling to configure group of UEs with a common pool of CSI-RS resources.
According to another embodiment, a detailed design of CSI-RS Pooling DCI or MAC CE Signaling is described. Several signaling designs include: (i) CSI measurement command signaled in DCI; and (ii) CSI measurement command signaled in MAC CE
MAC CE based signaling. In an embodiment, the following method can be used to signal CSI measurement command in MAC CE. Specifically, the NR node dynamically signals in MAC CE to the UE, transmission of CSI-RS preconfigured by RRC signaling. The indication of CSI-RS transmission in MAC CE may include the CSI-RS configuration index previously pre-configured in the UE (for e.g. via RRC signaling). The UE uses this index to locate the CSI-RS configuration information stored in its internal database. The UE may then perform measurement of the CSI-RS using the CSI-RS configuration parameters (e.g. antenna port count, resource information, CSI-RS transmission interval information, beam configuration) identified by the information (e.g. CSI-RS configuration index) received in the MAC CE.
In an exemplary embodiment, the MAC CE may carry in addition to the CSI-RS configuration index, the measurement time window. The measurement time windows may be pre-defined in the specification. It may be expressed in terms of an integer number of CSI-RS transmission time interval (e.g. CSI transmission periodicity time value), for e.g. 1, 2, 3, 4 etc. For example, if the measurement time window is 1, the UE measures CSI-RS over one CSI-RS transmission time interval and stop. Similarly, if the measurement time window is k, the UE measures CSI-RS over k CSI-RS transmission time intervals. In this embodiment, the NR node doesn't signals a MAC CE to the UE in order to terminate the CSI-RS measurement. The UE implicitly terminates the measurement using the received transmission time window.
In another embodiment, the NR node may explicitly signal to the UE in MAC CE, the termination (or de-activation) or a previously activated CSI-RS measurement. This may be the case, if the NR node didn't include in the prior CSR-RS measurement activation MAC CE, a measurement time window information. An example of CSI-RS measurement activation and deactivation MAC CE are depicted in
Two examples of MAC CE are illustrated below. The CSI RS measurement Activation/Deactivation MAC control element with one octet is defined in
The MAC CE as illustrated includes only one measurement time window TW. This means the measurement time window is common for all the CSI-RS configuration included in the MAC CE. However, the MAC CE may also be structure to include more than one TW. For example, assuming each of the CSI RS included in the MAC CE has different TW, then there will be as many TWs as RSs in the MCA CE.
The logical channel ID associated with the CSI-RS measurement activation/deactivation MAC CEs may be one of the existing reserved value of LTE downlink logical channels between the range 01011 and 10111 (binary coding). Alternatively, the LTE logical channel value ranges may be extended with new defined values assigned to CSI-RS measurement activation/deactivation MAC CE. The logical channel ID should uniquely identify the MAC CE. For e.g., the MAC CE in two figure above should have different logical channel IDs. The signalings described for MAC CE can be applicable to the DCI based signaling as well.
According to another embodiment, the following DCI based signaling methods can include: (i) CSI measurement command piggyback on DCI; (ii) Standalone CSI measurement command (sent on a separate DCI) for a specific UE; and (iii) Group-based DCI to schedule multiple UEs' CSI-RS measurement and feedback.
In Signaling Method 1, CSI measurement command is piggybacked on another DCI using one or both of the following options:
According to Option 1, the CSI measurement command is signaled in a DCI that is used for scheduling of NR-PUSCH, so called UL grant DCI. It will carry the following information (explicitly or implicitly):
According to Option 2, the CSI measurement command is signaled in a DCI that is used for scheduling of NR-PDSCH, which is the DL grant DCI. It will carry the following information (explicitly or implicitly) similar to Option 1, and will include the following additional fields.
According to another embodiment, a standalone CSI measurement command can be transmitted on a separate DCI can be used to active a CSI measurement for a UE. Such a standalone CSI measurement command DCI will carry the following information (explicitly or implicitly) as in Option 1 of signaling method 1, and include the following additional fields:
According to yet a further embodiment, UE Procedures for Signaling method 2 are as follows:
Signaling Method 3 is described in accordance with a further embodiment. Here, a group-based CSI measurement DCI can be used to schedule CSI-RS measurement and feedback for multiple UEs. Group-based CSI measurement DCI can achieve reduced signaling overhead when these UEs have the same CSI reporting configuration and share the same CSI-RS resource pool configured by higher layer signalings. Such a group-based CSI measurement DCI will carry the following information (explicitly or implicitly) similar to those in Option 1 of signaling method 1, except the following different fields:
A. Group ID: as described, such multiple UEs are already configured by higher layer signaling (such as RRC) to be in a group. Then, they can addressed their group ID or group-RNTI in the group-based CSI measurement DCI.
B. Signaling of which UEs need to perform CSI measurement: This can be done by a bitmap in order of UE's index/position within the group configured by higher layer signaling. For each UE that needs to perform CSI measurement, the corresponding position in the bitmap will be set to “1”, otherwise it will be set to “0”.
UE Procedures for Signaling method 2 are described below in accordance with a further embodiment as follows:
The signalings described for DCI based signaling in this section can be applicable to the MAC CE based signaling as well.
It is understood that the functionality, steps, and configurations illustrated in
Interfaces, such as Graphical User Interfaces (GUIs), can be used to assist user to control and/or configure functionalities related to reference signals and control channels in NR.
The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, the core transport network, and service capabilities—including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred as 3G), LTE (commonly referred as 4G), and LTE-Advanced standards. 3GPP has begun working on the standardization of next generation cellular technology, called New Radio (NR), which is also referred to as “5G”. 3GPP NR standards development is expected to include the definition of 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. The flexible radio access is expected to consist of a new, non-backwards compatible radio access in new spectrum below 6 GHz, and it is expected to include different operating modes that can be multiplexed together in the same spectrum to address a broad set of 3GPP NR use cases with diverging requirements. The ultra-mobile broadband is expected to include cmWave and mmWave spectrum that will provide the opportunity for ultra-mobile broadband access for, e.g., indoor applications and hotspots. In particular, the ultra-mobile broadband is expected to share a common design framework with the flexible radio access below 6 GHz, with cmWave and mmWave specific design optimizations.
3GPP has identified a variety of use cases that NR is expected to support, resulting in a wide variety of user experience requirements for data rate, latency, and mobility. The use cases include the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, indoor ultra-high broadband access, broadband access in a crowd, 50+ Mbps everywhere, ultra-low cost broadband access, mobile broadband in vehicles), critical communications, massive machine type communications, network operation (e.g., network slicing, routing, migration and interworking, energy savings), and enhanced vehicle-to-everything (eV2X) communications. Specific service and applications in these categories include, e.g., monitoring and sensor networks, device remote controlling, bi-directional remote controlling, personal cloud computing, video streaming, wireless cloud-based office, first responder connectivity, automotive ecall, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile internet, and virtual reality to name a few. All of these use cases and others are contemplated herein.
The communications system 100 may also include a base station 114a and a base station 114b. Base stations 114a may be any type of device configured to wirelessly interface with 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, and/or the other networks 112. Base stations 114b may be any type of device configured to wiredly and/or wirelessly interface with at least one of the RRHs (remote radio heads) 118a, 118b and/or TRPs (transmission and reception points) 119a, 119b to facilitate access to one or more communication networks, such as the core network 106/107/109, the Internet 110, and/or the other networks 112. RRHs 118a, 118b may be any type of device configured to wirelessly interface with 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, and/or the other networks 112. TRPs 119a, 119b may be any type of device configured to wirelessly interface with 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, and/or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, and the like. While 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 and/or network elements.
The base station 114a may be part of the RAN 103/104/105, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114b may be part of the RAN 103b/104b/105b, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a may be configured to transmit and/or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown). The base station 114b may be configured to transmit and/or receive wired and/or wireless signals within a particular geographic region, which may be referred to as a cell (not shown). The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, e.g., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.
The base stations 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).
The base stations 114b may communicate with one or more of the RRHs 118a, 118b and/or TRPs 119a, 119b over a wired or air interface 115b/116b/117b, which may be any suitable wired (e.g., cable, optical fiber, 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).
The RRHs 118a, 118b and/or TRPs 119a, 119b may communicate with one or more of the WTRUs 102c, 102d over 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).
More specifically, as noted above, the communications 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, and the like. For example, the base station 114a in the RAN 103/104/105 and the WTRUs 102a, 102b, 102c, or 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 establish the air interface 115/116/117 or 115c/116c/117c respectively using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).
In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c, or 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) and/or LTE-Advanced (LTE-A). In the future, the air interface 115/116/117 may implement 3GPP NR technology.
In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c, or 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 1×, 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), and the like.
The base station 114c in
The RAN 103/104/105 and/or RAN 103b/104b/105b may be in communication with the core network 106/107/109, which may be any type of network configured to provide voice, data, applications, and/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., and/or perform high-level security functions, such as user authentication.
Although not shown in
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, and/or other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide 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), user datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired or wireless communications networks owned and/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 and/or RAN 103b/104b/105 or a different RAT.
Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications 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. For example, the WTRU 102e shown in
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 in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/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. While
The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 115/116/117. For example, in an embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive Although not shown in
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, and/or other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide 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), user datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 112 may include wired or wireless communications networks owned and/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.
Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications 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 example, the WTRU 102c shown in
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 in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/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. While
The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 115/116/117. For example, in an embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In an embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet an embodiment, the transmit/receive element 122 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
In addition, although the transmit/receive element 122 is depicted in
The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.
The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad/indicators 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad/indicators 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. 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 an embodiment, the processor 118 may access information from, and store data in, 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 receive power from the power source 134, and may be configured to distribute and/or control the power to the 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, and the like.
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 over the air interface 115/116/117 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
The processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals 138 may include various sensors such as an accelerometer, biometrics (e.g., finger print) sensors, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.
The WTRU 102 may be embodied in other apparatuses or devices, such as a sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, truck, train, or airplane. The WTRU 102 may connect to other components, modules, or systems of such apparatuses or devices via one or more interconnect interfaces, such as an interconnect interface that may comprise one of the peripherals 138.
As shown in
The core network 106 shown in
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.
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 and the WTRUs 102a, 102b, 102c and IP-enabled devices.
As noted above, the core network 106 may also be connected to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.
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 an embodiment. 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 embodiment, 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.
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 the uplink and/or downlink, and the like. As shown in
The core network 107 shown in
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, and the like. 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.
The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via the 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 user planes during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
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.
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 communicate 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 and/or operated by other service providers.
As shown in
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, and/or mobility management.
The communication link between each of the base stations 180a, 180b, and 180c may be defined as an R8 reference point that includes protocols for facilitating WTRU handovers and the transfer of data between 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.
As shown in
The MIP-HA may be responsible for IP address management, and may enable the WTRUs 102a, 102b, and 102c to roam between different ASNs and/or different core networks. The MIP-HA 184 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. The AAA server 186 may be responsible for user authentication and for supporting user services. The gateway 188 may facilitate interworking with other networks. For example, the gateway 188 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. 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/or operated by other service providers.
Although not shown in
The core network entities described herein and illustrated in
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 the components in computing system 90 and defines the 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 system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.
Memories coupled to system bus 80 include random access memory (RAM) 82 and read only memory (ROM) 93. Such memories include circuitry that allows information to be stored and retrieved. ROMs 93 generally contain stored data that cannot easily be modified. Data stored in RAM 82 can be read or changed by processor 91 or other hardware devices. Access to RAM 82 and/or ROM 93 may be controlled by memory controller 92. Memory controller 92 may provide an address translation function that translates virtual addresses into physical addresses as instructions are executed. Memory controller 92 may also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in a first mode can access only memory mapped by its own process virtual address space; it cannot access memory within another process's virtual address space unless memory sharing between the processes has been set up.
In addition, computing system 90 may contain peripherals controller 83 responsible for communicating instructions from processor 91 to peripherals, such as printer 94, keyboard 84, mouse 95, and disk drive 85.
Display 86, which is controlled by display controller 96, is used to display visual output generated by 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). Display 86 may be implemented with a CRT-based video display, an LCD-based flat-panel display, gas plasma-based flat-panel display, or a touch-panel. Display controller 96 includes electronic components required to generate a video signal that is sent to display 86.
Further, computing system 90 may contain communication circuitry, such as for example a network adapter 97, that may be used to connect computing system 90 to an external communications network, such as the RAN 103/104/105, Core Network 106/107/109, PSTN 108, Internet 110, or Other Networks 112 of
It is understood that any or all of the apparatuses, systems, methods and processes described herein may be embodied in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium which instructions, when executed by a processor, such as processors 118 or 91, cause the processor to perform and/or implement the systems, methods and processes described herein. Specifically, any of the steps, operations or functions described herein may be implemented in the form of such computer executable instructions, executing on the processor of an apparatus or computing system configured for wireless and/or wired network communications. Computer readable storage media include volatile and nonvolatile, removable and non-removable media implemented in any non-transitory (e.g., tangible or physical) method or technology for storage of information, but such computer readable storage media do not includes signals. Computer readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible or physical medium which can be used to store the desired information and which can be accessed by a computing system.
This application is a continuation of U.S. patent application Ser. No. 17/132,026 filed Dec. 23, 2020 which is a continuation of U.S. patent application Ser. No. 16/346,972 filed May 2, 2019 which is the National Stage Application of International Patent Application No. PCT/US2017/059890 filed Nov. 3, 2017 which claims the benefit of priority to U.S. Provisional Application No. 62/416,902 filed Nov. 3, 2016, the contents of which are incorporated by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
934888 | Dahlberg | Sep 1909 | A |
4892292 | Russell | Jan 1990 | A |
5610653 | Abecassis | Mar 1997 | A |
5892554 | Dicicco et al. | Apr 1999 | A |
6750919 | Rosser | Jun 2004 | B1 |
6973130 | Wee et al. | Dec 2005 | B1 |
7114174 | Brooks et al. | Sep 2006 | B1 |
7117517 | Milazzo et al. | Oct 2006 | B1 |
7343617 | Katcher et al. | Mar 2008 | B1 |
7577980 | Kienzle et al. | Aug 2009 | B2 |
7782344 | Whittaker | Aug 2010 | B2 |
7949032 | Frost | May 2011 | B1 |
8055785 | Liu et al. | Nov 2011 | B2 |
8160077 | Traversat et al. | Apr 2012 | B2 |
8243797 | Lin et al. | Aug 2012 | B2 |
8331760 | Butcher | Dec 2012 | B2 |
8621000 | Adimatyam et al. | Dec 2013 | B2 |
8705527 | Addepalli et al. | Apr 2014 | B1 |
8902773 | Anderson et al. | Dec 2014 | B2 |
9002979 | Hansen | Apr 2015 | B2 |
9047236 | Gigliotti | Jun 2015 | B2 |
9060187 | Wu et al. | Jun 2015 | B2 |
9064313 | Seshadrinathan et al. | Jun 2015 | B2 |
9137027 | Matthews et al. | Sep 2015 | B2 |
9170707 | Aska et al. | Oct 2015 | B1 |
9177225 | Cordova-Diba et al. | Nov 2015 | B1 |
9198181 | Blankenship et al. | Nov 2015 | B2 |
9231838 | Ould-Brahim et al. | Jan 2016 | B2 |
9276710 | Damnjanovic et al. | Mar 2016 | B2 |
9288545 | Hill et al. | Mar 2016 | B2 |
9317688 | Yegin et al. | Apr 2016 | B2 |
9336060 | Nori et al. | May 2016 | B2 |
9338700 | Schulist et al. | May 2016 | B2 |
9344888 | Starsinic et al. | May 2016 | B2 |
9380623 | Kim et al. | Jun 2016 | B2 |
9413451 | Park et al. | Aug 2016 | B2 |
9559797 | Liao et al. | Jan 2017 | B2 |
9992553 | Bennett et al. | Jun 2018 | B2 |
10028302 | Au et al. | Jul 2018 | B2 |
10111163 | Vrzic et al. | Oct 2018 | B2 |
10306671 | Li et al. | May 2019 | B2 |
10432362 | Iyer et al. | Oct 2019 | B2 |
10530757 | Seed et al. | Jan 2020 | B2 |
10979924 | Tooher et al. | Apr 2021 | B2 |
11051293 | Tsai et al. | Jun 2021 | B2 |
11122027 | Seed et al. | Sep 2021 | B2 |
11218267 | Zhang et al. | Jan 2022 | B2 |
20020065678 | Peliotis et al. | May 2002 | A1 |
20020120931 | Hiuber et al. | Aug 2002 | A1 |
20020126990 | Rasmussen et al. | Sep 2002 | A1 |
20020174425 | Markel et al. | Nov 2002 | A1 |
20040032495 | Ortiz | Feb 2004 | A1 |
20040190779 | Sarachik et al. | Sep 2004 | A1 |
20050093976 | Valleriano et al. | May 2005 | A1 |
20050286466 | Tagg et al. | Dec 2005 | A1 |
20060155842 | Yeung et al. | Jul 2006 | A1 |
20060193295 | White et al. | Aug 2006 | A1 |
20070024706 | Brannon et al. | Feb 2007 | A1 |
20070042784 | Anderson | Feb 2007 | A1 |
20070086669 | Berger et al. | Apr 2007 | A1 |
20070101418 | Wood et al. | May 2007 | A1 |
20070104369 | Weatherhead | May 2007 | A1 |
20070140106 | Tsai et al. | Jun 2007 | A1 |
20070153739 | Zheng | Jul 2007 | A1 |
20070171921 | Wookey et al. | Jul 2007 | A1 |
20080127253 | Zhang et al. | May 2008 | A1 |
20080205351 | Bengt et al. | Aug 2008 | A1 |
20080225116 | Kang et al. | Sep 2008 | A1 |
20080261711 | Tuxen | Oct 2008 | A1 |
20090007023 | Sundstrom | Jan 2009 | A1 |
20090046152 | Aman | Feb 2009 | A1 |
20090047902 | Nory et al. | Feb 2009 | A1 |
20090197630 | Ahn et al. | Aug 2009 | A1 |
20090201917 | Maes et al. | Aug 2009 | A1 |
20090217339 | Kim et al. | Aug 2009 | A1 |
20090220080 | Herne et al. | Sep 2009 | A1 |
20090225164 | Renkis | Sep 2009 | A1 |
20090276805 | Andrews et al. | Nov 2009 | A1 |
20090298497 | Lee | Dec 2009 | A1 |
20090300692 | Mavlankar et al. | Dec 2009 | A1 |
20090305708 | Matsui et al. | Dec 2009 | A1 |
20090316795 | Chui et al. | Dec 2009 | A1 |
20090323607 | Park et al. | Dec 2009 | A1 |
20100027466 | Mustapha | Feb 2010 | A1 |
20100035611 | Montojo et al. | Feb 2010 | A1 |
20100061361 | Wu | Mar 2010 | A1 |
20100097221 | Kreiner et al. | Apr 2010 | A1 |
20100188531 | Cordes et al. | Jul 2010 | A1 |
20100227611 | Schmidt et al. | Sep 2010 | A1 |
20100232504 | Feng | Sep 2010 | A1 |
20110013836 | Gefen et al. | Jan 2011 | A1 |
20110016321 | Sundaram et al. | Jan 2011 | A1 |
20110077013 | Cho et al. | Mar 2011 | A1 |
20110113480 | Ma et al. | May 2011 | A1 |
20110222428 | Charbit et al. | Sep 2011 | A1 |
20110231653 | Bollay et al. | Sep 2011 | A1 |
20110242997 | Yin | Oct 2011 | A1 |
20110263250 | Mueck et al. | Oct 2011 | A1 |
20110299832 | Butcher | Dec 2011 | A1 |
20110304772 | Dasher et al. | Dec 2011 | A1 |
20120009963 | Kim et al. | Jan 2012 | A1 |
20120047551 | Pattar et al. | Feb 2012 | A1 |
20120056898 | Tsurumi et al. | Mar 2012 | A1 |
20120062732 | Marman et al. | Mar 2012 | A1 |
20120072952 | Vaysman et al. | Mar 2012 | A1 |
20120078712 | Fontana et al. | Mar 2012 | A1 |
20120117140 | Wang et al. | May 2012 | A1 |
20120127934 | Anderson et al. | May 2012 | A1 |
20120163335 | Chung et al. | Jun 2012 | A1 |
20120238264 | Jindal | Sep 2012 | A1 |
20120308202 | Murata et al. | Dec 2012 | A1 |
20130003576 | Segura et al. | Jan 2013 | A1 |
20130016910 | Murata et al. | Jan 2013 | A1 |
20130017833 | Sakamoto et al. | Jan 2013 | A1 |
20130031582 | Tinsman et al. | Jan 2013 | A1 |
20130034071 | Lee et al. | Feb 2013 | A1 |
20130036442 | Wingert | Feb 2013 | A1 |
20130077574 | Ekpenyong et al. | Mar 2013 | A1 |
20130091430 | Zhai et al. | Apr 2013 | A1 |
20130091515 | Sakata et al. | Apr 2013 | A1 |
20130111609 | Resch et al. | May 2013 | A1 |
20130142118 | Cherian et al. | Jun 2013 | A1 |
20130155106 | Rolleston et al. | Jun 2013 | A1 |
20130155847 | Li et al. | Jun 2013 | A1 |
20130167062 | Herring et al. | Jun 2013 | A1 |
20130185353 | Rondao et al. | Jul 2013 | A1 |
20130188503 | Anepu et al. | Jul 2013 | A1 |
20130223339 | Nakahara | Aug 2013 | A1 |
20130225184 | Liu et al. | Aug 2013 | A1 |
20130225189 | Moon et al. | Aug 2013 | A1 |
20130242882 | Blankenship et al. | Sep 2013 | A1 |
20130246784 | Zhang et al. | Sep 2013 | A1 |
20130265932 | Huang et al. | Oct 2013 | A1 |
20130266286 | Yu et al. | Oct 2013 | A1 |
20130294506 | Kang et al. | Nov 2013 | A1 |
20130312042 | Shaw et al. | Nov 2013 | A1 |
20130342539 | Khan et al. | Dec 2013 | A1 |
20140022074 | Balinski et al. | Jan 2014 | A1 |
20140026052 | Thorwirth et al. | Jan 2014 | A1 |
20140029462 | Stewart | Jan 2014 | A1 |
20140033074 | Thibaux et al. | Jan 2014 | A1 |
20140036806 | Chen et al. | Feb 2014 | A1 |
20140059457 | Min | Feb 2014 | A1 |
20140082054 | Denoual et al. | Mar 2014 | A1 |
20140086177 | Adjakple et al. | Mar 2014 | A1 |
20140086217 | Park et al. | Mar 2014 | A1 |
20140089990 | Van et al. | Mar 2014 | A1 |
20140126402 | Nam | May 2014 | A1 |
20140168056 | Swaminathan et al. | Jun 2014 | A1 |
20140195918 | Friedlander | Jul 2014 | A1 |
20140204247 | Bilgen et al. | Jul 2014 | A1 |
20140204854 | Freda et al. | Jul 2014 | A1 |
20140206854 | Bennett et al. | Jul 2014 | A1 |
20140215043 | Ryu et al. | Jul 2014 | A1 |
20140223095 | Storm et al. | Aug 2014 | A1 |
20140245367 | Sasaki et al. | Aug 2014 | A1 |
20140254544 | Kar et al. | Sep 2014 | A1 |
20140269932 | Su et al. | Sep 2014 | A1 |
20140279068 | Systrom et al. | Sep 2014 | A1 |
20140280781 | Gregotski | Sep 2014 | A1 |
20140282751 | Lee et al. | Sep 2014 | A1 |
20140282909 | Cherian et al. | Sep 2014 | A1 |
20140293901 | Hegde | Oct 2014 | A1 |
20140293942 | Kang et al. | Oct 2014 | A1 |
20140314100 | Song | Oct 2014 | A1 |
20140315593 | Vrzic et al. | Oct 2014 | A1 |
20140321375 | Agiwal et al. | Oct 2014 | A1 |
20140351891 | Grube et al. | Nov 2014 | A1 |
20140369201 | Gupta et al. | Dec 2014 | A1 |
20150014773 | Cheng et al. | Jan 2015 | A1 |
20150032901 | Wang et al. | Jan 2015 | A1 |
20150033312 | Seed et al. | Jan 2015 | A1 |
20150043520 | Sun et al. | Feb 2015 | A1 |
20150070587 | Emeott et al. | Mar 2015 | A1 |
20150089023 | Phillips et al. | Mar 2015 | A1 |
20150089072 | Phillips et al. | Mar 2015 | A1 |
20150103725 | Sun et al. | Apr 2015 | A1 |
20150104155 | Bloch et al. | Apr 2015 | A1 |
20150145782 | Brown et al. | May 2015 | A1 |
20150179219 | Gao et al. | Jun 2015 | A1 |
20150208103 | Guntur et al. | Jul 2015 | A1 |
20150222815 | Wang et al. | Aug 2015 | A1 |
20150223279 | Jiao et al. | Aug 2015 | A1 |
20150234708 | Storm et al. | Aug 2015 | A1 |
20150264096 | Swaminathan et al. | Sep 2015 | A1 |
20150268822 | Waggoner et al. | Sep 2015 | A1 |
20150282130 | Webb et al. | Oct 2015 | A1 |
20150296250 | Casper | Oct 2015 | A1 |
20150304693 | Hwang et al. | Oct 2015 | A1 |
20150326353 | Ko et al. | Nov 2015 | A1 |
20150326484 | Cao et al. | Nov 2015 | A1 |
20150327245 | Zhu et al. | Nov 2015 | A1 |
20150341091 | Park et al. | Nov 2015 | A1 |
20150348247 | McLaughlin et al. | Dec 2015 | A1 |
20150351084 | Werb | Dec 2015 | A1 |
20150382262 | Cho et al. | Dec 2015 | A1 |
20150382268 | Hampel et al. | Dec 2015 | A1 |
20160020877 | Koutsimanis et al. | Jan 2016 | A1 |
20160036578 | Malladi et al. | Feb 2016 | A1 |
20160042496 | Ichimi et al. | Feb 2016 | A1 |
20160057494 | Hwang et al. | Feb 2016 | A1 |
20160073106 | Su et al. | Mar 2016 | A1 |
20160073302 | Yang et al. | Mar 2016 | A1 |
20160100395 | Xu et al. | Apr 2016 | A1 |
20160113039 | Hole et al. | Apr 2016 | A1 |
20160135153 | Suzuki et al. | May 2016 | A1 |
20160156397 | Onggosanusi et al. | Jun 2016 | A1 |
20160156949 | Hattori et al. | Jun 2016 | A1 |
20160165309 | Van et al. | Jun 2016 | A1 |
20160165622 | Luo et al. | Jun 2016 | A1 |
20160182201 | Jiang et al. | Jun 2016 | A1 |
20160182593 | Denoual et al. | Jun 2016 | A1 |
20160183234 | Sung et al. | Jun 2016 | A1 |
20160192433 | Deenoo et al. | Jun 2016 | A1 |
20160217623 | Singh | Jul 2016 | A1 |
20160234736 | Kubota et al. | Aug 2016 | A1 |
20160234759 | Kubota et al. | Aug 2016 | A1 |
20160249269 | Niu et al. | Aug 2016 | A1 |
20160249353 | Nakata et al. | Aug 2016 | A1 |
20160253240 | Cocagne | Sep 2016 | A1 |
20160270102 | Zeng et al. | Sep 2016 | A1 |
20160306036 | Johnson | Oct 2016 | A1 |
20160337706 | Hwang et al. | Nov 2016 | A1 |
20160344464 | Kim | Nov 2016 | A1 |
20160352545 | Johnson | Dec 2016 | A1 |
20160353343 | Rahman et al. | Dec 2016 | A1 |
20160353465 | Vrzic et al. | Dec 2016 | A1 |
20160360235 | Ramasubramonian et al. | Dec 2016 | A1 |
20160366454 | Tatourian et al. | Dec 2016 | A1 |
20170013598 | Jung et al. | Jan 2017 | A1 |
20170034845 | Liu et al. | Feb 2017 | A1 |
20170070735 | Ramasubramonian et al. | Mar 2017 | A1 |
20170080158 | Cabiri et al. | Mar 2017 | A1 |
20170118054 | Ma et al. | Apr 2017 | A1 |
20170118540 | Thomas et al. | Apr 2017 | A1 |
20170134913 | Cui et al. | May 2017 | A1 |
20170136948 | Sypitkowski et al. | May 2017 | A1 |
20170163645 | Bradley et al. | Jun 2017 | A1 |
20170164212 | Opsenica et al. | Jun 2017 | A1 |
20170164349 | Zhu et al. | Jun 2017 | A1 |
20170201686 | Choi et al. | Jul 2017 | A1 |
20170201968 | Nam et al. | Jul 2017 | A1 |
20170201980 | Hakola et al. | Jul 2017 | A1 |
20170212583 | Krasadakis | Jul 2017 | A1 |
20170230915 | Kim et al. | Aug 2017 | A1 |
20170230985 | Yamada et al. | Aug 2017 | A1 |
20170236288 | Sundaresan et al. | Aug 2017 | A1 |
20170244529 | Yu et al. | Aug 2017 | A1 |
20170273063 | Kim et al. | Sep 2017 | A1 |
20170289791 | Yoo et al. | Oct 2017 | A1 |
20170290052 | Zhang et al. | Oct 2017 | A1 |
20170302719 | Chen et al. | Oct 2017 | A1 |
20170310431 | Iyer et al. | Oct 2017 | A1 |
20170331670 | Parkvall et al. | Nov 2017 | A1 |
20170331785 | Xu et al. | Nov 2017 | A1 |
20170359731 | Soldati et al. | Dec 2017 | A1 |
20170366311 | Iyer et al. | Dec 2017 | A1 |
20180034612 | Lin et al. | Feb 2018 | A1 |
20180076994 | Lee et al. | Mar 2018 | A1 |
20180115357 | Park et al. | Apr 2018 | A1 |
20180123763 | Yu | May 2018 | A1 |
20180124598 | Zeng | May 2018 | A1 |
20180139656 | Xu et al. | May 2018 | A1 |
20180167938 | Stephenne et al. | Jun 2018 | A1 |
20180184415 | Rong et al. | Jun 2018 | A1 |
20180198504 | Li et al. | Jul 2018 | A1 |
20180199361 | Zhang et al. | Jul 2018 | A1 |
20180220407 | Xiong et al. | Aug 2018 | A1 |
20180242304 | Rong et al. | Aug 2018 | A1 |
20180254851 | Roessel et al. | Sep 2018 | A1 |
20180270696 | Duan et al. | Sep 2018 | A1 |
20180270698 | Babaei et al. | Sep 2018 | A1 |
20180287722 | Takano | Oct 2018 | A1 |
20180294860 | Hakola et al. | Oct 2018 | A1 |
20180317213 | Islam et al. | Nov 2018 | A1 |
20180332632 | Vikberg et al. | Nov 2018 | A1 |
20180338277 | Byun et al. | Nov 2018 | A1 |
20180343043 | Hakola et al. | Nov 2018 | A1 |
20180367255 | Jeon et al. | Dec 2018 | A1 |
20180368018 | Kim et al. | Dec 2018 | A1 |
20190036910 | Choyi et al. | Jan 2019 | A1 |
20190037409 | Wang et al. | Jan 2019 | A1 |
20190045340 | Zhu et al. | Feb 2019 | A1 |
20190045577 | Kim et al. | Feb 2019 | A1 |
20190089423 | Davydov | Mar 2019 | A1 |
20190090284 | Kang et al. | Mar 2019 | A1 |
20190159107 | Kim et al. | May 2019 | A1 |
20190182856 | Moroga et al. | Jun 2019 | A1 |
20190190579 | Wang et al. | Jun 2019 | A1 |
20190200315 | Tsai et al. | Jun 2019 | A1 |
20190208474 | Ali et al. | Jul 2019 | A1 |
20190224474 | Yang et al. | Jul 2019 | A1 |
20190281623 | Andgart et al. | Sep 2019 | A1 |
20190288789 | Li et al. | Sep 2019 | A1 |
20190342782 | Yum et al. | Nov 2019 | A1 |
20190363777 | Karjalainen et al. | Nov 2019 | A1 |
20200021999 | Park et al. | Jan 2020 | A1 |
20200059969 | Agiwal | Feb 2020 | A1 |
20200092065 | Kuang et al. | Mar 2020 | A1 |
20200221480 | Li et al. | Jul 2020 | A1 |
20200351917 | Bang et al. | Nov 2020 | A1 |
20200359391 | Behravan et al. | Nov 2020 | A1 |
20200383129 | Ko et al. | Dec 2020 | A1 |
20200404655 | Salem | Dec 2020 | A1 |
20200404663 | Zhang et al. | Dec 2020 | A1 |
20210021314 | Sun et al. | Jan 2021 | A1 |
20210029646 | Park | Jan 2021 | A1 |
20210037561 | Lyu et al. | Feb 2021 | A1 |
20210044385 | Hosseini et al. | Feb 2021 | A1 |
20210045125 | Mondal et al. | Feb 2021 | A1 |
20210045181 | Li et al. | Feb 2021 | A1 |
20210051646 | Maaref et al. | Feb 2021 | A1 |
20210068138 | Baldemair et al. | Mar 2021 | A1 |
20210105104 | Cao et al. | Apr 2021 | A1 |
20210105833 | Reda et al. | Apr 2021 | A1 |
20210130629 | Suzuki et al. | May 2021 | A1 |
Number | Date | Country |
---|---|---|
101313578 | Nov 2008 | CN |
101331735 | Dec 2008 | CN |
101350923 | Jan 2009 | CN |
101622891 | Jan 2010 | CN |
101690271 | Mar 2010 | CN |
101868273 | Oct 2010 | CN |
101917765 | Dec 2010 | CN |
102026270 | Apr 2011 | CN |
102038998 | May 2011 | CN |
102045849 | May 2011 | CN |
102090126 | Jun 2011 | CN |
102238547 | Nov 2011 | CN |
102474394 | May 2012 | CN |
102577294 | Jul 2012 | CN |
102726109 | Oct 2012 | CN |
102752877 | Oct 2012 | CN |
102907068 | Jan 2013 | CN |
102939573 | Feb 2013 | CN |
102971032 | Mar 2013 | CN |
103069739 | Apr 2013 | CN |
103190089 | Jul 2013 | CN |
103560936 | Feb 2014 | CN |
103563462 | Feb 2014 | CN |
103944686 | Jul 2014 | CN |
104012106 | Aug 2014 | CN |
104052788 | Sep 2014 | CN |
104092488 | Oct 2014 | CN |
104205930 | Dec 2014 | CN |
104220975 | Dec 2014 | CN |
104394558 | Mar 2015 | CN |
104753780 | Jul 2015 | CN |
104782166 | Jul 2015 | CN |
104838713 | Aug 2015 | CN |
104869583 | Aug 2015 | CN |
104936189 | Sep 2015 | CN |
105050189 | Nov 2015 | CN |
105103566 | Nov 2015 | CN |
105144727 | Dec 2015 | CN |
105162557 | Dec 2015 | CN |
105264904 | Jan 2016 | CN |
105284172 | Jan 2016 | CN |
105323049 | Feb 2016 | CN |
105373331 | Mar 2016 | CN |
105471487 | Apr 2016 | CN |
105532050 | Apr 2016 | CN |
106023261 | Oct 2016 | CN |
106233745 | Dec 2016 | CN |
106416223 | Feb 2017 | CN |
107007910 | Aug 2017 | CN |
0246076 | Nov 1987 | EP |
1175785 | Jan 2002 | EP |
2086266 | Aug 2009 | EP |
2408196 | Jan 2012 | EP |
2426645 | Mar 2012 | EP |
2464076 | Jun 2012 | EP |
2530675 | Dec 2012 | EP |
2553860 | Feb 2013 | EP |
2710844 | Mar 2014 | EP |
2824883 | Jan 2015 | EP |
2824885 | Jan 2015 | EP |
2869478 | May 2015 | EP |
2882110 | Jun 2015 | EP |
2919471 | Sep 2015 | EP |
3051906 | Aug 2016 | EP |
3076672 | Oct 2016 | EP |
3082362 | Oct 2016 | EP |
3101971 | Dec 2016 | EP |
3110160 | Dec 2016 | EP |
3420659 | Jan 2019 | EP |
63-013503 | Jan 1988 | JP |
02-464076 | Feb 1990 | JP |
2004-104351 | Apr 2004 | JP |
2007-192988 | Aug 2007 | JP |
2010-050269 | Mar 2010 | JP |
2010-508789 | Mar 2010 | JP |
2010-519838 | Jun 2010 | JP |
2012-507961 | Mar 2012 | JP |
2013-522965 | Jun 2013 | JP |
2014-502128 | Jan 2014 | JP |
2014-525191 | Sep 2014 | JP |
2014-530534 | Nov 2014 | JP |
2015-207934 | Nov 2015 | JP |
2016-013351 | Jan 2016 | JP |
2016-504798 | Feb 2016 | JP |
2016-504851 | Feb 2016 | JP |
2016-514416 | May 2016 | JP |
6313503 | Apr 2018 | JP |
2019-518364 | Jun 2019 | JP |
2019-525616 | Sep 2019 | JP |
10-2008-0041237 | May 2008 | KR |
10-2008-0109535 | Dec 2008 | KR |
10-2009-0085640 | Aug 2009 | KR |
10-2010-0065327 | Jun 2010 | KR |
10-2010-0097625 | Sep 2010 | KR |
10-2011-0063565 | Jun 2011 | KR |
10-2013-0029374 | Mar 2013 | KR |
10-2014-0043532 | Apr 2014 | KR |
10-2014-0098156 | Aug 2014 | KR |
10-2014-0123870 | Oct 2014 | KR |
10-2015-0118874 | Oct 2015 | KR |
10-2015-0119355 | Oct 2015 | KR |
10-1563469 | Oct 2015 | KR |
10-2016-0021141 | Feb 2016 | KR |
10-2016-0055086 | May 2016 | KR |
10-2017-0128515 | Nov 2017 | KR |
10-2019-0089423 | Jul 2019 | KR |
0065837 | Nov 2000 | WO |
0118658 | Mar 2001 | WO |
2007052753 | May 2007 | WO |
2007125910 | Nov 2007 | WO |
2010001474 | Jan 2010 | WO |
2010021705 | Feb 2010 | WO |
2010050269 | May 2010 | WO |
2010082805 | Jul 2010 | WO |
2011082150 | Jul 2011 | WO |
2011097904 | Aug 2011 | WO |
2011123805 | Oct 2011 | WO |
2012021246 | Feb 2012 | WO |
2012114666 | Aug 2012 | WO |
2012130180 | Oct 2012 | WO |
2012141557 | Oct 2012 | WO |
2012155326 | Nov 2012 | WO |
2014057131 | Apr 2014 | WO |
2014059591 | Apr 2014 | WO |
2014067566 | May 2014 | WO |
2014090200 | Jun 2014 | WO |
2014090208 | Jun 2014 | WO |
2014111423 | Jul 2014 | WO |
2014135126 | Sep 2014 | WO |
2014183803 | Nov 2014 | WO |
2014190308 | Nov 2014 | WO |
2015013645 | Jan 2015 | WO |
2015013685 | Jan 2015 | WO |
2015045658 | Apr 2015 | WO |
2015059194 | Apr 2015 | WO |
2015067196 | May 2015 | WO |
2015080646 | Jun 2015 | WO |
2015084048 | Jun 2015 | WO |
2015100533 | Jul 2015 | WO |
2015113205 | Aug 2015 | WO |
2015122737 | Aug 2015 | WO |
2015141982 | Sep 2015 | WO |
2015166840 | Nov 2015 | WO |
2016013351 | Jan 2016 | WO |
2016028111 | Feb 2016 | WO |
2016033731 | Mar 2016 | WO |
2016040290 | Mar 2016 | WO |
2016040833 | Mar 2016 | WO |
2016094191 | Jun 2016 | WO |
2016130353 | Aug 2016 | WO |
2017061297 | Apr 2017 | WO |
2017147515 | Aug 2017 | WO |
2017191833 | Nov 2017 | WO |
2017195478 | Nov 2017 | WO |
2018028602 | Feb 2018 | WO |
Entry |
---|
3rd Generation Partnership Project (3GPP) TSG RAN WG1 #85, R1-165669, Way Forward on Frame Structure, Qualcomm and etc., Nanjing, China, May 23-27, 2016, Agenda Item 7.1.4, 2 pages. |
3rd Generation Partnership Project (3GPP) TSG RAN WG1 Meeting #83 R1-157351, Initial Views on Technical Design for NB-IoT, Nov. 15-22, 2015, 3 pages. |
3rd Generation Partnership Project (3GPP) TSG RAN WG1 Meeting #84bis R1-162379, “Overview of new radio access technology requirements and designs” Apr. 11-15, 2016, 4 pages. |
3rd Generation Partnership Project (3GPP) TSG RAN WG1 Meeting #84bis R1-162797, “Harq Enhancement for Improved Data Channel Efficiency”, Busan, Korea, Apr. 11-15, 2016, 3 pages. |
3rd Generation Partnership Project (3GPP) TSG RAN WG1 Meeting #85 R1-164871 “Frame structure for new radio interface”, May 23-27, 2016, 3 pages. |
3rd Generation Partnership Project (3GPP) TSG RAN WG1 Meeting #85 R1-165174 “Uplink multiple access schemes for NR”, May 23-27, 2016, 4 pages. |
3rd Generation Partnership Project (3GPP) TSG RAN WG1 Meeting #86bis R1-1610524, WF on NR RS Definition, Huawei, HiSilicon, Lisbon, Portugal, Oct. 10-14, 2016, Agenda Item: 8.1.4.4, 4 pages. |
3rd Generation Partnership Project (3GPP) TSG-RAN WG1 #85, R1-164628, Frame Structure for NR, Ericsson, Nanjing, China, May 23-27, 2016, 3 pages. |
3rd Generation Partnership Project (3GPP) TSG-RAN WG1 #85, R1-164694, Frame Structure Requirements, Qualcomm, Nanjing, China, May 23-27, 2016, 5 pages. |
3rd Generation Partnership Project (3GPP) TSG-RAN WG1#85 R1-165027 “Basic Frame Structure Principles for 5G” May 23-27, 2016, 6 pages. |
3rd Generation Partnership Project (3GPP) TSG-RAN WG1#85, R1-165363, Nokia, Alcatel-Lucent Shanghai Bell, Scalability of MIMO Operation Across NR Carrier Frequencies, Nanjing, P.R. China, May 23-27, 2016, 5 pages. |
3rd Generation Partnership Project (3GPP) TSG-RAN WG2 Meeting #94 R2-163371, “System Information Signalling Design in NR”, May 23-27, 2016, 7 pages. |
3rd Generation Partnership Project (3GPP) TSG-RAN WG2 Meeting #94, R2-163718 “Control Plane functions in NR”, Nanjing, China; May 23-27, 2016, 4 pages. |
3rd Generation Partnership Project (3GPP), RI-165027, vol. RAN WG1, Nokia et al: “Basic frame structure 1 principles for 5G”, 3GPP Draft; No. Nanjing, P.R. China; May 23, 2016-May 27, 2016 May 13, 2016. |
3rd Generation Partnership Project (3GPP), TS 36.212 V10.8.0, RAN WG1, Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and Channel Coding (Release 10), Jun. 17, 2013, pp. 1-79. |
3rd Generation Partnership Project (3GPP), TSG RAN WG1 Meeting #86, “RAN1 Chairman's Notes”, Gothenburg, Sweden, Aug. 22-26, 2016, 105 pages. |
3rd Generation Partnership Project; (3GPP) TR 22.891 V1.1.0, 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Feasibility Study on New Services and Markets Technology Enablers; Stage 1 (Release 14), Nov. 2015, 95 pages. |
3rd Generation Partnership Project; (3GPP) TR 23.799, “Technical Specification Group Services and System Aspects Study on Architecture for Next Generation System (Release 14)”, vol. SA WG2, No. V0.5.0, Jun. 8, 2016, pp. 1-179. |
3rd Generation Partnership Project; (3GPP) TR 38.913 V0.2.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on Scenarios and Requirements for Next Generation Access Technologies, (Release 14), Feb. 2016, 19 pages. |
3rd Generation Partnership Project; (3GPP) TS 36.211 V13.1.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 13), Mar. 2016, 155 pages. |
3rd Generation Partnership Project; (3GPP) TS 36.304 V13.0.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) Procedures in idle Mode (Release 13), Dec. 2015, 42 pages. |
3rd Generation Partnership Project; (3GPP) TS 36.331 V13.0.0, Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 13), Dec. 2015, 507 pages. |
3rd Generation Partnership Project; (3GPP) TSG-RAN WG1 #86bis, R1-1610177, “DL Control Channels Overview”, Qualcomm Incorporated, Oct. 10-14, 2016, Lisbon, Portugal, Discussion, Oct. 1, 2016, 6 pages. |
3rd Generation Partnership Project; 3GPP TR 23.799 VO.5.0; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14); May 2016; 179 pages. |
Budisin S. “Decimation Generator of Zadoff-Chu Sequences”, In: Carlet C., Pott A. (eds) Sequences and Their Applications—SETA 2010. SETA 2010. Lecture Notes in Computer Science, vol. 6338. Springer, Berlin, Heidelberg, 2010, 40 pages. |
CATT: “On interference measurement enhancement for multi-user MIMO operation”, 3GPP TSG RAN WG1 Meeting #85, R1-164223, May 14, 2016, May 23, 2016-May 27, 2016, XP051096527. |
CATT: “WF on Interference Measurement Enhancements”, 3GPP TSG RAN WGI Meeting #86bis, R1-1610771, Oct. 18, 2016, Oct. 10, 2016-Oct. 14, 2016, XP051160249. |
Chu, David, “Polyphase Codes With Good Periodic Correlation Properties”, IEEE Transactions on Information Theory, Jul. 1972, 531-532. |
Consideration on System Information Broadcast in New RAT, ZTE, 3GPPTSG-RANWG2 Meeting #93bis, R2-162629, Apr. 15, 2016. |
ETRI, “FS_NEO updated requirement of network slicing”, 3GPP TSG-SA WG1 #74 S1-161171, Apr. 29, 2016, URL:http://www. 3gpp. org/ftp/tsg_sa/WG1_Serv/TSGS1_74_Venice/docs/SI-161171.zip, 6 pages. |
ETRI, “High-level Functional Architecture for the Network Slicing”, 3GPPTSG-SA WG2 #114 SZ-161833, Apr. 6, 2016, URL: http: //www. 3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_114_Sophia_Antipolis/Docs/S2-161833.zip, 7 pages. |
Huawei et al., “Numerology and wideband operation in NR unlicensed”, 3GPP Draft; R1-1803677, 3rd Generation Partnership vol. RAN WG1, No. Sanya, China; Apr. 16, 2018-Apr. 20, 2018, Apr. 15, 2018, Apr. 16, 2018-Apr. 20, 2018. |
Huawei et al., “R1-162116, Discussion on enhanced frame structure for latency reduction in TDD,” 3GPP TSG RAN WG1 #84bis, (Apr. 1, 2016). |
Huawei et al., “Discussion on frame structure for NR”, 3 GPP TSG-RAN WG1#85, R1-164032, May 23-27, 2016, 8 pages. |
Huawei et al.: “Initial access in NR unlicensed”, 3GPP Draft R1-1808062 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, vol. RAN WG1, No. Aug. 10, 2018, Aug. 20, 2018-Aug. 24, 2018. |
Huawei, “HiSilicon, UE Slice Association/Overload control Procedure”, 3GPP TSG-SA WG2 #115 SZ-162605, May 17, 2016, URL:http://www. 3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_115_Nanjing_China/Docs/S2-162605.zip, 11 pages. |
Huawei, HiSilicon LTE-NR tight interworking control plane, R2-164268 LTE-NR tight interworking control plane, May 14, 2016. |
Huawei,R3-161134,“Network slice selection,” RAN WG3 Meeting #92, May 2016. |
IEEE P802.11, Wireless LANs, Proposed TGax draft specification, Comment Resolutions on UL MU Operation, Jul. 25, 2016, 27 pages. |
International Telecommunication Union (ITU-R), “IMT Vision—Framework and overall objectives of the future development of IMT for 2020 and beyond”, Recommendation ITU-R M.2083-0, Sep. 2015, 21 pages. |
ITRI, “Updates to Solution 6. 1.3: Introducing Network Instance ID”, 3GPP TSG-SA WG2 #115 SZ-162666, May 17, 2016, URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_115_Nanjing_China/Docs/S2-162666.zip>. |
MediaTek Inc., “HARQ Enhancement for Improved Data Channel Efficiency” [online], 3GPP TSG-RAN WG1#84b, R1-162797, <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_84b/Docs/R1-162797.zip>, Apr. 2016, 4 pages. |
NGMN 5G Initiative White Paper v1.0, Feb. 17, 2015, 125 pages. |
Nokia et al., R1-163267, On design of DL control channel for shorter TTI operation, 3GPP TSG RAN WG1 #84bis, #GPP Apr. 1, 2016. |
Nokia et al: Feature Lead's Summary on Channel Access Procedures 3GPP Draft; R1-1809801 NRU Channel Access Summary 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, vol. RAN WG1, No. Gothenburg, Sweden; Aug. 23, 2018, Aug. 20, 2018-Aug. 20, 2018. |
Nokia, “Alcatel-Lucent Shanghai Bell”, Slice Selection solution update, 3GPP TSG-SA WG2 #115 SZ-162982, May 27, 2016, URL: http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_115_Nanjing_China/Docs/S2-162982.zip, 15 pages. |
Nokia, “Solutions for Network Slice Selection”, Alcatel-Lucent Shanghai Bell, 3GPP TSGG-RAN WG3 Meeting #92, R3-161356, China, May 23-27, 2016, 9 pages. |
NTT Docomo Inc., “Discussion on frame structure for NR”, 3GPP TSG-RAN WG1#85, R1-165176, May 23-May 27, 2016, 10 pages. |
NTT Docomo, Inc., and Uplink multiple access schemesfor NR [online] and 3GPP TSG-RANWG 1#85R1-165174, the Internet<URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_1281/Docs/R1-165174.zip>, May 27, 2016, 1-4 pages. |
NTT Docomo, Inc., R1-160965, “UL aspects of TTI shortening,” 3GPP TSG RAN WG1 #84, 3GPP (Feb. 5, 2016). |
3rd Generation Partnership Project; 3GPP TS 23.228 V12.1.0; Technical Specification Group Services and System Aspects; IP Multimedia Substystem (IMS); Stage 2 (Release 12), Jun. 2013, 296 pages. |
ASUSTeK, R1-083574, Draft CR on RNTI for UE-specific search space, 3GPP TSG-RAN1 Meeting #54bis, Oct. 2018. |
Damour, N., “List of Common Services Functions-Call for Contributions”, M2M Functional Architecture Technical Specification, Doc# oneM2M-ARC-2013-0304R04-List of oneM2M CSFs- Call for contributions-2.DOC Input Contribution, Jul. 11, 2013, 1-5 pages. |
ETSI TS 102690 V2.0.14 Technical Specification, “Machine-to-Machine Communications (M2M) Functional Architecture”, Jul. 2013, 332 pages. |
European Telecommunications Standards Institute (ETSI), TS 102 690 V1.2.1; Machine-to- Machine Communications (M2M); Functional Architecture, Jun. 2013, 279 pages. |
ITRI, “Discussion on resource utilization for UE-specific BF CSI-RS”, R1-162987, 7.3.3.1.2, 3GPP TSG RAN WG1 Meeting #84b, 2016, 2 Pages. |
Machine-to-Machine Communications (M2M) Functional Architecture, Draft ETSI TS 102 690 V1.1.1, Oct. 2011, 280 pages. |
Motorola Mobility, “Synchronization signal in NR”, 3GPP TSG-RAN WG1#86b R1-1609917, Oct. 2016, 5 Pages. |
OMA (Open Mobile Alliance), OMA-TS-LightweightM2M-V1_0-20130206-D, Lightweight Machine to Machine Technical Specification, Draft Version 1.0—Feb. 6, 2013, 53 pages. |
OneM2M Technical Specification, oneM2M-TS-0001 oneM2M Functional Architecture-V-0.0.3, Jun. 8, 2013, 11 pages. |
“Consideration on TTI shortening for DL”, 3GPP TSG RAN WG1 Meeting #84, R1-161017, Feb. 2016, 4 Pages. |
“Considerations on required downlink physical layer enhancements for shorter TTI”, 3GPP TSG-RAN WG1 Meeting #84, R1-160786, Feb. 2016, 6 Pages. |
“Discussion on downlink control channel design,” 3GPP TSG RAN WG1 Meeting #86bis, R1-1609432, Oct. 10-14, 2016, p. 5. |
“Nokia Networks Enhancements for MTC Paging”, R3-151590 Discussion Paper MTC Paging vB, Aug. 14, 2015. |
“Study on TTI shortening for downlink transmissions”, 3GPP TSG RAN WG1 Meeting #84 , R1-160649, Feb. 2016, 6 Pages. |
3GPP TS 36.211 V13.0.0, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 13)”, Dec. 2015, 141pages. |
3GPP TSG GERA1 Adhoc #3 GPC150521, Samsung Electronics, “Discussions of Grant-Free Multiple Access in CIoT (Update GPC150512)”, Jul. 2015, 9 pages. |
3GPP TSG RAN WG1 Meeting #84bis R1-163049, Design Options for Longer Cyclic Prefix for MBSFN Subframes, Apr. 2016, 3 pages. |
3GPP TSG-RAN WG2 Meeting #95 R2-164693, Samsung, “System Information Signalling Design in NR” Aug. 2016, 6 pages. |
3GPP TSG-RAN1#85 R1-164869, “Low code rate and signature based multiple access scheme for New Radio,” May 23-27, 2016, pp. 1-4. |
3GPP TSG-RAN2 meeting #95bis R2-166202, Huawei et al., “Further Discussions of Minimum SI” Oct. 2016, 3 pages. |
3GPP TSG-RAN2 Meeting #95bis R2-166203, Huawei et al., “Delivery of “Other SI” in NR”, Oct. 2016, 5 pages. |
3GPP TSG=RAN WG2 Meeting #95bis, ETSI MCC, “Skeleton report”, Oct. 2016, 5 pages. |
3rd Generation Partnership Project (3GPP) R2-162571 TSGRAN WG2 Meeting #93bis, Introduction of Virtual Cell, CATT, Dubrovnik, Croatia, Apr. 11-15, 2016, 3 pages. |
3rd Generation Partnership Project (3GPP) RP-160301 TSG RAN Meeting #71, Motivation for new WI on Light Connection in LTE, Huawei, HiSilicon, Goteborg, Sweden, Mar. 7-11, 2016, 14 pages. |
3rd Generation Partnership Project (3GPP) RP-160425 TSG RAN Meeting #71, Further enhancements on signaling reduction to enable light connection for LTE, Intel Corporation, Gothenburg, Sweden, Mar. 7-10, 2016, 7 pages. |
3rd Generation Partnership Project (3GPP) RP-160540 TSG RAN Meeting #71, New WI proposal: Signalling reduction to enable light connection for LTE, Gothenburg, Sweden, Mar. 7-10, 2016, 7 pages. |
3rd Generation Partnership Project (3GPP) RP-161214 TSG RAN Meeting #72, Revision of SI: Study on New Radio Access Technology, NTT DOCOMO, Busan, Korea, Jun. 13-16, 2016, 8 pages. |
3rd Generation Partnership Project (3GPP) S1-152395 Revision of S1-152074, ZTE Corporation et al., “Update the network slicing use case in Smarter”, ZTE Smarter Update the Network Slicing Use case REV3, vol. SA WG1, No. Belgrade Serbia, Aug. 24, 2015, 3 pages. |
3rd Generation Partnership Project (3GPP) S1-161323 TSG-SA WG1 Meeting #74, Editorial cleanup and alignment of eMBB TR22.863, Venice, Italy, May 9-13, 2016, 4 pages. |
3rd Generation Partnership Project (3GPP) S2-161198 SA WG2 Meeting #113AH, Solution for optimized UE sleep state and state transitions, Sophia Antipolis, France, Feb. 23-26, 2016, 3 pages. |
3rd Generation Partnership Project (3GPP) S2-161324 SA WG2 Meeting #113, Solution to Key Issue on Mobility Framework, Sophia Antipolis, FR, Feb. 23-26, 2016, 3 pages. |
3rd Generation Partnership Project (3GPP) S2-162982 was S2-162717-MDD and Slice Selection in core and Ran V1, 3rd vol. SA WG2, , Nokia et al., No. Nanjing, P.R. China; May 27, 2016, 13 pages. |
3rd Generation Partnership Project (3GPP) SA WG2 Meeting #115 S2-162511 “Common CP functions and dedicate CP function for simultaneous multiple Network Slice (update of solution 1.3)” May 23-27, 2016, 4 pages. |
3rd Generation Partnership Project (3GPP) T-RAN WG1#85 R1-165027 “Basic Frame Structure Principles for 5G” May 23-27, 2016, 6 pages. |
3rd Generation Partnership Project (3GPP) TR 22.861 V14.1.0, Technical Specification Group Services and Systems Aspects, Feasibility Study on New Services and Markets Technology Enablers for Massive Internet of Things, Stage 1 (Release 14), Sep. 2016, 28 pages. |
3rd Generation Partnership Project (3GPP) TR 22.862 V14.1.0, Technical Specification Group Services and System Aspects, Feasibility Study on New Services and Markets Technology Enablers for Critical Communications, Stage 1 (Release 14), Sep. 2016, 31 pages. |
3rd Generation Partnership Project (3GPP) TR 22.863 V0.3.1, Technical Specification Group Services and System Aspects, Feasibility Study on New Services and Markets Technology Enablers—Enhanced Mobile Broadband; Stage 1 (Release 14), Feb. 2016, 13 pages. |
3rd Generation Partnership Project (3GPP) TR 22.863 V14.1.0, Technical Specification Group Services and System Aspects, Feasibility Study on New Services and Markets Technology Enablers—Enhanced Mobile Broadband, Stage 1 (Release 14), Sep. 2016, 21 pages. |
3rd Generation Partnership Project (3GPP) TR 22.864 V14.1.0, Technical Specification Group Services and System Aspects, Feasibility Study on New Services and Markets Technology Enablers—Network Operation, Stage 1 (Release 14), Sep. 2016, 35 pages. |
3rd Generation Partnership Project (3GPP) TR 22.891 V14.2.0, Technical Specification Group Services and System Aspects, Feasibility Study on New Services and Markets Technology Enablers, Stage 1 (Release 14), Sep. 2016, 95 pages. |
3rd Generation Partnership Project (3GPP) TR 23.720 V13.0.0, Technical Specification Group Services and System Aspects, Study on architecture enhancements for Cellular Internet of Things, (Release 13), Mar. 2016, 94 pages. |
3rd Generation Partnership Project (3GPP) TR 36.881 V14.0.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Study on Latency Reduction Techniques for LTE (Release 14), Jun. 2016, 249 pages. |
3rd Generation Partnership Project (3GPP) TR 36.897 V13.0.0, Technical Specification Group Radio Access Network, Study on Elevation Beamforming/Full-Dimension (FD) Multiple Input Multiple Output (MIMO) for LTE; (Release 13), Jun. 2015, 58 pages. |
3rd Generation Partnership Project (3GPP) TR 36.912 V13.0.0, Technical Specification Group Radio Access Network, Feasibility study for Further Advancements for E-UTRA (LTE-Advanced) (Release 13), Dec. 2015, 273 pages. |
3rd Generation Partnership Project (3GPP) TR 38.801 V0.2.0, Technical Specification Group Radio Access Network, Study on New Radio Access Technology: Radio Access Architecture and Interface (Release 14), Jun. 2016, 20 pages. |
3rd Generation Partnership Project (3GPP) TR 38.913 V14.3.0, Technical Specification Group Radio Access Network, Study on Scenarios and Requirements for Next Generation Access Technologies, (Release 14), Jun. 2017, 39 pages. |
3rd Generation Partnership Project (3GPP) TR 45.820 V13.1.0, Technical Specification Group GSM/EDGE Radio Access Network, Cellular system support for ultra-low complexity and low throughput Internet of Things (CIoT) (Release 13), Nov. 2015, 495 pages. |
3rd Generation Partnership Project (3GPP) TS 23.060 V13.6.0, Technical Specification Group Services and System Aspects, General Packet Radio Service (GPRS), Service description, Stage 2 (Release 13), Mar. 2016, 362 pages. |
3rd Generation Partnership Project (3GPP) TS 23.401 V13.6.1, Technical Specification Group Services and System Aspects, General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 13), Mar. 2016, 365 pages. |
3rd Generation Partnership Project (3GPP) TS 24.302 V13.5.0, Technical Specification Group Core Network and Terminals, Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 (Release 13), Mar. 2016, 126 pages. |
3rd Generation Partnership Project (3GPP) TS 36.133 V14.7.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Requirements for support of radio resource management (Release 14), Mar. 2018, 2997 pages. |
3rd Generation Partnership Project (3GPP) TS 36.213 V13.0.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical layer procedures (Release 13), Dec. 2015, 326 pages. |
3rd Generation Partnership Project (3GPP) TS 36.300 V13.3.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Overall description; Stage 2 (Release 13), Mar. 2016, 295 pages. |
3rd Generation Partnership Project (3GPP) TS 36.321 V13.0.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Medium Access Control (MAC) protocol specification (Release 13), Dec. 2015, 82 pages. |
3rd Generation Partnership Project (3GPP) TS TSG RAN WG1 Meeting #84bis, Busan, Korea ,Intel Corporation, Overview of New Radio Access Technology Requirements and Designs, 8.1.1, Discussion and Decision, Apr. 2016, 4 pages. |
3rd Generation Partnership Project (3GPP) TS TSG RAN WG1 Meeting #85,2016 Nanjing, China 23rd-27th,NTT DoCoMo, Inc., Uplink Multiple Access Schemes for NR, 7.1.3.2, Discussion and Decision, May 2016, 4 pages. |
3rd Generation Partnership Project (3GPP) TSG RAN WG1 #84bis Meeting, R1-163757, Way Forward on Channel Coding Evaluation for 5G New Radio, Busan, Korea, Apr. 11-15, 2016, Agenda Item 8.1.6.1, 5 pages. |
3rd Generation Partnership Project (3GPP) TSG RAN WG1 #85, R1-164013, Framework for Beamformed Access, Samsung, Nanjing, China, May 23-27, 2016, 4 pages. |
3rd Generation Partnership Project (3GPP) TSG RAN WG1 #85, R1-164014, Discussion on RS for Beamformed Access, Samsung, Nanjing, China, May 23-27, 2016, 3 pages. |
Qualcomm Incorporated, S2-162339, “Solution for key issue 1 on Network Slicing: Network Slice and Network Functions Selection based on evolved eDECOR model,” SA WG2 Meeting #115, May 2016. |
Qualcomm Incorporated: “Frame structure requirements”, 3GPP Draft; vol. RAN WG1, No. Nanjing, China; May 14, 2016. |
Qualcomm, 3GPP R1-1612062, TSG-RAN WG1 #87, Control Channel for slot format indicator, Nov. 14-18, 2016 (Year: 2016). |
Samsung: “Signaling of Slot Structure”, 3GPP Draft; R1-1609127, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lucioles; F-06921 Sophia Anti Polis CEO EX ; France, RAN WG1, No. Lisbon, Portugal; Oct. 10, 2016-Oct. 14, 2016 Sep. 30, 2016. |
Sesia et al., “LTE—The UMTS Long Term Evolution”, Chapter 9.3.3., LTE—The UMTS Long Term Evolution : from theory to Practice; Jul. 20, 2011, pp. 198-200. |
Spreadtrum Communications, R1-164584, “HARQ feedback for sTTI scheduling,” 3GPP TSG RAN WG1 #85, 3GPP (May 13, 2016). |
ZTE et al., “Forward compatibilty for numerology and fr ame structure design”, R1-164261, 3GPP TSG-RAN WG1#85, May 23-27, 2016, 7 pages. |
ZTE, “Consideration on RAN architecture impacts of network slicing”, 3GPP TSG-RAN WG2 Meeting #93bis, R2-162627, Croatia, Apr. 11-15, 2016, 10 pages. |
ZTE: “Considerations on channel access procedure for NR-U”, 3GPP Draft; R2-1811281 Considerations on Random Access Procedure for NR-U, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre vol. RAN WG2, No. Gothenburg, Sweden; Aug. 9, 2018, Aug. 20, 2018-Aug. 24, 2018. |
Huawei et al., “Design of initial downlink transmission for LBE-based LAA”, R1-150980, 3GPP TSG RAN WG1, Mar. 2015, 6 Pages. |
Nokia et al., “On supported Shorter TTI lengths and its configurability”, 3GPP TSG RAN WG1 Meeting #85, 2016, R1-164945, 4 pages. |
Spreadtrum Communications, “HARQ feedback for sTTI scheduling”, R1-162546, Apr. 2016, 3GPP TSG RAN WG1 Meeting #84bis, 4 Pages. |
Mavlankar et al., “Video Streaming with Interactive Pan/Tilt/Zoom”, High-Quality Visual Experience, Jan. 2010, pp. 26. |
Sun, et al., The Dynamic Videobook: A Hierarchical Summarization for Surveillance Video, Published in IEEE Sep. 2013, pp. 3963-3966. |
Third Generation Partnership Project, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding (Release 13),” 3GPP TS 36.212 V13.2.0 (Jun. 2016). |
LG Electronics, “Transmission modes for Un PDSCH”, 3GPP TSG RAN WG1 Meeting #63, R1-106138, 2010, pp. 3. |
Number | Date | Country | |
---|---|---|---|
20220361180 A1 | Nov 2022 | US |
Number | Date | Country | |
---|---|---|---|
62416902 | Nov 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17132026 | Dec 2020 | US |
Child | 17870284 | US | |
Parent | 16346972 | US | |
Child | 17132026 | US |