Physical channels in new radio
By improving the HARQ processing mechanism and channel signaling scheduling, the reliability and delay problems of HARQ transmission in radio communications are solved, and higher URLLC and mMTC transmission efficiency and reliability are achieved.
Patent Information
- Application Number
- CN202111184696.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2016-09-26
- Filing Date
- 2017-04-20
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2037-04-20
AI Technical Summary
When existing radio communication technologies achieve higher reliability and lower latency HARQ transmission methods, they face the challenges of channel reliability and resource provision, especially in low latency and unauthorized operation scenarios, which are difficult to meet URLLC and mMTC. demand.
By improving the HARQ processing mechanism, multi-bit ACK/NACK signaling, periodic response periods and irregular periods are used to schedule physical HARQ indicator channel signaling, combined with resource blocks and demodulation reference signals to optimize transmission, supporting low latency and unauthorized Operation to improve the reliability of control information and resource supply.
It realizes effective HARQ transmission in low latency and high reliability scenarios, improves the transmission reliability and efficiency of URLLC and mMTC, reduces system overhead, and adapts to resource allocation in different use cases.
Smart Images

Figure CN113965295B_ABST
Abstract
Description
[0001] This application is a divisional application of the patent application with international application number PCT / US2017 / 028596 and national application number 201780037931.0, entitled “Physical Channels in New Radio”, filed on April 20, 2017.
[0002] CROSS-REFERENCE TO RELATED APPLICATIONS
[0003] This application claims priority to U.S. Provisional Patent Application No. 62 / 325,335 filed on April 20, 2016 and U.S. Provisional Patent Application No. 62 / 399,921 filed on September 26, 2016, the disclosures of which are incorporated herein by reference in their entireties. Background Art
[0004] Existing and proposed telecommunication networks and sub-networks may operate according to various standards such as LTE, 4G, 5G, and 3GPP to support various applications such as real-time communications, entertainment media transmission, computer data transmission, and Internet of Things (IoT), IoT, and Machine-to-Machine (M2M) operations. The various standards include parameter sets for allocating communication resources by subcarriers and time slots. The various standards also include mechanisms such as hybrid automatic repeat request (HARQ) and physical hybrid automatic repeat request indicator channel (PHICH) signaling for ensuring reception of transmissions. Summary of the invention
[0005] Various embodiments described herein improve reliability for various scenarios in NR. Exemplary scenarios addressed include, but are not limited to: HARQ transmission methods for higher reliability, lower latency, erasure channels, unlicensed channels, and unequal error protection; reliability improvement of control information such as DL control information and A / N; and resource provisioning for low latency and unlicensed operation.
[0006] In one example, the apparatus transmits a transmission including a HARQ process until a transmission limit. If the transmission limit is reached or if a positive acknowledgement is received, the apparatus terminates the transmission including the HARQ process. In an example, at least two transmissions are transmitted before the positive acknowledgement is received. In another example, the apparatus receives a negative acknowledgement and transmits the transmission after receiving the negative acknowledgement until the transmission limit is reached.
[0007] Physical hybrid automatic repeat request indicator channel signaling can be scheduled by determining a regular response period and selecting the following irregular interval, wherein the irregular period can be one of multiple fixed opportunities within a short transmission time interval defined by a transmission time interval duration, a resource block, and a demodulation reference signal for an uplink transmission. The irregular interval can be selected from a series of opportunities associated with multiple transmission time intervals multiplexed in the uplink. The transmission can include multiple multiplexed parameter sets. The opportunity can be defined by a radio resource control, a master information block, or a system information block and modified via a control unit of a medium access control. An ACK / NACK response can be piggy-backed on a physical downlink shared data channel signal at a downlink grant, and multiple responses can be jointly encoded.
[0008] Multi-bit ACK / NACK signaling can be used to efficiently express the status of individual code blocks or code block groups within a transport block.
[0009] The non-grant transmission may be implicitly acknowledged, for example, via a response included in the downlink control information or sent via a physical hybrid automatic repeat request indicator channel.
[0010] This summary is provided to introduce in simplified form a selection of concepts 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 address any or all disadvantages noted in any part of this disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1 is an exemplary DL transmission chain for a transport block.
[0012] Figure 2 is an example of a MAC PDU.
[0013] Figure 3 An example of a contention-based random access procedure is shown.
[0014] Figure 4 The physical resource block (PRB) structure in the Long Term Evolution (LTE) communication standard is described.
[0015] Figure 5 An exemplary resource grid structure for a transmission time interval (TTI) using normal cyclic prefix (CP) symbols is shown.
[0016] Figure 6An exemplary time sequence of Physical Hybrid ARQ Indicator Channel (PHICH) groups mapped to three Resource Element Groups (REGs) is shown.
[0017] Figure 7 An exemplary PHICH processing flow is shown.
[0018] Figure 8 An uplink component carrier with an associated downlink component carrier of a PHICH with and without cross-carrier scheduling is illustrated.
[0019] Fig. 9 is an exemplary time sequence of eight parallel synchronous hybrid automatic repeat request (HARQ) processes.
[0020] Fig.10 It is an illustration of the concept of network slicing.
[0021] Fig.11 Telecommunications in applications where low latency may be required in uplink (UL) or downlink (DL) transmissions are described.
[0022] Fig.12 is a chart of the number of users and bit rates supported by various network technologies, broken down into general ranges for various applications that use those bit rates and amount of users.
[0023] Fig.13 is Fig.33 3D graph of general latency, reliability, and spectral efficiency for the group identified in .
[0024] Fig.14 Two time series of PHICH responses to UL transmissions are shown, one for a short TTI (sTTI) of 1 mS and the other for an sTTI of 0.25 mS.
[0025] Fig.15 Illustrates the high latency in retransmission of HARQ process #2 with 0.5mS sTTI, where other processes have 1mS duration.
[0026] Fig.16 An exemplary process flow for multiplexing different parameter sets is shown.
[0027] Fig.17 An example of NR-DCI for configuring HARQ retransmissions in multiple subframes is shown.
[0028] Fig.18 A / N resource allocation for transmission and retransmission in self-constrained subframes is shown.
[0029] Fig.19 An example is shown of how retransmission may occur even before the A / N is received.
[0030] Fig. 20 An example of a retransmission that is terminated upon receipt of an ACK is shown.
[0031] Fig.21 An example of retransmissions being stopped once the maximum limit is reached is shown.
[0032] Fig. 22 An exemplary retransmission with a period equal to 2 is shown.
[0033] Fig.23 An exemplary method for a UE to retransmit UL payload is shown.
[0034] Fig.24 An example of multiple RVs of a HARQ process transmitted in a single subframe is shown.
[0035] Fig.25 Examples of NR-DCI and NR-PDSCH for URLL users are shown.
[0036] Fig.26 An example of uNR-PDCCH allocation for multiple RVs of a data packet is shown.
[0037] Fig. 27 An example of uNR-PDCCH allocation for multiple HARQ processes is shown.
[0038] Fig.28 An example of a URLL UE procedure for receiving authorization is shown.
[0039] Fig.29 An example of selectively not puncturing some resources to maintain eMBB performance is shown.
[0040] Fig.30 It is shown that control and RS signaling are not affected by URLL transmission.
[0041] Fig.31 An example of a UL non-grant transmission interfering with a scheduled eMBB subframe is shown.
[0042] Fig.32 An example of a MAC PDU containing a response to an ungranted UL transmission is shown.
[0043] Fig.33 An example of implicit confirmation through an unauthorized response procedure is shown.
[0044] Fig.34 An example of implicit validation through an unauthorized response procedure including contention resolution is shown.
[0045] Fig.35An example of UL ungranted retransmission over eMBB is shown.
[0046] Fig.36 An example of CBs grouped in K groups, each with its own A / N, is shown.
[0047] Fig.37 An example of a header and MAC CE in one group with its own A / N is shown.
[0048] Fig.38 An example of retransmission of a Naked CB is shown.
[0049] Fig.39 Examples of different numbers of A / N resources for users multiplexed in CDM are shown.
[0050] Fig.40 An exemplary resource grid showing multiplexed parameter sets.
[0051] Fig.41 An exemplary resource grid with PHICH opportunities in a DL signaling interval is shown.
[0052] Fig.42 An exemplary time sequence of ACK / NACK (A / N) signaling using sTTIs of different durations is shown.
[0053] Fig.43 An exemplary time sequence of ACK / NACK (A / N) signaling of two user equipment (UE) nodes multiplexing A / N is shown.
[0054] Fig.44 An exemplary time sequence with PHICH collisions is shown.
[0055] Fig.45 An exemplary time sequence of DL with piggyback PHICH and common PHICH using 1 ms TTI to signal PHICH is shown.
[0056] Fig.46 An exemplary time sequence of DL with piggyback PHICH and common PHICH using 0.5 ms TTI to signal PHICH is shown.
[0057] Fig.47 An exemplary resource grid with PHICH piggybacked on a PD PDSCH grant is shown.
[0058] Fig.48 An example process flow of a DL transmission chain is shown for piggybacking a PHICH on a PDSCH and generating OFDM symbols with a CP for transmission.
[0059] Fig.49 Two exemplary HARQ process time sequences are shown.
[0060] Fig.50 An exemplary resource grid for the UL multiplexing parameter sets for three UEs is shown.
[0061] Fig.51 It shows that the DL bearer Fig.24 An exemplary resource grid for the DL of a common PHICH parameter set for a UE depicted in FIG.
[0062] Fig.52 A flow chart illustrating an exemplary method by which a UE may obtain a PHICH is shown.
[0063] Fig.53 An exemplary resource grid for allocating PHICH to two parameter sets is shown.
[0064] Fig.54 A flow chart of another exemplary method by which a UE may obtain a PHICH parameter set is shown.
[0065] Fig.55 An exemplary communication system is shown.
[0066] Fig.56 is a block diagram of an exemplary apparatus or device, such as, for example, a wireless transmit / receive unit (WTRU), configured for wireless communications.
[0067] Fig.57 is a system diagram of a first exemplary radio access network (RAN) and core network.
[0068] Fig.58 is a system diagram of a second exemplary radio access network (RAN) and core network.
[0069] Fig.59 is a system diagram of a third exemplary radio access network (RAN) and core network.
[0070] Fig.60 is a block diagram of an exemplary computing system that may embody one or more devices of a communication network such as a RAN, a core network, a public switched telephone network (PSTN), the Internet, or certain nodes or functional entities in other networks. DETAILED DESCRIPTION
[0071] Hybrid automatic repeat request (HARQ) processing, indicators, and similar methods can be used to improve new radio performance in a variety of ways. For example, the HARQ process can be made to retransmit multiple times even before a response is expected. Separate acknowledgments can be provided for various code blocks within a single transport block.
[0072] Multi-bit ACK / NACK signaling can be used to efficiently express the status of individual code blocks or code block groups within a transport block.
[0073] The non-grant transmission may be implicitly acknowledged by, for example, including a response in downlink control information or may be sent over a physical hybrid automatic repeat request indicator channel.
[0074] Physical HARQ indicator channel signaling may be scheduled by determining a regular response period and selecting an irregular interval, which may be one of a plurality of fixed opportunities within a short transmission time interval defined by the transmission time interval duration, resource blocks, and demodulation reference signals of the uplink transmission.
[0075] Table 1 is a list of acronyms related to service level technology that may appear in the above description. Unless otherwise specified, the acronyms used herein refer to the corresponding terms listed below.
[0076] Table 1
[0077] Abbreviations
[0078]
[0079]
[0080]
[0081]
[0082]
[0083] It is expected that NR will target a much lower BLER for data than LTE (e.g. a BLER of 10 or less). Currently the operating point for LTE is typically 10-1 for a single transmission, although it is a proprietary configuration in the eNB. It is expected that NR's target BLER will be achieved through more robust low-rate codes and possible retransmissions.
[0084] 3GPP TR 38.913 defines the scenarios and requirements for next generation access technologies. According to the requirements, for URLLC, the target for user plane latency should be 0.5ms for UL and 0.5ms for DL. This means that BLER must be achieved within these latency constraints.
[0085] LTE supports a minimum packet size of 40 bits. If a transport block (TB) is smaller than 40 bits, it is zero-padded to have 40 bits. A cyclic redundancy check (CRC) is applied to the TB. At the receiver, if the CRC check fails, a non-acknowledgement (NACK) is sent and then retransmitted.
[0086] Split transport block sizes greater than 6144 into multiple code blocks of no more than 6144 bits. Apply CRC to each code segment. Even if a single CB is in error, the HARQ retransmission consists of the entire transport block. Figure 1 An example of a data processing chain in LTE UL is shown.
[0087] It has been agreed in NR that a subframe can contain a fixed number of symbols. It can support multiple control regions and one or more data transmissions. Multiple parameter sets can be multiplexed in a subframe via TDM / FDM.
[0088] 3GPP TS 36.300 outlines the different features of MAC and RRC control, as shown in Table 2 below.
[0089] Table 2
[0090] Overview of the Differences between MAC and RRC Control
[0091]
[0092] The difference between MAC and RRC control is signaling reliability. Due to signaling reliability, signaling involving state transitions and radio bearer configuration should be performed by RRC. Basically, RRC also performs signaling performed by RRC in UTRA for E-UTRA.
[0093] The MAC sublayer is responsible for multiplexing MAC service data units (SDUs) belonging to one or more logical channels into transport blocks (TBs) delivered to / from the physical layer on a transport channel / demultiplexing MAC service data units (SDUs) from the above transport blocks. A MAC protocol data unit (PDU) consists of a MAC header, zero or more MAC SDUs, zero or more MAC control elements, and optional padding, such as Figure 2 shown.
[0094] Figure 3 An exemplary way of performing contention-based random access is illustrated. In step 1, a random access preamble is sent on the RACH in the uplink. This includes the transmission of a RACH preamble, which allows the eNB to estimate the transmission time of the UE.
[0095] In step 2, a random access response is generated by the MAC on the DL-SCH. The network transmits a timing advance command to adjust the UE transmission time. The network also allocates UL resources to the UE to be used in step 3.
[0096] In step 3, the first scheduled UL transmission is made on the UL-SCH. This includes transmitting the mobile terminal identifier to the network using the UL-SCH.
[0097] In step 4, a contention resolution message from the network is sent to the UE on the DL-SCH.
[0098] In some cases, contention-free random access is used to reestablish uplink synchronization upon downlink data arrival, handover, and positioning. In an example, the first two steps of the above procedure are applicable because no contention resolution is required when performing the contention-free random access procedure.
[0099] It is recognized here that a new HARQ mechanism is needed. Retransmissions in LTE have a minimum delay of 8ms. URLLC may require lower delay and higher reliability than LTE. Reliability can be defined by the probability of success of transmitting X bytes within the delay limit. In other words, reliability can be defined as the percentage of lost, erroneous, or delayed messages (e.g., exceeding a given delay limit) should be low. For example, for URLL, the target of user plane delay is 0.5mS for UL and 0.5ms for DL, which means a 1ms round trip delay or equivalently a maximum 1ms retransmission delay. A reliability of 1-10-5 within a 1ms delay means a reliability of 1-10-5 with a retransmission delay not exceeding 1mS. This is the case of URLL applications with a target reliability of 1-10-5 within a 1ms delay limit. For such applications, reliable transmission of messages within a 1ms delay limit should be provided at a reliability level of 1-10-5, which means that only 10-5 transmissions may fail (including retransmissions) or result in a delay exceeding the 1mS limit.
[0100] It is recognized here that low latency and high reliability are often conflicting requirements. In some cases, existing HARQ mechanisms in LTE / LTE-A cannot meet these goals. Thus, it is recognized here that NR may require new solutions to address HARQ design for higher reliability and lower latency. In addition, HARQ mechanisms have not yet been defined for unlicensed UL that can be used for URLL and mMTC. Similarly, in terms of UL and DL, eMBB performance may be affected due to erasures (DL) or interference (UL) from URLL transmissions. Thus, it is further recognized here that HARQ solutions for improving the robustness of eMBB transmissions should be considered.
[0101] Assuming that for some use cases in NR such as URLLC and mMTC, data transmission is required to be more robust than in LTE, it is recognized here that A / N transmission should also improve robustness to errors. Otherwise, errors in A / N will affect the data BLER in retransmissions. LTE targets P(N→DTX / A)=0.1%, P(A→N / DTX)=1% (DTX is discontinuous transmission). For URLLC, NR may require P(N→DTX / A)=0.001%, P(A→N / DTX)=0.01% or lower. Therefore, it is recognized here that NR needs a solution that can achieve higher A / N accuracy with minimal resources and latency. Similarly, it is further recognized here that for URLLC and mMTC, higher robustness is needed in the control channel to support more robust data. For example, this can be achieved by encoding the control information at a lower rate, but this may be at the expense of increased latency and resources. Therefore, it is recognized here that NR needs a solution for providing optimal performance with acceptable latency and resource overhead.
[0102] Assuming that the payload size can be lower than the minimum size provided by LTE (typically used for URLL and mMTC) or larger than the maximum code block size supported by LTE (typically used for eMBB), NR's transport chain should evolve to support these modes with minimum latency or improved reliability or power saving depending on the use case. For example, LTE supports a minimum TB (transport block) size of 40 bits. If the payload is smaller, zeros will be padded to 40 bits. LTE supports up to 6144 bits as its maximum CB (code block). CRC is applied to TBs before segmentation into CBs. CRC is also applied to each CB. The receiver sends one A / N bit per TB. This design can be improved in NR to support other payload sizes, lower latency, and higher reliability.
[0103] In addition, it is recognized here that there is a need to improve the reliability of MAC CE for certain use cases. This can be achieved, for example, by redesigning the transport chain in LTE / LTE-A. RAN2#94 initially discussed mobility in NR and agreed that two levels of network control can be supported for mobility: (1) RRC driven at the 'cell' level ('cell' refers to FFS); and (2) zero / minimal RRC involvement (e.g. at MAC / PHY).
[0104] Signaling related to mobility needs to be very reliable. The cell-level mobility that can be managed by the RRC layer in the NR network has ~10 -6 The proposed mobility signaling for NR systems is expected to have similar reliability at the MAC / PHY layer. However, for LTE, MAC control signaling has a reliability of ~10 for signaling over PDCCH.-2 reliability and ~10 for signaling via MAC control PDUs -3 Therefore, it is recognized here that more reliable MAC signaling is needed to support MAC layer mobility management in NR networks. It should be noted that various use cases (such as eMBB, URLL, and mMTC) may require improved MAC CE reliability.
[0105] Higher MAC CE reliability may also be required to support SI (system information) signaling over MAC CE (especially for URLL and mMTC).
[0106] Methods and apparatus for providing additional hybrid automatic repeat request (HARQ) opportunities and physical hybrid automatic repeat request indicator channel (PHICH) resources are presented to reduce system overhead and provide lower retransmission latency in networks that employ one or more parameter sets. For example, flexible HARQ ACK and NACK (A / N) response times may be allowed when occurring within a tolerance window provided for uplink (UL) transmissions.
[0107] Multiple PHICH signaling opportunities may be provided within a short transmission time interval sTTI duration, each of which is referred to as a "PHICH opportunity". The configuration of the opportunities is contained in system information such as a master information block (MIB). Alternatively, the location of the PHICH may be tied to the sTTI duration in addition to the uplink resource block (RB) location and demodulation reference signal (DMRS) cyclic code.
[0108] When the terminal is scheduled with a downlink (DL) grant, the A / N response can be piggybacked with the physical downlink shared data channel (PDSCH) resources. This avoids additional signaling related to PHICH resource configuration. When multiple PHICH transmissions for one user equipment (UE) are carried in the PDSCH, they can be jointly coded.
[0109] Synchronous uplink HARQ signaling can be achieved using multiplexed sTTIs, either by a priori sTTI scheduling or by radio resource control (RRC) and media access control (MAC) processing of HARQ in multiplexed sTTI uplinks. For the latter method, when multiple sTTI durations are multiplexed by terminals in the uplink, in order to maintain synchronous HARQ without the need for downlink control information (DCI) signaling to indicate the HARQ process number for uplink authorization, the sequence of HARQ processes transmitted to the terminal can be configured by RRC at the sTTI duration of the HARQ process supported by the terminal. The terminal can then be reconfigured by the control unit (CE) of the MAC.
[0110] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunication network technologies, including radio access, core transport networks, and service capabilities-including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), and LTE Advanced standards. 3GPP has begun to work on the standardization of next-generation cellular technology (commonly referred to as "5G"). It is expected that 5G development will include the definition of next-generation radio access technology (new RAT), which is expected to consist of multiple radio layers that work together in a multi-connection framework. It is expected that the framework will include the continued evolution of radio access ("5G evolution"), the provision of new flexible radio access below 6GHz ("5G flexible access"), and the provision of new ultra-mobile broadband radio access above 6GHz ("5G ultra-mobile broadband"). It is expected that 5G flexible access will consist of new non-backward compatible radio access in new spectrum below 6GHz, and it is expected to include a wide range of 5G use cases that can be multiplexed together in the same spectrum in different working modes to address a variety of different needs. 5G Ultra Mobile Broadband is expected to include centimeter wave and millimeter wave spectrum, which will provide opportunities for ultra mobile broadband access, such as indoor applications and hotspots. In particular, 5G Ultra Mobile Broadband is expected to share a common design framework with 5G Flexible Access, with centimeter wave and millimeter wave specific design optimizations. 5G is also expected to include specifications for non-3GPP radio access (such as WiFi).
[0111] 3GPP has identified various use cases that 5G is expected to support, which leads to various user experience requirements for data rate, latency, and mobility. The proposed use cases include the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, ultra-high broadband access indoors, broadband access in crowds, 50+Mbps everywhere, ultra-low-cost broadband access, in-vehicle mobile broadband), critical communications, massive machine-type communications, network operations (e.g., network slicing, routing, migration and intercommunication, energy saving), and enhanced cellular vehicle-to-everything (eV2X) communications. Specific use cases in these categories include, for example, monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connectivity, automotive emergency calls (ecalls), disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile Internet, virtual reality, and more. All of these use cases and others are considered here.
[0112] With such a variety of use cases, aspects of wireless communications disclosed and claimed herein may be embodied in a wide variety of wireless communication devices, including user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, tablets, netbooks, personal computers, wireless sensors, consumer electronics, wearable devices (such as smart watches or smart clothing), medical or e-health equipment, robots, industrial equipment, drones, vehicles (such as cars, trucks, trains or airplanes), and the like.
[0113] LTE defines UL and DL Transmission Time Intervals (TTIs) as 1 mS. Also referred to as a "subframe" in LTE, a TTI corresponds to a duration in which up to two dynamically sized transport blocks are passed to the physical layer and transmitted over the radio interface for each component carrier. The number of transport blocks transmitted within a TTI depends on the configuration of the multi-antenna transmission scheme. Without spatial multiplexing, there is at most a single transport block in a TTI. With spatial multiplexing, with transmissions on multiple layers in parallel with the same terminal, there are two transport blocks within a TTI.
[0114] In LTE, each 0.5 milliseconds of a TTI is called a "time slot". A physical resource block (PRB) is defined as a resource block corresponding to 180kHz in the frequency domain and 0.5mS in time. PRBs are allocated in pairs in the time domain by the scheduler in the UL and DL. A UL or DL grant is always at least one TTI long.
[0115] Figure 4 The resource structure of a single PRB in LTE is shown. Each time slot contains 6 or 7 symbols, depending on whether the configuration uses extended CP or normal CP. OFDM symbols are used in DL and SC-FDMA symbols are used in UL. A frame in LTE consists of 10 subframes and is therefore 10 mS long. Figure 5 The resource grid structure of 1 TTI is shown assuming a normal CP for symbols. In the time domain structure in LTE, various physical channels are multiplexed into resource elements of a TTI.
[0116] In the UL physical layer, the transmission of the LTE uplink includes the following PHY channels: Physical Random Access Channel (PRACH); Physical Uplink Shared Channel (PUSCH) for carrying data and the following control information, including ACK / NACK response (A / N) to DL authorization, channel state information (CSI), precoder matrix index (PMI), rank indicator (RI), and scheduling request (SR) for DL channels; and Physical Uplink Control Channel (PUCCH) for carrying A / N, CSI, PI, RI, and SR. PUCCH resources are allocated at the outer edge of the frequency band of the remaining part in the middle occupied by PUSCH resources. In addition, two reference signals are used in UL. Demodulation Reference Signal (DM-RS) is used to estimate the UL channel. Sounding Reference Signal (SRS) is used to obtain UL channel quality estimation.
[0117] Several physical channel types are defined for LTE. The Physical Downlink Shared Channel (PDSCH) is the primary physical channel used for unicast data transmission and also for paging information transmission. The Physical Broadcast Channel (PBCH) carries part of the system information required by terminals to access the network. The Physical Multicast Channel (PMCH) is used for MBSFN transmissions. The Physical Downlink Control Channel (PDCCH) is used for downlink control information, primarily the reception of the PDSCH and the scheduling decisions required to schedule grants to allow transmission on the PUSCH.
[0118] The Enhanced Physical Downlink Control Channel (EPDCCH) was introduced in Release 11. It is basically used for the same purpose as the PDCCH, but allows control information to be transmitted in a more flexible manner. The Relay Physical Downlink Control Channel (R-PDCCH) was introduced in Release 10 and is used to carry L1 / L2 control signaling on the donor-eNodeB to relay link. The Physical Hybrid ARQ Indicator Channel (PHICH) carries hybrid ARQ acknowledgments to indicate to the terminal whether a transport block should be retransmitted. The Physical Control Format Indicator Channel (PCFICH) is a channel used to provide the terminal with the information required to decode the PDCCH set. There is one PCFICH for each component carrier. In the DL L1 / L2 control signaling, the PCFICH, PHICH, and PDCCH are located in the control region at the beginning of the subframe, while the EPDCCH and R-PDCCH are located in the data region of the subframe. In addition, various reference signals such as C-RS, CSI-RS, and DMRS are multiplexed to the PRB to achieve channel estimation and channel quality estimation. Different channels may be multiplexed into the frames of LTE DL.PHICH may signal a Hybrid ARQ acknowledgment in response to an uplink UL-SCH transmission.
[0119] In LTE, PHICH is a downlink control channel that carries hybrid ARQ acknowledgments of the receipt of uplink transmissions from a terminal. For each UL transport block, one PHICH is transmitted in each TTI. Thus, for UL spatial multiplexing, two PHICHs are required to acknowledge an uplink transmission.
[0120] Like PCFICH, PHICH is usually transmitted in the first OFDM symbol of each subframe. In some cases such as narrow bandwidth, PHICH can be configured with an extended duration of up to 3 symbols. Multiple PHICHs can be mapped to the same set of resource element groups (REGs), each resource element group consisting of 4 REs. These PHICHs transmitted on the same set of REGs are called PHICH groups, and the PHICH group carries up to 8 and 4 PHICHs for normal and extended cyclic prefixes, respectively. These multiple PHICHs in the same group are multiplexed by different orthogonal sequences. The PHICH group is mapped to three REGs, which are evenly distributed within the system bandwidth after being allocated to PCFICH, such as Figure 6 shown.
[0121] The PHICH configuration is part of the Master Information Block (MIB) of the information elements phich-Duration and phich-Resource as shown in the computer code of Example 1 transmitted on the PBCH. The phich-Duration contains one bit indicating whether the normal duration or the extended duration applies, and the phich-Resource contains two bits indicating the amount of resources in the control region reserved for the PHICH, which is expressed as a portion of the downlink cell bandwidth in terms of resource blocks.
[0122] Example 1
[0123] PHICH configuration in the Master Information Block (MIB)
[0124]
[0125] In FDD, the number of PHICH groups is constant in all subframes and is given by
[0126] Equation 1
[0127]
[0128] The MIB provides phich-ResourceN g ∈{1 / 6,1 / 2,1,2} and the DL bandwidth in the number of RBs
[0129] In TDD, the number of PHICH groups can vary between subframes and is determined by Given, where is given by the above expression and m i It is given in Table 3 with the uplink-downlink configuration provided by the higher layer parameter subframeAssignment.
[0130] Table 3
[0131] Factor m of TDD frame structure i
[0132]
[0133] For a PUSCH transmission scheduled in subframe n, the corresponding PHICH resource is in subframe n+k. PHICH In which, for FDD, k PHICH Always 4, and for TDD can be 4, 6 or 7, depending on the configuration.
[0134] The PHICH resource of the terminal is determined by two parameters: PHICH group number and the orthogonal sequence index within the group These two parameters are obtained by the terminal from the lowest PRB index in the first slot of the corresponding PUSCH transmission and the DMRS cyclic shift in the uplink grant. For spatial multiplexing, the resources of the second PHICH are not obtained from the first lowest PRB index of the corresponding PUSCH transmission but from the second lowest PRB index.
[0135] First, a one-bit hybrid ARQ acknowledgment is repeated three times and thereafter modulated in BPSK. Each modulation symbol is multiplied by an orthogonal sequence of length four in a symbol-by-symbol manner, and cell-specific scrambling is applied to the final symbol. Finally, the sequence of 12 scrambled modulation symbols is mapped to three REGs corresponding to its PHICH group number. The entire PHICH processing is as follows: Figure 7 shown.
[0136] For normal duration, all 12 modulation symbols are transmitted in the first OFDM symbol, and the mapping of the PHICH group number to the resource element is defined according to the physical layer cell identity and the number of available REGs not allocated to the PCFICH in the first OFDM symbol. For extended duration, 4 symbols are transmitted in each of the first three OFDM symbols, and the mapping of the PHICH group number to the resource element is defined according to the physical layer cell identity and the number of available REGs not allocated to the PCFICH in each of the three OFDM symbols.
[0137] In order to support carrier aggregation where a terminal receives or transmits on multiple component carriers, the terminal must know which component carrier a certain DCI is associated with. With cross-carrier scheduling, PDSCH and PUSCH transmissions are performed on component carriers other than the carrier on which the PDCCH is transmitted, so that the carrier indicator in the PDCCH is required to provide which component carrier is used for PDSCH and PUSCH. Without cross-carrier scheduling, each uplink component carrier is scheduled on its corresponding downlink component carrier.
[0138] The PHICH is transmitted on the same component carrier used to send the uplink grant. In the absence of cross-carrier scheduling, each uplink component carrier has its associated downlink component carrier for PHICH, such as Figure 8 As shown. In case of cross-carrier scheduling, PHICH for uplink transmission on multiple component carriers must be sent on a single downlink component carrier. To avoid PHICH collision, the scheduler must assign different DMRS cyclic shifts or different lowest PRB indices to different uplink component carriers.
[0139] When a NACK is received, the UL HARQ process configures an UL retransmission of the packet. There are 8 parallel HARQ processes in LTE. The retransmission occurs in subframe n+8 for FDD and in subframe n+k for TDD, where k depends on the subframe configuration.
[0140] UL HARQ is synchronous. This means that the time of retransmission is implicitly known at the DL and no additional control signaling is required to indicate the process number.
[0141] UL HARQ can also be adaptive or non-adaptive. In adaptive HARQ operation, transmission properties such as modulation order, code rate, and resource allocation amount can be changed during retransmission. By applying these properties that are adaptive to different channel conditions, scheduling can be more flexible. Therefore, scheduling gain is easily obtained in adaptive HARQ mode. However, adaptive HARQ operation requires more control signaling overhead than non-adaptive HARQ operation because the receiver should be informed of the transmission properties at each retransmission.
[0142] In case of non-adaptive HARQ, the packet format for retransmission does not change or is known to the UE and eNodeB. Hence, no further control signaling is required, however scheduling gains may be difficult to obtain due to the fixed nature in the packet format.
[0143] Fig. 9is an exemplary time sequence of eight parallel synchronous hybrid automatic repeat request (HARQ) processes. The UE sends data to the eNodeB in the form of a transport block. If the transport block is received correctly, the eNodeB sends an ACK. Otherwise, the eNodeB sends a NACK. The PHICH physical channel is used to carry HARQ in the downlink direction of the received uplink data. Retransmissions are thereafter scheduled at fixed time intervals and the retransmissions use a specific process in a specific subframe. Every 8 subframes, the UE repeats the process ID. As a result, the eNodeB knows exactly when each HARQ process arrives. UL HARQ process ID = (SFN × 10 + subframe) modulo 8. Even if no resources are allocated during a specific subframe, the HARQ process can occur cyclically. As a result, the first process will be repeated every 8 milliseconds. Because the UE must use a specific HARQ process ID at a specific subframe, the receiving eNodeB knows exactly when which HARQ process arrives. In addition, the eNodeB can also know the redundancy version (RV) because the UL grant (DCI 0) from the eNodeB can use the MCS field to specify the RV. As mentioned above, the above HARQ is synchronous in UL. Whenever a retransmission occurs in UL, it can be adaptive or non-adaptive.
[0144] LTE can use semi-persistent scheduling (SPS) without increasing the size of the PDCCH to support more applications. With SPS, the UE is pre-configured by the eNodeB with an SPS-RNTI allocation ID and periodicity. Once pre-configured, if the UE will use the SPS-RNTI (e.g., instead of the typical C-RNTI) to receive allocations (DL / UL), the allocation will be repeated according to the pre-configured period. During SPS, certain things such as RB allocations, modulation, and coding schemes remain fixed for each allocation. Therefore, if the radio link conditions change, a new allocation (PDCCH) must be sent. In addition, any incremental redundancy such as subsequent HARQ transmissions will be scheduled separately using dynamic scheduling over the PDCCH instead of the PHICH.
[0145] There is great interest in reducing latency in future versions of LTE beyond what is currently achievable. Use cases include latency-sensitive M2M applications such as Voice over LTE (VoLTE), gaming, and conferencing, critical low-latency applications, and more robust real-time applications.
[0146] As part of Rel.14, the 3GPP working group recently approved work items related to latency reduction techniques in LTE (see 3GPP36.881 "Study on Latency reduction techniques for LTE", V13.0.0). In the corresponding study project, the group studied the proposal and implementation of various latency reduction schemes described below, which are backward compatible with LTE up to Release 13. One of the proposals considered to be critical is the introduction of short TTI (sTTI) much less than 1mS in duration to provide reduced user plane latency. The study project considers different TTI parameter sets, i.e. various sTTI lengths from 1 symbol duration to 1 slot duration. sTTI can reduce user plane latency because the signaling duration is reduced, and accordingly, the processing time at the receiver, the A / N response time, and the HARQ retransmission delay are also reduced.
[0147] Table 4 shows an example configuration of sTTI based on the proposal in 3GPP 36.881. Because backward compatibility is a requirement for these designs, all configurations assume 15kHz carrier spacing. As the sTTI duration is scaled, the one-way delay of signaling between UL and DL is scaled almost linearly.
[0148] Table 4
[0149] 3GPP 36.881 sTTI configuration to reduce user plane latency
[0150]
[0151] It is expected that ultra-reliable, low-latency applications (such as drone control and remote surgery) as well as some mMTC applications (such as robotic control and industrial automation) will greatly benefit from the reduction of control and user plane latency. Therefore, there is considerable interest in 5G UL and DL parameter sets to accommodate such use cases without backward compatibility with LTE.
[0152] 3GPP TR 38.913 "Study on Scenarios and Requirements for Next Generation Access Technologies" version 14 V0.2.0 defines the scenarios and requirements for next generation access technologies. The following is an excerpt from the key performance indicator (KPI) section of 3GPP TR 38.913 related to low latency design.
[0153] "7.5 User Plane Latency. For URLLC, the target for user plane latency should be 0.5 ms for UL and 0.5 ms for DL. In addition, if possible, the latency should also be low enough to support the use of next generation access technology as a radio transmission technology that can be used within the next generation access architecture." Id.
[0154] “Note 1: The reliability KPI also provides latency values with associated reliability requirements. The above values should be considered as averages and do not have associated high reliability requirements.” Id. “For eMBB, the target for user plane latency should be 4ms for UL and 4ms for DL” Id.
[0155] “Note 2: For the eMBB value, the evaluation needs to take into account in a valid way all typical delays associated with the transmission of data packets (e.g. applicable process delays when resources are not pre-allocated, average HARQ retransmission delay, impact of network architecture).” Id.
[0156] Fig.10 This is a high-level illustration of the concept of network slicing. A network slice consists of a collection of logical network functions that support the communication service requirements of a specific use case. It should be possible to direct the UE to the selected slice, for example based on subscription or UE type, in a way that meets operator or user needs. Network slicing is mainly aimed at partitioning of the core network, but it does not exclude that the radio access network (RAN) may require specific functions to support multiple slices or even divide resources for different network slices. See 3GPPTR 22.891 "Feasibility Study on New Services and Markets Technology Enablers (SMARTER)", Phase 1, Release 14, V-1.1.0.
[0157] Potential network slicing service requirements are defined in 3GPP TR 22.891. The 3GPP system should allow operators to compose network slices, i.e., independent sets of network functions that may come from different vendors, and parameter configurations such as for hosting multiple enterprises or mobile virtual network operators (MVNOs). Operators should be able to dynamically create network slices to form complete, autonomous, and fully operational networks that are customized to support different market scenarios. The 3GPP system should be able to identify certain UEs and subscribers associated with a specific network slice. The 3GPP system should be able to enable UEs to obtain services from a specific network slice, for example based on subscription or UE type.
[0158] Fig.11The predicted applications that require low latency in both UL and DL in 5G networks are described. It is predicted that 5G will support URLLC applications such as smart vehicle control, drone control, robotic surgery, and MTC applications like industrial automation, which require new solutions to address the need for lower latency.
[0159] Fig.12 and 13 The forecasts for various applications with different deployment densities and latency requirements in 5G are shown.
[0160] Solutions in LTE are currently insufficient to address the low latency requirements that 5G seeks to address. There is also a lack of solutions for seamless multiplexing of applications with different parameter sets at the same time. Because PHICH is only transmitted for a fixed duration after the UL transmission (e.g. 4mS in FDD in LTE), the latency of the UL HARQ process is fixed and cannot be further reduced in the current version of LTE.
[0161] As proposed in 3GPP 36.881, shorter duration sTTI may be considered for latency reduction. For example, a sTTI of 0.25 mS in UL may be accompanied by an A / N response time of 1 mS in DL that is linearly scaled from legacy LTE. This means that PHICH must be signaled every 0.25 mS. Fig.14 The expected timeline of PHICH response for UL transmissions with sTTI durations of 1mS and 0.25mS according to 3GPP 36.881 is shown.
[0162] However, currently in LTE, PHICH is signaled only at the beginning of a 1ms TTI. This does not address the goal of achieving low latency in A / N signaling. Obviously to keep A / N response times low, PHICH transmissions must occur more frequently. But this configuration has not yet been defined as part of SI in 3GPP 36.881. There is also no definition of sTTI duration or HARQ A / N timeline for 5G.
[0163] To support sTTI configurations as small as 1 or 2 symbols under current schemes, the number of PHICH resources required would increase by a factor of between 7 and 10. The 5G solution is expected to address this issue by allocating enough resources to support all sTTI parameter sets, preferably with minimal control overhead.
[0164] Another issue is the latency with synchronized UL HARQ processing. When multiple lengths of sTTI are multiplexed together and the UL HARQ processing occurs in a predetermined sequence of 0, 1, 2, ... 7 and then the sequence is repeated, the latency of the sTTI cannot be reduced. Fig.15The high latency of retransmission of 0.5mS sTTI of HARQ process #2 is illustrated when all other processes have the traditional duration of 1mS. It is desirable to have a new solution that allows synchronous operation and avoids excessive control overhead while allowing multiplexed sTTIs of different durations.
[0165] 5G is expected to support multiple parameter sets for TTI (i.e., CP length), subcarrier spacing (or equivalent symbol duration), and the number of symbols in a TTI. Multiple parameter sets can be multiplexed into the same time-frequency resource grid. Fig.16 An exemplary configuration of a 5G transmitter for multiplexing different parameter sets is depicted in FIG. The parameter sets are described in Table 5.
[0166] Table 5
[0167] Example parameter sets supported in 5G
[0168]
[0169] The various embodiments described below improve the reliability of various scenarios in NR. Exemplary scenarios addressed include, but are not limited to: HARQ transmission methods for higher reliability, lower latency, erasure channels, unlicensed channels, unequal error protection; improved reliability of control information such as DL control information and A / N; and resource provisioning for low latency and unlicensed operation.
[0170] In an exemplary embodiment, reliability in low latency situations is improved by multiple HARQ retransmissions that may occur before receiving an ACK and that always occur before receiving an ACK. A solution is also provided here for the eMBB situation where DL transmissions can be punctured by URLL transmissions. Here, erased portions of a transport block can be retransmitted, thereby saving resources. In another exemplary embodiment, reliability is provided for UL transmissions by transmitting only portions of a transport block that are erroneous due to UL interference. A / N is defined here for UL unauthorized transmissions by using a new unauthorized access response for acknowledgment messaging. According to another exemplary embodiment, code block grouping is introduced and A / N resources are provided for each group to allow a selective HARQ retransmission strategy.
[0171] Turning now to the enhanced HARQ strategy for NR, in one example, retransmissions occur until a low-latency ACK is received. It is recognized here that in some cases NR should support retransmissions for HARQ processing in a mode that can be predefined in the standard or configured through RRC / MAC CE. For example, HARQ retransmissions can occur with a periodicity P, where P is predefined in the specification or configured through RRC / MAC CE. Retransmissions can be any redundancy version predefined or configured.
[0172] In some cases, a predefined pattern enables NR downlink control information (NR-DCI) that provides a grant for the first (UL / DL) transmission to configure the resources and redundancy version for the retransmission so that subsequent retransmissions do not require explicit NR-DCI resources. For example, Fig.17 It shows the case where the transmission of HARQ process #0 occurs with a period of 1 (ie, every transmission time interval) up to a maximum of 4 times. According to this example, the NR-DCI in the first transmission configures the resources for the remaining 3 retransmissions.
[0173] In another example, reference Fig.18 , A / N resources are allocated to each HARQ transmission. Fig.18 An example of allocating A / N resources for each transmission and retransmission in a self-contained subframe is shown.
[0174] refer to Fig.19 , HARQ retransmissions can occur before the first A / N response to the TB is expected to be received. This reduces latency at the expense of increased redundancy. Fig.19 As shown, the first retransmission of HARQ process #0 occurs before the A / N of the first transmission is received.
[0175] In the example, HARQ retransmissions occur until an ACK is received or until a maximum limit L on the number of retransmissions is reached. Upon receiving an ACK, the additional pre-scheduled HARQ retransmissions for the TB may be interrupted. Fig. 20 An example is shown where HARQ process #0 is transmitted 4 times. This includes the initial transmission and three retransmissions. When the ACK corresponding to the first retransmission arrives, the NR node stops the retransmission HARQ and switches to a new transmission, although configured as L=4. Fig.21 An example is shown where L=4 and HARQ process #0 is transmitted 5 times. No ACK is received for the duration of those HARQ retransmissions. It should be noted that an A / N may be received after the last HARQ transmission. Fig. 22 An exemplary retransmission with a period equal to 2 is shown.
[0176] refer to Fig.23 , shows an exemplary UE process in the UL. As shown, the UE transmits up to L retransmissions for HARQ process #h. Upon receiving an ACK, it terminates the retransmissions. If it receives a NACK, it continues to retransmit until it exceeds its maximum retransmission limit L.
[0177] In some cases, the redundancy version (RV) in the retransmission may be the same or different from the first transmission. Therefore, the receiver may combine the retransmissions using chase combining or incremental redundancy. The RV of a transmission and / or subsequent retransmissions may be indicated by a single or multiple NR-DCIs. For example, the NR-DCI that grants the first transmission may also indicate the RV of the retransmission. Alternatively, a separate NR-DCI occurring in the same or different subframes may indicate a retransmission.
[0178] RV can be predefined for retransmission to reduce control signaling overhead. For example, the same RV can be used for each transmission and retransmission. Alternatively, the RV time sequence (i.e., RV0, RV1, ... RVN) can be predefined. In addition, for UL, in the example, an operation mode is proposed in which the UE can send an RV signal for transmission or retransmission through a control channel.
[0179] In an example, a retransmission may occur with a different set of parameters than the first transmission or other retransmissions. The parameter set may be indicated by an appropriate DL control signal.
[0180] refer to Fig.24 According to the example shown, a single subframe in NR can be configured to carry multiple redundant versions of the same HARQ process. This solution may be particularly suitable for scenarios where multiple use cases such as URLLC and eMBB are multiplexed. NR-DCI can signal the configuration to the UE. It can do so by indicating the symbol or PRB and RV for each HARQ retransmission. Alternatively, for example, in order to save control signaling overhead, the resources for retransmission of URLLC UEs can be determined according to predefined rules (for example, resources for L retransmissions after new data transmission can be specified in the specification).
[0181] In the frequency domain resources, the position may vary between symbols (used for each retransmission) to obtain more frequency diversity. In another example, one or more possible / allowed configurations of URLLC retransmissions may be predefined in the standard or configured by higher layer signaling (such as RRC signaling). For each new data transmission, NR-DCI may signal the index of the configuration of URLLC retransmission to be used for the URLLC UE.
[0182] Turning now to transmissions in the erasure channel in the DL, the URLLC grant may require puncturing of ongoing transmissions in the DL. For example, Fig.25 An exemplary case is shown where an eMBB transmission is already scheduled and ongoing when the NR node receives a request to transmit a URLLC payload. It therefore truncates the eMBB transmission and transmits the URLL payload.
[0183] For URLLC transmissions to be scheduled in this way on the DL, the NR-PDCCH must be defined so that the URLLC UE can monitor its grant. In an exemplary embodiment, user-specific DL control signaling on the uNR-PDCCH may be provided in resources predefined by the standard and configured by RRC. It should be noted that the uNR-PDCCH resources may be shared between multiple UEs - so the UE may decode its uNR-PDCCH resources and look for its CRC to pass through to obtain its NR-DCI.
[0184] The URLL UE monitors its uNR-PDCCH resources and once its NR-PDCCH is successfully detected, it processes its grant. If no NR-PDCCH is scheduled in these locations, the resources are used to carry data for other UEs, otherwise the uNR-PDCCH truncates the eMBB transmission (which may be noticeable to the eMBB user losing some bits from the truncation). This is similar to the ePDCCH in LTE, but the number of symbols allocated for the NR-PDCCH should be limited to as few symbols as possible to reduce latency. Fig.26 An example of NR-DCI for such a URLL NR-PDCCH transmission is shown. To minimize latency, the entire URLL transmission is sent in a single symbol as an example - this includes the uNR-PDCCH for the URLL UE.
[0185] In the example presented herein, the uNR-PDCCH may allocate multiple URLL transmissions in the same or subsequent symbols of the uNR-PDCCH resource. Fig.26 As shown, the uNR-PDCCH may allocate RV0 to a symbol for transmission and RV1 to a subsequent symbol for retransmission. Alternatively, the uNR-PDCH may provide a Fig. 27 The resources of HARQ process #h and process #(h+1) are shown. The corresponding URLL UE processes as in Fig.28 As shown in . A URLL UE is configured to receive its DL grant in its uNR-PDCCH resources. If it finds a valid NR-DCI grant, it acts on the grant. Otherwise, it continues to monitor the next set of user-specific NR-PDCCH resources.
[0186] In some cases, eMBB transmission may be affected due to puncturing. To address this issue, for example, the NR node may use any of a variety of retransmission strategies. For example, the NR node may retransmit the entire TB or a portion of the TB containing the punctured portion (such as the punctured RB or CB). The NR node may retransmit before receiving the A / N response.
[0187] Similarly, the NR node may indicate information related to the retransmission as part of the HARQ information. Some of the signaled NR-DCI information may include, for example, information about which part of a TB the retransmission corresponds to. This may be a parameter such as a CB or PRB or symbol.
[0188] Additionally or alternatively, the information related to the retransmission may relate to which part of the retransmission is subject to erasure. This is important because the UE can know whether it should discard the truncated part or perform catch-up combination with the corresponding part of the retransmission. The information can be indicated as a truncation pattern from a predefined pattern set.
[0189] In another example, the NR node may allocate DL URLL grants only on resources where the MAC CE for carrying eMBB transmissions is not punctured. This is possible in scenarios where, for example, a TB is decomposed into multiple CBs for large payloads, and puncturing may be optional to avoid eMBB CBs containing MAC CEs. Fig.29 An example is shown where the NR-node does not puncture the first available data symbol in a subframe as it contains a MAC CE for an eMBB user.
[0190] In yet another example, the NR node may allocate DL URLL grants only on resources that do not puncture NR-DCI and reference signals for other use cases. This may be important because NR is designed to have flexible configuration of control signaling and RS. The NR node may indicate the resources where control signals and RS are present. Alternatively, control signals and RS may puncture URLL transmissions, and the URLL UE may not be aware of the presence of control and RS signals. Fig.30 An exemplary scenario is shown where the resources of the URLL transmission do not affect the control and RS signals of the eMBB transmission. In the example, one URLL transmission is not punctured by another URLL transmission.
[0191] Currently in LTE when a DL transmission has to be scheduled, the UE is paged with the P-RNTI. Thereafter, the UE monitors the DCI for grants. Idle UEs have to establish RRC to start receiving DL grants, as they have to be able to send A / N on the UL. For URLL UEs, this process is slow, as the latency between paging and receiving the DL grant can be up to tens of milliseconds. In order to address this latency issue in NR, according to an exemplary embodiment, it is proposed here that the subframe carrying the P-RNTI also provides the UE with a DL grant. It should be noted that the DCI for the P-RNTI and the DL grant can be different.
[0192] The UE may respond in a number of ways. For example, if an RRC connection is not established, the UE may send an A / N in an unlicensed UL transmission, whereby the UE establishes RRC and thereafter sends an A / N. The NR node may provide A / N resources after sufficient time to enable an RRC connection. It should be appreciated that this solution is also applicable to mMTC UEs, as it minimizes the on-time by providing grants as well as paging.
[0193] Turning now to the enhanced HARQ process for UL unlicensed transmissions, NR will support asynchronous unlicensed UL transmissions. It is recognized here that the resources used for unlicensed transmissions may conflict with scheduled UL transmissions. Therefore, the scheduled transmissions may be interfered by the unlicensed transmissions. The NR node can detect the conflict. Fig.31 An example of how interference affects scheduled transmissions is shown. In such a scenario, various embodiments described below can improve HARQ and A / N performance in such a scenario.
[0194] In one example, if the NR node detects a failure on a scheduled transmission due to interference from an unlicensed transmission (e.g., from a URLL device), the NR node asynchronously schedules HARQ retransmissions (e.g., for eMBB devices). In some cases, the NR node transmits only the portion of the TB affected by the interference. The NR node can achieve this by transmitting all or part of the affected symbols or CBs or PRBs.
[0195] In some cases, if the NR node correctly receives an unlicensed transmission, it may need a mechanism to send an acknowledgment. In one example, the NR node responds with certain types of NR-DCI as an implicit acknowledgment of the unlicensed transmission. For example, certain types of UE-specific NR-DCI may be provided. For example, a new DCI called ACK-DCI may be defined as a user-specific DCI for indicating an ACK. Other existing DCI formats such as those used for DL or UL authorizations may be used to implicitly confirm unlicensed transmissions. Alternatively, a new DCI format using an authorization with an ACK may be used to explicitly indicate an ACK.
[0196] In yet another example, the UE may select its signature from a pool of available resources (e.g., codes or preambles) since an RRC connection may not be established and a C-RNTI may not be available to the UE. In some cases, if the resource pool is limited, there may be contention and the NR node must provide contention resolution.
[0197] In the example, the NR node defines a GL-RNTI (non-licensed RNTI) similar to the RA-RNTI to provide a response to the unlicensed UE. Through the GL-RNTI, the NR node indicates the PDU used to carry the identity or signature of the UE whose unlicensed transmission is received. Fig.32 An example of a MAC PDU indicated by the GL-RNTI is shown. It consists of several MAC GLARs (Non-licensed Access Responses) preceded by a header. Each GLAR may provide one or more of the following information presented as examples and not limitations: a signature of the non-licensed UE; and a time advance command so that the UE can synchronize in the UL for further transmissions.
[0198] In an exemplary contention-free system, user signatures are unique and the UE can be unambiguously determined from its signature. Here, if a UE receives a GLAR containing its signature, it can assume that the transmission is confirmed. Fig.33 This two step process is shown where the UE makes an ungranted transmission in step 1 and acknowledges with GLAR in step 2. However, if contention occurs in the system, e.g. due to limited resources, another step may be needed to resolve the contention after which the UE may assume acknowledgement. Fig.34 This exemplary process (similar to the random access procedure in LTE) is shown. The UE makes an unlicensed transmission in step 1. It receives a GLAR with its signature indicating that the NR node received the transmission in step 2. But other UEs with the same signature may also attempt to make unlicensed transmissions at the same time as the UE of interest. To resolve the contention, the UE can send its identity in a scheduled UL transmission in step 3. In step 4, the NR node transmits the following contention resolution message, which is used to indicate which UE is served during the UL unlicensed transmission. This provides an implicit confirmation to the UE.
[0199] In an example, this implicit acknowledgement via NR-DCI occurs within some maximum time frame to meet the latency requirements of the UE. The acknowledgement may be scheduled to be transmitted at a fixed time after the transmission is received, such as 'Tμsec / msec' after reception. Alternatively, the 'S' subframe may be sent after the UL transmission is received. In some cases, as the latency and radio on time of the UE decrease, it may be advantageous to schedule this NR-DCI with minimal latency (e.g., as early as possible) for both URLL and mMTC.
[0200] In another example, if an RRC connection has been established before the unlicensed transmission, the NR node can confirm the grant through NR-DCI that can perform grant or power control. If the unlicensed UL transmission is decoded correctly, the NR node can indicate ACK in a new NR-DCI format. The NR-DCI format can provide 1 or more bits for the A / N of the unlicensed TB. If the control information from the unlicensed transmission is decoded correctly, but the data is decoded incorrectly due to a CRC check failure, the NR node can detect the UE and NACK the transmission.
[0201] Alternatively, explicit A / N signaling may be supported for UL ungranted transmissions. Here, A / N resources may be allocated in the form of NR-PHICH (New Radio—Physical HARQ Indicator Channel) in a manner similar to PHICH in LTE. A / N may be signaled on the Nth (where N is predefined by the specification or configured by system information) DL subframe from the transmission time in the following manner.
[0202] This can be accomplished in a number of ways. For example, if RRC is not established, then RRC can be signaled on resources that correspond to the user signature and are predefined in the specification. If RRC is established, then it can be signaled on resources preconfigured by RRC or can be signaled on resources implicitly associated with UL unlicensed transmission resources. In some cases, these NR-PHICHs puncture data for other use cases so that these resources are not reserved specifically and are unused in the absence of unlicensed transmissions - unlike LTE where PHICH resources are reserved specifically for PHICH transmissions.
[0203] In another example, UL unlicensed transmissions use a single HARQ process, especially when operating in RRC connectionless mode. In some cases, the NR node may not be able to decode the unlicensed transmission. In this case, the NR node may not be aware that such a transmission has occurred and cannot NACK it. To improve reliability, for example, we propose that in some cases the UE retransmits its unlicensed transmission multiple times until an acknowledgment is received from the NR node or the transmission timer expires (or the maximum number of retransmissions allowed is reached). Resources for transmission and retransmission can be extracted from a predefined resource configuration set. Retransmissions can occur on a specific beam or on multiple beams. Fig.35 An example of such a retransmission that may occur before the A / N is received is shown.
[0204] In LTE, for turbo codes, RV0 has the highest reliability. Other RVs provide incremental redundancy and cannot be independently decoded with the same reliability as RV0. However, if NR uses a similar design for UL unlicensed transmissions, the incremental redundancy from subsequent retransmissions may not help if the NR node does not receive the first UL unlicensed transmission. Therefore, in an exemplary embodiment, the codes used for unlicensed transmissions have redundant versions that can be equally decoded with similar reliability. An example of such a configuration is to use a single redundant version for all retransmissions (e.g., the retransmission is the same as the original transmission).
[0205] Turning now to enhanced A / N signaling and partial retransmission of transport blocks, in LTE, a TB has a 24-bit CRC. If a TB is larger than 6144 bits, it is segmented into CBs. In response to the entire TB, the receiver transmits one A / N, regardless of the number of CBs in it. For large payload applications such as eMBB in NR, in some cases, it is proposed here to use a finer-grained A / N response, where K bits are provided for the A / N response to a TB. The K bits correspond to the KA / N bits from the K groups of CBs. The CBs in a TB can be grouped into K groups, such as Fig.36 As shown. Each group sends an ACK bit if all CBs in the group are successfully decoded, and sends a NACK bit if any CB in the group is incorrectly decoded. It should be noted that when K=1, the solution will revert to the solution in LTE. In the extreme case where K is equal to the number of CBs, there is one A / N bit for each CB. For this case, it may not be possible to encode the TB using the outer CRC.
[0206] In an exemplary embodiment, a group may contain different numbers of CBs and different numbers of coded bits. Before coding, the CBs themselves may contain different numbers of bits. For example, Fig.37 As shown, one group can consist of a CB containing only a MAC header and a MAC CE. Another group can contain a MAC SDU. This configuration requires K = 2, which provides a better ability to control the reliability of the MAC CE, but the additional overhead is small. In the example, K can be configured according to the payload, and the NR node configures the UE for K through RRC and MAC CE and / or NR-DCI.
[0207] In the example, the NR node responds to the A / N with a retransmission of only the portion / portions responded with a NACK (without transmitting the entire TB), thereby utilizing resources more efficiently. Fig.38 As shown in the example in , the retransmission can carry information about the part of the TB being retransmitted and the corresponding redundancy version in the NR-DCI.
[0208] Turning now to improving A / N performance in the UL, in an example, the amount of A / N resources allocated to a UE is based on the use case. For example, the resources allocated for URLL A / N may be double or quadruple compared to the resources used for eMBB. In another example, it is proposed that NR supports variable A / N resource allocation even within specific use cases. For example, the amount of resources may depend on UE power, channel conditions, etc. Fig.39 An example of providing different amounts of A / N resources to two users using CDM multiplexing is shown. These solutions use resources efficiently to prevent excessive overhead signaling.
[0209] Fig.40 An exemplary configuration of a multiplexing parameter set for 5G belonging to case-1, case-2, and case-3 parameter sets is shown. The parameter set of PHICH must be known at the terminal in order to successfully decode A / N. Although the PHICH parameter set can be configured to change dynamically, doing so will increase the control signaling overhead. The problems of latency and resource sufficiency can be solved by a solution for providing additional PHICH resources to support a large number of UL sTTIs and to support more frequent PHICH transmissions. For example, UL transmission can support flexible A / N timelines to minimize the frequency of PHICH signaling and adapt to scenarios where UE processing time may not scale linearly, especially when the sTTI duration is reduced to a very short length. In such a solution, each sTTI duration is associated with a minimum and maximum A / N latency tolerance (e.g., "min_response" and "max_response"), respectively, according to a predefined mapping. The eNode B transmits a PHICH response to the UL transmission in the kth signaling time interval within a time window (referred to here as a "tolerance window" and defined by the duration between k+minResponse and k+maxResponse). It should be noted that in LTE up to LTE Release 13, for FDD, minResponse = 4 ms and maxResponse = 4 ms.
[0210] Table 6 shows an exemplary configuration of minResponse and maxResponse for different slices of 5G. Here the minResponse and maxResponse times scale linearly with the sTTI duration and can be expressed as shown in equations 2 and 3 below.
[0211] Equation 2
[0212] maxResponse=k*sTTI
[0213] Equation 3
[0214] minResponse=(k-Δ)*sTTI
[0215] Therefore, the tolerance window is equal to Δ*sTTI.
[0216] Table 6
[0217] Example configuration of minResponse and maxResponse for k=4, Δ=1
[0218] Example sTTI Configuration sTTI duration minResponse maxResponse Tolerance Window 1LTE Symbol 0.0714mS 0.21mS 0.3mS 0.9mS 2LTE Symbols 0.1428mS 0.42mS 0.6mS 0.18mS LTE slot duration 0.5mS 1.5mS 2mS 0.5mS LTE TTI 1mS 3mS 4mS 1mS
[0219] Additional PHICH resources with appropriate delays may be provided through "PHICH opportunities", such as symbol duration when PHICH is signaled in DL, whereby the terminal expects A / N of UL transmissions in the Nth PHICH opportunity within its tolerance window. In other words, each PHICH opportunity corresponds to a reserved PHICH resource pool in one or more symbols. Fig.41 shows an exemplary configuration of PHICH opportunities in a DL signaling interval, and Fig.42 Example configurations of A / N signaling using N=1 and sTTIs of different durations and therefore different tolerance windows are shown.
[0220] In case the UE has knowledge of the parameters N, maxResponse and minResponse, and the PHICH opportunity configuration, the UE may set its timer to position its PHICH opportunity for an UL transmission of a sTTI of duration S to the symbol occurring at time p*S+m from its own transmission time, where p represents an integer and m represents the number of symbols between the UL transmission time and the PHICH opportunity sTTI or equivalently represents a fraction of a sTTI.
[0221] Multiple UEs can multiplex their A / Ns into the same PHICH opportunity regardless of Fig.43 Their sTTI durations are shown.
[0222] The PHICH opportunities may be semi-statically configured through system information such as the MIB or equivalent of SIB in LTE and subsequently updated through CE of MAC. The configuration defines the symbols in which the PHICH will be signaled within the TTI and the PHICH resources within the symbol.
[0223] In computer code example 2, PHICH-Symbols lists the symbols in the transmission duration that carry the PHICH. PHICH-Resources indicates the resource allocation for each symbol in the PHICH-Symbols list.
[0224] Example 2
[0225] Example fields for PHICH opportunity indication of CE via MIB or SIB or MAC
[0226]
[0227] Table 7 shows an example configuration of phich-Symbols and phich-Resource for the proposed solution. For each phich-Symbol carrying a PHICH opportunity, the phich-Resource can be selected from a number such as N g ∈{1 / 6,1 / 2,1,2} is drawn from a set of predefined values.
[0228] Table 7
[0229] Example configuration of phich-Symbols and phich-Resource assuming TTI length is 1ms and 14 symbols in TTI
[0230]
[0231] The sTTI parameters N, min_response, and max_response may be predefined in the 5G specification for each sTTI, or may be optionally allocated to the terminal via system information such as SIB in LTE. Computer code example 3 shows an exemplary configuration of the parameters min_response_k and max_response in_k for the kth TTI length in the SIB. The CE of the MAC may then reconfigure the values.
[0232] Example 3
[0233] Exemplary allocation of min_response and max_response via SIB
[0234]
[0235] The location of the PHICH can be implicitly derived from the sTTI length, RB position, and DMRS cyclic shift of the UL transmission. However, PHICH conflicts may occur when sTTIs of different durations are multiplexed. Fig.44 An exemplary transmission scenario is shown in which A / N responses for two different sTTIs occur simultaneously, resulting in a PHICH conflict.
[0236] Using flexible scheduling can reduce conflicts. As shown in Equation 4, the PHICH resource location is expressed as I PRB The UL PRB position, which is denoted as I DMRS The UL DMRS cyclic shift of sTTI Therefore, we can express the PHICH resource as the following relationship:
[0237] Formula 4
[0238]
[0239] The location of each PHICH resource and and They respectively represent the maximum number of PHICH groups and the DMRS cyclic shift of each PHICH group.
[0240] Not all conflicts are avoided in this way. The scheduler must ensure that resources are scheduled in such a way that no PHICH resource conflicts occur.
[0241] The A / N responses of all terminals may be multiplexed together in commonly configured PHICH resources (referred to herein as "common-PHICH" resources). Depending on the UL traffic and thus the A / N traffic in the DL, not all common PHICH resources may be used all the time.
[0242] Alternatively, the PHICH may be piggybacked on the PDSCH. For example, when a DL transmission to a terminal is ongoing, the terminal's A / N may be piggybacked on its DL PDSCH allocation to create a "piggybacked PHICH". If the first symbol of a terminal's DL grant is within the tolerance window of its previous UL transmission, the PHICH corresponding to the UL transmission may be piggybacked on the DL allocation without allocating PHICH resources from the common PHICH pool to the terminal.
[0243] There is no ambiguity as to whether the A / N for a particular grant occurs in the common-PHICH or the piggybacked-PHICH. This reduces the need to configure a large number of common PHICH resources that are reserved when there is not enough A / N traffic to fully utilize them. This provides dynamic management of resources used to deliver A / N traffic to the terminal. This can alleviate some PHICH resource conflicts because some PHICH resources that might otherwise conflict in the common PHICH are signaled by separate piggybacked resources.
[0244] Fig.45 An exemplary time sequence of DL with piggyback PHICH and common PHICH signaling PHICH using 1 ms TTI is shown. Fig.46 An exemplary time sequence of DL with piggyback PHICH and common PHICH signaling PHICH using 0.5 mS TTI is shown.
[0245] In both figures, the UL is composed of multiplexed sTTIs with different tolerance windows. If the start of the DL sTTI falls within the tolerance window, the A / N response for that UL grant is piggybacked. Otherwise, it is signaled via the common region in the 1st PHICH opportunity within the tolerance window of the UL grant.
[0246] Because a single DL grant can carry multiple A / N responses corresponding to cross-carrier aggregation, multiple spatial layers, and multiple sTTI durations, the A / N can be jointly encoded using error correction codes such as repetition codes, RM codes, or convolutional codes, depending on the number of A / N bits to be sent.
[0247] The modulation and number of resources reserved for piggybacking the PHICH may be based on the MCS of the DL grant, and the coded PHICH may be rate matched to fill the number of reserved resources. The location where the PHICH may be piggybacked on the DL grant may be defined as part of the specification or otherwise provided to the terminal so that the terminal has a priori knowledge of the location of the PHICH opportunities. This ensures that no additional control signaling is required to indicate the location of the PHICH resources.
[0248] Additionally, due to the allocation of the piggybacked PHICH, the PDSCH can be rate matched to accommodate the reduced amount of available resources. Fig.47 An exemplary configuration of a PHICH piggybacked on a DL PDSCH grant is shown.
[0249] Fig.48 An exemplary configuration of a DL transmission chain is shown in which a PHICH is carried on a PDSCH and an OFDM symbol with a CP is generated for transmission.
[0250] For the terminal via RRC signaling, the problem of delayed HARQ retransmissions in the UL can be solved by having the eNodeB configure the maximum number of HARQ processes, e.g. in a parameter called maxHarqProcessUL, and the duration of these HARQ processes, e.g. in a parameter called harqULProcessDuration. Table 8 shows a table with exemplary durations of process indices.
[0251] Table 8
[0252] Example configuration of HarqULProcessDuration
[0253] harqULProcessIndex 0 1 2 3 4 5 6 7 harqULProcessDuration(mS) 0.5 0.5 0.5 0.5 1 1 1 1
[0254] Subsequent reconfiguration may be performed by the CE of the MAC.As shown in computer code example 4, configuration of the UL HARQ may be performed by parameters.
[0255] Example 4
[0256] Example MAC-MainConfig message with parameters for UL HARQ to maintain synchronous operation with multiplexed sTTIs
[0257]
[0258]
[0259]
[0260]
[0261]
[0262]
[0263] Each valid HarqULProcessDuration vector may be mapped to a HARQ process which repeats itself and is a predefined sequence known a priori to the terminal. Computer code example 2 shows the mapping to the transmission order of the HARQ processes.
[0264] Table 9
[0265] Mapping HARQ process numbers and sTTIs to HARQ process transmission order
[0266]
[0267] Once the eNodeB establishes the duration of the HARQ process via RRC, the terminal obtains the sequence of HARQ process transmissions from the predefined mapping. No additional control signaling is required. Synchronous operation can be maintained without additional control overhead while ensuring acceptable latency for retransmissions of all TTI lengths.
[0268] Fig.49 A HARQ process transmission sequence is shown in Computer Code Example 2. TTIs of different durations have the opportunity to be retransmitted with an approximate delay of 8 to 9 times their length.
[0269] Multiple parameter sets with different subcarrier spacing and thus different symbol durations and different CP durations may be multiplexed in UL and DL where PHICH is transmitted on a single "common-PHICH-numerology" parameter set in DL. Fig.50 and Fig.51An exemplary configuration of UL and DL multiplexing various parameter sets is shown. DL carries all PHICHs for UE 1, 2, 3 in a common Common-PHICH-numerology through three configured PHICH opportunities. Here, Common-PHICH-numerology is set to the maximum possible subcarrier spacing and the minimum possible symbol duration. This meets the most stringent sTTI latency requirements. Resources for these PHICH opportunities can be allocated, for example, through MIB or RB and DMRS.
[0270] Common-PHICH-numerology can be delivered to the UE through key system information such as MIB in LTE and can be semi-statically updated or reconfigured through CE of MAC. Such a common parameter set for all PHICHs allows PHICH to be multiplexed in DL without the complexity or additional signaling overhead associated with DL parameter sets, regardless of the parameter set transmitted in UL.
[0271] Computer Code Example 5 shows an example configuration of a MIB with a "common-PHICH-numerology" field added to convey the parameter set of the PHICH. This field may be set to the value "Common-PHICH-numerology" whose example configuration is given in Table 10.
[0272] Example 5
[0273] Common-PHICH-numerology in Master Information Block (MIB) in LTE
[0274]
[0275] Table 10
[0276] Example configuration of Common-PHICH-numerology parameters for CE of system information or MAC
[0277] Common-PHICH-numerology cpConfig-k=1.18(μs) subcarrierSpacing-k=60(kHz)
[0278] Fig.52 An exemplary UE procedure for obtaining a PHICH parameter set is shown. The UE obtains synchronization with the cell by obtaining physical cell identity (PCI) acquisition and frame timing acquisition. Thereafter the UE decodes the PBCH for the following MIB, from which it obtains the Common-PHICH-numerology.
[0279] In some scenarios, it is not desirable to use Common-PHICH-numerology. For example, a narrowband IOT terminal may have a low sampling rate and may be able to operate only with the lowest subcarrier spacing parameter set and may only be able to operate on a small portion of the DL bandwidth of the cell. To support such situations, 5G may support PHICH signaling for different DL parameter sets and / or multiple different network slices and / or different UL parameter sets at different locations in the DL bandwidth. For example, the parameter set PHICH-numerology-k may be configured as shown in Table 11, where K is a plurality of network slices, PHICH-Numerology-k is a parameter set for supporting the kth DL parameter set or network slice, and k=1,2,...K.
[0280] Table 11
[0281] Example configuration of PHICH-numerology-k parameter for CE of system information or MAC
[0282] PHICH-numerology-k cpConfig-k=4.7(μs) subcarrierSpacing-k=15(kHz)
[0283] Fig.53 It is shown that PHICH-numerology-1 and PHICH-numerology-2 are allocated to PHICH in an exemplary configuration where DL supports two parameter sets. A single UE can support UL transmission on multiple parameter sets in 5G, whereby the UE receives its PHICH for different slices on multiple parameter sets.
[0284] PHICH-numerology-k may be delivered to the UE through key system information such as MIB in LTE, and may be semi-statically updated or reconfigured through CE of MAC, such as allocating resources of the PHICH transmitted using PHICH-numerology-k through MIB or RB and DMRS.
[0285] 5G may support a configuration in which the resources of the PHICH on PHICH-numerology-k are limited to some RBs of the DL. Such RBs are referred to herein as "PHICH-RB-numerology-k". The parameters of PHICH-RB-numerology-k may be configured through system information and updated through CE of MAC. For example, PHICH-RB-numerology-k may be defined by the first and last RB numbers of the DL bandwidth portion that supports PHICH resources and uses PHICH-numerology-k.
[0286] Fig.54An exemplary UE procedure for obtaining a PHICH parameter set is shown. Fig.54 In the example of , the UE obtains synchronization with the cell by obtaining the physical cell identity (PCI) acquisition and frame timing acquisition. Thereafter, the UE decodes the PBCH of the MIB from which it obtains the Common-PHICH-numerology.
[0287] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunication network technologies including radio access, core transport networks, and service capabilities - including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), and LTE Advanced standards. 3GPP has begun to work on the standardization of its next-generation cellular technology, known as New Radio (NR) (also known as "5G"). The development of the 3GPP NR standard is expected to include the definition of the next-generation radio access technology (new RAT), which is expected to include providing new flexible radio access below 6GHz and providing new ultra-mobile broadband radio access above 6GHz. Flexible radio access is expected to consist of new non-backward compatible radio access in new spectrum below 6GHz, and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a wide range of 3GPP NR use cases with different needs. It is expected that ultra-mobile broadband will include centimeter wave and millimeter wave spectrums that will provide opportunities for ultra-mobile broadband access such as indoor applications and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with sub-6 GHz flexible radio access with centimeter-wave and millimeter-wave specific design optimizations.
[0288] 3GPP has identified a variety of use cases that NR is expected to support, which results in a wide range of user experience requirements for data rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, ultra-high broadband access indoors, broadband access in crowds, 50+Mbps everywhere, ultra-low-cost broadband access, in-vehicle mobile broadband), critical communications, massive machine-type communications, network operations (e.g., network slicing, routing, migration and intercommunication, energy saving), and enhanced cellular vehicle-to-everything (eV2X) communications. Specific services and applications in these categories include, for example, monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connectivity, car emergency calls, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, perceptual Internet, and virtual reality, among others. All of these use cases and others are considered in this article.
[0289] Fig.55An embodiment of an exemplary communication system 100 is shown in which the methods and apparatus described and claimed herein may be implemented. As shown, the exemplary communication system 100 may include wireless transmit / receive elements (WTRUs) 102a, 102b, 102c, and / or 102d (which may be generally or collectively referred to as WTRUs 102), a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it should be understood that the disclosed embodiments encompass any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e may be any type of device or apparatus configured to operate and / or communicate in a wireless environment. Although in the Figure 55-Figure 59 Each WTRU 102a, 102b, 102c, 102d, 102e is depicted as a handheld wireless communication device, but it should be understood that with the wide variety of use cases expected for 5G wireless communications, each WTRU may include or be specifically implemented as any type of device or equipment configured to transmit and / or receive wireless signals, including, by way of example only, a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a portable computer, a tablet computer, a netbook, a laptop computer, a personal computer, a wireless sensor, a consumer electronics product, a wearable device (such as a smart watch or smart clothing), a medical or e-health device, a robot, an industrial equipment, a drone, a vehicle (such as a car, truck, train, or airplane), etc.
[0290] The communication system 100 may also include a base station 114a and a base station 114b. The base station 114a may be any type of device that is configured to have a wireless 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 other networks 112. The base station 114b may be any type of device that is configured to have a wired and / or wireless 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 other networks 112. The RRHs 118a, 118b may be any type of device that is configured to wirelessly interface with at least one WTRU 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. The TRPs 119a, 119b may be any type of device that is configured to wirelessly interface with at least one WTRU 102d to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be base transceiver stations (BTSs), Node-Bs, eNodeBs, Home NodeBs, Home eNodeBs, site controllers, access points (APs), wireless routers, and the like. While each of the base stations 114a, 114b is 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.
[0291] 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), a relay node, 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), a relay node, etc. The base station 114a may be configured to transmit and / or receive wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The base station 114b may be configured to transmit and / or receive wired and / or wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, such as 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 use multiple transceivers for each sector of the cell.
[0292] The base station 114a may communicate with one or more of the WTRUs 102a, 102b, 102c over an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).
[0293] The base station 114b may communicate with one or more of the RRHs 118a, 118b and / or the TRPs 119a, 119b via 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, centimeter wave, millimeter wave, etc.). The air interface 115b / 116b / 117b may be established using any suitable radio access technology (RAT).
[0294] The RRHs 118a, 118b and / or TRPs 119a, 119b may communicate with one or more WTRUs 102c, 102d via the 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, centimeter wave, millimeter wave, etc.). The air interface 115c / 116c / 117c may be established using any suitable radio access technology (RAT).
[0295] More specifically, as described above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b and TRPs 119a, 119b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d may implement a radio technology such as Universal Mobile Telecommunications System (UMTS), Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink Packet Access (HSDPA) and / or High Speed Uplink Packet Access (HSUPA).
[0296] In an embodiment, the base station 114a and the RRHs 118a, 118b and TRPs 119a, 119b in the WTRUs 102a, 102b, 102c or 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 use Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. In the future, the air interface 115 / 116 / 117 may implement 3GPP NR technology.
[0297] In an embodiment, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b and TRPs 119a, 119b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.
[0298] For example, Fig.55 The base station 114c in the example may be a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any appropriate RAT for facilitating wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, etc. In an embodiment, the base station 114c and the WTRU 102e may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114c and the WTRU 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114c and the WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or a femtocell. Fig.55 As shown, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114c may not be required to access the Internet 110 through the core network 106 / 107 / 109.
[0299] The RAN 103 / 104 / 105 and / or the 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.
[0300] Although in Fig.55 Although not shown, it will be appreciated that the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b and / or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b or a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b, which may employ an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) employing a GSM radio technology.
[0301] 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 a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another core network connected to one or more RANs described below, which may use the same RAT as the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b or a different RAT.
[0302] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities. For example, the WTRUs 102a, 102b, 102c, 102d, and 102e may include multiple transceivers for communicating with different wireless networks via different wireless links. Fig.55 The WTRU 102e shown in FIG. 1 may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114c, which may employ an IEEE 802 radio technology.
[0303] Fig.56 1 is a block diagram of an exemplary apparatus or device, such as, for example, WTRU 102, configured for wireless communication according to the embodiments described herein. Fig.56As shown, the exemplary WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It should be understood that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments. In addition, the embodiments contemplate that the base stations 114a and 114b and / or the nodes that the base stations 114a and 114b may represent (such as, but not limited to, a transceiver station (BTS), a Node B, a site controller, an access point (AP), a home node-B, an evolved home node-B (eNodeB), a home evolved node-B (HeNB), a home evolved node-B gateway, and a proxy node, etc.) may be included in Fig.56 Some or all of the elements depicted in and described herein.
[0304] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, 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 described below, which may be coupled to the transmit / receive element 122. Although Fig.56 The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0305] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via 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. Fig.55Although not shown, it will be appreciated that the RAN 103 / 104 / 105 and / or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT or a different RAT as the RAN 103 / 104 / 105. For example, in addition to being connected to the RAN 103 / 104 / 105, which may employ an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) employing a GSM radio technology.
[0306] 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 a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another core network connected to one or more RANs described below, which may use the same RAT as the RAN 103 / 104 / 105 or a different RAT.
[0307] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks via different wireless links. Fig.55 The WTRU 102c shown in FIG. 1 may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
[0308] Fig.56 1 is a block diagram of an exemplary apparatus or device, such as, for example, WTRU 102, configured for wireless communication according to the embodiments described herein. Fig.56As shown, the exemplary WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It should be understood that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments. In addition, the embodiments contemplate that the base stations 114a and 114b and / or the nodes that the base stations 114a and 114b may represent (such as, but not limited to, a transceiver station (BTS), a Node B, a site controller, an access point (AP), a home node-B, an evolved home node-B (eNodeB), a home evolved node-B (HeNB), a home evolved node-B gateway, and a proxy node, etc.) may be included in Fig.56 Some or all of the elements depicted in and described herein.
[0309] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, 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 described below, which may be coupled to the transmit / receive element 122. Although Fig.56 The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0310] The transmit / receive element 122 may be configured to transmit a signal to a base station (e.g., base station 114a) or receive a signal from a base station (e.g., base station 114a) via an air interface 115 / 116 / 117. For example, in an embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive an RF signal. In an embodiment, the transmit / receive element 122 may be a transmitter / detector configured to, for example, transmit and / or receive an IR, UV, or visible light signal. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and receive RF and light signals. It should be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.
[0311] In addition, despite Fig.56102 as a single element, but the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117.
[0312] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate over multiple RATs such as, for example, UTRA and IEEE 802.11.
[0313] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an 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 / indicator 128. In addition, the processor 118 may access information from and store data in any type of suitable memory such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In an embodiment, the processor 118 may access information from and store data in memory that is physically located on the WTRU 102, such as on a server or a home computer (not shown).
[0314] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control power to the other components in the WTRU 102. The power source 134 may be any suitable device for providing power to the WTRU 102. For example, the power source 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.
[0315] The processor 118 may also be coupled to the GPS chipset 136 described below, 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 information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 115 / 116 / 117 and / or determine its location based on the times of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.
[0316] The processor 118 may also be coupled to other peripherals 138 described below, which may include one or more software and / or hardware modules for providing additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include various sensors such as an accelerometer, a biometric (e.g., fingerprint) sensor, an electronic compass, a satellite transceiver, a digital camera (for photos or videos), a universal serial bus (USB) port or other interconnect interface, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, etc.
[0317] The WTRU 102 may be embodied in other apparatuses or devices, such as sensors, consumer electronics, wearable devices (such as smart watches or smart clothing), medical or e-health equipment, robots, industrial equipment, drones, vehicles (such as cars, trucks, trains or airplanes), etc. The WTRU 102 may be connected to other components, modules, or systems of such apparatuses or devices through one or more interconnect interfaces, such as an interconnect interface that may include one of the peripheral devices 138.
[0318] Fig.57 1 is a system diagram of the RAN 103 and the core network 106 according to an embodiment. As described above, the RAN 103 may employ UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 115. The RAN 103 may also communicate with the core network 106. Fig.57As shown, the RAN 103 may include Node-Bs 140a, 140b, 140c, each of which may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 115. Each of the Node-Bs 140a, 140b, 140c may be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and RNCs while remaining consistent with an embodiment.
[0319] like Fig.57 As shown, Node B 140a, 140b can communicate with RNC 142a. In addition, Node B 140c can communicate with RNC 142b. Node B 140a, 140b, 140c can communicate with corresponding RNC 142a, 142b through Iub interface. RNC 142a, 142b can communicate with each other through Iur interface. Each of RNC 142a, 142b can be configured to control each Node B 140a, 140b, 140c connected thereto. In addition, each of RNC 142a, 142b can be configured to perform or support other functions such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security function, data encryption, etc.
[0320] Fig.57 The core network 106 shown in FIG. 1 may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and / or a gateway GPRS support node (GGSN) 150. Although each of the foregoing elements is depicted as part of the core network 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.
[0321] 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.
[0322] The RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0323] As described above, the core network 106 may also be connected to the networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.
[0324] Fig.58 1 is a system diagram of the RAN 104 and the core network 107 according to an embodiment. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the core network 107.
[0325] 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. Each of the eNode-Bs 160a, 160b, 160c may 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.
[0326] Each of the eNodeBs 160a, 160b, 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, etc. Fig.58 As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.
[0327] Fig.58 The core network 107 shown in FIG. 1 may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. Although each of the foregoing elements is depicted as part of the core network 107, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.
[0328] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.
[0329] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The serving gateway 164 may generally route / forward user data packets to / from the WTRUs 102a, 102b, 102c. The serving gateway 164 may also perform other functions, such as anchoring a user plane during inter-eNode-B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.
[0330] 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.
[0331] 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 owned and / or operated by other service providers.
[0332] Fig.591 is a system diagram of the RAN 105 and the core network 109 according to an embodiment. The RAN 105 may be an access service network (ASN) that employs IEEE 802.16 radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 117. As will be discussed further below, the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, the RAN 105, and the core network 109 may be defined as reference points.
[0333] like Fig.59 As shown, the RAN 105 may include base stations 180a, 180b, 180c and an ASN gateway 182, but it should be appreciated that the RAN 105 may include any number of base stations and ASN gateways while remaining consistent with the embodiment. Each of the base stations 180a, 180b, 180c may be associated with a particular cell in the RAN 105 and may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 117. In an embodiment, the base stations 180a, 180b, 180c may implement MIMO technology. Thus, the base station 180a, for example, may use multiple antennas to send wireless signals to the WTRU 102a and receive wireless signals from the WTRU 102a. The base stations 180a, 180b, 180c may also provide mobility management functions, such as handover triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and the like. The ASN gateway 182 may serve as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 109, and the like.
[0334] The air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as an R1 reference point for implementing the IEEE 802.16 specification. In addition, each of the WTRUs 102a, 102b, 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.
[0335] The communication link between each base station 180a, 180b, 180c may be defined as an R8 reference point, which includes protocols for facilitating WTRU handovers and data transfer 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.
[0336] like Fig.59 As shown, the RAN 105 may be connected to a core network 109. The communication link between the RAN 105 and the core network 109 may be defined as an R3 reference point, which includes, for example, protocols for facilitating data transmission and mobility management capabilities. The core network 109 may include a mobile IP home agent (MIP-HA) 184, an authentication, authorization, accounting (AAA) server 186, and a gateway 188. Although each of the foregoing elements is depicted as part of the core network 109, it should be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.
[0337] The MIP-HA may be responsible for IP address management and may enable the WTRUs 102a, 102b, 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 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.
[0338] Despite Fig.59Although not shown, it will be appreciated that the RAN 105 may be connected to other ASNs and the core network 109 may be connected to other core networks. The communication link between the RAN 105 and the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 105 and the other ASNs. The communication link between the core network 109 and the other core networks may be defined as an R5 reference, which may include protocols for facilitating interworking between a home core network and a visited core network.
[0339] Described here and in Fig.55 , Fig.57 , Fig.58 ,as well as Fig.59 The core network entities described in the specification are identified by the names given to those entities in certain existing 3GPP specifications, but it should be understood that in the future these entities and functions may be identified by other names, and that certain entities or functions may be combined in future specifications published by 3GPP (including future 3GPP NR specifications). Figure 55-Figure 59 The specific network entities and functions described and illustrated in the present disclosure are provided by way of example only, and it should be understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or defined in the future.
[0340] Fig.60 is a block diagram of an exemplary computing system 90 in which the Fig.55 , Fig.57 , Fig.58 ,as well as Fig.59103 / 104 / 105, core network 106 / 107 / 109, PSTN 108, Internet 110, or some nodes or functional entities in other networks 112. The computing system 90 may include a computer or a server and may be controlled primarily by computer-readable instructions, which may be located anywhere in the form of software, or any device that stores or accesses such software. Such computer-readable instructions may be executed within the processor 91 to enable the computing system 90 to operate. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal encoding, data processing, power control, input / output processing, and / or any other function that enables the computing system 90 to operate in a communication environment. The coprocessor 81 is an optional processor or auxiliary processor 91 that is different from the main processor 91 and can perform additional functions. Processor 91 and / or coprocessor 81 may receive, generate, and process data related to the methods and apparatus disclosed herein.
[0341] In operation, processor 91 fetches, decodes, and executes instructions, and transmits information to and receives information from other resources through the computing system's main data transmission path (system bus 80). Such a system bus connects components in computing system 90 and defines a medium for data exchange. System bus 80 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus. An example of such a system bus 80 is a PCI (Peripheral Component Interconnect) bus.
[0342] The memory coupled to the system bus 80 includes a random access memory (RAM) 82 and a read-only memory (ROM) 93. Such memory includes circuits that allow information to be stored and retrieved. ROM 93 typically contains stored data that is not easily modified. The data stored in RAM 82 can be read or changed by a processor 91 or other hardware device. A memory controller 92 can control access to RAM 82 and / or ROM 93. The memory controller 92 can provide an address translation function for converting a virtual address to a physical address when executing instructions. The memory controller 92 can also provide a memory protection function for isolating processes within the isolation system and isolating system processes from user processes. Thus, a program running in the first mode can only access memory mapped by its own process virtual address space; unless memory sharing between processes has been set up, it cannot access memory within the virtual address space of another process.
[0343] In addition, the computing system 90 may include a peripheral device controller 83 that is responsible for transmitting instructions from the processor 91 to peripheral devices such as a printer 94 , a keypad 84 , a mouse 95 , and a disk drive 85 .
[0344] The display 86 controlled by the display controller 96 is used to display the visual output generated by the computing system 90. Such visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). The display 86 may be implemented with a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch pad. The display controller 96 includes the electronic components required to generate the video signal sent to the display 86.
[0345] In addition, the computing system 90 may include communication circuitry such as, for example, a network adapter 97, which may be used to connect the computing system 90 to a network such as the RAN 103 / 104 / 105, the core network 106 / 107 / 109, the PSTN 108, the Internet 110, or Figure 55-Figure 59 The processor 91 may be connected to an external communication network such as other networks 112 to enable the computing system 90 to communicate with other nodes or functional entities of those networks. Communication circuits, either alone or in combination with the processor 91, may be used to perform the sending and receiving steps of certain devices, nodes, or functional entities described herein.
[0346] It should be understood that any or all of the devices, 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, when executed by a processor such as processor 118 or 91, causes the processor to execute and / or implement the systems, methods, and processes described herein. Specifically, any step, operation, or function described herein may be implemented in the form of such computer executable instructions, which are executed on a processor of a device or computing system configured for wireless and / or wired network communication. Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented by any non-temporary (e.g., tangible or physical) method or technology for storing information, but such computer-readable storage media do not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, cassettes, tapes, disk storage or other magnetic storage devices, or any other tangible or physical media that can be used to store the desired information and can be accessed by a computing system.
Claims
1. A first device comprising a processor, a memory, and a communication circuit, the first device being connected to a network via its communication circuit, the first device further comprising computer executable instructions stored in the memory, the computer executable instructions when executed by the processor causing the first device to perform operations comprising: receiving an ungranted transmission from a second device via resources preconfigured for the second device, the ungranted transmission comprising a hybrid automatic repeat request process; receiving a first redundant version of the hybrid automatic repeat request process from a second device via a control channel; sending a response to the unauthorized transmission, the response to the unauthorized transmission comprising an acknowledgement in downlink control information, and wherein, The downlink control information includes one or more acknowledgement bits for a plurality of transport blocks and an unlicensed-radio network temporary identifier; as well as If the first device does not send a positive acknowledgement of the ungranted transmission, a retransmitted second redundancy version is received from the second device indicated via the control channel.
2. The device according to claim 1, wherein: The operations further include receiving multiple redundant versions of the multiple retransmissions.
3. An apparatus comprising a processor, a memory, and a communication circuit, the apparatus being connected to a network via its communication circuit, the apparatus further comprising computer executable instructions stored in the memory, the computer executable instructions when executed by the processor causing the apparatus to perform operations comprising: sending an ungranted transmission via resources preconfigured for the apparatus, the ungranted transmission including a hybrid automatic repeat request process; indicating a first redundancy version of the hybrid automatic repeat request process via a control channel; receiving a response to the unlicensed transmission, the response to the unlicensed transmission comprising an acknowledgement in downlink control information, and wherein the downlink control information comprises one or more acknowledgement bits for a plurality of transport blocks and an unlicensed-radio network temporary identifier; and If a positive acknowledgement is not received, then: selecting a second redundancy version for a first retransmission, the first retransmission including the hybrid automatic repeat request processing; sending a first retransmission via resources preconfigured for the apparatus; and The second redundancy version of the hybrid automatic repeat request process is indicated via a control channel.
4. The device according to claim 3, wherein: The operations further include: selecting a plurality of redundant versions of a plurality of retransmissions, a second retransmission including said hybrid automatic repeat request processing; indicating the plurality of redundancy versions via the control channel; and The plurality of retransmissions are sent via resources preconfigured for the apparatus.
5. The device according to claim 3, wherein: The operations further include: Transmit hybrid automatic repeat request processing; The HARQ transaction is retransmitted until a positive acknowledgement is received.
6. The device according to claim 5, wherein: The apparatus is configured to retransmit the hybrid automatic repeat request process at a specific period.
7. The device according to claim 5, wherein: The apparatus is configured to retransmit the hybrid automatic repeat request process until a predetermined limit on the number of retransmissions is met or a positive acknowledgement is received.
8. The device according to claim 7, wherein: The predetermined limit of the number of retransmissions is two or more.
9. The device according to claim 7, wherein: The operations further include: receiving a negative acknowledgement; and The hybrid automatic repeat request process is retransmitted a plurality of times after receiving the negative acknowledgement, up to a predetermined limit on the number of retransmissions.
10. The device according to claim 5, wherein: The retransmission starts before an acknowledgment response is expected to be received.
11. The device according to claim 3, wherein: The operations further include: transmitting a first transport block comprising a first set of code block groups; receiving a multi-bit ACK-NACK response to a first transport block, the multi-bit ACK-NACK response to the first transport block comprising an ACK-NACK response to each code block group in the first transport block; and A second transport block is transmitted including a second set of code block groups including only those code block groups of the first set for which no ACK response was received in the multi-bit ACK-NACK response.
12. The device according to claim 11, wherein: The number of bits in the multi-bit ACK-NACK response is equal to the number of code block groups in the first set of code block groups.
13. The device according to claim 11, wherein: The number of bits in the multi-bit ACK-NACK response is equal to the number of code blocks in the first transport block.
14. The device according to claim 11, wherein: The second transport block further includes link control information including information about a code block group included in the second transport block.
15. The device according to claim 14, wherein: The link control information is downlink control information.
16. The device according to claim 11, wherein The code block groups of the first set include a first group and a second group, and the first group and the second group include different numbers of code blocks.
