Determination of transport block size for physical shared channel

Abstract

A network device (e.g., a user equipment (UE), a new radio NB (gNB), or other network component) may process or generate a physical shared channel based on a number of resource blocks determined by one or more formulas of a transport block size (TBS). In response to determining a result of the one or more formulas based on one or more received parameters, a configured action for the physical shared channel may be determined based on the number of resource elements (REs). A radio frequency (RF) interface is configured to provide data for transmitting new radio (NR) communications based on the configured action to the RF circuitry.

Description

Technical Field

[0001] The present disclosure relates to wireless technologies, and more particularly, to transport block size determination for a physical shared channel. Background Art

[0002] Mobile communications have evolved significantly from early voice systems to today's highly complex integrated communications platforms. The next generation of wireless communication systems, 5G or New Radio (NR), will provide access to information and data sharing anytime, anywhere for a variety of users and applications. NR is expected to be a unified network / system designed to meet very different and sometimes conflicting performance dimensions and services. Such different multi-dimensional requirements are driven by different services and applications. In general, NR will evolve based on 3GPP LTE-Advanced with the addition of potential new radio access technologies (RATs) to provide better, simple and seamless wireless connectivity solutions for life. NR will enable everything to be connected wirelessly and provide fast, rich content and services.

[0003] Recently, the first release of the NR (5G) specification provides a set of baseline features and components for future cellular communication systems. It also supports aspects of Ultra-Reliable Low Latency Communication (URLLC) through flexible resource allocation, scheduling and hybrid automatic repeat request (HARQ), low spectrum efficiency transmission parameters, etc. In Release 16, the baseline URLLC functionality needs to be enhanced, and one of the design directions is to further improve the behavior regarding the support of transport block size (TBS) determination. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Figure 1 is an exemplary block diagram illustrating an example of a user equipment (UE) and a next generation Node B (gNB) or access node in a network with network components that can be used in conjunction with the various aspects (implementations) described herein.

[0005] Figure 2 is another exemplary block diagram illustrating a system that can be employed at a UE or a gNB in ​​accordance with various aspects described herein.

[0006] Figure 3 is an exemplary simplified block diagram of a UE wireless communication device or other network device / component (e.g., gNB) according to the various aspects described.

[0007] Figures 4 to 8 is a flow chart of an exemplary process flow that can be employed at a network device for communications in accordance with various aspects described herein.

[0008] Fig. 9 are example information elements for configuring various implementations on a logical channel in accordance with various aspects described herein. DETAILED DESCRIPTION

[0009] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0010] The present disclosure will now be described with reference to the accompanying drawings, wherein throughout the text, similar figure numerals are used to refer to similar elements, and the structures and devices shown therein need not be drawn to scale. As used herein, the terms "component", "system", "interface", etc. are intended to refer to entities, hardware, software (e.g., in execution) and / or firmware related to a computer. For example, a component may be a processor (e.g., a microprocessor, a controller or other processing device), a process running on a processor, a controller, an object, an executable file, a program, a storage device, a computer, a tablet computer, and / or a user equipment (e.g., a mobile phone, etc.) with a processing device. By way of example, an application program and a server running on a server may also be a component. One or more components may reside in a process, and a component may be located on a computer and / or distributed between two or more computers. This article may describe a set of elements or other component sets, wherein the term "set" may be interpreted as "one or more".

[0011] In addition, the components can execute from various computer-readable storage media having various data structures stored thereon, such as using modules, for example. The components can communicate via local and / or remote processes, such as according to signals having one or more data packets (e.g., data from one component interacts with another component in a local system, a distributed system, and / or throughout a network, such as the Internet, a local area network, a wide area network, or a similar network with other systems via signals).

[0012] As another example, a component may be a device having a specific function provided by a mechanical component operated by electrical or electronic circuitry, wherein the electrical or electronic circuitry may be operated by a software application or firmware application executed by one or more processors. The one or more processors may be internal or external to the device and may execute at least a portion of the software or firmware application. As another example, a component may be a device that provides a specific function by an electronic component without the need for a mechanical component; the electronic component may include one or more processors therein to execute at least a portion of the software and / or firmware that imparts the function to the electronic component.

[0013] The use of the word "exemplary" is intended to present concepts in a specific way. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X employs A or B" is intended to mean any natural inclusive arrangement. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied in any of the foregoing cases. In addition, the articles "one" and "an" used in this application and the appended claims should generally be interpreted as meaning "one or more" unless otherwise specified or clear from the context to point to a singular form. In addition, to the extent that the terms "including", "comprising", "having", "having", "with" or variations thereof are used in the detailed description and claims, such terms are intended to be included in a manner similar to the term "comprising". In addition, in the case of discussing one or more numbered items (e.g., "first X", "second X", etc.), generally, one or more numbered items may be different or they may be the same, but in some cases, the context may indicate that they are different or that they are the same.

[0014] As used herein, the term "circuit" may refer to, may be a part of, or may include an application specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or group), or associated memory (shared, dedicated, or group) operably coupled to the circuit that executes one or more software or firmware programs, combinational logic circuits, or other suitable hardware components that provide the described functionality. In some embodiments, the circuit may be implemented in one or more software or firmware modules, or the functions associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, the circuit may include a logic component that is capable of operating at least partially in hardware.

[0015] In view of various concerns about the transport block size (TBS) of a physical shared channel (e.g., a physical uplink shared channel (PUSCH) or a physical downlink shared channel (PDSCH)), various embodiments can ensure that smaller transmissions can be accommodated, especially with respect to the so-called orphan symbol problem being discussed. These embodiments may be advantageous for ultra-reliable low-latency communications and any physical shared channel. In short, due to segmentation, some actual transmissions may consist of one or a few symbols. These symbols may be perceived as carrying no useful information and do not conform to transmissions that may have been triggered by dynamic signaling. Due to these issues, special processing may be facilitated to support such transmissions by user equipment (UE). Therefore, it is conceivable that orphan symbols lack support, for example, in the 3GPP specification, however, the UE behavior regarding orphan symbols may be further clarified.

[0016] Other problems related to so-called orphan symbols can also be solved. More specifically, in ultra-reliable low-latency communications (URLLC), similar conditions to the orphan symbol problem may be encountered, and the determined transport block size (TBS) may be zero. In one embodiment, if the transport block size is zero, the physical uplink shared channel (PUSCH) transmission, physical downlink shared channel (PDSCH) or other such communications may be discarded. In other embodiments, the overhead caused by this particular PUSCH may not be as large as the overhead configured by RRC, then the adjustment of the transport block size calculation formula may be considered and the adjustment may be configured by the configured actions to be taken. This may result in the number of resource elements (REs) to be configured in the TBS being a positive value. Other aspects and details of the present disclosure are further described below with respect to the accompanying drawings.

[0017] The embodiments described herein may be implemented into a system or network device using any suitably configured hardware and / or software. Figure 1 The architecture of a system 100 of a network according to some embodiments is shown. System 100 is shown to include UE 101 and UE 102, which may further represent new radio (NR) devices (e.g., UE or gNB) as discussed herein.

