Enhanced HARQ feedback for reliable communication
By introducing a multi-valued HARQ-ACK feedback mechanism in the LTE system, the number of repetitions of PDSCH is dynamically adjusted, which solves the problem of improper resource allocation in the traditional HARQ mechanism in the LTE system, and improves spectrum efficiency and channel adaptability.
Patent Information
- Application Number
- CN201980054030.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-08-10
- Filing Date
- 2019-08-08
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2039-08-08
AI Technical Summary
In LTE systems, traditional HARQ mechanisms are difficult to effectively optimize the number of PDSCH repetitions, resulting in improper resource allocation and affecting the system spectrum efficiency.
By introducing a multi-valued HARQ-ACK feedback mechanism between the UE and gNB, the UE allows the UE to feedback the minimum number of repetitions correctly decoded according to actual needs, and dynamically schedule the number of repetitions of PDSCH on the network side to adapt to channel conditions.
It improves the spectrum efficiency of the system, reduces resource waste, improves the accuracy and flexibility of PDSCH transmission, and adapts to instantaneous channel changes.
Smart Images

Figure CN112567666B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 62 / 717,542, filed on August 10, 2018, which is hereby incorporated by reference in its entirety. Technical Field
[0003] The present application relates generally to wireless communication systems, and more particularly to Hybrid Automatic Repeat Request (HARQ) in New Radio (NR) systems. Background Art
[0004] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the third generation partnership project (3GPP) long term evolution (LTE); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is often referred to as the Worldwide Interoperability for Microwave Access (WiMAX) by industry organizations; and the IEEE 802.11 standard for wireless local area networks (WLANs), which is often referred to as Wi-Fi by industry organizations. In the 3GPP radio access network (RAN) in the LTE system, the base station may include a RAN node such as an evolved universal terrestrial radio access network (E-UTRAN) node B (also often referred to as an evolved node B, enhanced node B, eNodeB or eNB) and / or a radio network controller (RNC) in the E-UTRAN, which communicates with a wireless communication device called a user equipment (UE). In the fifth generation (5G) wireless RAN, the RAN node may include a 5G node, a new air interface (NR) node or a g node B (gNB). BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Figure 1 A four-value HARQ mapping according to one embodiment is shown.
[0006] Figure 2 A three-value HARQ mapping according to one embodiment is shown.
[0007] Figure 3 A method according to one embodiment is shown.
[0008] Figure 4 A method according to one embodiment is shown.
[0009] Figure 5 A system according to one embodiment is shown.
[0010] Figure 6 A system according to one embodiment is shown.
[0011] Figure 7 An apparatus according to one embodiment is shown.
[0012] Figure 8 An exemplary interface according to one embodiment is shown.
[0013] Fig. 9 Components according to one embodiment are shown. DETAILED DESCRIPTION
[0014] I. Introduction
[0015] To support enhanced reliability based on the 1ms latency constraint in LTE, only certain techniques are currently used or being considered. For example, for Physical Control Format Indicator Channel (PCFICH) reliability, semi-static configuration of PCFICH duration is being developed to avoid PCFICH reliability affecting overall downlink (DL) reliability. Blind / no HARQ repetition for scheduled downlink shared channel (DL-SCH) operation is also being studied. Specifically, due to the legacy short / extended (S / E) physical downlink control channel (PDCCH) and short (S) physical uplink control channel (PUCCH) formats (if applicable), any potential downlink control information (DCI) modifications are limited to supporting blind / no HARQ repetition.
[0016] In an implementation scheme, the PDCCH indicates the number of physical downlink shared channel (PDSCH) transmissions associated with the PDCCH. After successfully receiving the PDCCH, the PDSCH transmissions may be soft combined. The number of transmissions k is the number of PDSCH transmissions associated with the PDCCH starting with the current transmission time interval (TTI). If a PDSCH using blind repetition is received in a (s)TTI in a serving cell, the UE may delete any PDSCH allocation for that (s)TTI in the same serving cell with a cyclic redundancy check (CRC) scrambled with a cell radio network temporary identifier (C-RNTI). In some implementation schemes, for PDSCH repetition, a two-bit field is modified to a DCI related to the PDSCH. Blind / HARQ-free PDSCH repetition is enabled by RRC configuration. For slot / subslot PDSCH repetition, rate matching around short PDCCH (SPDCCH) resources for PDSCH transmissions within the repetition window follows rate matching around SPDCCH resources for the first PDSCH transmission in the repetition window. For TM10 blind / HARQ-free PDSCH repetition, the UE assumes that the same quasi-colocation indicator (PQI) applies to all PDSCH repetitions.
[0017] PDSCH repetitions associated with a single downlink (DL) allocation assume the same resource block (RB) allocation. For PDSCH based on slot / subslot PDSCH repetition and demodulation reference signal (DMRS), the UE can assume that the same precoder is retained between PDSCH repetitions. For time division duplex (TDD), the UE cannot assume coherent DMRS channel estimation across uplink (UL) / DL switching points. This allows the UE to perform coherent channel estimation filtering. For subslot PDSCH repetition, DMRS sharing does not support blind / HARQ-free PDSCH repetitions with k>1, i.e., DMRS is present in every subslot. For slot / subslot PDSCH with k>1, the maximum transmission level of the received PDSCH is 2. For PDSCH repetition, different redundancy versions (RVs) can be used in different PDSCH transmissions within the repetition window. For PDSCH repetition and RV cycles that can be configured by higher layer signaling and selected between {0,0,0,0} or {0,2,3,1}, the RV field of the repetition sequence for scheduling k PDSCH transmissions in the DCI identifies the starting RV in the cyclic sequence for the first transmission of PDSCH within the repetition window. For HARQ for repeated PDSCH transmissions, the UE can report HARQ feedback using the timing given by the last PDSCH repetition.
[0018] Embodiments of the present invention include methods for enhancing HARQ-acknowledgement (ACK) feedback for PDSCH repetition transmission. Specifically, the disclosed method enables UE to feedback ACK for PDSCH with fewer repetitions than scheduled. This helps the network adjust the PDSCH repetition number according to channel conditions to further optimize the overall system spectrum efficiency.
[0019] Embodiments herein include enhanced HARQ-ACK feedback for PDSCH repetition transmissions, whereby a UE can signal HARQ-ACK for a PDSCH with a repetition number less than the scheduled repetition number. Specifically, certain embodiments enable the network to implement different multi-value HARQ-ACK feedback for a PDSCH with repetitions.
[0020] In one embodiment, multi-value HARQ-ACK feedback is provided for multiple repetitions. In certain such embodiments, the multi-value HARQ-ACK feedback enables the UE to feedback the ACK response achieved with the minimum number of repetitions in the current scheduled data.
[0021] In another embodiment, multi-value HARQ-ACK feedback is provided for partial reception of scheduled PDSCH. In certain such embodiments, the UE may feedback a HARQ-ACK message corresponding to partial reception of scheduled data. Such embodiments may be applied, for example, to implicit repetitive data scheduling.
[0022] In another embodiment, a multi-value HARQ-ACK feedback configuration is used for PDSCH with repetitions. The gNB may use certain such embodiments, for example, to configure the UE to implement multi-value HARQ-ACK feedback.
[0023] Another implementation uses dynamic signaling with repeated data transmissions. Certain such implementations enable the gNB to dynamically schedule data with different repetition times to better adjust the transmission based on channel conditions.
[0024] Embodiments herein may include methods for enabling multi-value HARQ-ACK feedback for data transmission with repetitions. Based on the enhanced HARQ-ACK feedback, the gNB may appropriately adjust the number of repetitions according to channel conditions so that better overall system spectrum efficiency may be achieved.
[0025] II. Enhanced HARQ feedback for PDSCH repeated transmission
[0026] In traditional HARQ feedback for PDSCH repetition transmission, the UE may provide an ACK / negative acknowledgement (NACK) after receiving the last PDSCH repetition. In cases where channel conditions are better than assumed by the gNB, the UE may correctly decode the PDSCH before receiving all repetitions. For example, assuming good channel conditions, if the gNB schedules a PDSCH with four repetitions, the UE may correctly decode the PDSCH by using only the first two repetitions. When the UE feeds back an ACK response to the gNB, it may be beneficial for the UE to signal the minimum number of repetitions that is sufficient for the UE to achieve correct PDSCH decoding. Such an indication may help the gNB apply an appropriate number of repetitions to avoid allocating excessive resources for PDSCH transmission. Accordingly, the following enhanced HARQ feedback method is disclosed.
[0027] (A) Multi-value HARQ-ACK feedback for multiple repetitions
[0028] In one embodiment, when the UE provides feedback of the ACK response to the gNB, the UE may also signal the number of repetitions it actually used to achieve correct decoding. For example, if four repetitions are scheduled for PDSCH transmission, the following HARQ value mapping may be used for HARQ feedback:
[0029] 0: NACK
[0030] 1: ACK for 1 transmission / duplicate
[0031] 2: ACK for 2 transmissions / duplicates
[0032] 3: ACK for 4 transmissions / repeats
[0033] Using the above exemplary mapping, the UE can be configured with at least four PUCCH sequences, so that each of these sequences represents a specific HARQ value. On the receiver side, the gNB can detect which specific ACK sequence is received.
[0034] NR PUCCH format 0 based on a single RB can be used to feedback up to 2-bit HARQ response values. In this way, PUCCH format 0 can be used to convey the multi-value HARQ feedback for PDSCH with repetitions proposed above.
[0035] For example, Figure 1 A four-value HARQ mapping 100 of HARQ-ACK bits to sequences is shown according to one embodiment. Figure 1 In the example, m defines the cyclic shift value of the PUCCH format 0 sequence.
[0036] If such multi-valued HARQ feedback requires a smaller number of PUCCH sequences, the following ACK / NACK value mapping may be used for certain implementations:
[0037] 0: NACK
[0038] 1: ACK for at least 2 transmissions / duplicates
[0039] 2: ACK for at least 4 transmissions / repeats
[0040] Utilizing the above mapping example, the UE is configured with only three PUCCH sequences, which reduces the gNB PUCCH receiver complexity and potentially improves PUCCH coverage performance.
[0041] Figure 2 A three-value HARQ mapping 200 of HARQ-ACK bits to sequences is shown according to one embodiment. Figure 2 The m in defines the cyclic shift value of the PUCCH format 0 sequence.
[0042] (B) Multi-value HARQ-ACK feedback for partial reception of scheduled PDSCH
[0043] In NR, for PDSCH with data mapping type B, that is, the PDSCH scheduled thereby is not aligned with the time slot boundary and does not start from the beginning of the time slot boundary. The PDSCH can be scheduled for up to fourteen orthogonal frequency division multiplexing (OFDM) symbols. For mini-slot-based scheduling, such as two OS-based mini-slots, a single PDSCH can be scheduled by scheduling a mini-slot-based PDCCH to schedule a PDSCH with four repetitions, which spans several mini-slots corresponding to the total duration of several repetitions. In order to enable ACK responses for different effective coding rates to help the network determine the appropriate coding rate, similar to the implementation discussed above, the following multi-value ACK / NACK responses can be defined for the first option:
[0044] 0: NACK
[0045] 1: ACK received for 1 / 4 of the PDSCH
[0046] 2: ACK for PDSCH 1 / 2 reception
[0047] 3: ACK for complete reception of PDSCH
[0048] In another embodiment, the following multi-value ACK / NACK response may be defined for the second option:
[0049] 0: NACK
[0050] 1: ACK for 1 / 2 reception of PDSCH
[0051] 3: ACK for complete reception of PDSCH
[0052] In certain embodiments, the Figure 1 and Figure 2 The above two options are signaled based on the multi-valued HARQ feedback mapped as shown in .
[0053] (C) Multi-value HARQ-ACK feedback configuration for PDSCH with repetition
[0054] To enable multi-value HARQ-ACK feedback for PDSCH with repetition, radio resource control (RRC) based signaling may be used. In one embodiment, the RRC parameter PDSCH-MultipValueHARQPerTBFeedback may be defined as follows:
[0055] PDSCH-NbrHARQValuesPerTBFeedback:={"n2", "n3", "n4"}, where "n2" refers to 2-value HARQ feedback corresponding to legacy 1-bit HARQ feedback, "n3" refers to 3-value HARQ feedback, and "n4" refers to 4-value HARQ feedback.
[0056] (D) Dynamic signaling with repeated data transmission
[0057] In some NR implementations, PDSCH and PUSCH with repetitions may be semi-statically configured with RRC signaling. Therefore, if the UE wants to change the number of repetitions for scheduled data, RRC reconfiguration is performed. This can result in huge signaling overhead, and it is not possible to flexibly and quickly adjust the number of repetitions according to instantaneous channel conditions. Therefore, it may be beneficial to enable dynamic scheduling of different numbers of repetitions for each data transmission based on the latest channel state information (DCI) from the UE. To this end, the UE may be configured with a maximum or predetermined number of repetitions for each data scheduling through RRC signaling, and the accurate number of repetitions for the scheduled data may be signaled through the PDCCH of the scheduled data. In one embodiment, the DCI may signal a maximum number of repetitions not exceeding the maximum number of repetitions configured for the scheduled data. In another embodiment, in order to save DCI signaling overhead, the following method for reducing signaling overhead may also be used.
[0058] For example, a 1-bit repetition bit field in a DCI may have the following meanings:
[0059] 0: repetitions with half the configured maximum number of repetitions
[0060] 1: Repeat with the configured maximum number of repetitions
[0061] As another example, the 2-bit repeated bit field in the DCI may have the following meanings:
[0062] 0: has 1 / 4 of the configured maximum number of repetitions
[0063] 1: Repeat with half the configured maximum number of repetitions
[0064] 2: Repeat with configured maximum number of repetitions
[0065] III. Exemplary Methods
[0066] Figure 3A method 300 for a UE according to one embodiment is shown. In block 302, the method 300 processes repetitions of a PDSCH transmission. In block 304, the method 300 determines a minimum number of repetitions used by the UE to decode the PDSCH transmission. In block 306, the method 300 generates HARQ feedback in response to the PDSCH transmission, the HARQ feedback indicating the minimum number of repetitions used by the UE to decode the PDSCH transmission.
[0067] Figure 4 A method 400 for a node in a wireless network according to one embodiment is shown. In block 402, the method 400 schedules a first physical downlink shared channel (PDSCH) transmission having a first repetition number for a user equipment (UE). In block 404, the method 400 processes a hybrid automatic repeat request (HARQ) feedback from the UE corresponding to the first PDSCH transmission. In block 406, the method 400 determines a second repetition number used by the UE to decode the first PDSCH transmission based on the HARQ feedback. In block 408, the method 400 schedules a second PDSCH transmission for the UE based on the second repetition number.
[0068] IV. Exemplary Systems and Apparatus
[0069] Some systems and devices or apparatuses described below may be configured according to the embodiments described above. For example, some UEs (or apparatuses for UEs or baseband processors for UEs) or some nodes (or gNBs or apparatuses or processors for gNBs) described below may be configured to perform Figure 3 or Figure 4 The method shown, or any other embodiment described herein is provided.
[0070] Figure 5 The architecture of a system 500 of a network according to some embodiments is shown. The system 500 includes one or more user equipments (UEs), shown in this example as UE 502 and UE 504. UEs 502 and 504 are shown as smart phones (e.g., handheld touch screen mobile computing devices that can connect to one or more cellular networks), but these UEs may also include any mobile or non-mobile computing devices, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handheld terminals, or any computing device that includes a wireless communication interface.
[0071] In some embodiments, any of UEs 502 and 504 may include an Internet of Things (IoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communication, a sensor network, or an IoT network. The M2M or MTC data exchange may be a machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.
[0072] UE 502 and UE 504 may be configured to connect (e.g., be communicatively coupled) to a radio access network (RAN) (shown as RAN 506). RAN 506 may be, for example, an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NG RAN), or some other type of RAN. UE 502 and 504 utilize connection 508 and connection 510, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connection 508 and connection 510 are shown as air interfaces to achieve communicatively coupling, and may be consistent with a cellular communication protocol, such as a global system for mobile communications (GSM) protocol, a code division multiple access (CDMA) network protocol, a push-to-talk (PTT) protocol, a cellular PTT protocol (POC), a universal mobile telecommunications system (UMTS) protocol, a 3GPP long term evolution (LTE) protocol, a fifth generation (5G) protocol, a new radio (NR) protocol, etc.
[0073] In this embodiment, UE 502 and UE 504 may also directly exchange communication data via the ProSe interface 512. The ProSe interface 512 may alternatively be referred to as a sidelink interface including one or more logical channels including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).
[0074] UE 504 is shown configured to access an access point (AP) (shown as AP 514) via connection 516. Connection 516 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 514 would include wireless fidelity. In this example, AP 514 may be connected to the Internet without being connected to the core network of the wireless system (described in further detail below).
[0075] The RAN 506 may include one or more access nodes that enable connections 508 and 510. These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). The RAN 506 may include one or more RAN nodes (e.g., macro RAN nodes 518) for providing macro cells, and one or more RAN nodes (e.g., low power (LP) RAN nodes such as LP RAN nodes 520) for providing femto cells or pico cells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macro cells).
[0076] Either the macro RAN node 518 or the LP RAN node 520 may terminate the air interface protocol and may be the first point of contact for the UE 502 and the UE 504. In some embodiments, either the macro RAN node 518 or the LP RAN node 520 may fulfill various logical functions of the RAN 506, including but not limited to radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
[0077] According to some embodiments, UE 502 and UE 504 may be configured to communicate with each other or with either macro RAN node 518 and LP RAN node 520 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as but not limited to orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communication) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.
[0078] In some embodiments, the downlink resource grid can be used for downlink transmission from either the macro RAN node 518 and the LP RAN node 520 to the UE 502 and the UE 504, while the uplink transmission can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is the physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is a common practice, which makes the allocation of wireless resources intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements. In the frequency domain, this can represent the minimum amount of resources that can be currently allocated. Several different physical downlink channels are transmitted using such resource blocks.
[0079] The physical downlink shared channel (PDSCH) may carry user data and high-layer signaling to the UE 502 and UE 504. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocation related to the PDSCH channel, among other things. It may also inform the UE 502 and UE 504 of the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to the UE 504 within the cell) may be performed at either the macro RAN node 518 and the LP RAN node 520 based on channel quality information fed back from either the UE 502 and UE 504. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of the UE 502 and UE 504.
[0080] PDCCH can use control channel elements (CCE) to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to four sets of nine physical resource elements, called resource element groups (REGs). Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the downlink control information (DCI) and channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).
[0081] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. One or more enhanced control channel elements (ECCEs) may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to four sets of nine physical resource elements, referred to as enhanced resource element groups (EREGs). In some cases, ECCEs may have other numbers of EREGs.
[0082] The RAN 506 is communicatively coupled to a core network (CN) (shown as CN 528) via an S1 interface 522. In an embodiment, the CN 528 may be an evolved packet core (EPC) network, a next generation packet core (NPC) network, or some other type of CN. In this embodiment, the S1 interface 522 is divided into two parts: an S1-U interface 524, which carries traffic data between the macro RAN node 518 and the LP RAN node 520 and the serving gateway (S-GW) (shown as S-GW 532), and an S1-mobility management entity (MME) interface (shown as S1-MME interface 526), which is a signaling interface between the macro RAN node 518 and the LP RAN node 520 and the MME 530.
[0083] In this embodiment, CN 528 includes MME 530, S-GW 532, Packet Data Network (PDN) Gateway (P-GW) (shown as P-GW 534) and Home Subscriber Server (HSS) (shown as HSS 536). MME 530 may be similar in function to the control plane of a conventional Serving General Packet Radio Service (GPRS) Support Node (SGSN). MME 530 may manage access-related mobility aspects such as gateway selection and tracking area list management. HSS 536 may include a database for network users, which includes subscription-related information for supporting network entities in handling communication sessions. Depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, etc., CN528 may include one or more HSS 536. For example, HSS 536 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc.
[0084] The S-GW 532 may terminate the S1 interface 322 towards the RAN 506 and route data packets between the RAN 506 and the CN 528. In addition, the S-GW 532 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies.
[0085] The P-GW 534 may terminate the SGi interface towards the PDN. The P-GW 534 may route data packets between the CN 528 (e.g., the EPC network) and an external network such as a network including an application server 542 (alternatively referred to as an application function (AF)) via the Internet Protocol (IP) (shown as an IP communication interface 538). Generally, the application server 542 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS packet service (PS) domain, LTE PS data service, etc.). In this embodiment, the illustrated P-GW 534 is communicatively coupled to the application server 542 via the IP communication interface 538. The application server 542 may also be configured to support one or more communication services (e.g., voice over Internet protocol (VoIP) sessions, PTT sessions, group communication sessions, social network services, etc.) for the UE 502 and UE 504 via the CN 528.
[0086] The P-GW 534 may also be a node for policy enforcement and charging data collection. The Policy and Charging Enforcement Function (PCRF) (shown as PCRF 540) is a policy and charging control element of the CN 528. In a non-roaming scenario, there may be a single PCRF in a domestic public land mobile network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of a UE. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with an IP-CAN session of a UE: a domestic PCRF (H-PCRF) within the HPLMN and a visited PCRF (V-PCRF) within a visited public land mobile network (VPLMN). The PCRF 540 may be communicatively coupled to an application server 542 via the P-GW 534. The application server 542 may signal the PCRF 540 to indicate a new service flow and select appropriate quality of service (QoS) and charging parameters. PCRF 540 may configure the rule to a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate Communication Flow Template (TFT) and QoS Class Identifier (QCI), which initiates the QoS and charging specified by the application server 542 .
[0087] Figure 6The architecture of a system 600 of a network according to some embodiments is shown. The illustrated system 600 includes a UE 602, which may be the same or similar to the previously discussed UE 502 and UE 504; a 5G access node or RAN node (illustrated as (R) AN node 608), which may be the same or similar to the previously discussed macro RAN node 518 and / or LP RAN node 520; a user plane function (illustrated as UPF 604); a data network (DN 606), which may be, for example, an operator service, Internet access, or a third-party service; and a 5G core network (5GC) (illustrated as CN 610).
[0088] CN 610 may include an authentication server function (AUSF 614); a core access and mobility management function (AMF 612); a session management function (SMF 618); a network exposure function (NEF 616); a policy control function (PCF 622); a network function (NF) repository function (NRF 620); a unified data management (UDM 624); and an application function (AF 626). CN 610 may also include other elements not shown, such as a structured data storage network function (SDSF), an unstructured data storage network function (UDSF), etc.
[0089] The UPF 604 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with the DN 606, and a branch point to support multi-homed PDU sessions. The UPF 604 may also perform packet routing and forwarding, packet inspection, user plane portion of policy rule enforcement, lawful interception of packets (UP collection); traffic usage reporting, QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic validation (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF 604 may include an uplink classifier for supporting routing of communication flows to a data network. The DN 606 may represent various network operator services, Internet access, or third-party services. The DN 606 may include or be similar to the application server 542 discussed previously.
[0090] The AUSF 614 may store data and handle authentication-related functions for authenticating the UE 602. The AUSF 614 may facilitate a common authentication framework for various access types.
[0091] AMF 612 may be responsible for registration management (e.g., responsible for registering UE 602, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. AMF 612 may provide delivery for SM messages for SMF 618 and act as a transparent proxy for routing SM messages. AMF 612 may also provide services for UE 602 and SMS function (SMSF) ( Figure 6 The AMF 612 may provide for transmission of short message service (SMS) messages between the AUSF 614 and the UE 602 (not shown). The AMF 612 may act as a security anchor function (SEA), which may include interaction with the AUSF 614 and the UE 602, receiving intermediate keys established as a result of the UE 602 authentication process. In the case of using USIM-based authentication, the AMF 612 may retrieve security information from the AUSF 614. The AMF 612 may also include a secure content management (SCM) function that receives keys from the SEA for deriving access network-specific keys. In addition, the AMF 612 may be the termination point for the RAN CP interface (N2 reference point), the termination point for NAS (NI) signaling, and perform NAS encryption and integrity protection.
[0092] AMF 612 may also support NAS signaling with UE 602 via the N3 interworking function (IWF) interface. N3IWF may be used to provide access to untrusted entities. N3IWF may be an endpoint of the N2 and N3 interfaces for the control plane and user plane, respectively, and may therefore handle N2 signaling for PDU sessions and QoS from SMF and AMF, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets in the uplink, and enforce QoS corresponding to the N3 packet marking taking into account the QoS requirements associated with such markings received via N2. N3IWF may also relay uplink and downlink control plane NAS (NI) signaling between UE 602 and AMF 612, and relay uplink and downlink user plane packets between UE 602 and UPF 604. N3IWF also provides a mechanism for establishing an IPsec tunnel with UE 602.
[0093] SMF 618 may be responsible for session management (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes); UE IP address allocation & management (including optional authorization); selection and control of UP functions; configuring traffic steering at UPF to route traffic to the correct destination; terminating the interface towards the policy control function; control part of policy enforcement and QoS; lawful interception (for SM events and interface with LI system); terminating the SM part of NAS messages; downlink data notification; initiator of AN-specific SM information sent to AN via AMF over N2; determining the SSC mode of the session. SMF 618 may include the following roaming functions: handling local execution to apply QoS SLA (VPLMN); charging data collection and charging interface (VPLMN); lawful interception (for SM events and interface with LI system, in VPLMN); supporting interaction with external DNs to transmit signaling for PDU session authorization / authentication over external DNs.
[0094] NEF 616 may provide components for securely exposing services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, application functions (e.g., AF 626), edge computing or fog computing systems, etc. In such embodiments, NEF 616 may authenticate, authorize and / or restrict AF. NEF 616 may also convert information exchanged with AF 626 and information exchanged with internal network functions. For example, NEF 616 may convert between AF service identifiers and internal 5GC information. NEF 616 may also receive information from other network functions (NFs) based on the exposure capabilities of other network functions. The information may be stored at NEF 616 as structured data, or stored at a data storage NF using a standardized interface. The stored information may then be re-exposed to other NFs and AFs by NEF 616, and / or used for other purposes such as analysis.
[0095] NRF 620 may support service discovery functions, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 620 also maintains information of available NF instances and the services they support.
[0096] PCF 622 may provide for control plane functions to enforce their policy rules and may also support a unified policy framework for managing network behavior. PCF 622 may also implement a front end (FE) to access subscription information related to policy decisions in the UDR of UDM 624.
[0097] The UDM 624 may process subscription-related information to support the handling of communication sessions by network entities, and may store subscription data for the UE 602. The UDM 624 may include two parts: an application FE and a user data repository (UDR). The UDM may include a UDM FE that is responsible for handling credentials, location management, subscription management, and the like. In different transactions, several different front ends may serve the same user. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing; user identity processing; access authorization; registration / mobility management; and subscription management. The UDR may interact with the PCF 622. The UDM 624 may also support SMS management, where the SMS-FE implements similar application logic as previously discussed.
[0098] AF 626 can provide application influence on traffic routing, access to network capability exposure (NCE), and interact with the policy framework for policy control. NCE can be a mechanism that allows 5GC and AF 626 to provide information to each other via NEF 616, which can be used for edge computing implementation. In such implementations, network operators and third-party services can be hosted near the UE 602 access point of the attachment to achieve effective service delivery through reduced end-to-end delay and load on the transmission network. For edge computing implementation, 5GC can select UPF 604 near UE 602 and perform traffic steering from UPF 604 to DN 606 via the N6 interface. This can be based on UE subscription data, UE location and information provided by AF 626. In this way, AF 626 can affect UPF (re) selection and traffic routing. Based on operator deployment, when AF 626 is considered a trusted entity, the network operator can allow AF 626 to interact directly with the relevant NF.
[0099] As previously discussed, CN 610 may include SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages from / to other entities, such as SMS-GMSC / IWMSC / SMS routers, to / from UE 602. SMS may also interact with AMF 612 and UDM 624 for notification procedures so that UE 602 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 624 when UE 602 is available for SMS).
[0100] System 600 may include the following service-based interfaces: Namf: a service-based interface presented by AMF; Nsmf: a service-based interface presented by SMF; Nnef: a service-based interface presented by NEF; Npcf: a service-based interface presented by PCF; Nudm: a service-based interface presented by UDM; Naf: a service-based interface presented by AF; Nnrf: a service-based interface presented by NRF; and Nausf: a service-based interface presented by AUSF.
[0101] System 600 may include the following reference points: N1: a reference point between UE and AMF; N2: a reference point between (R)AN and AMF; N3: a reference point between (R)AN and UPF; N4: a reference point between SMF and UPF; and N6: a reference point between UPF and data network. There may be more reference points and / or service-based interfaces between NF services in these NFs, however, these interfaces and reference points are omitted for clarity. For example, the NS reference point may be between PCF and AF; the N7 reference point may be between PCF and SMF; the N11 reference point may be between AMF and SMF, etc.; In some embodiments, CN 610 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 530) and AMF 612, so as to enable intercommunication between CN 610 and CN 528.
[0102] Despite Figure 6 Not shown, the system 600 may include multiple RAN nodes (such as (R)AN nodes 608), wherein an Xn interface is defined between two or more (R)AN nodes 608 (e.g., gNBs, etc.) connected to the 5GC 410, and an (R)AN node 608 (e.g., gNBs, etc.) connected to the CN 610 and an eNB (e.g., Figure 5 between macro RAN nodes 518), and / or between two eNBs connected to CN610.
[0103] In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 602 in connected mode (e.g., CM connection) includes functions for managing UE mobility in connected mode between one or more (R)AN nodes 608. Mobility support may include context transfer from an old (source) serving (R)AN node 608 to a new (target) serving (R)AN node 608; and control of a user plane tunnel between the old (source) serving (R)AN node 608 and the new (target) serving (R)AN node 608.
[0104] The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GTP-U layer for carrying user plane PDUs on top of a UDP and / or IP layer. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on an SCTP layer. The SCTP layer may be located on top of the IP layer. The SCTP layer provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.
[0105] Figure 7 Example components of a device 700 according to some embodiments are shown. In some embodiments, the device 700 may include an application circuit 702, a baseband circuit 704, a radio frequency (RF) circuit (shown as RF circuit 720), a front-end module (FEM) circuit (shown as FEM circuit 730), one or more antennas 732, and a power management circuit (PMC) (shown as PMC 734) (at least coupled together as shown). The components of the illustrated device 700 may be included in a UE or a RAN node. In some embodiments, the device 700 may include fewer elements (e.g., the RAN node cannot utilize the application circuit 702, but includes a processor / controller to process IP data received from the EPC). In some embodiments, the device 700 may include additional elements, such as a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the following components may be included in more than one device (e.g., the circuit may be separately included in more than one device for a cloud-RAN (C-RAN) specific implementation).
[0106] The application circuit 702 may include one or more application processors. For example, the application circuit 702 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The one or more processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include memory / storage devices, and may be configured to execute instructions stored in the memory / storage devices to enable various applications or operating systems to run on the device 700. In some embodiments, the processor of the application circuit 702 may process IP data packets received from the EPC.
[0107] The baseband circuit 704 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 704 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 720 and generate baseband signals for the transmit signal path of the RF circuit 720. The baseband circuit 704 may interact with the application circuit 702 to generate and process baseband signals and control the operation of the RF circuit 720. For example, in some embodiments, the baseband circuit 704 may include a third generation (3G) baseband processor (3G baseband processor 706), a fourth generation (4G) baseband processor (4G baseband processor 708), a fifth generation (5G) baseband processor (5G baseband processor 710), or other baseband processors 712 of other existing generations, generations under development or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 704 (e.g., one or more processors in the baseband processor) may handle various radio control functions that can communicate with one or more radio networks via the RF circuit 720. In other embodiments, some or all of the functions of the illustrated baseband processor may be included in a module stored in the memory 718 and executed via the central processing unit (CPU 714). Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 704 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 704 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.
[0108] In some embodiments, the baseband circuit 704 may include a digital signal processor (DSP), such as one or more audio DSPs 716. The audio DSP 716 may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 704 and the application circuit 702 may be implemented together, such as on a system on a chip (SOC).
[0109] In some embodiments, the baseband circuit 704 may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 704 may support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which the baseband circuit 704 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.
[0110] The RF circuit 720 may communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, the RF circuit 720 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 720 may include a receive signal path, which may include circuits for down-converting RF signals received from the FEM circuit 730 and providing baseband signals to the baseband circuit 704. The RF circuit 720 may also include a transmit signal path, which may include circuits for up-converting baseband signals provided by the baseband circuit 704 and providing an RF output signal for transmission to the FEM circuit 730.
[0111] In some embodiments, the receive signal path of the RF circuit 720 may include a mixer circuit 722, an amplifier circuit 724, and a filter circuit 726. In some embodiments, the transmit signal path of the RF circuit 720 may include a filter circuit 726 and a mixer circuit 722. The RF circuit 720 may also include a synthesizer circuit 728 for synthesizing frequencies used by the mixer circuit 722 of the receive signal path and / or the transmit signal path. In some embodiments, the mixer circuit 722 of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 730 based on the synthesized frequency provided by the synthesizer circuit 728. The amplifier circuit 724 may be configured to amplify the down-converted signal, and the filter circuit 726 may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 704 for further processing. In some embodiments, although this is not required, the output baseband signal may be a zero frequency baseband signal. In some embodiments, mixer circuit 722 of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.
[0112] In some embodiments, the mixer circuit 722 of the transmit signal path can be configured to up-convert an input baseband signal based on a synthesized frequency provided by the synthesizer circuit 728 to generate an RF output signal for the FEM circuit 730. The baseband signal can be provided by the baseband circuit 704 and can be filtered by the filter circuit 726.
[0113] In some embodiments, the mixer circuit 722 of the receive signal path and the mixer circuit 722 of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 722 of the receive signal path and the mixer circuit 722 of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 722 of the receive signal path and the mixer circuit 722 of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 722 of the receive signal path and the mixer circuit 722 of the transmit signal path may be configured for superheterodyne operation.
[0114] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 720 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 704 may include a digital baseband interface to communicate with the RF circuit 720.
[0115] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.
[0116] In some embodiments, synthesizer circuit 728 may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, but the scope of the embodiments is not limited in this regard, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 728 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.
[0117] The synthesizer circuit 728 may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer circuit 722 of the RF circuit 720. In some embodiments, the synthesizer circuit 728 may be a fractional-N / N+1 synthesizer.
[0118] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by baseband circuitry 704 or application circuitry 702 (such as an application processor) according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by application circuitry 702.
[0119] The synthesizer circuit 728 of the RF circuit 720 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a D-type flip-flop set. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
[0120] In some embodiments, the synthesizer circuit 728 can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 720 can include an IQ / polarity converter.
[0121] The FEM circuitry 730 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 732, amplify the receive signal, and provide an amplified version of the receive signal to the RF circuitry 720 for further processing. The FEM circuitry 730 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 720 for transmission by one or more of the one or more antennas 732. In various embodiments, amplification by either the transmit signal path or the receive signal path may be accomplished only in the RF circuitry 720, only in the FEM circuitry 730, or in both the RF circuitry 720 and the FEM circuitry 730.
[0122] In some embodiments, the FEM circuit 730 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 730 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 730 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 720). The transmit signal path of the FEM circuit 730 may include a power amplifier (PA) to amplify the input RF signal (e.g., provided by the RF circuit 720), and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 732).
[0123] In some embodiments, the PMC 734 can manage the power provided to the baseband circuit 704. Specifically, the PMC 734 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When the device 700 is capable of being powered by a battery, for example, when the device 700 is included in a UE, the PMC 734 can generally be included. The PMC 734 can improve power conversion efficiency while providing the desired specific implementation size and heat dissipation characteristics.
[0124] Figure 7PMC 734 is shown coupled only to baseband circuitry 704. However, in other embodiments, PMC 734 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuitry 702, RF circuitry 720, or FEM circuitry 730) and perform similar power management operations for these components.
[0125] In some embodiments, the PMC 734 may control or otherwise be part of various power saving mechanisms of the device 700. For example, if the device 700 is in the RRC_Connected state, where the device is still connected to the RAN node because it expects to receive traffic immediately, then after a period of inactivity, the device may enter a state known as discontinuous reception mode (DRX). During this state, the device 700 may be powered off for short time intervals, thereby saving power.
[0126] If there is no data traffic activity for an extended period of time, the device 700 may transition to the RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 700 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 700 cannot receive data in this state, and in order to receive data, the device must transition back to the RRC_Connected state.
[0127] An additional power saving mode can keep a device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.
[0128] The processor of the application circuit 702 and the processor of the baseband circuit 704 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 704 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 702 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.
[0129] Figure 8 An exemplary interface 800 of a baseband circuit according to some embodiments is shown. As described above, Figure 7 The baseband circuit 704 may include a 3G baseband processor 706, a 4G baseband processor 708, a 5G baseband processor 710, other baseband processors 712, a CPU 714, and a memory 718 for use by the processors. As shown, each of the processors may include a corresponding memory interface 802 for sending / receiving data to / from the memory 718.
[0130] The baseband circuit 704 may also include one or more interfaces to communicatively couple to other circuits / devices, such as a memory interface 804 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 704), an application circuit interface 806 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 704), and an application circuit interface 807 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 704). Figure 7 The application circuit 702 sends / receives data), the RF circuit interface 808 (for example, for sending / receiving data to / from the application circuit 702), Figure 7 an interface for sending / receiving data to / from a RF circuit 720), a wireless hardware connection interface 810 (e.g., for sending / receiving data to / from a near field communication (NFC) component, Components (e.g. Low Energy), components and other communication components to send / receive data) and a power management interface 812 (for example, an interface for sending / receiving power or control signals to / from PMC 734).
[0131] Fig. 9 is a block diagram illustrating a component 900 capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of performing any one or more of the methods discussed herein, according to some example embodiments. Specifically, Fig. 9 A schematic diagram of hardware resources 902 is shown, which includes one or more processors 912 (or processor cores), one or more memory / storage devices 918, and one or more communication resources 920, each of which can be communicatively coupled via a bus 922. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 904 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 902.
[0132] Processor 912 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 914 and processor 916.
[0133] The memory / storage device 918 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 918 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.
[0134] The communication resources 920 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 906 or one or more databases 908 via the network 910. For example, the communication resources 920 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Components (e.g. Low power consumption), components and other communication components.
[0135] The instructions 924 may include software, programs, applications, applets, applications, or other executable code for causing at least any one of the processors 912 to perform any one or more of the methodologies discussed herein. The instructions 924 may reside completely or partially in at least one of the processors 912 (e.g., in a cache memory of the processor), the memory / storage device 918, or any suitable combination thereof. In addition, any portion of the instructions 924 may be transmitted to the hardware resources 902 from any combination of the peripheral devices 906 or the database 908. Thus, the memory of the processor 912, the memory / storage device 918, the peripheral devices 906, and the database 908 are examples of computer-readable and machine-readable media.
[0136] V. Additional Examples
[0137] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.
[0138] The following examples relate to further embodiments.
[0139] Example 1 is an apparatus for a user equipment (UE), the apparatus comprising a memory interface and a processor. The memory interface is used to send or receive data corresponding to a hybrid automatic repeat request (HARQ) feedback to or from a memory device. The processor is used to: process repetitions of a physical downlink shared channel (PDSCH) transmission; determine a minimum number of repetitions used by the UE to decode the PDSCH transmission; and generate the HARQ feedback in response to the PDSCH transmission, the HARQ feedback indicating the minimum number of repetitions used by the UE to decode the PDSCH transmission.
[0140] Example 2 is an apparatus according to Example 1, wherein the processor is further configured to: determine that four or more repetitions have been scheduled for the PDSCH transmission; in response to the determination that the four or more repetitions have been scheduled for the PDSCH transmission, generate the HARQ feedback using HARQ value mapping, the HARQ value mapping including: a HARQ value 0 for indicating a negative acknowledgement (NACK); a HARQ value 1 for indicating an acknowledgement (ACK), the ACK being for at most one quarter of the repetitions used by the UE to decode the PDSCH transmission; a HARQ value 2 for indicating an ACK, the ACK being for at most one half of the repetitions used by the UE to decode the PDSCH transmission; and a HARQ value 3 for indicating an ACK, the ACK being for more than half of the repetitions used by the UE to decode the PDSCH transmission.
[0141] Example 3 is an apparatus according to Example 2, wherein the processor is further configured to configure the UE with at least four physical uplink control channel (PUCCH) sequences corresponding to different HARQ values, respectively.
[0142] Example 4 is an apparatus according to Example 2, wherein generating the HARQ feedback includes generating a physical uplink control channel (PUCCH) format 0 sequence, wherein m defines a cyclic shift value, and wherein: m=0 corresponds to the HARQ value 0; m=3 corresponds to the HARQ value 1; m=6 corresponds to the HARQ value 2; and m=9 corresponds to the HARQ value 3.
[0143] Example 5 is an apparatus according to Example 1, wherein the processor is further configured to generate the HARQ feedback using a HARQ value mapping, the HARQ value mapping comprising: a HARQ value 0 for indicating a negative acknowledgement (NACK); a HARQ value 1 for indicating an acknowledgement (ACK), the ACK being for at most half of the repetitions used by the UE to decode the PDSCH transmission; and a HARQ value 2 for indicating an ACK, the ACK being for more than half or all of the repetitions used by the UE to decode the PDSCH transmission.
[0144] Example 6 is an apparatus according to Example 5, wherein the processor is further configured to configure the UE with three physical uplink control channel (PUCCH) sequences corresponding to different HARQ values, respectively.
[0145] Example 7 is an apparatus according to Example 5, wherein generating the HARQ feedback includes generating a physical uplink control channel (PUCCH) format 0 sequence, wherein m defines a cyclic shift value, and wherein: m=0 corresponds to the HARQ value 0; m=4 corresponds to the HARQ value 1; and m=8 corresponds to the HARQ value 2.
[0146] Example 8 is an apparatus according to Example 1, wherein the PDSCH transmission is configured for PDSCH data mapping type B so that the scheduled PDSCH is not aligned with a time slot boundary, wherein the processor is further configured to determine the scheduled PDSCH with repetitions by scheduling a single PDSCH based on a physical downlink control channel (PDCCH) based on a micro-slot, and the single PDSCH spans multiple micro-slots corresponding to a total duration of multiple repetitions.
[0147] Example 9 is an apparatus according to Example 1, wherein the processor is further configured to process a radio resource control (RRC) signal to determine whether to enable the HARQ feedback to use the repeated multiple values for the PDSCH.
[0148] Example 10 is an apparatus according to Example 9, wherein processing the RRC signal includes determining an RRC parameter indicating use of one of 2-value HARQ feedback, 3-value HARQ feedback, and 4-value HARQ feedback corresponding to 1-bit HARQ feedback.
[0149] Example 11 is an apparatus according to Example 1, wherein the processor is further configured to: process a radio resource control (RRC) signal from a base station to determine a maximum number of repetitions for a scheduled data transmission; generate channel state information (CSI) for the base station; and determine an actual number of repetitions used by the base station based on the CSI for the scheduled data transmission, wherein the actual number of repetitions does not exceed the maximum number of repetitions.
[0150] Example 12 is an apparatus according to Example 11, wherein determining the actual number of repetitions comprises processing a physical downlink control channel (PDCCH) that schedules the data transmission.
[0151] Example 13 is an apparatus according to Example 11, wherein determining the actual number of repetitions comprises decoding downlink control information (DCI) indicating the actual number of repetitions.
[0152] Example 14 is an apparatus according to Example 13, wherein the processor is further configured to use a single DCI bit to determine the actual number of repetitions, wherein a first value of the single DCI bit indicates using half of the maximum number of repetitions, and wherein a second value of the single DCI bit indicates using the maximum number of repetitions.
[0153] Example 15 is an apparatus according to Example 13, wherein the processor is further configured to determine the actual number of repetitions using a 2-bit repetition field in the DCI, wherein a first value of the 2-bit repetition field indicates using one quarter of the maximum number of repetitions, a second value of the 2-bit repetition field indicates using half of the maximum number of repetitions, and a third value of the 2-bit repetition field indicates using the maximum number of repetitions.
[0154] Example 16 is a computer-readable storage medium comprising instructions which, when executed by a processor of a node in a wireless network, causes the processor to: schedule a first physical downlink shared channel (PDSCH) transmission having a first number of repetitions for a user equipment (UE); process hybrid automatic repeat request (HARQ) feedback from the UE corresponding to the first PDSCH transmission; determine a second number of repetitions used by the UE to decode the first PDSCH transmission based on the HARQ feedback; and schedule a second PDSCH transmission for the UE based on the second number of repetitions.
[0155] Example 17 is a computer-readable storage medium according to example 16, wherein the HARQ feedback indicates that the second number is one of one quarter of the first number, half of the first number, or equal to the first number.
[0156] Example 18 is a computer-readable storage medium according to Example 16, wherein the HARQ feedback includes a physical uplink control channel (PUCCH) format 0, the PUCCH format 0 including a cyclic shift corresponding to the second value.
[0157] Example 19 is a computer-readable storage medium according to Example 16, wherein the instructions further configure the processor to: generate a radio resource control (RRC) signal to enable the UE to use multi-value HARQ acknowledgement (ACK) feedback for a PDSCH with repetitions.
[0158] Example 20 is a computer-readable storage medium according to Example 19, wherein the RRC signal includes an RRC parameter indicating the use of one of 2-value HARQ feedback, 3-value HARQ feedback, and 4-value HARQ feedback corresponding to 1-bit HARQ feedback.
[0159] Example 21 is a computer-readable storage medium according to Example 16, wherein the instructions further configure the processor to: generate a radio resource control (RRC) signal to indicate to the UE a maximum number of repetitions of scheduled data transmission; process channel state information (CSI) from the UE; and determine, based on the CSI, an actual number of repetitions of the scheduled data transmission.
[0160] Example 22 is a computer-readable storage medium according to Example 21, wherein the instructions further configure the processor to generate a physical downlink control channel (PDCCH) to schedule the data transmission, wherein the PDCCH indicates the actual number of repetitions.
[0161] Example 23 is a computer-readable storage medium according to Example 22, wherein the instructions further configure the processor to generate downlink control information (DCI) indicating the actual number of repetitions.
[0162] Example 24 is a computer-readable storage medium according to Example 23, wherein the DCI includes a single DCI bit for indicating the actual number of repetitions, wherein a first value of the single DCI bit indicates using half of the maximum number of repetitions, and wherein a second value of the single DCI bit indicates using the maximum number of repetitions.
[0163] Example 25 is a computer-readable storage medium according to Example 23, wherein the DCI includes a 2-bit repetition field for indicating the actual number of repetitions, wherein a first value of the 2-bit repetition field indicates that one quarter of the maximum number of repetitions is used, a second value of the 2-bit repetition field indicates that half of the maximum number of repetitions is used, and a third value of the 2-bit repetition field indicates that the maximum number of repetitions is used.
[0164] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.
[0165] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters / attributes / aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters / attributes / aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters / attributes / aspects, etc. may be combined with or substituted for parameters / attributes, etc. of another embodiment.
[0166] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways of implementing both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be regarded as illustrative rather than restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Claims
1. A device for a user equipment UE, the device comprising: a memory interface, the memory interface being used to send or receive data corresponding to a hybrid automatic repeat request (HARQ) feedback to or from a memory device; and A processor, the processor being configured to: Handling repetition of Physical Downlink Shared Channel (PDSCH) transmissions; determining a minimum number of repetitions for use by the UE to decode the PDSCH transmission; and generating the HARQ feedback in response to the PDSCH transmission, the HARQ feedback indicating the minimum number of repetitions used by the UE to decode the PDSCH transmission; The HARQ feedback is a multi-value HARQ feedback generated using a multi-value HARQ mapping, and the multi-value HARQ mapping includes: A HARQ value of 0 indicating a negative acknowledgement NACK; and At least two non-zero HARQ values are used to indicate an acknowledgement ACK, and the ACK indicated by each non-zero HARQ value is a different proportional value of the number of repetitions of the PDSCH transmission used by the UE to decode the PDSCH transmission.
2. The apparatus of claim 1, wherein the processor is further configured to: determining that four or more repetitions have been scheduled for the PDSCH transmission; and In response to the determining that the four or more repetitions have been scheduled for the PDSCH transmission, generating the HARQ feedback using a HARQ value mapping, the HARQ value mapping comprising: HARQ value 0 used to indicate NACK; a HARQ value of 1 for indicating an ACK, the ACK indicated by the HARQ value 1 being used by the UE to decode the PDSCH transmission for at most one quarter of the number of repetitions; a HARQ value of 2 for indicating an ACK, the ACK indicated by the HARQ value 2 being used by the UE to decode the PDSCH transmission for at most half of the number of repetitions; and A HARQ value of 3 is used to indicate an ACK, and the ACK indicated by the HARQ value 3 is used by the UE to decode the PDSCH transmission for more than half of the repetition number.
3. The apparatus of claim 2, wherein the processor is further configured to configure the UE with at least four physical uplink control channel (PUCCH) sequences respectively corresponding to different HARQ values.
4. The apparatus of claim 2, wherein generating the HARQ feedback comprises generating a Physical Uplink Control Channel (PUCCH) format 0 sequence, wherein m defines a cyclic shift value, and wherein: m=0 corresponds to the HARQ value 0; m=3 corresponds to the HARQ value 1; m=6 corresponds to the HARQ value 2; and m=9 corresponds to the HARQ value 3.
5. The apparatus of claim 1 , wherein the processor is further configured to generate the HARQ feedback using a HARQ value mapping, the HARQ value mapping comprising: HARQ value 0 used to indicate NACK; a HARQ value of 1 for indicating an ACK, the ACK indicated by the HARQ value 1 being used by the UE to decode the PDSCH transmission for at most half of the number of repetitions; and A HARQ value of 2 is used to indicate an ACK, and the ACK indicated by the HARQ value 2 is used by the UE to decode the PDSCH transmission for more than half or all of the repetition times. 6 . The apparatus of claim 5 , wherein the processor is further configured to configure the UE with three physical uplink control channel (PUCCH) sequences respectively corresponding to different HARQ values.
7. The apparatus of claim 5, wherein generating the HARQ feedback comprises generating a Physical Uplink Control Channel (PUCCH) format 0 sequence, wherein m defines a cyclic shift value, and wherein: m=0 corresponds to the HARQ value 0; m=4 corresponds to the HARQ value 1; and m=8 corresponds to the HARQ value 2.
8. An apparatus according to claim 1, wherein the PDSCH transmission is configured for PDSCH data mapping type B so that the scheduled PDSCH is not aligned with a time slot boundary, wherein the processor is further configured to determine the scheduled PDSCH with repetitions by scheduling a single PDSCH based on a physical downlink control channel (PDCCH) based on a micro-slot, and the single PDSCH spans multiple micro-slots corresponding to a total duration of multiple repetitions.
9. The apparatus of claim 1, wherein the processor is further configured to process a radio resource control (RRC) signal to determine whether to enable the HARQ feedback to use the repeated multiple values for the PDSCH transmission.
10. The apparatus of claim 9, wherein processing the RRC signal comprises determining an RRC parameter indicating use of one of 3-value HARQ feedback, 4-value HARQ feedback, and 2-value HARQ feedback corresponding to 1-bit HARQ feedback.
11. The apparatus of claim 1 , wherein the processor is further configured to: processing a radio resource control (RRC) signal from a base station to determine a maximum number of repetitions of a scheduled data transmission; Generate channel state information CSI for the base station; as well as An actual number of repetitions used by the base station is determined based on the CSI for the scheduled data transmission, wherein the actual number of repetitions does not exceed the maximum number of repetitions.
12. The apparatus of claim 11, wherein determining the actual number of repetitions comprises processing a physical downlink control channel (PDCCH) that schedules the data transmission.
13. The apparatus of claim 11, wherein determining the actual number of repetitions comprises decoding downlink control information (DCI) indicating the actual number of repetitions.
14. The apparatus of claim 13, wherein the processor is further configured to determine the actual number of repetitions using a single DCI bit, wherein a first value of the single DCI bit indicates using half of the maximum number of repetitions, and wherein a second value of the single DCI bit indicates using the maximum number of repetitions.
15. The apparatus of claim 13, wherein the processor is further configured to determine the actual number of repetitions using a 2-bit repetition field in the DCI, wherein a first value of the 2-bit repetition field indicates using one quarter of the maximum number of repetitions, a second value of the 2-bit repetition field indicates using half of the maximum number of repetitions, and a third value of the 2-bit repetition field indicates using the maximum number of repetitions.
16. A computer-readable storage medium comprising instructions that, when executed by a processor of a node in a wireless network, cause the processor to: Scheduling a first physical downlink shared channel (PDSCH) transmission with a first repetition number for a user equipment (UE); Processing a hybrid automatic repeat request (HARQ) feedback corresponding to the first PDSCH transmission from the UE; determining, based on the HARQ feedback, a second number of repetitions for decoding the first PDSCH transmission by the UE; as well as Scheduling a second PDSCH transmission for the UE based on the second number of repetitions; in, The HARQ feedback is a multi-value HARQ feedback generated using a multi-value HARQ mapping, and the multi-value HARQ mapping includes: A HARQ value of 0 is used to indicate a negative acknowledgement NACK; as well as At least two non-zero HARQ values are used to indicate an acknowledgement ACK, and the ACK indicated by each non-zero HARQ value is a different proportional value of the first repetition number used by the UE to decode the first PDSCH transmission.
17. The computer-readable storage medium of claim 16, wherein the HARQ feedback indicates that the second repetition number is one of one quarter of the first repetition number, half of the first repetition number, or equal to the first repetition number.
18. The computer-readable storage medium of claim 16, wherein the HARQ feedback comprises a Physical Uplink Control Channel (PUCCH) format 0, the PUCCH format 0 comprising a cyclic shift corresponding to a HARQ value of the HARQ feedback.
19. The computer-readable storage medium of claim 16, wherein the instructions further configure the processor to generate a radio resource control (RRC) signal to enable the UE for multi-value HARQ ACK feedback for a PDSCH with repetitions.
20. The computer-readable storage medium of claim 19, wherein the RRC signal comprises an RRC parameter indicating use of one of 3-value HARQ feedback, 4-value HARQ feedback, and 2-value HARQ feedback corresponding to 1-bit HARQ feedback.
21. The computer-readable storage medium of claim 16, wherein the instructions further configure the processor to: generating a radio resource control (RRC) signal to indicate to the UE a maximum number of repetitions of scheduled data transmission; processing channel state information CSI from the UE; and Based on the CSI, an actual number of repetitions of the scheduled data transmission is determined.
22. The computer-readable storage medium of claim 21, wherein the instructions further configure the processor to generate a physical downlink control channel (PDCCH) to schedule the data transmission, wherein the PDCCH indicates the actual number of repetitions.
23. The computer-readable storage medium of claim 22, wherein the instructions further configure the processor to generate downlink control information (DCI) indicating the actual number of repetitions.
24. The computer-readable storage medium of claim 23, wherein the DCI comprises a single DCI bit for indicating the actual number of repetitions, wherein a first value of the single DCI bit indicates that half of the maximum number of repetitions is used, and wherein a second value of the single DCI bit indicates that the maximum number of repetitions is used.
25. A computer-readable storage medium according to claim 23, wherein the DCI includes a 2-bit repetition field for indicating the actual number of repetitions, wherein a first value of the 2-bit repetition field indicates that one quarter of the maximum number of repetitions is used, a second value of the 2-bit repetition field indicates that half of the maximum number of repetitions is used, and a third value of the 2-bit repetition field indicates that the maximum number of repetitions is used.
Citation Information
Patent Citations
Multiplexing control and data information from a User Equipment in a physical data channel
AU2014201577A1
Determining timing for transmission or reception of signaling in a coverage enhanced operating mode
CN105850058A
Apparatus and method for handling configuration of bundle sizes in communications involving transmission and / or reception of more than one bundle in transmission and / or reception attempt
CN107624227A
Transmission repetition reduction in a wireless communication system
WO2017031675A1
