WO2017200562A1 - Conception de couche supérieure pour le traitement de paquets de plan de commande dans une communication vestimentaire de cinquième génération (5g) - Google Patents

Conception de couche supérieure pour le traitement de paquets de plan de commande dans une communication vestimentaire de cinquième génération (5g) Download PDF

Info

Publication number
WO2017200562A1
WO2017200562A1 PCT/US2016/053024 US2016053024W WO2017200562A1 WO 2017200562 A1 WO2017200562 A1 WO 2017200562A1 US 2016053024 W US2016053024 W US 2016053024W WO 2017200562 A1 WO2017200562 A1 WO 2017200562A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
buffer
retransmission
sdu
processors
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2016/053024
Other languages
English (en)
Inventor
Satish C. Jha
Yaser M. FOUAD
Qian Li
Guangjie Li
JoonBeom Kim
Vesh Raj SHARMA BANJADE
Xiaoyun May Wu
Geng Wu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
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 Intel Corp filed Critical Intel Corp
Priority to CN201680084788.6A priority Critical patent/CN109076568B/zh
Publication of WO2017200562A1 publication Critical patent/WO2017200562A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/321—Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • 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/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present disclosure relates to wireless technology, and more specifically to a higher layer design for communications between wearable user equipments (wUEs) and network UEs (nUEs).
  • wUEs wearable user equipments
  • nUEs network UEs
  • LTE Long Term Evolution
  • RRC radio resource control
  • IP Internet protocol
  • PDCP packet data convergence protocol
  • FIG. 1 is a block diagram illustrating an example user equipment (UE) useable in connection with various aspects described herein.
  • UE user equipment
  • FIG. 2 is an example diagram of a communication system that can facilitate fifth generation (5G) wearable (5G-Wearable or 5G-W) communications according to various aspects described herein.
  • 5G fifth generation
  • 5G-Wearable or 5G-W fifth generation
  • FIG. 3 is a diagram illustrating a protocol stack for a wUE (wearable UE)-nUE (network UE) interface, according to various aspects described herein.
  • FIG. 4 is a flow diagram illustrating an example of processing details control plane (CP) data may go through at a w-HL (wearable higher layer) layer according to various aspects described herein.
  • FIG. 5 is a block diagram illustrating a system that facilitates a higher layer for wearable communication (w-HL) at a UE, according to various aspects described herein.
  • FIG. 6 is a flow diagram illustrating a method that facilitates generation of a w- HL C-PDU (control plane protocol data unit) from one or more w-RRC (wearable radio resource control) CP packets, according to various aspects described herein.
  • w- HL C-PDU control plane protocol data unit
  • w-RRC wearable radio resource control
  • FIG. 7 is a flow diagram illustrating a method that facilitates generation and in-order delivery of one or more w-RRC CP packets from one or more received TBs (transport blocks), according to various aspects described herein.
  • FIG. 8A is a diagram illustrating an example of a padding subheader that can be added at the beginning of a w-HL C-PDU header when a left over grant has only one Byte to exactly match a w-HL C-PDU size to the grant size, according to various aspects described herein.
  • FIG. 8B is a diagram illustrating an example of a padding subheader that can be added at the beginning of a w-HL C-PDU header when a left over grant has only two Bytes to exactly match the w-HL C-PDU size to the grant size, according to various aspects described herein.
  • FIG. 8C is a diagram illustrating an example of a padding subheader that can be added at the end of a w-HL C-PDU header to enable insertion of 0 or more Bytes of padding data field at the end of a w-HL-PDU (data field) so that the w-HL C-PDU size can be matched exactly to the grant size, according to various aspects described herein.
  • FIG. 9A is a diagram illustrating an example of a C-PDU consisting of only a
  • CP SDU service data unit
  • UL uplink
  • FIG. 9B is a diagram illustrating an example of a C-PDU consisting of a BSR
  • buffer status report (buffer status report) and a CP SDU from UL CP Transmission buffer.
  • FIG. 10A is a diagram illustrating an example of a C-PDU consisting of a PHR
  • FIG. 10B is a diagram illustrating an example of a C-PDU consisting of a
  • FIG. 11 is a diagram illustrating an example of a C-PDU similar to that in FIG. 10B, with one byte of padding subheader at the beginning.
  • FIG. 12 is a diagram illustrating an example of a C-PDU similar to that in FIG. 10B, with two bytes of padding subheader at the beginning.
  • FIG. 13 is a diagram illustrating an example of a C-PDU similar to that in FIG. 10B, with bytes of padding subheader at the end.
  • FIG. 14 is a diagram illustrating an example a w-HL C-PDU having a BSR, a PHR, and a CP-SDU segment (that is not the last segment of this SDU) from a UL CP Tx (transmission) buffer.
  • FIG. 15 is a diagram illustrating an example of a w-HL C-PDU having a BSR, a PHR and a CP-SDU segment (that is the last segment of this SDU) from the UL CP TX buffer.
  • FIG. 16A is a diagram illustrating an example of a w-HL C-PDU having a BSR, a PHR and a UP-SDU (user plane SDU) from UL User plane Tx buffer.
  • FIG. 16B is a diagram illustrating an example of a w-HL C-PDU having a BSR, a PHR and a UP-SDU segment (not last segment of this SDU) from UL user plane TX buffer.
  • FIG. 17A is a diagram illustrating an example of a w-HL C-PDU having a BSR, a PHR and a UP-SDU segment (last segment of this SDU) from UL user plane TX buffer.
  • FIG. 17B is a diagram illustrating an example of an ARQ retransmission of a w-HL C-PDU having a BSR, a PHR and a C-PDU (not resegmented) from UL ARQ control plane retransmission buffer.
  • FIG. 18A is a diagram illustrating an example of an ARQ retransmission of a w-HL C-PDU having a BSR, a PHR and a C-PDU segment (not last segment of this resegmented C-PDU) from UL ARQ control plane retransmission buffer.
  • FIG. 18B is a diagram illustrating an example of an ARQ retransmission of a w-HL C-PDU segment having a BSR, a PHR and a C-PDU Segment (last segment of this resegmented C-PDU) from UL ARQ control plane retransmission buffer.
  • FIG. 19 is a diagram illustrating an example of a w-HL C-PDU having a BSR, a PHR, a CP-SDU from UL control plane TX buffer and an UP-SDU from UL user plane
  • FIG. 20 is a diagram illustrating an example of a w-HL CP PDU having a BSR, a PHR, a CP-SDU from UL control plane TX buffer and an UP-SDU segment (not last segment of the UP-SDU) from UL user plane TX buffer.
  • FIG. 21 is a diagram illustrating an example of a w-HL CP PDU having a BSR, a PHR, a CP-SDU segment (last segment of this SDU) from UL control plane TX buffer and an UP-SDU from UL user plane TX buffer.
  • FIG. 22 is a diagram illustrating an example of a w-HL CP PDU having a BSR, a PHR, a CP-SDU segment (last segment of this SDU) from UL control plane TX buffer, and a UP-SDU Segment (not last segment of this SDU) from UL user plane TX buffer.
  • FIG. 23 is a diagram illustrating an example of a w-HL C-PDU having a BSR, a PHR, a C-PDU (NOT resegmented) from UL control plane retransmission buffer and a UP-SDU from UL user plane TX buffer.
  • FIG. 24 is a diagram illustrating an example of a w-HL C-PDU having a BSR, a PHR, a C-PDU (NOT resegmented) from UL control plane retransmission buffer and a UP-SDU segment (not last segment) from UL user plane TX buffer.
  • FIG. 25 is a diagram illustrating an example of a w-HL C-PDU having a BSR, a PHR, a C-PDU (NOT resegmented) from UL control plane retransmission buffer, a CP SDU from UL control plane transmission buffer and a UP-SDU (not segmented) from UL user plane TX buffer.
  • FIG. 26 is a diagram illustrating an example of a w-HL C-PDU having a BSR, a PHR, a C-PDU Segment (Last Segment of this resegmented C-PDU) from UL control plane retransmission buffer and a CP-SDU from UL Control plane TX buffer.
  • FIG. 27 is a diagram illustrating an example of a w-HL C-PDU having a BSR, a PHR, a C-PDU Segment (Last Segment of this resegmented C-PDU) from UL control plane retransmission buffer and a CP-SDU Segment (Not last Segment) from UL Control plane TX buffer.
  • a component can be a processor (e.g., a microprocessor, a controller, or other processing device), a process running on a processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet PC and/or a user equipment (e.g., mobile phone, etc.) with a processing device.
  • a processor e.g., a microprocessor, a controller, or other processing device
  • a process running on a processor e.g., a microprocessor, a controller, or other processing device
  • an object running on a server and the server
  • a user equipment e.g., mobile phone, etc.
  • an application running on a server and the server can also be a component.
  • One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers.
  • a set of elements or a set of other components can be described herein, in which the term "set"
  • these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example.
  • the components can communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).
  • a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).
  • a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors.
  • the one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application.
  • a component can be an apparatus that provides specific functionality through electronic components without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components.
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • FIG. 1 illustrates, for one embodiment, example components of a User Equipment (UE) device 100.
  • the UE device 100 may include application circuitry 102, baseband circuitry 104, Radio Frequency (RF) circuitry 106, front-end module (FEM) circuitry 108 and one or more antennas 1 10, coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • the application circuitry 102 may include one or more application processors.
  • the application circuitry 102 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.
  • the baseband circuitry 104 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 104 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 106 and to generate baseband signals for a transmit signal path of the RF circuitry 106.
  • Baseband processing circuity 104 may interface with the application circuitry 102 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 106.
  • the baseband circuitry 104 may include a second generation (2G) baseband processor 104a, third generation (3G) baseband processor 104b, fourth generation (4G) baseband processor 104c, and/or other baseband processor(s) 104d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.).
  • the baseband circuitry 104 e.g., one or more of baseband processors 104a-d
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 104 may include Fast-Fourier Transform (FFT), precoding, and/or constellation
  • encoding/decoding circuitry of the baseband circuitry 104 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry 104 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements.
  • EUTRAN evolved universal terrestrial radio access network
  • a central processing unit (CPU) 104e of the baseband circuitry 104 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
  • the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 104f.
  • DSP audio digital signal processor
  • the audio DSP(s) 104f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 104 and the application circuitry 102 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 104 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 104 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 104 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 106 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 106 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 106 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 108 and provide baseband signals to the baseband circuitry 104.
  • RF circuitry 106 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1 04 and provide RF output signals to the FEM circuitry 108 for transmission.
  • the RF circuitry 106 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 106 may include mixer circuitry 1 06a, amplifier circuitry 106b and filter circuitry 106c.
  • the transmit signal path of the RF circuitry 106 may include filter circuitry 106c and mixer circuitry 106a.
  • RF circuitry 106 may also include synthesizer circuitry 106d for synthesizing a frequency for use by the mixer circuitry 106a of the receive signal path and the transmit signal path.
  • the mixer circuitry 106a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 108 based on the synthesized frequency provided by synthesizer circuitry 106d.
  • the amplifier circuitry 106b may be configured to amplify the down-converted signals and the filter circuitry 106c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals may be provided to the baseband circuitry 104 for further processing.
  • the output baseband signals may be zero- frequency baseband signals, although this is not a requirement.
  • mixer circuitry 1 06a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 106a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 106d to generate RF output signals for the FEM circuitry 108.
  • the baseband signals may be provided by the baseband circuitry 104 and may be filtered by filter circuitry 1 06c.
  • the filter circuitry 1 06c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively.
  • the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 1 06a of the receive signal path and the mixer circuitry 106a may be arranged for direct downconversion and/or direct upconversion, respectively.
  • the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 106 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 104 may include a digital baseband interface to communicate with the RF circuitry 106.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the
  • the synthesizer circuitry 106d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 106d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 106d may be configured to synthesize an output frequency for use by the mixer circuitry 106a of the RF circuitry 1 06 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 106d may be a fractional N/N+1 synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 104 or the applications processor 102 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1 02.
  • Synthesizer circuitry 1 06d of the RF circuitry 106 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip- flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 1 06d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 106 may include an IQ/polar converter.
  • FEM circuitry 108 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1 10, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 106 for further processing.
  • FEM circuitry 108 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 106 for transmission by one or more of the one or more antennas 1 1 0.
  • the FEM circuitry 108 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 106).
  • LNA low-noise amplifier
  • the transmit signal path of the FEM circuitry 108 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 106), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1 1 0.
  • PA power amplifier
  • the UE device 100 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.
  • additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.
  • device 100 is in the context of a UE device (e.g., a wearable UE (wUE) or a network UE (nUE)), in various aspects, a similar device can be employed in connection with a base station (BS) such as an Evolved NodeB (eNB), etc.
  • BS base station
  • eNB Evolved NodeB
  • techniques disclosed herein can employ a simplified higher layer design for communication between a wUE and a nUE, involving a single layer (referred to herein as wearable higher layer (w-HL)) between the w-RRC
  • FIG. 2 illustrated is an example diagram of a communication system 200 that can facilitate fifth generation (5G) wearable (5G-Wearable or 5G-W) communications according to various aspects described herein.
  • the communication system of FIG. 2 shows the following network nodes and interfaces: (1 ) a nUE (network UE) with a full infrastructure network (NW) access protocol stack (e.g., full C/U
  • control/user plane functions (2) three wUEs (wearable UEs), one with a direct NW connection and two accessing the NW (e.g., the E-UTRAN (Evolved Universal
  • nUE Terrestrial Radio Access Network
  • EPC Evolved Packet Core
  • a wUE can communicate with the E-UTRAN via the nUE.
  • Each nUE can have several wUEs associated with it which together form a PAN (such as the nUE and three wUEs shown in FIG. 2).
  • PAN such as the nUE and three wUEs shown in FIG. 2.
  • the E-UTRAN can assign a common resource pool for wearable communication. This resource pool can be shared among multiple PANs in a relatively small geographical area, and among potentially multiple wUEs within each PAN on a contention based resource access basis.
  • Each nUE can have two higher layer protocol stacks: one for the interface between wUE and nUE (the Xu-a air interface) and one for the interface between nUE and E-UTRAN (the Uu-p air interface).
  • the Higher Layer protocol stack for the interface nUE-EUTRAN can be the LTE Uu stack or can be an LTE evolved 5G protocol stack.
  • the higher layer protocol stack can refer mainly to the protocol layer(s) in between PHY and the Radio Resource Control layer for control plane traffic and between PHY and the IP/Application layers for user plane traffic.
  • higher layer refer to the MAC, RLC and PDCP layers in conventional LTE systems.
  • each packet transmission (e.g., PHY transport block (TB) size) can be shorter in wearable communication in order to reduce the impact of collision on system
  • the TB size can be a relatively small number of bytes, such as less than 75 bytes. In such a use case, reducing the size of packet header added at the higher layer can ensure that the data-to-packet-header ratio remains reasonable.
  • the higher layer protocol design and packet processing procedure design for higher layer discussed herein can minimize the higher layer protocol header overhead per packet transmission, which can increase throughput.
  • a single wearable higher layer can be employed for the control plane, which can provide some or all of the following features: (1 ) a simplified Higher layer protocol design; (2) functionalities of a Higher layer protocol customized for wearable communication; (3) a reduced number of protocol layer specific header fields (e.g., addition of multiple levels of packet ID (such as sequence number) is avoided); (4) a shorter size of various packet header fields; (5) packet segmentation and combination with lower packet header overhead; (6) multiplexing of buffer status report (BSR), power headroom report (PHR), control plane data and user plane data; and (7) retransmission of packets with lower packet header overhead.
  • BSR buffer status report
  • PHR power headroom report
  • all of the higher layer functionalities (such as conventional LTE MAC/RLC/PDCP functionalities) for control plane data processing can be merged into a single layer referred to herein as Wearable Higher Layer (w-HL), which can reduce packet header during transmission over the air- interface.
  • w-HL Wearable Higher Layer
  • the packet header reduction can provide significant advantages in terms of throughput, given that the fact that each PHY-SDU (PHY service data unit, e.g., PHY TB) on the control PRA (physical resource assignment) can be of very small size (e.g., 180-600 bits or 22.5-75 bytes) for the 5G-w, in contrast to conventional LTE.
  • a protocol stack for a wUE-nUE interface (e.g., the Xu-a interface discussed herein), according to various aspects described herein.
  • a CP/UP (control plane/user plane) data packet to be transmitted over the air-interface can be received as a w-HL service data unit (w-HL SDU) from the wearable-RRC (control plane data) layer or IP/host (user plane data) layer.
  • the w-RRC layer can handle the configuration of the w-HL.
  • the w-HL can store the CP data in a UL CP transmission buffer until PHY indicates a UL grant on a control PRA.
  • the w-HL can store the UP data in a UL UP transmission buffer.
  • CP w-HL PDU CP w-HL protocol data unit
  • the w-HL can then pass the w-HL CP PDU to PHY for transmission.
  • the CP data packet w-HL SDU can go through several operations discussed herein during its lifetime in the w-HL protocol layer.
  • FIG. 4 illustrated is an example flow diagram showing
  • FIG. 4 also shows generation of a PDU to be transmitted on a control PRA/resource (such a PDU is referred to herein as a control PDU or C-PDU).
  • Some of the functionalities of w-HL for control plane data include: (1 ) maintenance of w-HL SNs (sequence numbers); (2) optional (e.g., configured by w- RRC) integrity protection of control plane data flows; (3) optional (e.g., configured by w- RRC) ciphering and deciphering of control plane data; (4) in-sequence delivery of upper layer data; (5) duplicate detection and discarding of duplicate w-HL CP SDU(s); (6) w- HL CP SDU discard (e.g., timer based); (7) concatenation, segmentation and reassembly of SDUs; (8) multiplexing buffer status report, power headroom report, control plane data and/or user plane data; (9) re-segmentation of w-HL C-PDUs; and (10) protocol error detection and recovery by retransmission at two levels: (a) HARQ (hybrid ARQ (automatic repeat request)) first at the TB
  • a w-HL can be employed that was based on the following design choices for guiding CP data processing at w-HL.
  • control PRA an implicitly/explicitly known separate PRA/resource
  • control plane data is transmitted solely on the control PRA, and other PRAs can be employed for user plane data transmission.
  • a PRA Physical resource Assignment
  • PHR power headroom report
  • BSR buffer status report
  • w-HL PDU for control PRA.
  • a multiplexing and assembly operation for w-HL PDU for control PRA can be employed in various embodiments.
  • a system 500 that facilitates a higher layer for wearable communication (w-HL) at a UE (e.g., network UE (nUE) or wearable UE (wUE)), according to various aspects described herein.
  • a UE e.g., network UE (nUE) or wearable UE (wUE)
  • System 500 can include one or more processors 510 (e.g., one or more baseband processors such as one or more of the baseband processors discussed in connection with FIG. 1 ), transceiver circuitry 520 (e.g., comprising one or more of transmitter circuitry or receiver circuitry, which can employ common circuit elements, distinct circuit elements, or a combination thereof), and a memory 530 (which can comprise any of a variety of storage mediums and can store instructions and/or data associated with one or more of processor(s) 510 or transceiver circuitry 520).
  • system 500 can be included within a user equipment (UE), either in a wearable UE (wUE) or in a network UE (nUE).
  • UE user equipment
  • wUE wearable UE
  • nUE network UE
  • system 500 can provide higher layer functionality for control messaging between a network UE (nUE) and one or more wearable UEs (wUEs) within a personal area network (PAN).
  • PAN personal area network
  • Processor(s) 510 can implement a wearable higher layer (w-HL) that can perform higher layer functionalities associated with control messaging exchanged between a wUE and a nUE.
  • w-HL wearable higher layer
  • such higher layer functionality e.g., functionality of layer(s) between the w-RRC (wearable radio resource control) layer and PHY (the physical layer)
  • processor(s) 510 can implement functions associated with a w-HL transmission (Tx) entity and/or functions associated with a w-HL reception (Rx) entity.
  • processor(s) 510 can implement one or more functions associated with a w-HL Tx entity, such as any of the acts shown or described in connection with FIG. 4.
  • processor(s) 510 can receive one or more w-RRC (radio resource control) CP (control plane) packets as w-HL SDU (service data unit) packets.
  • processor(s) 510 can assign a distinct sequence number (SN) to the w-HL SDU(s).
  • processor(s) 510 can apply integrity protection and/or encryption (ciphering) to the w-HL SDU(s).
  • Processor(s) 510 can add the w-HL SDU(s) (e.g., w- RRC CP packets) to a CP transmission buffer (e.g., an uplink (UL) CP Tx buffer at a wUE, a downlink (DL) CP Tx buffer at a nUE).
  • a CP transmission buffer e.g., an uplink (UL) CP Tx buffer at a wUE, a downlink (DL) CP Tx buffer at a nUE.
  • Processor(s) 510 can determine a physical resource assignment (PRA) and corresponding allocation size for transmission of a w-HL PDU (protocol data unit) via PHY (the physical layer) by transceiver circuitry 520.
  • PRA physical resource assignment
  • the PRA can be indicated via an UL grant (e.g., from the nUE).
  • processor(s) 510 can generate a w-HL PDU, which can comprise one or more of a buffer status report (BSR) (e.g., when processor(s) 510 determine to include the BSR), a power headroom report (PHR) (e.g., when processor(s) 510 determine to include the PHR), one or more w-HL SDUs or segments thereof from the CP Tx buffer (e.g., wherein processor(s) 51 0 can perform segmentation as appropriate based on the allocated size), one or more w-HL PDUs or segments thereof from a CP retransmission buffer (e.g., wherein processor(s) 510 can perform re-segmentation as appropriate based on the allocated size), and/or user plane (UP) data from a UP Tx buffer and/or a UP retransmission buffer.
  • BSR buffer status report
  • PHR power headroom report
  • UP user plane
  • Each of the BSR, PHR, CP retransmission buffer, CP Tx buffer, UP retransmission buffer, and UP Tx buffer can have an associated priority, which in some aspects can be prioritized in that order (BSR, PHR, CP retransmission buffer, CP Tx buffer, etc.).
  • Processor(s) 51 0 can include the BSR and/or PHR based on a determination by processor(s) 510 to include the BSR/PHR (e.g., receiving a trigger/request to provide BSR/PHR, based on current BSR/PHR status, etc.).
  • processor(s) 510 can perform such multiplexing based on the associated priorities.
  • processor(s) 510 can add padding to the w-HL C-PDU to match the size of the w-HL C-PDU to the allocation size.
  • Processor(s) 510 can add a w-HL packet header to the w-HL C-PDU generated as described herein, which, depending on the data content of the w-HL C- PDU, can comprise one or more sub-headers indicating the contents of the w-HL C- PDU.
  • Processor(s) 510 can pass the w-HL C-PDU with header to PHY for transmission by transceiver circuitry 520 via the PRA.
  • Processor(s) 510 can employ a two-level retransmission mechanism in connection with the w-HL C-PDU(s).
  • Processor(s) 510 can employ a HARQ (Hybrid Automatic Repeat reQuest) mechanism at the physical layer TB level, which can involve processor(s) 510 processing HARQ ACK feedback (e.g., ACK (acknowledgement) or NACK (negative acknowledgement)) received via transceiver circuitry 520 in response to TBs used to communicate the w-HL C-PDU via PHY. In response to NACK(s), processor(s) 510 can retransmit the TB(s) one or more times unless a HARQ retransmission limit has been reached.
  • HARQ Hybrid Automatic Repeat reQuest
  • Processor(s) 510 can also employ an ARQ (Automatic Repeat reQuest) mechanism at the w-HL C-PDU level, which can involve processor(s) 510 processing ARQ ACK feedback (e.g., ACK (acknowledgement) or NACK (negative
  • processor(s) 510 can pass the w-HL C-PDU to PHY for retransmission one or more times (e.g., which can involve re-segmentation, etc.) unless an ARQ retransmission limit has been reached.
  • processor(s) 510 can re-determine a PRA and allocated size for the w-HL C-PDU (e.g., based on a new UL grant, etc.).
  • processor(s) 510 can involve processor(s) 510 multiplexing the CP data of the w-HL C-PDU with other data (e.g., BSR, PHR, other CP data or segments thereof, UP data, etc.) and/or processor(s) 510 re-segmenting the w-HL C- PDU.
  • other data e.g., BSR, PHR, other CP data or segments thereof, UP data, etc.
  • processor(s) 510 can implement one or more functions associated with a w-HL Rx entity (e.g., at a nUE or a wUE).
  • processor(s) 51 0 can generate HARQ ACK feedback (e.g., ACK/NACK, etc.) that can be transmitted by transceiver circuitry 520 in response to TB(s) successfully or unsuccessfully received by transceiver circuitry 520 in connection with one or more w-HL C-PDUs.
  • Processor(s) 51 0 can generate the w-HL C-PDU(s) based on the TB(s) received by transceiver circuitry 520.
  • Processor(s) 510 can also generate ARQ ACK feedback (e.g.,
  • transceiver circuitry 520 can be transmitted by transceiver circuitry 520 in response to w- HL C-PDU(s) successfully or unsuccessfully reconstructed by processor(s) 510.
  • processor(s) 510 can generate (and transceiver circuitry 520 can transmit) UL grant(s) that indicate PRA(s) and allocated size(s) that the w-HL C-PDU(s) are received via.
  • Processor(s) 510 can provide the generated w-HL C-PDU(s) from PHY to w- HL for higher layer processing by processor(s) 510.
  • individual w- HL C-PDU(s) can comprise one or more of a BSR, a PHR, one or more CP packets and/or segments thereof, or one or more UP packets and/or segments thereof.
  • the header(s) of the w- HL C-PDU(s) can comprise two or more subheaders, which can indicate information associated with the two or more data.
  • processor(s) 510 can generate one or more w-HL C-SDUs (e.g., w-RRC CP packet(s)). From the header(s) of the w-HL C-PDU(s) and SN(s) indicated therein, processor(s) 510 can determine an ordering of the C-SDU(s) (RRC CP packet(s)) and deliver the C-SDU(s) (w-RRC CP packet(s)) in order to a w- RRC layer.
  • w-HL C-SDUs e.g., w-RRC CP packet(s)
  • method 600 that facilitates generation of a w-HL C-PDU from one or more w-RRC CP packets, according to various aspects described herein.
  • method 600 can be performed at a UE.
  • a machine readable medium can store instructions associated with method 600 that, when executed, can cause a UE (e.g., nUE or wUE) to perform the acts of method 600.
  • one or more w-HL C-SDUs can be received from a w-RRC layer.
  • a unique SN can be assigned to each of the one or more w-HL C- SDUs.
  • the one or more w-HL C-SDUs can be stored in a UL CP Tx buffer.
  • one or more PRAs and allocated sizes can be determined for transmission of the one or more w-HL C-PDUs.
  • one or more w-HL C-PDUs can be generated based at least in part on the PRA and allocated size.
  • the w-HL C-PDU(s) can comprise one or more of BSR, PHR, UL CP Tx buffer, UL CP retransmission buffer, UL UP Tx buffer, or UL UP retransmission buffer.
  • the w-HL C-PDU can be passed to PHY.
  • the w-HL C-PDU can be transmitted via one or more TBs.
  • method 600 can include one or more other acts performed by a w-HL Tx entity described above in connection with system 500.
  • method 700 that facilitates generation and in-order delivery of one or more w-RRC CP packets from one or more received TBs, according to various aspects described herein.
  • method 700 can be performed at a UE.
  • a machine readable medium can store instructions associated with method 700 that, when executed, can cause a UE
  • one or more TBs can be received carrying w-RRC CP packet data.
  • one or more w-HL C-PDUs can be generated from the one or more TBs.
  • the one or more w-HL C-PDUs can be passed to a w-HL for further processing.
  • one or more w-HL C-SDUs (e.g., w-RRC CP packet(s)) can be generated from the one or more w-HL C-PDUs.
  • w-HL C-SDUs e.g., w-RRC CP packet(s)
  • an ordering of the one or more w-HL C-SDUs can be determined.
  • the one or more w-HL C-SDUs can be delivered in order to the w- RRC layer.
  • method 700 can include one or more other acts performed by a w-HL Rx entity described above in connection with system 500.
  • w-HL When w-HL receives a packet from a higher layer (w-RRC), the packet becomes a CP w-HL SDU (service data unit) for w-HL protocol layer.
  • w-RRC higher layer
  • a sequence number (SN) can be added per w-HL CP SDU (to save header overhead, a SN per w-HL C-PDU can be omitted). Encryption (ciphering/deciphering) and/or Integrity protection can be done per CP SDU, and a SDU SN can be used for these operations, thus a sequence number (SN) can be added per w-HL SDU.
  • CP SDUs can be stored in a separate buffer than the UP SDUs. Therefore, the sequence number assignment can be independent for CP and UP. That is, a SN does not need to be unique among CP and UP SDUs. However, a CP SDU SN can be unique among SNs assigned to CP SDUs to avoid errors. Additionally, the SN for a CP SDU does not need to be of the same length as that for a UP SDU.
  • w-HL can perform an Integrity protection operation on CP SDU. Otherwise, the w-HL CP SDU can skip the Integrity protection operation.
  • the Integrity protection operation increases the size of the w-HL SDU by adding some integrity check bytes.
  • the w-HL CP SDU can go through a ciphering operation which adds security to the air-interface transmission. Ciphering does not change the size of the w-HL CP SDU.
  • the w-HL CP SDU (possibly modified CP SDU if Integrity protection and/or Encryption operations were performed) can be placed in UL CP Transmission buffer along with its assigned SN. Note that the w-HL header can be added when the w-HL C- PDU is generated upon request from PHY layer. PHY can ask for the w-HL PDU if there is an UL grant received on control PRA, in aspects employed at a wUE. [00108] Buffering of the w-HL SDU in the UL CP transmission buffer can trigger sending a scheduling request to the nUE in order to request an UL grant on control PRA, in aspects employed at a wUE.
  • PHY can pass the UL grant to w-HL, asking to provide a w-HL C-PDU for transmission on control PRA.
  • a w-HL C-PDU can then be generated with size made equal to the PHY transport block (TB) size (e.g., size of a received UL grant).
  • TB PHY transport block
  • w-HL can generate a w-HL C-PDU, which can involve multiplexing BSR, PHR, w-HL CP SDUs buffered in UL CP Tx buffer (and/or UL CP ARQ retransmission buffer), and w-HL UP SDUs buffered in UL UP Tx buffer (and/or UL UP ARQ
  • w-HL can do one or more of the following: segment an SDU from UL CP/UP Tx buffer; re-segment a w-HL CP/UP PDU from UL CP/UP ARQ retransmission buffer; combine one or more SDU segments; combine 1 or more SDUs; and/or combine 0 or 1 BSR, 0 or 1 PHR, 0 or more re- segments, 0 or more CP/UP segments and 0 or more CP/UP SDUs.
  • the w-HL can then add a packet header to create a w-HL C-PDU for the control PRA.
  • the w-HL PDU for the control PRA can also be referred to as a w-HL C-PDU or a w-HL CP PDU. Examples of packet header additions and their details are discussed in greater detail below.
  • w-HL can store a copy of the w-HL C-PDU in the UL CP ARQ retransmission buffer.
  • w-HL can pass the w-HL C-PDU to PHY for transmission on control PRA.
  • PHY can transmit the w-HL C-PDU one or more times, until either (a) the w- HL C-PDU is received successfully at the nUE/wUE or (b) a maximum HARQ retransmissions limit is reached.
  • w-HL can invoke an ARQ retransmission procedure.
  • the original w-HL C-PDU can be re-segmented if the grant size is smaller, or it can be combined with other segment(s)/SDU(s) if the grant size is larger.
  • PHY For each ARQ retransmission, PHY can try up to the maximum number of HARQ retransmission times to deliver the C-PDU.
  • w-HL can discard the associated SDU(s) and can inform a higher layer (protocol layer above w-HL, e.g., w-RRC) about it.
  • w-RRC protocol layer above w-HL
  • Packet header design features at w-HL for control plane :
  • a sequence number (SN) of 10 bits can be assigned per w-HL SDU for the UP data such as IP data.
  • a 10 bit SN can accommodate 1024 UP SDUs in the UL UP Tx buffer.
  • CP SDUs are generated by w-RRC. It is highly unlikely that there will be more than 128 w-RRC messages or control plane messages (i.e., w-HL CP SDUs) pending for transmission in the UL CP Tx buffer at any time.
  • a control plane sequence number (C-SN) of 7 bits can be assigned to a CP SDU.
  • addition of a SN per w-HL C-PDU can be omitted, in order to reduce packet header overhead.
  • Encryption Integrity protection when performed
  • a control sequence number can be added per w-HL CP SDU.
  • retransmission is employed at the w-HL level (such as if w-HL ARQ is enabled), it can be done per w-HL C-PDU.
  • a tag (unique ID) as described herein can be employed to identify each C-PDUs so that w-HL Rx (Receive) entity can send the C-PDU Identification tag (unique ID) to the w-HL Tx (Transmit) entity while requesting a retransmission of missing C-PDU.
  • tags are provided which can be used to identify each C- PDU.
  • a SDU C-SN (or SN) or a SDU C-SN (or SN) plus a Segment ID can be used as tag/ID to uniquely identify any w-HL C-PDU as described below.
  • L1 /PHY transport block can be limited to a few tens of Bytes (less than 75 Bytes) due to the contention based transmission environment over Xu-a interface.
  • a smaller L1 TB size can be helpful in reducing the performance impact from potential collision.
  • Table 1 below shows an example L1 /PHY TB size range.
  • the maximum C-PDU (or UP PDU) size is approximately 600 bits (75 Bytes) and the minimum is 176 bits (22 Bytes).
  • Table 1 An example showing TB Size range for 5G-W.
  • Number of bits to represent Segment of a SDU The number of bits to represent a segment of a CP SDU depends on the maximum size of SDU that can be received at the w-HL.
  • the max supported PDCP SDU size in conventional LTE (Bytes) 8188 Bytes.
  • most of the control message packet size is much smaller than 81 88 Bytes in wearable communication.
  • the control plane message size will be ⁇ 1500 Bytes. Based on these possible two maximum SDU sizes, a segment ID can be designed. For user plane data sizes, both options of maximum packet sizes, 81 88 Bytes and 1 500 Bytes, can be assumed.
  • Re-transmission data can have a higher priority than new transmission.
  • Re-segmented data can be the first data segment/field if an UL grant is available in a TTI (transmission time interval) expecting HARQ/ARQ retransmission.
  • PRAs can be implicitly/explicitly designated as control PRA.
  • control data can be transmitted only on these PRAs.
  • PHR and BSR can be piggybacked in the wHL-PDU on this control PRA if PHR/BSR transmission is triggered and/or should be transmitted based on values.
  • user plane data can be included in the wHL-PDU for control PRA if there are resources left after finishing CP data.
  • a 1 bit flag (e.g., PDU Type) can identify wHL PDU for control PRA or that for UP PRAs.
  • Multiplexing of BSR, PHR, CP data and UP data in C-PDU Since BSR, PHR, CP data and/or UP data can be multiplexed for C-PDU, a field (e.g., Field-Type) can be included in the header to handle multiplexing.
  • a field e.g., Field-Type
  • the grant may be of a smaller size, and in that case a C-PDU (original C- PDU) in the retransmission buffer can be re-segmented.
  • a C-PDU original C- PDU
  • an ID can be assigned to each of its re-segments to help the w-HL RX entity to recreate the original C-PDU and also to request retransmission of lost resegment(s). If some re-segment of the original C-PDU is lost, only the missed resegments can be re-sent.
  • second level resegmentation there can be multiple levels of
  • retransmission packet header can be added in such a way that each segment (of resegmentation) can be identified uniquely and can be recreated from the original w-HL C-PDU if a segment (of resegmentation) is to be retransmitted.
  • a w-HL C-PDU (as well as UP PDU) is of maximum size up to 75 Bytes.
  • stating the start offset in Byte for a resegment is efficient as it needs only 7 bits. Therefore, a segment (of re-segmentation) can be identified via an ID to identify the original C-PDU and a start offset in bytes within the original C-PDU, as described below.
  • a flag indicating whether this is a last segment or not can also be included.
  • C-Rseg-SO (7 bits):
  • a Resegmentation Start Offset can specify a start byte of the original C-PDU (Original Header (e.g., excluding padding at the beginning, BSR and PHR subheaders) + Original Data fields) for this resegment, which can be the starting Byte number in the original C-PDU carried in this Re-segment while performing resegmentation during ARQ re-transmission of a C-PDU.
  • the whole C-PDU can be considered, excluding padding at beginning, BSR and PHR subheaders (e.g., original Header excluding padding at beginning, BSR and PHR subheaders + original data fields) as a data to specify the start offset of a resegment.
  • BSR and PHR subheaders e.g., original Header excluding padding at beginning, BSR and PHR subheaders + original data fields
  • C-RSeg-SN (10 Bits): During re-transmission each original C-PDU can be identified so that the C-PDU identification tag (PDU ID) can be used in its resegmentation.
  • the C-PDU identification tag (PDU ID) is discussed in various cases below.
  • C-PDU identification (PDU ID) can be based on a SDU C- SN (or UP SDU SN) (7 or 1 0 bits) only, or on a SDU C-SN (or UP SDU SN) with Segment number (14 or 19 bits) from the original C-PDU.
  • a Reseg C-PDU tag id can be defined called control plane Resegment Sequence Number (C-Rseg-SN) (e.g., of 3 bits) to be transmitted in the header during ARQ retransmission of C-PDU if resegmentation is employed.
  • C-Rseg-SN control plane Resegment Sequence Number
  • the w-HL Tx entity can maintain a table with a mapping of C-Rseg-SN to the original C-PDU identification Tag (PDU ID) at least temporarily, so that the w-HL Tx entity can create the remaining resegments for future grants. Note that the w-HL Tx does not need to exchange this mapping Table information to the w-HL Rx side.
  • the Rx side can extract the original packet, thus the mapping table information is not necessary.
  • the original packet can have the original header (excluding padding at beginning, BSR and PHR subheaders) and original data fields.
  • the Rx side can get the SN or SN plus Seg-N from the original header.
  • a 1 bit C-RSeg-SN can be employed for control PRA ARQ retransmission as there is only one TB per TTI per wUE and retransmission has higher priority.
  • a C-RSeg-SN of 3 bits can be defined so that the w-HL Receive entity can avoid sending ARQ ACK per C-PDU.
  • the w-HL Receive entity can thus have the flexibility to receive 8 C-PDUs (due to the 3 bits C-RSeg-SN) and can send a cumulative ACK to reduce ARQ ACK overhead.
  • the w-HL transmit entity can send at most 8 C-PDUs without getting ARQ ACK.
  • a C-PDU-SN (a SN for each PDU) can be employed.
  • C-RSeg-SN only for retransmission, 3 bits can be saved in the first transmission per C-PDU.
  • C-PDU ID C-PDU identification tag
  • Control Plane packet Header design for w-HL data processing
  • the following fields can be included in a packet header design of a w-HL C-PDU, which can efficiently allow segmentation and concatenation of SDUs, SDU-segment and/or wHL C-PDU-Resegment.
  • User plane data transmission related packet headers can differ from those discussed below. Table 2, below, provides a summary of several packet header fields that can be included in various aspects:
  • Seg-N 0 to 51 1 (9 Segment Number of a UP SDU.
  • a segment of a UP w- bits) 0 to 127 HL SDU is uniquely identified by SN and Seg-N.
  • a segment (of resegmented wHL UP PDU) is uniquely identified by Rseg-SN and Rseg-SO
  • a segment (of resegmented wHL CP PDU) is uniquely identified by C-Rseg-SN and C-Rseg-SO
  • Pad Variable Padding Used to make a PDU header/subheader
  • Length Indicator whenever there is more than one SDUs/SDU-Segments/C- PDU-Resegments in a w-HL field, the corresponding subheader fields for all data fields except the last data field can have a length indicator field. There is one case (called Padding at the end) when the last data field can also have a length field as described below.
  • w-HL can make sure it provides L1 a w-HL C-PDU of exactly the same size as indicated by L1 .
  • the L1 transport block size i.e., grant size for w-HL C-PDU generation indicated by L1
  • padding can be used to match the size of w-HL to the grant size.
  • Padding In some situations, only a few bytes (e.g., 1 , 2, 3 or 4 Bytes, etc.) of grant can be left over after including 0 or more SDUs/SDU-Segments/C-PDU- Resegments while preparing a w-HL C-PDU.
  • the left over grant may not be sufficient to include a new subheader and a corresponding data field of at least one Byte.
  • relatively large padding hundredseveral Bytes say more than 4 Bytes
  • padding can be added as described in the following cases and the example octets shown in FIGS. 8A, 8B, and 8C.
  • FIG. 8A illustrated is an example of a padding subheader that can be added at the beginning of a w-HL C-PDU header when a left over grant has only one Byte to exactly match a w-HL C-PDU size to the grant size, according to various aspects described herein.
  • a padding sub header of 1 Byte can be added at the beginning as shown in the example of FIG. 8A.
  • the LI field can be omitted for the last SDU/SDU-Segment/C-PDU-Resegment subheader, as it is still the last data field.
  • the receiving side can simply ignore the padding subheader as if this byte does not exist when it finds a padding subheader at the beginning of C-PDU header during decoding.
  • FIG. 8B illustrated is an example of a padding subheader that can be added at the beginning of a w-HL C-PDU header when a left over grant has only two Bytes to exactly match the w-HL C-PDU size to the grant size, according to various aspects described herein.
  • only two Bytes of Grant are left over, and two one-Byte padding sub headers can be added to the two Bytes at the beginning, as seen in FIG. 8B.
  • the LI field can be omitted for the last SDU/SDU-Segment/C-PDU-Resegment subheader, as it is still the last data field.
  • the receiving side can simply ignore padding subheaders at the beginning of the C-PDU header during decoding as if these two bytes did not exist.
  • FIG. 8C illustrated is an example of a padding subheader that can be added at the end of a w-HL C-PDU header to enable insertion of 0 or more Bytes of padding data field at the end of a w-HL-PDU (data field) so that the w-HL C-PDU size can be matched exactly to the grant size, according to various aspects described herein.
  • three or more Bytes of Grant can be left over.
  • sufficient grant can exist to add the LI field in the last SDU/SDU- Segment/C-PDU-Resegment subheader (of the w-HL C-PDU as constructed before padding) and add a padding subheader at the end.
  • the padding subheader (as shown in FIG. 8C) at the end can indicate that after the last SDU/SDU-Segment/C-PDU- Resegment data field (for which there is a LI), the remaining grant can be filled with padding.
  • the padding data field in this case can comprise 0 or more bytes.
  • the receiving side w-HL Rx entity
  • An example set of priorities for creating a w-HL C-PDU can be as follows.
  • the BSR and PHR can have a highest priority, which can be followed by C-PDU in the CP retransmission buffer.
  • CP data in the CP Tx buffer can have a next highest priority.
  • CP data can have higher priority than the UP data while creating C-PDU to be transmitted on a control PRA.
  • UP data can be included in the C-PDU only when there is no more CP data to be transmitted.
  • the grant left after placing BSR and PHR (when included) can be used for ARQ retransmission of C-PDU in the CP retransmission buffer. If there is grant left over, the grant can then be filled with CP data. If there is still grant left over after putting in CP data, then UP data can be placed in the C-PDU.
  • the priority of various data in decreasing order, can be as follows: (1 ) the BSR field can have a first (Highest) priority to be included in C-PDU; (2) the PHR field can have a second priority; (3) the C-PDU in the ARQ retransmission buffer pending to be retransmitted can have a third priority; (4) CP data can have a fourth priority; and (5) UP data can have a fifth (least) priority.
  • BSR Buffer Status Report
  • PHR Power Headroom Report
  • BSR can provide an estimate of UL data in a wUE's buffers to the nUE so that the nUE can assign a reasonable UL grant to the wUE.
  • buffer size represents the total data in buffers at wUE, such as in the user plane transmission buffer and the control plane transmission buffer.
  • PHR can be sent by a wUE to tell the nUE whether the wUE can transmit at a higher transmission power or not compared to the power being used by current transmission.
  • PHR can be positive or negative. Positive PHR indicates that the wUE is not transmitting at a maximum allowed transmission power and therefore it is still capable to transmit at a higher Tx power or it is still capable of transmitting at higher throughput. If PHR is negative, the wUE is already transmitting at maximum allowed Tx power.
  • PHR information can be used by nUE to determine whether to allocate more or less UL grant to wUE. For example, in case of a positive PHR, the nUE can allocate more PRA/resource to wUE.
  • PH Power headroom
  • Table 4 An example showing Power Headroom Levels and Power Headroom Report
  • the PDU-Type can be 1 here to indicate that the PDU is a C-PDU to be transmitted over control PRA.
  • the C-PDU in FIG. 9A can be uniquely identified by the C-SN field.
  • FIG. 9B illustrated is an example of a C-PDU consisting of a BSR and a CP SDU from UL CP Transmission buffer.
  • C-PDU ID C-PDU ID (C-PDU
  • the C-PDU in FIG. 9B can be uniquely identified by the C-SN field.
  • C-PDU consisting of a PHR and a CP SDU from UL CP Transmission buffer.
  • C-PDU in FIG. 10A can be uniquely identified by C-SN field.
  • FIG. 10B illustrated is an example of a C-PDU consisting of a BSR, a PHR and a CP SDU from UL CP Transmission buffer.
  • the w-HL Receive entity can know that 5 bits BSR-filed is followed by a 5 bits-PHR field.
  • the type of data field (a CP SDU - NOT segmented) can be identified by Content- Type field 001 1 .
  • C-PDU ID C-PDU Identification Tag) for Retransmission: the C-PDU in FIG. 10B can be uniquely identified by C-SN field.
  • C-PDU ID C-PDU Identification Tag
  • C-PDU ID C-PDU Identification Tag
  • the C- PDU in FIG. 12 can be uniquely identified by C-SN field.
  • C-PDU ID C- PDU Identification Tag
  • w-HL C-PDU Headers showing BSR, PHR and a CP SDU Segment from UL CP Transmission Examples of w-HL C-PDU Headers showing BSR, PHR and a CP SDU Segment from UL CP Transmission:
  • each segment can have a segment number (C-Seg-N) along with the SDU's SN.
  • C-Seg-N segment number
  • FIG. 14 illustrated is an example a w- HL C-PDU having a BSR, a PHR, and a CP-SDU segment (that is not the last segment of this SDU) from a UL CP Tx buffer.
  • C-PDU ID C-PDU Identification Tag
  • the C-PDU in FIG. 14 can be uniquely identified by C-SN and C-Seg-N field.
  • C-PDU ID C-PDU Identification Tag
  • the C-PDU in FIG. 15 can be uniquely identified by C-SN and C-Seg-N field.
  • CP data can have a higher priority than the UP data while creating a C-PDU to be transmitted.
  • UP data can be included in the C-PDU only when there is no more CP data to be transmitted.
  • the grant left after placing BSR and PHR can be used for ARQ retransmission of C-PDU in
  • retransmission buffer If there is grant left over, the grant can then be filled with CP data. If there is still grant left over after putting CP data, then UP data can be placed in the C- PDU.
  • C-PDU ID C-PDU ID
  • the C-PDU in FIG. 16A can be uniquely identified by SN field.
  • C-PDU ID C-PDU Identification Tag
  • the C-PDU in FIG. 16B can be uniquely identified by SN and Seg-N fields.
  • C-PDU ID C-PDU Identification Tag
  • the C-PDU in FIG. 17A can be uniquely identified by SN and Seg-N fields.
  • retransmission as the grant can be smaller than the w-HL C-PDU.
  • the w-HL C-PDU is not segmented during retransmission.
  • FIG. 17B illustrated is an example of an ARQ retransmission of a w-HL C-PDU having a BSR, a PHR and a C-PDU (not resegmented) from UL ARQ control plane retransmission buffer.
  • FIG. 18A illustrated is an example of an ARQ retransmission of a w-HL C-PDU having a BSR, a PHR and a C-PDU segment (not last segment of this resegmented C-PDU) from UL ARQ control plane retransmission buffer.
  • Re- segmentation of a w-HL C-PDU in retransmission buffer can be performed due to a smaller grant.
  • FIG. 18B illustrated is an example of an ARQ retransmission of a w-HL C-PDU segment having a BSR, a PHR and a C-PDU Segment (last segment of this resegmented C-PDU) from UL ARQ control plane retransmission buffer.
  • Re- segmentation of a wHL C-PDU in retransmission buffer can be performed due to a smaller grant.
  • this segment is the last segment, however, the grant is not sufficient to accommodate any other data field.
  • FIG. 19 illustrated is an example of a w-HL C-PDU having a BSR, a PHR, a CP-SDU from UL control plane TX buffer and an UP-SDU from UL user plane TX buffer.
  • FIG. 20 illustrated is an example of a w-HL CP PDU having a BSR, a PHR, a CP-SDU from UL control plane TX buffer and an UP-SDU segment (not last segment of the UP-SDU) from UL user plane TX buffer.
  • FIG. 21 illustrated is an example of a w-HL CP PDU having a BSR, a PHR, a CP-SDU segment (last segment of this SDU) from UL control plane TX buffer and an UP-SDU from UL user plane TX buffer.
  • w-HL CP PDU having a BSR, a PHR, a CP-SDU segment (last segment of this SDU) from UL control plane TX buffer, and a UP-SDU Segment (not last segment of this SDU) from UL user plane TX buffer.
  • w-HL C-PDU Headers showing BSR, PHR, C-PDU, C-PDU Segment, CP/UP SDU and/or CP/UP SDU Segment:
  • FIG. 23 illustrated is an example of a w-HL C-PDU having a BSR, a PHR, a C-PDU (NOT resegmented) from UL control plane retransmission buffer and a UP-SDU from UL user plane TX buffer.
  • a w-HL C-PDU having a BSR, a PHR, a C-PDU (NOT resegmented) from UL control plane retransmission buffer and a UP-SDU from UL user plane TX buffer.
  • FIG. 24 illustrated is an example of a w-HL C-PDU having a BSR, a PHR, a C-PDU (NOT resegmented) from UL control plane retransmission buffer and a UP-SDU segment (not last segment) from UL user plane TX buffer.
  • a w-HL C-PDU having a BSR, a PHR, a C-PDU (NOT resegmented) from UL control plane retransmission buffer and a UP-SDU segment (not last segment) from UL user plane TX buffer.
  • FIG. 25 illustrated is an example of a w-HL C-PDU having a BSR, a PHR, a C-PDU (NOT resegmented) from UL control plane retransmission buffer, a CP SDU from UL control plane transmission buffer and a UP-SDU (not segmented) from UL user plane TX buffer.
  • a w-HL C-PDU having a BSR, a PHR, a C-PDU (NOT resegmented) from UL control plane retransmission buffer, a CP SDU from UL control plane transmission buffer and a UP-SDU (not segmented) from UL user plane TX buffer.
  • FIG. 26 illustrated is an example of a w-HL C-PDU having a BSR, a PHR, a C-PDU Segment (Last Segment of this resegmented C-PDU) from UL control plane retransmission buffer and a CP-SDU from UL Control plane TX buffer.
  • a C-PDU Segment (Last Segment of this resegmented C-PDU) from UL control plane retransmission buffer
  • a CP-SDU from UL Control plane TX buffer.
  • FIG. 27 illustrated is an example of a w-HL C-PDU having a BSR, a PHR, a C-PDU Segment (Last Segment of this resegmented C-PDU) from UL control plane retransmission buffer and a CP-SDU Segment (Not last Segment) from UL Control plane TX buffer.
  • a C-PDU Segment (Last Segment of this resegmented C-PDU) from UL control plane retransmission buffer
  • CP-SDU Segment Not last Segment
  • Examples herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described.
  • a machine e.g., a processor with memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like
  • Example 1 is an apparatus configured to be employed within a User
  • UE comprising a memory; and one or more processors configured to: assign a distinct sequence number to each of one or more control plane (CP) packets from a wearable radio resource control (w-RRC) layer; buffer the one or more CP packets to a CP transmission buffer; determine a physical resource assignment (PRA) and an allocated size for a wearable higher layer (w-HL) control protocol data unit (C- PDU); generate the w-HL C-PDU based at least in part on the one or more CP packets buffered to the CP transmission buffer, the PRA, and the allocated size; add a packet header to the w-HL C-PDU; and provide the w-HL C-PDU to a physical layer based on the PRA.
  • CP control plane
  • w-RRC wearable radio resource control
  • Example 2 comprises the subject matter of any variation of any of example(s)
  • the one or more processors are further configured to generate the w-HL C- PDU based at least in part on one or more of a buffer status report (BSR), a power headroom report (PHR), a CP retransmission buffer, a user plane (UP) transmission buffer, or a UP retransmission buffer.
  • BSR buffer status report
  • PHR power headroom report
  • CP retransmission buffer CP retransmission buffer
  • UP user plane
  • UP UP retransmission buffer
  • Example 3 comprises the subject matter of any variation of any of example(s)
  • the one or more processors are further configured to determine distinct priorities for each of the CP transmission buffer, the CP retransmission buffer, the BSR, the PHR, the UP transmission buffer, and the UP retransmission buffer.
  • Example 4 comprises the subject matter of any variation of any of example(s)
  • the one or more processors are further configured to: generate the w-HL C- PDU based at least in part on multiplexing the CP transmission buffer and the one or more of the CP retransmission buffer, the BSR, the PHR, the UP transmission buffer, or the UP retransmission buffer, wherein the multiplexing is based at least in part on the distinct priorities determined for each of the CP transmission buffer, the CP
  • Example 5 comprises the subject matter of any variation of any of example(s) 2-4, wherein the one or more processors are further configured to: generate one or more segments via segmenting one or more CP packets buffered to the CP
  • Example 6 comprises the subject matter of any variation of any of example(s) 2-4, wherein the one or more processors are further configured to generate the w-HL C- PDU based at least in part on combining two or more of: one or more CP packets buffered to the CP transmission buffer, one or more prior w-HL C-PDUs buffered to the CP retransmission buffer, or one or more segments.
  • Example 7 comprises the subject matter of any variation of any of example(s) 2-4, wherein the one or more processors are configured to make a determination whether to indicate at least one of the BSR or the PHR via the w-HL C-PDU, and wherein the w-HL C-PDU comprises the at least one of the BSR or the PHR when the determination is positive.
  • Example 8 comprises the subject matter of any variation of any of example(s) 1 -4, wherein the packet header comprises two or more subheaders.
  • Example 9 comprises the subject matter of any variation of any of example(s) 1 -4, wherein the one or more processors are further configured to adjust a size of the w- HL C-PDU via padding to match the allocated size.
  • Example 10 comprises the subject matter of any variation of any of example(s) 1 -4, wherein the one or more processors are further configured to process at least one hybrid automatic repeat request (HARQ) ACK/NACK
  • HARQ hybrid automatic repeat request
  • the one or more processors are configured to employ a retransmission mechanism at a physical layer transport block (TB) level in response to the at least one HARQ ACK/NACK response comprising a HARQ NACK.
  • TB physical layer transport block
  • Example 1 1 comprises the subject matter of any variation of any of example(s) 1 -4, wherein the one or more processors are further configured to process at least one automatic repeat request (ARQ) ACK/NACK (acknowledgement/negative acknowledgement) response in connection with the w-HL C-PDU, wherein the one or more processors are further configured to employ a retransmission mechanism at a w- HL C-PDU level in response to the at least one ARQ ACK/NACK response comprising an ARQ NACK.
  • ARQ automatic repeat request
  • Example 12 comprises the subject matter of any variation of any of example(s) 1 1 , wherein, in response to the at least one ARQ ACK/NACK response comprising an ARQ NACK, the one or more processors are further configured to:
  • a new PRA and a new allocated size for the w-HL C-PDU determine a new PRA and a new allocated size for the w-HL C-PDU; and based on the new allocated size, at least one of re-segment the w-HL C-PDU, or combine the w-HL C-PDU with at least one of one or more CP packets buffered to the CP transmission buffer, one or more prior w-HL C-PDUs buffered to the CP retransmission buffer, or one or more segments.
  • Example 13 comprises the subject matter of any variation of any of example(s) 1 -4, wherein the UE is a wearable UE (w-UE), and wherein the one or more processors are configured to determine the PRA and the allocated size based on an uplink (UL) grant.
  • w-UE wearable UE
  • UL uplink
  • Example 14 comprises the subject matter of any variation of any of example(s) 1 -4, wherein the UE is a network UE (n-UE).
  • Example 15 comprises the subject matter of any variation of any of example(s) 2-4, wherein the one or more processors are further configured to: generate one or more segments via segmenting one or more CP packets buffered to the CP transmission buffer, segmenting one or more prior w-HL C-PDUs buffered to the CP retransmission buffer, or resegmenting one or more previously generated segments, wherein the w-HL C-PDU is generated based at least in part on the one or more segments.
  • Example 16 comprises the subject matter of any variation of any of example(s) 2-4 or 15, wherein the one or more processors are further configured to generate the w-HL C-PDU based at least in part on combining two or more of: one or more CP packets buffered to the CP transmission buffer, one or more prior w-HL C- PDUs buffered to the CP retransmission buffer, or one or more segments.
  • Example 17 comprises the subject matter of any variation of any of example(s) 2-4 or 15-16, wherein the one or more processors are configured to make a determination whether to indicate at least one of the BSR or the PHR via the w-HL C- PDU, and wherein the w-HL C-PDU comprises the at least one of the BSR or the PHR when the determination is positive.
  • Example 18 comprises the subject matter of any variation of any of example(s) 1 -4 or 15-16, wherein the packet header comprises two or more
  • Example 19 comprises the subject matter of any variation of any of example(s) 1 -4 or 15-18, wherein the one or more processors are further configured to adjust a size of the w-HL C-PDU via padding to match the allocated size.
  • Example 20 comprises the subject matter of any variation of any of example(s) 1 -4 or 15-19, wherein the one or more processors are further configured to process at least one hybrid automatic repeat request (HARQ) ACK/NACK
  • HARQ hybrid automatic repeat request
  • the one or more processors are configured to employ a retransmission mechanism at a physical layer transport block (TB) level in response to the at least one HARQ ACK/NACK response comprising a HARQ NACK.
  • TB physical layer transport block
  • Example 21 comprises the subject matter of any variation of any of example(s) 1 -4 or 15-20, wherein the one or more processors are further configured to process at least one automatic repeat request (ARQ) ACK/NACK
  • ARQ automatic repeat request
  • the one or more processors are further configured to employ a retransmission mechanism at a w-HL C-PDU level in response to the at least one ARQ ACK/NACK response comprising an ARQ NACK.
  • Example 22 comprises the subject matter of any variation of any of example(s) 21 , wherein, in response to the at least one ARQ ACK/NACK response comprising an ARQ NACK, the one or more processors are further configured to:
  • a new PRA and a new allocated size for the w-HL C-PDU determine a new PRA and a new allocated size for the w-HL C-PDU; and based on the new allocated size, at least one of re-segment the w-HL C-PDU, or combine the w-HL C-PDU with at least one of one or more CP packets buffered to the CP transmission buffer, one or more prior w-HL C-PDUs buffered to the CP retransmission buffer, or one or more segments.
  • Example 23 is an apparatus configured to be employed within a User Equipment (UE), comprising a memory; and one or more processors configured to: generate one or more wearable higher layer (w-HL) control protocol data units (C- PDUs) from one or more physical layer transport blocks (TBs); provide the one or more w-HL C-PDUs to the w-HL; generate a plurality of w-HL control service data units (C- SDUs) from the one or more w-HL C-PDUs; determine an ordering of the plurality of w- HL SDUs based on a distinct sequence number (SN) associated with each w-HL SDU of the plurality of w-HL SDUs; and deliver the plurality of w-HL C-SDUs to a wearable radio resource control (w-RRC) layer based on the ordering.
  • w-HL wearable higher layer
  • C- PDUs control protocol data units
  • TBs physical layer transport blocks
  • Example 24 comprises the subject matter of any variation of any of example(s) 23, wherein the one or more processors are further configured to generate one or more hybrid automatic repeat request (HARQ) ACK/NACK
  • HARQ hybrid automatic repeat request
  • Example 25 comprises the subject matter of any variation of any of example(s) 23, wherein the one or more processors are further configured to generate one or more automatic repeat request (ARQ) ACK/NACK (acknowledgement/negative acknowledgement) responses in connection with the one or more w-HL C-PDUs.
  • ARQ automatic repeat request
  • ACK/NACK acknowledgement/negative acknowledgement
  • Example 26 comprises the subject matter of any variation of any of example(s) 23, wherein a first w-HL C-PDU of the one or more w-HL C-PDUs comprises a multiplexing of two or more of a segment of a first w-HL C-SDU of the plurality of w-HL C-SDUs, a second w-HL C-SDU of the plurality of w-HL C-SDUs, a buffer status report (BSR), a power headroom report (PHR), a segment of a first user plane (UP) packet, or a second UP packet.
  • BSR buffer status report
  • PHR power headroom report
  • UP user plane
  • Example 27 comprises the subject matter of any variation of any of example(s) 23, wherein a first w-HL C-PDU of the one or more w-HL C-PDUs comprises a header comprising a plurality of subheaders.
  • Example 28 comprises the subject matter of any variation of any of example(s) 23-27, wherein the UE is a wearable UE (w-UE).
  • w-UE wearable UE
  • Example 29 comprises the subject matter of any variation of any of example(s) 23-27, wherein the UE is a network UE (n-UE), and wherein the one or more processors are configured to generate one or more uplink (UL) grants that indicate one or more physical resource assignments (PRAs), wherein the one or more physical layer TBs correspond to the one or more PRAs.
  • n-UE network UE
  • PRAs physical resource assignments
  • Example 30 comprises the subject matter of any variation of any of example(s) 29, wherein the one or more UL grants indicates grant sizes that correspond to sizes of the one or more w-HL C-PDUs.
  • Example 31 comprises the subject matter of any variation of any of example(s) 23-24, wherein the one or more processors are further configured to generate one or more automatic repeat request (ARQ) ACK/NACK
  • Example 32 is a machine readable medium comprising instructions that, when executed, cause a wearable User Equipment (w-UE) to: receive one or more wearable higher layer (w-HL) control service data units (C-SDUs) from a wearable radio resource control (w-RRC) layer; assign a unique sequence number (SN) to each of the one or more w-HL C-SDUs; store the one or more w-HL C-SDUs in a uplink (UL) control plane (CP) transmission buffer; receive a UL grant that indicates a physical resource assignment (PRA) and a grant size; generate a w-HL control protocol data unit (C-PDU) based at least in part on the UL grant, wherein the w-HL C-PDU comprises one or more of a buffer status report (BSR), a power headroom report (PHR), the UL CP
  • BSR buffer status report
  • PHR power headroom report
  • transmission buffer a UL CP retransmission buffer, a UL user plane (UP) transmission buffer, or a UL UP retransmission buffer; and pass the w-HL C-PDU to a physical layer.
  • a UL CP retransmission buffer a UL CP retransmission buffer, a UL user plane (UP) transmission buffer, or a UL UP retransmission buffer; and pass the w-HL C-PDU to a physical layer.
  • UP user plane
  • Example 33 comprises the subject matter of any variation of any of example(s) 32, wherein the w-HL C-PDU comprises a multiplexing based on two or more of the BSR, the PHR, the UL CP transmission buffer, the UL CP retransmission buffer, the UL UP transmission buffer, or the UL UP retransmission buffer.
  • Example 34 comprises the subject matter of any variation of any of example(s) 32-33, wherein the instructions, when executed, further cause the UE to employ an automatic repeat request (ARQ) ACK/NACK (acknowledgement/negative acknowledgement) retransmission mechanism at a w-HL C-PDU level and a hybrid ARQ (HARQ) ACK/NACK retransmission mechanism at a physical layer transport block (TB) level.
  • ARQ automatic repeat request
  • ACK/NACK acknowledgement/negative acknowledgement
  • HARQ hybrid ARQ
  • Example 35 comprises the subject matter of any variation of any of example(s) 32-33, wherein the w-HL C-PDU header comprises multiple subheaders.
  • Example 36 is an apparatus configured to be employed within a User
  • UE comprising means for storing configured to store instructions; and means for processing configured to execute the instructions to: receive one or more wearable higher layer (w-HL) control service data units (C-SDUs) from a wearable radio resource control (w-RRC) layer; assign a unique sequence number (SN) to each of the one or more w-HL C-SDUs; store the one or more w-HL C-SDUs in a uplink (UL) control plane (CP) transmission buffer; receive a UL grant that indicates a physical resource assignment (PRA) and a grant size; generate a w-HL control protocol data unit (C-PDU) based at least in part on the UL grant, wherein the w-HL C-PDU comprises one or more of a buffer status report (BSR), a power headroom report (PHR), the UL CP
  • BSR buffer status report
  • PHR power headroom report
  • Example 37 comprises the subject matter of any variation of any of example(s) 36, wherein the w-HL C-PDU comprises a multiplexing based on two or more of the BSR, the PHR, the UL CP transmission buffer, the UL CP retransmission buffer, the UL UP transmission buffer, or the UL UP retransmission buffer.
  • Example 38 comprises the subject matter of any variation of any of example(s) 36-37, wherein the means for processing are further configured to execute the instructions to employ an automatic repeat request (ARQ) ACK/NACK
  • ARQ automatic repeat request
  • Example 39 comprises the subject matter of any variation of any of example(s) 36-37, wherein the w-HL C-PDU header comprises multiple subheaders.

Landscapes

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

Abstract

L'invention concerne des techniques pour mettre en oeuvre une couche supérieure vestimentaire (w-HL) pour des communications impliquant un équipement utilisateur vestimentaire (wUE). Un exemple consiste à attribuer un numéro de séquence distinct à chacun d'un ou plusieurs paquets de plan de commande (CP) provenant d'une couche de commande de ressource radio vestimentaire (w-RRC) ; à mettre en mémoire tampon le ou les paquets CP au niveau d'une mémoire tampon de transmission de CP ; à déterminer une attribution de ressource physique (PRA) et une taille attribuée pour une unité de données de protocole de commande (C-PDU) de couche supérieure portable (w-HL)) ; à générer le C-PDU de w-HL sur la base, au moins en partie, du ou des paquets CP mis en mémoire tampon au niveau de la mémoire tampon de transmission de CP, à la PRA, et à la taille attribuée ; à ajouter un en-tête de paquet à la C-PDU de w-HL ; et à fournir la C-PDU de w-HL à une couche physique sur la base du PRA.
PCT/US2016/053024 2016-05-19 2016-09-22 Conception de couche supérieure pour le traitement de paquets de plan de commande dans une communication vestimentaire de cinquième génération (5g) Ceased WO2017200562A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201680084788.6A CN109076568B (zh) 2016-05-19 2016-09-22 用于第五代(5g)可穿戴通信中的控制平面分组处理的高层设计

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662338917P 2016-05-19 2016-05-19
US62/338,917 2016-05-19

Publications (1)

Publication Number Publication Date
WO2017200562A1 true WO2017200562A1 (fr) 2017-11-23

Family

ID=57043036

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/053024 Ceased WO2017200562A1 (fr) 2016-05-19 2016-09-22 Conception de couche supérieure pour le traitement de paquets de plan de commande dans une communication vestimentaire de cinquième génération (5g)

Country Status (2)

Country Link
CN (1) CN109076568B (fr)
WO (1) WO2017200562A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019196762A1 (fr) * 2018-04-09 2019-10-17 Mediatek Inc. Instructions at pour la gestion de sessions 5g
WO2020034577A1 (fr) * 2019-01-11 2020-02-20 Zte Corporation Transmissions de charge utile à base de contention utilisant un codage différentiel
WO2020069678A1 (fr) * 2018-10-06 2020-04-09 Mediatek Inc. Commande at portant sur une session de pdu toujours active
WO2020126018A1 (fr) * 2018-12-20 2020-06-25 Telefonaktiebolaget Lm Ericsson (Publ) Rapport d'état de tampon dans des systèmes de communication sans fil
US20210218535A1 (en) * 2018-09-27 2021-07-15 Vivo Mobile Communication Co.,Ltd. Data transmission method and communications device
CN113302860A (zh) * 2019-01-17 2021-08-24 中兴通讯股份有限公司 使用差分编码的基于竞争的有效载荷传输

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090068317A (ko) * 2009-06-10 2009-06-26 엘지전자 주식회사 상태 보고를 보고하는 방법 및 수신기
CA2722781A1 (fr) * 2008-06-18 2009-12-23 Lg Electronics Inc. Procede de transmission de mac pdu
EP2713650A1 (fr) * 2011-07-15 2014-04-02 Huawei Technologies Co., Ltd Procédé, appareil et système pour une communication à très large bande sans fil

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2028890B1 (fr) * 2007-08-12 2019-01-02 LG Electronics Inc. Procédé de transfert avec récupération d'un échec de lien, dispositif sans fil et station de base pour mettre en 'uvre ce procédé
KR101391382B1 (ko) * 2007-10-01 2014-05-07 인터디지탈 패튼 홀딩스, 인크 Ｐｄｃｐ를 폐기하기 위한 방법 및 장치
US8254333B2 (en) * 2008-09-22 2012-08-28 Htc Corporation Method for improving buffer status triggering mechanism in wireless communications system and related communication device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2722781A1 (fr) * 2008-06-18 2009-12-23 Lg Electronics Inc. Procede de transmission de mac pdu
KR20090068317A (ko) * 2009-06-10 2009-06-26 엘지전자 주식회사 상태 보고를 보고하는 방법 및 수신기
EP2713650A1 (fr) * 2011-07-15 2014-04-02 Huawei Technologies Co., Ltd Procédé, appareil et système pour une communication à très large bande sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC: "5G user plane protocol design", vol. RAN WG2, no. Dubrovnik, Croatia; 20160411 - 20160415, 2 April 2016 (2016-04-02), XP051082602, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_93bis/Docs/> [retrieved on 20160402] *

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10911979B2 (en) 2018-04-09 2021-02-02 Mediatek Inc. AT commands for 5G session management
WO2019196762A1 (fr) * 2018-04-09 2019-10-17 Mediatek Inc. Instructions at pour la gestion de sessions 5g
US11876746B2 (en) * 2018-09-27 2024-01-16 Vivo Mobile Communication Co., Ltd. Data transmission method and communications device
US20210218535A1 (en) * 2018-09-27 2021-07-15 Vivo Mobile Communication Co.,Ltd. Data transmission method and communications device
TWI747056B (zh) * 2018-10-06 2021-11-21 聯發科技股份有限公司 常駐協定資料單元會話之處理方法及其裝置
WO2020069678A1 (fr) * 2018-10-06 2020-04-09 Mediatek Inc. Commande at portant sur une session de pdu toujours active
US11184934B2 (en) 2018-10-06 2021-11-23 Mediatek Inc. AT-command for always-on PDU session
WO2020126018A1 (fr) * 2018-12-20 2020-06-25 Telefonaktiebolaget Lm Ericsson (Publ) Rapport d'état de tampon dans des systèmes de communication sans fil
US11864022B2 (en) 2018-12-20 2024-01-02 Teleonaktiebolaget LM Ericsson (publ) Buffer status reporting in wireless communication systems
CN113303013A (zh) * 2019-01-11 2021-08-24 中兴通讯股份有限公司 使用差分编码的基于竞争的有效载荷传输
WO2020034577A1 (fr) * 2019-01-11 2020-02-20 Zte Corporation Transmissions de charge utile à base de contention utilisant un codage différentiel
CN113303013B (zh) * 2019-01-11 2024-04-16 中兴通讯股份有限公司 使用差分编码的基于竞争的有效载荷传输
US12047217B2 (en) 2019-01-11 2024-07-23 Zte Corporation Contention-based payload transmissions using differential coding
CN113302860A (zh) * 2019-01-17 2021-08-24 中兴通讯股份有限公司 使用差分编码的基于竞争的有效载荷传输
US11601318B2 (en) 2019-01-17 2023-03-07 Zte Corporation Contention-based payload transmissions using differential coding
CN113302860B (zh) * 2019-01-17 2023-05-09 中兴通讯股份有限公司 使用差分编码的基于竞争的有效载荷传输

Also Published As

Publication number Publication date
CN109076568B (zh) 2022-08-19
CN109076568A (zh) 2018-12-21

Similar Documents

Publication Publication Date Title
US11758615B2 (en) User equipment (UE), evolved node-B (ENB) and methods for a packet convergence and link control (PCLC) layer
CN107005383B (zh) 用于ca(载波聚合)和laa(授权辅助接入)的多个分量载波上的传输块的联合处理
EP3348012B1 (fr) Transmission de multiples bits de rétroaction harq-ack correspondant à de multiples cellules de liaison descendante et un ou deux blocs de transport par cellule
US10708000B2 (en) Contention window size adaptation
CA2954996C (fr) Equipement d&#39;utilisateur et procedes d&#39;allocation et de signalisation de ressources de temps pour les communications de dispositif a dispositif (d2d)
EP3453222B1 (fr) Conception de couche supérieure destinée au traitement de paquets de plan utilisateur dans une communication de liaison latérale d&#39;objet (tsl) de nouvelle radio (nr) de cinquième génération (5g)
WO2017200562A1 (fr) Conception de couche supérieure pour le traitement de paquets de plan de commande dans une communication vestimentaire de cinquième génération (5g)
WO2017160350A1 (fr) Équipement utilisateur (ue), nœud b évolué (enb) et procédés de demande de répétition automatique hybride (harq) destinés aux aménagements d&#39;agrégation de porteuse
EP3251458B1 (fr) Informations de commande de salve à accès assisté par licence (laa)
WO2019056369A1 (fr) Procédé et dispositif de communication
US20220368494A1 (en) Uplink re-transmission with compact memory usage
WO2018080565A1 (fr) Procédures de transfert et de réception de données dans des communications de liaison latérale 5g/s
WO2018038758A1 (fr) Transmission d&#39;informations de commande après autorisation de liaison montante
WO2017099831A1 (fr) Signalisation de commande dans un fonctionnement de faisceaux multiples
US10285168B2 (en) Systems and methods for elimination of PDCCH in resource allocation signaling for MTC devices
TWI703831B (zh) 通道狀態資訊回饋通道
EP4133641B1 (fr) Indication d&#39;intervalle de redondance pour transmission de données améliorée
WO2018071050A1 (fr) Procédures de retransmission pour une communication de liaison latérale des objets (tsl) new radio (nr) de cinquième génération (5g)
CN116171626B (zh) 用于利用多物理下行链路共享信道调度的基于码本组的操作的方法和装置
WO2018119458A2 (fr) Traitement d&#39;en-tête de paquet préalablement à un autorisation
WO2025148034A1 (fr) Configurations temporelles et de numéro de paquet de données pour des communications sans fil
WO2018044258A1 (fr) Procédé et appareil permettant d&#39;éviter l&#39;entrée d&#39;un indicateur de longueur pour des unités de données de service de même longueur dans une unité de données de protocole de commande de liaison radioélectrique
HK1237154A1 (en) Joint processing of transport blocks on multiple component carriers for ca (carrier aggregation) and laa (license assisted access)
HK1252882B (zh) 无线系统中的上行链路控制信息的传输
HK1237154B (zh) 用於ca(载波聚合)和laa(授权辅助接入)的多个分量载波上的传输块的联合处理

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 16774800

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16774800

Country of ref document: EP

Kind code of ref document: A1