WO2018036604A1 - Uplink resource allocation to transmit network-configured information and user device-configurable information for wireless networks - Google Patents

Uplink resource allocation to transmit network-configured information and user device-configurable information for wireless networks Download PDF

Info

Publication number
WO2018036604A1
WO2018036604A1 PCT/EP2016/069792 EP2016069792W WO2018036604A1 WO 2018036604 A1 WO2018036604 A1 WO 2018036604A1 EP 2016069792 W EP2016069792 W EP 2016069792W WO 2018036604 A1 WO2018036604 A1 WO 2018036604A1
Authority
WO
WIPO (PCT)
Prior art keywords
user device
control information
information
network
uplink
Prior art date
Application number
PCT/EP2016/069792
Other languages
French (fr)
Inventor
Timo Koskela
Samuli Heikki TURTINEN
Juho Mikko Oskari Pirskanen
Original Assignee
Nokia Solutions And Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2016/069792 priority Critical patent/WO2018036604A1/en
Publication of WO2018036604A1 publication Critical patent/WO2018036604A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
    • H04L1/0003—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate by switching between different modulation schemes
    • H04L1/0004—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate by switching between different modulation schemes applied to control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0027—Scheduling of signalling, e.g. occurrence thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information

Definitions

  • This description relates to communications, and in particular, to use of an uplink resource allocation by a user device to transmit both a network-configured information and a user device-configurable information within a wireless network.
  • a communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.
  • LTE Long Term Evolution
  • APs base stations or access points
  • eNBs enhanced Node AP
  • UE user equipments
  • LTE has included a number of improvements or developments.
  • the network e.g., a base station
  • the network may typically indicate a format of the uplink control channel to be used for uplink transmission by the user device UE.
  • LTE defines several possible physical uplink control channel
  • PUCCH formats by indicating a format code to the user device.
  • the indicated PUCCH format indicates the contents or fields that will be transmitted by the user device in the uplink control channel.
  • a method may include receiving, by a user device from a base station in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and transmitting, by the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
  • an apparatus includes at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: receive, by a user device from a base station in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and transmit, by the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
  • an apparatus includes means for receiving, by a user device from a base station in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and means for transmitting, by the user device via the allocated uplink channel resources, the network-configured information and the user device- configurable uplink control information.
  • a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: receiving, by a user device from a base station in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and transmitting, by the user device via the allocated uplink channel resources, the network- configured information and the user device-configurable uplink control information.
  • a method may include transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
  • an apparatus includes at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: transmit, by a base station to a user device in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and receive, by the base station from the user device via the allocated uplink channel resources, the network- configured information and the user device-configurable uplink control information.
  • an apparatus includes means for transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and means for receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
  • a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
  • FIG. 1 is a block diagram of a wireless network according to an example implementation.
  • FIG. 2 is a diagram illustrating operation of a system according to an example implementation.
  • FIG. 3 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to an example implementation.
  • FIG. 4 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to another example implementation.
  • FIG. 5 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to another example implementation.
  • FIG. 6 illustrates an uplink channel resource allocation that provides an extension field according to an example implementation.
  • FIG. 7 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to another example implementation.
  • FIG. 8 is a flow chart illustrating operation of a user device according to an example implementation.
  • FIG. 9 is a flow chart illustrating operation of a base station according to an example implementation.
  • FIG. 10 is a block diagram of a node or wireless station (e.g., network device, base station/access point or mobile station user device/UE) according to an example implementation.
  • a node or wireless station e.g., network device, base station/access point or mobile station user device/UE
  • FIG. 1 is a block diagram of a wireless network 130 according to an example implementation.
  • user devices 131, 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipment (UEs) may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB) or a network node.
  • AP access point
  • eNB enhanced Node B
  • At least part of the functionalities of an access point (AP), base station (BS) or (e)Node B (eNB) may be also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head.
  • BS (or AP) 134 provides wireless coverage within a cell 136, including to user devices 131, 132, 133 and 135. Although only four user devices are shown as being connected or attached to BS 134, any number of user devices may be provided. BS 134 is also connected to a core network 150 via a SI interface 151. This is merely one simple example of a wireless network, and others may be used.
  • a user device may refer to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, and a multimedia device, as examples.
  • SIM subscriber identification module
  • MS mobile station
  • PDA personal digital assistant
  • a handset a device using a wireless modem (alarm or measurement device, etc.)
  • laptop and/or touch screen computer a tablet, a phablet, a game console, a notebook, and a multimedia device, as examples.
  • a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a
  • the various example implementations or techniques described herein may be applied to various user devices, such as machine type communication (MTC) user devices, enhanced machine type communication (eMTC) user devices, Internet of Things (IoT) user devices, and/or narrowband IoT user devices.
  • IoT may refer to an ever-growing group of objects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices.
  • many sensor type applications or devices may monitor a physical condition or a status, and may send a report to a server or other network device, e.g., when an event occurs.
  • Machine Type Communications MTC, or Machine to Machine communications
  • MTC Machine to Machine communications
  • core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • EPC Evolved Packet Core
  • MME mobility management entity
  • gateways may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • the various example implementations may be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE- A, 5G, cmWave, and/or mmWave band networks, IoT, MTC, eMTC, etc., or any other wireless network or wireless technology.
  • wireless technologies or wireless networks such as LTE, LTE- A, 5G, cmWave, and/or mmWave band networks, IoT, MTC, eMTC, etc., or any other wireless network or wireless technology.
  • implementations may be applied to a variety of user devices, such as, for example, user devices, UEs, mobile stations, eMTC user devices, and/or IoT or narrowband IoT user devices.
  • user devices such as, for example, user devices, UEs, mobile stations, eMTC user devices, and/or IoT or narrowband IoT user devices.
  • the network may typically configure a format and resources of the uplink control channel to be used for uplink transmission by the user device/UE by RRC signaling.
  • LTE defines several possible physical uplink control channel (PUCCH) formats by indicating a format code to the user device.
  • the configured PUCCH format indicates the contents or fields that will be transmitted by the user device in the uplink control channel.
  • Some examples may include the following formats for uplink transmissions on the PUCCH:
  • Format 2a for a CSI channel state information, which may include channel quality indication/CQI, rank indication/RI and/or precoding matrix
  • an uplink channel that allows the user device to configure or determine the format or contents of at least a portion of the information that is transmitted in an uplink channel.
  • FIG. 2 is a diagram illustrating operation of a system according to an example implementation.
  • User device (UE) 132 may be in communication with a BS 134.
  • user device receives from BS 134 information identifying a type or format of network-configured information to be transmitted by the user device.
  • network-configured information may include information (e.g., data, control information, ...) that may be controlled or configured by a network entity, such as a BS, core network ISO, or any entity that is part of core network ISO, such as a base station controller or other network entity.
  • Network-configured may refer to information that is determined, controlled or configured by the network (or a network entity), as opposed to user device- configurable information that may be determined, controlled or configured by a user device or UE.
  • BS 134 may send a message (e.g., a radio resource control or RRC message, or other message) to indicate type or format of information (e.g., uplink control information or other information) to be transmitted to the BS 134.
  • a message e.g., a radio resource control or RRC message, or other message
  • user device 132 may receive a downlink control information (OCT) that may specify one or more fields to be provided to the BS 134 as uplink feedback from the user device 132.
  • OCT downlink control information
  • the network configured information may include physical layer control information.
  • the DCI (or other message) may include one or more fields or flags indicating which, if any, of one or more types of control information should be provided as feedback to the BS 134.
  • a field or flag may be provided to indicate whether acknowledgment negative acknowledgement (ACK NAK) feedback should be provided, e.g., to ACK or NAK data received by the user device 132, and a field or flag to indicate that channel state information (CSI) should be provided, which may include one or more of a channel quality indication (CQI), rank indication (RI) and/or a precoding matrix index
  • PMI Network Configuration Information
  • the network configured part may be predetermined (to include for example ACK ACK indication).
  • the amount of network configured information may also be determined by the used transmission mode (e.g. multi-antenna transmission) or a number of carriers used for transmission.
  • network-configured information e.g., physical layer control information or feedback
  • the network such as BS 134 or other network entity, may determine, control or configure the network-configured information to be transmitted by the UE, and then this determination or configuring (of information to be transmitted by the user device 132) is communicated by BS 134 to user device 132 via the information sent at 210.
  • the BS 134 may also send or provide an allocation (or grant) of uplink channel resources for user device 132 to transmit uplink control information to BS 134.
  • the channel resources may include, for example, time-frequency resources, and may be indicated, e.g., by providing a quantity of resources starting from a specific or know resource, and/or by providing an indication of specific time-frequency resources that are allocated or granted to user device 132 for transmitting uplink control
  • the allocation of uplink channel resources may be, for example, an allocation of uplink channel resources for an uplink control channel such as for a physical uplink control channel (PUCCH) or an allocation of uplink channel resources for a shared channel such as for a physical uplink shared channel PUSCH).
  • an uplink control channel such as for a physical uplink control channel (PUCCH)
  • an allocation of uplink channel resources for a shared channel such as for a physical uplink shared channel PUSCH.
  • the allocation of uplink resources may be indicated or provided to user device 132 within a downlink control information (OCT) sent from BS 132 to user device 132.
  • OCT downlink control information
  • both the information (sent at 210) identifying a type or format of network-configured information to be transmitted and an allocation (sent or provided at 212) of uplink channel resources for transmitting uplink control information may be provided by or within one message (e.g., within one DO message), or may be communicated by BS 134 via separate messages, e.g., messages 210 and 212 (e.g., a first message,. 210, to transmit information identifying a type or format of network-configured information and a second message, 212 identifying a type or format of network-configured information to be transmitted and an allocation of uplink channel resources for transmitting uplink control information).
  • messages 210 and 212 e.g., a first message,. 210, to transmit information identifying a type or format of network-configured information and a second message, 212 identifying a type or format of network-configured information to be transmitted and an allocation of uplink channel resources for transmitting uplink control information.
  • the network-configured information may include physical layer control information, such as, for example, physical layer ACK NAK feedback and/or CSI feedback from the user device, although these are merely some examples and other types of information may be used for the network-configured information.
  • physical layer control information such as, for example, physical layer ACK NAK feedback and/or CSI feedback from the user device, although these are merely some examples and other types of information may be used for the network-configured information.
  • a user device is provided with the allocation of uplink channel resources (at 212) for the transmission of uplink control information, including for the transmission of 1) network-configured information (e.g., as indicated by message 212) and 2) user-configurable uplink control information.
  • uplink channel resources may be used by the user device 132 to configure and transmit user device-configurable control information (e.g., rather than having the network configure the format or contents of the uplink control information as previous performed in LTE, for example).
  • the techniques of the various example implementations provide significantly more flexibility than the approach where the network defines the format or content of all information transmitted via uplink channel resources.
  • the user device 132 may determine a portion of the allocated uplink channel resources that is available for user device-configurable uplink control information. For example, the user device may determine a difference between the quantity of the allocated channel resources for uplink control information (indicated at 212, e.g., 22 bits), and a quantity of the network-configured information to be transmitted (indicated at 210, e.g., 2 bits for ACK NAK feedback).
  • user device may determine a (remaining) portion of the allocated uplink channel resources that are available for transmitted user-configured control information, e.g., by subtracting the quantity of the uplink channel resources (e.g., 22 bits) from the quantity of the network-configured information to be transmitted (e.g., 2 bits).
  • the quantity of the uplink channel resources e.g. 22 bits
  • the quantity of the network-configured information to be transmitted e.g., 2 bits.
  • any remaining portion e.g., not used or occupied for the transmission of the network-configured information
  • the user device 214 may configure the format or content of the user device-configuration control information, which may include, for example, user device selecting one or more fields or types of fields to be transmitted to the BS 134, e.g., depending on the state of the user device, what information needs to be transmitted, etc.
  • the user device may configure or select, e.g., for each uplink transmission of control information, which specific fields or types of data will be included in the user-configured uplink control information.
  • the user-configured control information may include any type of information, such as PHY layer control information, or any upper layer (at a network layer above PHY layer) control information, or other information.
  • the user device-configurable control information may include media access control (MAC) layer control information, or control information at or for another upper layer network entity, such as, for example, radio resource control (RRC) layer or entity, a packet data convergence protocol (PDCP), Radio Link Control (RLC) Entity, or other network layer or network entity.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • RLC Radio Link Control Entity
  • 3GPP 5G or New Radio
  • the entities PDCP and RLC may be identified by different names (Network Control Sublayer NCS , Radio Control Sublayer RCS respectively) and may perform different functions than in LTE
  • the user device transmits, via the allocated uplink channel resources, the network-configured information (as indicated by message at 210) and the user device-configurable uplink control information (e.g., which may include PHY layer or MAC layer control information, in an illustrative example implementation, or other information).
  • the network-configured information as indicated by message at 210
  • the user device-configurable uplink control information e.g., which may include PHY layer or MAC layer control information, in an illustrative example implementation, or other information.
  • FIG. 3 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to an example implementation.
  • an uplink channel resource allocation 310 is shown, e.g., for the transmission of uplink control information.
  • This resource allocation 310 (e.g., including specifying a quantity of resources and/or specific time-frequency resources) may be signaled or indicated by BS 134 to user device 132 via 212 in FIG. 2, for example.
  • the allocated uplink channel resources 310 may be allocated for an uplink control channel, such as for a physical uplink control channel (PUCCH), or for a physical uplink shared channel (PUSCH).
  • the allocated uplink channel resources 310 are resources for the transmission of 22 bits, but any number of resources may be provided.
  • the allocated uplink channel resources 310 may include resources for the transmission of network-configured information 312.
  • Network-configured information may include, for example: physical (PHY) layer control information, such as ACK NAK feedback or information, PHY layer channel state information (CSI), or other physical layer feedback or information (e.g. beam related feedback on physical layer such as BSI or BRI); media access control (MAC) layer control information, or other control information that may be configured by a network entity (e.g., by BS 134 or other network entity within core network 150 or other location) for transmission from user device 132.
  • PHY physical
  • CSI PHY layer channel state information
  • MAC media access control
  • the specific fields or content of network-configured information 312 and/or number of bits or resources to be used by the user device to transmit the network-configured information 312 via the allocated uplink channel resources 310 may be signaled or indicated by BS 134 to user device 132, e.g., via message (e.g., a downlink control information (DO)) at 210, FIG. 2.
  • message e.g., a downlink control information (DO)
  • the user device 132 may determine that 20 bits are provided as an uplink control channel (e.g., PUCCH) container 314 for the transmission of user device-configurable uplink control
  • PUCCH uplink control channel
  • the user device 132 may determine that 20 bits are provided for the transmission of user-configured uplink control information by subtracting the number of bits (2 bits) required for the network-configured information 312 from the number of bits (22 bits) provided by the allocated uplink channel resource allocation 310.
  • the container 314, which includes the user device-configurable control information may include, for one or more fields or control information elements: 1) a control element identifier (CE ID) 315 to identify a type of control information element or field that is provided or follows the CE ID 315, and 2) a control element information or field (e.g., shown CE information 316).
  • CE ID control element identifier
  • the container 314 may include, for one or more fields or control information elements: 1) a control element identifier (CE ID) 315 to identify a type of control information element or field that is provided or follows the CE ID 315, and 2) a control element information or field (e.g., shown CE information 316).
  • CE ID control element identifier
  • CE ID control element identifier
  • 16 bits are provided for the control element information 316 or field (which is identified by the CE ID 315).
  • the CE ID and control element information or field may be repeated within container 314 to identify (by CE ID 315) and then provide (by CE information 316) one or more additional fields or control element information within the user device-configurable uplink control information.
  • a specific CE ID may map to a specific LCID of MAC CE and this mapping can be configured by network
  • mapping MAC LCIDs (which are used to identify MAC CEs and data channels) is to optimize the header overhead when transmitting uplink control information.
  • the protocol complexity may be optimized by omitting the use of CE IDs and using the specified MAC CEs with full LCIDs with the cost of signaling overhead.
  • CE ID is replaces by LCID (with appropriate lengths)
  • previously known control information format types e.g., type la, lb, 2, .., see examples above for LTE
  • network may configure UE with "known" LTE control information format such as Format 2/2a/2b (that include the CQI/CSI) but allow user to override the specific field - the CQI/CSI information with user configured control information.
  • control information may be included within the user-configured control information (included within container 314), such as for example any physical (PHY) layer control information, any upper layer control information, such as MAC layer control information, radio resource control (RRC) control information, packet data control protocol (PDCP) control information, or control information with respect to other protocol layers or provided for or between protocol entities at any layer.
  • PHY physical
  • RRC radio resource control
  • PDCP packet data control protocol
  • the user-device configured control information may include, e.g., a user device ID that identifies the user device, such as a Temporary mobile subscriber identifier (TMSI) or cell-radio network temporary identifier (C-RNTI) or other identifier, channel state information (CSI) feedback which may include CQI (channel quality indication), RI (rank indication) and/or PMI (precoding matrix index); a buffer status report (BSR) that may report the status or level of fullness of a data buffer at the user device, or may report the number of containers (e.g., PUCCH containers) needed for transmission; a beam measurement report such as beam state information (BSI) or a beam refinement information (BRI); ACK (or NAK) information related MAC level feedback, e.g., to acknowledge request from BS or network; a clear-to-send (CTS) indication, e.g., for unlicensed band operation; status reports from ARQ entities/process
  • TMSI Temporary mobile
  • FIG. 4 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to another example implementation.
  • an uplink channel resource allocation 410 is shown, e.g., for the transmission of uplink control information.
  • the allocated uplink channel resources 410 are resources for the transmission of 32 bits, but any number of resources may be provided.
  • the allocated uplink channel resources 410 may include resources for the transmission of network-configured information 412, while any remaining resources within uplink channel resources 410 may be used for the transmission of user device-configurable control information.
  • the network-configured information 412 may include PHY layer control information (alternatively, the network-configured information may include MAC layer control information or information with respect to another protocol layer or protocol entity).
  • all of the fields transmitted within the 32 bits of allocated uplink channel resources 410, other than 4 bits of network- configured information 412, may be user-configured control information, e.g., dynamically configured by the user device based on need or status of the user device 132.
  • control element IDs may each indicate the presence of a specific or identified type of control element information or field within the user device-configurable control information.
  • CE ID end of data
  • CE ID end of data
  • the user configured information may be limited by network to include, e.g., a specific amount of Control Elements (CE) per container; in this case the EOD/padding need not to be indicated.
  • CE Control Elements
  • FIG. 5 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to another example implementation.
  • an uplink channel resource allocation 510 is shown, e.g., for the transmission of uplink control information.
  • the allocated uplink channel resources 510 are resources for the transmission of N bits, including for the transmission of K-bits for network-configured information 512 (e.g., which may be physical layer information, MAC layer information, etc.).
  • network-configured information 512 e.g., which may be physical layer information, MAC layer information, etc.
  • FIG. 5 illustrates an example of a general structure of an uplink channel resource allocation (e.g., PUCCH resource allocation) of N-bits for the transmission of both: 1) network-configured information (K-bits), e.g., network- configured PHY information, and 2) dynamically generated user-configurable
  • K-bits network-configured information
  • PHY information e.g., network- configured PHY information
  • MAC content in an illustrative example.
  • the network-configured information 512 may depend on the various aspects as a configuration (by higher layer, e.g., RRC layer message from network entity) or explicit request by network or implicit indication (e.g., where the user device will need to send PHY layer feedback in the allocated resource, e.g., to ACK NAK received data).
  • a MAC entity at the user device 132 may select the contents (one or more MAC level fields) and transmit M - control element (or information elements).
  • M - control element or information elements
  • CE ID control element identifier
  • the number of control element information items may depend on the amount of available resources, and the amount of control information to be transmitted.
  • the CE ID field length is set to 4 bits in the example shown in FIG. 5 only as an example.
  • the control element information item depends on the CE ID value (which indicates the type of control element information).
  • the length and type of the control element information is known, or can be determined, based on the CE ID (these may be preconfigured or fixed in the specification).
  • CE Di indicates an information type for CE IDi information
  • CE ID 2 indicates an information type for CE ID2
  • CE IDM indicates an information type for CE IDM information, etc.
  • an extension field may follow each CE ID to indicate whether or not another CE ID (and corresponding control element information or field) will follow.
  • FIG. 6 illustrates an uplink channel resource allocation that provides an extension field according to an example implementation.
  • an uplink channel resource allocation 610 is shown, e.g., for the transmission of uplink control information.
  • an extension field (E) 620 is set to 1 after CE IDi to indicate that further (or more) CE IDs are provided within the container or within the allocated uplink channel resources.
  • CE ID 2 follows CE IDi.
  • extension field 622 is set to 0 to indicate that no more CE IDs are provided within the container or within the uplink channel resources 610.
  • FIG. 7 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to another example implementation.
  • the allocated uplink channel resources 710 may include resources for a network-configured information, and for the transmission of user device-configurable control information, e.g., within a control information container 720.
  • the information received in the control information container (or user device-configurable control information) 720 may be passed up to a MAC entity (or other upper layer protocol entity) at the BS 134 for parsing, interpreting, processing and/or forwarding.
  • CE ID 720 data
  • CE ID data
  • MAC protocol entities or other entities at the user device 132 and/or BS 134 may store and use a mapping between this CE ID value 722 and a LCID for the data, so that the received data can be forwarded by BS 134 in accordance with the corresponding LCID, for example. In this manner, it may be unnecessary to include a relatively long LCID value within the control information container 720.
  • a shorter CE ID may be included within container 720.
  • Using a shorter CE ID (which may be shorter than the LCID) may allow more bits for data, while the CE ID/LCID map at the BS 134 may allow the BS 134 to determine the LCID for the data (based on received CE ID 722 and the CE ID/LCID mapping) and then forward the data according to the associated LCID for this data.
  • the network-configured information may be optional. Or, a size of the network-configured information may be indicated as a value between zero and some upper threshold number. Thus, in the case where 0 bits are indicated by BS 134 for the network-configured information, this means that the entire allocation of uplink channel resources can be used for the control information container or for the transmission of user device-configurable control information.
  • control information (e.g., PUCCH) container may have a fixed size of K -bits or octets, this allows pre-determined MAC CE formats to be defined.
  • PUCCH container size may be configured by higher layers (e.g., MAC layer or higher).
  • the network may dynamically indicate/schedule the number of PUCCH (or uplink control information) resource elements for the user device.
  • a control information resource element (which may be or include the uplink channel resources allocated for uplink control information, including resources for network-controlled information and resources for a control information container for user device-configurable control information) is a smallest unit of allocation for the uplink control information, e.g., one resource element could have a size of 22bits. By allocating/aggregating more of these resource elements the number of available bits for uplink control information is increased.
  • the amount of resources may based, e.g., on the configured transmission mode (single antenna, multi-antenna/ MIMO/ beamforming, carrier aggregation etc..) or the amount of resource are explicitly indicated.
  • Explicit indication may allocate uplink control information resources (e.g in a DO) by pointing to a frequency index and the feedback timing and additionally the number of resource elements or amount of frequency resources. In some cases the uplink control timing with respect to the DL transmission be fixed.
  • the user device may transmit user device-configurable control information via one or more of these control information resource elements, either separately, or use a combination or multiple resource elements.
  • a separate resource allocation may be received for each control information resource element, and then user device may separately transmit user device-configurable control information via each or one or more of the containers provided by the separate resource allocations (as defined in FIG.3).
  • one resource allocation may be received by the user device 132 which allocates channel resources to allow for network-configured
  • Network-configured control information may be mapped to a single resource element while rest of the elements are provided as a single or separate containers to upper layer (e.g., MAC layer).
  • the feedback resources may be preconfigured by RRC signaling (amount of uplink resource elements, the periodicity, implicit mapping based on DL-SCH (downlink scheduling) allocation) or alternatively the PUCCH may be scheduled by network.
  • the uplink control information may be embedded to part of uplink contention based transmission.
  • the network may schedule a short uplink allocation (allocate uplink channel resources to user device) for fast transmission of uplink control information and potential small amount of uplink data.
  • SR scheduling request
  • a physical layer (PHY) entity may determine the available resources (available for user device-configurable information), and indicate this amount of available UL resources to a MAC layer or MAC entity at the user device 132, based on the configured feedback format (indicated by DCI):
  • a specific PUCCH format may be determined which defines the amount of physical layer information and the container size to be included.
  • a generic PUSCH format does not allow any uplink physical layer control information to be transmitted but all resources are used by MAC entity for network-configured MAC layer information and user device-configurable information, which may multiplex both control and data into uplink transmission on the allocated resources.
  • the uplink control information when transmitted with uplink data, can be included as a first part of transport block and it may have a different MCS (modulation and/or coding scheme) than the data.
  • the uplink control information may also have its own codeword (a channel coded transport block / a separate data stream) which is mapped to one or more transmission layers.
  • the network-configured information may be
  • the control information container (e.g., which may include data or other information) may be transmitted using a second MCS, that is different from the first MCS.
  • the CE ID 722 may be transmitted with a different MCS as compared to the data within the container 720.
  • data and control information may be transmitted using different MCS.
  • the network-configured information may include physical layer information, such as HARQ related feedback, such as: ACK/NAK feedback; or ACK/NAK feedback for MIMO (multi-input, multi-output) / per carrier ACK/NAK feedback, and/or uplink sounding symbols for mobility/channel quality measurements.
  • physical layer information such as HARQ related feedback, such as: ACK/NAK feedback; or ACK/NAK feedback for MIMO (multi-input, multi-output) / per carrier ACK/NAK feedback, and/or uplink sounding symbols for mobility/channel quality measurements.
  • the user device may transmit a higher layer data PDU (protocol data unit) in the PUCCH container.
  • PDU protocol data unit
  • the data may be sent only from a specific logical channel (configured by network, thus no explicit LCID need to be present for receiver side mapping, or no CE ID/LCID map is necessary).
  • the uplink control information is transmitted on PUCCH via allocated channel resources, where the network-configured information (e.g., which may include physical layer content) such as ACK/NAK feedback may be sent via N bits and a remainder of the PUCCH content (or remainder of allocated uplink channel resources) is provided for user device-configurable information (which may include MAC layer control information, for example).
  • the network-configured information e.g., which may include physical layer content
  • ACK/NAK feedback may be sent via N bits and a remainder of the PUCCH content (or remainder of allocated uplink channel resources) is provided for user device-configurable information (which may include MAC layer control information, for example).
  • One or more of the example implementations may have one or more advantages, such as, for example:
  • user device may dynamically decide what control information is to be included in the container. This may allow the user device to prioritize specific kinds of control information to be transmitted, rather than only transmitting what the network has configured for transmission (which may meet the needs of the user device, and may then cause the user device to obtain additional resources to transmit what it needs to transmit).
  • the flexible uplink approach to allow a portion of the uplink channel resources to be used for user device-configurable control information to be transmitted may also provide a more efficient use of resources.
  • [0082] Provides a flexible way to prioritize transmission of the user device- configurable control information (e.g., MAC CEs/information elements) via the allocated PUCCH channel resources; the feedback format within container is not fixed, so that the user device may UE could prioritize e.g. beam state information over CSI feedback
  • the user device- configurable control information e.g., MAC CEs/information elements
  • a control information container can be included in PUSCH transmission and transmitted together with uplink data, to provide both control information and data. Also, for example, data may be transmitted within the control information container, either within PUSCH or within PUCCH.
  • FIG. 8 is a flow chart illustrating operation of a user device according to an example implementation.
  • Operation 810 includes receiving, by a user device from a base station in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information.
  • operation 820 includes transmitting, by the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
  • the method may further include determining, by the user device, a portion of the allocated uplink channel resources available to the user device for transmitting user-device configurable uplink control information; and configuring, by the user device, a format of the user device-configurable uplink control information.
  • the configuring, by the user device, a format of the user device-configurable uplink control information may include: selecting, by the user device, one or more fields of uplink control information to be transmitted within the user device-configurable control information and via the allocated channel resources.
  • the information identifying a type or format of network-configured information to be transmitted by the user device is received by the user device via a first message, and wherein the allocation of uplink channel resources for the transmission of uplink control information is received by the user device via a second message.
  • both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station in one message.
  • both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station via downlink control information (OCT) received in a message.
  • OCT downlink control information
  • the information identifying a type or format of network-configured information to be transmitted by the user device includes: a downlink control information (DCI) that identifies that the user device should transmit to the base station at least one of the following types of uplink control information: acknowledgement/negative
  • DCI downlink control information
  • acknowledgement acknowledgement
  • CSI channel state information
  • the receiving an allocation of uplink channel resources for the transmission of uplink control information includes at least one of: receiving an allocation of uplink channel resources in a physical uplink control channel (PUCCH) for the transmission of uplink control information; and receiving an allocation of uplink channel resources in a physical uplink shared channel (PUSCH) for the transmission of uplink control information.
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • the receiving may include: receiving an allocation of uplink control channel resources in a physical uplink control channel (PUCCH) and information that identifies network- configured physical layer control information to be transmitted via the allocated uplink channel resources.
  • PUCCH physical uplink control channel
  • the cletermining may include: determining, by the user device, a portion of the allocated uplink channel resources available to the user device for transmitting user-device configurable uplink control information, based on a difference between an amount of allocated uplink channel resources and an amount of resources required to transmit the network-configured information.
  • the transmitting may include: transmitting, by the user device via the allocated uplink channel resources, network-configured physical layer control information configured by a network entity and upper layer control information configured by the user device, wherein an amount of allocated uplink channel resources and the network-configured physical layer control information are configured or determined by a network entity, and the content or format of the upper layer control information is determined or configured by the user device.
  • the user-device configurable control information may include the following information for one or more control information elements: a control element identifier that identifies a type of control information element or type of field that is present in the user device- configurable control information; and a control information element or field.
  • the user device-configurable uplink control information may include upper layer control information for any network layer above a physical (PHY) layer.
  • PHY physical
  • the user device-configurable uplink control information comprises control information for a media access control (MAC) layer.
  • MAC media access control
  • the network-configured information may include one or more network-determined fields of physical layer control information.
  • the network-configured information comprises one or more network-determined fields of media access control (MAC) layer control information.
  • MAC media access control
  • the network-configured information may include physical layer acknowledgement/negative acknowledgement (ACK/NAK) information.
  • ACK/NAK physical layer acknowledgement/negative acknowledgement
  • the user device-configurable uplink control information may include: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
  • the user device-configurable uplink control information includes: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
  • an apparatus includes at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: receive, by a user device from a base station in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and transmit, by the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
  • a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: receiving, by a user device from a base station in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and transmitting, by the user device via the allocated uplink channel resources, the network- configured information and the user device-configurable uplink control information.
  • an apparatus includes means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving, by a user device from a base station in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and means for transmitting, by the user device via the allocated uplink channel resources, the network- configured information and the user device-configurable uplink control information.
  • means e.g., 1002A/1002B and/or 1004, FIG. 10
  • the apparatus may further include means (e.g., 1002A/1002B and/or 1004, FIG. 10) for determining, by the user device, a portion of the allocated uplink channel resources available to the user device for transmitting user-device configurable uplink control information; and means (e.g., 1002A/1002B and/or 1004, FIG. 10) for configuring, by the user device, a format of the user device-configurable uplink control information.
  • means e.g., 1002A/1002B and/or 1004, FIG. 10
  • the means for configuring, by the user device, a format of the user device-configurable uplink control information may include: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for selecting, by the user device, one or more fields of uplink control information to be transmitted within the user device-configurable control information and via the allocated channel resources.
  • the information identifying a type or format of network-configured information to be transmitted by the user device is received by the user device via a first message, and wherein the allocation of uplink channel resources for the transmission of uplink control information is received by the user device via a second message.
  • both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station in one message.
  • both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station via downlink control information (OCT) received in a message.
  • OCT downlink control information
  • the information identifying a type or format of network-configured information to be transmitted by the user device includes: a downlink control information (OCT) that identifies that the user device should transmit to the base station at least one of the following types of uplink control information: acknowledgement/negative acknowledgement (ACK/NAK) feedback for received data; and channel state information (CSI) feedback.
  • OCT downlink control information
  • ACK/NAK acknowledgement/negative acknowledgement
  • CSI channel state information
  • the means for receiving an allocation of uplink channel resources for the transmission of uplink control information includes at least one of: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving an allocation of uplink channel resources in a physical uplink control channel (PUCCH) for the transmission of uplink control information; and means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving an allocation of uplink channel resources in a physical uplink shared channel (PUSCH) for the transmission of uplink control information.
  • means e.g., 1002A/1002B and/or 1004, FIG. 10 for receiving an allocation of uplink channel resources in a physical uplink shared channel (PUSCH) for the transmission of uplink control information.
  • PUSCH physical uplink shared channel
  • the means for receiving may include: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving an allocation of uplink control channel resources in a physical uplink control channel (PUCCH) and information that identifies network-configured physical layer control information to be transmitted via the allocated uplink channel resources.
  • means e.g., 1002A/1002B and/or 1004, FIG. 10.
  • the means for cietermining may include: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for determining, by the user device, a portion of the allocated uplink channel resources available to the user device for transmitting user-device configurable uplink control information, based on a difference between an amount of allocated uplink channel resources and an amount of resources required to transmit the network-configured information.
  • the means for transmitting may include: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for transmitting, by the user device via the allocated uplink channel resources, network- configured physical layer control information configured by a network entity and upper layer control information configured by the user device, wherein an amount of allocated uplink channel resources and the network-configured physical layer control information are configured or determined by a network entity, and the content or format of the upper layer control information is determined or configured by the user device.
  • the user-device configurable control information may include the following information for one or more control information elements: a control element identifier that identifies a type of control information element or type of field that is present in the user device-configurable control information; and a control information element or field.
  • the user device-configurable uplink control information may include upper layer control information for any network layer above a physical (PHY) layer.
  • PHY physical
  • the user device-configurable uplink control information may include control information for a media access control (MAC) layer.
  • MAC media access control
  • the network- configured information may include one or more network-determined fields of physical layer control information.
  • the network- configured information may include one or more network-determined fields of media access control (MAC) layer control information.
  • MAC media access control
  • the network- configured information may include physical layer acknowledgement/negative acknowledgement (ACK/NAK) information.
  • ACK/NAK physical layer acknowledgement/negative acknowledgement
  • the user device-configurable uplink control information may include: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
  • the apparatus further including means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving, by the user device from the base station, information granting the user device permission to transmit data within the user device-configurable uplink control information; and wherein the user device-configurable uplink control information includes: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
  • FIG. 9 is a flow chart illustrating operation of a base station according to an example implementation.
  • Operation 910 includes transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information.
  • Operation 920 includes receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
  • the information identifying a type or format of network-configured information to be transmitted by the user device is transmitted by the base station via a first message, and wherein the allocation of uplink channel resources for the transmission of uplink control information is transmitted by the base station via a second message.
  • both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are transmitted by the base station in one message.
  • the transmitting an allocation of uplink channel resources for the transmission of uplink control information includes at least one of: transmitting an allocation of uplink channel resources in a physical uplink control channel (PUCCH) for the transmission of uplink control information; and transmitting an allocation of uplink channel resources in a physical uplink shared channel (PUSCH) for the transmission of uplink control information.
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station via downlink control information (OCT) received in a message.
  • OCT downlink control information
  • the information identifying a type or format of network-configured information to be transmitted by the user device may include: a downlink control information (OCT) that identifies that the user device should transmit to the base station at least one of the following types of uplink control information: acknowledgement/negative
  • OCT downlink control information
  • CSI information feedback
  • the receiving may include: receiving, by the base station via the allocated uplink channel resources, network-configured physical layer control information configured by a network entity and upper layer control information configured by the user device, wherein an amount of allocated uplink channel resources and the network-configured physical layer control information are configured or determined by a network entity, and the content or format of the upper layer control information is determined or configured by the user device.
  • the user device-configurable uplink control information may include: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
  • the method may further include transmitting, by the base station to the user device, information granting the user device permission to transmit data within the user device- configurable uplink control information; and wherein the user device-configurable uplink control information includes: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
  • an apparatus includes at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: transmit, by a base station to a user device in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and receive, by the base station from the user device via the allocated uplink channel resources, the network- configured information and the user device-configurable uplink control information.
  • a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
  • an apparatus includes means (e.g., 1002A/1002B and/or 1004, FIG. 10) for transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
  • means e.g., 1002A/1002B and/or 1004, FIG. 10.
  • the information identifying a type or format of network-configured information to be transmitted by the user device is transmitted by the base station via a first message, and wherein the allocation of uplink channel resources for the transmission of uplink control information is transmitted by the base station via a second message.
  • both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are transmitted by the base station in one message.
  • the means for transmitting an allocation of uplink channel resources for the transmission of uplink control information includes at least one of: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for transmitting an allocation of uplink channel resources in a physical uplink control channel (PUCCH) for the transmission of uplink control information; and means (e.g., 1002A/1002B and/or 1004, FIG. 10) for transmitting an allocation of uplink channel resources in a physical uplink shared channel (PUSCH) for the transmission of uplink control information.
  • means e.g., 1002A/1002B and/or 1004, FIG.
  • PUSCH physical uplink shared channel
  • both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station via downlink control information (OCT) received in a message.
  • OCT downlink control information
  • the information identifying a type or format of network-configured information to be transmitted by the user device may include: a downlink control information (DO) that identifies that the user device should transmit to the base station at least one of the following types of uplink control information: acknowledgement/negative acknowledgement (ACK/NAK) feedback for received data; and channel state information (CSI) feedback.
  • DO downlink control information
  • ACK/NAK acknowledgement/negative acknowledgement
  • CSI channel state information
  • the means for receiving may include: means (e.g., 1002A/1002B and/or 1004, FIG.
  • the user device-configurable uplink control information may include: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
  • the apparatus may further include means (e.g., 1002A/1002B and/or 1004, FIG. 10) for transmitting, by the base station to the user device, information granting the user device permission to transmit data within the user device-configurable uplink control information; and wherein the user device-configurable uplink control information includes: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
  • means e.g., 1002A/1002B and/or 1004, FIG. 10
  • the user device-configurable uplink control information includes: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
  • FIG. 10 is a block diagram of a wireless station (e.g., AP or user device) 1000 according to an example implementation.
  • the wireless station 1000 may include, for example, one or two RF (radio frequency) or wireless transceivers 1002A, 1002B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals.
  • the wireless station also includes a processor or control unit/entity (controller) 1004 to execute instructions or software and control transmission and receptions of signals, and a memory 1006 to store data and/or instructions.
  • Processor 1004 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein.
  • Processor 1004 which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 1002 (1002A or 1002B).
  • Processor 1004 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 1002, for example).
  • Processor 1004 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above.
  • Processor 1004 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these.
  • processor 1004 and transceiver 1002 together may be considered as a wireless transmitter/receiver system, for example.
  • a controller (or processor) 1008 may execute software and instructions, and may provide overall control for the station 1000, and may provide control for other systems not shown in FIG. 10, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 1000, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.
  • controlling input/output devices e.g., display, keypad
  • software for one or more applications that may be provided on wireless station 1000, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.
  • a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 1004, or other controller or processor, performing one or more of the functions or tasks described above.
  • transceivers 1002A/1002B may receive signals or data and/or transmit or send signals or data.
  • Processor 1004 (and possibly transceivers 1002A/1002B) may control the RF or wireless transceiver 1002A or 1002B to receive, send, broadcast or transmit signals or data.
  • SG Another example of a suitable communications system is the SG concept. It is assumed that network architecture in SG will be quite similar to that of the LTE-advanced. 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple input - multiple output
  • NFV network functions virtualization
  • a virtualized network function may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized.
  • radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent.
  • Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Implementations may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium. Implementations of the various techniques may also include implementations provided via transitory signals or media, and/or programs and/or software
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program.
  • carrier include a record medium, computer memory, readonly memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • implementations of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities).
  • CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, etc embedded in physical objects at different locations.
  • ICT devices sensors, actuators, processors microcontrollers, etc.
  • Mobile cyber physical systems in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber- physical systems. Therefore, various implementations of techniques described herein may be provided via one or more of these technologies.
  • a computer program such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment.
  • a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
  • Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset.
  • a processor will receive instructions and data from a read-only memory or a random access memory or both.
  • Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data.
  • a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
  • Information carriers suitable for embodying computer program instructions and data include all forms of non- volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • the processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.
  • implementations may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.
  • a display device e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor
  • a user interface such as a keyboard and a pointing device, e.g., a mouse or a trackball
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
  • Implementations may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back-end, middleware, or front-end components.
  • Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
  • LAN local area network
  • WAN wide area network

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

