WO2018071064A1 - Systèmes, procédés et dispositifs de protocole de commande de transmission de liaison descendante dans des réseaux cellulaires - Google Patents

Systèmes, procédés et dispositifs de protocole de commande de transmission de liaison descendante dans des réseaux cellulaires Download PDF

Info

Publication number
WO2018071064A1
WO2018071064A1 PCT/US2017/036767 US2017036767W WO2018071064A1 WO 2018071064 A1 WO2018071064 A1 WO 2018071064A1 US 2017036767 W US2017036767 W US 2017036767W WO 2018071064 A1 WO2018071064 A1 WO 2018071064A1
Authority
WO
WIPO (PCT)
Prior art keywords
drwa
drb
value
data packets
message
Prior art date
Application number
PCT/US2017/036767
Other languages
English (en)
Inventor
Jing Zhu
Sarabjot SINGH
Ehsan ARYAFAR
Original Assignee
Intel Corporation
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 Corporation filed Critical Intel Corporation
Publication of WO2018071064A1 publication Critical patent/WO2018071064A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1832—Details of sliding window management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1874—Buffer management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/30—Flow control; Congestion control in combination with information about buffer occupancy at either end or at transit nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • 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/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0242—Determining whether packet losses are due to overload or to deterioration of radio communication conditions
    • 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/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • 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/0273—Traffic management, e.g. flow control or congestion control adapting protocols for flow control or congestion control to wireless environment, e.g. adapting transmission control protocol [TCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/06—Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless

Definitions

  • the present disclosure relates generally to the field of wireless
  • TCP transmission control protocol
  • Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device.
  • Wireless communication system standards and protocols can include the 3rd
  • 3GPP long term evolution
  • IEEE Institute of Electrical and Electronics Engineers 802.16 standard, which is commonly known to industry groups as worldwide interoperability for microwave access
  • the base station can include a RAN node such as an evolved universal terrestrial radio access network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE).
  • E-UTRAN evolved universal terrestrial radio access network
  • Node B also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB
  • RNC Radio Network Controller
  • UE user equipment
  • RAN nodes can include a 5G node or next generation NodeB (gNB).
  • RANs use a radio access technology (RAT) to communicate between the RAN node and UE.
  • RANs can include global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), universal terrestrial radio access network (UTRAN), and/or E-UTRAN, which provide access to communication services through a core network.
  • GSM global system for mobile communications
  • EDGE enhanced data rates for GSM evolution
  • GERAN enhanced data rates for GSM evolution
  • UTRAN universal terrestrial radio access network
  • E-UTRAN which provide access to communication services through a core network.
  • the GERAN implements GSM and/or EDGE RAT
  • the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT
  • the E-UTRAN implements LTE RAT.
  • UMTS universal mobile telecommunication system
  • a core network can be connected to the UE through the RAN node.
  • the core network can include a serving gateway (SGW), a packet data network (PDN) gateway (PGW), an access network detection and selection function (ANDSF) server, an enhanced packet data gateway (ePDG) and/or a mobility management entity (MME).
  • SGW serving gateway
  • PGW packet data network gateway
  • ANDSF access network detection and selection function
  • ePDG enhanced packet data gateway
  • MME mobility management entity
  • FIG. 1 is a diagram illustrating an example of an environment in which the present systems and methods may be implemented in accordance with some embodiments.
  • FIG. 2 illustrates a sequence diagram for adding a retransmission TCP data packet radio bearer to a user equipment in accordance with some
  • FIG. 3 illustrates a sequence diagram for a RAN node assisted dynamic receiver window advertisement procedure in accordance with some embodiments.
  • FIG. 4 is a block diagram illustrating electronic device circuitry that may be UE circuitry, evolved universal terrestrial radio access network (E-UTRAN) Node B (evolved Node B, eNodeB, or eNB) circuitry, or network node circuitry in accordance with some embodiments.
  • E-UTRAN evolved universal terrestrial radio access network
  • Node B evolved Node B, eNodeB, or eNB
  • network node circuitry in accordance with some embodiments.
  • FIG. 5 illustrates an architecture of a system of a network in accordance with some embodiments.
  • FIG. 6 illustrates example components of a device 600 in accordance with some embodiments.
  • FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • FIG. 8 is a block diagram illustrating components, according to some example embodiments.
  • Next generation cellular systems are expected to provide very high peak data rates, for example, 10Gbps, by using a high frequency band or spectrum, such as a millimeter wave (mmWave) frequency band.
  • mmWave channels are highly sensitive to the environment, especially by blockage of the signal. This results in an available data rate that may vary rapidly based on the environment of the UE.
  • the end-to-end TCP connection may suffer a "bufferbloat" problem and experience excessively long latency. For example, when the mmWave channel changes from light-of-sight (LoS) to non-LoS, there may be a significant data rate deduction, resulting in data packets sitting in a queue for longer than a desired period of time.
  • LiS light-of-sight
  • a conventional solution to the bufferbloat problem is active queue management (AQM).
  • AQM monitors the queue status, for example, a queue length and delay, to detect a potential bufferbloat risk in advance.
  • AQM then proactively drops data packets to trigger congestion control at the TCP sender and prevent bufferbloat. The dropped data packets, however, must be retransmitted at a later time.
  • the TCP sender may not reduce its transmission rate quickly enough when a risk of bufferbloat is detected, resulting in lots of data packets already in the queue of the buffer.
  • the retransmitted data packet When a retransmitted data packet arrives to be transmitted, the retransmitted data packet must wait for all the data packets in the front of the queue to be transmitted first. The data packets are then out of order at the TCP receiver and must wait at the TCP receiver until the retransmitted packet is delivered successfully. While the TCP receiver is waiting for the retransmitted data packet, the application receives no data at all, since the TCP receiver is waiting to process the data packets in order.
  • the TCP sender may reduce its transmission rate too much in an attempt to reduce bufferbloat, resulting in link underutilization and low throughput.
  • FIG. 1 illustrates an example of an
  • the environment 100 includes multiple RAN nodes 1 10.
  • the RAN nodes 1 10 may be mmWave enhanced RAN nodes or next generation NodeBs (gNBs).
  • each of the multiple RAN nodes 1 10 may be part of the same E-UTRAN.
  • at least one of the RAN nodes 1 10 is associated with a different RAN (e.g., a different E-UTRAN).
  • One or more UEs 105 may be within the coverage area of a RAN node 1 10 and may communicate with the RAN node 1 10 via a cellular air interface 120 (such as an LTE/LTE-Advanced access link).
  • FIG. 2 is a sequence diagram 200 illustrating a procedure for creating a separate data radio bearer (DRB) in a UE 105 for retransmitted data packets.
  • a RAN node 1 10 initiates a TCP retransmission DRB establishment procedure by sending a radio resource control (RRC) connection reconfiguration message 202 to the UE 105.
  • RRC radio resource control
  • FIG. 2 it is assumed a first DRB is already established and a second DRB is added for retransmitting TCP data packets. This allows retransmitted data packets to be accessed and processed more quickly, as they are transmitted in a separate DRB from new data packets and do not have to sit in a queue with the new data packets.
  • the data packets can quickly be retransmitted in a separate DRB to allow for the retransmitted data packets to be processed more quickly, rather than waiting in a queue behind new data packets.
  • the RRC connection reconfiguration message 202 includes configuration information for the UE 105 to establish the second DRB.
  • the UE 105 processes the received RRC connection reconfiguration message 202 and establishes the second DRB based on the configuration information.
  • the UE 105 successfully establishes the second DRB based on the configuration information in the RRC connection reconfiguration message 202, the UE 105 generates and sends an RRC connection reconfiguration complete message 204 to the RAN node 1 10 to confirm the second DRB was successfully added by the UE 105.
  • the RAN node 1 10 processes the RRC connection reconfiguration complete message 204 to confirm that the second DRB was successfully added by the UE 105 and begins sending retransmitted TCP data packets 208 over the second DRB while sending new TCP data packets 206 over the first DRB.
  • the RAN node 1 10 may determine which TCP data packets are retransmitted data packets by using deep packet inspection, for example. However, the RAN node 1 10 may use other methods as well, as will be understood by one of ordinary skill in the art, to determine whether a TCP data packet is a retransmitted data packet, and as such, to determine which DRB to use to send a TCP data packet.
  • the RAN node 1 10 instructs the UE 105 to establish a single retransmission DRB to support all quality of service (QoS) flows in the TCP connection and the RAN node 1 10 sends all of the retransmitted TCP data packets 208 over the single retransmission DRB.
  • QoS quality of service
  • the RAN node 1 10 instructs the UE 105 to establish a retransmission DRB for each QoS flow in the TCP connection. For example, if there are four established DRBs, each DRB associated with a QoS flow, the RRC connection reconfiguration message 202 instructs the UE 105 to establish four retransmission DRBs, each retransmission DRB associated with an established DRB and its QoS flow, resulting in eight total DRBs.
  • the RAN node 1 10 may send a single RRC connection reconfiguration message 202 to establish a plurality of retransmission DRBs, or, alternatively, the RAN node 1 10 may send a plurality of RRC connection reconfiguration messages 202, each message instructing the UE 105 to establish a respective retransmission DRB.
  • the RAN node 1 10 may provide an established DRB identification in the RRC connection reconfiguration message 202 to indicate with which established DRB the retransmission DRB is associated. Therefore, when a retransmitted data packet is received at the retransmission DRB, the UE 105 is able to know which QoS flow the transmitted data packet is associated with.
  • the RAN node 1 10 may determine a recommended receiver window advertisement (RWA) for the TCP connection and send the recommended RWA to the UE 105 to implement.
  • RWA receiver window advertisement
  • FIG. 3 illustrates a sequence diagram 300 for a RAN node-assisted dynamic RWA (DRWA) procedure.
  • the RAN node 1 10 detects 314 a potential bufferbloat and sends a RAN node-assisted DRWA start message to the UE 105 with an initial value for a recommended RWA for the TCP connection.
  • DRWA RAN node-assisted dynamic RWA
  • the RAN node 1 10 uses a specific time interval and a target delay for each data packet in the queue to be sent to the UE 105.
  • a queuing delay is calculated which is the amount of time a data packet is spent waiting in the queue.
  • the lowest queuing delay for the specific time interval is stored.
  • the specific time interval may be 100ms, and the lowest queuing delay over 100ms is recorded and stored in a memory of the RAN node 1 10.
  • the RAN node 1 10 compares the lowest queuing delay to the target queuing delay. If the lowest queuing delay is greater than the target queuing delay during the specific time interval, bufferbloat is detected. For example, the target queuing delay over the specific time interval of 100ms may be 5ms. If the lowest queuing delay is greater than 5ms, bufferbloat is declared.
  • the RAN node 1 10 calculates a
  • the RAN node 1 10 calculates the recommended RWA value, Wj, by equation (1 ):
  • Variable Qj is an estimated bandwidth-delay product.
  • a bandwidth-delay product is the product of a data link's capacity, in bits per second, and its round-trip delay time.
  • Variable ⁇ is an estimated link throughput, or available bandwidth.
  • Variable tj is an estimated round-trip time when bufferbloat is not present.
  • Variable T is the specific time interval, which may be configurable, and qj is a current queue length.
  • Variable dj is an estimated queue increase. That is, variable dj is the amount the queue of data packets is estimated to increase.
  • the RAN node 1 10 may calculate the
  • the RAN node 1 10 may calculate the
  • equations (2) and (3) a is a constant that may be configurable and variable D is a tolerable maximum queuing delay, which also may be configurable.
  • the RAN node 1 10 sends the RAN node-assisted DRWA start message 302 with the recommended RWA value, Wj, to the UE 105.
  • UE 105 compares the recommended RWA value, Wj, to a local RWA value stored in a memory. If the recommended RWA value is lower than the local RWA value, then the UE 105 implements and uses the received recommended RWA value from the RAN node 1 10.
  • the RAN node 1 10 continues to monitor the queue delay over the specific time interval, and if the bufferbloat continues, the RAN node 1 10 calculates an updated recommended RWA value based on one of equations (1 )- (3), discussed above. That is, after bufferbloat is declared, the RAN node 1 10 continues to monitor the queue delay for continuing specific time intervals, and if needed, recalculates the RWA value to send an updated RWA value to the UE 105.
  • the RAN node 1 10 sends 304 the updated RWA value to the UE 105 in a RAN node-assisted DRWA update message.
  • the UE 105 uses the recommended RWA value for the
  • the RAN node 1 10 After continuing to monitor the queuing delay, once the RAN node 1 10 detects 316 that the bufferbloat has ended, the RAN node 1 10 sends 306 a RAN node-assisted DRWA end message to stop the RAN node-assisted DRWA procedure and the UE 105 then uses the local RWA value for the corresponding TCP data flow.
  • a RAN node 1 10 does not modify or inspect a data packet for a TCP and merely forwards the TCP data packet to the core network for processing.
  • a RAN node 1 10 may run a TCP connection on behalf of a UE 105, referred to as a RAN-based TCP offload.
  • the RAN node 1 10 is responsible for sending a TCP acknowledgement message to the core network.
  • the RAN node 1 10 may then send a recommended RWA value to the core network in the TCP acknowledgement message.
  • the recommended RWA value is determined using one of equations (1 )-(3), discussed above.
  • FIG. 4 is a block diagram illustrating electronic device circuitry 400 that may be RAN node circuitry, UE circuitry, network node circuitry, or some other type of circuitry in accordance with various embodiments.
  • the electronic device circuitry 400 may be, or may be incorporated into or otherwise a part of, an RAN node, a UE, a network node, or some other type of electronic device.
  • the electronic device circuitry 400 may include radio transmit circuitry 410 and receive circuitry 412 coupled to control circuitry 414.
  • the transmit circuitry includes a transmit buffer 418 for storing TCP data packets to be sent.
  • the transmit circuitry 410 and/or receive circuitry 412 may be elements or modules of transceiver circuitry, as shown.
  • the electronic device circuitry 400 may be coupled with one or more plurality of antenna elements 416 of one or more antennas.
  • the electronic device circuitry 400 and/or the components of the electronic device circuitry 400 may be configured to perform operations similar to those described elsewhere in this disclosure.
  • the receive circuitry 412 may be to receive, from a RAN node 1 10 of a long term evolution (LTE) network, an RRC connection configuration message to establish at least one retransmission DRB.
  • LTE long term evolution
  • the control circuitry 414 may be to process the RRC connection configuration message and establish the at least one retransmission DRB.
  • the transmit circuitry 410 may be to transmit, to the RAN node 1 10, an RRC connection reconfiguration complete message to inform the RAN node 1 10 the at least one retransmission DRB is established.
  • the receive circuitry 412 may be to receive, from a RAN node 1 10 of a long term evolution (LTE) network, a RAN node- assisted DRWA start message, a RAN node-assisted DRWA update message, and/or a RAN node-assisted DRWA end message.
  • the control circuitry 414 may be to process the various messages and set a RWA value for the TCP connection based on the received message.
  • the transmit circuitry 410 may be to transmit to a carrier aggregation (CA)-enabled user equipment (UE) of a long term evolution (LTE) network, an RRC connection configuration message with instructions for the UE to establish a retransmission DRB.
  • CA carrier aggregation
  • UE user equipment
  • LTE long term evolution
  • the receive circuitry 412 may be to receive, from the UE based on the transmitting, an RRC connection reconfiguration complete message indicating whether the UE added the retransmission DRB.
  • the control circuitry 414 may be to determine or otherwise prepare the RRC connection reconfiguration message.
  • the transmit circuitry 410 may be to transmit to a carrier aggregation (CA)-enabled user equipment (UE) of a long term evolution (LTE) network, an RRC connection configuration message with instructions for the UE to establish a retransmission DRB.
  • CA carrier aggregation
  • UE user equipment
  • LTE long term evolution
  • the receive circuitry 412 may be to receive, from the UE based on the transmitting, an RRC connection reconfiguration complete message indicating whether the UE added the retransmission DRB.
  • the control circuitry 414 may be to determine or otherwise prepare the RRC connection reconfiguration message as well as process the RRC connection reconfiguration complete message.
  • 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. 5 illustrates an architecture of a system 500 of a network in
  • the system 500 is shown to include a user equipment (UE) 501 and a UE 502.
  • UE user equipment
  • the UEs 501 and 502 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets wireless communications interface
  • any of the UEs 501 and 502 can comprise an Internet of Things (loT) UE, which can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections.
  • An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type
  • MTC mobile communications
  • PLMN public land mobile network
  • Proximity-Based Service ProSe
  • D2D device-to- device
  • the M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An loT network describes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the loT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.
  • the UEs 501 and 502 may be configured to connect, e.g.,
  • the RAN 510 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 501 and 502 utilize connections 503 and 504, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 503 and 504 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the UEs 501 and 502 may further directly exchange communication data via a ProSe interface 505.
  • the ProSe interface 505 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery
  • PSDCH Physical Sidelink Broadcast Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 502 is shown to be configured to access an access point (AP) 506 via connection 507.
  • the connection 507 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.1 1 protocol, wherein the AP 506 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 506 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 510 can include one or more access nodes that enable the connections 503 and 504. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • BSs base stations
  • eNBs evolved NodeBs
  • gNB next Generation NodeBs
  • RAN nodes and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the RAN 510 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 51 1 , and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g. , low power (LP) RAN node 512.
  • RAN nodes 51 1 and 512 can terminate the air interface protocol and can be the first point of contact for the UEs 501 and 502. In some
  • any of the RAN nodes 51 1 and 512 can fulfill various logical functions for the RAN 510 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • the UEs 501 and 502 can be configured to communicate using Orthogonal Frequency-Division Multiplexing
  • OFDMMA Orthogonal Frequency- Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 51 1 and 512 to the UEs 501 and 502, while uplink transmissions can utilize similar techniques.
  • the grid can be a time- frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.
  • the physical downlink shared channel may carry user data and higher-layer signaling to the UEs 501 and 502.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 501 and 502 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 51 1 and 512 based on channel quality information fed back from any of the UEs 501 and 502.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 501 and 502.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • RAGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L 1 , 2, 4, or 8).
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • the RAN 510 is shown to be communicatively coupled to a core network (CN) 520— via an S1 interface 513.
  • the CN 520 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the S1 interface 513 is split into two parts: the S1 -U interface 514, which carries traffic data between the RAN nodes 51 1 and 512 and the serving gateway (S-GW) 522, and the S1 -mobility management entity (MME) interface 515, which is a signaling interface between the RAN nodes 51 1 and 512 and MMEs 521 .
  • MME mobility management entity
  • the CN 520 comprises the MMEs 521 , the S-GW 522, the Packet Data Network (PDN) Gateway (P-GW) 523, and a home subscriber server (HSS) 524.
  • the MMEs 521 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • GPRS General Packet Radio Service
  • the MMEs 521 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 524 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 520 may comprise one or several HSSs 524, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 524 can provide support for routing/roaming, authentication, authorization,
  • the S-GW 522 may terminate the S1 interface 513 towards the RAN 510, and routes data packets between the RAN 510 and the CN 520.
  • the S- GW 522 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 523 may terminate an SGi interface toward a PDN.
  • the P-GW 523 may route data packets between the EPC network 523 and external networks such as a network including the application server 530 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 525.
  • the application server 530 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • LTE PS data services etc.
  • the application server 530 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 501 and 502 via the CN 520.
  • VoIP Voice-over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 523 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Enforcement Function (PCRF) 526 is the policy and charging control element of the CN 520.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V-PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • the PCRF 526 may be communicatively coupled to the application server 530 via the P- GW 523.
  • the application server 530 may signal the PCRF 526 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 526 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 530.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 6 illustrates example components of a device 600 in accordance with some embodiments.
  • the device 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown.
  • the components of the illustrated device 600 may be included in a UE or a RAN node.
  • RF Radio Frequency
  • FEM front-end module
  • PMC power management circuitry
  • the device 600 may include less elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor/controller to process IP data received from an EPC).
  • the device 600 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN)
  • the application circuitry 602 may include one or more application processors.
  • the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • processor(s) may include any combination of general-purpose processors
  • processors of application circuitry 602 may process IP data packets received from an EPC.
  • the baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606.
  • Baseband processing circuity 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606.
  • the baseband circuitry 604 may include a third generation (3G) baseband processor 604A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) baseband processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 604 e.g., one or more of baseband processors 604A-D
  • radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio
  • modulation/demodulation circuitry of the baseband circuitry 604 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC)
  • 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 604 may include one or more audio digital signal processor(s) (DSP) 604F.
  • the audio DSP(s) 604F 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 604 and the application circuitry 602 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 604 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 604 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.
  • RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 606 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604.
  • RF circuitry 606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.
  • the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c.
  • the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a.
  • RF circuitry 606 may also include
  • synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path.
  • the mixer circuitry 606a of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d.
  • the amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c 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 604 for further processing.
  • the output baseband signals may be zero- frequency baseband signals, although this is not a requirement.
  • mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608.
  • the baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a 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 606a of the receive signal path and the mixer circuitry 606a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a 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 606 may include analog-to- digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.
  • 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 embodiments is not limited in this respect.
  • the synthesizer circuitry 606d may be a fractionally synthesizer or a fractional N/N+1 synthesizer, although the scope of the
  • synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606d 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 604 or the applications processor 602 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 602.
  • Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • DLL delay-locked loop
  • 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. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.
  • synthesizer circuitry 606d 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 606 may include an IQ/polar converter.
  • FEM circuitry 608 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing.
  • FEM circuitry 608 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM 608, or in both the RF circuitry 606 and the FEM 608.
  • the FEM circuitry 608 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 an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606).
  • the transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).
  • PA power amplifier
  • the PMC 612 may manage power provided to the baseband circuitry 604.
  • the PMC 612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 612 may often be included when the device 600 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 6 shows the PMC 612 coupled only with the baseband circuitry 604.
  • the PMC 612 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM 608.
  • the PMC 612 may control, or otherwise be part of, various power saving mechanisms of the device 600. For example, if the device 600 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 600 may transition off to an RRCJdle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 600 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 600 may not receive data in this state, in order to receive data, it must transition back to RRC_Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 602 and processors of the baseband circuitry 604 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 604 alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 604 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g.,
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 604 of FIG. 6 may comprise processors 604A-604E and a memory 604G utilized by said processors.
  • Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send/receive data to/from the memory 604G.
  • the baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 712 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604), an application circuitry interface 714 (e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6), an RF circuitry interface 716 (e.g., an interface to send/receive data to/from RF circuitry 606 of FIG. 6), a wireless hardware connectivity interface 718 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication
  • NFC Near Field Communication
  • Bluetooth® components e.g., Bluetooth® Low Energy
  • Wi-Fi® components e.g., Wi-Fi® components
  • a power management interface 720 e.g., an interface to send/receive power or control signals to/from the PMC 612.
  • FIG. 8 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • FIG. 8 shows a diagrammatic representation of hardware resources 800 including one or more processors (or processor cores) 810, one or more
  • a hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 800
  • the processors 810 may include, for example, a processor 812 and a processor 814.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the memory/storage devices 820 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 820 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • the communication resources 830 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 via a network 808.
  • the communication resources 830 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular
  • NFC components NFC components
  • Bluetooth® components e.g., Bluetooth® Low Energy
  • Wi-Fi® components Wi-Fi components
  • Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein.
  • the instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor's cache memory), the memory/storage devices 820, or any suitable combination thereof.
  • any portion of the instructions 850 may be transferred to the hardware resources 800 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the memory/storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine- readable media.
  • Example 1 is an apparatus for user equipment (UE).
  • the apparatus includes a memory interface to store or access, to or from a memory device, a radio resource control (RRC) connection reconfiguration message, the RRC connection reconfiguration message including configuration information to add a retransmission data radio bearer (DRB) dedicated to retransmitted transmission control protocol (TCP) data packets.
  • RRC radio resource control
  • the apparatus also includes a baseband processor circuitry to process new TCP data packets from a radio access network (RAN) node over a first DRB and process the RRC connection reconfiguration message to identify the configuration information.
  • RAN radio access network
  • the apparatus also includes a baseband processor circuitry to in response to the RRC connection reconfiguration message, establish the retransmission DRB based on the configuration information, and process the retransmitted TCP data packets from the RAN node over the retransmission DRB.
  • Example 2 is the apparatus of Example 1 , where the baseband processor circuitry is further designed to process the retransmitted TCP data packets over the retransmission DRB for a single quality of service (QoS) data flow corresponding to the first DRB, and where the configuration information includes a DRB identifier (ID) associated with the first DRB.
  • QoS quality of service
  • Example 3 is the apparatus of Example 1 , where the baseband processor circuitry is further designed to process the retransmitted TCP data packets over the retransmission DRB for a variety of quality of service (QoS) data flows corresponding to the first DRB and at least a second DRB.
  • QoS quality of service
  • Example 4 is the apparatus of Example 1 , where the baseband processor circuitry is further designed to establish a variety of retransmission DRBs, each retransmission DRB to process retransmitted TCP data packets for a respective quality of service (QoS) data flow.
  • QoS quality of service
  • Example 5 is the apparatus of Example 4, where the memory interface is designed to store a variety of RRC connection reconfiguration messages, where each of the variety of RRC connection reconfiguration message includes the configuration information for a respective retransmission DRB to receive the retransmitted TCP data packets for a respective QoS data flow.
  • Example 6 is the apparatus of Example 5, where each of the variety of
  • RRC connection reconfiguration messages further includes an identification of an established DRB associated with the respective retransmission DRB.
  • Example 7 is an method for user equipment (UE).
  • the method includes processing a radio resource control (RRC) connection reconfiguration message, the
  • RRC connection reconfiguration message including configuration information to add a retransmission data radio bearer (DRB) dedicated to retransmitted transmission control protocol (TCP) data packets.
  • the method includes processing new TCP data packets from a radio access network (RAN) node over a first DRB in response to the
  • RRC connection reconfiguration message establishing the retransmission DRB based on the configuration information, and processing the retransmitted TCP data packets from the RAN node over the retransmission DRB.
  • Example 8 is the method of Example 7, further including processing the retransmitted TCP data packets over the retransmission DRB for a single quality of service (QoS) data flow corresponding to the first DRB, and where the configuration information includes a DRB identifier (ID) associated with the first DRB.
  • QoS quality of service
  • Example 9 is the method of Example 7, further including processing the retransmitted TCP data packets over the retransmission DRB for a variety of quality of service (QoS) data flows corresponding to the first DRB and at least a second DRB.
  • QoS quality of service
  • Example 10 is the method of Example 7, further including establishing a variety of retransmission DRBs, each retransmission DRB to process retransmitted TCP data packets for a respective quality of service (QoS) data flow.
  • QoS quality of service
  • Example 1 1 is the method of Example 10, further including processing a variety of RRC connection reconfiguration messages, where each of the variety of RRC connection reconfiguration message includes the configuration information for a respective retransmission DRB to receive the retransmitted TCP data packets for a respective QoS data flow.
  • Example 12 is the method of Example 1 1 , where each of the variety of RRC connection reconfiguration messages further includes an identification of an established DRB associated with the respective retransmission DRB.
  • Example 13 is an apparatus for the UE, the apparatus includes a means for performing the method of any one of Examples 7-12.
  • Example 14 is a computer-readable storage medium having instructions stored thereon that, when executed by a processor of the UE, cause the processor to perform the method of any one of Examples 7-12.
  • Example 15 is a computer-readable storage medium.
  • the computer- readable storage medium having instructions stored thereon that, when executed by a processor of a radio access network (RAN) node, cause the processor to establish a first data radio bearer (DRB) to communicate data packets to a user equipment (UE) according to a quality of service (QoS) data flow.
  • the computer-readable storage medium having instructions stored thereon that, when executed by a processor of a radio access network (RAN) node, cause the processor to determine that the first DRB is unable to provide, at least temporarily, the QoS data flow based on a subset of the data packets that are delayed, dropped, or otherwise initially undelivered to the UE.
  • the computer-readable storage medium having instructions stored thereon that, when executed by a processor of a radio access network (RAN) node, cause the processor to in response to the determination that the first DRB is unable to provide the QoS data flow, establish a second DRB to communicate with the UE.
  • the computer-readable storage medium having instructions stored thereon that, when executed by a processor of a radio access network (RAN) node, cause the processor to direct initial transmissions of the data packets through the first DRB and the subset of the data packets that are dropped or otherwise initially undelivered through the second DRB.
  • Example 16 is the computer-readable storage medium of Examples 15, where the instructions further cause the processor to determine configuration information to instruct the UE to add the second DRB, the configuration information including an indication that the second DRB is dedicated to receiving and processing the subset of the data packets that are delayed, dropped, or otherwise initially undelivered.
  • RRC radio receiver control
  • Example 17 is the computer-readable storage medium of any of Examples 15-16, where the instructions further cause the processor to perform active queue management to proactively drop a variety of the subset of the data packets for congestion control.
  • Example 18 is the computer-readable storage medium of any of Examples 15-16, where the instructions further cause the processor to direct the subset of the data packets for transmission through the second DRB at a higher priority and lower latency than the initial transmission of the data packets through the first DRB.
  • Example 19 is the computer-readable storage medium of any of Examples 15-16, where the instructions further cause the processor to design the second DRB to communicate retransmitted data packets for one or more additional QoS data flows.
  • Example 20 is the computer-readable storage medium of any of Examples 15-16, where the instructions further cause the processor to design a third DRB to communicate retransmitted data packets to the UE for another QoS data flow.
  • Example 21 is a method for a radio access network (RAN) node.
  • the method establishes a first data radio bearer (DRB) to communicate data packets to a user equipment (UE) according to a quality of service (QoS) data flow, and determining that the first DRB is unable to provide, at least temporarily, the QoS data flow based on a subset of the data packets that are delayed, dropped, or otherwise initially undelivered to the UE.
  • DRB data radio bearer
  • QoS quality of service
  • the method in response to the determination that the first DRB is unable to provide the QoS data flow, establishing a second DRB to communicate with the UE, and directing initial transmissions of the data packets through the first DRB and the subset of the data packets that are dropped or otherwise initially undelivered through the second DRB.
  • Example 22 is the method of Examples 21 , further including determining configuration information to instruct the UE to add the second DRB, the configuration information including an indication that the second DRB is dedicated to receiving and processing the subset of the data packets that are delayed, dropped, or otherwise initially undelivered, and generating a radio receiver control (RRC) connection reconfiguration message for the UE, the RRC connection reconfiguration message including the configuration information.
  • RRC radio receiver control
  • Example 23 is the method of any of Examples 21 -22, further including performing active queue management to proactively drop a variety of the subset of the data packets for congestion control.
  • Example 24 is the method of any of Examples 21 -22, further including directing the subset of the data packets for transmission through the second DRB at a higher priority and lower latency than the initial transmission of the data packets through the first DRB.
  • Example 25 is the method of any of Examples 21 -22, further including including the second DRB to communicate retransmitted data packets for one or more additional QoS data flows.
  • Example 26 is the method of any of Examples 21 -22, further including designing a third DRB to communicate retransmitted data packets to the UE for another QoS data flow.
  • Example 27 is an apparatus for the RAN node, the apparatus including a means for performing the method of any one of Examples 21 -26.
  • Example 28 is an apparatus for a radio access network (RAN) node.
  • the node includes a memory interface to store or access, to or from a memory device, data packets.
  • the node includes one or more baseband processors designed to establish a first data radio bearer (DRB) to communicate the data packets to a user equipment (UE) according to a quality of service (QoS) data flow, and determine that the first DRB is unable to provide, at least temporarily, the QoS data flow based on a subset of the data packets that are delayed, dropped, or otherwise initially
  • DRB data radio bearer
  • UE user equipment
  • QoS quality of service
  • the node includes one or more baseband processors designed to in response to the determination that the first DRB is unable to provide the QoS data flow, establish a second DRB to communicate with the UE, and direct initial transmissions of the data packets through the first DRB and the subset of the data packets that are dropped or otherwise initially undelivered through the second DRB.
  • Example 29 is the apparatus of Example 28, where the one or more baseband processors are further designed to determine configuration information to instruct the UE to add the second DRB, the configuration information including an indication that the second DRB is dedicated to receiving and processing the subset of the data packets that are delayed, dropped, or otherwise initially undelivered, and generate a radio receiver control (RRC) connection reconfiguration message for the UE, the RRC connection reconfiguration message including the configuration information.
  • RRC radio receiver control
  • Example 30 is the apparatus of any of Examples 28-29, where the one or more baseband processors are further designed to perform active queue
  • Example 31 is the apparatus of any of Examples 28-29, where the one or more baseband processors are further designed to direct the subset of the data packets for transmission through the second DRB at a higher priority and lower latency than the initial transmission of the data packets through the first DRB.
  • Example 32 is the apparatus of any of Examples 28-29, where the one or more baseband processors are further designed to design the second DRB to communicate retransmitted data packets for one or more additional QoS data flows.
  • Example 33 is the apparatus of any of Examples 28-29, where the one or more baseband processors are further designed to design a third DRB to
  • Example 34 is an apparatus for a radio access network (RAN) node.
  • the node includes a memory interface to store, in a memory device, a timing interval and a target queue delay for data packets in a queue of a transmit buffer of the RAN node to be sent to a user equipment (UE).
  • the node includes one or more baseband processors to determine a queue delay of the queue for the timing interval, compare the queue delay to the target queue delay, and when the queue delay is greater than the target queue delay, determine a dynamic receiver window advertisement (DRWA) value for a transmission control protocol (TCP) connection based on the queue delay.
  • DRWA dynamic receiver window advertisement
  • Example 35 is the apparatus of Example 34, where the one or more baseband processors are further designed to generate a RAN node-assisted DRWA message to begin a DRWA procedure, the message including the DRWA value to transmit to the UE to use the DRWA value for a receiver window advertisement (RWA) for the TCP connection.
  • RWA receiver window advertisement
  • Example 36 is the apparatus of Example 35, where the one or more baseband processors are further designed to compare a queue delay after the first DRWA value is determined to the target queue delay and if the queue delay is less than the target queue delay, generate a second RAN node-assisted DRWA message to end the DRWA procedure.
  • Example 37 is the apparatus of Example 35, where the DRWA value is a first DRWA value and the one or more baseband processors are further designed to compare a queue delay after the first DRWA value is determined to the target queue delay, andif the queue delay is greater than the target queue delay, determine a second DRWA value for a TCP connection based on the queue delay after the first DRWA value is determined, and generate a RAN node-assisted DRWA message including the second DRWA value to transmit to the UE the second DRWA value for the RWA for the TCP connection.
  • Example 38 is the apparatus of any of Examples 34-37, where the one or more baseband processors are further designed to generate a TCP
  • acknowledgement message on behalf of the UE including the DRWA value for a receiver window advertisement (RWA) for the TCP connection.
  • RWA receiver window advertisement
  • RWA recommended receiver window advertisement
  • RWA recommended receiver window advertisement
  • RWA recommended receiver window advertisement
  • Example 42 is a method for a radio access network (RAN) node.
  • the method includes determining a queue delay of the queue for the timing interval, and comparing the queue delay to a target queue delay for data packets in a queue of a transmit buffer of the RAN node to be sent to a user equipment (UE).
  • the method includes when the queue delay is greater than the target queue delay, determining a dynamic receiver window advertisement (DRWA) value for a transmission control protocol (TCP) connection based on the queue delay.
  • DRWA dynamic receiver window advertisement
  • TCP transmission control protocol
  • Example 43 is the method of Example 42, further including generating a RAN node-assisted DRWA message to begin a DRWA procedure, the message including the DRWA value to transmit to the UE to use the DRWA value for a receiver window advertisement (RWA) for the TCP connection.
  • RWA receiver window advertisement
  • Example 44 is the method of Example 43, further including comparing a queue delay after the first DRWA value is determined to the target queue delay and if the queue delay is less than the target queue delay, generate a second RAN node- assisted DRWA message to end the DRWA procedure.
  • Example 45 is the method of Example 43, where the DRWA value is a first DRWA value and the method further includes comparing the queue delay after the first DRWA value is determined to the target queue delay, if the queue delay is greater than the target queue delay, determining a second DRWA value for a TCP connection based on the queue delay after the first DRWA value is determined, and generating a RAN node-assisted DRWA message including the second DRWA value to transmit to the UE the second DRWA value for the RWA for the TCP connection.
  • Example 46 is the method of any of Examples 42-45, further including generating a TCP acknowledgement message on behalf of the UE including the DRWA value for a receiver window advertisement (RWA) for the TCP connection.
  • RWA receiver window advertisement
  • RWA recommended receiver window advertisement
  • RWA recommended receiver window advertisement
  • RWA recommended receiver window advertisement
  • Example 50 is an apparatus for the RAN node, the apparatus including a means for performing the method of any of Examples 42-48.
  • Example 51 is a computer-readable storage medium having instructions stored thereon that, when executed by a processor of the RAN node, cause the processor to perform the method of any of Examples 42-49.
  • Example 52 is an apparatus for a user equipment (UE).
  • the apparatus includes a memory interface to store a radio access network (RAN) node assisted dynamic receiver window advertisement (DRWA) message to begin a DRWA procedure, the message including a DRWA value for a transmission control protocol (TCP) connection, and a local window advertisement value.
  • RAN radio access network
  • DRWA node assisted dynamic receiver window advertisement
  • the apparatus includes one or more baseband processors designed to process the RAN node-assisted DRWA message to identify the DRWA value.
  • the apparatus includes compare the DRWA value with the local window advertisement value, and if the DRWA value is less than the local window advertisement value, implement the DRWA value for a corresponding TCP connection.
  • Example 53 is the apparatus of Example 52, where the RAN node- assisted DRWA message includes a first RAN node-assisted DRWA message, and the one or more baseband processors are further designed to process a second RAN node-assisted DRWA message, the message including an indication to end the DRWA procedure and halt the DRWA procedure based on the indicated to end the DRWA procedure.
  • the RAN node- assisted DRWA message includes a first RAN node-assisted DRWA message
  • the one or more baseband processors are further designed to process a second RAN node-assisted DRWA message, the message including an indication to end the DRWA procedure and halt the DRWA procedure based on the indicated to end the DRWA procedure.
  • Example 54 is the apparatus of Example 52, where the RAN node- assisted DRWA message includes a first RAN node-assisted DRWA message, and the one or more baseband processors are further designed to process a second RAN node-assisted DRWA message, the message including an updated DRWA value to implement for the corresponding TCP connection.
  • Example 55 is an method for a user equipment (UE).
  • the apparatus includes processing a radio access network (RAN) node-assisted DRWA message to identify a DRWA value for a transmission control protocol (TCP) connection and begin a DRWA procedure.
  • the apparatus includes comparing the DRWA value with a local window advertisement value, and if the DRWA value is less than the local window advertisement value, implementing the DRWA value for a corresponding TCP connection.
  • RAN radio access network
  • TCP transmission control protocol
  • Example 56 is the method of Example 55, where the RAN node-assisted DRWA message includes a first RAN node-assisted DRWA message, and the method further includes processing a second RAN node-assisted DRWA message, the message including an indication to end the DRWA procedure and halt the DRWA procedure based on the indicated to end the DRWA procedure.
  • Example 57 is the method of Example 55, where the RAN node-assisted DRWA message includes a first RAN node-assisted DRWA message, and the method further includes processing a second RAN node-assisted DRWA message, the message including an updated DRWA value to implement for the corresponding TCP connection.
  • Example 58 is an apparatus for the UE, the apparatus includes a means for performing the method of any one of Examples 55-57.
  • Example 59 is a computer-readable storage medium having instructions stored thereon that, when executed by a processor of the UE, cause the processor to perform the method of any of Examples 55-57.
  • a computing device may include a processor such as a microprocessor, microcontroller, logic circuitry, or the like.
  • the computing device may include a computer-readable storage device such as non-volatile memory, static random access memory (RAM), dynamic RAM, read-only memory (ROM), disk, tape, magnetic, optical, flash memory, or other computer-readable storage medium.
  • a component or module 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 components that provide the described functionality.
  • ASIC application specific integrated circuit
  • processor shared, dedicated, or group
  • memory shared, dedicated or group
  • a software module or component may include any type of computer instruction or computer executable code located within or on a non-transitory computer-readable storage medium.
  • a software module or component may, for instance, comprise one or more physical or logical blocks of computer instructions, which may be organized as a routine, program, object, component, data structure, etc., which performs one or more tasks or implements particular abstract data types.
  • a particular software module or component may comprise disparate instructions stored in different locations of a computer-readable storage medium, which together implement the described functionality of the module or component.
  • a module or component may comprise a single instruction or many instructions, and may be distributed over several different code segments, among different programs, and across several computer-readable storage media.