[0018] Figure 1 An exemplary architecture of a system 100 of a network according to various embodiments is shown. The following description is provided for an exemplary system 100 operating in conjunction with LTE system standards and 5G or NR system standards provided by 2GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 2GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0019] like Figure 1As shown, system 100 includes UE 101a and UE 101b (collectively referred to as "UE 101"). In this example, UE 101 is shown as a smart phone (e.g., a handheld touch screen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a consumer electronic device, a cellular phone, a smart phone, a feature phone, a tablet computer, a wearable computer device, a personal digital assistant (PDA), a pager, a wireless handheld device, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-car entertainment (ICE) device, an instrument panel (IC), a head-up display (HUD) device, an on-board diagnostic (OBD) device, a dashtop mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine electronic control unit (ECU), an electronic / engine electronic control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a networked or "smart" appliance, a machine type communication (MTC) device, a machine to machine (M2M) device, an Internet of Things (IoT) device, etc.

[0020] In some embodiments, any of the UEs 101 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a public land mobile network (PLMN), a short-range service (ProSe) or a device-to-device (D2D) communication, a sensor network, or an IoT network. The M2M or MTC data exchange may be a machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0021] UE 101 may be configured to connect (e.g., be communicatively coupled) to a radio access network (RAN) 110. In an embodiment, RAN 110 may be a next generation (NG) RAN or 5G RAN, an evolved-UMTS terrestrial RAN (E-UTRAN), or a legacy RAN such as UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to a RAN 110 operating in an NR or 5G system 100, while the term "E-UTRAN" or the like may refer to a RAN 110 operating in an LTE or 4G system 100. UE 101 utilizes connections (or channels) 102 and 104, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).

[0022] In this example, connection 102 and connection 104 are shown as air interfaces to achieve communication coupling, and may be consistent with a cellular communication protocol, such as a global mobile communication (GSM) protocol, a code division multiple access (CDMA) network protocol, a push-to-talk (PTT) protocol, a cellular PTT (POC) protocol, a universal mobile telecommunications system (UMTS) protocol, a 2GPP LTE protocol, a 5G protocol, a NR protocol, and / or any of the other communication protocols discussed herein. In an embodiment, the UE 101 may directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a SL interface 105 and may include one or more logical channels, including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0023] UE 101b is shown configured to access AP 106 (also referred to as "WLAN node 106," "WLAN 106," "WLAN terminal 106," "WT 106," etc.) via connection 107. Connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 106 will include Wireless Fidelity. router. In this example, AP 106 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 101b, RAN 110, and AP 106 may be configured to utilize LTE-WLAN aggregation (LWA) operation and / or LTE / WLAN radio level operation integrated with IPsec tunnel (LWIP). LWA operation may involve UE 101b in a radio resource control RRC_CONNECTED state being configured by RAN nodes 111a-111b to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 101b using WLAN radio resources (e.g., connection 107) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through connection 107. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0024] The RAN 110 includes one or more access nodes (ANs) or RAN nodes 111a and 111b (collectively referred to as "RAN nodes 111") that enable connections 102 and 104. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, Node Bs, RSUs, transmit receive points (TRxPs), or TRPs, and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN nodes," and the like may refer to RAN nodes 111 (e.g., gNBs) operating in NR or 5G systems 100, while the terms "E-UTRAN nodes," and the like may refer to RAN nodes 111 (e.g., eNBs) operating in LTE or 4G systems 100. According to various embodiments, the RAN node 111 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0025] In some embodiments, all or part of the plurality of RAN nodes 111 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN functional partitioning such as a packet data convergence protocol (PDCP) partitioning, where the radio resource control (RRC) and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 111; a media access control (MAC) / physical (PHY) layer partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 111; or a "lower PHY" partitioning, where the RRC, PDCP, RLC, MAC layer, and upper portions of the PHY layer are operated by the CRAN / vBBUP, and the lower portions of the PHY layer are operated by individual RAN nodes 111. This virtualization framework allows idle processor cores of the plurality of RAN nodes 111 to execute other virtualized applications. In some implementations, the individual RAN nodes 111 may represent individual gNB distributed units (DUs) connected to a gNB central unit (CU) via respective F1 interfaces. In these implementations, the gNB-DU may include one or more remote radio heads or RF front end modules (RFEMs) (not shown), and the gNB-CU may be operated by a server (not shown) located in the RAN 110 or by a server pool in a manner similar to CRAN / vBBUP. In addition or alternatively, one or more of the multiple RAN nodes 111 may be a next generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminals to the UE 101 and is connected to the 5GC via an NG interface.

[0026] In a V2X scenario, one or more of the RAN nodes 111 may be or act as an RSU. The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", etc. In one example, the RSU is a computing device coupled to a radio frequency circuit located on the road side that provides connectivity support to a passing vehicle UE 101 (vUE 101). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz DSRC band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, etc. In addition or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications as well as other cellular communication services. In addition or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weather-resistant enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

[0027] Any of the RAN nodes 111 may serve as a termination point for the air interface protocol and may be the first point of contact for the UE 101. In some embodiments, any of the RAN nodes 111 may perform various logical functions of the RAN 110, including but not limited to the functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0028] In an embodiment, UE 101 may be configured to communicate with each other or with any of RAN nodes 111 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0029] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 111 to the UE 101, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is common practice, which makes radio resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0030] According to various embodiments, the UE 101 and the RAN node 111 communicate data (e.g., transmit data and receive data) through a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed frequency band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed frequency band"). The licensed spectrum may include channels operating in a frequency range of about 400 MHz to about 2.8 GHz, and the unlicensed spectrum may include a 5 GHz frequency band.

[0031] To operate in the unlicensed spectrum, the UE 101 and the RAN node 111 may operate using license assisted access (LAA), eLAA, and / or feLAA mechanisms. In these implementations, the UE 101 and the RAN node 111 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0032] LBT is a mechanism by which equipment (e.g., UE 101, RAN node 111, etc.) senses the medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include a clear channel assessment (CCA) that utilizes at least energy detection (ED) to determine whether other signals are present on the channel in order to determine whether the channel is occupied or clear. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an intended transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0033] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLAN adopts a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 101, AP 106, etc.) intends to transmit, the WLAN node may first perform CCA before transmission. In addition, in the case where more than one WLAN node senses the channel as idle and transmits at the same time, a backoff mechanism is used to avoid conflicts. The backoff mechanism can be a counter randomly introduced within the CWS, which increases exponentially when a conflict occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to CSMA / CA for WLAN. In some implementations, the LBT process for a downlink (DL) or uplink (UL) transmission burst (including a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmission) may have a variable length LAA contention window between X extended CCA (ECCA) slots and Y extended CCA (ECCA) slots, respectively, where X and Y are the minimum and maximum values ​​of the contention window size (CWS) for LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and the maximum channel occupancy time (MCOT) (e.g., a transmission burst) may be based on government regulatory requirements.

[0034] The LAA mechanism is built on the carrier aggregation (CA) technology of the LTE-Advanced system. In CA, each aggregated carrier is called a component carrier (CC). A CC may have a bandwidth of 1.4MHz, 2MHz, 5MHz, 10MHz, 15MHz, or 20MHz, and up to about five or other numbers of CCs may be aggregated, so the maximum aggregate bandwidth may be, for example, about 100MHz. In a frequency division duplex (FDD) system, the number of aggregated carriers may be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC may have a different bandwidth from other CCs. In a time division duplex (TDD) system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0035] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide a primary component carrier (PCC) for both UL and DL, and may handle radio resource control (RRC) and non-access layer (NAS) related activities. Other serving cells are called SCells, and each SCell may provide a single secondary component carrier (SCC) for both UL and DL. SCCs may be added and removed as needed, and changing PCCs may require UE 101 to undergo switching. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by PCells operating in a licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0036] The PDSCH carries user data and higher layer signaling to multiple UEs 101. The physical downlink control channel (PDCCH) carries information about the transport format and resource allocation related to the PDSCH channel, among other things. It may also inform the UE 101 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 101b within a cell) may be performed at any one of the RAN nodes 111 based on channel quality information fed back from any one of the UEs 101. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of the UEs 101.

[0037] PDCCH uses control channel elements (CCE) to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0038] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize an extended (E)-PDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREG. In some cases, ECCE may have other numbers of EREGs.

