WO2018063463A1

WO2018063463A1 - Dynamic resource allocation of scheduling requests

Info

Publication number: WO2018063463A1
Application number: PCT/US2017/039045
Authority: WO
Inventors: Gang Xiong; Umesh PHUYAL; Hwan-Joon Kwon; Joonyoung Cho; Hong He
Original assignee: Intel IP Corporation
Priority date: 2016-09-30
Filing date: 2017-06-23
Publication date: 2018-04-05

Abstract

An apparatus employed in a next Generation NodeB (gNB) comprising baseband circuitry. The circuitry has one or more processors configured to dynamically allocate a scheduling request (SR) resource and grant the scheduling request (SR) resource via a downlink control information (DCI) within a physical downlink control channel (PDCCH) or medium access layer - control element (MAC-CE).

Description

DYNAMIC RESOURCE ALLOCATION OF SCHEDULING REQUESTS

FIELD

[0001] Various embodiments generally may relate to the field of wireless

communications.

RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No.

62/402,858, filed September 30, 2016.

BACKGROUND

[0003] Wireless or mobile communication involves wireless communication between two or more devices. The communication requires resources to transmit data from one device to another and/or to receive data at one device from another.

[0004] Wireless communication typically has limited resources. Thus, how the limited resources are utilized can impact communication data rate, reliability, latency and the like. If too many resources are allocated for a communication, other devices may be unable to communicate and/or have degraded communications. If too few resources are allocated for a communication, the involved device may be unable to communicate and/or have degraded communications.

[0005] What is needed is a technique to facilitate allocation of resources used for wireless communications.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] FIG. 1 illustrates a block diagram of an example wireless communications network environment for a network device (e.g., a UE or an eNB) according to various aspects or embodiments.

[0007] FIG. 2 illustrates another block diagram of an example of wireless communications network environment for a network device (e.g., a UE or an eNB) according to various aspects or embodiments.

[0008] FIG. 3 another block diagram of an example of wireless communications network environment for network device (e.g., a UE or an eNB) with various interfaces according to various aspects or embodiments. [0009] FIG. 4A is a diagram illustrating a system for uplink data transmission in accordance with some embodiments.

[0010] FIG. 4B is a diagram illustrating a system for uplink data transmission in accordance with some embodiments.

[0011] FIG. 5 is a table illustrating example suitable configurations for a DCI are provided.

[0012] FIG. 6 is a diagram illustrating timing between triggering of activation and deactivation of SR resource and when SR resource is activated or deactivated.

[0013] FIG. 7 is a flow diagram illustrating a method of allocating SR resource in accordance with an embodiment.

DETAILED DESCRIPTION

[0014] The present disclosure will now be described with reference to the attached drawing figures, wherein like reference numerals are used to refer to like elements throughout, and wherein the illustrated structures and devices are not necessarily drawn to scale. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. Embodiments herein may be related to RAN1 and 5G.

[0015] As utilized herein, terms "component," "system," "interface," and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and/or firmware. For example, a component can be a processor, a process running on a processor, a controller, an object, an executable, a program, a storage device, and/or a computer with a processing device. By way of illustration, an application running on a server and the server can also be a component. One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers. A set of elements or a set of other components can be described herein, in which the term "set" can be interpreted as "one or more." [0016] Further, these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example. The components can communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).

[0017] As another example, a component can be an apparatus with specific

functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components.

[0018] Use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless specified otherwise, or clear from context, "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied under any of the foregoing instances. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms "including", "includes", "having", "has", "with", or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term

"comprising".

[0019] As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.

[0020] Mobile communication has evolved significantly from early voice systems to today's highly sophisticated integrated communication platform. The next generation wireless communication system, 5G or new radio (NR), will provide substantial access to information and sharing of data by various users, applications and the like. NR is expected to be a unified network and/or system that targets to meet vastly different and sometime conflicting performance dimensions and services. Such diverse multidimensional requirements are driven by different services and applications. In general, NR may evolve based on 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich or enhance mobile/wireless communication with enhanced, simple and seamless wireless connectivity solutions. NR can enable communication for mobile devices connected by wireless communications and deliver fast, rich contents and services.

[0021] Various techniques and/or embodiments are provided that facilitate SR scheduling and utilization. These facilitate forward compatibility, increase the time and/or frequency resources that can be utilized without causing backward compatibility issues, use blank resources to reduce transmission of always-on signal and confine signals and/or channels for physical layer functionalities within a configurable/allocable time and frequency resource.

[0022] FIG. 1 illustrates an architecture of a system 100 of a network in accordance with some embodiments. The system 100 is shown to include a user equipment (UE) 101 and a UE 102. The UEs 101 and 1 02 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but can also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.

[0023] In some embodiments, any of the UEs 101 and 102 can comprise an Internet of Things (loT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections. An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data can be a machine-initiated exchange of data. An loT network describes interconnecting loT UEs, which can include uniquely identifiable embedded computing devices (within the

Internet infrastructure), with short-lived connections. The loT UEs can execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.

[0024] The UEs 101 and 102 can be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 1 10— the RAN 1 10 can be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.

[0025] In this embodiment, the UEs 101 and 1 02 can further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 can

alternatively be referred to as a sidelink interface comprising 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).

[0026] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.1 1 protocol, wherein the AP 106 would comprise a wireless fidelity (WiFi®) router. In this example, the AP 1 06 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0027] The RAN 1 1 0 can include one or more access nodes that enable the connections 1 03 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). A network device as referred to herein can include any one of these APs, ANs, UEs or any other network component. The RAN 1 10 can include one or more RAN nodes for providing macrocells, e.g., macro RAN node 1 1 1 , and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 1 12.

[0028] Any of the RAN nodes 1 1 1 and 1 12 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102. In some embodiments, any of the RAN nodes 1 1 1 and 1 12 can fulfill various logical functions for the RAN 1 1 0 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink (UL) and downlink (DL) dynamic radio resource

management and data packet scheduling, and mobility management.

