Flexible uplink control information (UCI) transmission using a physical uplink sharing channel (PUSCH).

Abstract

Various embodiments herein are directed to uplink control information (UCI) transmitted along with a physical uplink shared channel (PUSCH). Other embodiments may be disclosed or claimed.

Description

Technical Field

[0001] Various embodiments may generally relate to the field of wireless communication. For example, some embodiments may relate to uplink control information (UCI) transmitted with a physical uplink shared channel (PUSCH).

Background Art

[0002] Cross-reference of related applications This application claims the priority of U.S. Provisional Patent Application No. 63 / 155,218, filed on March 1, 2021, and U.S. Provisional Patent Application No. 63 / 161,338, filed on March 15, 2021.

[0003] Background technology Mobile communication has evolved significantly from the early voice systems to today's highly sophisticated integrated communication platforms. The next-generation wireless communication system, 5G, or New Radio (NR), provides access to information and sharing of data anywhere and at any time for various users and applications. NR is expected to be a unified network / system that aims to meet significantly different and sometimes competing performance dimensions and services. Such diverse multi-dimensional requirements are driven by different services and applications. Generally, NR evolves based on 3GPP (registered trademark) LTE-Advanced, along with further potential new radio access technologies (RATs), to enrich people's lives with better, simpler, and seamless wireless connectivity solutions. NR enables everything to be wirelessly connected and delivers high-speed and rich content and services.

Brief Description of the Drawings

[0004] Embodiments will be readily apparent from the following detailed description in conjunction with the accompanying drawings. For the sake of this description, similar reference numerals indicate similar structural elements. Embodiments are shown in the figures of the accompanying drawings as examples, not as limitations. [Figure 1] This shows an example of a front-loaded UCI transmission on PUSCH using various embodiments. [Figure 2] This shows examples of UCI transmission on PUSCH using various embodiments. [Figure 3] Examples of various embodiments for UCI transmission in conjunction with PUSCH are shown. [Figure 4] Examples of various embodiments for UCI transmission in conjunction with PUSCH are shown. [Figure 5] Examples of various embodiments for UCI transmission in conjunction with PUSCH are shown. [Figure 6] Examples of various embodiments for UCI transmission in conjunction with PUSCH are shown. [Figure 7] Examples of various embodiments for UCI transmission in conjunction with PUSCH are shown. [Figure 8] A schematic diagram of wireless networks according to various embodiments is shown. [Figure 9] The components of a wireless network according to various embodiments are schematically shown. [Figure 10] This block diagram shows components according to several exemplary embodiments that can read instructions from a computer-readable medium (e.g., a non-temporary machine-readable storage medium) and perform any one or more of the methods described herein. [Figure 11] Examples of procedures for carrying out the various embodiments described herein are provided. [Figure 12] Examples of procedures for carrying out the various embodiments described herein are provided. [Figure 13] Examples of procedures for carrying out the various embodiments described herein are provided. [Modes for carrying out the invention]

[0005] The following detailed description refers to the accompanying drawings. The same reference numeral may be used in different drawings to identify elements of the same reference numeral. In the following description, certain details such as specific structures, architectures, interfaces, and techniques are described for illustrative purposes only, not limiting purposes, to provide a complete understanding of the various aspects of the various embodiments. However, it will be apparent to those skilled in the art who are interested in this disclosure that various aspects of the various embodiments may be implemented in other examples that deviate from these specific details. In some examples, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary details. For the purposes of this specification, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).

[0006] In some embodiments, uplink control information (UCI) may be carried by a physical uplink shared channel (PUSCH) transmission. In particular, the UCI may include one or more of the following: scheduling requests (SR), hybrid automatic retransmission request-acknowledgment (HARQ-ACK) feedback, channel status information (CSI) reports, e.g., channel quality indicator (CQI), precoding matrix indicator (PMI), CSI resource indicator (CRI) and rank indicator (RI), and / or beam-related information (e.g., L1-RSRP (Layer 1-reference signal received power)). The UCI on PUSCH is generally transmitted at the beginning of a PUSCH transmission and co-located with front-loaded DM-RS symbols. Figure 1 shows an example of a “front-loaded” UCI transmission in conjunction with PUSCH.

[0007] The Rel-15 NR supports aperiodic CSI-RS triggering using the UL DCI format. More specifically, the DCI can indicate triggering of aperiodic CSI-RS transmissions in the DL, CSI reporting in the UL, and PUSCH transmissions. As shown in Figure 2, when CSI-RS is used for beam management, the minimum duration of beamSwitchTimming (measured in absolute time quantized by the symbol or DFT-s-OFDM symbol duration) between the last symbol of the PDCCH and the first symbol of the CSI-RS should be provided to the UE. This time can be used by the UE for PDCCH decoding and application of the DCI-indicated beam for CSI-RS reception.

[0008] In addition to beamSwitchTimming, the UE should also be given at least Z' symbols between the last symbol of the CSI-RS and the first symbol of the UCI. The above duration is used for the preparation of the CSI-RS measurement and UCI report. Due to the above processing timeline and possibly flexible CSI-RS transmission in the DL portion, it is difficult to guarantee front-loaded DM-RS transmission.

[0009] Conventional standards and techniques only support front-loaded UCI transmissions, and these existing methods are very limited and may impose some constraints on PUSCH scheduling flexibility to ensure that all processing timelines are met. Various embodiments herein address these and other issues by providing systems and methods for flexible UCI transmission over PUSCH using UL-SCH multiplexing, where the UCI may be transmitted in different parts of the uplink transmission.

[0010] In some embodiments, a CBB (Code Block Bundle) is a set of OFDM symbols containing an integer number of code blocks. This is used to facilitate efficient processing at the receiver. In some embodiments, the CBB size (DFT-s-OFDM symbol count) has a fixed size for a given PUSCH transmission and can take values ​​of 1, 2, 4, or 8.

[0011] In one embodiment, UCI transmission on a push (which also carries UL-SCH) is performed in a first DFT-s-OFDM symbol that satisfies UE capability for Z' and Z, taking into account the CBB boundary. An example of a corresponding embodiment is shown in Figure 3, where a CBB of size 2 is shown and UCI is transmitted between two adjacent CBBs. Furthermore, the UCI transmission may puncture the UL-SCH on the push, or the UL-SCH may be rate-matched around the UCI transmission. In this case, some DFT-s-OFDM symbols within the CBB may be used for UCI transmission. The same applies to other embodiments.

[0012] In another example of this embodiment, an additional DM-RS symbol for UCI may be transmitted within a symbol adjacent to UCI (e.g., one preceding UCI). An example of a corresponding embodiment is shown in Figure 4. If the additional DM-RS overlaps with a DM-RS symbol for UL-SCH transmission, this additional DM-RS symbol is skipped.

[0013] In one embodiment, the UCI transmission is performed after the first DM-RS symbol of PUSCH that satisfies UE capability for Z' and Z, taking into account the CBB boundary. An example of a corresponding embodiment is shown in Figure 5.

[0014] In one embodiment, the UCI transmission may be postponed until the end of the UL portion of the TDD period, or in the final portion of the PUSCH transmission after UL-SCH. An example of a corresponding embodiment is shown in Figure 6.

[0015] In one embodiment, UCI transmission can be deferred until the next TDD period. In such an embodiment, UCI transmission can be based on the front loaded or other techniques proposed in the above embodiments. An example of a corresponding embodiment is shown in FIG. 7.

[0016] In some embodiments, the reception of UCI can be acknowledged by the receiving gNB. More specifically, UCI can be regarded as a special code block bundle (CBB). The corresponding CBB can be assigned a HARQ process number to enable the identification of UCI transmission. Then, the corresponding UCI transmission can be acknowledged by the gNB in another DCI. In such an embodiment, if the DCI that acknowledges the UCI transmission is not received within a certain time period after the UCI transmission, the UCI (e.g., beam indication) is considered inapplicable. In another example of this embodiment, if the UCI transmission is received within a certain time period after the UCI transmission, the UCI (including, for example, the preferred beam indicated by the CRI index of the CSI-RS resource) is considered applicable to all channel transmissions (PDSCH, PUSCH) after a predetermined time.

[0017] In another example, a dedicated CSI triggering state for the CSI triggering field in DCI can be used to acknowledge UCI transmission. For example, if a DCI is transmitted and includes a CSI field set to a predetermined specific value, the corresponding UCI can be considered to have been correctly received or not correctly received by the gNB. If the UCI is acknowledged by the gNB, the preferred beam measured in CSI-RS and indicated by the UE in the UCI is considered applicable to other physical channels (PDSCH, PUSCH) after a predetermined time interval.

[0018] System and Implementation Figures 8 to 9 show various systems, devices, and components that can implement aspects of the disclosed embodiments.

[0019] Figure 8 shows a network 800 according to various embodiments. The network 800 can operate in a manner consistent with 3GPP technical specifications for an LTE or 5G / NR system. However, the exemplary embodiments are not limited in this regard, and the described embodiments can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems.

[0020] The network 800 can include a UE 802 that can include any mobile or non-mobile computing device designed to communicate with the RAN 804 via an over-the-air connection. The UE 802 can be communicatively coupled to the RAN 804 by means of a Uu interface. The UE 802 can be, but is not limited to, a smartphone, a tablet computer, a wearable computer device, a desktop computer, a laptop computer, an in-vehicle infotainment, an in-vehicle entertainment device, an instrument cluster, a head-up display device, an on-vehicle diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a network appliance, a machine-type communication device, an M2M or D2D device, an IoT device, etc.

[0021] In some embodiments, the network 800 can include a plurality of UEs directly coupled to each other via a sidelink interface. The UEs can be, but are not limited to, M2M / D2D devices that communicate using physical sidelink channels such as PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0022] In some embodiments, the UE802 may further communicate with the AP806 via an over-the-air connection. The AP806 can manage the WLAN connection, which can work to offload some / all network traffic from the RAN804. The connection between the UE802 and the AP806 may conform to any IEEE 802.11 protocol, and the AP806 may be a Wireless Fidelity (Wi-Fi®) router. In some embodiments, the UE802, RAN804, and AP806 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve the UE802 being configured by the RAN804 to utilize both cellular radio resources and WLAN resources.