[0039] The RAN nodes 111 may be configured to communicate with each other via an interface 112. In an embodiment where the system 100 is an LTE system, the interface 112 may be an X2 interface 112. The X2 interface may be defined between two or more RAN nodes 111 (e.g., two or more eNBs, etc.) connected to an evolved packet core (EPC) or core network 120, and / or between two eNBs connected to the EPC 120. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U provides a flow control mechanism for user packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs. For example, X2-U may provide specific sequence number information about user data transmitted from the master eNB (MeNB) to the secondary eNB (SeNB); information about successful in-sequence delivery of PDCP packet data units (PDUs) from the SeNB to the UE 101 for user data; information about PDCP PDUs that were not delivered to the UE 101; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; etc. The X2-C may provide intra-LTE access mobility functions, including context transfer from the source eNB to the target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

[0040] In an embodiment where the system 100 is a 5G or NR system, the interface 112 may be an Xn interface 112. The Xn interface is defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) connected to the 5GC 120, between a RAN node 111 (e.g., a gNB) and an eNB connected to the 5GC 120, and / or between two eNBs connected to the 5GC 120. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 101 in a connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 111. The mobility support may include context transfer from the old (source) serving RAN node 111 to the new (target) serving RAN node 111; and control of the user plane tunnel between the old (source) serving RAN node 111 and the new (target) serving RAN node 111. The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer and a user plane GPRS tunneling protocol (GTP-U) layer on top of a user datagram protocol (UDP) and / or IP layer for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on a stream control transmission protocol (SCTP). SCTP may be on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0041] RAN 110 is shown as being communicatively coupled to a core network—in this embodiment, communicatively coupled to a core network (CN) 120. CN 120 may include a plurality of network elements 122 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 101) connected to CN 120 via RAN 110. The components of CN 120 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 120 may be referred to as a network slice, and a logical instance of a portion of CN 120 may be referred to as a network sub-slice. Network Function Virtualization (NFV) architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more Evolved Packet Core (EPC) components / functions.

[0042] In general, the application server 130 may be an element that provides applications that use IP bearer resources with the core network (e.g., Universal Mobile Telecommunications System Packet Service (UMTS PS) domain, LTE PS data service, etc.). The application server 130 may also be configured to support one or more communication services for the UE 101 via the EPC 120 (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.).

[0043] In an embodiment, CN 120 may be a 5GC (referred to as “5GC 120”, etc.), and RAN 110 may be connected to CN 120 via an NG interface 112. In an embodiment, NG interface 112 may be divided into two parts: a next generation (NG) user plane (NG-U) interface 114, which carries traffic data between RAN node 111 and user plane function (UPF); and an S1 control plane (NG-C) interface 115, which is a signaling interface between RAN node 111 and access and mobility management function (AMF). Core network CN 120 may also be 5GC 120.

[0044] In an embodiment, CN 120 may be a 5G CN (referred to as "5GC 120", etc.), while in other embodiments, CN 120 may be an EPC. In the case where CN 120 is an EPC (referred to as "EPC 120", etc.), RAN 110 may be connected to CN 120 via an S1 interface 112. In an embodiment, S1 interface 112 may be divided into two parts: an S1 user plane (S1-U) interface 114, which carries traffic data between RAN node 111 and S-GW; and an S1-MME interface 115, which is a signaling interface between RAN node 111 and MME.

[0045] Figure 2 Exemplary components of a device 200 according to some embodiments are shown. In some embodiments, the device 200 may include at least an application circuit 202, a baseband circuit 204, a radio frequency (RF) circuit 206, a front-end module (FEM) circuit 208, one or more antennas 210, and a power management circuit (PMC) 212 coupled together as shown. The components of the illustrated device 200 may be included in a UE or a RAN node, such as a UE 101 / 102 or an eNB / gNB 111 / 112. In some embodiments, the device 200 may include fewer elements (e.g., the RAN node cannot utilize the application circuit 202, but includes a processor / controller to process IP data received from the EPC). In some embodiments, the device 200 may include additional elements, such as a memory / storage device, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the following components may be included in more than one device (e.g., the circuit may be included separately in more than one device for a cloud-RAN (C-RAN) implementation).

[0046] The application circuit 202 may include one or more application processors. For example, the application circuit 202 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include a memory / storage device, and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the device 200. In some embodiments, the processor of the application circuit 202 may process IP data packets received from the EPC.

[0047] The baseband circuit 204 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The baseband circuit 204 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuit 206 and generate baseband signals for the transmit signal path of the RF circuit 206. The baseband processing circuit 204 may interact with the application circuit 202 to generate and process baseband signals and control the operation of the RF circuit 206. For example, in some embodiments, the baseband circuit 204 may include a third generation (3G) baseband processor 204A, a fourth generation (4G) baseband processor 204B, a fifth generation (5G) baseband processor 204C, or other baseband processors 204D of other existing generations, under development, or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuit 204 (e.g., one or more baseband processors 204A-D) may handle various radio control functions, which may communicate with one or more radio networks via the RF circuit 206. In other embodiments, some or all of the functions of the baseband processors 204A-D may be included in a module stored in the memory 204G and executed via the central processing unit (CPU) 204E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 204 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 204 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments.

[0048] In addition, memory 204G (and other memory components discussed herein, such as memory, data storage device, etc.) may include one or more machine-readable media, including instructions, which when executed by the machine or component herein, cause the machine to perform the method or device or system for concurrent communication using multiple communication technologies according to the embodiments and examples described herein. It should be understood that the aspects described herein can be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, the function can be stored as one or more instructions or codes on a computer-readable medium (e.g., a memory or other storage device described herein) or transmitted by a computer-readable medium. Computer-readable media include both computer storage media and communication media, and the communication media include any media that helps to transfer a computer program from one place to another. Storage media or computer-readable storage devices can be any available media that can be accessed by a general or special-purpose computer. By way of example only and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, disk storage devices or other magnetic storage devices or other tangible and / or non-transient media, which can be used to carry or store required information or executable instructions. Moreover, any connection may also be referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.

[0049] In some embodiments, the baseband circuit 204 may include one or more audio digital signal processors (DSPs) 204F. The audio DSP 204F may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be appropriately combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 204 and the application circuit 202 may be implemented together, such as, for example, on a system on a chip (SOC).

[0050] In some embodiments, baseband circuitry 204 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 204 may support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), wireless personal area network (WPAN). Embodiments in which baseband circuitry 204 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0051] RF circuit 206 can communicate with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 206 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 206 may include a receive signal path, which may include circuits that down-convert RF signals received from FEM circuit 208 and provide baseband signals to baseband circuit 204. RF circuit 206 may also include a transmit signal path, which may include circuits that up-convert baseband signals provided by baseband circuit 204 and provide RF output signals to FEM circuit 208 for transmission.

[0052] In some embodiments, the receive signal path of the RF circuit 206 may include a mixer circuit 206a, an amplifier circuit 206b, and a filter circuit 206c. In some embodiments, the transmit signal path of the RF circuit 206 may include a filter circuit 206c and a mixer circuit 206a. The RF circuit 206 may also include a synthesizer circuit 206d for synthesizing the frequencies used by the mixer circuit 206a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 206a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 208 based on the synthesized frequency provided by the synthesizer circuit 206d. The amplifier circuit 206b may be configured to amplify the down-converted signal, and the filter circuit 206c may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 204 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required.In some embodiments, the mixer circuit 206a of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0053] In some embodiments, mixer circuit 206a of the transmit signal path can be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 206d to generate an RF output signal for FEM circuit 208. The baseband signal can be provided by baseband circuit 204 and can be filtered by filter circuit 206c.

[0054] In some embodiments, the mixer circuit 206a of the receiving signal path and the mixer circuit 206a of the transmission signal path may include two or more mixers and may be arranged for orthogonal down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 206a of the receiving signal path and the mixer circuit 206a of the transmission signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 206a of the receiving signal path and the mixer circuit 206a of the transmission signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 206a of the receiving signal path and the mixer circuit 206a of the transmission signal path may be configured for superheterodyne operation.

[0055] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuit 206 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 204 may include a digital baseband interface to communicate with RF circuit 206.