[0029] In accordance with some embodiments, the UEs 101 and 102 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 1 1 1 and 1 1 2 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0030] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 1 1 1 and 1 12 to the UEs 101 and 1 02, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this can represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks. [0031] The physical downlink shared channel (PDSCH) can carry user data and higher-layer signaling to the UEs 101 and 102. The physical downlink control channel (PDCCH) can carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It can also inform the UEs 101 and 102 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) can be performed at any of the RAN nodes 1 1 1 and 1 12 based on channel quality information fed back from any of the UEs 101 and 102. The downlink resource assignment information can be sent on the PDCCH used for (e.g., assigned to) each of the UEs 101 and 1 02.

[0032] The PDCCH can use control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be permuted using a sub-block interleaver for rate matching. Each PDCCH can be transmitted using one or more of these CCEs, where each CCE can correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=1 , 2, 4, or 8).

[0033] Some embodiments can use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments can utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH can be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE can correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE can have other numbers of EREGs in some situations.

[0034] The RAN 1 1 0 is shown to be communicatively coupled to a core network (CN) 1 20— via an S1 interface 1 1 3. In embodiments, the CN 120 can be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S1 interface 1 13 is split into two parts: the S1 -U interface 1 14, which carries traffic data between the RAN nodes 1 1 1 and 1 12 and the serving gateway (S-GW) 122, and the S1 -mobility management entity (MME) interface 1 15, which is a signaling interface between the RAN nodes 1 1 1 and 1 12 and MMEs 121 .

[0035] In this embodiment, the CN 1 20 comprises the MMEs 121 , the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 can be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 can manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 can comprise a database for network users, including subscription-related information to support the network entities' handling of

communication sessions. The CN 120 can comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0036] The S-GW 122 can terminate the S1 interface 1 13 towards the RAN 1 1 0, and routes data packets between the RAN 1 10 and the CN 1 20. In addition, the S-GW 122 can be a local mobility anchor point for inter-RAN node handovers and also can provide an anchor for inter-3GPP mobility. Other responsibilities can include lawful intercept, charging, and some policy enforcement.

[0037] The P-GW 123 can terminate an SGi interface toward a PDN. The P-GW 123 can route data packets between the CN network 120 and external networks such as a network including the application server 130 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. Generally, the application server 130 can be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 123 is shown to be communicatively coupled to an application server 130 via an IP communications interface 125. The application server 130 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 1 01 and 102 via the CN 120.

[0038] The P-GW 123 can further be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, there can be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there can be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 can be communicatively coupled to the application server 130 via the P-GW 123. The application server 130 can signal the PCRF 1 26 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF 126 can provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 130.

[0039] In one or more embodiments, IMS services can be identified more accurately in a paging indication, which can enable the UEs 101 , 102 to differentiate between PS paging and IMS service related paging. As a result, the UEs 101 , 102 can apply preferential prioritization for IMS services as desired based on any number of requests by any application, background searching (e.g., PLMN searching or the like), process, or communication. In particular, the UEs 1 01 , 102 can differentiate the PS domain paging to more distinguishable categories, so that IMS services can be identified clearly in the UEs 101 , 102 in comparison to PS services. In addition to a domain indicator (e.g., PS or CS), a network (e.g., CN 120, RAN 1 10, AP 106, or combination thereof as an eNB or the other network device) can provide further, more specific information with the TS 36.331 -Paging message, such as a "paging cause" parameter. The UE can use this information to decide whether to respond to the paging, possibly interrupting some other procedure like an ongoing PLMN search.

[0040] In one example, when UEs 101 , 102 can be registered to a visited PLMN (VPLMN) and performing PLMN search (i.e., background scan for a home PLMN (HPLMN) or a higher priority PLMN), or when a registered UE is performing a manual PLMN search, the PLMN search can be interrupted in order to move to a connected mode and respond to a paging operation as part of a MT procedure / operation.

Frequently, this paging could be for PS data (non-IMS data), where, for example, an application server 130 in the NW wants to push to the UE 101 or 102 for one of the many different applications running in / on the UE 101 or 1 02, for example. Even though the PS data could be delay tolerant and less important, in legacy networks the paging is often not able to be ignored completely, as critical services like an IMS call can be the reason for the PS paging. The multiple interruptions of the PLMN search caused by the paging can result in an unpredictable delay of the PLMN search or in the worst case even in a failure of the procedure, resulting in a loss of efficiency in network

communication operations. A delay in moving to or handover to a preferred PLMN (via manual PLMN search or HPLMN search) in a roaming condition can incur more roaming charges on a user as well.

[0041] FIG. 2 illustrates example components of a network device 200 in accordance with some embodiments. In some embodiments, the device 200 can include application circuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 210, and power management circuitry (PMC) 21 2 coupled together at least as shown. The components of the illustrated device 200 can be included in a UE 101 , 102 or a RAN node 1 1 1 , 1 12, AP, AN, eNB or other network component. In some embodiments, the device 200 can include less elements (e.g., a RAN node can not utilize application circuitry 202, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the network device 200 can include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

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

[0043] The baseband circuitry 204 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 204 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 206 and to generate baseband signals for a transmit signal path of the RF circuitry 206. Baseband processing circuity 204 can interface with the application circuitry 202 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 206. For example, in some embodiments, the baseband circuitry 204 can 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 processor(s) 204D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), si2h generation (6G), etc.). The baseband circuitry 204 (e.g., one or more of baseband processors 204A-D) can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 206. In other embodiments, some or all of the functionality of baseband processors 204A-D can be included in modules stored in the memory 204G and executed via a Central Processing Unit (CPU) 204E. The radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 204 can include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments,

encoding/decoding circuitry of the baseband circuitry 204 can include convolution, tail- biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other embodiments.

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

[0045] In some embodiments, the baseband circuitry 204 can provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 204 can support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 204 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry. [0046] RF circuitry 206 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various

embodiments, the RF circuitry 206 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 206 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 208 and provide baseband signals to the baseband circuitry 204. RF circuitry 206 can also include a transmit signal path which can include circuitry to up- convert baseband signals provided by the baseband circuitry 204 and provide RF output signals to the FEM circuitry 208 for transmission.

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

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

