[go: up one dir, main page]

WO2018174887A1 - Commande de flux de tunnel - Google Patents

Commande de flux de tunnel Download PDF

Info

Publication number
WO2018174887A1
WO2018174887A1 PCT/US2017/023809 US2017023809W WO2018174887A1 WO 2018174887 A1 WO2018174887 A1 WO 2018174887A1 US 2017023809 W US2017023809 W US 2017023809W WO 2018174887 A1 WO2018174887 A1 WO 2018174887A1
Authority
WO
WIPO (PCT)
Prior art keywords
header
control information
tunnel
key
indication
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/US2017/023809
Other languages
English (en)
Inventor
Hans Thomas Hoehne
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.)
Nokia Technologies Oy
Nokia USA Inc
Original Assignee
Nokia Technologies Oy
Nokia USA Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy, Nokia USA Inc filed Critical Nokia Technologies Oy
Priority to PCT/US2017/023809 priority Critical patent/WO2018174887A1/fr
Publication of WO2018174887A1 publication Critical patent/WO2018174887A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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
    • 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/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers

Definitions

  • Tunneling can be used to encapsulate a first protocol within another protocol.
  • IP Internet Protocol
  • a packet of a first protocol can be encapsulated within an IP packet.
  • the encapsulation can be used to provide privacy, security, authentication, and/or for other reasons such as enabling the encapsulated packet to be transported in another type of network or using another type of transport protocol.
  • GRE Generic Routing Encapsulation
  • RFC-2890 describes an extension to the GRE protocol that adds a Key for authentication and a Sequence Number for ordering packets.
  • a method that includes receiving, on a wireless link, at least one packet data unit including a header, the header including an indication of whether the at least one packet data unit carries a control information or another type of information; and forwarding, in response to detecting that the indication corresponds to the control information, the at least one packet data unit including at least a portion of the control information to a control information processor.
  • the control information may include a flow control report.
  • the control information processor may schedule, based on the flow control report, data in a flow identified in the received header.
  • the other type information may include another flow control report for another tunnel.
  • the control information processor may schedule, based on the other flow control report, data in the other flow.
  • the other type of information may be user plane data.
  • the user plane traffic may be forwarding, in response to detecting that the indication corresponds to user plane data, to a higher layer for handling.
  • the tunnel may include the at least one packet data unit.
  • the tunnel may include a generic routing encapsulation tunnel.
  • the header may include a general routing encapsulation header.
  • the indication may include a predetermined key signaling that the tunnel includes control information comprising a flow control report.
  • the indication may be located in a field of the header.
  • the field may be the key field and/or the reserved bits field of a general routing encapsulation header.
  • the indication may be detected from the header of the at least one packet data unit.
  • the key may be extracted, wherein the key identifies the tunnel associated with the control information.
  • a method that includes scheduling for transmission user plane data and control information; and sending at least one packet data unit including a header, the header including an indication determined based on at least the schedule for transmission of the user plane data and the control information, the indication indicating whether the at least one packet data unit carries a control information or another type of information.
  • the indication may be configured in the header as a key.
  • the control information may include a flow control report.
  • the other type information may include another flow control report for another tunnel and/or user plane data.
  • the at least one packet data unit may provide a tunnel.
  • the tunnel may include a generic routing encapsulation tunnel.
  • the header may include a general routing encapsulation header.
  • the indication may include a predetermined key signaling that the control information comprises a flow control report.
  • the indication may be located in a field of the header.
  • the field may be the key field and/or the reserved bits field of a general routing encapsulation header.
  • FIG. 1A depicts an example of a system including a cellular base station and a user equipment 154, in accordance with some example embodiments;
  • FIG. IB depicts an example of a GRE header, in accordance with some example embodiments.
  • FIG. 2 depicts a tunnel protocol demultiplexer such as receiver 200, in accordance with some example embodiments
  • FIG. 3 depicts another example of a GRE header, in accordance with some example embodiments.
  • FIG. 4 depicts another example of a GRE receiver, in accordance with some example embodiments.
  • FIG. 5 A depicts an example of a process for tunnel flow control, in accordance with some example embodiments.
  • FIG. 5B depicts another example of a process for tunnel flow control, in accordance with some example embodiments;
  • FIG. 6 depicts another example of a GRE header, in accordance with some example embodiments.
  • FIG. 7 depicts an example of an apparatus, in accordance with some example embodiments.
  • flow control feedback may enable enhanced throughput performance by at least enabling a flow control function, such as a scheduler, to place data on different transmission channels such that out-of-order delivery of the data is reduced and/or minimized, when compared to not using flow control feedback.
  • a flow control function such as a scheduler
  • flow control feedback may be carried on a reverse link.
  • flow control feedback may be distinguished from other data including control data and user plane (UP) data carried on the reverse link.
  • UP user plane
  • tunneling such as generic routing encapsulation (GRE)
  • GRE generic routing encapsulation
  • flow control feedback for tunneling such as GRE tunneling and/or the like.
  • encoding of flow control feedback related information in the reverse channel may enable a reduction in the signaling overhead for setting up dedicated flow control feedback channels.
  • the flow's (which is being reported in a flow control report) identifier (ID) may be encoded in the header of a tunnel.
  • ID information about the tunnel or flow control
  • This encoding may enable, as noted, a reduction in flow control tunnel setup signaling.
  • GRE tunnels the examples described herein may be implemented using other types of tunnels as well.
  • FIG. 1 A depicts an example system 99 including a cellular base station 152 and a user equipment 154, in accordance with some example embodiments.
  • the base station 152 may wirelessly transmit data (which may comprise at least one flow) over one or more radio channels to the user equipment 154 via downlink(s) 156.
  • the downlink(s) 156 may carry at least one downlink user plane tunnel, such as GRE tunnel 158 having a GRE header, including a key, such as a downlink key (key DL).
  • the downlink key may identify the downlink user plane GRE tunnel 158.
  • the downlink key may be implemented in a variety of ways to identify the GRE tunnel 158.
  • the downlink key may be derived, in LTE, from a bearer ID and/or data radio bearer ID, while in 5G the downlink key may be derived from a packet data unit (PDU) session ID and/or a flow indicator identification (FII), network slice identification or a composite of thereof.
  • PDU packet data unit
  • FII flow indicator identification
  • the user equipment may provide the flow control feedback via at least one uplink tunnel such as GRE tunnel 168 carried by the uplink(s) 160.
  • the base station 152 may serve a "receiver" of one or more GRE tunnels carried in the uplink 160, some of which may carry user plane (UP) data 162 and some of which may carry a feedback control (FC) report 164 for a tunnel such as GRE tunnel 158 carried via the downlink 156.
  • UP user plane
  • FC feedback control
  • the receiver at the base station 152 may distinguish, based on the encoded keys, between a tunnel including user plane PDUs 162 and a tunnel including the FC report 164.
  • at least one tunnel header such as a GRE header may include an encoded key indicating whether the PDUs for a given tunnel are user plane traffic (which can be passed to higher layers for processing) or whether the PDUs for a given tunnel include other data such as a FC report, in which case the FC report should be forwarded to the receiver's flow control function to enable flow control feedback control such as scheduling.
  • the encoded key may include a predetermined value indicating that the PDUs for a given tunnel include a FC report.
  • the encoded key may include a predetermined value indicating that the PDU for a given tunnel are user plane traffic (which can be passed to higher layers for processing).
  • FIG. 1A depicts a single base station and a single user equipment for illustrative purpose only.
  • other base stations, WiFi access points, user equipment, and cellular network nodes may be included in system 99 and may further include access to the core cellular network, Internet, and/or the like.
  • the base station 152 may aggregate traffic download via a primary downlink link transmitted by the base station 152 and one or more secondary downlinks transmitted by the base station 152, other base stations, and/or wireless access points (e.g., WiFi wireless access points). This type of aggregation may be referred to as carrier aggregation.
  • the base station 152 may comprise several links using the same or different radio access technologies.
  • FIG. IB depicts an example of a tunnel header 100 such as a GRE header, in accordance with some example embodiments.
  • the header 100 may include one or more fields in accordance with for example RFC 2890, such as a key present field (labeled "K") indicating whether a key is present in the GRE header and so forth.
  • the GRE header 100 may further include a flow control key 102 A (labeled Key FC), a downlink key 102B labeled (key DL), and a payload 104 comprising a flow control report.
  • the downlink key 102B may identify the GRE tunnel 158 which is the subject of the FC report 104.
  • one or more (if not all of) the flow control reports may be carried on an uplink GRE tunnel 168 having a previously agreed (e.g., predetermined) flow control key, such as Key_FC 102 A.
  • This Key_FC 102A may identify the GRE tunnel 168 as carrying at least a flow control report, such as a flow control feedback report.
  • the header 100 may include the flow control key 102A and the downlink key 102B (labeled key DL) forming an aggregate key 102A-B.
  • one or more PDUs for a given GRE tunnel may include the flow control key 102A and the downlink key 102B (labeled key DL) forming the aggregate key 102A-B.
  • presence of the flow control key 102A (Key FC), in the GRE header may signal that the tunnel includes a FC report.
  • the flow control key 102A may comprise one or more bits, and these one or more bits may have a predetermined value which when detected indicates that the tunnel includes the FC report.
  • FIG. 2 depicts a receiver 200 such as a GRE receiver including a GRE receiver key field demultiplexing function 202 and a flow control function 204, in accordance with some example embodiments.
  • the receiver 200 may be located at the base station 152 in order to distinguish, based on the presence of the flow control key, Key_FC 102A, whether PDUs for a tunnel include a flow control report and, if so, the key field demultiplexer 202 can route a control information processor, such as a flow control function 204, the PDUs and the extracted downlink key 102B (which identifies the tunnel(s) in the downlink 156 that the flow control report is about).
  • a control information processor such as a flow control function 204
  • the receiver also referred to as a tunnel receiver or a GRE tunnel receiver
  • the receiver may be located at the user equipment as well to perform a similar feedback control function for the uplink user plane packets.
  • FIG. 1A depicts the base station 152 and the user equipment 154, other types of wireless radios may be used as well.
  • the base station 152 may be implemented as a wireless access point, such as a Wi-Fi base station, user equipment, an Internet of Things (IoT) sensor, and/or the like.
  • the user equipment 154 may be implemented as a wireless access point, such as a WiFi base station, another user equipment, an Internet of Things (IoT) sensor, and/or the like.
  • the receiver 200 including the key field demultiplexer 202 may detect from the header 100 carried by a PDU, the flow control key, such as Key FC 102A, which indicates that the tunnel 160 carrying the flow control key 102A includes a flow control report that needs to be forwarded to the flow control function 204.
  • the key field demultiplexer 202 may extract the downlink key (key DL 102B) identifying the downlink tunnel 158 for which the flow control report is about.
  • the key field demultiplexer 202 may provide the FC report and extracted downlink key (key DL 102B) to flow control function 204, which may enable flow control such as scheduling of PDUs on the GRE tunnel 158 carried via downlink 156.
  • a flow control report can be delivered by referring to only one of the transmission legs, such as downlink key 102B identifying the downlink tunnel 158 and by choosing a predetermined, such as previously agreed, key prefix value, such as the flow control key 102A (e.g., key_FC2).
  • a predetermined such as previously agreed, key prefix value, such as the flow control key 102A (e.g., key_FC2).
  • FIG. 3 depicts another example of a GRE header 300, in accordance with some example embodiments.
  • the header 300 may include one or more fields in accordance with RFC 2890 but further include a key uplink value 302A (labeled key UL), a key downlink value 302B (labeled key DL), and a payload 304 comprising a flow control report for the tunnel identified by key downlink 302B.
  • a key uplink value 302A label UL
  • a key downlink value 302B label downlink value
  • payload 304 comprising a flow control report for the tunnel identified by key downlink 302B.
  • any user plane tunnel on the uplink 160 may be used to carry the flow control report.
  • the GRE header key field of the tunnel (which carries the FC report) may be configured to include the key uplink value 302A (labeled key UL) and the key downlink value 302B (labeled key DL) identifies the user plane downlink tunnel the flow control report is about.
  • the key downlink value's 302B (key DL) presence in the GRE header, may signal that the tunnel includes a FC report.
  • the key downlink value may be predetermined, in accordance with some example embodiments.
  • FIG. 4 depicts a GRE receiver 400, in accordance with some example embodiments.
  • the GRE receiver 400 may receive PDUs forming a GRE tunnel, and the GRE header 300 may include the key uplink value 302A (key UL) and the key downlink value 302B (key DL).
  • the key field demultiplexer 402 may then route the PDU(s) (as they relate to FC reporting) to the flow control function 404 along with the downlink key (key DL) identifying the associated downlink tunnel the flow control report is about.
  • the key field demultiplexer detects this condition and, determines that the PDUs for that uplink tunnel do not include the flow control report. When this is the case, the key field demultiplexer 402 may then route these PDUs to a higher layer, such as a user plan function 406 alone with the identifier of the uplink tunnel (such as the uplink key, key UL).
  • a higher layer such as a user plan function 406 alone with the identifier of the uplink tunnel (such as the uplink key, key UL).
  • FIG. 5A depicts an example process 599 for tunnel flow control, in accordance with some example embodiments.
  • the process 599 may be associated with downlink transmitters 590A-B, downlink receivers 592A-B, an uplink transmitter 594, and an uplink receiver 596.
  • the downlink transmitter 590A may correspond to a transmit portion of the base station 152, and the downlink transmitter 59B to another transmit portion of base station 152. Those transmitters may be transmitted on the same radio link, or may be transmitted over different radio links. Alternatively or additionally, the transmitters may be physically separated.
  • the downlink receivers 592A and 592B may correspond to the receiver portion of the user equipment.
  • the uplink transmitter 594 may correspond to a transmit portion of the user equipment.
  • the downlink transmitter 590A may identify a downlink flow with an identifier, such as the downlink key value (e.g., key_DL4).
  • the downlink transmitter 590B may identify a downlink flow with an identifier, such as the downlink key value (e.g., key_DL3).
  • each of the downlink transmitters 590A-B may schedule data belonging to at least one downlink flow by taking into account information provided by the flow control function for the corresponding flow.
  • the downlink transmitter 590A may encapsulate the PDUs of the downlink flow to form a tunnel, such as a GRE tunnel, and configure the header, such as the GRE header, to have a key value of the downlink key value (e.g., key_DL4 to identify that tunnel).
  • the downlink transmitter 590B may encapsulate the PDUs of the downlink flow to form a tunnel, such as a GRE tunnel, and configure the header, such as the GRE header, to have a key value of the downlink key value (e.g., key_DL3 to identify that tunnel).
  • each of the downlink transmitters 590A-B may transmit via the downlink 156 PDUs including the configured headers.
  • the downlink receiver 592 A may receive the encapsulated PDUs having a header key value of key DL, such as key_DL4, and at 560B, the downlink receiver 592B may receive the encapsulated PDUs having a header key value of key DL, such as key_DL3.
  • the downlink receiver 592A may assemble one or more flow control status reports for the data flow identified by the key DL, such as key_DL4, and at 562B, the downlink receiver 592B may assemble one or more flow control status reports for the data flow identified by the key DL, such as key_DL3.
  • each of the downlink receiver 592A-B may forward user plane traffic to higher layers for additional processing.
  • the uplink transmitter 594 may schedule for transmission data including user plane data and/or the flow control report(s) for each of the downlink tunnels, such as the FC report for the downlink tunnel identified by key_DL4 transmitted by transmitter 590A and the FC report for the downlink tunnel identified by key_DL3 transmitted by transmitter 590B.
  • the uplink transmitter 594 may configure, establish, and/or set a key according to the content of the scheduled data.
  • the key may be selected as noted herein with respect to headers 100, 300, and/or 600 to allow a GRE tunnel receiver to detect whether the tunnel includes a FC report, user plane data, and/or other data.
  • the uplink transmitter 594 may encapsulate the scheduled data for transmission and then transmit the PDUs in the uplink.
  • the uplink receiver 596 may receive PDUs forming a tunnel such as a GRE tunnel associated with the key as described with respect to headers 100, 300, and/or 600, in accordance with some example embodiments.
  • a GRE tunnel receiver may process the PDU headers to detect header keys, such as a flow control key 102A, downlink key 102B/302B/601, and/or uplink key 302A.
  • the uplink receiver 596 may demultiplex, based on the header key, user plane traffic, flow control data for FC report contained in a PDU having a header key associated with key_DL3, and/or flow control data for FC report contained in a PDU having a header key associated with key_DL4.
  • the user plane traffic may be delivered, at 575A-B, to a higher layer for additional handling.
  • the flow control data for the key DL3 may be forwarded at 580 to a control information processor, such as a schedule function (see, e.g., 554B) at the downlink transmitter 590B.
  • the flow control data for the key_DL4 may be forwarded at 578 to a control information processor, such as a schedule function (see, e.g., 554A), at the downlink transmitter 590A.
  • a schedule function see, e.g., 554A
  • FIG. 5B depicts an example process 500 for tunnel flow control, in accordance with some example embodiments.
  • the process 500 may be associated with a downlink transmitter 590, a downlink receiver 592, an uplink transmitter 594, and an uplink receiver 596.
  • the downlink transmitter 590 may correspond to a transmit portion of the base station 152
  • the uplink receiver 596 may correspond to the receive portion of the base station 152.
  • the downlink receiver 592 may correspond to the receiver portion of the user equipment 154
  • the uplink transmitter 594 may correspond to the transmit portion of the user equipment 154.
  • the uplink receiver 596 may be implemented to handle headers 100, 200, and 600 using a corresponding GRE tunnel receiver.
  • association of the base station and user equipment with the downlink transmitter 590, the downlink receiver 592, the uplink transmitter 594, and the uplink receiver 596 is for illustrative purposes as other types of radios may include these transmitters and receivers.
  • the downlink transmitter 590 may identify a downlink flow with an identifier, such as the downlink key value (e.g. , key DL) 302B.
  • the downlink transmitter 590 may schedule data belonging to the downlink flow taking into account information provided by the flow control function.
  • the downlink transmitter 590 may encapsulate the PDUs of the downlink flow to form a tunnel, such as a GRE tunnel, and configure the header, such as the GRE header, to have a key value of the downlink key value (e.g., key DL) 302B.
  • the downlink transmitter 590 may transmit the PDU via the downlink 156.
  • the downlink receiver 592 may receive the encapsulated PDUs having a header key value of key_DL 302B.
  • the downlink receiver 592 may assemble one or more flow control status reports for the data flow identified by the key DL 302B.
  • the downlink receiver 592 may forward user plane traffic to higher layers for additional processing.
  • the uplink transmitter 594 may schedule for transmission the flow control report(s) determined for the downlink identified by key DL 302B.
  • the uplink transmitter 594 may also schedule for transmission user plane data for a corresponding key_UL value.
  • the uplink transmitter 594 may configure, establish, and/or set a key according to the content of the scheduled data.
  • the key may be selected as noted herein with respect to headers 100, 300, and/or 600 to allow a GRE tunnel receiver to detect whether the tunnel includes a FC report.
  • the uplink transmitter 594 may encapsulate (including the set header keys) the scheduled data for transmission and then transmit the PDUs in the uplink.
  • the uplink receiver 596 may receive PDUs forming a tunnel such as a GRE tunnel associated with the key as described with respect to headers 100, 300, and/or 600, in accordance with some example embodiments.
  • a GRE tunnel receiver may process the PDU headers to detect keys, such as a flow control key 102A, downlink key 102B/302B/601 and/or uplink key 302 A.
  • the uplink receiver 596 may demultiplex, based on the GRE header key, user plane traffic and flow control data, in accordance with some example embodiments.
  • the presence of the flow control key 102A (Key FC), in the GRE header may signal that the tunnel includes an FC report.
  • the presence of the key downlink value's 302B (key DL), in the GRE header may signal that the tunnel includes a FC report.
  • the presence of an indicator, such as a key downlink value 602 in a field of the header 600 (e.g., the reserved bits field or other field) may signal that the tunnel includes a FC report.
  • the encoding for the flow control key 102A may be predetermined in the sense that the transmitter of the PDUs and the receiver of PDUs both have to understand the encoding scheme.
  • the predetermined encoding scheme may be specified in a standard, so that the transmitter and receiver know the encoding scheme.
  • the encoding may be exchanged via signaling between the base station 152 and the user equipment 154.
  • the base station may signal to the user equipment the value for key FC, and the maximum length of any key DL, which may enable providing the examples described with respect to FIGs.
  • the encoding scheme being used may further define, indicate, or encode the length of the flow control key 102A, the length of the downlink key 102B, the function of the flow control key 102A (e.g., its role to signal the presence of the flow control report), and/or the function of the downlink key 102B (e.g., its role to identifying the tunnel(s) in the downlink that the flow control report is about).
  • the encoding may include concatenating of keys such as concatenating the downlink key (key DL) with the flow control key (e.g., key FC).
  • the concatenation may be implemented as a bit-shifting of for example the key FC by an amount of bits larger, or equal to, the length of the downlink key (e.g., key DL) and then adding the resulting number to the downlink key (key DL).
  • the length of the downlink key plus the length of the flow control key (key FC) is sized to fit the length of the hdr key field of the GRE header, for example.
  • the encoding scheme being used may further define, indicate, or encode the length of the uplink key 302 A, the length of the downlink key 302B, as well as the functions of those keys.
  • a receiver of the PDUs may detect and then demultiplex based on the presence of at least the key downlink value 302B (key DL), so that those PDUs having key DL are routed to a flow control function at 534, while other PDUs (e.g., PDUs not having the key DL but only having an hdr key as key UL) may be delivered, at 536, to the user plane at 540, in accordance with some example embodiments.
  • FIG. 6 depicts another example of a GRE header 600, in accordance with some example embodiments.
  • the header 600 may include one or more fields in accordance with RFC 2890 but further include a key downlink value 602 configured in a field, such as the reserved bits field. To identify a flow control report, the reserved bits of the GRE header may be used configured with the key downlink value 602 (Key DL 602).
  • FIG. 7 illustrates a block diagram of an apparatus 10, in accordance with some example embodiments.
  • the apparatus may be implemented as a user equipment, such as a smart phone, tablet, IoT device, and/or any other processor and memory based device including a wireless access point, a base station, and/or the like.
  • the apparatus may include the receivers and/or transmitters disclosed herein for handling the tunnels.
  • the DL receiver 592, 592A, and/or 592B as well as the UL transmitter 594 may be included in the apparatus 10.
  • one or more aspects of the apparatus 10 may be used to provide a wireless access point and/or base station.
  • the apparatus may include the DL transmitter 590, 590 A, 590B as well as the UL receiver 596.
  • the apparatus 10 may include at least one antenna 12 in communication with a transmitter 14 and a receiver 16. Alternatively transmit and receive antennas may be separate.
  • the apparatus 10 may also include a processor 20 configured to provide signals to and receive signals from the transmitter and receiver, respectively, and to control the functioning of the apparatus.
  • Processor 20 may be configured to control the functioning of the transmitter and receiver by effecting control signaling via electrical leads to the transmitter and receiver.
  • processor 20 may be configured to control other elements of apparatus 10 by effecting control signaling via electrical leads connecting processor 20 to the other elements, such as a display or a memory.
  • the processor 20 may, for example, be embodied in a variety of ways including circuitry, at least one processing core, one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits (for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and/or the like), or some combination thereof. Accordingly, although illustrated in FIG. 7 as a single processor, in some example embodiments the processor 20 may comprise a plurality of processors or processing cores.
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • Signals sent and received by the processor 20 may include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireline or wireless networking techniques, comprising but not limited to Wi-Fi, wireless local access network (WLAN) techniques, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, ADSL, DOCSIS, and/or the like.
  • these signals may include speech data, user generated data, user requested data, and/or the like.
  • the apparatus 10 may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like.
  • the apparatus 10 and/or a cellular modem therein may be capable of operating in accordance with various first generation (1G) communication protocols, second generation (2G or 2.5G) communication protocols, third-generation (3G) communication protocols, fourth- generation (4G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (for example, session initiation protocol (SIP) and/or the like.
  • IMS Internet Protocol Multimedia Subsystem
  • the apparatus 10 may be capable of operating in accordance with 2G wireless communication protocols IS-136, Time Division Multiple Access TDMA, Global System for Mobile communications, GSM, IS-95, Code Division Multiple Access, CDMA, and/or the like.
  • the apparatus 10 may be capable of operating in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and/or the like. Further, for example, the apparatus 10 may be capable of operating in accordance with 3G wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), and/or the like. The apparatus 10 may be additionally capable of operating in accordance with 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and/or the like. Additionally, for example, the apparatus 10 may be capable of operating in accordance with 4G wireless communication protocols, such as LTE Advanced, 5G, and/or the like as well as similar wireless communication protocols that may be subsequently developed.
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data GSM Environment
  • the processor 20 may include circuitry for implementing audio/video and logic functions of apparatus 10.
  • the processor 20 may comprise a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and/or the like. Control and signal processing functions of the apparatus 10 may be allocated between these devices according to their respective capabilities.
  • the processor 20 may additionally comprise an intemal voice coder (VC) 20a, an internal data modem (DM) 20b, and/or the like.
  • the processor 20 may include functionality to operate one or more software programs, which may be stored in memory. In general, processor 20 and stored software instructions may be configured to cause apparatus 10 to perform actions.
  • processor 20 may be capable of operating a connectivity program, such as a web browser.
  • the connectivity program may allow the apparatus 10 to transmit and receive web content, such as location-based content, according to a protocol, such as wireless application protocol, WAP, hypertext transfer protocol, HTTP, and/or the like.
  • Apparatus 10 may also comprise a user interface including, for example, an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, a user input interface, and/or the like, which may be operationally coupled to the processor 20.
  • the display 28 may, as noted above, include a touch sensitive display, where a user may touch and/or gesture to make selections, enter values, and/or the like.
  • the processor 20 may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as the speaker 24, the ringer 22, the microphone 26, the display 28, and/or the like.
  • the processor 20 and/or user interface circuitry comprising the processor 20 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions, for example, software and/or firmware, stored on a memory accessible to the processor 20, for example, volatile memory 40, non-volatile memory 42, and/or the like.
  • the apparatus 10 may include a battery for powering various circuits related to the mobile terminal, for example, a circuit to provide mechanical vibration as a detectable output.
  • the user input interface may comprise devices allowing the apparatus 20 to receive data, such as a keypad 30 (which can be a virtual keyboard presented on display 28 or an externally coupled keyboard) and/or other input devices.
  • apparatus 10 may also include one or more mechanisms for sharing and/or obtaining data.
  • the apparatus 10 may include a short-range radio frequency (RF) transceiver and/or interrogator 64, so data may be shared with and/or obtained from electronic devices in accordance with RF techniques.
  • RF radio frequency
  • the apparatus 10 may include other short-range transceivers, such as an infrared (IR) transceiver 66, a BluetoothTM (BT) transceiver 68 operating using BluetoothTM wireless technology, a wireless universal serial bus (USB) transceiver 70, a BluetoothTM Low Energy transceiver, a ZigBee transceiver, an ANT transceiver, a cellular device-to-device transceiver, a wireless local area link transceiver, and/or any other short-range radio technology.
  • Apparatus 10 and, in particular, the short-range transceiver may be capable of transmitting data to and/or receiving data from electronic devices within the proximity of the apparatus, such as within 10 meters, for example.
  • the apparatus 10 including the Wi-Fi or wireless local area networking modem may also be capable of transmitting and/or receiving data from electronic devices according to various wireless networking techniques, including 6LoWpan, Wi-Fi, Wi-Fi low power, WLAN techniques such as IEEE 802.11 techniques, IEEE 802.15 techniques, IEEE 802.16 techniques, and/or the like.
  • the apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, and/or the like, which may store information elements related to a mobile subscriber.
  • SIM subscriber identity module
  • R-UIM removable user identity module
  • eUICC embedded user identity module
  • UICC universal integrated circuit card
  • the apparatus 10 may include volatile memory 40 and/or non-volatile memory 42.
  • volatile memory 40 may include Random Access Memory (RAM) including dynamic and/or static RAM, on-chip or off-chip cache memory, and/or the like.
  • RAM Random Access Memory
  • Non-volatile memory 42 which may be embedded and/or removable, may include, for example, read-only memory, flash memory, magnetic storage devices, for example, hard disks, floppy disk drives, magnetic tape, optical disc drives and/or media, non-volatile random access memory (NVRAM), and/or the like.
  • NVRAM non-volatile random access memory
  • non-volatile memory 42 may include a cache area for temporary storage of data. At least part of the volatile and/or non-volatile memory may be embedded in processor 20.
  • the memories may store one or more software programs, instructions, pieces of information, data, and/or the like which may be used by the apparatus for performing operations disclosed herein.
  • the memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying apparatus 10.
  • the memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying apparatus 10.
  • the processor 20 may be configured using computer code stored at memory 40 and/or 42 to control and/or provide one or more aspects disclosed herein (see, for example, process 500 and 599).
  • Some of the embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic.
  • the software, application logic, and/or hardware may reside on memory 40, the control apparatus 20, or electronic components, for example.
  • the application logic, software or an instruction set is maintained on any one of various conventional computer- readable media.
  • a "computer-readable medium" may be any non-transitory media that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry, with examples depicted at FIG. 7, computer-readable medium may comprise a non-transitory computer-readable storage medium that may be any media that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
  • a technical effect of one or more of the example embodiments disclosed herein is encoding the FC report information in a key field reducing the need to for dedicated signaling for setting up a FC channel to carry the FC report.
  • the base stations and user equipment (or one or more components therein) and/or the processes described herein can be implemented using one or more of the following: a processor executing program code, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an embedded processor, a field programmable gate array (FPGA), and/or combinations thereof.
  • ASIC application-specific integrated circuit
  • DSP digital signal processor
  • FPGA field programmable gate array
  • These various implementations may include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.
  • These computer programs also known as programs, software, software applications, applications, components, program code, or code
  • computer-readable medium refers to any computer program product, machine-readable medium, computer-readable storage medium, apparatus and/or device (for example, magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions.
  • PLDs Programmable Logic Devices
  • systems are also described herein that may include a processor and a memory coupled to the processor.
  • the memory may include one or more programs that cause the processor to perform one or more of the operations described herein.

Landscapes

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

Abstract

La présente invention concerne des procédés et un appareil, notamment des produits programmes d'ordinateur, pour une commande de flux. Dans certains modes de réalisation donnés à titre d'exemple, l'invention concerne un procédé qui consiste à recevoir, sur une liaison sans fil, au moins une unité de données par paquets comprenant un en-tête, l'en-tête comprenant une indication précisant si la ou les unités de données par paquets transportent des informations de commande ou un autre type d'informations; et acheminer, en réponse à la détection que l'indication correspond aux informations de commande, la ou les unités de données par paquets comprenant au moins une partie des informations de commande à un processeur d'informations de commande. La présente invention se rapporte également à des systèmes, des procédés et des articles de fabrication associés.
PCT/US2017/023809 2017-03-23 2017-03-23 Commande de flux de tunnel Ceased WO2018174887A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2017/023809 WO2018174887A1 (fr) 2017-03-23 2017-03-23 Commande de flux de tunnel

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2017/023809 WO2018174887A1 (fr) 2017-03-23 2017-03-23 Commande de flux de tunnel

Publications (1)

Publication Number Publication Date
WO2018174887A1 true WO2018174887A1 (fr) 2018-09-27

Family

ID=58547812

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/023809 Ceased WO2018174887A1 (fr) 2017-03-23 2017-03-23 Commande de flux de tunnel

Country Status (1)

Country Link
WO (1) WO2018174887A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11510059B2 (en) * 2017-09-29 2022-11-22 Huawei Technologies Co., Ltd. Data security processing method and apparatus
US20220377819A1 (en) * 2019-07-03 2022-11-24 Zte Corporation Method and apparatus for establishing data transmission link and computer-readable storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060164985A1 (en) * 2005-01-27 2006-07-27 Samsung Electronics Co., Ltd. Apparatus and method for enhanced flow control in a wireless network
US20090161545A1 (en) * 2007-12-21 2009-06-25 Qualcomm Incorporated Downlink flow control
US20120147750A1 (en) * 2009-08-25 2012-06-14 Telefonaktiebolaget L M Ericsson (Publ) Using the ECN Mechanism to Signal Congestion Directly to the Base Station
US20140254358A1 (en) * 2004-04-01 2014-09-11 Apple Inc. Method for Providing Bearer Specific Information for Wireless Networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140254358A1 (en) * 2004-04-01 2014-09-11 Apple Inc. Method for Providing Bearer Specific Information for Wireless Networks
US20060164985A1 (en) * 2005-01-27 2006-07-27 Samsung Electronics Co., Ltd. Apparatus and method for enhanced flow control in a wireless network
US20090161545A1 (en) * 2007-12-21 2009-06-25 Qualcomm Incorporated Downlink flow control
US20120147750A1 (en) * 2009-08-25 2012-06-14 Telefonaktiebolaget L M Ericsson (Publ) Using the ECN Mechanism to Signal Congestion Directly to the Base Station

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11510059B2 (en) * 2017-09-29 2022-11-22 Huawei Technologies Co., Ltd. Data security processing method and apparatus
US20220377819A1 (en) * 2019-07-03 2022-11-24 Zte Corporation Method and apparatus for establishing data transmission link and computer-readable storage medium
US12089270B2 (en) * 2019-07-03 2024-09-10 Zte Corporation Method and apparatus for establishing data transmission link and computer-readable storage medium

Similar Documents

Publication Publication Date Title
US11917472B2 (en) Facilitating quality of service flow remapping utilizing a service data adaptation protocol layer
CN111183672B (zh) 无线通信中的报头格式
CN113038528B (zh) 用于在无线通信系统中将数据分组路由到用户设备的基站
US20180077605A1 (en) Methods and apparatus for formatting a protocol data unit for wireless communication
KR20190129191A (ko) 차세대 이동 통신 시스템에서 주변 셀의 기준 신호로 준지속적 사운딩 기준 신호를 지시하는 방법 및 장치
US12309649B2 (en) User equipment (UE) mobility history information management
US11690022B2 (en) Managing transmit power control
CN111049626A (zh) 无线通信的方法和装置
CN116491166A (zh) 通信配置的方法和通信装置
EP3257317B1 (fr) Planification de liaison montante avec une agrégation de réseau local sans fil (wlan)/de projet de partenariat de troisième génération (3gpp)
GB2506389A (en) Information Elements in a paging message to indicate a changed system information relating to local area connectivity
US20230036243A1 (en) Systems and methods for responding to a maximum permissible exposure condition
CN114930887B (zh) 一种密钥管理方法、通信装置
CN115136536A (zh) 多时隙传输块配置
WO2017076454A1 (fr) Initiation d'une mesure, d'un rapport et/ou d'une utilisation d'un retard de chemin secondaire pour attribuer des paquets ou supports parmi un chemin primaire et un chemin secondaire dans un réseau sans fil
WO2018174887A1 (fr) Commande de flux de tunnel
US20240430667A1 (en) User plane integrity protection (up ip) capability signaling in 5g/4g systems
EP3216180A1 (fr) Amélioration de l'efficacité des communications
US20240154908A1 (en) Delay Reporting For Network Segments In An End-To-End Communication Path
US12301462B2 (en) Managing end-to-end quality of service (QoS) in a multi-network communication path
WO2023000177A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la communication
WO2018227478A1 (fr) Amélioration sps prenant en compte la granularité d'intervalles au niveau symbole
EP4576871A1 (fr) Procédé de communication et appareil de communication
EP4557805A1 (fr) Procédé et dispositif permettant d'effectuer une fonction de réseau d'accès sans fil à l'aide d'une mise à l'échelle dynamique
WO2017162273A1 (fr) Amélioration de l'efficacité de communication indiquant la longueur de deux en-têtes dans la pdu

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: 17717559

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: 17717559

Country of ref document: EP

Kind code of ref document: A1