[0056] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0057] In some embodiments, synthesizer circuit 206d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, synthesizer circuit 206d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0058] Synthesizer circuit 206d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 206a of RF circuit 206. In some embodiments, synthesizer circuit 206d may be a fractional-N / N+1 synthesizer.

[0059] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by baseband circuitry 204 or application processor 202 depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by application processor 202.

[0060] The synthesizer circuit 206d of the RF circuit 206 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a D-type flip-flop set. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0061] In some embodiments, the synthesizer circuit 206d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 206 can include an IQ / polarity converter.

[0062] The FEM circuitry 208 may include a receive signal path that may include circuitry configured to operate on RF signals received from the one or more antennas 210, amplify the received signals, and provide an amplified version of the received signals to the RF circuitry 206 for further processing. The FEM circuitry 208 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 206 for transmission via one or more of the one or more antennas 210. In various embodiments, amplification by either the transmit or receive signal path may be accomplished only in the RF circuitry 206, only in the FEM 208, or in both the RF circuitry 206 and the FEM 208.

[0063] In some embodiments, the FEM circuit 208 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 206). The transmit signal path of the FEM circuit 208 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuit 206), and one or more filters to generate an RF signal for subsequent transmission (e.g., through one or more of the one or more antennas 210).

[0064] In some embodiments, PMC 212 can manage the power provided to baseband circuit 204. Specifically, PMC 212 can control power selection, voltage scaling, battery charging, or DC-DC conversion. When device 200 is capable of being powered by a battery, for example, when the device is included in a UE, PMC 212 can generally be included. PMC 212 can improve power conversion efficiency while providing a desired implementation size and heat dissipation characteristics.

[0065] and Figure 2 PMC 212 is shown coupled only to baseband circuitry 204. However, in other embodiments, PMC 212 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuitry 202, RF circuitry 206, or FEM 208) and perform similar power management operations.

[0066] In some embodiments, the PMC 212 may control or otherwise be part of various power saving mechanisms of the device 200. For example, if the device 200 is in the RRC_Connected state, where it is still connected to the RAN node as expected to receive traffic soon, then after a period of inactivity, it may enter a state known as discontinuous reception mode (DRX). During this state, the device 200 may be powered off for short time intervals, thereby saving power.

[0067] If there is no data traffic activity for an extended period of time, the device 200 may transition to the RRC_Idle state, in which it is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device 200 enters a very low power state, and it performs paging, in which it wakes up periodically again to listen to the network, and then powers down again. The device 200 cannot receive data in this state, and in order to receive data, it must transition back to the RRC_Connected state.

[0068] An additional power saving mode can keep a device from using the network for longer than the paging interval (which can range from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0069] The processor of the application circuit 202 and the processor of the baseband circuit 204 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 204 can be used alone or in combination to perform the functions of Layer 3, Layer 2, or Layer 1, while the processor of the application circuit 204 can utilize data received from these layers (e.g., packet data) and further perform the functions of Layer 4 (e.g., Transport Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, Layer 3 may include a radio resource control (RRC) layer, which will be described in further detail below. As mentioned herein, Layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, Layer 1 may include a physical (PHY) layer of a UE / RAN node, which will be described in further detail below.

[0070] refer to Figure 3 , a block diagram of a user equipment wireless communication device (UE) or other network device / component (e.g., a gNB, eNB, or other participating entity) is shown. The UE device 300 includes: one or more processors 310 (e.g., one or more baseband processors), the one or more processors including processing circuits and associated interfaces; transceiver circuits 320 (e.g., including RF circuits, the RF circuits may include transmitter circuits (e.g., associated with one or more transmit chains) and / or receiver circuits (e.g., associated with one or more receive chains), the transmitter circuits and receiver circuits may use common circuit elements, different circuit elements, or a combination thereof); and a memory 330 (which may include any of a variety of storage media and may store instructions and / or data associated with one or more of the processors 310 or the transceiver circuits 320).

[0071] In various embodiments (aspects) discussed herein, a signal or message may be generated and output for transmission, and / or a transmitted message may be received and processed. Depending on the type of signal or message generated, output for transmission (e.g., by processor 310, processor 310, etc.) may include one or more of the following operations: generating a set of associated bits encoding the content of the signal or message; encoding (e.g., may include adding a cyclic redundancy check (CRC) and / or encoding via a turbo code, a low-density parity check (LDPC) code, a tail-biting convolutional code (TBCC), etc.); scrambling (e.g., based on a scrambling seed); modulation (e.g., via one of binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), or some form of quadrature amplitude modulation (QAM), etc.); and / or resource mapping (e.g., mapping to a scheduled resource set, mapping to a time and frequency resource set authorized for uplink transmission, etc.). Depending on the type of signal or message received, processing (e.g., by processor 310) may include one or more of the following operations: identifying physical resources associated with the signal / message, detecting the signal / message, resource element group deinterleaving, demodulating, descrambling and / or decoding.

[0072] According to various embodiments, various types of PUSCH can be performed in two ways: Type A, as a time slot-based repetition, that is, the same time domain allocation can be used for the repeated time slots, in particular, the starting symbol in each time slot in the aggregation, the duration of the PUSCH and the PUSCH mapping type are the same and are derived from the time domain resource allocation field of the DCI that schedules the PUSCH or activates the type 2 configured grant (CG)-PUSCH; Type B, as back-to-back repetition (or minimum repetition, tiny repetition), that is, the start symbol of the repetition different from the initial repetition is derived based on the end symbol of the previous repetition or based on other rules / indications, so that the repetition can be performed even within one time slot, or with minimum gaps / no gaps in different time slots.

[0073] Basically, type B may be a mechanism to repeat the time domain resource allocation on a back-to-back (or continuous) basis rather than on a slot basis, such that the time domain resource allocation gives the starting symbol and the duration of the initial transmission, and the repetition begins with the next available symbol (e.g., symbol 0 in slot n+1 with repetition, in the next slot, or in other examples within the slot), even if it can be done in the same slot, such that the duration is given by the duration of the initial transmission; however, the starting symbol of the repetition is given by finding the next available symbol of the previous repetition. Thus, type B repetition may be different from type A repetition.

[0074] In one embodiment, the transport block size (TBS) determination may be configured by the UE 101, 200 or 300 through the procedures found in the appendix of Technical Specification (TS) 38.214). A key parameter that may be utilized may be the number of REs available for transmission, N′ RE Specifically, the number of REs available for PUSCH transmission is N′ RE The representation can be as follows: Where N′ RE is the number of REs available for PUSCH transmission within a physical resource block (PRB), where is the number of subcarriers in the frequency domain in the physical resource block, where is the number of symbols allocated to the physical shared channel in a time slot, where is an overhead parameter configured through higher layer signaling based on the serving cell configuration of the information element with respect to different signal durations of PUSCH transmission or PDSCH transmission as a physical shared channel, and wherein is the number of REs used for demodulation reference signal (DMRS) per physical resource block (PRB) in the allocated duration including the overhead of DM-RS code division multiplexing (CDM) groups without data. Provides the total number of REs in a PRB and PUSCH allocation of symbols. Parameters It can be the overhead configured by the higher layer parameter xOverhead in PUSCH-ServingCellConfig, which can take values ​​from 0, 6, 12, 18. For PDSCH, the parameter It can be the overhead configured by the higher layer parameter xOverhead in PDSCH-ServingCellConfig, which can take values ​​from 0, 6, 12, and 18.

[0075] The UE 101, 200 or 300 may be configured to first determine the available REs in a single PRB, or calculate the number of REs available for PRB transmission. For example, the formula In terms of It can be 12, which can be fixed to 12 and not affected by changes. This is the number of tones in one PRB in NR transmission. It can be, for example, two symbols, but changes dynamically as indicated, for example, by RRC or higher layer signaling. The third term is the number of DMRS or DMRS overhead. It may be 6, for example. DMRS may be configuration type 1 or configuration type 2. For configuration type 1, for example, a continuous structure is enabled, and for example, in this configuration example, ie, configuration type 1 of DMRS, Can be 6. The 18 REs that may be configured as an overhead of other resources as a fixed RRC configuration and cannot be changed with dynamic signaling.