[0023] RAN804 may include one or more access nodes, such as AN808. AN808 may terminate the air interface protocol for UE802 by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN808 can enable data / voice connectivity between CN820 and UE802. In some embodiments, AN808 may be implemented as one or more software entities operating on a server computer in a separate device or as part of a virtual network which may be called CRAN or virtual baseband unit pool. AN808 may be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN808 may be a macrocell base station or low-power base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0024] In embodiments where RAN804 includes multiple ANs, they may be coupled to each other via an X2 interface (if RAN804 is an LTE RAN) or an Xn interface (if RAN804 is a 5G RAN). In some embodiments, the X2 / Xn interface may be separated into a control / user plane interface, which may allow ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0025] Each AN of RAN804 can manage one or more cells, cell groups, component carriers, etc., for example, to provide an air interface for network access to UE802. UE802 may be connected simultaneously to multiple cells provided by the same or different ANs of RAN804. For example, UE802 and RAN804 may use carrier aggregation to enable UE802 to connect to multiple component carriers, each corresponding to a Pcell or Scell. In a dual-connection scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second ANs may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0026] The RAN804 may provide an air interface via an authorized or unauthorized spectrum. To operate in an unauthorized spectrum, the node may use LAA, ELaA, and / or feLAA mechanisms based on carrier aggregation techniques using PCell / SCell. Prior to accessing an unauthorized spectrum, the node may perform medium / carrier sensing operations based, for example, on a listen-before-talk (LBT) protocol.

[0027] In a V2X scenario, UE802 or AN808 can be or act as an RSU, referring to any transport infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable AN or stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be called a “UE-type RSU,” an RSU implemented in or by an eNB may be called an “eNB-type RSU,” an RSU implemented in or by a gNB may be called a “gNB-type RSU,” and so on. In one example, an RSU is a computing device coupled to a radio frequency circuit located on the roadside, providing connectivity support to a passing vehicle UE. An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling oncoming vehicle and pedestrian traffic. An RSU can provide very low latency communication required for high-speed events such as collision avoidance and traffic warnings. As an addition or alternative, an RSU may provide other cellular / WLAN communication services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing wired connectivity (e.g., Ethernet®) to a traffic signal controller or backhaul network.

[0028] In some embodiments, RAN804 may be an LTE RAN810 having an eNB, eNB812, for example. The LTE RAN810 can provide an LTE air interface having the following characteristics: 15kHz SCS, CP-OFDM waveforms for DL ​​and SC-FDMA waveforms for UL; turbo code for data and TBCC for control, etc. The LTE air interface may rely on a CSI-RS for CSI acquisition and beam management; a PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and a CRS for channel estimation for cell discovery and initial acquisition, channel quality measurement, and coherent demodulation / detection at the UE. The LTE air interface may operate in the sub-6GHz band.

[0029] In some embodiments, the RAN804 may be an NG-RAN814 having a gNB, e.g., gNB816, or an ng-eNB, e.g., ng-eNB818. The gNB816 can connect to a 5G-enabled UE using a 5G NR interface. The gNB816 can connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB818 can also connect to the 5G core via an NG interface, but can also connect to the UE via an LTE air interface. The gNB816 and ng-eNB818 can connect to each other via an Xn interface.

[0030] In some embodiments, the NG interface may be divided into two parts: an NG user plane (NG-U) interface that carries traffic data between the NG-RAN814 node and the UPF848 (e.g., the N3 interface), and an NG control plane (NG-C) interface that is a signaling interface between the NG-RAN814 node and the AMF844 (e.g., the N2 interface).

[0031] NG-RAN814 can provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to an LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and a tracking reference signal for time tracking. The 5G-NR air interface may operate on the FR1 band, including the sub-6GHz band, or the FR2 band, including the 24.25GHz to 52.6GHz band. The 5G-NR air interface may include SSB, which is an area of ​​the downlink resource grid including PSS / SSS / PBCH.

[0032] In some embodiments, a 5G-NR air interface can utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCSs. For instance, UE802 may consist of multiple BWPs, each with a different SCS. When a BWP change is indicated to UE802, the SCS for transmission is also changed. Another example of a use case for BWPs relates to power saving. In particular, multiple BWPs can be configured for UE802 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. BWPs with fewer PRBs can be used for data transmission with low traffic loads, allowing power saving in UE802 and possibly in gNB816. BWPs with more PRBs can be used for scenarios with higher traffic loads.

[0033] RAN804 is communicatively coupled to CN820, which includes network elements for providing customers / subscribers (e.g., users of UE802) with various functions to support data and telecommunications services. The components of CN820 may be implemented on one physical node or separate physical nodes. In some embodiments, NFV may be used to virtualize some or all of the functions provided by the network elements of CN820 onto physical computing / storage resources such as servers, switches, etc. Logical instantiations of CN820 may be referred to as network slices, and some logical instantiations of CN820 may be referred to as network subslices.

[0034] In some embodiments, CN820 may be LTE CN822, sometimes referred to as EPC. LTE CN822 may include MME824, SGW826, SGSN828, HSS830, PGW832, and PCRF834 coupled to one another via an interface (or “reference point”) as shown in the figure. A brief description of the function of each component of LTE CN822 is as follows:

[0035] The MME824 can implement mobility management features to track the current location of the UE802, facilitating paging, bearer activation / deactivation, handover, gateway selection, authentication, and more.

[0036] The SGW826 terminates the S1 interface toward the RAN and can route data packets between the RAN and the LTE CN822. The SGW826 may also be a local mobility anchor point for handover between RAN nodes and may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, billing, and certain policy enforcement.

[0037] The SGSN828 can track the location of the UE802 and perform security functions and access control. Furthermore, the SGSN828 can perform EPC node-to-node signaling for mobility between different RAT networks, PDN and S-GW selection specified by the MME824, MME selection for handover, etc. An S3 reference point between the MME824 and the SGSN828 can enable user and bearer information exchange for mobility between 3GPP access networks in idle / active states.

[0038] The HSS830 may include a database for network users, containing join-related information to support the processing of network entities in communication sessions. The HSS830 can provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. An S6a reference point between the HSS830 and the MME824 may enable the transfer of join and authentication data for authenticating / authorizing user access to the LTE CN820.

[0039] PGW832 may terminate an SGi interface toward a data network (DN) 836, which may include an application / content server 838. PGW832 may route data packets between the LTE CN 822 and the data network 836. PGW832 may be coupled with SGW826 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW832 may further include nodes (e.g., PCEF) for policy enforcement and billing data collection. In addition, the SGi reference point between PGW832 and the data network 836 may be, for example, an external public, private PDN, or intra-operator packet data network for providing IMS services. PGW832 may be coupled with PCRF834 via a Gx reference point.

[0040] PCRF834 is the policy and billing control element of LTE CN822. PCRF834 can be communicatively coupled to the app / content server 838 to determine appropriate QoS and billing parameters for the service flow. PCRF832 can provision associated rules to the PCEF (via the Gx reference point) along with appropriate TFT and QCI.

[0041] In some embodiments, CN820 may be 5GC840. 5GC840 may include AUSF842, AMF844, SMF846, UPF848, NSSF850, NEF852, NRF854, PCF856, UDM858, and AF860 coupled to one another via interfaces (or “reference points”) as shown in the figure. A brief description of the function of each component of 5GC840 is as follows:

[0042] The AUSF842 can store data for authentication of the UE802 and handle authentication-related functions. The AUSF842 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC840 via reference points as illustrated, the AUSF842 can present a Nausf service-based interface.

[0043] The AMF844 may enable other functions of the 5GC840 to communicate with the UE802 and RAN804 and subscribe to notifications about mobility events concerning the UE802. The AMF844 may be responsible for registration management (e.g., for registering the UE802), connectivity management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF844 may provide transport for SM messages between the UE802 and SMF846 and may act as a transparent proxy for routing SM messages. The AMF844 may also provide transport for SMS messages between the UE802 and SMSF. The AMF844 can interact with the AUSF842 and UE802 to perform various security anchor and context management functions. Furthermore, the AMF844 may include, or may be, an N2 reference point between the RAN804 and the AMF844, and may be the endpoint of the RANCP interface, and may be the endpoint of NAS(N1) signaling, and may perform NAS encryption and integrity protection. The AMF844 may also support NAS signaling with the UE802 via the N3IWF interface.

[0044] The SMF846 may be responsible for SM (e.g., session establishment, tunnel management between UPF848 and AN808), UE IP address allocation and management (including optional authorization), selection and control of UP functions, configuration of traffic steering in UPF848 for routing traffic to appropriate destinations, termination of interfaces to policy control functions, policy enforcement, billing, and some control of QoS, lawful interception (for SM events and interfaces to LI systems), termination of the SM portion of NAS messages, downlink data notification, initiation of AN-specific SM information sent to AN808 on N2 via AMF844, and determination of the session's SSC mode. SM may refer to the management of PDU sessions, and PDU sessions or "sessions" may refer to PDU connectivity services that provide or enable the exchange of PDUs between UE802 and data network 836.

[0045] The UPF848 can act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 836, and a branch point for supporting multi-homed PDU sessions. The UPF848 can also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), perform transport-level packet marking on uplinks and downlinks, and perform downlink packet buffering and downlink data notification triggering. The UPF848 may include an uplink classifier to support routing of traffic flows to the data network.