[0049] In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path can include two or more mixers and can be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a can be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 206a of the receive signal path and the mixer circuitry 206a of the transmit signal path can be configured for super-heterodyne operation.

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

[0051] In some dual-mode embodiments, a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the

embodiments is not limited in this respect.

[0052] In some embodiments, the synthesizer circuitry 206d can 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 can be suitable. For example, synthesizer circuitry 206d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

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

[0054] In some embodiments, frequency input can be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input can be provided by either the baseband circuitry 204 or the applications processor 202 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications processor 202.

[0055] Synthesizer circuitry 206d of the RF circuitry 206 can include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip- flop. In these embodiments, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, 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.

[0056] In some embodiments, synthesizer circuitry 206d can be configured to generate a carrier frequency as the 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 in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency can be a LO frequency (fLO). In some embodiments, the RF circuitry 206 can include an IQ/polar converter.

[0057] FEM circuitry 208 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 210, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 206 for further processing. FEM circuitry 208 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 206 for transmission by one or more of the one or more antennas 21 0. In various embodiments, the amplification through the transmit or receive signal paths can be done solely in the RF circuitry 206, solely in the FEM 208, or in both the RF circuitry 206 and the FEM 208.

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

[0059] In some embodiments, the PMC 212 can manage power provided to the baseband circuitry 204. In particular, the PMC 212 can control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 212 can often be included when the device 200 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 21 2 can increase the power conversion efficiency while providing desirable implementation size and heat dissipation

characteristics.

[0060] While FIG. 2 shows the PMC 212 coupled only with the baseband circuitry 204. However, in other embodiments, the PMC 2 12 can be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 202, RF circuitry 206, or FEM 208.

[0061] In some embodiments, the PMC 212 can control, or otherwise be part of, various power saving mechanisms of the device 200. For example, if the device 200 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it can enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 200 can power down for brief intervals of time and thus save power.

[0062] If there is no data traffic activity for an extended period of time, then the device 200 can transition off to an RRCJdle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 200 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 200 does not receive data in this state, in order to receive data, it transitions back to RRC_Connected state.

[0063] An additional power saving mode can allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device can be unreachable to the network and can power down completely. Any data sent during this time can incur a large delay with the delay presumed to be acceptable.

[0064] Processors of the application circuitry 202 and processors of the baseband circuitry 204 can be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 204, alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 204 can utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 can comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 can comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 can comprise a physical (PHY) layer of a UE/RAN node. Each of these layers can be implemented to operate one or more processes or network operations of embodiments / aspects herein.

[0065] In addition, the memory 204G can comprise one or more machine-readable medium / media including instructions that, when performed by a machine or

component herein cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein. It is to be understood that aspects described herein can be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium (e.g., the memory described herein or other storage device). Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media or a computer readable storage device can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD- ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or other tangible and/or non-transitory medium, that can be used to carry or store desired information or executable instructions. Also, any connection can also be termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.

[0066] In general, there is a move to provide network services for the packet domain. The earlier network services like UMTS or 3G and predecessors (2G) configured a CS domain and a packet domain providing different services, especially CS services in the CS domain as well as voice services were considered to have a higher priority because consumers demanded an immediate response. Based on the domain that the paging was received, the device 200 could assign certain priority for the incoming transaction. Now with LTE / 5G most services are moving to the packet domain. Currently, the UE (e.g., 1 01 , 102, or device 200) can get paging for a packet service without knowing any further information about the paging of the MT procedure, such as whether someone is calling on a line, a VoIP call, or just some packet utilized from Facebook, other application service, or other similar MT service. As such, a greater opportunity exists for further delays without the possibility for the UE to discriminate between the different application packets that could initiate a paging and also give a different priority to it based on one or more user preferences. This can could be important for the UE because the UE might be doing other tasks more vital for resource allocation.

[0067] In one example, a UE (e.g., 101 , 102, or device 200) could be performing a background search for other PLMNs. This is a task the UE device 200 could do in regular intervals if it is not connected on its own home PLMN or a higher priority PLMN, but roaming somewhere else. A higher priority could be a home PLMN or some other PLMNs according to a list provided by the provider or subscriber (e.g., HSS 124).

Consequently, if a paging operation arrives as an MT service and an interruption results, such that a start and begin operation are executed, a sufficient frequency of these interruptions could cause the UE to never complete a background search in a reasonable way. This is one way where it would be advantageous for the UE or network device to know that the interruption is only a packet service, with no need to react to it immediately, versus an incoming voice call that takes preference immediately and the background scan should be postponed.

[0068] Additionally, the device 200 can be configured to connect or include multiple subscriber identity / identification module (SIM) cards / components, referred to as dual SIM or multi SIM devices. The device 200 can operate with a single transmit and receive component that can coordinate between the different identities from which the SIM components are operating. As such, an incoming voice call should be responded to as fast as possible, while only an incoming packet for an application could be relatively ignored in order to utilize resources for the other identity (e.g., the voice call or SIM component) that is more important or has a higher priority from a priority list / data set / or set of user device preferences, for example. This same scenario can also be utilized for other operations or incoming data, such as with a PLMN background search such as a manual PLMN search, which can last for a long period of time since, especially with a large number of different bands from 2G, etc. With an ever increasing number of bands being utilized in wireless communications, if paging interruptions come in between the operations already running without distinguishing between the various packet and real critical services such as voice, the network devices can interpret this manual PLMN search to serve and ensure against a drop or loss of any increment voice call, with more frequent interruptions in particular.

[0069] As stated above, even though in most of these cases the PS data is delay tolerant and less important, in legacy networks the paging cannot be ignored

completely, as critical services like an IMS call can be the reason for the PS paging. The multiple interruptions of a PLMN search caused by the paging can result in an unpredictable delay of the PLMN search or in the worst case even in a failure of the procedure. Additionally, a delay in moving to preferred PLMN (via manual PLMN search or HPLMN search) in roaming condition can incur more roaming charges on user.