[0076] A normal transmission can be anything from 1 symbol to 14 symbols. Therefore, the overhead may be too much only in certain cases, where only two symbols are transmitted, but in other cases more symbols are transmitted. This can be a problem, where the overhead is difficult to adapt to URLLC communications because it is RRC configured and is not affected by changes in transmission duration, for example, where it is generally preferred to be able to transmit with a small number of symbols, and the so-called orphan symbol problem discussed above. Since this RRC configuration varies, transmissions are not always possible with a very small number of symbols.

[0077] In URLLC, since a nominal transmission can be anywhere from 1 symbol to 14 symbols, the budget overhead may be too much for short transmissions. (For example, for a single symbol configuration type 1 DMRS, 6 REs), Then in the case where 2 OFDM symbols are used for PUSCH nominal transmission, then Therefore, from the perspective of UE implementation, the number N′ RE In the case where it is technically zero or even a negative number, then the UE will not transmit anything on a given transmission.

[0078] Since the nominal PUSCH has a small duration, if the same approach of using cell-common parameters (PUSCH-ServingCellConfig→xOverhead) for PUSCH transmission can be adopted, then in many cases, if the signal duration (L) is too small, N′ RE Can be a negative number. As described herein, for PDSCH, it is possible to consider N′ based on that used for PUSCH. RE The same modified alternative.

[0079] refer to Figure 4 , shows an exemplary processing flow for determining a transport block size according to one or more configured actions for a network device (e.g., UE 101, gNB 110, etc.) for determining TBS in accordance with the implementation scheme of this document.

[0080] At 410, a process flow may be initiated in which one or more parameters related to a physical shared channel are processed for determining a transport block size. The one or more parameters may include, for example, at least one of the following: the number of subcarriers in the frequency domain in a physical resource block; The number of symbols allocated to the physical shared channel in a time slot Overhead parameters configured via higher layer signaling for serving cell configuration based on information elements with respect to different signal durations for PUSCH transmissions or PDSCH transmissions as physical shared channel or the number of REs used for demodulation reference signal (DMRS) per physical resource block (PRB) in the allocated duration including the overhead of DM-RS code division multiplexing (CDM) groups without data

[0081] At 420, the process flow 400 may also include configuring a formula based on one or more parameters to determine the number of resource elements (REs) for a physical shared channel within a physical resource block (PRB). At 430, the process flow also includes determining the number of REs N′ based on the formula and any one or more of the one or more parameters. RE . For example, the formula could be: Or a different formula in other embodiments. At 440, the process flow also includes transmitting a transmission based on the configured action for the physical shared channel and the determination of the number of REs. Then at A, the process flow may continue with other embodiments.

[0082] refer to Figure 5 , showing a process flow that can continue from or be independent of process flow 400 Figure 4 The process flow 500 of the process flow 400 of the embodiment of the present invention is used to determine the TBS in the physical shared channel. For example, the process flow 500 can be initiated at 510, where it is determined whether the formula meets the threshold value of the signal duration of the PUSCH transmission or PDSCH as the physical shared channel. At 520, the process flow 500 may include determining whether to discard the transmission or perform a different configured action in response to whether the formula meets the threshold value. Here, the different configured actions can be, for example, reformulating the formula or modifying the formula, determining different thresholds, or other aspects disclosed in the present disclosure.

[0083] In one embodiment, In the case of RE If the RE number count N′ is negative or zero, the UE 101, 200 or 300 may perform the configured action. In this case, the configured action includes discarding the actual transmission (i.e., no PUSCH transmission). Here, the RRC configured overhead may be applied to transmissions of all durations. This can be achieved to avoid the UE from continuing to work hard, and therefore, the UE 101, 200, 300 may be signaled or pre-configured to REIf is negative or zero, the actual transmission is discarded and not performed. Therefore, the configuration of the information element or any options are not changed.

[0084] refer to Figure 6 , showing that Figure 4 Processing flow 400 or Figure 5 Process flow 600 may be a continuation of process flow 500 or independent of process flow 400 or 500 for determining a TBS in a physical shared channel. For example, process flow 600 may be initiated at 610, where it is determined whether the formula meets a threshold (such as, for example, the number of REs is zero or a negative value according to the formula). At 620, process flow 600 may also include, in response to the result not meeting the threshold value of the signal duration of the PUSCH or PDSCH, modifying the formula to another formula, wherein the other or second formula may include a different number of terms based on one or more parameters than the formula.

[0085] For example, UE 101, 200, or 300 may calculate a formula where And when N′ RE When N is negative or zero, the following modified formula is used to recalculate N′ as follows: RE : Here, when N′ in the original formula RE When N is negative or zero, an alternative formula is used to determine N′ for transmission. RE This second modified / alternative formula may, for example, discard overhead items configured according to higher layer parameters. This may reduce transmission overhead for other transmissions such as for sounding reference signals (SRS) and reduce RRC overhead.

[0086] refer to Figure 7 , showing that Figure 4 Processing flow 400, Figure 5 Processing flow 500 or Figure 6 Process flow 700 may be a continuation of process flow 600 or may be independent of process flow 400, 500, or 600 for determining a TBS in a physical shared channel. Process flow 700 may be initiated at 710, where a determination is made as to whether a formula satisfies a threshold, such as whether the number of REs is zero or a negative value according to the formula. At 720, process flow 700 may also include, in response to the result not satisfying a threshold value for a signal duration of a PUSCH or PDSCH, modifying the formula to another formula having a proportional term. Here, the first formula may be modified or replaced with a second formula having a proportional term, the proportional term being based on an overhead parameter configured by the RRC. The number of REs (N′) is configured as a ratio of the nominal PUSCH duration or the nominal PDSCH duration of the nominal transmission. RE).

[0087] At 730, process flow 700 can include determining whether to drop the transmission or perform a different configured action in response to whether the formula satisfies a threshold value.

[0088] In an embodiment, for all cases, UE 101, 200 or 300 may set N' RE Use the following modified formula: If N′ RE If is negative or zero, the actual transmission is discarded (i.e., no PUSCH transmission); with this solution, the assumed overhead can be proportional to the nominal PUSCH duration. Specifically, the proportional term may include: Thus, the proportional term includes the number of symbols allocated by the physical shared channel within the time slot of a nominal PDSCH or PUSCH transmission, and the configured action includes dropping transmissions via the physical shared channel.

[0089] refer to Figure 8 , showing that Figure 4 Processing flow 400 to Figure 7 Process flow 800 may be a continuation of process flow 700 or may be independent of process flow 400, 500, 600, or 700 for determining TBS in a physical shared channel. Process flow 800 may be initiated at 810, where it is determined whether the formula satisfies a threshold (such as, for example, the number of REs is zero or a negative value according to the formula). At 820, process flow 800 also includes determining whether to utilize a modification of the first formula or use the second formula based on the number of transmitted symbols being less than a threshold signal duration (e.g., L=7 or other). At 830, process flow 800 may utilize the modified first formula or the second formula in response to the modified first formula or the second formula being greater than zero, and in response to a negative value or a zero value, drop the physical shared channel according to the configured action.

[0090] For example, if is less than the threshold (for example, when L=7), the formula can be modified as Use or modify Otherwise, use the original formula If N′ RE If t is negative or zero, the actual transmission is discarded (ie, no PUSCH or PDSCH transmission).

[0091] Alternatively or additionally, if is less than the threshold, the UE 101, 200 or 300 may configure or if If it is greater than the threshold, then Here, UE 101, 200 or 300 configures at least two different thresholds based on the number of symbols allocated by PUSCH or PDSCH. Therefore, different levels of values ​​of the configured overhead parameters can then be determined based on the number of symbols allocated by PUSCH or PDSCH associated with the at least two different thresholds.