[0046] The NSSF850 can select a set of network slice instances to service the UE802. The NSSF850 can also determine, if necessary, the authorized NSSAIs and their mappings to the joined S-NSSAIs. The NSSF850 can also determine, based on a preferred configuration, a set of AMFs to be used to service the UE802, or a list of candidate AMFs, possibly by querying the NRF854. The selection of a set of network slice instances for the UE802 can be triggered by the AMF844, to which the UE802 registers, by interacting with the NSSF850, which can result in a change of AMF. The NSSF850 can interact with the AMF844 via the N22 reference point and can communicate with other NSSFs in the visited network via the N31 reference point (not shown). In addition, the NSSF850 can represent an NNSSF service-based interface.

[0047] The NEF852 can securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g., AF860), edge computing, or fog computing systems. In such embodiments, the NEF852 can authenticate, authorize, or restrict AFs. The NEF852 can also translate information exchanged with AF860 and information exchanged with internal network functions. For example, the NEF852 can translate between AF service identifiers and internal 5GC information. The NEF852 can also receive information from other NFs based on the exposed capabilities of those NFs. This information may be stored in the NEF852 as structured data or in a data storage NF using a standardized interface. The stored information can then be re-exposed by the NEF852 to other NFs and AFs, or used for other purposes such as analysis. Furthermore, the NEF852 can represent Nnef service-based interfaces.

[0048] The NRF854 supports service discovery functionality, receiving NF discovery requests from NF instances and providing NF instances with information about discovered NF instances. The NRF854 also maintains information about available NF instances and their supported services. Where used herein, terms such as “instantiate” and “instantiation” may refer to the creation of an instance, and “instance” may refer to the specific occurrence of an object, for example, during the execution of program code. Furthermore, the NRF854 can represent Nnrf service-based interfaces.

[0049] The PCF856 can provide policy rules to control plane functions and enforce them, and can also support an integrated policy framework to manage network behavior. The PCF856 can also implement a front-end for accessing subscription information related to policy decisions within the UDR of the UDM858. In addition to communicating with functions via reference points as illustrated, the PCF856 exhibits an Npcf service-based interface.

[0050] The UDM858 can process subscription-related information to support the processing of network entities in a communication session and can store subscription data for the UE802. For example, subscription data may be communicated between the UDM858 and the AMF844 via an N8 reference point. The UDM858 can include two parts: an application frontend and a UDR. The UDR can store subscription and policy data for the UDM858 and PCF856, as well as structured data for publication and application data for the NEF852 (including a PFD for application discovery and application request information for multiple UE802s). A Nudr service-based interface, indicated by the UDR221, may allow the UDM858, PCF856, and NEF852 to access specific sets of stored data, as well as read notifications of changes to the relevant data in the UDR, update (e.g., add, modify), delete, and subscribe. A UDM can include a UDM-FE responsible for handling credentials, location management, and enrollment management. Several different frontends can serve the same user in different transactions. The UDM-FE accesses enrollment information stored in the UDR and performs authentication certificate processing, user identification processing, access permission, enrollment / mobility management, and enrollment management. In addition to communicating with other NFs via a reference point as shown in the diagram, the UDM858 can represent a Nudm service-based interface.

[0051] The AF860 provides application influence over traffic routing, offers access to the NEF, and can interact with the policy framework for policy control.

[0052] In some embodiments, the 5GC840 may enable edge computing by selecting operator / third-party services to be geographically close to the point where the UE802 is attached to the network. This can reduce latency and load on the network. To provide an edge computing implementation, the 5GC840 may select a UPF848 close to the UE802 and perform traffic steering from the UPF848 to the data network 836 via the N6 interface. This can be based on UE join data, UE location, and information provided by the AF860. In this way, the AF860 can influence UPF (re)selection and traffic routing. When the AF860 is considered a trusted entity based on operator deployment, the network operator may allow the AF860 to interact directly with the relevant NF. In addition, the AF860 may exhibit a NAF service-based interface.

[0053] The data network 836 may represent various network operator services, internet access, or third-party services that may be provided by one or more servers, for example, including an application / content server 838.

[0054] Figure 9 schematically shows the wireless network 900 in various embodiments. The wireless network 900 may include a UE 902 that wirelessly communicates with AN 904. UE 902 and AN 904 are similar to and substantially interchangeable components of similar names described elsewhere in this specification.

[0055] UE902 can be communicatively coupled to AN904 via connection 906. Connection 906 is shown as an air interface to enable communication coupling and can comply with cellular communication protocols such as LTE or 5GNR protocols operating at mmWave or frequencies below 6GHz.

[0056] The UE902 may include a host platform 908 coupled to a modem platform 910. The host platform 908 may include an application processing circuit 912 that can be coupled to a protocol processing circuit 914 of the modem platform 910. The application processing circuit 912 can run various applications for the UE902 to source / sink application data. The application processing circuit 912 may further implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

[0057] The protocol processing circuit 914 may implement one or more layer operations to facilitate the transmission or reception of data via connection 906. The layer operations implemented by the protocol processing circuit 914 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0058] The modem platform 910 may further include a digital baseband circuit 916 that can implement one or more layer operations, which are “lower” layer operations performed by the protocol processing circuit 914 in the network protocol stack. These operations may include PHY operations, for example, one or more of the following: HARQ-ACK functionality, scrambling / descrambling, coding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bitmetric determination, multi-antenna port precoding / decoding which may include one or more of spatiotemporal, spatial frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronous sequence generation / detection, control channel signal blind decoding, and other related functions.

[0059] The modem platform 910 may further include a transmitting circuit 918, a receiving circuit 920, an RF circuit 922, and an RF front end (RFFE) 924, the RFFE 910 may include or be connected to one or more antenna panels 926. The transmitting circuit 918 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc., the receiving circuit 920 may include an analog-to-digital converter, a mixer, an IF component, etc., the RF circuit 922 may include a low-noise amplifier, a power amplifier, a power tracking component, etc., and the RFFE 924 may include filters (e.g., surface / bulk acoustic wave filters), switches, an antenna tuner, a beamforming component (e.g., a phase array antenna component), etc. The selection and configuration of components in the transmitting circuit 918, receiving circuit 920, RF circuit 922, RFFE 924, and antenna panel 926 (collectively referred to as the “transmitting / receiving components”) may be specific to particular implementation details, such as whether the communication is TDM or FDM, or whether it is millimeter wave or sub-6 GHz frequency.

[0060] In some embodiments, the protocol processing circuit 914 may include one or more instances of a control circuit (not shown) that provides control functions for the transmit / receive components.

[0061] UE reception can be established by and through the antenna panel 926, RFFE 924, RF circuit 922, receiving circuit 920, digital baseband circuit 916, and protocol processing circuit 914. In some embodiments, the antenna panel 926 can receive transmissions from AN904 by receiving beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 926.

[0062] UE transmission can be established by and through the protocol processing circuit 914, the digital baseband circuit 916, the transmit circuit 918, the RF circuit 922, the RFFE 924, and the antenna panel 926. In some embodiments, the transmit components of UE 904 may apply spatial filters to the data to be transmitted in order to form a transmit beam emitted by the antenna elements of the antenna panel 926.

[0063] Similar to UE902, AN904 may include a host platform 928 coupled to a modem platform 930. The host platform 928 may include an application processing circuit 932 coupled to the protocol processing circuit 934 of the modem platform 930. The modem platform may further include a digital baseband circuit 936, a transmit circuit 938, a receive circuit 940, an RF circuit 942, an RFFE circuit 944, and an antenna panel 946. The components of AN904 are similar to the components of UE902 with similar names and may be substantially interchangeable. In addition to performing data transmission / reception as described above, the components of AN908 can perform various logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0064] Figure 10 is a block diagram showing components according to several exemplary embodiments that can read instructions from a machine-readable medium or computer-readable medium (e.g., a non-temporary machine-readable storage medium) and perform any one or more of the methods described herein. Specifically, Figure 10 shows a schematic diagram of hardware resources 1000 including one or more processors (or processor cores) 1010, one or more memory / storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040 or other interface circuitry. In embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1002 may be executed to provide execution environments for one or more network slices / subslices for utilizing the hardware resources 1000.

[0065] Processor 1010 may include, for example, processors 1012 and 1014. Processor 1010 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a composite instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those described herein), or any suitable combination thereof.

[0066] The memory / storage device 1020 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1020 may include, but is not limited to, any type of volatile, non-volatile, or semi-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, or solid-state storage.

[0067] The communication resource 1030 may include an interconnect or network interface controller, component, or other suitable device that communicates with one or more peripheral devices 1004 or one or more databases 1006 or other network elements via the network 1008. For example, the communication resource 1030 may include a wired communication component (for coupling via USB, Ethernet®, etc.), a cellular communication component, an NFC component, a Bluetooth® (or Bluetooth® Low Energy) component, a Wi-Fi® component, and other communication components.