A technique includes receiving, by a user device from a base station in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an al location of uplink channel resources for the transmission of uplink control information, and transmitting, by the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.

Description

Uplink Resource Allocation to Transmit Network-Configured Information and User Device-Configurable Information For Wireless Networks
TECHNICAL FIELD
[0001 ] This description relates to communications, and in particular, to use of an uplink resource allocation by a user device to transmit both a network-configured information and a user device-configurable information within a wireless network.
BACKGROUND
[0002] A communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.
[0003] An example of a cellular communication system is an architecture that is being standardized by the 3rd Generation Partnership Project (3GPP). A recent development in this field is often referred to as the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology. E- UTRA (evolved UMTS Terrestrial Radio Access) is the air interface of 3GPP's Long Term Evolution (LTE) upgrade path for mobile networks. In LTE, base stations or access points (APs), which are referred to as enhanced Node AP (eNBs), provide wireless access within a coverage area or cell. In LTE, mobile devices, or mobile stations are referred to as user equipments (UE). LTE has included a number of improvements or developments.
[0004] In LTE, the network (e.g., a base station) may typically indicate a format of the uplink control channel to be used for uplink transmission by the user device UE. Thus, for example, LTE defines several possible physical uplink control channel
(PUCCH) formats by indicating a format code to the user device. The indicated PUCCH format indicates the contents or fields that will be transmitted by the user device in the uplink control channel.
SUMMARY
[0005] According to an example implementation, a method may include receiving, by a user device from a base station in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and transmitting, by the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
[0006] According to an example implementation, an apparatus includes at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: receive, by a user device from a base station in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and transmit, by the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
[0007] According to an example implementation, an apparatus includes means for receiving, by a user device from a base station in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and means for transmitting, by the user device via the allocated uplink channel resources, the network-configured information and the user device- configurable uplink control information.
[0008] According to an example implementation, a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: receiving, by a user device from a base station in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and transmitting, by the user device via the allocated uplink channel resources, the network- configured information and the user device-configurable uplink control information.
[0009] According to an example implementation, a method may include transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
[0010] According to an example implementation, an apparatus includes at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: transmit, by a base station to a user device in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and receive, by the base station from the user device via the allocated uplink channel resources, the network- configured information and the user device-configurable uplink control information.
[0011 ] According to an example implementation, an apparatus includes means for transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and means for receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
[0012] According to an example implementation, a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
[0013] The details of one or more examples of implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014] FIG. 1 is a block diagram of a wireless network according to an example implementation.
[0015] FIG. 2 is a diagram illustrating operation of a system according to an example implementation.
[0016] FIG. 3 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to an example implementation.
[0017] FIG. 4 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to another example implementation.
[0018] FIG. 5 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to another example implementation.
[0019] FIG. 6 illustrates an uplink channel resource allocation that provides an extension field according to an example implementation.
[0020] FIG. 7 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to another example implementation.
[0021 ] FIG. 8 is a flow chart illustrating operation of a user device according to an example implementation.
[0022] FIG. 9 is a flow chart illustrating operation of a base station according to an example implementation.
[0023] FIG. 10 is a block diagram of a node or wireless station (e.g., network device, base station/access point or mobile station user device/UE) according to an example implementation.
DETAILED DESCRIPTION
[0024] FIG. 1 is a block diagram of a wireless network 130 according to an example implementation. In the wireless network 130 of FIG. 1, user devices 131, 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipment (UEs), may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB) or a network node. At least part of the functionalities of an access point (AP), base station (BS) or (e)Node B (eNB) may be also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head. BS (or AP) 134 provides wireless coverage within a cell 136, including to user devices 131, 132, 133 and 135. Although only four user devices are shown as being connected or attached to BS 134, any number of user devices may be provided. BS 134 is also connected to a core network 150 via a SI interface 151. This is merely one simple example of a wireless network, and others may be used.
[0025] A user device (user terminal, user equipment (UE)) may refer to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, and a multimedia device, as examples. It should be appreciated that a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.
[0026] By way of illustrative example, the various example implementations or techniques described herein may be applied to various user devices, such as machine type communication (MTC) user devices, enhanced machine type communication (eMTC) user devices, Internet of Things (IoT) user devices, and/or narrowband IoT user devices. IoT may refer to an ever-growing group of objects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices. For example, many sensor type applications or devices may monitor a physical condition or a status, and may send a report to a server or other network device, e.g., when an event occurs. Machine Type Communications (MTC, or Machine to Machine communications) may, for example, be characterized by fully automatic data generation, exchange, processing and actuation among intelligent machines, with or without intervention of humans.
[0027] In LTE (as an example), core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
[0028] The various example implementations may be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE- A, 5G, cmWave, and/or mmWave band networks, IoT, MTC, eMTC, etc., or any other wireless network or wireless technology. These example networks or technologies are provided only as illustrative examples, and the various example implementations may be applied to any wireless technology/wireless network. Also, as noted, the various example
implementations may be applied to a variety of user devices, such as, for example, user devices, UEs, mobile stations, eMTC user devices, and/or IoT or narrowband IoT user devices.
[0029] In LTE, as an illustrative example, the network (e.g., a base station or other network entity) may typically configure a format and resources of the uplink control channel to be used for uplink transmission by the user device/UE by RRC signaling. Thus, for example, LTE defines several possible physical uplink control channel (PUCCH) formats by indicating a format code to the user device. The configured PUCCH format indicates the contents or fields that will be transmitted by the user device in the uplink control channel. Some examples may include the following formats for uplink transmissions on the PUCCH:
[0030] Format la for 1-bit HARQ (hybrid automatic repeat request)-ACK
(acknowledgement) or in case of FDD (frequency division duplex) or FDD-TDD (time division duplex) primary cell frame structure type 1 for 1-bit HARQ-ACK with positive SR (scheduling request).
[0031 ] Format lb for 2-bit HARQ-ACK or for 2-bit HARQ-ACK with positive SR.
[0032] Format lb for up to 4-bit HARQ-ACK with channel selection when the UE is configured with more than one serving cell or, in the case of TDD, when the UE is configured with a single serving cell.
[0033] Format 1 for positive SR.
[0034] Format 2 for a CSI (channel state information) report when not multiplexed with HARQ-ACK.
[0035] Format 2a for a CSI (channel state information, which may include channel quality indication/CQI, rank indication/RI and/or precoding matrix
indication PMI)) report multiplexed with 1-bit HARQ-ACK for normal cyclic prefix.
[0036] Format 2b for a CSI report multiplexed with 2-bit HARQ-ACK for normal cyclic prefix.
[0037] Format 2 for a CSI report multiplexed with HARQ-ACK for extended cyclic prefix.
[0038] By specifying the format for the uplink control channel to be used by the user device, this may allow the BS to decode received information in a known format. However, this type of approach may, at least in some cases, be very inflexible, as it does not allow for the user device to configure or change the format or content of it uplink control channel.
[0039] Therefore, according to an example implementation, a more flexible approach is provided for an uplink channel that allows the user device to configure or determine the format or contents of at least a portion of the information that is transmitted in an uplink channel.
[0040] FIG. 2 is a diagram illustrating operation of a system according to an example implementation. User device (UE) 132 may be in communication with a BS 134. At 210, user device receives from BS 134 information identifying a type or format of network-configured information to be transmitted by the user device. In general, network-configured information may include information (e.g., data, control information, ...) that may be controlled or configured by a network entity, such as a BS, core network ISO, or any entity that is part of core network ISO, such as a base station controller or other network entity. Network-configured may refer to information that is determined, controlled or configured by the network (or a network entity), as opposed to user device- configurable information that may be determined, controlled or configured by a user device or UE.
[0041 ] For example, at 210 in FIG. 2, BS 134 may send a message (e.g., a radio resource control or RRC message, or other message) to indicate type or format of information (e.g., uplink control information or other information) to be transmitted to the BS 134. Alternatively, user device 132 may receive a downlink control information (OCT) that may specify one or more fields to be provided to the BS 134 as uplink feedback from the user device 132. In an illustrative example, the network configured information may include physical layer control information. For example, the DCI (or other message) may include one or more fields or flags indicating which, if any, of one or more types of control information should be provided as feedback to the BS 134. For example, a field or flag may be provided to indicate whether acknowledgment negative acknowledgement (ACK NAK) feedback should be provided, e.g., to ACK or NAK data received by the user device 132, and a field or flag to indicate that channel state information (CSI) should be provided, which may include one or more of a channel quality indication (CQI), rank indication (RI) and/or a precoding matrix index
(PMI).Also such network configured information can be preconfigured so it is implicitly known what fields are present for example if DCI allocates resources for downlink data transmission and in the same message allocates UL resources for feedback, the network configured part may be predetermined (to include for example ACK ACK indication). The amount of network configured information may also be determined by the used transmission mode (e.g. multi-antenna transmission) or a number of carriers used for transmission.
[0042] These are merely some examples of the types of network-configured information (e.g., physical layer control information or feedback) that may be indicated via 210 to be provided by user device 132. Therefore, the network, such as BS 134 or other network entity, may determine, control or configure the network-configured information to be transmitted by the UE, and then this determination or configuring (of information to be transmitted by the user device 132) is communicated by BS 134 to user device 132 via the information sent at 210.
[0043] At 212, the BS 134 may also send or provide an allocation (or grant) of uplink channel resources for user device 132 to transmit uplink control information to BS 134. The channel resources may include, for example, time-frequency resources, and may be indicated, e.g., by providing a quantity of resources starting from a specific or know resource, and/or by providing an indication of specific time-frequency resources that are allocated or granted to user device 132 for transmitting uplink control
information. The allocation of uplink channel resources may be, for example, an allocation of uplink channel resources for an uplink control channel such as for a physical uplink control channel (PUCCH) or an allocation of uplink channel resources for a shared channel such as for a physical uplink shared channel PUSCH). In an example
implementation, the allocation of uplink resources may be indicated or provided to user device 132 within a downlink control information (OCT) sent from BS 132 to user device 132.
[0044] In one example implementation, both the information (sent at 210) identifying a type or format of network-configured information to be transmitted and an allocation (sent or provided at 212) of uplink channel resources for transmitting uplink control information may be provided by or within one message (e.g., within one DO message), or may be communicated by BS 134 via separate messages, e.g., messages 210 and 212 (e.g., a first message,. 210, to transmit information identifying a type or format of network-configured information and a second message, 212 identifying a type or format of network-configured information to be transmitted and an allocation of uplink channel resources for transmitting uplink control information).
[0045] According to an example implementation, the network-configured information may include physical layer control information, such as, for example, physical layer ACK NAK feedback and/or CSI feedback from the user device, although these are merely some examples and other types of information may be used for the network-configured information.
[0046] According to an example implementation, a user device is provided with the allocation of uplink channel resources (at 212) for the transmission of uplink control information, including for the transmission of 1) network-configured information (e.g., as indicated by message 212) and 2) user-configurable uplink control information. In this manner, at least a portion of the allocated uplink channel resources may be used by the user device 132 to configure and transmit user device-configurable control information (e.g., rather than having the network configure the format or contents of the uplink control information as previous performed in LTE, for example). Thus, by allowing at least a portion (e.g., if not all) of allocated uplink channel resources for transmission of control information to be used for the transmission of user device-configurable control information, the techniques of the various example implementations provide significantly more flexibility than the approach where the network defines the format or content of all information transmitted via uplink channel resources.
[0047] Therefore, according to an example implementation, at 214, the user device 132 may determine a portion of the allocated uplink channel resources that is available for user device-configurable uplink control information. For example, the user device may determine a difference between the quantity of the allocated channel resources for uplink control information (indicated at 212, e.g., 22 bits), and a quantity of the network-configured information to be transmitted (indicated at 210, e.g., 2 bits for ACK NAK feedback). Thus, in this illustrative example, user device may determine a (remaining) portion of the allocated uplink channel resources that are available for transmitted user-configured control information, e.g., by subtracting the quantity of the uplink channel resources (e.g., 22 bits) from the quantity of the network-configured information to be transmitted (e.g., 2 bits). Thus, according to an example implementation, any remaining portion (e.g., not used or occupied for the transmission of the network-configured information) of the allocated uplink channel resources may be used by the user device to transmit user-configured control information (e.g., 22 bits - 2 bits = 20 bits in this example are available for user -configured control information).
[0048] Also, at 214, the user device 214 may configure the format or content of the user device-configuration control information, which may include, for example, user device selecting one or more fields or types of fields to be transmitted to the BS 134, e.g., depending on the state of the user device, what information needs to be transmitted, etc. Thus, a much more flexible approach is provided that allows the user device to configure or select, e.g., for each uplink transmission of control information, which specific fields or types of data will be included in the user-configured uplink control information.
[0049] The user-configured control information may include any type of information, such as PHY layer control information, or any upper layer (at a network layer above PHY layer) control information, or other information. For example, the user device-configurable control information may include media access control (MAC) layer control information, or control information at or for another upper layer network entity, such as, for example, radio resource control (RRC) layer or entity, a packet data convergence protocol (PDCP), Radio Link Control (RLC) Entity, or other network layer or network entity. In 3GPP 5G (or New Radio ) the entities PDCP and RLC may be identified by different names (Network Control Sublayer NCS , Radio Control Sublayer RCS respectively) and may perform different functions than in LTE
[0050] At 216, the user device transmits, via the allocated uplink channel resources, the network-configured information (as indicated by message at 210) and the user device-configurable uplink control information (e.g., which may include PHY layer or MAC layer control information, in an illustrative example implementation, or other information).
[0051 ] FIG. 3 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to an example implementation. According to this illustrative example, an uplink channel resource allocation 310 is shown, e.g., for the transmission of uplink control information. This resource allocation 310 (e.g., including specifying a quantity of resources and/or specific time-frequency resources) may be signaled or indicated by BS 134 to user device 132 via 212 in FIG. 2, for example. According to an example implementation, the allocated uplink channel resources 310 may be allocated for an uplink control channel, such as for a physical uplink control channel (PUCCH), or for a physical uplink shared channel (PUSCH). In this illustrative example, the allocated uplink channel resources 310 are resources for the transmission of 22 bits, but any number of resources may be provided.
[0052] In the illustrative example shown in FIG. 3, the allocated uplink channel resources 310 may include resources for the transmission of network-configured information 312. Network-configured information may include, for example: physical (PHY) layer control information, such as ACK NAK feedback or information, PHY layer channel state information (CSI), or other physical layer feedback or information (e.g. beam related feedback on physical layer such as BSI or BRI); media access control (MAC) layer control information, or other control information that may be configured by a network entity (e.g., by BS 134 or other network entity within core network 150 or other location) for transmission from user device 132. The specific fields or content of network-configured information 312 and/or number of bits or resources to be used by the user device to transmit the network-configured information 312 via the allocated uplink channel resources 310 may be signaled or indicated by BS 134 to user device 132, e.g., via message (e.g., a downlink control information (DO)) at 210, FIG. 2.
[0053] According to an example implementation, at least a portion of the allocated uplink channel resources 310 are provided for the user device to transmit user device-configurable control information. Therefore, in this example, the user device 132 may determine that 20 bits are provided as an uplink control channel (e.g., PUCCH) container 314 for the transmission of user device-configurable uplink control
information. By way of illustrative example, the user device 132 may determine that 20 bits are provided for the transmission of user-configured uplink control information by subtracting the number of bits (2 bits) required for the network-configured information 312 from the number of bits (22 bits) provided by the allocated uplink channel resource allocation 310.
[0054] According to an illustrative example, as shown in FIG. 3, the container 314, which includes the user device-configurable control information, may include, for one or more fields or control information elements: 1) a control element identifier (CE ID) 315 to identify a type of control information element or field that is provided or follows the CE ID 315, and 2) a control element information or field (e.g., shown CE information 316). Thus, within the user-configured control information, there may be a CE ID that may include one or more bits or flags that may indicate a specific field or control element information is provided. In this example, 4 bits are provided for control element identifier (CE ID) 315, while 16 bits are provided for the control element information 316 or field (which is identified by the CE ID 315). According to an example implementation, the CE ID and control element information or field may be repeated within container 314 to identify (by CE ID 315) and then provide (by CE information 316) one or more additional fields or control element information within the user device-configurable uplink control information. A specific CE ID may map to a specific LCID of MAC CE and this mapping can be configured by network
(dynamically) or agreed in a specification (to be fixed). One benefit of mapping MAC LCIDs (which are used to identify MAC CEs and data channels) is to optimize the header overhead when transmitting uplink control information. Alternatively, the protocol complexity may be optimized by omitting the use of CE IDs and using the specified MAC CEs with full LCIDs with the cost of signaling overhead. Thus in this case in the example figures the CE ID is replaces by LCID (with appropriate lengths) Also, previously known control information format types (e.g., type la, lb, 2, .., see examples above for LTE) may be used or provided within user-configured information in place of CE IDs to identify format or content of fields within user-configured control information, if agreed between the user device 132 and BS 134. Also in one example network may configure UE with "known" LTE control information format such as Format 2/2a/2b (that include the CQI/CSI) but allow user to override the specific field - the CQI/CSI information with user configured control information.
[0055] According to an example implementation, a variety of different types of control information may be included within the user-configured control information (included within container 314), such as for example any physical (PHY) layer control information, any upper layer control information, such as MAC layer control information, radio resource control (RRC) control information, packet data control protocol (PDCP) control information, or control information with respect to other protocol layers or provided for or between protocol entities at any layer. By way of illustrative example, the user-device configured control information may include, e.g., a user device ID that identifies the user device, such as a Temporary mobile subscriber identifier (TMSI) or cell-radio network temporary identifier (C-RNTI) or other identifier, channel state information (CSI) feedback which may include CQI (channel quality indication), RI (rank indication) and/or PMI (precoding matrix index); a buffer status report (BSR) that may report the status or level of fullness of a data buffer at the user device, or may report the number of containers (e.g., PUCCH containers) needed for transmission; a beam measurement report such as beam state information (BSI) or a beam refinement information (BRI); ACK (or NAK) information related MAC level feedback, e.g., to acknowledge request from BS or network; a clear-to-send (CTS) indication, e.g., for unlicensed band operation; status reports from ARQ entities/processes; power headroom report (PHR); and/or any other information. These are merely some illustrative examples of information that may be included within the user-configured information (e.g., within container 314) in FIG. 3.
[0056] FIG. 4 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to another example implementation.
According to this illustrative example, an uplink channel resource allocation 410 is shown, e.g., for the transmission of uplink control information. In this illustrative example, the allocated uplink channel resources 410 are resources for the transmission of 32 bits, but any number of resources may be provided.
[0057] In the illustrative example shown in FIG. 4, the allocated uplink channel resources 410 may include resources for the transmission of network-configured information 412, while any remaining resources within uplink channel resources 410 may be used for the transmission of user device-configurable control information. In this illustrative example, the network-configured information 412 may include PHY layer control information (alternatively, the network-configured information may include MAC layer control information or information with respect to another protocol layer or protocol entity).
[0058] Also, as shown in the example of FIG. 4, all of the fields transmitted within the 32 bits of allocated uplink channel resources 410, other than 4 bits of network- configured information 412, may be user-configured control information, e.g., dynamically configured by the user device based on need or status of the user device 132. Several control element IDs may each indicate the presence of a specific or identified type of control element information or field within the user device-configurable control information. A control element identifier (CE ID) field 414 is set to buffer status report (CE ID = BSR) to indicate that a buffer status report (BSR) is provided via field 416. A control element identifier (CE ID) 418 is set to beam state information (CE ID = BSI) to indicate that field 420 includes beam state information (BSI). With this illustrative PUCCH allocation 410 of 32 bits, the remaining 4 bits would be unused in this example, so the end of the information may be indicated by a CE ID = end of data (EOD) or padding, which means that field 424 marks the end of the interpreted information for allocation 410. For example, at a receiving BS 134, no bits are interpreted after the CE ID 424. In one example the user configured information may be limited by network to include, e.g., a specific amount of Control Elements (CE) per container; in this case the EOD/padding need not to be indicated. Also, in case no user configurable information is configured by UE to be included, it may indicate the absence of data by using
EOD Padding CE ID.
[0059] FIG. 5 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to another example implementation.
According to this illustrative example, an uplink channel resource allocation 510 is shown, e.g., for the transmission of uplink control information. In this illustrative example, the allocated uplink channel resources 510 are resources for the transmission of N bits, including for the transmission of K-bits for network-configured information 512 (e.g., which may be physical layer information, MAC layer information, etc.). Thus, in the uplink channel resources 510 (providing N bits), there are therefore, N-K bits available for user device-configurable control information.
[0060] Therefore, FIG. 5 illustrates an example of a general structure of an uplink channel resource allocation (e.g., PUCCH resource allocation) of N-bits for the transmission of both: 1) network-configured information (K-bits), e.g., network- configured PHY information, and 2) dynamically generated user-configurable
information or content, e.g., MAC content in an illustrative example.
[0061 ] The network-configured information 512 (or format or content thereof) may depend on the various aspects as a configuration (by higher layer, e.g., RRC layer message from network entity) or explicit request by network or implicit indication (e.g., where the user device will need to send PHY layer feedback in the allocated resource, e.g., to ACK NAK received data). The network-configurable information includes K-bits where K=0,1,.. ,Ν bits. Thus, as noted, there are N-K bits available for the user device- configurable control information.
[0062] In an example implementation where the user device-configurable information includes MAC control information, a MAC entity at the user device 132 may select the contents (one or more MAC level fields) and transmit M - control element (or information elements). For each control element information (or field), there is a control element identifier (CE ID) that identifies the type of control element information that is included or follows the CE ID. The number of control element information items may depend on the amount of available resources, and the amount of control information to be transmitted. The CE ID field length is set to 4 bits in the example shown in FIG. 5 only as an example. The control element information item depends on the CE ID value (which indicates the type of control element information). The length and type of the control element information is known, or can be determined, based on the CE ID (these may be preconfigured or fixed in the specification).
[0063] In the example shown in FIG. 5, CE Di indicates an information type for CE IDi information; CE ID2 indicates an information type for CE ID2; CE IDM indicates an information type for CE IDM information, etc.
[0064] Also, according to an example implementation, an extension field may follow each CE ID to indicate whether or not another CE ID (and corresponding control element information or field) will follow. The extension (E) field (or bit) may be set to zero to indicate no further CE IDs are provided (hence E=0 in this example means that this is the last field in the channel resource allocation), and a extension (E) field is set to 1 to indicate a further CE ID is included within the uplink channel resource allocation. By way of illustrative example,
[0065] FIG. 6 illustrates an uplink channel resource allocation that provides an extension field according to an example implementation. According to this illustrative example, an uplink channel resource allocation 610 is shown, e.g., for the transmission of uplink control information. In this illustrative example, an extension field (E) 620 is set to 1 after CE IDi to indicate that further (or more) CE IDs are provided within the container or within the allocated uplink channel resources. CE ID2 follows CE IDi. In addition, extension field 622 is set to 0 to indicate that no more CE IDs are provided within the container or within the uplink channel resources 610. In this manner, the extension field may indicate whether further fields are provided within the container or allocated channel resources (e.g., extension field, E=l), or to indicate a last field (or a last CE ID) within the allocated channel resources (e.g., extension field, E=0).
[0066] FIG. 7 is a diagram illustrating information that may be transmitted via an uplink channel resource allocation according to another example implementation. The allocated uplink channel resources 710 may include resources for a network-configured information, and for the transmission of user device-configurable control information, e.g., within a control information container 720. In this illustrative example, with 22 bits for the allocated channel resources 710, and 2 bits for the network-configured
information, this leaves 20 bits for the user device-configurable control information. In this example, a control element identifier (CE ID) 722 is set to data (CE ID = data) to indicate that the control information container 720 (or the user device-configurable portion of the allocated channel resources 710) includes data (e.g., user data, transmitted from the user device).
[0067] Thus, for example, while the specific contents, format and fields within the container 720 (or of the user device-configurable control information) may be transparent or unknown to the physical layer (PHY) entity at the BS 134, the information received in the control information container (or user device-configurable control information) 720 may be passed up to a MAC entity (or other upper layer protocol entity) at the BS 134 for parsing, interpreting, processing and/or forwarding. Thus, for example, a MAC entity at the BS 134 may receive the CE ID 722, and detect that such CE ID indicates that data will be included in the container 720 (based on CE ID = data). The MAC entity at the BS 134 may then process or forward the received data.
[0068] According to an example implementation, the value of CE ID 720 (CE ID = data) may also map to or be associated with a logical channel identifier or logical channel ID (LCID) at a MAC entity at the BS 134, so that the received data may be processed or forwarded based on the LCID for the received data. Thus, for example, MAC protocol entities (or other entities) at the user device 132 and/or BS 134 may store and use a mapping between this CE ID value 722 and a LCID for the data, so that the received data can be forwarded by BS 134 in accordance with the corresponding LCID, for example. In this manner, it may be unnecessary to include a relatively long LCID value within the control information container 720. Rather, a shorter CE ID may be included within container 720. Using a shorter CE ID (which may be shorter than the LCID) may allow more bits for data, while the CE ID/LCID map at the BS 134 may allow the BS 134 to determine the LCID for the data (based on received CE ID 722 and the CE ID/LCID mapping) and then forward the data according to the associated LCID for this data.
[0069] In an example implementation, the network-configured information may be optional. Or, a size of the network-configured information may be indicated as a value between zero and some upper threshold number. Thus, in the case where 0 bits are indicated by BS 134 for the network-configured information, this means that the entire allocation of uplink channel resources can be used for the control information container or for the transmission of user device-configurable control information.
[0070] In one example implementation, the control information (e.g., PUCCH) container may have a fixed size of K -bits or octets, this allows pre-determined MAC CE formats to be defined. PUCCH container size may be configured by higher layers (e.g., MAC layer or higher).
[0071] In one example implementation, the network (e.g., BS 134) may dynamically indicate/schedule the number of PUCCH (or uplink control information) resource elements for the user device. A control information resource element (which may be or include the uplink channel resources allocated for uplink control information, including resources for network-controlled information and resources for a control information container for user device-configurable control information) is a smallest unit of allocation for the uplink control information, e.g., one resource element could have a size of 22bits. By allocating/aggregating more of these resource elements the number of available bits for uplink control information is increased. The amount of resources may based, e.g., on the configured transmission mode (single antenna, multi-antenna/ MIMO/ beamforming, carrier aggregation etc..) or the amount of resource are explicitly indicated. Explicit indication may allocate uplink control information resources (e.g in a DO) by pointing to a frequency index and the feedback timing and additionally the number of resource elements or amount of frequency resources. In some cases the uplink control timing with respect to the DL transmission be fixed. Based on predefined rules/provided scheduling decision etc., the user device may transmit user device-configurable control information via one or more of these control information resource elements, either separately, or use a combination or multiple resource elements. Thus, for example, a separate resource allocation may be received for each control information resource element, and then user device may separately transmit user device-configurable control information via each or one or more of the containers provided by the separate resource allocations (as defined in FIG.3). Or, one resource allocation may be received by the user device 132 which allocates channel resources to allow for network-configured
information plus multiple control information containers of N-bits to be transmitted together via the allocated channel resources. In one example Network-configured control information may be mapped to a single resource element while rest of the elements are provided as a single or separate containers to upper layer (e.g., MAC layer).
[0072] In one example implementation, the feedback resources may be preconfigured by RRC signaling (amount of uplink resource elements, the periodicity, implicit mapping based on DL-SCH (downlink scheduling) allocation) or alternatively the PUCCH may be scheduled by network. In one example implementation, the uplink control information may be embedded to part of uplink contention based transmission.
[0073] In one embodiment upon receiving a scheduling request (SR) sent by user device, the network may schedule a short uplink allocation (allocate uplink channel resources to user device) for fast transmission of uplink control information and potential small amount of uplink data.
[0074] In one example implementation, at a user device, a physical layer (PHY) entity may determine the available resources (available for user device-configurable information), and indicate this amount of available UL resources to a MAC layer or MAC entity at the user device 132, based on the configured feedback format (indicated by DCI): A specific PUCCH format may be determined which defines the amount of physical layer information and the container size to be included. Or, a generic PUSCH format does not allow any uplink physical layer control information to be transmitted but all resources are used by MAC entity for network-configured MAC layer information and user device-configurable information, which may multiplex both control and data into uplink transmission on the allocated resources.
[0075] In an example implementation, when transmitted with uplink data, the uplink control information (network configured information and user-configured information) can be included as a first part of transport block and it may have a different MCS (modulation and/or coding scheme) than the data. In one example the uplink control information may also have its own codeword (a channel coded transport block / a separate data stream) which is mapped to one or more transmission layers. In one further example with reference to FIG. 7, the network-configured information may be
transmitted using a first MCS, while the control information container (e.g., which may include data or other information) may be transmitted using a second MCS, that is different from the first MCS. These methods are applicable for scheduled transmission in a frame based system, contention based transmission in a frame based system or a contention based transmission in non-frame based system (such as WLAN on unlicensed band). Alternatively, the CE ID 722 may be transmitted with a different MCS as compared to the data within the container 720. Thus, data and control information may be transmitted using different MCS.
[0076] In one example implementation, the network-configured information may include physical layer information, such as HARQ related feedback, such as: ACK/NAK feedback; or ACK/NAK feedback for MIMO (multi-input, multi-output) / per carrier ACK/NAK feedback, and/or uplink sounding symbols for mobility/channel quality measurements.
[0077] In one example implementation, the user device may transmit a higher layer data PDU (protocol data unit) in the PUCCH container. To optimize the size of the PDU the data may be sent only from a specific logical channel (configured by network, thus no explicit LCID need to be present for receiver side mapping, or no CE ID/LCID map is necessary).
[0078] In one example implementation, the uplink control information is transmitted on PUCCH via allocated channel resources, where the network-configured information (e.g., which may include physical layer content) such as ACK/NAK feedback may be sent via N bits and a remainder of the PUCCH content (or remainder of allocated uplink channel resources) is provided for user device-configurable information (which may include MAC layer control information, for example).
[0079] Example illustration of uplink control information container in the context of PUCCH resource:
[0080] One or more of the example implementations may have one or more advantages, such as, for example:
[0081 ] More signaling flexibility for the system: user device (such as a MAC layer at user device) may dynamically decide what control information is to be included in the container. This may allow the user device to prioritize specific kinds of control information to be transmitted, rather than only transmitting what the network has configured for transmission (which may meet the needs of the user device, and may then cause the user device to obtain additional resources to transmit what it needs to transmit). Thus, the flexible uplink approach to allow a portion of the uplink channel resources to be used for user device-configurable control information to be transmitted may also provide a more efficient use of resources.
[0082] Provides a flexible way to prioritize transmission of the user device- configurable control information (e.g., MAC CEs/information elements) via the allocated PUCCH channel resources; the feedback format within container is not fixed, so that the user device may UE could prioritize e.g. beam state information over CSI feedback
[0083] Reduces also the amount of fixed information in network-configured information to be transmitted (e.g., in physical layer) which may reduce waster of resources; and, may provide forward compatibility of uplink control channel for further extensions.
[0084] A control information container can be included in PUSCH transmission and transmitted together with uplink data, to provide both control information and data. Also, for example, data may be transmitted within the control information container, either within PUSCH or within PUCCH.
[0085] FIG. 8 is a flow chart illustrating operation of a user device according to an example implementation. Operation 810 includes receiving, by a user device from a base station in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information. And, operation 820 includes transmitting, by the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
[0086] According to an example implementation of the method of FIG. 8, the method may further include determining, by the user device, a portion of the allocated uplink channel resources available to the user device for transmitting user-device configurable uplink control information; and configuring, by the user device, a format of the user device-configurable uplink control information.
[0087] According to an example implementation of the method of FIG. 8, the configuring, by the user device, a format of the user device-configurable uplink control information may include: selecting, by the user device, one or more fields of uplink control information to be transmitted within the user device-configurable control information and via the allocated channel resources.
[0088] According to an example implementation of the method of FIG. 8, the information identifying a type or format of network-configured information to be transmitted by the user device is received by the user device via a first message, and wherein the allocation of uplink channel resources for the transmission of uplink control information is received by the user device via a second message.
[0089] According to an example implementation of the method of FIG. 8, both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station in one message.
[0090] According to an example implementation of the method of FIG. 8, both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station via downlink control information (OCT) received in a message.
[0091 ] According to an example implementation of the method of FIG. 8, the information identifying a type or format of network-configured information to be transmitted by the user device includes: a downlink control information (DCI) that identifies that the user device should transmit to the base station at least one of the following types of uplink control information: acknowledgement/negative
acknowledgement (ACK/NAK) feedback for received data; and channel state information (CSI) feedback.
[0092] According to an example implementation of the method of FIG. 8, the receiving an allocation of uplink channel resources for the transmission of uplink control information includes at least one of: receiving an allocation of uplink channel resources in a physical uplink control channel (PUCCH) for the transmission of uplink control information; and receiving an allocation of uplink channel resources in a physical uplink shared channel (PUSCH) for the transmission of uplink control information.
[0093] According to an example implementation of the method of FIG. 8, the receiving may include: receiving an allocation of uplink control channel resources in a physical uplink control channel (PUCCH) and information that identifies network- configured physical layer control information to be transmitted via the allocated uplink channel resources.
[0094] According to an example implementation of the method of FIG. 8, the cletermining may include: determining, by the user device, a portion of the allocated uplink channel resources available to the user device for transmitting user-device configurable uplink control information, based on a difference between an amount of allocated uplink channel resources and an amount of resources required to transmit the network-configured information.
[0095] According to an example implementation of the method of FIG. 8, the transmitting may include: transmitting, by the user device via the allocated uplink channel resources, network-configured physical layer control information configured by a network entity and upper layer control information configured by the user device, wherein an amount of allocated uplink channel resources and the network-configured physical layer control information are configured or determined by a network entity, and the content or format of the upper layer control information is determined or configured by the user device.
[0096] According to an example implementation of the method of FIG. 8, the user-device configurable control information may include the following information for one or more control information elements: a control element identifier that identifies a type of control information element or type of field that is present in the user device- configurable control information; and a control information element or field.
[0097] According to an example implementation of the method of FIG. 8, the user device-configurable uplink control information may include upper layer control information for any network layer above a physical (PHY) layer.
[0098] According to an example implementation of the method of FIG. 8, the user device-configurable uplink control information comprises control information for a media access control (MAC) layer.
[0099] According to an example implementation of the method of FIG. 8, the network-configured information may include one or more network-determined fields of physical layer control information.
[00100] According to an example implementation of the method of FIG. 8, the network-configured information comprises one or more network-determined fields of media access control (MAC) layer control information.
[00101 ] According to an example implementation of the method of FIG. 8, the network-configured information may include physical layer acknowledgement/negative acknowledgement (ACK/NAK) information.
[00102] According to an example implementation of the method of FIG. 8, the user device-configurable uplink control information may include: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
[00103] According to an example implementation of the method of FIG. 8, and further including receiving, by the user device from the base station, information granting the user device permission to transmit data within the user device-configurable uplink control information; and wherein the user device-configurable uplink control information includes: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
[00104] According to an example implementation, an apparatus includes at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: receive, by a user device from a base station in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and transmit, by the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
[00105] According to an example implementation, a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: receiving, by a user device from a base station in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and transmitting, by the user device via the allocated uplink channel resources, the network- configured information and the user device-configurable uplink control information.
[00106] According to an example implementation, an apparatus includes means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving, by a user device from a base station in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and means for transmitting, by the user device via the allocated uplink channel resources, the network- configured information and the user device-configurable uplink control information.
[00107] According to an example implementation of the apparatus, the apparatus may further include means (e.g., 1002A/1002B and/or 1004, FIG. 10) for determining, by the user device, a portion of the allocated uplink channel resources available to the user device for transmitting user-device configurable uplink control information; and means (e.g., 1002A/1002B and/or 1004, FIG. 10) for configuring, by the user device, a format of the user device-configurable uplink control information.
[00108] According to an example implementation of the apparatus, the means for configuring, by the user device, a format of the user device-configurable uplink control information may include: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for selecting, by the user device, one or more fields of uplink control information to be transmitted within the user device-configurable control information and via the allocated channel resources.
[00109] According to an example implementation of the apparatus, the information identifying a type or format of network-configured information to be transmitted by the user device is received by the user device via a first message, and wherein the allocation of uplink channel resources for the transmission of uplink control information is received by the user device via a second message.
[00110] According to an example implementation of the apparatus, both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station in one message.
[00111] According to an example implementation of the apparatus, both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station via downlink control information (OCT) received in a message.
[00112] According to an example implementation of the apparatus, the information identifying a type or format of network-configured information to be transmitted by the user device includes: a downlink control information (OCT) that identifies that the user device should transmit to the base station at least one of the following types of uplink control information: acknowledgement/negative acknowledgement (ACK/NAK) feedback for received data; and channel state information (CSI) feedback.
[00113] According to an example implementation of the apparatus, the means for receiving an allocation of uplink channel resources for the transmission of uplink control information includes at least one of: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving an allocation of uplink channel resources in a physical uplink control channel (PUCCH) for the transmission of uplink control information; and means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving an allocation of uplink channel resources in a physical uplink shared channel (PUSCH) for the transmission of uplink control information.
[00114] According to an example implementation of the apparatus, the means for receiving may include: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving an allocation of uplink control channel resources in a physical uplink control channel (PUCCH) and information that identifies network-configured physical layer control information to be transmitted via the allocated uplink channel resources.
[00115] According to an example implementation of the apparatus, the means for cietermining may include: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for determining, by the user device, a portion of the allocated uplink channel resources available to the user device for transmitting user-device configurable uplink control information, based on a difference between an amount of allocated uplink channel resources and an amount of resources required to transmit the network-configured information.
[00116] According to an example implementation of the apparatus, the means for transmitting may include: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for transmitting, by the user device via the allocated uplink channel resources, network- configured physical layer control information configured by a network entity and upper layer control information configured by the user device, wherein an amount of allocated uplink channel resources and the network-configured physical layer control information are configured or determined by a network entity, and the content or format of the upper layer control information is determined or configured by the user device.
[00117] According to an example implementation of the apparatus, the user-device configurable control information may include the following information for one or more control information elements: a control element identifier that identifies a type of control information element or type of field that is present in the user device-configurable control information; and a control information element or field.
[00118] According to an example implementation of the apparatus, the user device-configurable uplink control information may include upper layer control information for any network layer above a physical (PHY) layer.
[00119] According to an example implementation of the apparatus, the user device-configurable uplink control information may include control information for a media access control (MAC) layer.
[00120] According to an example implementation of the apparatus, the network- configured information may include one or more network-determined fields of physical layer control information.
[00121 ] According to an example implementation of the apparatus, the network- configured information may include one or more network-determined fields of media access control (MAC) layer control information.
[00122] According to an example implementation of the apparatus, the network- configured information may include physical layer acknowledgement/negative acknowledgement (ACK/NAK) information.
[00123] According to an example implementation of the apparatus, the user device-configurable uplink control information may include: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
[00124] According to an example implementation of the apparatus, the apparatus further including means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving, by the user device from the base station, information granting the user device permission to transmit data within the user device-configurable uplink control information; and wherein the user device-configurable uplink control information includes: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
[00125] FIG. 9 is a flow chart illustrating operation of a base station according to an example implementation. Operation 910 includes transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information. Operation 920 includes receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
[00126] According to an example implementation of the method of FIG. 9, the information identifying a type or format of network-configured information to be transmitted by the user device is transmitted by the base station via a first message, and wherein the allocation of uplink channel resources for the transmission of uplink control information is transmitted by the base station via a second message.
[00127] According to an example implementation of the method of FIG. 9, both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are transmitted by the base station in one message.
[00128] According to an example implementation of the method of FIG. 9, the transmitting an allocation of uplink channel resources for the transmission of uplink control information includes at least one of: transmitting an allocation of uplink channel resources in a physical uplink control channel (PUCCH) for the transmission of uplink control information; and transmitting an allocation of uplink channel resources in a physical uplink shared channel (PUSCH) for the transmission of uplink control information.
[00129] According to an example implementation of the method of FIG. 9, both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station via downlink control information (OCT) received in a message.
[00130] According to an example implementation of the method of FIG. 9, the information identifying a type or format of network-configured information to be transmitted by the user device may include: a downlink control information (OCT) that identifies that the user device should transmit to the base station at least one of the following types of uplink control information: acknowledgement/negative
acknowledgement (ACK/NAK) feedback for received data; and channel state
information (CSI) feedback.
[00131 ] According to an example implementation of the method of FIG. 9, the receiving may include: receiving, by the base station via the allocated uplink channel resources, network-configured physical layer control information configured by a network entity and upper layer control information configured by the user device, wherein an amount of allocated uplink channel resources and the network-configured physical layer control information are configured or determined by a network entity, and the content or format of the upper layer control information is determined or configured by the user device.
[00132] According to an example implementation of the method of FIG. 9, the user device-configurable uplink control information may include: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data. [00133] According to an example implementation of the method of FIG. 9, the method may further include transmitting, by the base station to the user device, information granting the user device permission to transmit data within the user device- configurable uplink control information; and wherein the user device-configurable uplink control information includes: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
[00134] According to an example implementation, an apparatus includes at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to: transmit, by a base station to a user device in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and receive, by the base station from the user device via the allocated uplink channel resources, the network- configured information and the user device-configurable uplink control information.
[00135] According to an example implementation, a computer program product includes a computer-readable storage medium and storing executable code that, when executed by at least one data processing apparatus, is configured to cause the at least one data processing apparatus to perform a method including: transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
[00136] According to an example implementation, an apparatus includes means (e.g., 1002A/1002B and/or 1004, FIG. 10) for transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network- configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information, and means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
[00137] According to an example implementation of the apparatus, the information identifying a type or format of network-configured information to be transmitted by the user device is transmitted by the base station via a first message, and wherein the allocation of uplink channel resources for the transmission of uplink control information is transmitted by the base station via a second message.
[00138] According to an example implementation of the apparatus, both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are transmitted by the base station in one message.
[00139] According to an example implementation of the apparatus, the means for transmitting an allocation of uplink channel resources for the transmission of uplink control information includes at least one of: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for transmitting an allocation of uplink channel resources in a physical uplink control channel (PUCCH) for the transmission of uplink control information; and means (e.g., 1002A/1002B and/or 1004, FIG. 10) for transmitting an allocation of uplink channel resources in a physical uplink shared channel (PUSCH) for the transmission of uplink control information.
[00140] According to an example implementation of the apparatus, both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station via downlink control information (OCT) received in a message.
[00141 ] According to an example implementation of the apparatus, the information identifying a type or format of network-configured information to be transmitted by the user device may include: a downlink control information (DO) that identifies that the user device should transmit to the base station at least one of the following types of uplink control information: acknowledgement/negative acknowledgement (ACK/NAK) feedback for received data; and channel state information (CSI) feedback. [00142] According to an example implementation of the apparatus, the means for receiving may include: means (e.g., 1002A/1002B and/or 1004, FIG. 10) for receiving, by the base station via the allocated uplink channel resources, network-configured physical layer control information configured by a network entity and upper layer control information configured by the user device, wherein an amount of allocated uplink channel resources and the network-configured physical layer control information are configured or determined by a network entity, and the content or format of the upper layer control information is determined or configured by the user device.
[00143] According to an example implementation of the apparatus, the user device-configurable uplink control information may include: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
[00144] According to an example implementation of the apparatus, the apparatus may further include means (e.g., 1002A/1002B and/or 1004, FIG. 10) for transmitting, by the base station to the user device, information granting the user device permission to transmit data within the user device-configurable uplink control information; and wherein the user device-configurable uplink control information includes: a control element identifier indicating that data is provided within the user device-configurable uplink control information; and data.
[00145] FIG. 10 is a block diagram of a wireless station (e.g., AP or user device) 1000 according to an example implementation. The wireless station 1000 may include, for example, one or two RF (radio frequency) or wireless transceivers 1002A, 1002B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit/entity (controller) 1004 to execute instructions or software and control transmission and receptions of signals, and a memory 1006 to store data and/or instructions.
[00146] Processor 1004 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 1004, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 1002 (1002A or 1002B). Processor 1004 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 1002, for example). Processor 1004 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 1004 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these. Using other terminology, processor 1004 and transceiver 1002 together may be considered as a wireless transmitter/receiver system, for example.
[00147] In addition, referring to FIG. 10, a controller (or processor) 1008 may execute software and instructions, and may provide overall control for the station 1000, and may provide control for other systems not shown in FIG. 10, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 1000, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.
[00148] In addition, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 1004, or other controller or processor, performing one or more of the functions or tasks described above.
[00149] According to another example implementation, RF or wireless
transceivers) 1002A/1002B may receive signals or data and/or transmit or send signals or data. Processor 1004 (and possibly transceivers 1002A/1002B) may control the RF or wireless transceiver 1002A or 1002B to receive, send, broadcast or transmit signals or data.
[00150] The embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other
communication systems. Another example of a suitable communications system is the SG concept. It is assumed that network architecture in SG will be quite similar to that of the LTE-advanced. 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
[00151 ] It should be appreciated that future networks will most probably utilise network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent.
[00152] Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Implementations may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium. Implementations of the various techniques may also include implementations provided via transitory signals or media, and/or programs and/or software
implementations that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks. In addition, implementations may be provided via machine type communications (MTC), and also via an Internet of Things (IOT). [00153] The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers include a record medium, computer memory, readonly memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
[00154] Furthermore, implementations of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers,...) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber- physical systems. Therefore, various implementations of techniques described herein may be provided via one or more of these technologies.
[00155] A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
[00156] Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
[00157] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data.
Generally, a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non- volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.
[00158] To provide for interaction with a user, implementations may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
[00159] Implementations may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation, or any combination of such back-end, middleware, or front-end components. Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
[00160] While certain features of the described implementations have been illustrated as described herein, many modifications, substitutions, changes and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the various embodiments.