Landscapes

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

Abstract

L'invention concerne un système comprenant un équipement utilisateur (UE) et un nœud de réseau d'accès radio (RAN), le nœud RAN ayant un processeur configuré pour établir une première porteuse radio de données (DRB) pour communiquer des paquets de données à l'UE selon un flux de données de qualité de service (QoS) et déterminer que le premier DRB est incapable de fournir, au moins temporairement, le flux de données de QoS sur la base d'un sous-ensemble des paquets de données qui sont abandonnés ou autrement initialement non délivrés à l'UE. En réponse à la détermination que le premier DRB est incapable de fournir le flux de données de QoS, le processeur est configuré pour établir une seconde DRB pour communiquer avec l'UE, et diriger des transmissions initiales des paquets de données par l'intermédiaire de la première DRB et du sous-ensemble des paquets de données qui sont abandonnés ou autrement initialement non délivrés par le biais de la seconde DRB.
PCT/US2017/036767 2016-10-14 2017-06-09 Systèmes, procédés et dispositifs de protocole de commande de transmission de liaison descendante dans des réseaux cellulaires WO2018071064A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662408375P 2016-10-14 2016-10-14
US62/408,375 2016-10-14

Publications (1)

Publication Number Publication Date
WO2018071064A1 true WO2018071064A1 (fr) 2018-04-19