[0068] Instruction 1050 may comprise other executable code that causes at least one of the following to execute one or more of the methods described herein: software, programs, applications, applets, apps, or processor 1010. Instruction 1050 may reside entirely or partially in at least one of the following: processor 1010 (e.g., in the processor's cache memory), memory / storage device 1020, or any preferred combination thereof. Furthermore, any portion of instruction 1050 may be transferred to hardware resource 1000 from any combination of peripheral device 1004 or database 1006. Thus, the memory of processor 1010, memory / storage device 1020, peripheral device 1004, and database 1006 are examples of computer-readable and machine-readable media.

[0069] Exemplary procedure In some embodiments, electronic devices(s), networks(s), systems(s), chips(s) or components(s), or parts thereof or implementations, of Figures 8-10 or some other figures herein may be configured to perform one or more processes, techniques, or methods, or parts thereof, as described herein. One such process is shown in Figure 11. For example, process 1100 may include, in 1105, determining the location of uplink control information (UCI) in a physical uplink shared channel (PUSCH) transmission based on UE capability information. The process further includes, in 1110, encoding a PUSCH message for transmission containing the UCI at the determined location.

[0070] Another such process is shown in Figure 12. In this example, process 1200 includes determining, in 1205, the location of uplink control information (UCI) to be transmitted with a physical uplink shared channel (PUSCH) transmission, based on one or more UE capabilities. The process further includes, in 1210, encoding a PUSCH message for transmission containing the UCI at the determined location.

[0071] Another such process is shown in Figure 13. In this example, process 1300 includes receiving uplink control information (UCI) transmitted from the user equipment (UE) along with a physical uplink shared channel (PUSCH) transmission at 1305. The process further includes encoding a message for transmission to the UE at 1310, which includes downlink control information (DCI) acknowledging the UCI, the DCI including an indication of a Hybrid Automatic Retransmission Request (HARQ) process number associated with the UCI.

[0072] In one or more embodiments, at least one of the components shown in one or more of the aforementioned figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the following exemplary section. For example, a baseband circuit described above in relation to one or more of the aforementioned figures may be configured to operate according to one or more of the examples described below. In another example, a circuit associated with a UE, base station, network element, etc., described above in relation to one or more of the aforementioned figures may be configured to operate according to one or more of the examples described in the following exemplary section. Examples Example 1 may include a method for transmitting flexible uplink control information (UCI), and the method Scheduling PUSCH transmissions that multiplex the Uplink Shared Channel (UL SCH) and UCI; Based on UE capabilities, the location of the UCI transmission is determined based on signaling instructions from the serving cell and other parameters of PUSCH; This includes submitting PUSCH along with UL-SCH and UCI.

[0073] Example 2 may include the methods of Example 1 or some other examples herein, in which the UCI is transmitted in the earliest DFT-s-OFDM before the code block bundle (CBB) that satisfies the UE capability for Z' and Z, where Z' is the minimum time between the last symbols of the aperiodic CSI-RS used for measurement and UCI reporting, and Z is the minimum time between the last symbol of the PDCCH and the UCI.

[0074] Example 3 may include the method of Example 2 or some other example herein, in which the UCI is sent along with an additional DM-RS.

[0075] Example 4 may include the method of Example 1 or some other example herein, where the UCI is transmitted in the earliest DFT-s-OFDM after the DM-RS of PUSCH that satisfies the UE capability for Z' and Z, where Z' is the minimum time between the last symbol of the aperiodic CSI-RS used for measurement and the UCI report, and Z is the minimum time between the last symbol of the PDCCH and the UCI.

[0076] Example 5 may include the method of Example 1 or some other example herein, in which the UCI is transmitted in the last DFT-s-OFDM symbol of PUSCH.

[0077] Example 6 may include the method of Example 1 or some other example herein, in which the UCI is transmitted in the first DFT-s-OFDM symbol of the PUSCH portion of the next TDD period.

[0078] Example 7 may include the method of Example 1 or some other example herein, in which the UCI punctures the PUSCH transmission.

[0079] Example 8 may include the method of Example 2 or some other example herein, in which the PUSCH transmission is performed on a DFT-s-OFDM symbol that is not assigned for UCI transmission (rate matching operation).

[0080] Example 9 may include the systems and methods of Example 1 or some other examples herein, wherein the UCI is acknowledged by DCI transmission within a predetermined time after the UCI is reported.

[0081] Example 10 may include the systems and methods of Example 9 or some other examples herein, in which the UCI is assigned using the HARQ process.

[0082] Example 11 may include the systems and methods of Example 9 or some other examples herein, in which post-acknowledgment UCI is considered effective.

[0083] Example 12 may include systems and methods of Example 10 or some other examples herein, and if the UCI includes a CRI (CSI-RS Resource Index), the beam used to transmit the corresponding CSI-RS is also applicable to other downlink and uplink transmissions.

[0084] Example 13 may include a method that includes the following: To receive a message for scheduling the transmission of a physical uplink shared channel (PUSCH) with multiplexed uplink control information (UCI); Determining the position of the UCI in the transmission based on one or more of the UE capability, instructions received from the serving cell, and / or parameters of the PUSCH; Encode the PUSCH for transmission based on the determined position of the UCI.

[0085] Example 14 may include the method of Example 13 or some other example herein, where the position of the UCI is determined as the earliest DFT-s-OFDM symbol before the code block bundle (CBB) that satisfies the UE capability for Z' and Z', where Z' is the minimum time between the last symbol of the aperiodic CSI-RS used for measurement and the UCI report, and Z' is the minimum time between the last symbol of the PDCCH and the UCI.

[0086] Example 15 may include the method of Example 13 or some other example herein, where the position of the UCI is determined as the earliest DFT-s-OFDM symbol after the PUSCH DM-RS that satisfies the UE capability for Z' and Z', where Z' is the minimum time between the last symbol of the aperiodic CSI-RS used in the measurement and the UCI report, and Z is the minimum time between the last symbol of the PDCCH and the UCI.

[0087] Example 16 may include the methods of Examples 14-15 or some other examples herein, where PDCCH is a message for scheduling the transmission of PUSCH.

[0088] Example 17 may include the methods of Examples 13–16 or some other examples herein, in which the UCI is sent along with an additional DM-RS.

[0089] Example 18 may include the methods of Examples 13–17 or some other examples herein, and further includes receiving an acknowledgment from a gNB that the gNB has received a UCI.

[0090] Example 19 may include the method of Example 18 or some other example herein, in which the acknowledgment is included in the downlink control information (DCI).

[0091] Example 20 may include the methods of Examples 18-19 or some other examples herein, where the affirmative response is associated with the HARQ process ID.

[0092] Example 21 may include methods from Examples 13-20 or some other examples herein, the methods being performed by a user device (UE) or a part thereof.

[0093] Example X1 is a user equipment (UE) device: A memory for storing capability information associated with the aforementioned UE A processing circuit coupled to the memory Based on the aforementioned UE capability information, the location of the uplink control information (UCI) within the physical uplink shared channel (PUSCH) transmission is determined; The system has a processing circuit that encodes a PUSCH message for transmission, including the UCI, at the determined location.

[0094] Example X2 includes the apparatus of Example X1 or some other example herein, wherein the UE capability information includes an indication of the minimum time between the last symbol of the non-periodic channel status information reference signal (CSI-RS) used for measurement and the UCI.

[0095] Example X3 includes the apparatus of Example X1 or some other example herein, and the UE capability information includes an indication of the minimum time between the last symbol of the physical downlink control channel (PDCCH) transmission and the UCI.

[0096] Example X4 includes the apparatus of Example X1 or several other examples herein, and the UCI position is based on the earliest Discrete Fourier Transform Spreading Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) symbol prior to the code block bundle (CBB) that satisfies the capability in the UE capability information.

[0097] Example X5 includes the apparatus of Example X4 or some other example herein, where the UCI is located between two adjacent CBBs.

[0098] Example X6 includes the apparatus of Example X1 or some other examples herein, wherein the transmission of UCI in the PUSCH message includes a demodulated reference signal (DM-RS) symbol transmitted in a symbol adjacent to the UCI.

[0099] Example X7 includes the apparatus of Example X1 or some other examples herein, in which the transmission of UCI in the PUSCH message is performed after the first DM-RS symbol that satisfies the capability in the UE capability information.

[0100] Example X8 includes the apparatus of Example X1 or some other examples herein, in which the transmission of UCI in a PUSCH message is deferred until the end of the uplink (UL) portion of the time-division duplex (TDD) period.

[0101] Example X9 includes the apparatus of any of Examples X1 to X8 or some other examples herein, where PUSCH includes uplink shared channel (UL SCH) information.

[0102] Example X10 includes the apparatus of Example X9 or some other examples herein, in which the transmission of UCI in the PUSCH message is deferred until after the transmission of UL SCH information.

[0103] Example X11 includes any of the devices from Examples X1 to X10 and further includes the step of receiving downlink control information (DCI) from a next-generation node B (gNB) acknowledging the UCI.

[0104] Example X12 includes the apparatus of Example X11 or some other example herein, and DCI includes an indication of the Hybrid Automated Retransmission Request (HARQ) process number associated with UCI.

[0105] Example X13 includes one or more computer-readable media that store instructions, and when the instructions are executed by one or more processors, they are delivered to the user equipment (UE): Based on one or more UE capabilities, determine the location of uplink control information (UCI) to be transmitted with a physical uplink shared channel (PUSCH) transmission; The system will then encode a PUSCH message for transmission based on the determined UCI location.

[0106] Example X14 includes one or more computer-readable media of Example X13 or some other examples herein, wherein one or more UE capabilities include an indication of the minimum time between the last symbol of a non-periodic channel status information reference signal (CSI-RS) used for measurement and the UCI.

[0107] Example X15 includes one or more computer-readable media of Example X13 or some other examples herein, where one or more UE capabilities include a minimum time indication between the last symbol of a physical downlink control channel (PDCCH) transmission and the UCI.

[0108] Example X16 includes one or more computer-readable media of Example X13 or some other examples herein, where the location of the UCI is based on the earliest Discrete Fourier Transform Spreading Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) symbol prior to the code block bundle (CBB) that satisfies the capability in the UE capability information.

[0109] Example X17 includes one or more computer-readable media of Example X16 or some other examples herein, where the location of the UCI is between two adjacent CBBs.

[0110] Example X18 includes one or more computer-readable media of Example X13 or some other examples herein, and the transmission of UCI in conjunction with a PUSCH message is: The UCI includes a demodulated reference signal (DM-RS) symbol transmitted in a symbol adjacent to the UCI, or It is executed after a first DM-RS symbol that satisfies the capability in the aforementioned UE capability information, or; The delay will be extended until the end of the uplink (UL) portion of the time-division deadweight (TDD) period. Example X19 includes a computer-readable medium from any of Examples X13 to X18 or one or more of some other examples herein, where PUSCH includes uplink shared channel (UL SCH) information.

[0111] Example X20 includes one or more computer-readable media of Example X19 or some other examples herein, in which the transmission of UCI in the PUSCH message is deferred until after the transmission of UL SCH information.