Claims

WHAT IS CLAIMED IS:
1. A method comprising:
receiving, by a user device from a base station in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information; and
transmitting, by the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
2. The method of claim 1 and further comprising:
determining, by the user device, a portion of the allocated uplink channel resources available to the user device for transmitting user-device configurable uplink control information; and
configuring, by the user device, a format of the user device-configurable uplink control information.
3. The method of claim 2 wherein the configuring, by the user device, a format of the user device-configurable uplink control information comprises:
selecting, by the user device, one or more fields of uplink control information to be transmitted within the user device-configurable control information and via the allocated channel resources.
4. The method of any previous claim wherein the information identifying a type or format of network-configured information to be transmitted by the user device is received by the user device via a first message, and wherein the allocation of uplink channel resources for the transmission of uplink control information is received by the user device via a second message.
5. The method of any previous claim wherein both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station in one message.
6. The method of any previous claim wherein both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station via downlink control information (DO) received in a message.
7. The method of any previous claim wherein the information identifying a type or format of network-configured information to be transmitted by the user device comprises:
a downlink control information (DO) that identifies that the user device should transmit to the base station at least one of the following types of uplink control information:
acknowledgement/negative acknowledgement (ACK/NAK) feedback for received data; and
channel state information (CSI) feedback.
8. The method of any previous claim wherein the receiving an allocation of uplink channel resources for the transmission of uplink control information comprises at least one of:
receiving an allocation of uplink channel resources in a physical uplink control channel (PUCCH) for the transmission of uplink control information; and
receiving an allocation of uplink channel resources in a physical uplink shared channel (PUSCH) for the transmission of uplink control information.
9. The method of any previous claim wherein the receiving comprises: receiving an allocation of uplink control channel resources in a physical uplink control channel (PUCCH) and information that identifies network-configured physical layer control information to be transmitted via the allocated uplink channel resources.
10. The method of any of claims 2-3 wherein the determining comprises:
determining, by the user device, a portion of the allocated uplink channel resources available to the user device for transmitting user-device configurable uplink control information, based on a difference between an amount of allocated uplink channel resources and an amount of resources required to transmit the network-configured information.
11. The method of any previous claim wherein the transmitting comprises:
transmitting, by the user device via the allocated uplink channel resources, network-configured physical layer control information configured by a network entity and upper layer control information configured by the user device, wherein an amount of allocated uplink channel resources and the network-configured physical layer control information are configured or determined by a network entity, and the content or format of the upper layer control information is determined or configured by the user device.
12. The method of any previous claim wherein the user-device configurable control information comprises the following information for one or more control information elements:
a control element identifier that identifies a type of control information element or type of field that is present in the user device-configurable control information; and
a control information element or field.
13. The method of any previous claim wherein the user device-configurable uplink control information comprises upper layer control information for any network layer above a physical (PHY) layer.
14. The method of any previous claim wherein the user device-configurable uplink control information comprises control information for a media access control (MAC) layer.
15. The method of any previous claim wherein the network-configured information comprises one or more network-determined fields of physical layer control information.
16. The method of any previous claim wherein the network-configured information comprises one or more network-determined fields of media access control (MAC) layer control information.
17. The method of any previous claim wherein the network-configured information comprises physical layer acknowledgement/negative
acknowledgement (ACK/NAK) information.
18. The method of any previous claim wherein the user device-configurable uplink control information comprises:
a control element identifier indicating that data is provided within the user device- configurable uplink control information; and
data.
19. The method of any previous claim, and further comprising:
receiving, by the user device from the base station, information granting the user device permission to transmit data within the user device-configurable uplink control information; and
wherein the user device-configurable uplink control information comprises:
a control element identifier indicating that data is provided within the user device- configurable uplink control information; and
data.
20. An apparatus comprising means for performing a method of any of claims 1- 19.
21. A computer program product for a computer, comprising software code portions for performing the steps of any of claims 1-19 when said product is run on the computer.
22. An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to:
receive, by a user device from a base station in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information; and
transmit, by the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
23. A method comprising:
transmitting, by a base station to a user device in a wireless network, information identifying a type or format of network-configured information to be transmitted by the user device, and an allocation of uplink channel resources for the transmission of uplink control information; and
receiving, by the base station from the user device via the allocated uplink channel resources, the network-configured information and the user device-configurable uplink control information.
24. The method of claim 23 wherein the information identifying a type or format of network-configured information to be transmitted by the user device is transmitted by the base station via a first message, and wherein the allocation of uplink channel resources for the transmission of uplink control information is transmitted by the base station via a second message.
25. The method of any of claims 23-24 wherein both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are transmitted by the base station in one message.
26. The method of any of claims 23-25 wherein the transmitting an allocation of uplink channel resources for the transmission of uplink control information comprises at least one of:
transmitting an allocation of uplink channel resources in a physical uplink control channel (PUCCH) for the transmission of uplink control information; and
transmitting an allocation of uplink channel resources in a physical uplink shared channel (PUSCH) for the transmission of uplink control information.
27. The method of any of claims 23-26 wherein both the information identifying a type or format of network-configured information to be transmitted by the user device and the allocation of uplink channel resources are received by the user device from the base station via downlink control information (DO) received in a message.
28. The method of any of claims 23-27 wherein the information identifying a type or format of network-configured information to be transmitted by the user device comprises:
a downlink control information (DO) that identifies that the user device should transmit to the base station at least one of the following types of uplink control information:
acknowledgement/negative acknowledgement (ACK/NAK) feedback for received data; and
channel state information (CSI) feedback.
29. The method of any of claims 23-28 wherein the receiving comprises:
receiving, by the base station via the allocated uplink channel resources, network- configured physical layer control information configured by a network entity and upper layer control information configured by the user device, wherein an amount of allocated uplink channel resources and the network-configured physical layer control information are configured or determined by a network entity, and the content or format of the upper layer control information is determined or configured by the user device.
30. The method of any of claims 23-29 wherein the user device-configurable uplink control information comprises:
a control element identifier indicating that data is provided within the user device- configurable uplink control information; and
data.
31. The method of any of claims 23-30, and further comprising:
transmitting, by the base station to the user device, information granting the user device permission to transmit data within the user device-configurable uplink control information; and
wherein the user device-configurable uplink control information comprises:
a control element identifier indicating that data is provided within the user device- configurable uplink control information; and
data.
32. An apparatus comprising means for performing a method of any of claims 23- 31.
33. A computer program product for a computer, comprising software code portions for performing the steps of any of claims 23-31 when said product is run on the computer.
34. An apparatus comprising at least one processor and at least one memory including computer instructions, when executed by the at least one processor, cause the apparatus to perform the method of claim 23.
PCT/EP2016/069792 2016-08-22 2016-08-22 Uplink resource allocation to transmit network-configured information and user device-configurable information for wireless networks WO2018036604A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2016/069792 WO2018036604A1 (en) 2016-08-22 2016-08-22 Uplink resource allocation to transmit network-configured information and user device-configurable information for wireless networks

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2016/069792 WO2018036604A1 (en) 2016-08-22 2016-08-22 Uplink resource allocation to transmit network-configured information and user device-configurable information for wireless networks