Similarly, in multi-SIM scenario when UE is listening to paging channel of two networks simultaneously and has priority for voice service, a MT IMS voice call can be interpreted as "data" call as indicated in MT paging message and can be preceded by MT Circuit Switched (CS) paging of another network or MO CS call initiated by user at same time. As such, embodiments / aspects herein can increase the call drop risk significantly for the SIM using IMS voice service.

[0070] In embodiments, 3GPP NW can provide further granular information about the kind of service the network is paging for. For example, the Paging cause parameter could indicate one of the following values / classes / categories: 1 ) IMS voice/video service; 2) IMS SMS service; 3) IMS other services (not voice/video/SMS-related; 4) any IMS service; 5) Other PS service (not IMS-related). In particular, a network device (e.g., an eNB or access point) could only be discriminating between IMS and non-IMS services could use 4) and 5), whereas a network that is able to discriminate between different types of IMS services (like voice/video call, SMS, messaging, etc.) could use 3) instead of 4) to explicitly indicate to the UE that the paging is for an IMS service different from voice/video and SMS. By obtaining this information UE may decide to suspend PLMN search only for critical services like incoming voice/video services.

[0071] In other aspects, dependent on the service category (e.g., values or classes 1 -5 above), the UE 101 , 102, or device 200 can memorize that there was a paging to which it did not respond, and access the network later, when the PLMN search has been completed and the UE decides to stay on the current PLMN. For example, if the reason for the paging was a mobile terminating IMS SMS, the MME can then inform the HSS (e.g., 124) that the UE is reachable again, and the HSS 124 can initiate a signaling procedure which will result in a delivery of the SMS to the UE once resources are more available or less urgent for another operation / application / or category, for example. To this purpose the UE 101 , 102, or 200 could initiate a periodic tau area update (TAU) procedure if the service category in the Paging message indicated "IMS SMS service", for example.

[0072] FIG. 3 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 204 of FIG. 2 can comprise processors 204A-204E and a memory 204G utilized by said processors. Each of the processors 204A-204E can include a memory interface, 304A-304E, respectively, to send/receive data to/from the memory 204G.