[0112] Example X21 includes one or more computer-readable media from any of Examples X13 to X20, the media further storing instructions causing the UE to receive downlink control information (DCI) from the next-generation node B (gNB) acknowledging the UCI, the DCI including instructions for a Hybrid Auto-Retransmission Request (HARQ) process number associated with the UCI.

[0113] Example X22 includes one or more computer-readable media for storing instructions, and when the instructions are executed by one or more processors, they are sent to the next-generation NodeB (gNB): Receiving uplink control information (UCI) transmitted from the user equipment (UE) along with the physical uplink shared channel (PUSCH) transmission; Encode a message for transmission to the UE, which includes downlink control information (DCI) acknowledging the UCI, wherein the DCI includes an instruction for a Hybrid Automatic Retransmission Request (HARQ) process number associated with the UCI.

[0114] Example X23 includes one or more computer-readable media of Example X22 or some other examples herein, in which the UCI is transmitted between two adjacent code block bundles (CBBs).

[0115] Example X24 includes one or more computer-readable media of Example X22 or some other examples herein, the UCI being transmitted in conjunction with the PUSCH transmission: The UCI includes a demodulated reference signal (DM-RS) symbol transmitted in a symbol adjacent to the UCI, or It is executed after a first DM-RS symbol that satisfies the capability in the aforementioned UE capability information, or; It will be postponed until the end of the uplink (UL) portion of the time-division deadlink (TDD) period.

[0116] Example Z01 may include an apparatus equipped with means for performing one or more elements of any other method or process described herein, or any other method or process described herein.

[0117] Example Z02 may include one or more non-temporary computer-readable media containing instructions that cause an electronic device to perform one or more elements of any other method or process described herein, or any other method described herein, when an instruction is executed by one or more processors of the electronic device.

[0118] Example Z03 may include a device comprising logic, modules, or circuits for performing one or more elements of any method described in or related to any of Examples 1 to X24, or any other method or process described herein.

[0119] Example Z04 may include methods, techniques, or processes, or parts or portions thereof, as described in or related to any of Examples 1-X24.

[0120] Example Z05 may include a device comprising one or more processors and one or more computer-readable media containing instructions, which, when executed by one or more processors, cause one or more processors to execute one or more of the methods, techniques, or processes described in or related to any of Examples 1 to X24.

[0121] Example Z06 may include a signal, or part or portion thereof, as described in any of Examples 1 to X24, or related to any of Examples 1 to X24.

[0122] Example Z07 may include datagrams, packets, frames, segments, protocol data units (PDUs), or messages described in or related to any of Examples 1 through X24, or any other items described in this disclosure.

[0123] Example Z08 may include data, or parts thereof, or signals encoded with data as described in any of Examples 1 to X24, or related to any of Examples 1 to X24, or data as otherwise described herein.

[0124] Example Z09 may include signals encoded in any of Examples 1 to X24, or in part or in part thereof, or in datagrams, packets, frames, segments, protocol data units (PDUs), or messages described in this disclosure.

[0125] Example Z10 may include an electromagnetic signal that carries a computer-readable instruction, and the execution of the computer-readable instruction by one or more processors causes one or more processors to execute a method, technique, or process, or part thereof, described in or related to any of Examples 1 to X24.

[0126] Example Z11 may include a computer program containing instructions, and the execution of the program by a processing element causes the processing element to execute a method, technique, or process, or part thereof, described or related to any of Examples 1 to X24.

[0127] Example Z12 may include signals in a wireless network as shown and described herein.

[0128] Example Z13 may include a method of communication in a wireless network as shown and described herein.

[0129] Example Z14 may include a system for providing wireless communication as shown and described herein.

[0130] Example Z15 may include a device for providing wireless communication as shown and described herein.