[0092] Alternatively, depending on UE 101, 200 or 300 may be configured with multiple levels of For example, if but if but if but Where x1≤x2≤xoverhead. Thus, at least two different thresholds are based on the number of symbols allocated by PUSCH or PDSCH, and the values ​​of different levels of the configured overhead parameter may be determined based on the number of symbols allocated by PUSCH or PDSCH associated with the at least two different thresholds.

[0093] In this paper N′ RE Any actual repetition under a nominal repetition of ≤ 0 may be considered an orphan symbol transmission of an actual transmission at one OFDM symbol, for example, and the UE discards the actual transmission.

[0094] Note that one motivation for the proposed implementation is to avoid zero TBS size allocation. In Rel-16, PDSCH type B with 1, 2, 3, 4, ..., 13 symbols can be supported. For TBS size determination, the following formula can be used for PUSH In addition, for DL, is determined from the xOverhead signaled in PDSCH-ServingCellConfig and takes values ​​from {6, 12, 18}. For PDSCH as discussed in the embodiments herein, N′ based on that used for PUSCH may be considered. RE The same modified alternative.

[0095] In another embodiment, the number of PRB allocations is considered as another factor for determining which formula to use (i.e., between the original formula in the TS 38.214 specification and any of the modifications proposed herein). In one example, if the number of PRB allocations or the number of PRB allocations is different from In another example, if the product of the number of PRB allocations or the number of PRB allocations is less than the threshold, the modification is adopted. If the product of is higher than the threshold, the modification is adopted.

[0096] Fig. 9 An exemplary information element for PDSCH serving cell configuration is shown. This may be signaled by the gNB 111, 200, or 300 to the UE 101, 200, or 300, for example, to configure one or more of the parameters. For example, the configuration elements of IE can be as follows: PDSCH-ServingCellConfig::=SEQUENCE{codeBlockGroupTransmissionSetupRelease{PDSCH-CodeBlockGroupTransmission}OPTIONAL,--Need M;xOverheadENUMERATED{xOh6,xOh12,xOh18}OPTIONAL,--Need S;nrofHARQ-ProcessesForPDSCHENUMERATED{n2,n4,n6,n10,n12,n16}OPTIONAL,--Need S pucch-Cell ServCellIndexOPTIONAL,--Cond SCellAddOnly...,[[maxMIMO-Layers INTEGER(1..8)OPTIONAL,--NeedMprocessingType2Enabled BOOLEANOPTIONAL--Need M]]}

[0097] The appendix to section 6.1.4.2 of TS 38.214 states as follows: Transport block size determination is:

[0098] For PUSCH scheduled by RAR U grant, or for PUSCH scheduled by DCI format 0_0 with CRC scrambled with C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI, or for PUSCH scheduled by DCI format 0_1 ​​with CRC scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI, SP-CSI-RNTI, or for PUSCH transmission with configured grant; if 0≤I MCS ≤27 ​​and transform precoding is disabled and Table 5.1.3.1-2 is used, or 0≤I MCS ≤28 and transform precoding is disabled and a table other than Table 5.1.3.1-2 is used, or 0≤I MCS ≤27 ​​and transform precoding is enabled, the UE shall first determine the TBS as follows: The UE shall first determine the number of REs in the time slot (N RE ):UE first passes Determine the number of REs (N′) allocated for PUSCH within a PRBRE ),in is the number of subcarriers in the frequency domain in the physical resource block, is the number of symbols allocated by PUSCH in a time slot, is the number of REs used for DM-RS per PRB in the allocated duration, including the overhead of DM-RS CDM groups without data, as described in subclause 6.1.2.3 for PUSCH with configured grants, or as indicated in DCI format 0_1, or as described in subclause 6.2.2 for DCI format 0_0, and It is the overhead configured by the higher layer parameter xOverhead in PUSCH-ServingCellConfig. If not configured (a value of 6, 12, or 18), then Assume it is 0. For Msg3 transmission, Always set to 0. UE passes N RE =min(156,N′ RE )·n PRB Determine the total number of REs allocated for PUSCH (N RE ), where n PRB is the total number of allocated PRBs for the UE. Next, the procedure continues with steps 2-4 as defined in subclause 5.1.3.2.

[0099] As used in this specification, the term "processor" may refer to substantially any computing processing unit or device, including but not limited to single-core processors; single processors with software multi-threaded execution capabilities; multi-core processors; multi-core processors with software multi-threaded execution capabilities; multi-core processors with hardware multi-threading technology; parallel platforms; and parallel platforms with distributed shared memory. In addition, a processor may refer to an integrated circuit, an application-specific integrated circuit, a digital signal processor, a field programmable gate array, a programmable logic controller, a complex programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions and / or processes described herein. The processor may utilize nanoscale architectures, such as but not limited to molecular and quantum dot-based transistors, switches, and gates, in order to optimize space usage or enhance the performance of mobile devices. The processor may also be implemented as a combination of computing processing units.

[0100] Examples may include subject matter, such as a method, an apparatus for performing the actions or blocks of the method, and at least one machine-readable medium comprising instructions that, when executed by a machine (e.g., a processor with memory, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), cause the machine to perform the actions of a method or apparatus or system for concurrent communication using multiple communication technologies according to the embodiments and examples described herein.

[0101] The first embodiment is a device configured to be employed in a user equipment (UE), the device comprising: one or more processors, the one or more processors being configured to: process one or more parameters related to a physical shared channel for determining a transport block size; generate a determination of the number of resource elements (REs) used for the physical shared channel within a physical resource block (PRB) based on a first value derived from the one or more parameters; and generate a configured action for the physical shared channel based on the determination of the number of resource elements (REs); and a radio frequency (RF) interface, the RF interface being configured to provide data for transmission based on the configured action to the RF circuit.

[0102] A second embodiment may include the first embodiment, wherein the one or more processors are further configured to generate the determination by determining whether the first value indicates an integer value greater than a threshold value of a signal duration of a physical uplink shared channel (PUSCH) transmission or a physical downlink shared channel (PDSCH) transmission as a physical shared channel.

[0103] A third embodiment may include the first embodiment or the second embodiment, wherein the one or more processors are further configured to: provide a negative value or a zero value in response to the first value, discard the physical shared channel according to the configured action, and apply overhead parameters configured by radio resource control (RRC) of the service cell configuration based on the information element for different signal durations relative to PUSCH transmission or PDSCH transmission as the physical shared channel.

[0104] A fourth embodiment may include one or more of the first to third embodiments, wherein the one or more parameters include at least one of the following: the number of subcarriers in the frequency domain in the physical resource block; The number of symbols allocated to the physical shared channel in a time slot Overhead parameters configured via higher layer signaling based on information element serving cell configuration for different signal durations relative to PUSCH transmission or PDSCH transmission and the number of demodulation reference signals (DM-DM) per physical shared resource block (PRB) in the allocated duration including the overhead of DM-RS code division multiplexing (CDM) groups without data

[0105] A fifth embodiment may include any one or more of the first to fourth embodiments, wherein the one or more processors are further configured to: in response to the first value providing a negative number or zero according to a first formula, modify the first formula to a second formula, wherein the second formula includes one or more parameters of a different number from the first formula, and the second formula is expressed as follows: or And the first formula is expressed as follows:

[0106] The sixth embodiment may include any one or more of the first embodiment to the fifth embodiment, wherein the first value is derived from a first formula including a proportional term, the proportional term being based on an overhead parameter configured by RRC. The number of REs (N′) is configured as a ratio of the nominal PUSCH duration or the nominal PDSCH duration of the nominal transmission. RE ).