[0073] The baseband circuitry 204 can further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 312 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 204), an application circuitry interface 314 (e.g., an interface to send/receive data to/from the application circuitry 202 of FIG. 2), an RF circuitry interface 316 (e.g., an interface to send/receive data to/from RF circuitry 206 of FIG. 2), a wireless hardware connectivity interface 31 8 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 320 (e.g., an interface to send/receive power or control signals to / from the PMC 21 2.

[0074] FIG. 4A is a diagram illustrating a system 400 for uplink data transmission in response to a scheduling request. The system 400 can be utilized with the above embodiments and variations thereof. The system 400 is provided as an example and it is appreciated that suitable variations are contemplated.

[0075] The system 400 includes a network device 401 and a node 402. The device 401 is shown as a UE device and the node 402 is shown as an eNB for illustrative purposes. It is appreciated that the UE device 401 can be other network devices, such as Aps, ANs and the like. It is also appreciated that the eNB 402 can be other nodes or access nodes (ANs), such as BSs, gNB, RAN nodes and the like.

[0076] The UE device 401 intends to transmit data in an uplink (UL). Thus, the UE device 401 requests a UL resource as a scheduling request (SR) using a physical uplink control channel (PUCCH) format as shown at 404. After detecting the SR, the eNB 402 transmits downlink control information (DCI) format that includes an uplink grant to allocate an uplink resource for the UE device 401 . The DCI is provided using a physical downlink control channel (PDCCH) as shown at 406.

[0077] In response to the uplink grant, the UE device 401 can send a buffer status report (BSR) at 406 using a physical uplink shared channel (PUSCH) using the granted uplink resource. The BSR is carried in a medium access control (MAC) protocol data unit (PDU), which informs the eNB 402 of the amount of data in the UE device's 401 buffer to be transmitted. Then, the eNB 402 additionally allocates appropriate resource(s) and a modulation and coding scheme (MCS), which is included in future uplink grant(s). The additional allocated resource(s) are sent by the eNB 402 at 41 0 using a PDCCH. The UE device 401 then transmits uplink data on the PUSCH at 412 using the additional allocated resources.

[0078] In LTE, the SR uses a simple on/off mechanism. The information is conveyed by the presence of energy on the corresponding PUCCH resource. If the UE device 401 does not request an uplink resource, it does so by transmitting nothing on the configured PUCCH resource. Additionally, the SR resource is semi-statically configured by higher layers to allow periodic opportunities for the UE device 401 to request resources for uplink transmission. The SR is carried by the PUCCH, which indicates that a PUCCH resource is periodically allocated for transmissions for SR. The periodic allocation may be problematic for some scenarios, such as dynamic TDD systems where periodically allocated PUCCH resources may need to be mitigated to improve a data rate.

[0079] FIG. 4B is a diagram illustrating the system 400 for uplink data transmission in accordance with some embodiments. The system 400, in this example, allocates or activates a SR resource dynamically or as a hybrid combination of dynamically and periodically. The system 400 can be utilized with the above embodiments and variations thereof. The system 400 is provided as an example and it is appreciated that suitable variations are contemplated.

[0080] The system 400 includes a network device 401 and a node 402. The device 401 is shown as a UE device and the node 402 is shown as an eNB for illustrative purposes. It is appreciated that the UE device 401 can be other network devices, such as APs, ANs and the like. It is also appreciated that the eNB 402 can be other nodes or access nodes (ANs), such as BSs, gNB, RAN nodes and the like.

[0081] The UE device 401 intends to transmit data in an uplink (UL). The device 401 monitors downlink control channels for activation or allocation of SR resource.

[0082] The eNB 402 allocates or activates a SR resource for the UE device at 426/428. The allocation has a configuration that can be specified using signaling at 426 or using a DCI at 428. The DCI can be included with a transmitted physical downlink control channel (PDCCH). The allocation can be performed dynamically, as a hybrid combination of dynamically, and the like. Furthermore, the allocation can be cell or group specific and/or UE specific.

[0083] The UE device 401 sends a SR using the allocated SR resource to request uplink data transmission resource(s) at 430.

[0084] The eNB 402 grants the requested uplink resource(s) at 432 based on the SR. The granted resource(s) can be specified in a physical downlink control channel (PDCCH). The eNB 402 can transmit the uplink grant within a PDCCH. The uplink grant identifies the resources that the UE 401 can utilize for transmitting uplink data. The resources include time and frequency allocations.

[0085] The UE device 401 sends uplink data using the granted uplink resource at 434. The UE device 401 typically uses a physical uplink shared channel (PUSCH) to send the uplink data.

[0086] The eNB 402 deactivates the SR resource at 436. Typically, the deactivation occurs after the uplink communications have completed.

[0087] Several embodiments or techniques can be used by the system 400 for scheduling SR resource(s) instead of or in addition to periodically allocating PUCCH resources. The example allocations and/or configurations are provided below in greater deal.

[0088] In one embodiment, an SR resource can be dynamically triggered by the node 402 via a downlink control information (DCI) in a UE specific or group/cell specific manner.

[0089] When a UE specific DCI is used to trigger SR resource, a 1 bit indicator in the DL or UL grant can be used to indicate that SR resource is triggered. Additionally, an SR resource index and configuration including periodicity and subframe/slot offset for SR transmission on NR physical uplink control channel (PUCCH) can be configured or indicated. In one example, these are configured by higher layer via radio resource control (RRC) signaling. In another example, these are indicated in the DCI format.

[0090] When the group/cell specific DCI is used to trigger SR resource, a new DCI format can be defined. In one example, 1 bit in DCI can be used to trigger SR resource for one UE. The order of UE in the DCI can be configured by higher layers via RRC signaling. For instance, bit "1 " may indicate that an SR resource is allocated while bit "0" indicates that SR resource is not allocated. Furthermore, an SR resource index and configuration including periodicity and subframe/slot offset can be configured by higher layers. [0091] Additionally, an SR resource index for each UE can be included in the DCI format. Similarly, the order of UE in the DCI can be configured by higher layers via RRC signaling. Further, the SR resource index and configuration including periodicity and subframe/slot offset can be configured by higher layers to save overhead in DCI signaling.

[0092] It is appreciated that for a group/cell specific DCI, a new radio network temporary identifier (RNTI) can be defined for the transmission of an NR physical downlink control channel (PDCCH), wherein a CRC is scrambled by a SR-RNTI. This SR-RNTI can be predefined or configured by higher layers via NR master information block (MIB), NR system information block (SIB) or radio resource control (RRC) signaling.

[0093] To control the timescale of dynamic allocation of SR resource, the periodicity of the NR PDCCH which contains the dynamic allocation of SR resource can be configured. This may also help to reduce the UE power consumption due to the fact that UE only needs to monitor certain subframe for NR PDCCH with CRC scrambled by SR-RNTI.

[0094] It is noted that the subframes that UE device 401 monitors for NR PDCCH with CRC scrambled by SR-RNTI can be defined as the downlink subframes or special subframes in TDD system satisfying

[0095] (l0 n_f + [n_s/2\ - N_OFFSET ,SRACT)^m°d SRACT_PERI0DICITY = 0

[0096] where n_T and n_s are a radio frame number and a slot number; N_0FFSETiSRACT and SRACT_PERI0DICITY are the subframe offset and periodicity of the xPDCCH

transmission with CRC scrambled by SR-RNTI, respectively.

[0097] Fig. 5 is a table 500 illustrating example suitable configurations for a DCI are provided. The table includes example values for a configuration index, periodicity and subframe offset.

[0098] The subframe offset, N_{0FFSET SRACT} , and the periodicity, SRACT_PERI0DICITY , are defined by the parameter I_SRACT _> which is given in the table 500 as the configuration index. It is noted that other values of I_SRACT _> ^NOFFSET,SRACT ^ar>d SRACT_PERI0DICITY can be extended from the examples as shown in the table 500. Further, it is appreciated that the configuration index can be predefined or configured by higher layers via MIB, SIB or dedicated RRC signaling.

[0099] In another embodiment, a hybrid mode of semi-static configuration and dynamic triggering can be used for SR resource allocation by the system 400 and variations thereof. [00100] In particular, a semi-static SR resource can be configured by higher layers, while dynamical signaling via layer 1 (L1 ) or higher layer control signaling can be used to dynamically activate or deactivate allocated SR resource(s). This mechanism can facilitate forward compatibility and efficient support of dynamic TDD system. For example, periodic NR PUCCH resource(s) may be released to reduce the overhead and thereby improve system level spectrum efficiency and can be configured or activated on a need basis.

[00101 ] In another example/embodiment, downlink control information (DCI) can be used to activate and deactivate SR resource. The DCI can be UE specific and one bit field in the DCI carrying a DL or UL grant can be used to activate and deactivate SR resource. For example, bit "1 " may indicate that SR resource is activated while bit "0" indicates that SR resource is deactivated. In order to present error cases that the node 402 and the UE 401 happen to have a different understanding on the

activation/deactivation of the SR resource, acknowledge from the UE 401 can be utilized via an uplink HARQ-ACK or an explicit indication from the UE 401 on the activation/de-activation of the SR resource.

[00102] In another option, a DCI can be cell specific or group specific, where one bit may be used to activate or deactivate an SR resource for one UE. Further, a new RNTI, e.g., SR-RNTI can be defined for the transmission of NR physical downlink control channel (PDCCH), wherein the CRC is scrambled by SR-RNTI. This SR-RNTI can be predefined or configured by higher layers via NR master information block (MIB), NR system information block (SIB) or radio resource control (RRC) signalling. Further, the periodicity of the NR PDCCH which contains the activation and deactivation information of SR resource can be configured by higher layers via MIB, SIB or RRC signalling.

[00103] In another embodiment, a new Logical Channel ID (LCID) in the Medium Access Control (MAC) header may be defined for the purpose of activation and deactivation of an SR resource. Further, a corresponding MAC control element (CE) can be defined. In one option, the MAC CE can be zero bits long, thus the presence of the MAC CE indicates activation or deactivation of the SR resources. For example, the SR resources may be toggled for each occurrence of the MAC CE. As another example, two MAC CEs can be defined, a first for activation and a second for deactivation. In another option, the MAC CE can include further information about the activation and deactivation of SR resource, such as an identification or index of particular SR resources to be activated and deactivated. [001 04] In another embodiment, RRC signaling can be used to activate or deactivate SR resource(s). One or more sets of SR resources are defined and identifiable by their corresponding identifier or indices. RRC signaling is used to activate or deactivate a certain SR resource/set using an identifier or index in the RRC message. In one example, the RRC message is dedicated message to a specific UE, such as RRC Connection Reconfiguration message. Optionally, the specific UE may acknowledge or confirm the successful reception of the RRC message. In other example, a broadcast message such as a system information broadcast (SIB) may be use to activate or deactivate the SR resources for a group of users.

[001 05] It is appreciated that a fixed gap of time can be defined between the triggering of activation and deactivation of SR resource and when the SR resource is activated or deactivated. For example, assuming the subframe or slot for the triggering of activation or deactivation of SR resource is slot n and gap is k_delay, then SR resource can actually be activated or deactivated in slot n + k_delay. The gap can be predefined in the specification or configured by higher layers via MIB, SIB or RRC signalling.

[001 06] FIG. 6 is a diagram illustrating timing 600 between triggering of activation and deactivation of SR resource and when SR resource is activated or deactivated. The timing 600 is provided for illustrative purposes and it is appreciated that suitable variations are contemplated.

[001 07] In this example, the timing gap k_delay=7. This predetermined timing gap can facilitate the alignment between a NR eNB (such as gNB) and a UE, such as the node 402 and the UE device 401 . The timing gap can scale in accordance to the numerology applied to the slot. For instance, the k_delay=7 may be assumed for slot length = 1 ms. In an example where the slot length is 0.5 ms, the subcarrier spacing is doubled and ^deiay=^{1 4} can be applied instead.

[001 08] The UE device 401 can also be configured to acknowledge and/or confirm a successful reception of a SR activation/deactivation command/signal/message. For example, an indication that the activation/deactivation is successfully received can be sent using a separate indication in the uplink, such as using NR PUCCH. In such case, the gap between the time when triggering of activation/deactivation of SR and the time when the SR resource is actually activated/deactivated may be variable.

[001 09] It is appreciated that after a SR resource is deactivated, a UE can perform other procedures to request uplink data resource(s), such as an LTE RACH procedure.

[001 10] While the methods described within this disclosure are illustrated in and described herein as a series of acts or events, it will be appreciated that the illustrated ordering of such acts or events are not to be interpreted in a limiting sense. For example, some acts may occur in different orders and/or concurrently with other acts or pre apart from those illustrated and/or described herein. In addition, not all illustrated acts may be required to implement one or more aspects or embodiments of the description herein. Further, one or more of the acts depicted herein may be carried out in one or more separate acts and/or phases.

[00111 ] FIG. 7 is a flow diagram illustrating a method 700 of allocating SR resource in accordance with an embodiment. The method or process 700 is described with reference to a UE device and a gNB, however it is appreciated that other device and/or nodes can be used. For example, the gNB can be other types of nodes, such as an eNodeB. The method 700 can be implemented using the above arrangements and variations thereof.

[00112] The UE device requires or intends to utilize a SR resource at block 702.

[00113] The gNB allocates or activates the SR resource at block 704. The allocation or activation can be performed dynamically or as a hybrid combination of dynamically and periodically. Additionally, the allocation or activation can be cell specific and/or UE specific.

[00114] The UE device sends an SR on the allocated SR resource at block 706.

[00115] The gNB transmits an uplink grant within a physical downlink control channel (PDCCH) at block 708. The uplink grant identifies resources that the UE device can utilize for transmitting uplink data. The resources include time and frequency allocations.

[00116] The UE device receives and identifies the transmitted uplink grant at block 71 0.

[00117] The UE device utilizes the granted resource at block 712 for uplink communications. The UE device uses the specified resources to send the uplink data. The UE device typically uses a physical uplink shared channel (PUSCH) to send the uplink data

[00118] Once the uplink communications are completed, the gNB deactivates the SR resource at block 714. The deactivation can occur based on an elapsed time or other suitable determination.

[00119] The method 700 can be repeated or re-utilized for additional SR. It is appreciated that suitable variations of the method 700 are contemplated.

[00120] As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.

[00121 ] As it employed in the subject specification, the term "processor" can refer to substantially any computing processing unit or device including, but not limited to including, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology;

parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can 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, a discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions and/or processes described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of mobile devices. A processor may also be implemented as a combination of computing processing units.

[00122] In the subject specification, terms such as "store," "data store," data storage," "database," and substantially any other information storage component relevant to operation and functionality of a component and/or process, refer to "memory

components," or entities embodied in a "memory," or components including the memory. It is noted that the memory components described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.

[00123] By way of illustration, and not limitation, nonvolatile memory, for example, can be included in a memory, non-volatile memory (see below), disk storage (see below), and memory storage (see below). Further, nonvolatile memory can be included in read only memory, programmable read only memory, electrically programmable read only memory, electrically erasable programmable read only memory, or flash memory.

Volatile memory can include random access memory, which acts as external cache memory. By way of illustration and not limitation, random access memory is available in many forms such as synchronous random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, Synchlink dynamic random access memory, and direct Rambus random access memory. Additionally, the disclosed memory components of systems or methods herein are intended to include, without being limited to including, these and any other suitable types of memory.

[00124] Examples can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including instructions that, when performed by a machine cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described herein.

[00125] Example 1 is an apparatus for a base station comprising baseband circuitry. The baseband circuitry having a radio frequency (RF) interface and one or more processors. The one or more processors are configured to dynamically allocate a scheduling request (SR) resource, grant the scheduling request (SR) resource via a downlink control information (DCI), wherein the DCI is included in a physical downlink control channel (PDCCH) and send PDCCH data to the RF interface for transmission to one or more user equipment devices, wherein the PDCCH data includes the DCI.

[00126] Example 2 includes the subject matter of Example 1 , including or omitting optional elements, wherein the one or more processors are further configured to dynamically allocate the SR resource based on power consumption, overhead and/or spectrum efficiency.

[00127] Example 3 includes the subject matter of any of Examples 1 -2, including or omitting optional elements, where the DCI grants the SR resource to a single UE device of the one or more UE devices.

[00128] Example 4 includes the subject matter of any of Examples 1 -3, including or omitting optional elements, where the DCI grants the SR resource to group of UE devices of the one or more UE devices.

[00129] Example 5 includes the subject matter of any of Examples 1 -4, including or omitting optional elements, where the scheduling request is granted via a medium access layer - control element (MAC-CE).

[00130] Example 6 includes the subject matter of any of Examples 1 -5, including or omitting optional elements, where the one or more processors are configured to generate a downlink or uplink grant of the SR resource, wherein the downlink or uplink grant includes a 1 bit indicator to indicate that the SR resource is triggered.

[00131 ] Example 7 includes the subject matter of any of Examples 1 -6, including or omitting optional elements, where the one or more processors are configured to provide an SR resource index and SR configuration, wherein the SR resource index identifies the SR resource and the SR configuration includes a periodicity and subframe/slot offset for SR transmission on new radio (NR) physical uplink control channel (PUCCH).

[00132] Example 8 includes the subject matter of any of Examples 1 -7, including or omitting optional elements, where the SR configuration is configured via radio resource control (RRC) signaling.

[00133] Example 9 includes the subject matter of any of Examples 1 -8, including or omitting optional elements, where the SR configuration is configured via the DCI.

[00134] Example 10 includes the subject matter of any of Examples 1 -9, including or omitting optional elements, where the one or more processors are further configured to grant the SR resource via signaling.

[00135] Example 1 1 includes the subject matter of any of Examples 1 -1 0, including or omitting optional elements, where the one or more processors are further configured to grant the SR resource via a logical channel identification (LCID) in a medium access control (MAC) header.

[00136] Example 12 includes the subject matter of any of Examples 1 -1 1 , including or omitting optional elements, where the one or more processors are further configured to deactivate the SR resource via a second DCI.

[00137] Example 13 includes the subject matter of any of Examples 1 -1 2, including or omitting optional elements, where the DCI includes a CRC associated with a new radio network temporary identifier (RNTI).

[00138] Example 14 includes the subject matter of any of Examples 1 -1 3, including or omitting optional elements, where the base station is an evolved Node B (eNodeB).

[00139] Example 15 is an apparatus configured to be employed within a user equipment (UE) device. The apparatus comprises baseband circuitry, which includes a radio frequency (RF) interface and one or more processors. The one or more processors are configured to monitor downlink transmissions from the RF interface for a dynamic grant of a scheduling request (SR) resource; receive a SR configuration for the SR resource via a downlink control information (DCI); and generate a SR using the SR resource based on the SR configuration. [00140] Example 16 includes the subject matter of Example 15, including or omitting optional elements, where the one or more processors are further configured to utilize the granted SR resource to request an uplink resource.

[00141 ] Example 17 includes the subject matter of any of Examples 15-16, including or omitting optional elements, where the one or more processors are further configured to utilize the uplink resource for uplink data.

[00142] Example 18 includes one or more computer-readable media having instructions that, when executed, cause a base station or next Generation NodeB (gNB) or evolved Node B (eNB) to dynamically allocate a scheduling request (SR) resource, provide a SR configuration for the SR resource, and receive a SR via the allocated SR resource.

[00143] Example 19 includes the subject matter of Example 18, including or omitting optional elements, where the instructions, when executed further cause the base station or eNB to grant an uplink resource in response to the SR.

[00144] Example 20 includes the subject matter of any of Examples 18-19, including or omitting optional elements, where the instructions, when executed further cause the base station or eNB to deactivate the SR resource.

[00145] Example 21 includes the subject matter of any of Examples 18-20, including or omitting optional elements, where the instructions, when executed further cause the base station or eNB to dynamically allocate the SR resource for a group of UE devices.

[00146] Example 22 is an apparatus configured to be employed in a base station. The apparatus comprises a means to dynamically allocate a scheduling request (SR) resource, a means to transmit the allocated SR resource using a physical downlink control channel (PDCCH), a means to receive a SR via the allocated SR resource, a means to grant an uplink resource based on the received SR, and a means to receive an uplink data transmission using the uplink resource.

[00147] Example 23 includes the subject matter of Example 22, including or omitting optional elements, further comprising a means to generate downlink control information (DCI) for the SR resource and transmit the DCI using the PDCCH.

[00148] It is to be understood that aspects described herein can be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media or a computer readable storage device can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD- ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or other tangible and/or non-transitory medium, that can be used to carry or store desired information or executable instructions. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

Combinations of the above should also be included within the scope of computer- readable media.

[00149] Various illustrative logics, logical blocks, modules, and circuits described in connection with aspects disclosed herein can be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other

programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform functions described herein. A general-purpose processor can be a microprocessor, but, in the alternative, processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Additionally, at least one processor can comprise one or more modules operable to perform one or more of the s and/or actions described herein.

[00150] For a software implementation, techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform functions described herein. Software codes can be stored in memory units and executed by processors. Memory unit can be implemented within processor or external to processor, in which case memory unit can be communicatively coupled to processor through various means as is known in the art. Further, at least one processor can include one or more modules operable to perform functions described herein.

[00151 ] Techniques described herein can be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system can implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA1800, etc. UTRA includes Wideband-CDMA (W-CDMA) and other variants of CDMA. Further, CDMA1800 covers IS-1800, IS-95 and IS-856 standards. A TDMA system can implement a radio technology such as Global System for Mobile

Communications (GSM). An OFDMA system can implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.1 1 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.18, Flash-OFDML , etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which employs OFDMA on downlink and SC-FDMA on uplink. UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). Additionally, CDMA1 800 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). Further, such wireless communication systems can additionally include peer-to-peer (e.g., mobile-to-mobile) ad hoc network systems often using unpaired unlicensed spectrums, 802. xx wireless LAN, BLUETOOTH and any other short- or long- range, wireless communication techniques.