[0131] Any of the above examples can be combined with any other example (or combination of examples) unless expressly specified otherwise. The above descriptions of one or more implementations are illustrative and descriptive, but are not intended to be exhaustive or to limit the scope of embodiments to the exact forms disclosed. Such examples may be possible in light of the above teachings or can be obtained from the practice of various embodiments. Abbreviation Unless otherwise used herein, terms, definitions, and abbreviations may correspond to those defined in 3GPP TR 21.905 v16.0.0 (2019-06). For the purposes of this specification, the following abbreviations may apply to the examples and embodiments discussed herein. 3GPP Third Generation Partnership Project 4G Fourth Generation 5G Fifth Generation 5GC 5G Core network AC Application Client ACK (Acknowledgement) ACID Application Client Identification AF Application Function AM Acknowledged Mode AMBR Aggregate Maximum Bit Rate AMF Access and Mobility Management Function AN Access Network ANR Automatic Neighbor Relation AP (Application Protocol), Antenna Port, Access Point API Application Programming Interface APN (Access Point Name) ARP Allocation and Retention Priority ARQ Automatic Repeat Request Automatic repeat request AS Access Stratum Access Layer ASP Application Service Provider ASN.1 Abstract Syntax Notation One AUSF Authentication Server Function AWGN Additive White Gaussian Noise BAP (Backhaul Adaptation Protocol) BCH Broadcast Channel BER (Bit Error Ratio) BFD Beam Failure Detection BLER Block Error Rate BPSK (Binary Phase Shift Keying) - 2-state phase shift keying BRAS Broadband Remote Access Server BSS Business Support System BS Base Station BSR Buffer Status Report BW Bandwidth BWP Bandwidth Part C-RNTI Cell Radio Network Temporary Identity CA (Carrier Aggregation), Certification Authority CAPEX CAPital EXpenditure Capital Expenditure CBRA Contention-Based Random Access CC Component Carrier, Country Code, Cryptographic Checksum CCA Clear Channel Assessment (Available Channel Assessment) CCE Control Channel Element CCCH Common Control Channel CE Coverage Enhancement CDM (Content Delivery Network) CDMA Code-Division Multiple Access CFRA Contention Free Random Access CG Cell Group CGF Charging Gateway Function CHF Charging Function CI cell characteristics [identification information] CID Cell-ID Cell ID (e.g., positioning method) CIM Common Information Model CIR Carrier-to-Interference Ratio CK Cipher Key CM Connection Management, Conditional Mandatory CMAS Commercial Mobile Alert Service CMD Command CMS Cloud Management System CO Conditional Optional CoMP Coordinated Multi-Point CORESET Control Resource Set Control resource set COTS Commercial Off-The-Shelf CP Control Plane, Cyclic Prefix, Connection Point CPD Connection Point Descriptor CPE Customer Premise Equipment CPICH Common Pilot Channel CQI Channel Quality Indicator CPU (CSI processing unit), Central Processing Unit (CSI processing unit) C / R Command / Response field bit CRAN (Cloud Radio Access Network) CRB Common Resource Block CRC Cyclic Redundancy Check Cyclic Redundancy Check CRI Channel-State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI Cell RNTI CS Circuit Switched CSAR Cloud Service Archive CSI Channel-State Information CSI-IM CSI Interference Measurement CSI Interference Measurement CSI-RS CSI Reference Signal CSI reference signal CSI-RSRP CSI reference signal received power CSI reference signal received power CSI-RSRQ CSI reference signal received quality CSI reference signal received quality CSI-SINR CSI signal-to-noise and interference ratio CSMA Carrier Sense Multiple Access CSMA / CA CSMA with collision avoidance CSS Common Search Space, Cell-specific Search Space CTF Charging Trigger Function CTS Clear-to-Send transmission enabled. CWCodeword Codeword CWS Contention Window Size D2D Device-to-Device DC Dual Connectivity, Direct Current DCI Downlink Control Information DF Deployment Flavor DL Downlink DMTF Distributed Management Task Force DPDK Data Plane Development Kit DM-RS, DMRS Demodulation Reference Signal DN Data Network DNN Data Network Name DNAI (Data Network Access Identifier) DRB Data Radio Bearer DRS Discovery Reference Signal DRX Discontinuous Reception DSL (Domain Specific Language), Digital Subscriber Line DSLAM DSL Access Multiplexer DwPTS Downlink Pilot Time Slot E-LAN ​​Ethernet Local Area Network E2E End-to-End ECCA extended clear channel assessment, extended CCA ECCE Enhanced Control Channel Element ED Energy Detection EDGE Enhanced Datarates for GSM Evolution EAS Edge Application Server EASID (Edge Application Server Identification) ECS Edge Configuration Server ECSP (Edge Computing Service Provider) EDN (Edge Data Network) EEC Edge Enabler Client EECID Edge Enabler Client Identification EES Edge Enabler Server EESID: Edge Enabler Server Identification EHE Edge Hosting Environment EGMF Exposure Governance Table Management Function EGPRS Enhanced GPRS Enhanced GPRS EIR Equipment Identity Register eLAA (enhanced Licensed Assisted Access) EM, Element Manager eMBB Enhanced Mobile Broadband EMS Element Management System eNB evolved NodeB, E-UTRAN NodeB EN-DC E-UTRA-NR Dual Connectivity EPC Evolved Packet Core EPDCCH enhanced PDCCH, enhanced Physical Downlink Control Channel EPRE: Energy per resource element EPS Evolved Packet System EREG (enhanced REG), enhanced resource element groups ETSI (European Telecommunications Standards Institute) ETWS Earthquake and Tsunami Warning System eUICC embedded UICC, embedded Universal Integrated Circuit Card E-UTRA Evolved UTRA Evolved UTRA E-UTRAN Evolved UTRAN EV2X Improved V2X F1AP F1 Application Protocol F1-C F1 Control Plane Interface F1-U F1 User Plane Interface FACCH Fast Associated Control Channel FACCH / F Fast Associated Control Channel / Full rate FACCH / H Fast Associated Control Channel / Half rate FACH (Forward Access Channel) FAUSCH Fast Uplink Signalling Channel FB Functional Block FBI Feedback Information FCC (Federal Communications Commission) FCCH Frequency Correction Channel FDD (Frequency Division Duplex) FDM Frequency Division Multiplexing FDMA Frequency Division Multiple Access FE Front End FEC Forward Error Correction FFS For Further Study FFT Fast Fourier Transformation feLAA (Further Enhanced Licensed Assisted Access) FN Frame Number FPGA Field-Programmable Gate Array FR Frequency Range FQDN: Fully Qualified Domain Name G-RNTI GERAN Radio Network Temporary Identity GERAN (GSM EDGE RAN), GSM EDGE Radio Access Network GGSN Gateway GPRS Support Node GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System) gNB Next Generation NodeB gNB-CU (gNB-centralized unit), Next Generation NodeB Centralized unit gNB-DU (gNB-distributed unit), Next Generation NodeB distributed unit GNSS Global Navigation Satellite System GPRS General Packet Radio Service GSM Global System for Mobile Communications, Groupe Spécial Mobile GSM Alliance GTP GPRS Tunneling Protocol GTP-U GPRS Tunneling Protocol for User Plane GTS Go To Sleep Signal (Sleep Transition Signal related to WUS) GUMMEI: Globally Unique MME Identifier GUTI: Globally Unique Temporary UE Identity HARQ Hybrid ARQ, Hybrid Automatic Repeat Request HANDO Handover HFN HyperFrame Number HHO Hard Handover HLR Home Location Register HN Home Network Home Network HO Handover HPLMN Home Public Land Mobile Network HSDPA (High Speed ​​Downlink Packet Access) HSN Hopping Sequence Number HSPA High Speed ​​Packet Access HSS Home Subscriber Server HSUPA High Speed ​​Uplink Packet Access HTTP (Hypertext Transfer Protocol) HTTPS (Hypertext Transfer Protocol Secure) is a secure hypertext transfer protocol (HTTPS stands for http / 1.1 over SSL, i.e., port 443). I-Block Information Block ICCID (Integrated Circuit Card Identification) IAB Integrated Access and Backhaul ICIC Inter-Cell Interference Coordination ID Identity, Identifier Identification information, Identifier IDFT Inverse Discrete Fourier Transform IE Information Element IBE In-Band Emission IEEE Institute of Electrical and Electronics Engineers IEI Information Element Identifier IEIDL Information Element Identifier Data Length IETF Internet Engineering Task Force IF Infrastructure IM Interference Measurement, Intermodulation, IP Multimedia IMC IMS Credentials IMS Credentials IMEI (International Mobile Equipment Identity) IMGI International mobile group identity IMPI IP Multimedia Private Identity IMPU IP Multimedia Public Identity IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IoT (Internet of Things) IP Internet Protocol IPsec IP Security, Internet Protocol Security IP-CAN IP-Connectivity Access Network IP-M IP Multicast IP Multicast IPv4 Internet Protocol Version 4 IPv6 Internet Protocol Version 6 IR Infrared IS In Sync Syncing IRP Integration Reference Point ISDN Integrated Services Digital Network ISIM IM Services Identity Module ISO International Organization for Standardization ISP (Internet Service Provider) IWF Interworking Function I-WLAN Interworking WLAN Constraint length of the convolutional code, USIM individual key kB Kilobyte (1000 bytes) kbps kilobits per second Kc Ciphering key Encryption key Individual subscriber authentication key KPI Key Performance Indicator KQI Key Quality Indicator KSI Key Set Identifier ksps kilo-symbols per second KVM (Kernel Virtual Machine) L1 Layer 1 (physical layer) L1-RSRP Layer 1 reference signal received power L2 Layer 2 (data link layer) L3 Layer 3 (Network Layer) LAA Licensed Assisted Access LAN (Local Area Network) LADN (Local Area Data Network) LBT Listen Before Talk LCM (Life Cycle Management) LCR Low Chip Rate LCS Location Services LCID: Logical Channel ID LI Layer Indicator LLC Logical Link Control, Low Layer Compatibility LPLMN Local PLMN Local PLMN LPP LTE Positioning Protocol LSB (Least Significant Bit) LTE Long Term Evolution LWA LTE-WLAN aggregation LWIP LTE / WLAN Radio Level Integration with IPsec Tunnel: LTE / WLAN radio level integration via IPsec tunnel. LTE Long Term Evolution M2M Machine-to-Machine MAC Medium Access Control (in the context of protocol layering) MAC Message authentication code (in the context of security / encryption) MAC-A MAC used for authentication and key agreement (in the context of TSG T WG3) MAC-I MAC used for data integrity: MAC used for data integrity in signaling messages (in the context of TSG T WG3) MANO Management and Orchestration MBMS (Multimedia Broadcast and Multicast Service) MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MCC Mobile Country Code MCG Master Cell Group MCOT Maximum Channel Occupancy Time MCS Modulation and coding scheme MDAF Management Data Analytics Function MDAS Management Data Analytics Service Minimization of Drive Tests (MDT) ME Mobile Equipment Mobile Devices MeNB master eNB Master eNB MER Message Error Ratio MGL Measurement Gap Length MGRP Measurement Gap Repetition Period MIB Master Information Block, Management Information Base MIMO Multiple Input Multiple Output MLC Mobile Location Centre MM Mobility Management Mobility Management MME Mobility Management Entity MN Master Node MNO Mobile Network Operator MO: Measurement Object, Mobile Originated. MPBCH MTC Physical Broadcast Channel MPDCCH MTC Physical Downlink Control Channel MPDSCH MTC Physical Downlink Shared Channel MPRACH MTC Physical Random Access Channel MPUSCH MTC Physical Uplink Shared Channel MPLS (MultiProtocol Label Switching) MS Mobile Station Mobile station MSB (Most Significant Bit) MSC Mobile Switching Centre MSI Minimum System Information, MCH Scheduling Information MSID Mobile Station Identifier MSIN Mobile Station Identification Number MSISDN Mobile Subscriber ISDN Number MT Mobile Terminated, Mobile Termination MTC Machine-Type Communications mMTC massive MTC, massive Machine-Type Communications Mechanical large-scale machine-type communication MU-MIMO (Multi-User MIMO) MWUS MTC wake-up signal, MTC WUS MTC WUS NACK (Negative Acknowledgement) NAI (Network Access Identifier) NAS Non-Access Stratum, Non-Access Stratum layer NCT Network Connectivity Topology NC-JT Non-Coherent Joint Transmission NEC Network Capability Exposure: Network Function Disclosure NE-DC NR-E-UTRA Dual Connectivity NEF Network Exposure Function (Network Exposure Function) NF Network Function NFP Network Forwarding Path NFPD Network Forwarding Path Descriptor NFV (Network Functions Virtualization) NFVI NFV Infrastructure NFV Infrastructure NFVO NFV orchestrator NFV orchestrator NG Next Generation Next Generation, Next Gen NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity NM Network Manager NMS Network Management System N-PoP Network Point of Presence NMIB, N-MIB, Narrowband MIB NPBCH (Narrowband Physical Broadcast Channel) NPDCCH Narrowband Physical Downlink Control Channel NPDSCH Narrowband Physical Downlink Shared Channel NPRACH Narrowband Physical Random Access Channel NPUSCH Narrowband Physical Uplink Shared Channel NPSS Narrowband Primary Synchronization Signal NSSS Narrowband Secondary Synchronization Signal NR (New Radio), Neighbor Relation NRF NF Repository Function NRS Narrowband Reference Signal NS Network Service NSA Non-Standalone operation mode NSD Network Service Descriptor NSR Network Service Record NSSAI Network Slice Selection Assistance Information S-NNSAI Single-NSSAI Single NSSAI NSSF Network Slice Selection Function NW Network NWUS (Narrowband WUS) NZP Non-Zero Power O&M Operation and Maintenance ODU2 Optical Channel Data Unit - Type 2 OFDM (Orthogonal Frequency Division Multiplexing) OFDMA (Orthogonal Frequency Division Multiple Access) OOB (Out-of-band) OOS (Out of Sync) OPEX: Operating Expenses OSI Other System Information OSS Operations Support System OTA over-the-air PAPR (Peak-to-Average Power Ratio) PAR (Peak to Average Ratio) PBCH (Physical Broadcast Channel) PC Power Control, Personal Computer PCC Primary Component Carrier, Primary CC PCell Primary Cell Main cell PCI Physical Cell ID, Physical Cell Identity PCEF Policy and Charging Enforcement Function PCF Policy Control Function PCRF Policy Control and Charging Rules Function PDCP (Packet Data Convergence Protocol) and Packet Data Convergence Protocol layer. PDCCH Physical Downlink Control Channel PDCP (Packet Data Convergence Protocol) PDN (Packet Data Network), Public Data Network PDSCH (Physical Downlink Shared Channel) PDU Protocol Data Unit PEI Permanent Equipment Identifiers PFD Packet Flow Description P-GW PDN Gateway PHICH Physical hybrid-ARQ indicator channel PHY Physical layer PLMN Public Land Mobile Network PIN (Personal Identification Number) PM Performance Measurement Performance measurement PMI Precoding Matrix Indicator PNF (Physical Network Function) PNFD (Physical Network Function Descriptor) PNFR (Physical Network Function Record) POC PTT over Cellular PP, PTP: Point-to-Point PPP (Point-to-Point Protocol) PRACH Physical RACH Physical RACH PRB Physical resource block PRG Physical resource block group ProSe (Proximity Services), Proximity-Based Service PRS Positioning Reference Signal PRR Packet Reception Radio PS Packet Services PSBCH Physical Sidelink Broadcast Channel PSDCH Physical Sidelink Downlink Channel PSCCH Physical Sidelink Control Channel PSSCH Physical Sidelink Shared Channel PSCell Primary SCell Primary SCell PSS Primary Synchronization Signal Primary synchronization signal PSTN Public Switched Telephone Network PT-RS Phase-tracking reference signal Phase-tracking reference signal PTT Push-to-Talk PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel QAM (Quadrature Amplitude Modulation) QCI QoS class of identifier QCL Quasi co-location (quasi-co-location) QFI QoS Flow ID, QoS Flow Identifier QoS (Quality of Service) QPSK Quadrature (Quaternary) Phase Shift Keying QZSS Quasi-Zenith Satellite System RA-RNTI Random Access RNTI Random Access RNTI RAB Radio Access Bearer Radio Access Bearer, Random Access Burst Random Access Burst RACH Random Access Channel Random Access Channel RADIUS Remote Authentication Dial In User Service Remote Authentication Dial In User Service RAN Radio Access Network Radio Access Network RAND RANDom number Random number (used for authentication) RAR Random Access Response Random Access Response RAT Radio Access Technology Radio Access Technology RAU Routing Area Update Routing Area Update RB Resource block Resource block, Radio Bearer Radio Bearer RBG Resource block group Resource block group REG Resource Element Group Resource Element Group Rel Release Release REQ REQuest Request RF Radio Frequency Radio Frequency RI Rank Indicator Rank Indicator RIV Resource indicator value Resource indicator value RL Radio Link Radio Link RLC Radio Link Control Radio Link Control, Radio Link Control layer Radio Link Control layer RLC AM RLC Acknowledged Mode RLC Acknowledged Mode RLC UM: RLC Unacknowledged Mode, RLC Unacknowledged Mode RLF: Radio Link Failure, Radio Link Failure RLM: Radio Link Monitoring, Radio Link Monitoring RLM-RS: Reference Signal for RLM, Reference Signal for RLM RM: Registration Management, Registration Management RMC: Reference Measurement Channel, Reference Measurement Channel RMSI: Remaining MSI, Remaining Minimum System Information, Remaining MSI, Remaining Minimum System Information RN: Relay Node, Relay Node RNC: Radio Network Controller, Radio Network Controller RNL: Radio Network Layer, Radio Network Layer RNTI: Radio Network Temporary Identifier, Radio Network Temporary Identifier ROHC: RObust Header Compression, RObust Header Compression RRC: Radio Resource Control, Radio Resource Control layer, Radio Resource Control, Radio Resource Control layer Radio Resource Control Layer RRM: Radio Resource Management, Radio Resource Management RS: Reference Signal, Reference Signal RSRP: Reference Signal Received Power, Reference Signal Received Power RSRQ: Reference Signal Received Quality, Reference Signal Received Quality RSSI: Received Signal Strength Indicator, Received Signal Strength Indicator RSU Road Side Unit RSTD Reference Signal Time Difference RTP (Real Time Protocol) RTS Ready-To-Send Ready to send RTT (Round Trip Time) Rx Reception, Receiving Receiver S1AP S1 Application Protocol S1-MME S1 for the control plane S1-U S1 for the user plane S-GW Serving Gateway S-RNTI SRNC Radio Network Temporary Identity S-TMSI SAE Temporary Mobile Station Identifier SAE Temporary Mobile Station Identifier SA Standalone operation mode SAE System Architecture Evolution SAP Service Access Point SAPD Service Access Point Descriptor SAPI Service Access Point Identifier SCC Secondary Component Carrier, Secondary CC SCell Secondary Cell SCEF Service Capability Exposure Function SC-FDMA (Single Carrier Frequency Division Multiple Access) SCG Secondary Cell Group SCM Security Context Management SCS Subcarrier Spacing SCTP Stream Control Transmission Protocol SDAP (Service Data Adaptation Protocol) - Service Data Adaptation Protocol Layer SDL Supplementary Downlink SDNF (Structured Data Storage Network Function) SDP Session Description Protocol SDSF (Structured Data Storage Function) SDU Service Data Unit SEAF Security Anchor Function SeNB secondary eNB SEPP Security Edge Protection Proxy Security Edge Protection Proxy SFI Slot format indication Slot format indication SFTD Space-Frequency Time Diversity, SFN and frame timing difference Space-Frequency Time Diversity, SFN and frame timing difference SFN System Frame Number System Frame Number SgNB Secondary gNB Secondary gNB SGSN Serving GPRS Support Node Serving GPRS Support Node S-GW Serving Gateway Serving Gateway SI System Information System Information SI-RNTI System Information RNTI System Information RNTI SIB System Information Block System Information Block SIM Subscriber Identity Module Subscriber Identity Module SIP Session Initiated Protocol Session Initiated Protocol SiP System in Package System in Package SL Sidelink Sidelink SLA Service Level Agreement Service Level Agreement SM Session Management Session Management SMF Session Management Function Session Management Function SMS Short Message Service Short Message Service SMSF SMS Function SMS Function SMTC SSB-based Measurement Timing Configuration SN Secondary Node, Sequence Number SoC (System on Chip) SON Self-Organizing Network SpCell Special Cell SP-CSI-RNTI Semi-Persistent CSI RNTI SPS Semi-Persistent Scheduling SQN Sequence number SR Scheduling Request SRB Signaling Radio Bearer SRS Sounding Reference Signal Detection reference signal SS Synchronization Signal Synchronization signal SSB Synchronization Signal Block SSID (Service Set Identifier) SS / PBCH Block SS / PBCH Block SSBRI SS / PBCH Block Resource Indicator, Syncheronization Signal Block Resource Indicator SSC Session and Service Continuity SS-RSRP Synchronization Signal based Reference Signal Received Power SS-RSRQ Synchronization Signal based Reference Signal Received Quality SS-SINR Synchronization Signal-based Signal-to-Noise and Interference Ratio SSS Secondary Synchronization Signal SSSG Search Space Set Group SSSIF Search Space Set Indicator SST Slice / Service Types SU-MIMO (Single User MIMO) SUL Supplementary Uplink TA Timing Advance, Tracking Area TAC Tracking Area Code TAG Timing Advance Group TAI Tracking Area Identity TAU Tracking Area Update TB Transport Block TBS Transport Block Size TBD To Be Defined TCI Transmission Configuration Indicator TCP Transmission Communication Protocol TDD (Time Division Duplex) TDRA Time Domain Resource Allocation TDM Time Division Multiplexing TDMA (Time Division Multiple Access) TE Terminal Equipment TEID: Tunnel End Point Identifier TFT Traffic Flow Template TMSI (Temporary Mobile Subscriber Identity) TNL (Transport Network Layer) TPC Transmit Power Control TPMI Transmitted Precoding Matrix Indicator TR Technical Report Technical report TRP, TRxP Transmission Reception Point TRS Tracking Reference Signal TRx Transceiver TS Technical Specifications, Technical Standards TTI Transmission Time Interval Tx Transmission, Transmitting, Transmission, Transmitter U-RNTI UTRAN Radio Network Temporary Identity UART Universal Asynchronous Receiver and Transmitter UCI Uplink Control Information UE User Quest User Device UDM Unified Data Management: Centralized Data Management UDP User Datagram Protocol UDSF (Unstructured Data Storage Network Function) UICC Universal Integrated Circuit Card UL Uplink UM Unacknowledged Mode (No Acknowledgment Response Mode) UML (Unified Modeling Language) UMTS Universal Mobile Telecommunications System UP User Plane UPF User Plane Function URI Uniform Resource Identifier URL Uniform Resource Locator URLLC Ultra-Reliable and Low Latency USB Universal Serial Bus USIM Universal Subscriber Identity Module USS UE-specific search space UTRA UMTS Terrestrial Radio Access UTRAN (Universal Terrestrial Radio Access Network) UwPTS Uplink Pilot Time Slot V2I Vehicle-to-Infrastructure V2P Vehicle-to-Pedestrian V2V Vehicle-to-Vehicle V2X Vehicle-to-everything VIM Virtualized Infrastructure Manager VL Virtual Link, VLAN (Virtual LAN), Virtual Local Area Network VM (Virtual Machine) VNF (Virtualized Network Function) VNF Forwarding Graph VNFFGD VNF Forwarding Graph Descriptor VNFM VNF Manager VNF Manager VoIP (Voice-over-IP, Voice-over-Internet Protocol) VPLMN Visited Public Land Mobile Network VPN (Virtual Private Network) VRB (Virtual Resource Block) WiMAX Worldwide Interoperability for Microwave Access WLAN (Wireless Local Area Network) WMAN Wireless Metropolitan Area Network WPAN Wireless Personal Area Network X2-C X2-Control plane X2-U X2-User plane XML eXtensible Markup Language XRES Expected User Response XOR eXclusive OR exclusive OR ZC Zadoff-Chu ZP Zero Po Zero Power Technical terms For the purposes of this specification, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0132] As used herein, the term “circuit” may refer to, part of, or include hardware components such as electronic circuits, logic circuits, processors (shared, distributed, or grouped), and / or memories (shared, distributed, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), composite PLDs (CPLDs), high-capacitance PLDs (HCPLDs), structured ASICs, programmable SoCs), and digital signal processors (DSPs) configured to provide the functions described. In some embodiments, a circuit may run one or more software or firmware programs that provide at least some of the functions described. The term “circuit” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with program code used to perform the functions of the program code. In such embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuit.