Family

ID=59091617

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/036767 WO2018071064A1 (fr) 2016-10-14 2017-06-09 Systèmes, procédés et dispositifs de protocole de commande de transmission de liaison descendante dans des réseaux cellulaires

Country Status (1)

Country Link
WO (1) WO2018071064A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2559840A (en) * 2016-12-12 2018-08-22 Samsung Electronics Co Ltd Improvements in and relating to QoS flow mobility
US20180270697A1 (en) * 2017-03-15 2018-09-20 Nokia Technologies Oy Buffer status reporting and new quality of service flows on default bearer in next generation radio access networks
CN113791901A (zh) * 2021-08-31 2021-12-14 上海弘积信息科技有限公司 一种高效的负载均衡设备tcp重传实现方法
US12004004B2 (en) 2016-12-12 2024-06-04 Samsung Electronics Co., Ltd. Apparatus and method for controlling data flow in wireless communication system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020071407A1 (en) * 2000-07-08 2002-06-13 Samsung Electronics Co., Ltd. HARQ method in a CDMA mobile communication system
US20160094466A1 (en) * 2013-05-31 2016-03-31 Telefonaktiebolaget L M Ericsson (Publ) Network node for controlling transport of data in a wireless communication network
WO2016068316A1 (fr) * 2014-10-31 2016-05-06 日本電気株式会社 Station de base sans fil, dispositif d'émission de paquets, terminal sans fil, procédé et programme de commande

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020071407A1 (en) * 2000-07-08 2002-06-13 Samsung Electronics Co., Ltd. HARQ method in a CDMA mobile communication system
US20160094466A1 (en) * 2013-05-31 2016-03-31 Telefonaktiebolaget L M Ericsson (Publ) Network node for controlling transport of data in a wireless communication network
WO2016068316A1 (fr) * 2014-10-31 2016-05-06 日本電気株式会社 Station de base sans fil, dispositif d'émission de paquets, terminal sans fil, procédé et programme de commande
EP3214886A1 (fr) * 2014-10-31 2017-09-06 Nec Corporation Station de base sans fil, dispositif d'émission de paquets, terminal sans fil, procédé et programme de commande

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2559840A (en) * 2016-12-12 2018-08-22 Samsung Electronics Co Ltd Improvements in and relating to QoS flow mobility
US10993138B2 (en) 2016-12-12 2021-04-27 Samsung Electronics Co., Ltd. Apparatus and method for controlling data flow in wireless communication system
GB2559840B (en) * 2016-12-12 2021-07-07 Samsung Electronics Co Ltd Improvements in and relating to QoS flow mobility
US11665579B2 (en) 2016-12-12 2023-05-30 Samsung Electronics Co., Ltd. Apparatus and method for controlling data flow in wireless communication system
US12004004B2 (en) 2016-12-12 2024-06-04 Samsung Electronics Co., Ltd. Apparatus and method for controlling data flow in wireless communication system
US20180270697A1 (en) * 2017-03-15 2018-09-20 Nokia Technologies Oy Buffer status reporting and new quality of service flows on default bearer in next generation radio access networks
US10511993B2 (en) * 2017-03-15 2019-12-17 Nokia Technologies Oy Buffer status reporting and new quality of service flows on default bearer in next generation radio access networks
CN113791901A (zh) * 2021-08-31 2021-12-14 上海弘积信息科技有限公司 一种高效的负载均衡设备tcp重传实现方法
CN113791901B (zh) * 2021-08-31 2023-12-26 上海弘积信息科技有限公司 一种高效的负载均衡设备tcp重传实现方法