[00152] Single carrier frequency division multiple access (SC-FDMA), which utilizes single carrier modulation and frequency domain equalization is a technique that can be utilized with the disclosed aspects. SC-FDMA has similar performance and essentially a similar overall complexity as those of OFDMA system. SC-FDMA signal has lower peak-to-average power ratio (PAPR) because of its inherent single carrier structure. SC-FDMA can be utilized in uplink communications where lower PAPR can benefit a mobile terminal in terms of transmit power efficiency.

[00153] Moreover, various aspects or features described herein can be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, key drive, etc.). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data. Additionally, a computer program product can include a computer readable medium having one or more instructions or codes operable to cause a computer to perform functions described herein.

[00154] Communications media embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media. The term "modulated data signal" or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode 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.

[00155] Further, the actions of a method or algorithm described in connection with aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or a combination thereof. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium can be coupled to processor, such that processor can read information from, and write information to, storage medium. In the alternative, storage medium can be integral to processor. Further, in some aspects, processor and storage medium can reside in an ASIC. Additionally, ASIC can reside in a user terminal. In the alternative, processor and storage medium can reside as discrete components in a user terminal. Additionally, in some aspects, the s and/or actions of a method or algorithm can reside as one or any combination or set of codes and/or instructions on a machine-readable medium and/or computer readable medium, which can be incorporated into a computer program product.