[0133] As used herein, the term “processor circuit” may refer to, a part thereof, or include a circuit capable of sequentially and automatically executing a sequence of arithmetic or logical operations, or recording, storing and / or transferring digital data. A processing circuit may include one or more processing cores that execute instructions, and one or more memory structures that store program and data information. The term “processor circuit” may also refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single-core processors, dual-core processors, triple-core processors, quad-core processors, and / or any other devices capable of executing or otherwise manipulating computer executable instructions, such as program code, software modules, and / or functional processes. A processing circuit may include further hardware accelerators, such as microprocessors and programmable processing devices. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuit” and / or “baseband circuit” may be considered synonymous with “processor circuit” and may be referred to as “processor circuit.”

[0134] As used herein, the term “interface circuit” may refer to, a part thereof, or include a circuit that enables the exchange of information between two or more components or devices. The term “interface circuit” may also refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and / or similar.

[0135] As used herein, the terms “User Equipment” or “UE” refer to a device with wireless communication capabilities and may also refer to a remote user of network resources within a communication network. The terms “User Equipment” or “UE” may be considered synonymous with, and may be referred to as, a client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable wireless equipment, reconfigurable mobile device, etc. Furthermore, the terms “User Equipment” or “UE” may include any type of wireless / wired device or any computing device including a wireless communication interface.