Publications (1)

Publication Number Publication Date
WO2018036604A1 true WO2018036604A1 (en) 2018-03-01

Family

ID=56740254

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2016/069792 WO2018036604A1 (en) 2016-08-22 2016-08-22 Uplink resource allocation to transmit network-configured information and user device-configurable information for wireless networks

Country Status (1)

Country Link
WO (1) WO2018036604A1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010148319A1 (en) * 2009-06-19 2010-12-23 Interdigital Patent Holdings, Inc. Signaling uplink control information in lte-a
EP2658331A1 (en) * 2010-12-22 2013-10-30 Fujitsu Limited Resource allocation method, channel state information transmission method, base station and user equipment

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010148319A1 (en) * 2009-06-19 2010-12-23 Interdigital Patent Holdings, Inc. Signaling uplink control information in lte-a
EP2658331A1 (en) * 2010-12-22 2013-10-30 Fujitsu Limited Resource allocation method, channel state information transmission method, base station and user equipment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NTT DOCOMO ET AL: "Remaining details for PUCCH format and PUCCH resource selection for HARQ-ACK feedback", vol. RAN WG1, no. Anaheim, USA; 20151115 - 20151122, 15 November 2015 (2015-11-15), XP051003452, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20151115] *

Similar Documents

Publication Publication Date Title
US11425697B2 (en) Dynamic management of uplink control signaling resources in wireless network
US11785602B2 (en) Channel state information feedback for flexible uplink control signaling
US11337186B2 (en) Method and apparatus for control information searching and data information transmission in a communication system
US10461912B2 (en) Dynamical search space alterations
US20180324786A1 (en) Resource determination for uplink control channel for wireless networks
US20210028823A1 (en) Method for measurement and report of channel state information for network cooperative communication
US10959225B2 (en) Techniques for handling semi-persistent scheduling collisions for wireless networks
US20190116006A1 (en) Low latency hybrid automatic repeat request (harq) feedback for wireless networks
CN111133708A (en) Enabling uplink transmissions during downlink subframes based on preemption of data transmissions in a wireless network
US20230179339A1 (en) Flexible semi-static harq-ack codebook overhead
CN111316718B (en) Carrier aggregation for sidelink communications
WO2020074069A1 (en) Enhanced scheduling request transmissions in wireless networks
CN110622552B (en) Apparatus and method for communication
WO2016116165A1 (en) Method, apparatus and system for the configuration of an uplink control channel
KR102627046B1 (en) Device and Method for Handling Physical Uplink Control Channel Collision
EP3777431B1 (en) Feedback indication for continued transmission for wireless networks
WO2018054478A1 (en) Flexible resource usage between scheduling-based and contention-based resource access for wireless networks
WO2018036604A1 (en) Uplink resource allocation to transmit network-configured information and user device-configurable information for wireless networks
US11974265B2 (en) Use of priority mismatch indication for uplink transmission for wireless networks
US20210329658A1 (en) Use of priority mismatch indication for uplink transmission for wireless networks
US11502892B2 (en) Modulation adjustment for 16-QAM in narrowband IoT
WO2023213411A1 (en) Enhanced uplink control information mapping to uplink channel allocations
JP2023160784A (en) Device and method for handling multi-cell scheduling
CN117716780A (en) Method and network node for communicating using downlink control information
CN116615886A (en) Multiplexing high priority and low priority uplink control information on a physical uplink shared channel

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16753938

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16753938

Country of ref document: EP

Kind code of ref document: A1