Similar Documents

Publication Publication Date Title
US10530539B2 (en) Systems, devices, and methods for variable RTT in HARQ operations
US11457503B2 (en) Re-transmission of PDCP PDUS by centralized nodes of a RAN architecture
US10764822B2 (en) Systems, methods and devices for selecting a public land mobile network using coverage enhancement indicators
US11812513B2 (en) Buffer status report enhancements for TCP flow
WO2018064483A1 (fr) Appareil de gestion d'une défaillance d'une liaison radio
EP3665970A1 (fr) Augmentation de puissance d'un prach (canal physique d'accès aléatoire) et commutation dynamique de faisceau de transmissions de commande et de données
US11044626B2 (en) Systems, methods, and apparatuses for configuring measurement gap per frequency group and per cell
US11082901B2 (en) Signaling of support for network controlled small gap, NCSG, for interruption control
US10856169B2 (en) Beam measurement and reporting in cellular networks
WO2018118788A1 (fr) Rapport de combinaisons de capacités cellulaires prises en charge d'un dispositif utilisateur mobile
WO2018085723A1 (fr) Systèmes et procédés pour optimiser la notification de paramètres de capacité physique dans un réseau de télécommunication
WO2018144936A1 (fr) Attribution de ressources de liaison montante sur la base de classes de puissance d'équipement utilisateur
WO2020086514A1 (fr) Améliorations d'intervalle de mesure
WO2018071064A1 (fr) Systèmes, procédés et dispositifs de protocole de commande de transmission de liaison descendante dans des réseaux cellulaires
EP3646637A1 (fr) Gestion améliorée d'expiration de temporisateur pour csfb mt
WO2018102138A1 (fr) Reconnaissance de paquet lwip (intégration de niveau radio lte/wlan en utilisant un tunnel ipsec) à l'aide d'un en-tête gre (encapsulation de routage générique)
US20220345953A1 (en) Apparatuses for partially offloading protocol processing
WO2018031395A1 (fr) Message de liaison montante commun pour des scénarios initiés par un équipement d'utilisateur
US20220014979A1 (en) Command handling for simultaneous connectivity handoffs
WO2018031241A1 (fr) Sélection de faisceau de transmission à mobilité élevée
WO2020069032A1 (fr) Mesures de performance dans un réseau d'accès radio de génération suivante (ng-ran)

Legal Events

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

Ref document number: 17731721

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17731721

Country of ref document: EP

Kind code of ref document: A1