[0136] As used herein, the term “Network Element” refers to physical or virtualized devices and / or infrastructure used to provide wired or wireless network services. The term “Network Element” may be considered synonymous with and / or referred to as networked computers, networking hardware, network devices, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN devices, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, and / or similar.

[0137] As used herein, the term “computer system” refers to any type of interconnected electronic device or component thereof. Furthermore, the terms “computer system” and / or “system” may refer to various components of a computer that are interconnected in a communicative manner. Furthermore, the terms “computer system” and / or “system” may refer to multiple computer devices and / or multiple computing systems that are interconnected in a communicative manner and configured to share computing and / or network resources.

[0138] As used herein, terms such as “appliance” and “computer appliance” refer to a computer device or computer system equipped with program code (e.g., software or firmware) specifically designed to provide a particular computing resource. A “virtual appliance” is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance, or otherwise dedicated to providing a particular computing resource.

[0139] As used herein, the term “resource” means physical or virtual devices, physical or virtual components in a computing environment, and / or physical or virtual components in a particular device, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operation, ports or network sockets, channel / link allocation, throughput, memory utilization, networks, databases and applications, workload units, and / or so. “Hardware resources” may mean computing, storage, and / or network resources provided by physical hardware elements. “Virtualized resources” may mean computing, storage, and / or network resources provided by a virtualization infrastructure to applications, devices, systems, etc. The term “network resources” or “communication resources” may mean resources accessible by computer devices / systems over a communication network. The term “system resources” may mean any kind of shared entity for providing services, and may include computing and / or network resources. System resources may be considered as a set of coherent functions, network data objects, or services accessible through a server, and such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0140] As used herein, the term “channel” refers to any tangible or intangible transmission medium used to communicate data or data streams. The term “channel” may be synonymous and / or equivalent to any other similar term that describes a path or medium through which data is communicated, such as “communication channel,” “data communication channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radio frequency carrier,” and / or any other similar term. Furthermore, as used herein, the term “link” refers to a connection between two devices via a RAT for transmitting and receiving information.

[0141] As used herein, terms such as "instantiate" and "instantiate" refer to the creation of an instance. An "instance" also refers to a specific appearance of an object that may occur, for example, during the execution of program code.

[0142] The terms “joined” and “communicatively joined” are used herein, along with their derivatives. The term “joined” can mean that two or more elements are in direct physical or electrical contact with one another, that two or more elements are in indirect contact with one another but still cooperate or interact with one another, and / or that one or more other elements are joined or connected between the elements said to be joined together. The term “directly joined” can mean that two or more elements are in direct contact with one another. The term “communicatively joined” can mean that two or more elements may be in contact with one another through wired or other interconnect connections, through wireless communication channels or links, and / or by means of communication including the same.

[0143] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains content.

[0144] The term "SMTC" refers to the SSB-based measurement timing settings configured by SSB-MeasurementTimingConfiguration.

[0145] The term "SSB" refers to the SS / PBCH block.

[0146] The term "primary cell" refers to an MCG cell that operates at the primary frequency from which a UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

[0147] The term "primary SCG cell" refers to the SCG cell that performs random access when the UE executes a synchronized reconfiguration procedure for DC operation.

[0148] The term "secondary cell" refers to a cell that provides additional radio resources in addition to the special cell set up by the CA for the UE.

[0149] The term "secondary cell group" refers to a subset of service cells that have a PSCell and zero or more secondary cells for UEs configured by the DC.

[0150] The term "serving cell" refers to the primary cell for an RRC_CONNECTED UE that is not configured by CA / DC, and a primary cell consists of only one serving cell.

[0151] The term "serving cell" or "multiple serving cells" refers to a set of cells that includes a special cell for the UE of RRC_CONNECTED set by CA / and all secondary cells.

[0152] The term "special cell" refers to the PCell or SCGnoPSCell of the MCG for DC operation; otherwise, the term "special cell" refers to the PCell.

Claims

1. A user equipment (UE) device, said device is A memory for storing capability information associated with the aforementioned UE, A processing circuit coupled to the memory, wherein the processing circuit is Based on the capability information of the UE, the position of the uplink control information (UCI) within the physical uplink shared channel (PUSCH) transmission is determined, and the position of the UCI is determined as the earliest discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) symbol before the code block bundle (CBB) that satisfies the UE's capability for the minimum time between the last symbol of the non-periodic channel state information reference signal (CSI-RS) used for measurement and the UCI, and the minimum time between the last symbol of the physical downlink control channel (PDCCH) transmission and the UCI. Encode the PUSCH message for transmission, including the UCI, at the determined location. Including a processing circuit, Device.

2. The apparatus according to claim 1, wherein the capability information of the UE includes an indication of the minimum time between the last symbol of a non-periodic channel state information reference signal (CSI-RS) used for measurement and the UCI.

3. The apparatus according to claim 1, wherein the capability information of the UE includes an instruction for the minimum time between the last symbol of a physical downlink control channel (PDCCH) transmission and the UCI.

4. The apparatus according to claim 1, wherein the position of the UCI is between two adjacent CBBs.

5. The apparatus according to claim 1, wherein the transmission of the UCI in the PUSCH message includes a demodulated reference signal (DM-RS) symbol transmitted in a symbol adjacent to the UCI.

6. The apparatus according to claim 1, wherein the transmission of the UCI in the PUSCH message is performed after the first DM-RS symbol that satisfies the capability in the capability information of the UE.

7. The apparatus according to claim 1, wherein the transmission of the UCI in the PUSCH message is deferred until the end of the uplink (UL) portion of the time-division duplex (TDD) period.

8. The apparatus according to any one of claims 1 to 7, wherein the PUSCH includes uplink shared channel (UL SCH) information.

9. The apparatus according to claim 8, wherein the transmission of the UCI in the PUSCH message is delayed until after the transmission of the UL SCH information.

10. Furthermore, the apparatus according to any one of claims 1 to 7, which receives downlink control information (DCI) from a next-generation NodeB (gNB) that affirms the UCI.

11. The apparatus according to claim 10, wherein the DCI includes an instruction for a Hybrid Automatic Retransmission Request (HARQ) process number associated with the UCI.

12. One or more computer-readable storage media for storing instructions, wherein, when the instructions are executed by one or more processors, they are transmitted to the user equipment (UE). Based on one or more UE capabilities, the position of uplink control information (UCI) to be transmitted with a physical uplink shared channel (PUSCH) transmission is determined, and the position of the UCI is determined as the earliest discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) symbol before the code block bundle (CBB) that satisfies the one or more UE capabilities for the minimum time between the last symbol of the non-periodic channel status reference signal (CSI-RS) used for measurement and the UCI, and the minimum time between the last symbol of the physical downlink control channel (PDCCH) transmission and the UCI. Based on the determined UCI location, encode the PUSCH message for transmission. One or more computer-readable storage media.

13. The computer-readable storage medium according to claim 12, wherein the one or more UE capabilities include indicating the minimum time between the last symbol of a non-periodic channel state information reference signal (CSI-RS) used for measurement and the UCI.

14. The computer-readable storage medium according to claim 12, wherein the one or more UE capabilities include the instruction of the minimum time between the last symbol of a physical downlink control channel (PDCCH) transmission and the UCI.

15. The computer-readable storage medium according to claim 12, wherein the position of the UCI is between two adjacent CBBs.

16. Sending the UCI along with the PUSCH message means that The UCI includes a demodulated reference signal (DM-RS) symbol transmitted in a symbol adjacent to the UCI, or Executed after the first DM-RS symbol that satisfies the capability among the one or more UE capabilities, It will be postponed until the end of the uplink (UL) portion of the time-division duplexing (TDD) period. One or more computer-readable storage media according to claim 12.

17. The PUSCH includes uplink shared channel (UL SCH) information, one or more computer-readable storage media according to any one of claims 12 to 16.

18. The transmission of the UCI in the PUSCH message is delayed until after the transmission of the UL SCH information, one or more computer-readable storage media according to claim 17.

19. The one or more computer-readable storage media further store instructions causing the UE to receive downlink control information (DCI) from the next-generation NodeB (gNB) acknowledging the UCI, the DCI including instructions for a Hybrid Automatic Retransmission Request (HARQ) process number associated with the UCI. One or more computer-readable storage media according to any one of claims 12 to 16.

20. One or more computer-readable storage media for storing instructions, wherein, when the instructions are executed by one or more processors, they are transmitted to a next-generation NodeB (gNB). The user equipment (UE) receives uplink control information (UCI) transmitted along with a physical uplink shared channel (PUSCH) transmission, the position of the UCI in the PUSCH transmission is determined by the UE based on the UE's capability information, and the position of the UCI is determined by the UE as the earliest discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) symbol before a code block bundle (CBB) that satisfies the UE's capability for the minimum time between the last symbol of a non-periodic channel state information reference signal (CSI-RS) used for measurement and the UCI, and the minimum time between the last symbol of a physical downlink control channel (PDCCH) transmission and the UCI. Encode a message for transmission to the UE, which includes downlink control information (DCI) acknowledging the UCI, the DCI including an indication of a Hybrid Automatic Retransmission Request (HARQ) process number associated with the UCI, One or more computer-readable storage media.

21. The computer-readable storage medium according to claim 20, wherein the UCI is transmitted between two adjacent code block bundles (CBBs).

22. The UCI transmitted together with the PUSCH transmission is The UCI includes a demodulated reference signal (DM-RS) symbol transmitted in a symbol adjacent to the UCI, or Executed after a first DM-RS symbol that satisfies the capabilities in the capability information of the aforementioned UE, It will be postponed until the end of the uplink (UL) portion of the time-division duplex (TDD) period. One or more computer-readable storage media according to claim 20.

Images