[00156] The above description of illustrated embodiments of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such embodiments and examples, as those skilled in the relevant art can recognize.

[00157] In this regard, while the disclosed subject matter has been described in connection with various embodiments and corresponding Figures, where applicable, it is to be understood that other similar embodiments can be used or modifications and additions can be made to the described embodiments for performing the same, similar, alternative, or substitute function of the disclosed subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

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

Claims

CLAIMS What is claimed is:

1 . An apparatus for a base station, comprising baseband circuitry having:

a radio frequency (RF) interface; and

one or more processors configured to:

dynamically allocate a scheduling request (SR) resource;

grant the scheduling request (SR) resource via a downlink control information (DCI), wherein the DCI is included in a physical downlink control channel (PDCCH); and

send PDCCH data to the RF interface for transmission to one or more user equipment (UE) devices, wherein the PDCCH data includes the DCI.

2. The apparatus of claim 1 , wherein the one or more processors are further configured to dynamically allocate the SR resource based on power consumption, overhead and/or spectrum efficiency.

3. The apparatus of claim 1 , wherein the DCI grants the SR resource to a single UE device of the one or more UE devices.

4. The apparatus of claim 1 , wherein the DCI grants the SR resource to group of UE devices of the one or more UE devices.

5. The apparatus of claim 1 , wherein the scheduling request is granted via a medium access layer - control element (MAC-CE).