[0107] The seventh embodiment may include any one or more of the first embodiment to the sixth embodiment, wherein the proportional term also includes the number of symbols allocated by the physical shared channel within the time slot of the nominal transmission, and the configured action includes discarding the transmission via the physical shared channel in response to the first formula indicating a negative value or zero value, and modifying the signal duration of the transmission in response to the first formula indicating that the number of REs is higher than zero and lower than a threshold signal duration.

[0108] The eighth embodiment may include any one or more of the first to seventh embodiments, wherein the one or more processors are further configured to: in response to the first formula providing a negative number or zero, modify the first formula to a second formula, wherein the second formula includes one or more parameters of a different number than the first formula.

[0109] The ninth embodiment may include any one or more of the first to eighth embodiments, wherein the one or more processors are further configured to determine whether to utilize a modification from a first formula providing a first value to a second formula providing a second value based on the number of transmitted symbols being less than a threshold signal duration.

[0110] The tenth embodiment may include any one or more of the first to ninth embodiments, wherein the one or more processors are further configured to: in response to the modified first formula or the second formula providing the second value being greater than zero, utilize the modified first formula or the second formula, and in response to a negative value or a zero value, discard the physical shared channel according to the configured action.

[0111] The eleventh embodiment may include any one or more of the first to tenth embodiments, wherein the one or more processors are further configured to: process one or more parameters including a configured overhead parameter, wherein the configured overhead parameter is zero in response to the number of symbols allocated by the PUSCH or PDSCH being less than a threshold number, or the configured overhead parameter is equal to the overhead parameter configured by the serving cell of the information element from the PUSCH or PDSCH.

[0112] The twelfth embodiment may include any one or more of the first to eleventh embodiments, wherein the one or more processors are further configured to: configure at least two different thresholds based on the number of symbols allocated by PUSCH or PDSCH; and determine different levels of the value of the configured overhead parameter based on the number of symbols allocated by PUSCH or PDSCH associated with the at least two different thresholds.

[0113] The thirteenth embodiment is a tangible computer-readable storage device that stores executable instructions that, in response to execution, cause one or more processors of a user equipment (UE) for transmission to perform operations, the operations including: processing one or more parameters related to a physical shared channel for determining a transport block size (TBS); configuring a formula based on the one or more parameters to determine the number of resource elements (REs) used for a physical shared channel within a physical resource block (PRB); determining the number of REs based on the formula; and transmitting the transmission based on the configured action for the physical shared channel and the determination of the number of REs.

[0114] The fourteenth embodiment includes the thirteenth embodiment, wherein the operations further include: determining whether the formula satisfies a threshold value of a signal duration of a physical uplink shared channel (PUSCH) transmission or a physical downlink shared channel (PDSCH) as a physical shared channel; and determining whether to discard the transmission or perform a different configured action in response to whether the formula satisfies the threshold value.

[0115] The fifteenth embodiment may include any one or more of the thirteenth to fourteenth embodiments, wherein the operations further include: in response to not meeting a threshold value of the signal duration of the PUSCH or PDSCH, modifying the formula into another formula, wherein the other formula includes a different number of terms based on one or more parameters than the formula.

[0116] The sixteenth embodiment may include any one or more of the thirteenth to fifteenth embodiments, wherein the operations further include: determining whether to utilize a modification of the formula or another formula based on the number of transmitted symbols being less than a threshold signal duration, wherein the formula or the other formula includes a proportional term that configures the number of REs based on a ratio of an RRC-configured overhead parameter to a nominal PUSCH duration or a PDSCH duration; and determining the TBS based on the number of available resource elements (REs).

[0117] The seventeenth embodiment is an apparatus configured to be employed at a network device including a user equipment (UE) or a next generation node B (gNB), the apparatus comprising: one or more processors, the one or more processors configured to: determine the number of resource elements (REs) for a physical shared channel within a physical resource block (PRB) based on a first value derived from one or more parameters; and determine a configured action for the physical shared channel based on the number of resource elements (REs); a radio frequency (RF) interface, the RF interface configured to provide data for transmitting communications based on the configured action to the RF circuit.

[0118] An eighteenth embodiment may include the seventeenth embodiment, wherein the one or more parameters include at least one of the following: the number of subcarriers in the frequency domain in the physical resource block; The number of symbols allocated to the physical shared channel in a time slot Overhead parameters configured via higher layer signaling based on information element serving cell configuration for different signal durations relative to PUSCH transmission or PDSCH transmission and the number of demodulation reference signals (DM-DM) per physical shared physical resource block (PRB) in the allocated duration including the overhead of DM-RS code division multiplexing (CDM) groups without data

[0119] A nineteenth embodiment may include any one or more of the seventeenth to eighteenth embodiments, wherein the one or more processors are further configured to: in response to the first formula providing a negative number or zero as the first value, modify the first formula providing the first value to a second formula, wherein the second formula includes one or more parameters of a different number from the first formula.

[0120] The twentieth embodiment may include any one or more of the seventeenth to nineteenth embodiments, wherein the second formula includes a proportional term that configures the number of REs based on a ratio of an overhead parameter configured by RRC to a nominal PUSCH duration and the number of symbols allocated to a physical shared channel within a time slot.

[0121] The twenty-first embodiment may include any one or more of the seventeenth to twentieth embodiments, wherein the one or more processors are further configured to: in response to the first formula indicating a negative value or a zero value, discard the PUSCH transmission, otherwise modify the signal duration based on the number of REs used for URLLC communication.

[0122] The twenty-second embodiment may include any one or more of the seventeenth to twenty-first embodiments, wherein the one or more processors are further configured to: process one or more parameters including a configured overhead parameter, wherein the configured overhead parameter is zero in response to the number of symbols allocated by the PUSCH being less than a threshold number, or the configured overhead parameter is equal to an overhead parameter configured by a serving cell from an information element of the PUSCH.

[0123] An embodiment may include one or more non-transitory computer-readable media that include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of the above-described embodiments or any other method or process described herein.

[0124] In addition, various aspects or features described herein may be implemented as methods, devices or articles using standard programming and / or engineering techniques. As used herein, the term "article" is intended to cover a computer program accessible from any computer-readable device, carrier or medium. For example, a computer-readable medium may include, but is not limited to, a magnetic storage device (e.g., a hard disk, a floppy disk, a magnetic strip), an optical disk (e.g., a compact disk (CD), a digital versatile disk (DVD), etc.), a smart card, and a flash memory device (e.g., an EPROM, a card, a stick, a key drive, etc.). In addition, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data. In addition, a computer program product may include a computer-readable medium having one or more instructions or codes that are operable to cause a computer to perform the functions described herein.

[0125] Communication media embodies computer readable instructions, data structures, program modules, or other structured or unstructured data in a data signal such as a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery or transmission medium. The term "modulated data signal" or signal refers to a signal that has one or more of its characteristics set or changed in a manner that encodes information in one or more signals. By way of example, and not limitation, communication media include wired media such as a wired network or direct wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

[0126] An exemplary storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integrated with the processor. In addition, in some aspects, the processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a user terminal. In an alternative, the processor and the storage medium may reside in a user terminal as discrete components. In addition, in some aspects, the process and / or action of the method or algorithm may reside on a machine-readable medium and / or a computer-readable medium as one or any combination or set of codes and / or instructions, and may be incorporated into a computer program product.

[0127] In this regard, although the subject matter disclosed in the present invention has been described in conjunction with various embodiments and corresponding drawings, it should be understood that other similar embodiments may be used or modifications and additions may be made to the described embodiments to perform the same, similar, alternative or alternative functions of the disclosed subject matter without departing from the described embodiments. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but should be interpreted according to the breadth and scope of the following claims.