6. The apparatus of any one of claims 1 -5, wherein the one or more processors are configured to generate a downlink or uplink grant of the SR resource, wherein the downlink or uplink grant includes a 1 bit indicator to indicate that the SR resource is triggered.

7. The apparatus of any one of claims 1 -5, wherein the one or more processors are configured to provide an SR resource index and SR configuration, wherein the SR resource index identifies the SR resource and the SR configuration includes a periodicity and subframe/slot offset for SR transmission on new radio (NR) physical uplink control channel (PUCCH).

8. The apparatus of claim 7, wherein the SR configuration and the SR resource are configured via radio resource control (RRC) signaling.

9. The apparatus of claim 7, wherein the SR configuration and the SR resource are configured via the DCI.

10. The apparatus of any one of claims 1 -5, wherein the one or more processors are further configured to grant the SR resource via signaling.

1 1 . The apparatus of any one of claims 1 -5, wherein the one or more processors are further configured to grant the SR resource via a logical channel identification (LCID) in a medium access control (MAC) header.

12. The apparatus of any one of claims 1 -5, wherein the one or more processors are further configured to deactivate the SR resource via a second DCI.

13. The apparatus of any one of claims 1 -5, wherein the DCI includes a CRC associated with a new radio network temporary identifier (RNTI).

14. The apparatus of claim 1 , wherein the base station is an evolved Node B (eNodeB).

15. An apparatus employed in a user equipment (UE) device comprising baseband circuitry having:

a radio frequency (RF) interface; and

one or more processors configured to:

monitor received downlink transmissions from the RF interface for a dynamic grant of a scheduling request (SR) resource;

receive a SR configuration for the SR resource via a downlink control information (DCI); and

generate a SR using the SR resource based on the SR configuration.

16. The apparatus of claim 15, wherein the one or more processors are further configured to utilize the granted SR resource to request an uplink resource.

17. The apparatus of any one of claims 15-16, wherein the one or more processors are further configured to utilize the uplink resource for uplink data.

18. One or more computer-readable media having instructions that, when executed, cause an evolved Node B (eNB) to:

dynamically allocate a scheduling request (SR) resource;

provide SR configuration for the SR resource; and

receive a SR via the allocated SR resource.

19. The computer-readable media of claim 18 comprising one or more computer- readable media having instructions that, when executed, further cause the eNB to: grant an uplink resource in response to the SR.

20. The computer-readable media of claim 19, comprising one or more computer- readable media having instructions that, when executed, further cause the eNB to: deactivate the SR resource.

21 . The computer-readable media of claim 18, comprising one or more computer- readable media having instructions that, when executed, further cause the eNB to: dynamically allocate the SR resource for a group of UE devices.

22. An apparatus configured to be employed in a base station, the apparatus comprising:

a means to dynamically allocate a scheduling request (SR) resource;

a means to transmit the allocated SR resource using a physical downlink control channel (PDCCH);

a means to receive a SR via the allocated SR resource;

a means to grant an uplink resource based on the received SR; and

a means to receive an uplink data transmission using the uplink resource.

23. The apparatus of claim 22, further comprising:

a means to generate downlink control information (DCI) for the SR resource and transmit the DCI using the PDCCH.