[0128] In particular, with respect to the various functions performed by the above-described components (assemblies, devices, circuits, systems, etc.), unless otherwise specified, the terms used to describe such components (including references to "means") are intended to correspond to any component or structure that performs the specified function of the component (e.g., functionally equivalent), even if not structurally equivalent to the disclosed structure that performs the function in the exemplary implementation of the disclosure shown herein. In addition, while particular features have been disclosed with respect to only one of several implementations, for any given or specific application, such features may be combined with one or more other features of other implementations, which may be desirable and advantageous.

Claims

1. An apparatus configured to be employed in a user equipment UE, the apparatus comprising: One or more processors configured to: processing one or more parameters associated with a physical shared channel for use in determining a transport block size; determining a number of resource elements RE within a physical resource block PRB for the physical shared channel based on whether a first value derived from the one or more parameters indicates an integer value greater than a threshold value for a signal duration of the physical shared channel; and generating a configured action for the physical shared channel based on the determination of the number of REs; as well as A radio frequency (RF) interface is configured to provide data to the RF circuit for transmission based on the configured action.

2. The apparatus of claim 1 , wherein the one or more processors are further configured to: In response to the first value being a negative value or a zero value, the physical shared channel is dropped according to the configured action, and overhead parameters configured by a radio resource control (RRC) configured by a serving cell based on an information element with respect to different signal durations of a physical uplink shared channel (PUSCH) transmission or a physical downlink shared channel (PDSCH) transmission as the physical shared channel are applied.

3. The apparatus according to claim 1 or claim 2, wherein the one or more parameters include at least one of the following: the number of subcarriers in the frequency domain in a physical resource block; The number of symbols allocated to the physical shared channel in a time slot or overhead parameters configured based on serving cell configuration of information element with respect to different signal durations for physical uplink shared channel PUSCH transmission or physical downlink shared channel PDSCH transmission and the number of DM-RS per physical shared physical resource block PRB for the allocated duration including the overhead of a demodulation reference signal DM-RS code division multiplexing CDM group without data 4. The apparatus of claim 3, wherein the one or more processors are further configured to: In response to the first value providing a negative number or zero according to a first formula, the first formula is modified to a second formula, wherein the second formula includes a different number of one or more parameters than the first formula, the second formula being represented as follows: or And the first formula is expressed as follows:

5. The apparatus according to claim 1 or claim 2, wherein the first value is derived from a first formula including a proportional term, the proportional term being based on an overhead parameter configured by a radio resource control (RRC). The number of REs N is configured in proportion to the physical uplink shared channel PUSCH duration or the physical downlink shared channel PDSCH duration of the transmission R ′ E .

6. The apparatus of claim 5, wherein the proportional term further comprises a number of symbols allocated by a physical shared channel within a time slot of the transmission, and the configured actions comprise, in response to the first formula indicating a negative or zero value, discarding the transmission via the physical shared channel, and in response to the first formula indicating that the number of REs is above zero and below a threshold signal duration, modifying a signal duration of the transmission.

7. The apparatus of claim 5, wherein the one or more processors are further configured to: In response to the first formula providing a negative number or zero, the first formula is modified to a second formula, wherein the second formula includes a different number of one or more parameters than the first formula.

8. The apparatus of claim 1 or claim 2, wherein the one or more processors are further configured to: A determination is made based on the number of symbols transmitted being less than a threshold signal duration whether to utilize a second formula that modifies the first formula that provides the first value to provide a second value.

9. The apparatus of claim 8, wherein the one or more processors are further configured to: In response to the second formula providing the second value being greater than zero, utilizing the second formula; or In response to the second value being a negative value or a zero value, dropping the physical shared channel according to a configured action.

10. The apparatus of claim 1 or claim 2, wherein the one or more processors are further configured to: Processing the one or more parameters including the configured overhead parameter, wherein the configured overhead parameter is zero in response to the number of symbols allocated by a physical uplink shared channel (PUSCH) or a physical downlink shared channel (PDSCH) being less than a threshold number, or the configured overhead parameter is equal to the overhead parameter configured by the serving cell from an information element of the PUSCH or PDSCH.

11. The apparatus of claim 1 or claim 2, wherein the one or more processors are further configured to: configuring at least two different thresholds based on the number of symbols allocated by a physical uplink shared channel (PUSCH) or a physical downlink shared channel (PDSCH); and Different levels of a value of the configured overhead parameter are determined based on a number of symbols allocated by the PUSCH or the PDSCH associated with the at least two different thresholds.

12. A tangible computer-readable storage device storing executable instructions that, in response to being executed, cause one or more processors of a user equipment (UE) for transmission to perform operations comprising: Processing one or more parameters related to a physical shared channel for determining a transport block size TBS; Configuring a formula based on the one or more parameters to determine the number of resource elements RE in a physical resource block PRB for the physical shared channel; determining the number of REs based on whether the formula satisfies a threshold value of a signal duration for the physical shared channel; as well as The transmission is transmitted based on the configured action for the physical shared channel and the determination of the number of REs.

13. The tangible computer readable storage device of claim 12, wherein the operations further comprise: Based on whether the formula satisfies the threshold value, the transmission is dropped or a different configured action is performed.

14. The tangible computer readable storage device of claim 13, wherein the operations further comprise: In response to the formula not satisfying the threshold value of the signal duration of a physical uplink shared channel (PUSCH) or a physical downlink shared channel (PDSCH), the formula is modified to another formula, wherein the other formula includes a different number of terms based on the one or more parameters than the formula.

15. The tangible computer readable storage device of any one of claims 12-14, wherein the operations further comprise: Determining whether to utilize another formula based on the number of transmitted symbols being less than a threshold signal duration, wherein the another formula includes a proportional term, the proportional term configuring the number of REs based on a ratio of an overhead parameter configured by a radio resource control RRC to a physical uplink shared channel PUSCH duration or a physical downlink shared channel PDSCH duration; and The TBS is determined based on the number of available resource elements RE.

16. A baseband processor of a network device including a user equipment UE or a next generation Node B (gNB), the baseband processor being configured to: determining a number of resource elements RE within a physical resource block PRB for a physical shared channel based on a first value derived from one or more parameters; determining a configured action for the physical shared channel based on the determined number of REs and whether the first value indicates an integer value greater than a threshold value of a signal duration for the physical shared channel; and Data for communications based on the configured actions is provided to the radio frequency (RF) interface for transmission.

17. The baseband processor of claim 16, wherein the one or more parameters include at least one of the following: the number of subcarriers in the frequency domain in a physical resource block; The number of symbols allocated to the physical shared channel in a time slot or overhead parameters configured based on serving cell configuration of information element with respect to different signal durations for physical uplink shared channel PUSCH transmission or physical downlink shared channel PDSCH transmission and the number of DM-RS per physical shared physical resource block PRB for the allocated duration including the overhead of a demodulation reference signal DM-RS code division multiplexing CDM group without data 18. The baseband processor according to claim 16 or claim 17, wherein the baseband processor is further configured to: In response to a first formula providing a negative number or zero as the first value, the first formula providing the first value is modified to a second formula, wherein the second formula includes a different number of the one or more parameters than the first formula.

19. The baseband processor of claim 18, wherein the second formula includes a proportional term, which configures the number of REs based on a ratio of an overhead parameter configured by a radio resource control (RRC) to a physical uplink shared channel (PUSCH) duration and the number of symbols allocated to the physical shared channel within a time slot.

20. The baseband processor of claim 18, wherein the baseband processor is further configured to: In response to the first formula indicating a negative or zero value, a physical uplink shared channel (PUSCH) transmission is discarded, otherwise the signal duration is modified based on the number of REs used for ultra-reliable low latency communication (URLLC) communication.

21. The baseband processor according to claim 16 or claim 17, wherein the baseband processor is further configured to: Processing the one or more parameters including a configured overhead parameter, wherein the configured overhead parameter is zero in response to the number of symbols allocated by a physical uplink shared channel (PUSCH) being less than a threshold number, or the configured overhead parameter is equal to an overhead parameter configured by a serving cell from an information element of the PUSCH.

Images