methods and apparatus to allow rate adaptation through network settings

专利摘要:
METHODS AND EQUIPMENT TO ALLOW RATE ADAPTATION THROUGH NETWORK SETTINGS. Systems and methods for implementing explicit congestion notification (ECN) across distinct networks, configurations, and protocols are described. Local rate adaptation using ECN can be provided without resorting to other operators to upgrade or ensure that their networks are transparent to ECN or ECN capable.
公开号:BR112012007131B1
申请号:R112012007131-9
申请日:2010-09-30
公开日:2021-05-18
发明作者:Nikolai Konrad Nepomucceno Leung；Arungundram Chandrasekaran Mahendran
申请人:Qualcomm Incorporated；
IPC主号:

专利说明:

Reference to Related Orders
[001] This application claims priority to US Provisional Patent Application Serial No. 61/247 095, entitled METHODS FOR ENABLING RATE ADAPTATION THROUGH VARIOUS NETWORK CONFIGURATIONS, filed September 30, 2009, the contents of which are hereby incorporated in its entirety by way of reference for all purposes. Field of Invention
[002] This application relates generally to wireless communication systems. More specifically, but not exclusively, the application refers to methods and an apparatus for providing explicit congestion notification (ECN) functionality across distinct networks, configurations and/or protocols. Description of Prior Art
[003] Wireless communication systems are widely used to provide various types of communication content, such as voice, data and the like, and provisions are likely to increase with the introduction of new data-oriented systems, such as data-driven systems. Long Term Evolution (LTE). Wireless communication systems can be multiple access systems capable of supporting communication with multiple users by sharing available system resources (bandwidth and transmission power, for example). Examples of such multiple access systems include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Long Term Evolution systems (LTE) 3GPP and other Orthogonal Frequency Division Multiple Access (OFDMA) systems.
[004] Generally, a wireless multiple access communication system can simultaneously support communication to multiple wireless terminals (also known as user equipment (UEs) or access terminals (ATs)). Each terminal communicates with one or more base stations (also known as access points (APs), eNodesBs, or eNBs) through transmissions on the forward and reverse links. The forward link (also referred to as the downlink or DL) refers to the communication link from the base stations to the terminals, and the reverse link (also referred to as the uplink or UL) refers to the communication link from the terminals to the terminals. base stations. These communication links can be established using a single-in, single-out, single-in and multiple-out, multiple-in and single-out, or a multiple-in, multiple-out (MIMO) system.
[005] A MIMO system uses multiple (NT) transmit antennas and multiple (NR) receive antennas for data transmission. A MIMO channel formed by the NT transmit antennas and the NR receive antennas can be decomposed into NS independent channels, which are also referred to as spatial channels. Generally, each of the independent NS channels corresponds to a dimension. The MIMO system can show improved performance (greater transmission capacity and/or greater security, for example) if the additional dimensions created by the various transmit and receive antennas are used. A MIMO system also supports time division duplex (TDD) and frequency division duplex (FDD) systems. In a TDD system, transmissions on the forward and reverse links are in the same frequency region so that the principle of reciprocity allows estimation of the forward link channel from the reverse link channel. This allows an access point to extract transmit beamforming gain on the forward link when multiple antennas are available at the access point.
[006] Base station nodes, sometimes referred to as eNBs, have different capabilities for use in a network. This includes transmission power classes, access restriction and so on. In one respect, heterogeneous network characteristics create wireless coverage dead spots (cover hole, for example). This can cause marked intercellular interference, which requires an undesirable association between user equipment cells. In general, heterogeneous network characteristics require deep penetration of physical channels, which can cause unwanted interference between nodes and equipment in the respective network.
[007] Explicit Congestion Notification (ECN) is an extension of the Internet Protocol (IP) and the Transmission Control Protocol (TCP) and is defined in RFC 3168 (2001). ECN allows end-to-end notification of network congestion by dropping packets, and is an optional feature that is only used when both endpoints support it and want to use it. ECN is only effective when supported by the underlying network. Traditionally, TCP/IP networks signal congestion by dropping packets. However, when the ECN is successfully negotiated, an ECN-aware router can mark the IP header instead of dropping a packet in order to signal impending congestion. The receiver of the packet echoes the congestion indication to the sender, who must react as if a packet were dropped. Some outdated or faulty networking equipment may drop packets with ECN bits set instead of ignoring the bits.
[008] The ECN functionality can be used to perform end-to-end rate adaptation between equipment or user devices (UEs) in a wireless network. However, if the transport network does not properly support the ECN, the terminals will have to disable the ECN and the UEs will not be able to perform rate adaptation. Even if the operator ensures that their network supports ECN properly, they cannot guarantee that another operator will do the same for their network. Consequently, it cannot be guaranteed that calls between UEs in different carrier networks will support rate adaptation using ECN.
[009] One solution is to require all operators' networks and UEs to support ECN. One problem with this approach is that it requires significant work for operators to ensure that their networks are transparent to ECN and not all operators are interested in this feature. Another solution is to have UEs constantly probe the transport path in order to determine if it is transparent to the ECN. If not, UEs disable ECN and the rate adaptation function. Therefore, this does not ensure ECN/rate adaptation for all calls and has the added complexity burden of requiring UEs to constantly probe and monitor the transport path. Invention Summary
[0010] This disclosure relates generally to wireless communication systems and the management and mitigation of congestion using ECN and rate reduction functionality across various networks.
[0011] In one respect, disclosure refers to a method for providing communications. The method may include receiving, at an interworking gateway coupled between a first network and a second network, a first set of media generated at a first data rate, wherein the first set of media includes an indication of network congestion generated within of the first network, and providing, in response to the indication, a data rate adjustment request to request a lower data rate from a first user equipment (UE) in the first network.
[0012] The method may also include receiving, at the interworking gateway, a second set of media sent from the first UE at a second data rate in response to the data rate adjustment request and sending, from the interworking gateway to the second network , the second set of media. The first media set and the second media set may be generated by the first UE in the first network for transmission to a second UE in the second network. The second set of media can be modified so as to remove the ECN marking on the first network. Submission may include uploading modified media. The congestion indication may include an explicit congestion indication-found (ECN-CE) tag or other tag, indication, or bit setting compatible with an ECN protocol. The method may also include modifying the first set of media so as to remove the ECN-CE marking and may also include sending the first modified set of media to the second network.
[0013] The first network may be an ECN capable network and the second network node may be a non ECN capable network. The data rate adjustment request may comprise a Temporary Maximum Media Stream Bit Rate Request (TMMBR) or Codec Mode Request (CMR). The first network and the second network can be wireless communications networks. One or more of the first and second networks may be wired communications networks, in whole or in part.
[0014] In another aspect, disclosure refers to a method for processing media at an interworking gateway. The method may include receiving, at the interworking gateway, which may be in communication with a first wireless network and a second wireless network, a media data packet transmitted by a UE within the first wireless network. The media data package can be marked with ECN. The method may also include processing the data packet so as to remove the ECN tag and sending the processed data packet to the second network.
[0015] In another aspect, disclosure refers to a method for providing communications. The method may include sending a first set of media, from a UE in a first network, to a UE in a second network, receiving, in response to sending a first set of media, a data rate adjustment request from a interworking gateway and sending, in response to the data rate adjustment request, a second set of media to the UE in the second network at a rate adjusted. The data rate adjustment request may comprise a TMMBR or CMR.
[0016] In another aspect, the disclosure refers to a method for providing communications in an interworking gateway. The method includes receiving, from a first UE in a first network, a data rate adjustment request, wherein the data rate adjustment request is provided from the first UE in response to receiving a congestion indication on provided media. of a second UE in a second network, and processing the data rate adjustment request so as to provide integration of ECN functionality between the first and second networks.
[0017] Processing the rate adjustment request may include issuing data rate adjustment information to the second UE if the interworking gateway determines that the second UE can support an adjusted data rate compatible with the rate adjustment request. Dice. The interworking gateway can determine that the second UE can support an adjusted data rate during a negotiation session between the interworking gateway and the second UE. Processing the rate adjustment request may include transcoding the media received from the second UE compatible with the data rate reduction request. Transcoding may include lowering the media data rate of the media received from the second UE in order to alleviate congestion in the first network.
[0018] The interworking gateway can process the media of the second network so as to make them ECN capable. For example, the media received can be marked compatible with an ECN protocol. The tag can be an ECT tag. Marked media can be provisioned to the first network, where they can be delivered to the first UE.
[0019] The disclosure also relates to computer program products, devices, apparatus and systems for implementing the above-described methods, as well as other methods and processes described herein. Several additional aspects are also described below in conjunction with the attached Drawings. Brief Description of Figures
[0020] The present application can be understood more fully in connection with the following detailed description considered in conjunction with the accompanying drawings, in which:
[0021] Figure 1 shows details of a wireless communication system.
[0022] Figure 2 shows details of a wireless communication system that has multiple cells.
[0023] Figure 3 shows connectivity details in an exemplary wireless communication system.
[0024] Figure 4 shows connectivity details in another exemplary wireless communication system.
[0025] Figure 5 shows details of interconnection between ECN capable and non ECN capable networks.
[0026] Figure 6 shows details of an embodiment of a system that includes interconnection between ECN capable and non ECN capable networks that use an interworking gateway.
[0027] Figure 7 shows details of an embodiment of a system that includes interconnection between an ECN capable network and another network that has either unknown ECN capability or that may also be ECN capable.
[0028] Figure 8 shows details of an embodiment of a subsystem to facilitate communications between a terminal or UE and an interworking gateway in an ECN capable network.
[0029] Figure 9 shows details of a modality of a terminal or UE and a base station or eNB.
[0030] Figure 10 shows details of a modality of an interworking gateway.
[0031] Figure 11 shows details of a modality of a process to facilitate transparent communications to the ECN between networks.
[0032] Figure 12 shows details of a modality of a process to facilitate transparent communications to the ECN between networks.
[0033] Figure 13 shows details of a modality of a process to facilitate transparent communications to ECN between networks.
[0034] Figure 14 shows details of a modality of a process to facilitate transparent communications to the ECN between networks. Detailed Description of the Invention
[0035] This disclosure refers generally to systems and methods for managing and mitigating congestion in wireless communication systems, which can facilitate interworking based on ECN functionality through distinct networks, configurations and/or protocols. As described herein, a network that supports ECN functionality is said to be ECN Transport Capable (ECT) and may also be described herein as being ECN capable, transparent to the ECN, and/or ECN-compliant. Similarly, a network that does not support ECN functionality may be referred to as non-compliant with the ECN or not capable or transparent to the ECN.
[0036] In one respect, disclosure refers to a method for providing communications. The method may include receiving, at an interworking gateway coupled between a first network and a second network, a first set of media generated at a first data rate, wherein the first set of media includes an indication of network congestion generated within of the first network, and providing, in response to the indication, a data rate adjustment request to request a lower data rate from a first user equipment (UE) in the first network.
[0037] The method may also include receiving, at the interworking gateway, a second set of media sent from the first UE at a second data rate in response to the data rate adjustment request, and sending from the interworking gateway to the second network, the second set of media. The first media set and the second media set may be generated by the first UE in the first network for transmission to a second UE in the second network. The second set of media can be modified so as to remove the ECN marking on the first network. Uploading may include uploading the modified media. The congestion indication may include an explicit congestion indication-found (ECN-CE) tag or other tag, indication, or bit setting compatible with an ECN protocol. The method may also include modifying the first media set so as to remove the ECN-CE marking and may also include sending the modified first media set to the second network.
[0038] The first network can be an ECN capable network and the second network node can be a non ECN capable network. The data rate adjustment request may comprise a Temporary Maximum Media Stream Bit Rate Request (TMMBR) or Codec Mode Request (CMR). The first network and the second network can be wireless communications networks. One or more of the first and second networks may be wired communications networks, in whole or in part.
[0039] In another aspect, the disclosure refers to a computer program product. The computer program product may include a computer-readable medium that has codes to cause a computer to receive a first set of generated media at a first data rate, wherein the first set of media includes an indication of network congestion. generated within the first network. The codes may also include codes to cause the computer to provide, in response to the indication, a data rate adjustment request to request a lower data rate from a first UE in a first network.
[0040] In another aspect, the disclosure refers to an interworking gateway. The interworking gateway may include a first network interface module configured to receive a first set of media generated at a first data rate from a first network, wherein the first data set includes an indication of network congestion generated within the first network, and providing, in response to the indication, a data rate adjustment request to request a lower data rate from a first UE in the first network. The first network interface module may also be configured to receive a second set of media sent from the first UE at a second data rate in response to the data rate adjustment request. The gateway may also include a second network interface module configured to send the second set of media to a second network.
[0041] The first media set and the second media set may be generated by the first UE in the first network for transmission to a second UE in the second network. The gateway may also include a processor module configured to remove the ECN marking from the second set of media in order to generate modified media. Uploading may include uploading the modified media.
[0042] The congestion indication may comprise an explicit congestion indication-encountered marking (ENC-CE). The gateway may also include a processor module configured to modify the first set of media to remove the ECN-CE marking. The gateway may also include a second network interface module configured to send the first modified media set to the second network. The first network can be an ECN capable network and the second network can be a non ECN capable network. The gateway may also include a processor module configured to generate the data rate adjustment request as a TMMBR or CMR. The first network and the second network can be wireless communications networks. The first network and/or the second network can be wired communication networks.
[0043] In another aspect, the disclosure refers to an interworking gateway. The interworking gateway may include means for receiving a first set of generated media at a first data rate, wherein the first set of media includes an indication of network congestion generated within the first network. The gateway may also include means for providing, in response to the indication, a data rate adjustment request to request a lower data rate from a first UE in the first network.
[0044] In another aspect, disclosure refers to a method for processing media at an interworking gateway. The method may include receiving, at the interworking gateway, which may be in communication with a first wireless network and a second wireless network, a media data packet transmitted by a UE within the first wireless network. The media data package can be marked with ECN. The method may also include processing the data packet to remove the ECN tag and sending the processed data packet to the second network.
[0045] In another aspect, the disclosure refers to a computer program product. The computer program product may include a computer readable medium having codes to cause a computer to receive, at the interworking gateway, which may be in communication with a first wireless network and a second wireless network, a packet of media data transmitted by a UE within the first wireless network. The media data package can be marked with ECN. The codes may also include codes to cause the computer to process the data packet to remove the ECN tag and send the processed data packet to the second network.
[0046] In another aspect, the disclosure refers to an interworking gateway. The interworking gateway can be in communication with a first wireless network and a second wireless network. The interworking gateway can be configured to receive a media data packet transmitted by a UE within the first wireless network. The media data package can be marked with ECN. The gateway can also be configured to process the data packet to remove the ECN tag and send the processed data packet to the second network.
[0047] In another aspect, the disclosure refers to an interworking gateway. The interworking gateway can be in communication with a first wireless network and a second wireless network. The interworking gateway may include means for receiving a media data packet transmitted by a UE within the first wireless network. The media data package can be marked with ECN. The gateway may also include means for processing the data packet to remove the ECN marking and means for sending the processed data packet to the second network.
[0048] In another aspect, disclosure refers to a method for providing communications. The method may include sending a first set of media, from a UE in a first network, to a UE in a second network, receiving, in response to sending a first set of media, a data rate adjustment request from a interworking gateway and sending, in response to the data rate adjustment request, a second set of media to the UE in the second network at a rate adjusted. The data rate adjustment request may comprise a TMMBR or CMR.
[0049] In another aspect, the disclosure refers to a computer program product. The computer program product may include a computer-readable medium that has codes to cause a computer to receive, in response to sending a first set of media, a data rate adjustment request from an interworking gateway and send , in response to the data rate adjustment request, a second set of media to the UE in the second network at a rate adjusted. The data rate adjustment request may comprise a TMMBR or CMR.
[0050] In another aspect, disclosure refers to a communication device. The communication device may include a transmitter module configured to send a first set of media to a UE in a second network and a receiver module configured to receive, in response to sending a first set of media, a request for adjustment of data rate of an interworking gateway. The transmitter module may also be configured to send, in response to the data rate adjustment request, a second set of media to the UE in the second network at an adjusted rate. The communication device can be a terminal or UE.
[0051] In another aspect, disclosure refers to a communication device. The communication device may include means for sending a first set of media to a UE in a second network, means for receiving, in response to sending a first set of media, a data rate adjustment request from an interworking gateway and means for sending, in response to the data rate adjustment request, a second set of media to the UE in the second network at a rate adjusted.
[0052] In another aspect, the disclosure refers to a method for providing communications in an interworking gateway. The method may include receiving, from a first UE in a first network, a data rate adjustment request, wherein the data rate adjustment request is provided from the first UE in response to receiving a media congestion indication. provided with a second UE in a second network, and processing the rate adjustment request so as to provide integration of ECN functionality between the first and second networks.
[0053] Processing the rate adjustment request may include issuing data rate adjustment information to the second UE if the interworking gateway determines that the second UE can support an adjusted data rate compatible with the rate adjustment request. Dice. The interworking gateway can determine that the second UE can support an adjusted data rate during a negotiation session between the interworking gateway and the second UE. Processing the rate adjustment request may include transcoding the media received from the second UE compatible with the data rate reduction request. Transcoding may include lowering the media data rate of the media received from the second UE in order to alleviate congestion in the first network.
[0054] In another aspect, disclosure refers to a method for providing communications. The method may include receiving, at an interworking gateway coupled between a first network and a second network, a first set of media generated at a first data rate, wherein the first set of media includes an indication of network congestion generated within of the first network, and providing, in response to the indication, a data rate adjustment request to request a lower data rate from a first user equipment (UE) in the first network.
[0055] The method may also include receiving, at the interworking gateway, a second set of media sent from the first UE at a second data rate in response to the data rate adjustment request and sending, from the interworking gateway to the second network , the second set of media. The first media set and the second media set may be generated by the first UE in the first network for transmission to a second UE in the second network. The second set of media can be modified so as to remove the ECN marking on the first network. Submission may include sending modified media. The congestion indication may include an explicit congestion indication-found (ECN-CE) tag or other tag, indication, or bit setting compatible with an ECN protocol. The method may also include modifying the first set of media so as to remove the ECN-CE marking and may also include sending the first modified set of media to the second network.
[0056] The first network can be an ECN capable network and the second network node can be a non ECN capable network. The data rate adjustment request can comprise TMMBR or CMR. The first network and the second network can be wireless communications networks. One or more of the first and second networks may be wired communications networks, in whole or in part.
[0057] In another aspect, the disclosure refers to a computer program product. The computer program product may include a computer-readable medium that has codes to cause a computer to receive a first set of generated media at a first data rate, wherein the first set of media includes an indication of network congestion. generated within the first network. The codes may also include codes to cause the computer to provide, in response to the indication, a data rate adjustment request to request a lower data rate from a first UE in a first network.
[0058] In another aspect, the disclosure refers to an interworking gateway. The interworking gateway may include a first network interface module configured to receive a first set of media generated at a first data rate from a first network, wherein the first data set includes an indication of network congestion generated within the first network, and providing, in response to the indication, a data rate adjustment request to request a lower data rate from a first UE in the first network. The first network interface module may also be configured to receive a second set of media sent from the first UE at a second data rate in response to the data rate adjustment request. The gateway may also include a second network interface module configured to send the second set of media to a second network.
[0059] The first media set and the second media set can be generated by the first UE in the first network for transmission to a second UE in the second network. The gateway may also include a processor module configured to remove the ECN marking from the second set of media in order to generate modified media. Uploading may include uploading the modified media.
[0060] The congestion indication may comprise an explicit congestion indication-found congestion (ENC-CE) marking. The gateway may also include a processor module configured to modify the first set of media to remove the ECN-CE marking. The gateway may also include a second network interface module configured to send the first modified media set to the second network. The first network can be an ECN capable network and the second network can be a non ECN capable network. The gateway may also include a processor module configured to generate the data rate adjustment request as a TMMBR or CMR. The first network and the second network can be wireless communications networks. The first network and/or the second network can be wired communication networks.
[0061] In another aspect, the disclosure refers to an interworking gateway. The interworking gateway may include means for receiving a first set of generated media at a first data rate, wherein the first set of media includes an indication of network congestion generated within the first network. The gateway may also include means for providing, in response to the indication, a data rate adjustment request to request a lower data rate from a first UE in the first network.
[0062] In another aspect, disclosure refers to a method for processing media at an interworking gateway. The method may include receiving, at the interworking gateway, which may be in communication with a first wireless network and a second wireless network, a media data packet transmitted by a UE within the first wireless network. The media data package can be marked with ECN. The method may also include processing the data packet to remove the ECN tag and sending the processed data packet to the second network.
[0063] In another aspect, the disclosure refers to a computer program product. The computer program product may include a computer readable medium having codes to cause a computer to receive, at the interworking gateway, which may be in communication with a first wireless network and a second wireless network, a packet of media data transmitted by a UE within the first wireless network. The media data package can be marked with ECN. The codes may also include codes to cause the computer to process the data packet to remove the ECN tag and send the processed data packet to the second network.
[0064] In another aspect, the disclosure refers to an interworking gateway. The interworking gateway can be in communication with a first wireless network and a second wireless network. The interworking gateway can be configured to receive a media data packet transmitted by a UE within the first wireless network. The media data package can be marked with ECN. The gateway can also be configured to process the data packet to remove the ECN tag and send the processed data packet to the second network.
[0065] In another aspect, the disclosure refers to an interworking gateway. The interworking gateway can be in communication with a first wireless network and a second wireless network. The interworking gateway may include means for receiving a media data packet transmitted by a UE within the first wireless network. The media data package can be marked with ECN. The gateway may also include means for processing the data packet to remove the ECN marking and means for sending the processed data packet to the second network.
[0066] In another aspect, disclosure refers to a method for providing communications. The method may include sending a first set of media, from a UE in a first network, to a UE in a second network, receiving, in response to sending a first set of media, a data rate adjustment request from a interworking gateway and sending, in response to the data rate adjustment request, a second set of media to the UE in the second network at a rate adjusted. The data rate adjustment request may comprise a TMMBR or CMR.
[0067] In another aspect, the disclosure refers to a computer program product. The computer program product may include a computer-readable medium that has codes to cause a computer to receive, in response to sending a first set of media, a data rate adjustment request from an interworking gateway and send , in response to the data rate adjustment request, a second set of media to the UE in the second network at a rate adjusted. The data rate adjustment request may comprise a TMMBR or CMR.
[0068] In another aspect, disclosure refers to a communication device. The communication device may include a transmitter module configured to send a first set of media to a UE in a second network and a receiver module configured to receive, in response to sending a first set of media, a request for adjustment of data rate of an interworking gateway. The transmitter module may also be configured to send, in response to the data rate adjustment request, a second set of media to the UE in the second network at an adjusted rate. The communication device can be a terminal or UE.
[0069] In another aspect, disclosure refers to a communication device. The communication device may include means for sending a first set of media to a UE in a second network, means for receiving, in response to sending a first set of media, a data rate adjustment request from an interworking gateway and means for sending, in response to the data rate adjustment request, a second set of media to the UE in the second network at a rate adjusted.
[0070] In another aspect, the disclosure refers to a method for providing communications in an interworking gateway. The method may include receiving, from a first UE in a first network, a data rate adjustment request, wherein the data rate adjustment request is provided from the first UE in response to receiving a media congestion indication. provided with a second UE in a second network, and processing the rate adjustment request so as to provide integration of ECN functionality between the first and second networks.
[0071] Processing the rate adjustment request may include issuing data rate adjustment information to the second UE if the interworking gateway determines that the second UE can support an adjusted data rate compatible with the rate adjustment request. Dice. The interworking gateway can determine that the second UE can support an adjusted data rate during a negotiation session between the interworking gateway and the second UE. Processing the rate adjustment request may include transcoding the media received from the second UE compatible with the data rate reduction request. Transcoding may include lowering the media data rate of the media received from the second UE in order to alleviate congestion in the first network.
[0072] In another aspect, the disclosure refers to a computer program product. The computer program product may include a computer readable medium having codes to cause a computer to receive a data rate adjustment request, wherein the data rate adjustment request is provided by a first UE in response. receiving a media congestion indication provided by a second UE in a second network, and processing the data rate adjustment request so as to provide integration of ECN functionality between the first and second networks.
[0073] In another aspect, the disclosure refers to an interworking gateway. The interworking gateway may include a first network interface module configured to receive, from a first UE in a first network, a data rate adjustment request, wherein the data rate adjustment request is provided by the first UE in response to receiving a media congestion indication provided by a second UE in a second network, and a processor module configured to process the data rate adjustment request so as to provide integration of ECN functionality between the first and second networks.
[0074] The processor module may be configured to issue data rate adjustment information to the second UE if the interworking gateway determines that the second UE can support an adjusted data rate compatible with the data rate adjustment request . The gateway may also include a second network interface module, wherein the processor module is configured to determine whether the second UE can support an adjusted data rate during a negotiation session between the interworking gateway and the second UE via the second network interface module. The processor module can be configured to transcode media received from the second UE compatible with the data rate reduction request. Transcoding can be performed by lowering the media data rate of the media received from the second UE in order to alleviate congestion in the first network.
[0075] In another aspect, the disclosure refers to an interworking gateway. The gateway includes means for receiving, from a first UE in a first network, a data rate adjustment request, wherein the data rate adjustment request is provided by the first UE in response to receiving a congestion indication in media provided with a second UE in a second network, and means for processing the data rate adjustment request so as to provide integration of ECN functionality between the first and second networks.
[0076] In another aspect, the disclosure refers to a computer program product. The product may include a computer readable medium having codes to cause a computer to receive a data rate adjustment request, wherein the data rate adjustment request is provided by a first UE in response to the receipt of a media congestion indication provided by a second UE in a second network and process the rate adjustment request so as to provide integration of ECN functionality between the first and second networks.
[0077] In another aspect, the disclosure refers to an interworking gateway. The gateway may include a first network interface module configured to receive, from a first UE in a first network, a data rate adjustment request, wherein the data rate adjustment request is provided by the first UE in response. receiving a media congestion indication provided by a second UE in a second network, and a processor module configured to process the rate adjustment request so as to provide integration of ECN functionality between the first and second networks.
[0078] The processor module can be configured to output data rate adjustment information to the second UE if the interworking gateway determines that the second UE can support an adjusted data rate compatible with the data rate adjustment request . The gateway may also include a second network interface module, wherein the processor module is configured to determine whether the second UE can support an adjusted data rate during a negotiation session between the interworking gateway and the second UE via the second network interface module. The processor module can be configured to transcode media received from the second UE compatible with the data rate reduction request. Transcoding can be performed by lowering the media data rate of the media received from the second UE in order to alleviate congestion in the first network.
[0079] In another aspect, the disclosure refers to an interworking gateway. The gateway includes means for receiving, from a first UE in a first network, a data rate adjustment request, wherein the data rate adjustment request is provided by the first UE in response to receiving a congestion indication in media provided with a second UE in a second network, and means for processing the data rate adjustment request so as to provide integration of ECN functionality between the first and second networks.
[0080] The interworking gateway can process the media of the second network so as to make them ECN capable. For example, received media can be marked compatible with an ECN protocol. The tag can be an ECT tag. Marked media can be provisioned to the first network, where it can be delivered to the first UE.
[0081] Several additional aspects are also described below in conjunction with the attached drawings.
[0082] In various embodiments, the techniques and apparatus described herein can be used for interconnection between wireless communications networks, such as Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks ), Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single Carrier FDMA (SC-FDMA) networks, LTE networks, as well as other communications networks. As described herein, the terms "networks" and "systems" may be used interchangeably. In addition, the techniques and apparatus described herein can be used for interconnecting between wired and wireless communications networks, as well as for interconnecting between wired communications networks.
[0083] A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access ("UTRA"), cdma2000 and the like. UTRA includes Broadband CDMA (W-CDMA) and Low Chip Rate (LCR). cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network can implement a radio technology such as the Global System for Mobile Communications (GSM).
[0084] An OFDMA network can implement a radio technology such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDM and the like. UTRA, E-UTRA and GSM are part of the Universal Mobile Telecommunications System (UMTS). In particular, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents from an organization called the “3rd Generation Partnership Project” (3GPP), and cdma2000 is described in documents from an organization called the “Project for 3rd Generation Partnerships 2” (3GPP2). These various radio technologies and standards are known or are being developed in the art. The 3rd Generation Partnerships Project (3GPP) is a collaboration between groups of telecommunication associations that aims to define a globally applicable third generation (3G) mobile phone specification. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP can define specifications for the next generation of mobile networks, mobile systems and mobile devices. For clarity, certain aspects of apparatus and techniques are described below for LTE implementations, and LTE terminology is used throughout much of the following description; however, the description is not intended to be limited to LTE applications. Accordingly, it will be apparent to those skilled in the art that the apparatus and methods described herein can be applied to a variety of other communication systems and applications.
[0085] The logical channels in wireless communication systems can be classified into Control Channels and Traffic Channels. Logical Control Channels comprise a Broadcast Control Channel (BCCH), which is a downlink (DL) channel for broadcasting system control information, and a Multicast Control Channel (MCCH), which is a channel Point-to-multipoint DL used to transmit Multimedia Broadcast and Multicast Services (MBMS) scheduling and control information to one or multiple MTCHs. Generally, after establishing a Radio Resource Control (RRC) connection, this channel is only used by UEs that receive MBMS. A Dedicated Control Channel (DCCH) is a bidirectional point-to-point channel that transmits dedicated control information and is used by UEs that have an RRC connection.
[0086] Logical Traffic Channels may include a Dedicated Traffic Channel (DTCH), which is a point-to-point bidirectional channel, dedicated to a UE, for the transfer of user information, and a Multicast Traffic Channel ( MTCH) for Point-to-Multipoint DL channel to transmit traffic data.
[0087] Transport Channels can be classified into Downlink (DL) and Uplink (UL) Transport Channels. DL Transport Channels comprise a Broadcast Channel (BCH), a Downlink Shared Data Channel (DL-SDCH) and an Alert Channel (PCH). The PCH can be used to support energy saving in UEs (when a DRX cycle is indicated to the UE by the network), transmitted across an entire cell and mapped to physical layer resources (PHY) that can be used for other channels of control/traffic. UL Transport Channels may include a Random Access Channel (RACH), a Request Channel (REQCH), an Uplink Shared Data Channel (UL-SDCH), and a series of PHY channels. PHY channels can include a set of DL channels and UL channels.
[0088] In addition, PHY DL channels may include the following:
PHY UL channels may include the following:


[0089] The word "exemplary" is used herein to mean "which serves as an example, occurrence or illustration". Any aspect and/or embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous compared to other features and/or embodiments.
[0090] For the purpose of explaining various aspects and/or modalities, the following terminology and abbreviations may be used here:



[0091] A MIMO system uses multiple (NT) transmit antennas and multiple (NR) receive antennas for data transmission. A MIMO channel formed by the NT transmit antennas and the NR receive antennas can be decomposed into NS independent channels, which are also referred to as spatial channels. The maximum NS spatial multiplexing, if a linear receiver is used, is min(NT, NR), with each of the NS independent channels corresponding to a dimension. A MIMO system can show improved performance (greater transmission capacity and/or greater security, for example) if the additional dimensions created by the various transmit and receive antennas are used. The spatial dimension can be described can be described in terms of a classification.
[0092] MIMO systems support implementations of time division duplex (TDD) and frequency division duplex (FDD). In a TDD system, transmissions on the forward and reverse links use the same frequency region, so that the principle of reciprocity allows the estimation of the forward link channel from the reverse link channel. This allows the access point to extract transmit beamforming gain on the forward link when multiple antennas are available at the access point.
[0093] System designs can support various time-frequency reference signals for downlink and uplink to facilitate beamforming and other functions. A reference signal is a signal generated based on known data and may also be referred to as pilot, preamble, training signal, sound signal and the like. A reference signal can be used by a receiver for various purposes, such as channel estimation, coherent demodulation, signal quality measurement, signal strength measurement, and the like. MIMO systems using multiple antennas generally provide coordination of the sending of reference signals between antennas, but LTE systems generally do not provide coordination of the sending of reference signals from multiple base stations or eNBs.
[0094] The 3GPP specification 36211-900 defines in Section 5.5 specific reference signals for modulation, associated with PUSCH or PUCCH transmission, as well as resonance, which is not associated with PUSCH or PUCCH transmission. For example, Table 1 lists some reference signals for LTE implementations that can be transmitted downlink and uplink and presents a short description of each reference signal. A cell-specific reference signal may also be referred to as a dedicated reference signal. TABLE 1

[0095] In some implementations, a system can use time division duplexing (TDD). For TDD, downlink and uplink share the same frequency spectrum or channel, and downlink and uplink transmissions are sent in the same frequency spectrum. The response to the downlink channel can thus be correlated with the response to the uplink channel. A principle of reciprocity may allow estimation of a downlink channel based on transmissions sent over the uplink. These uplink transmissions can be reference signals or uplink control channels (which can be used as reference symbols after demodulation. Uplink transmissions can allow the estimation of a selective channel in space by means of several antennas .
[0096] In LTE implementations, orthogonal frequency division multiplexing is used in the downlink - that is, from the base station, access point or eNodeB to the terminal or UE. The use satisfies LTE's requirement for spectral flexibility and allows for inexpensive solutions for very wide carriers with high peak rates and is a well-established technology, OFDM, for example, being used in standards such as IEEE 802.11a/g., 802.16, HIPERLAN-2, DVB and DAB.
[0097] Physical frequency resource blocks (also denoted here as resource blocks or "RBs" for brevity") can be defined in OFDM systems as groups of transport carriers (subcarriers, for example) or intervals that are assigned to transport data. RBs are defined over a period of time and frequency. Resource blocks are made up of time-frequency resource elements (also denoted here as resource elements or “REs” for brevity), which can be defined by time and frequency indices in a partition. Additional details of LTE RBs and REs are described in 3GPP TS 36.211.
[0098] LTE UMTS supports scalable carrier bandwidths from 20 MHz to 1.4 MHz. In LTE, an RB is defined as 12 sub-carriers when the sub-carrier bandwidth is 15 kHz or 24 sub -carriers when the carrier bandwidth is 7.5 kHz. In an exemplary implementation, in the time domain a radio frame is defined that is 10 msec in length and consists of 10 subframes of 1 msec each. Each subframe consists of 2 partitions, where each partition is 0.5 msec. The spacing between sub-carriers in the frequency domain is 15 kHz. +Twelve of these sub-carriers together (per partition) constitute one RB, so that, in this implementation, a resource block is 180 kHz. 6 resource blocks fit on a 1.4 MHz carrier and 100 resource blocks fit on a 20 MHz carrier.
[0099] On the downlink, there are typically several physical channels, as described above. In particular, PDCCH is used for sending control, PHICH for sending ACK/NACK, PCFICH for specifying the number of control symbols, Physical Downlink Shared Channel (PDSCH) for data transmission, Physical Multicast Channel (PMCH) for broadcast transmission using a Single Frequency Network and Physical Broadcast Channel (PBCH) to send important system information within a cell. Modulation formats supported in PDSCH in LTE are QPSK, 16QAM and 64QAM.
[00100] On the uplink, there are typically three physical channels. Although Physical Random Access Channel (PRACH) is only used for initial access and when the UE is not uplink synchronized, data is sent on Physical Uplink Shared Channel (PUSCH). If there is no data to be transmitted on the uplink for a UE, control information will be transmitted on the Physical Uplink Control Channel (PUCCH). Modulation formats supported on the uplink data channel are QPSK, 16QAM and 64QAM
[00101] If virtual MIMO/Spatial Division Multiple Access (SDMA) is introduced, the data rate in the uplink direction can be increased according to the number of antennas in the base station. With this technology, more than one mobile can reuse the same resources. For MIMO operation, a distinction is made between single-user MIMO, to improve the data transmission capability of one user, and multi-user MIMO, to improve the cellular transmission capability.
[00102] In 3GPP LTE, a station or mobile device may be referred to as “user device” or “user equipment” (UE). A base station can be referred to as an evolved NodeB or eNB. A semi-autonomous base station may be referred to as a native eNB or HeNB. A HeNB can thus be an example of an eNB. The HeNB and/or the HeNB coverage area may be referred to as a femto-cell, HeNB cell or Closed Subscriber Group (CSG) cell (where access is restricted).
[00103] Several other aspects and features of the disclosure are also described below. It should be evident that the present teachings may be embodied in a wide variety of forms and that any structure, function, or both, which are here disclosed, is merely representative. Based on the present teachings, those skilled in the art should understand that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus can be implemented or a method can be put into practice using any number of the aspects presented herein. Furthermore, such apparatus may be implemented or such method may be put into practice using another structure, functionality, or structure and functionality in addition to or other than one or more of the aspects presented herein. Furthermore, an aspect may comprise at least one element of a claim.
[00104] Systems and methods are described to facilitate the processing and management of explicit congestion notification (ECN) through different networks, configurations and protocols. The present systems and methods can be used to provide local rate adaptation using the ECN functionality, which can be done without the need to rely on other operators to update and/or ensure that their networks are transparent to ECN or supported or capable of ECN.
[00105] In one respect, an operator planning to use ECN for rate adaptation makes at least its own supported network support ECN. A gateway function between the operator's network and other networks, which may be wired or wireless and may be controlled by other operators, can act as an ECN endpoint in case the other networks involved in a call do not support ECN, or in whole or in part. The gateway function can be implemented in an interworking gateway device as described herein, or it can be incorporated into other elements of a network, as in components that comprise a core network. In some implementations, the other network may include two or more distinct networks, each of which may be controlled by separate carriers.
[00106] In one respect, the following methods can be used to provide gateway functionality. In an exemplary implementation, a gateway first negotiates the use of ECN between itself and a LAN UE if a far-end UE or related far-end network involved in the call does not support ECN. The gateway can then receive ECN "congestion experience" information from the local UE to adapt its uplink transmission. The local UE can then adapt the rate at which it provided media in response to the rate request, such as, for example, lowering the output data rate.
[00107] In some cases, the gateway may receive rate adaptation requests from the local UE and relay this information to a far-end UE associated with a different network without ECN support to adapt its rate. Request retransmission may involve local UE rate request translation (such as Temporary Maximum Media Stream Bit Request, TMMBR, Real-Time Transport Control Protocol (RTCP-APP), CMR and the like ) in a rate request that the far-end UE can understand. Alternatively or in addition, if the gateway does not relay the rate adaptation information to the far-end UE (or UEs), the gateway can perform media transcoding of the far-end UE to match the rate requested by the local UE. In this way, the ECN can be supported in the network associated with a given UE and still allow communication with related networks and UEs that do not support the ECN functionality.
[00108] Reference is now made to Figure 1, which shows details of an implementation of a multi-access wireless communication system, which may be part of an LTE system or other communication system in which the ECN and ECN functionality rate adaptation described here is implemented. An evolved Node B (eNB) 100 (also known as an access point or AP) may include multiple antenna groups, one including 104 and 106, another including 108 and 110, and an additional group including 112 and 114. In Figure 1, only two antennas are shown for each antenna group, however more or fewer antennas can be used for each antenna group. A user equipment (UE) 116 (also known as an access terminal or AT) is in communication with antennas 112 and 114, wherein antennas 112 and 114 transmit information to the UE 116 over the forward link (also known as the link downlink) 120 and receive information from the UE 116 over the reverse link (also known as the uplink) 118. A second UE 122 is in communication with the antennas 106 and 108, wherein the antennas 106 and 108 transmit information to the UE 122 over the from forward link 126 and receive information from access terminal 122 over reverse link 124. UEs 116 and 122, as well as others (not shown), may be configured to implement ECN functionality, as described herein.
[00109] In a frequency division duplex (FDD) system, the communication links 118, 120, 124 and 126 can use different frequencies for communication. For example, forward link 120 may use a different frequency than that used by reverse link 118. In a time division duplex (TDD) system, downlink and uplink can be shared.
[00110] Each group of antennas and/or the area in which they are designed to communicate is often referred to as the eNB sector. The antenna groups are each designed to communicate with UEs in a sector of the access areas covered by the eNB 100. In communication over direct links 120 and 126, the transmission antennas of the eNB 400 use beamforming of in order to improve the signal-to-noise ratio of the forward links to the different access terminals 116 and 124. Furthermore, an eNB that uses beamforming to transmit to UEs randomly spread across its coverage causes less interference in the UEs in neighboring cells than an eNB that transmits through a single antenna to all its UEs. An eNB may be a fixed station used to communicate with the UEs and may also be referred to as an access point, Node B or some other equivalent terminology. A UE may also be called an access terminal, AT, user equipment, wireless communication device, terminal or some other equivalent terminology.
[00111] Figure 2 shows details of an implementation of a multiple access wireless communication system 200, such as an LTE system, in which the ECN and rate adaptation functionality described here can be implemented. Multiple access wireless communication system 200 may include multiple cells, including cells 202, 204, and 206. In one aspect, system 200, cells 202, 204, and 206 may include an eNB that includes multiple sectors. The various sectors can be formed by groups of antennas, with each antenna responsible for communicating with UEs in one part of the cell. In cell 202, for example, antenna groups 212, 214, and 216 may each correspond to a different sector. In cell 204, antenna groups 218, 220, and 222 each correspond to a different sector. In cell 206, antenna groups 224, 226, and 228 each correspond to a different sector. Cells 202, 204 and 206 can include various wireless communication devices, such as user equipment or UEs, which can be in communication with one or more sectors of each cell 202, 204 or 206. UEs 230 and 232 can be in communication with eNB 242, UEs 234 and 236 can be in communication with eNB 244 and UEs 238 and 240 can be in communication with eNB 246. Cells and related base stations can be coupled to a system controller 250, which may be part of a backhaul or backhaul network, such as may be used to perform functions, as also described herein, relating to subframe partition allocation and configuration.
[00112] In many implementations, congestion processing and mitigation using ECN and rate adaptation functionality can be done in conjunction with other nodes and/or a core or backhaul network, which can facilitate interconnection between networks. Figure 3 shows details of an exemplary network modality 300 of interconnecting ENBs with other eNBs, exemplary network components, and a backhaul network. Network 300 may include a macro-eNB 302 and/or several additional eNBs, which may be picocellular eNBs 310 or other eNBs such as femtocellular eNBs or other base stations. Network 300 may include a HeNB 334 gateway for scalability reasons. The macro-eNB 302 and the gateway 334 can each communicate with a combination 340 of mobility management entities (MMEs) 342 and/or a combination of 344 server gateways (SGW) 346. The eNB gateway 334 can appear as a relay in plane C and plane U for dedicated 336 connections. An S1 connection 336 can be a logical interface specified as the boundary between an Evolved Packet Core (EPC) and an Evolved Universal Terrestrial Access Network (EUTRAN) . As such, it provides an interface to a core network (not shown explicitly in Figure 3) that can also be coupled to other networks and through which the ECN and rate adaptation functionality described here can be performed. The eNB Gateway 334 can act as a macro-eNB 302 from an EPC point of view. The interface in plane C can be S1-MME and the interface in plane U can be S1-U. Network 300 may include a macro eNB 302 and a number of additional eNBs, which may be other macro-eNBs, pico-cellular eNBs 310, femto-cellular eNBs, and/or other base stations or network nodes.
[00113] The eNB 334 gateway can act towards an eNB 310 as a single EPC node. The eNB gateway 334 can ensure S1-flex connectivity to one eNB 310. The eNB gateway 334 can provide a 1:n relay functionality so that a single eNB 310 can communicate with n MMEs 342. The eNB gateway 334 registers with combination 340 of MMEs 342 when put into operation through an S1 establishment procedure. The eNB gateway 334 can support the establishment of S1 336 interfaces with the eNBs 310.
[00114] The network 300 may also include a self-organizing network server (SON) 338. The SON server 338 may provide automated optimization of a 3GPP LTE network. The SON server 338 can be a key driver to improve the administration and keep up and running (OAM) functions in the wireless communication system 300. To facilitate this, an X2 link 320 can exist between the macro-eNB 302 and the gateway of eNB 334. X2 links 320 may also exist between each of the eNBs 310 connected to a common eNB 334 gateway. X2 links 320 can be established based on an entry from the SON server 338. An X2 link 320 can transmit ICIC information. If an X2 link 320 cannot be established, the S1 link 336 can be used to transmit ICIC information. UEs 304 can be serviced by eNB 302, and UEs 314 can be serviced by eNB 310. All nodes shown in Figure 1, as well as others (not shown) can come under the control of a first operator. Alternatively or in addition, other UEs and/or eNBs (not shown) may also be included and may have UEs connected. UEs 304, 314 and/or others (not shown) may be in communication with other eNBs or other network apparatus in separate or different networks (for remote network nodes or second network nodes, for example) which are controlled by second networks carriers or additional carriers.
[00115] According to an aspect, UEs associated with a first carrier may communicate with UEs associated with a second carrier using ECN functionality and/or other rate adaptation functionality described herein. Figure 4 shows another example of a network mode 400 of interconnecting eNBs with other eNBs and a return or basic transport network (not shown), which may be associated with the first carrier. In network 400, no SON server is included, and macro-eNBs, such as the eNB 402, can communicate with other eNBs, such as the pico-eNB 410 (and/or with other base stations or network nodes that do not They are shown). According to an aspect, UEs associated with a first carrier may communicate with UEs associated with a second carrier using ECN functionality and/or other functionality described herein.
[00116] Reference is now made to Figure 5, which shows details of a communication system 500. System 500 includes at least one network 530, which is configured to support ECN or conform to or be ECN capable, or not. whole or in part. As noted earlier, a network that supports ECN functionality is said to be ECN Transport Capable (ECT) and can be described herein as being ECN capable or ECN compliant. Likewise, a network that does not support ECN functionality may be referred to as non-ECN compliant or ECN not capable. In general, a non-ECN capable network is a network in which one or more network components do not support ECN functionality, so connections to endpoints or UEs in the network do not support ECN functionality.
[00117] The 530 and 550 networks can be operated by different operators, and in this case information about the capabilities of one network may not be known or available to the other. For example, network 530 may not know whether or not network 550 is ECN capable or not. Likewise, the 550 network may be aware of the capabilities of the 530 network.
[00118] As shown in Figure 5 by way of example, network 550 may be not ECN capable, while network 530 may be ECN capable. The 530 network may be controlled by a first operator, such as AT&T, while the 550 network may be controlled by a second, different operator, such as Verizon. A logical boundary 565 may exist in system 500 between the ECN capable and non-ECN capable sides shown in Figure 5. In many configurations, the non-ECN capable side may include network 550, as well as, in some cases, additional networks (not shown) as well as a transport infrastructure 560, which may include components such as switches, routers, cabling, wireless connection, and the like. Connectivity between networks 530 and 550 may include signaling transmission, which may consist, in an exemplary case, of Internet Protocol (IP) packets, between networks 530 and 550, as well as their respective terminals or UEs 510 and 570 , which can be routed using various infrastructure mechanisms.
[00119] In the example shown in Figure 5, the UEs 510 and 570 can have a connection or established link 580, which can be routed through the various components shown (as well as others not shown for clarity). For example, data or media, which may correspond to the digitized voice for transmission over IP (VOIP), may be sent via the communication link 581 between the UE 510 and a base station 512, which may be an eNB, as shown earlier in Figures 1-4. Data can then be sent from base station 512 to core network components 532 via connection 582, which can be configured, for example, as shown in Figure 3 or 4. Data can then be processed through core network components 532 and be provided through connections 583, 584, and 585 to core network components 554 of network 550, which, as noted earlier, may not be ECN capable.
[00120] Data can then be sent from core network components 554 to one or more base stations 552 of the second network 550, and can be transmitted wirelessly, via connection 587, to a terminal or UE 570. In some In implementations, the connection 587 to the UE 570 may be a wired connection rather than a wireless connection.
[00121] In implementations where the ECN is used, in order to ensure the proper functioning of the ECN, the operator shall ensure that its core network elements and transport routers are transparent to the ECN. This is necessary for the ECN rate adaptation functionality to work properly across the operator's entire network. In particular, transparency to ECN requires the transport network element/router not to drop tagged packets (ie, ECT or ECN-CE tagged packets) unless there is congestion that requires such drop; do not reset the ECN bits of ECN-CE tagged packets; and do not change the ECN bits of ECT-tagged packets unless there is a congestion experience.
[00122] While the operator can generally ensure that its network elements and routers are transparent to the ECN as the operator configures and controls its own network, the UEs associated with the first operator, such as the terminal or UE 510, can make calls to terminals in networks of other operators, such as, for example, UE 570.
[00123] When the second operator's network (the 550 network, for example) is not configured for and/or does not present transparency to ECN, the first operator cannot guarantee that the 510 and 550 terminals are able to establish ECN rate adaptation end-to-end. In this case, for example, packets may be dropped and/or other ECN functionality may also be impaired or non-functional. For example, if the first operator were to use ECN capable UEs, such as the UE 510, but did not ensure that their network elements were transparent to the ECN, then the operation of the ECN would be unreliable. Furthermore, unreliable operation may also derive from specific limitations of a second carrier's network components, such as network components 550, such as, for example, basic elements 554, as well as others (not shown). For example, packets that are ECN marked by intermediate nodes in the first network and/or by other nodes in element 560, for example, such as CE or ECT marked, may be discarded or otherwise processed incorrectly or have the indications removed by us on the network capable of ECN 550.
[00124] One way to potentially determine the capacity of a network is to use polling. For example, ECT probing is described in 3GPP S4-09060 and 3GPP S4-070314, which are incorporated herein by reference. When ECN polling is performed, UEs can disable the ECN when they determine that the transport is not transparent to the ECN. In particular, this requires the operator to ensure that the basic network elements of the Gateway Proxy (GW Proxy) and the Gateway Server (GW Server), as well as the transport path routers, are transparent for the ECN's operation.
[00125] As an example, at the start of an RTP session, when the first packets with ECT are sent, it can be useful to check that IP packets with ECN field values of ECT or ECN-CE will reach their destination(s). ). There is some risk that using ECN will result in either resetting the ECN field or losing all packages with ECT or ECN-CE markings. If the path between sender and receiver exhibits one or the other of these behaviors, it may be desirable to stop using ECN in order to protect both the network and the application.
[00126] Consequently, this can introduce procedures that UEs must perform in an attempt to probe and monitor the transport route in order to try to determine if this will occur, which can lead to inefficiency or other problems, such as excessive consumption of energy, congestion and the like. Specifically, A) UEs can poll the transport path in order to determine if it is an ECT (ECN capable transport) before “turning on” the ECN; B) UEs can monitor the transport path to determine if a change in the routing path has caused a problematic router to enter the transport path, making it non-ECT; and C) If an ECT failure is detected, then the UE can turn the ECN off again. The UE then tries again further polling in order to determine if the path has become an ECT once more.
[00127] These procedures can cause complexity in the UE by requiring probing, monitoring, backoff and/or retries (as described above and as discussed, for example, in 3GPP S4-090607, which is hereby incorporated by reference). Security raises questions about how a simple packet loss, or even worse, a burst of packet loss on the wireless link will affect the security of the probe and ECT failure detection. Aggressive probing (such as tagging many packets with ECT, where ECT is used as the tag to indicate capable of ECN, as also described hereinafter) can provide more robust detection of ECT, but increases the probability of clipping of media if the transport is non-ECT. In addition, incorrect detection of non-ECT because of packet losses can cause ECN to be disabled unnecessarily, thus disabling rate adaptation. This can result in “ECN state swing” between ECT and non-ECT. The delay in the case of transport probe for ECN support requires balancing the need to send enough probes in order to quickly and reliably detect the transport behavior with the simultaneous reduction to a minimum of the number of probes, since each one of these media port probes that can be discarded if the transport is non-ECT. Exemplary recommendations call for at least two probes to be sent per default Real-Time Transport Control Protocol (RTCP) reporting interval and for the sender to wait until at least 4 probes have been sent before evaluating the ECN Feedback message in order to determine if the transport is ECN capable.
[00128] Sending the minimum number of probes implies that the channel poll must be done through at least 1-2 regular RTCP intervals. This means that, in such a situation, the ECN is initialized after sending broadcast media for more than at least one RTCP reporting period. This can slow down the “rate adaptation mechanism” that amount of time. This problem cannot be solved by simply slowing down the codec mode rise rate in the MTSI Initial Codec Mode procedures, as this would unnecessarily deteriorate the initial voice quality for all VoIP calls over an extended period of time, or simply increasing the number of ECY-tagged packets during the poll to speed up reaction time, as this increases the risk of media clipping.
[00129] It is possible to have an eNB tag the probe packets with ECN-CE to indicate congestion on the way before ECN initialization. However, since the number of probe packets is small, the media sender receiving an indication of the small number of ECN-CE-marked packets at the receiver may not be able to reliably react to such feedback. For example, some 3GPP specifications state that the media sender must treat the receipt of ECN-CE marked packets from the media receiver as if it were reacting to packet loss. However, a media sender would not be expected to significantly reduce its rate in response to some packet loss.
[00130] For RTCP bandwidth, for feedback of received ECN data to the media sender, several specifications resort to sending an ECN (or RTCP XR) message back, indicating which received media packets are tagged with ECT or CE or discarded. These specifications also recommend that the receiver send this ECN message under the following conditions: ASAP (immediate or initial AVPF mode) upon detection of an ECN-CE tagged or dropped packet and included in every regular composite RTCP packet that will be transmitted. The amount of data that is reported and the frequency of reporting can be important.
[00131] When included in a composite RTCP packet, the ECN message is required to report the condition of received packets over the last 3 RTCP reporting periods. By some calculations, this can be up to 750 VoIP packages that are reported on. For each of these packets, the ECN message would indicate whether the packet has been dropped, marked with ENC-CE or ECT, which requires at least 2 bits for each of the packets that are reported. There can be a reduction in message size by using lossless compression. However, typical compression ratios will have to be estimated based on the variation in the state of the received packets (how often packet losses are detected at the receiver, for example).
[00132] When an ECN message is triggered by a packet loss or receipt of a packet marked with ECN-CE, it does not have to be reported in such a large packet arrival window. However, it is still recommended to include an RR or SR, which will increase the total RTCP packet size even when reduced size RTCP packets are sent. The combination of message size and reporting frequency would increase the RTCP reporting bandwidth for VoIP. This adds a significant amount of signaling overhead compared to the rate adaptation solution used in UMTS Circuit Switched voice calls in which signaling occurs at most once when it is necessary to change the codec mode. Also, if the RTCP bandwidth is kept small via the RR and RS SDP attributes, then the need to constantly send back the ECN message may not be met (ie increase reporting delay) other AVPF messages when eNB decides to mark all media packs during periods of congestion or usage time.
[00133] In summary, the complexity and problems described above in implementing ECN functionality between ECN capable and non ECN capable networks suggest other approaches to facilitate communications across networks, such as through networks controlled by different carriers.
[00134] Figure 6 shows details of an embodiment of a communication system 600 in which aspects can be implemented. In this example, system 600 includes at least a first network 630, which is configured to support ECN or conform to or be ECN capable, as well as one or more additional networks 650, which are not ECN capable, or at all or in part. The 630 and 650 networks may be operated by different operators, in which case information about the capabilities of one network may not be available or accessible to the other. For example, network 630 may not know whether or not network 650 is or is not ECN capable. Likewise, the 650 network may not be aware of the compliance or non-compliance of the 630 network.
[00135] As in the example shown in Figure 5, the 630 network can be controlled by a first operator, such as AT&T, while the 650 network can be controlled by a different second network, such as, for example, Verizon. Likewise, a logical boundary 665 may exist in system 600 between ECN-compliant and non-ECN-compliant sides. In various configurations, the non-ECN compliant side may include the 650 network, as well as, in some cases, additional networks or network elements (not shown), and the 660 transport infrastructure, such as switches, routers, cabling, wireless connection and the like. Likewise, connectivity between networks 630 and 650 may include signaling transmission, which may consist, in an exemplary case, of Internet Protocol (IP) packets between networks 630 and 650, as well as their respective terminals. or UEs 610 and 670, which can be routed using various infrastructure mechanisms.
[00136] In the example shown in Figure 6, UEs 610 and 670 can have a connection or established link 680, which can be routed through the various components shown (as well as others not shown). For example, data, which may correspond to the digitized voice for transmission over IP (VOIP), may be sent via the communication link 681 between the UE 610 and a base station 612, which may be an eNB, as shown above in Figures 1-4. Data can be generated from inputs such as analog audio (a source of voice or other user audio, for example) and converted to digital data by means of an Encoder-Decoder (Codec). In general, the terminal at the other end of the connection may need to use the same codec to convert the data back to analog output. Data conversion rate can be codec controlled, which can be done based on data rate signaling received from other network elements, such as gateway 640, as further described below. Data can be formatted as a message or packet, as well as in the form of an IP packet.
[00137] Once generated, data can then be sent from base station 612 to core network elements 632 via connection 682, which can be, for example, configured as shown in Figure 3 or 4. Data can then pass through by core networking components 632 and sent to an ECM 640 interworking gateway via connection 683. Gateway 640 can be configured to perform various ECN functionality, as also described below. In some implementations, interworking gateway 640 may be implemented as a separate system or systems, whereas, in other implementations, interworking gateway 640 may be integrated, in whole or in part, within other network elements, such as such as the 632 core network elements.
[00138] In communication with a second network, such as network 650, gateway 640 may provide modified or adjusted media data, which may be modified from data provided from connection 683 to remove ECN functionality signaling and provide the modified data to transport elements 660 via connection 684. The modified media data can then be received on network 650 and also sent to terminal 670, ie, via connections 685 to 687 via base station 652 , in a way not capable of ECN. Similar connectivity between terminals 670 and 610 can be provided in the opposite direction to facilitate bidirectional communication and corresponding functionality between terminals 670 and 610. In an exemplary embodiment, the media can be modified with the removal of ECN markings , such as ECT or CE markings, of packets received from a first network node, such as UE 610, as well as for signaling to the first network and connected nodes about rate adjustments. An example of this is also described here below. Alternatively, or in addition, the interworking gateway can be configured to transcode or adjust data rates for media between the first and second networks and/or to perform a combination of these functions or others described herein.
[00139] The connection between terminals 610 and 670 in this example can be seen as a two-part connection, shown as sub-connections or links 680A and 680B, as opposed to the connection or single link 580 shown in Figure 5. In a sub -connection supported by ECN 680A, the connectivity of the first network may appear transparent to the ECN capabilities of the other network. From the perspective of the UE 610, for example, a connection to the UE 670 may appear to be ECN capable, regardless of the actual configuration of the 650 network (and/or the configuration of any additional or intermediate networks, which may be non-ECN compliant ). In effect, the gateway 640 can function as termination for ECN signaling to and from the UE 610. Likewise, from the perspective of the UE 670, the connection 680B to the UE 610 may appear agnostic or may appear as not being ECN compliant, even if ECN functionality is supported from UE 610.
[00140] As also described below, this functionality can be facilitated by the gateway 640, which can be, in various implementations, presented as a component of the core network, as a component of other elements of the first operator's system and/or as a separate component (as shown in the exemplary configuration of Figure 6). Gateway 640 may be located within the first carrier's infrastructure or, in some cases, may be external to the first carrier's network. In some implementations, for example, gateway 640 may be located on transport components 660 or it may lie between other networks (not shown in Figure 6). In some implementations, such as the one shown in Figure 7, a gateway between a first network capable of ECN and a second network of unknown ECN capability may be presented. Furthermore, in some implementations, a gateway between two networks capable of ECN can be presented, presenting at the same time interworking capability between the two networks, as also described below.
[00141] Returning to Figure 6, the functionality provided by the gateway 640 can be performed by providing local rate adaptation between the terminals or UEs in the first operator's network and those of other networks. To do this, gateway 640 can be configured to function as an ECN endpoint for UE 610 so as to allow local rate adaptation when network 650 (and/or other connecting networks or transport components) is not capable. of ECN.
[00142] The ECN functionality within an IP network tag works by adding certain bits to the IP header to encode different code points. For example, the two least significant bits (ie, on the right) of the ServDif field in the IP header can be encoded as follows: 00: Transport Not ECN Capable; 10: Capable transport of ECN ECT(0); 01: ECN Capable Transport ECT(1): 11: Congestion Found (CE). When both endpoints support ECN, they can mark their packets with ECT(0) or ECT(1). If the packet traverses a queue that supports initial congestion detection, such as an Active Queue Management (AQM) queue, it can change the code point to CE instead of discarding the packet. This is also known as "tag" and its purpose is to inform the receiving endpoint of impending congestion. At the receiving endpoint, this congestion indication can be processed by a higher layer protocol (TCP, for example) and can be echoed back to the transmitting node so that it has its transmission rate reduced.
[00143] In an exemplary embodiment, interworking gateway 640 may be configured to perform one or more of the following functions to facilitate inter-network ECN functionality for congestion mitigation. 1. Negotiate the use of the ECN between the gateway 640 and the local UE (the UE 610, for example) when setting up the call if the far-end UE (the 670, for example) and/or the far-end network (the 650 network, for example) do not support ECN. In this way, the local UE can function transparently as if the other network and the terminal were ECN capable. 2. During a session, provide rate adaptation feedback. For example, if gateway 640 receives congestion found (CE) flags from the uplink from the local UE and if the far end terminal (the UE 670, for example) is not ECN capable, then the gateway 640 can read the information CE code point marking in order to determine an appropriate rate and send a TMMBR, CMR or other data or rate request message to the local UE to request this baud rate (typically a reduced baud rate) on its link ascending. 3. During the session, the gateway may lower the rate of media sent on the downlink path to the local UE so as to equal the rate request threshold (TMMBR, for example) of the local UE. This can be done by the gateway as follows. The gateway effectively relays the Local UE Rate Request Information (TMMBR) to the far-end UE, translating this into an appropriate command for the far-end UE when necessary (for example, as an RTCP-codec mode request. APP, in-band codec mode request via RTP and the like). This allows the far-end UE to encode its media at a rate requested by the local UE, thus achieving end-to-end rate adaptation in the downlink direction for the local UE.
[00144] In some implementations, rate adjustment processing may be performed in whole or in part by other nodes within the first network in addition to the UEs, such as by base station 612. For example, base station 612 may receiving a rate reduction request from the interworking gateway 640 and instructing the UE 610 to adjust its output data rate.
[00145] In another aspect, if the gateway 640 does not retransmit the rate request information from the local UE, the gateway 640 can "downlink transcode" the media data received from the far-end UE to the rate requested by the local UE. G.711 transcoding for dynamically changing target rates is already required in MGW to support calls to public switched telephone network (PSTN) endpoints. The functionality described above can be used in order to extend this functionality to support transcoding of a non-G.711 codec. Rate transcoding may be needed only in the downlink direction and may be needed only for rate reduction (that is, there would generally be no need for the gateway to transcode far-end media if its rate was lower than that requested by the local EU). Voice quality deterioration should be minimal compared to end-to-end case since transcoding aims at the same quality/lower rate.
[00146] A potential problem for ECN implementations relates to the complexity of having UEs probe and monitor the transport path in order to ensure that it remains currently and in the future transparent to the ECN. However, based on the above-described arrangements, there may be no need for a local UE, such as UE 610, to probe the transport path. When an ECN-capable local UE is in its native network, its network elements are guaranteed to be transparent to the ECN insofar as the network is configured as such. Furthermore, if the local UE establishes an MTSI session with another UE, such as the UE 670, in a network of another operator, such as the network 650, which does not support ECN, the aspects described above will still allow rate adaptation for o Local UE on the native network.
[00147] In some cases, terminals or UEs can roam into another carrier's networks. ECN functionality, using an interworking gateway, can be resolved in this case. For example, an ECN-enabled UE, such as UE 610, may roam into an ECN-capable network, such as network 650, and make a call to an ECN UE in another ECN-transparent network. In this case, since both UEs may be ECN capable, the ECN can be negotiated end-to-end, but it is possible for the network not transparent to the ECN to drop media packets, which could result in potential media loss. .
[00148] One solution to this roaming problem is to provide edge routers for the ECN transparent network to remove the ECN capability from the SDP and mechanisms can also be called to process the ECN locally if the routers cannot confirm (through agreements level of service (SLAs), for example) that the SDP originates from a network transparent to the ECN.
[00149] In another example of roaming, when a non-ECN UE such as the 670 UE roams into an ECN transparent network such as the 630 network, the ECN will not be enabled for this UE (since is devoid of ECN capability). Consequently, the operator of network 630 cannot adapt the rate for the UE that roamed into its network. However, the number of inbound roaming agents without ECN capability should be expected to be relatively small compared to the total number of local UEs in the operator's network. Therefore, the impact of these roaming agents that do not have rate adaptation should be expected to be minimal.
[00150] Rate decision feedback can be sent from the media receiver to the sender using, for example, APP RTCP packets as defined in 3GPP TS 26.114, which is incorporated herein by reference. Therefore, the most generic message, TMMBR, can be used to cover all codecs, including video codecs. TMMBR message support is already required for Multimedia Telephony Services for IMS (MTSI) video services in 3GPP TS 26.114 and can therefore be extended for use in all codecs.
[00151] In general, there may not be a need for an ECN Feedback message. Sending an ECN feedback message can raise the following issues. Sending requires a significant amount of RTCP bandwidth, especially when compared to the amount of bandwidth that is required for VoIP media. The specified procedures for using ECN Feedback messages and APP RTCP packets can cause ambiguity of “ double adaptation” in the media sender. The media receiver requests a certain rate from the media sender using the APP RTCO packet, while the media sender is required to adapt their rate using the information in the ECN Feedback message. Since rate information is fed back directly to the media sender and MTSI endpoints do not have to probe the transport path, it may not be necessary to send the ECN feedback message.
[00152] Not all operators may be interested in the rate adaptation feature that uses ECN and therefore the ECN capability may be optional in the UE and/or in the network. An operator that is interested in using such capacity may require UE vendors to implement this in their terminals and require infrastructure vendors to ensure that their network elements meet the applicable requirements.
[00153] Figure 7 shows another communication system 700 in which aspects can be implemented. In system 700, first network 730 may be configured similarly to network 630 of Figure 6 and may include similar elements, including a first UE 731, a base station or eNB 712, a core network 732, an interworking gateway 740, as well as other intermediate elements (not shown). Data may also be routed over links 781, 782 and 783 between the first UE 710 and the gateway 740 so as to form a first network link 780A.
[00154] However, the capabilities of the second network 750 may be either unknown (that is, the second network may be ECN capable, but the first network may not be able to determine whether or not it is or, in some cases, both first and second networks may be ECN-capable For example, base network 752, base station 752, terminal or UE 770, and/or other components, such as components 760, may or may not be ECN-capable. In network 750, signaling may be provided from gateway 740 over links such as links 784, 785, 786 and 787, similar to the connections shown in Figure 6. Link 780B may comprise an unknown or ECN capable link, depending on the configuration. In either of these cases, interworking gateway 740 can be configured to provide functionality analogous to that described with respect to network 600 acting as an ECN termination for congestion indications of either the first or second network or both, thus like to provide transparency to ECN functionality for one or both networks.
[00155] In one case, for example, the operator of the first network may choose never to negotiate ECN capacity with the second network. Alternatively, the interworking gateway can negotiate ECN health with either the first or second network. In this case, the gateway can receive, for example, media marked with ECN, in which it can send the packets marked with ECN to the nodes of the first network so that they can process them, for example, to transcode the media to different rates depending on the rates supported by devices on the first and second networks.
[00156] In another example, a sender triggered congestion control may be implemented instead of a receiver triggered congestion control. In the examples described above, the congestion control triggered by the ECN receiver is used in a general way (that is, the receiver uses the congestion information to determine the rate the sender should use, which is signaled to the sender, either through of a rate adjustment request, for example). In implementations using sender-triggered congestion control, the receiver indicates to the sender that congestion is encountered, but the sender decides which rate to use. In this case, the interworking gateway can be configured to negotiate sender and receiver congestion control between nodes in the two networks and, in particular, between networks using different approaches (ie, sender in one, receiver in the other) . In some cases, when a CE marking is received, the interworking function may decide to generate an ECN feedback message, ie, by marking the media with ECN markings. Furthermore, the interworking function can be used to negotiate rates between nodes in the first and second networks, even though both are ECN capable.
[00157] In some cases, more than one network can be implemented, for example, in the case of a three-way call between users in three different networks, which can be controlled by three different carriers. In this case, the interworking gateway can be configured to provide interworking between the three (or more) networks, such as negotiating rates between different networks, transcoding media between different networks, managing interworking between different networks, or providing other interworking functionality similar to that described elsewhere here. For example, the interworking gateway can be used to signal node rate reductions on one of the networks but not on the others. Alternatively, or in addition, media can be transcoded between various networks based on specific network congestion conditions.
[00158] Reference is now made to Figure 8, which shows details of an embodiment of a system 800 that can be used to provide ECN functionality between Interworking Gateway 840 components, which may correspond to Interworking Gateway 640 of Figure 6 or to interworking gateway 740 of Figure 7, and one or more UEs 830, which may correspond to UE 610 or UE 710, in the network associated with the same carrier. System 800 may include one or more base stations 820 (also referred to as nodes, evolved nodes Bs - eNBs, server eNBs, target eNBs, macro-nodes, femto-nodes, pico-nodes, and the like), which may be capable entities. communication via the wireless network (or networks) 810 with various terminal devices 830, such as, for example, those shown in Figures 1-4 and 6-7. For example, each device 830 may be an access terminal (also referred to as a terminal, user equipment (UE), mobility management entity (MME), mobile device, and the like). Base station 820 and/or devices 830 may include an explicit congestion notification (ECN) 883 component that communicates with gateway component 840. Corresponding Gateway 843 ECN components may be presented to facilitate interconnectivity between the UE 830 and devices on another network, such as UEs on a different carrier network, that may not be ECN capable. This can be done through connection 884, which can correspond to connections 684 and 784 of Figures 6 and 7.
[00159] As shown, the base station 820 can communicate with the device (or devices) 830 via a downlink (DL) 860 and can receive data via an uplink (UL) 870. Uplink and downlink is arbitrary since device 830 may also transmit data through downlink channels and receive data through uplink channels in various implementations. Note that although two 820 and 830 components are shown, more than two components can be used in the 810 network (and/or in other networks and network implementations).
[00160] In general, system 800 is configured to process explicit congestion notification protocols (ECN) through distinct networks, as described here. This can include communicating the ECN protocol to at least one 830 device (or 830 devices). Gateway component 840 may then process the ECN protocol together with device(s) 830 and at least one local network, which may be ECN capable, wherein gateway component 840 also communicates device data. 830 and from the local network to at least one other network that does not support the ECN protocol or for which the ECN capability may be unknown.
[00161] Figure 9 shows a block diagram of a modality of a base station 910 (an eNB or HeNB, for example) and a terminal 950 (i.e. a terminal, AT or UE) in an LTE 900 communication system example, which can be configured to provide ECN functionality, as described herein. These components can correspond to those shown in Figures 1-4 and 6 and can be configured to implement all or part of the processing shown hereinafter in Figures 10-13.
[00162] Various functions can be performed in the processors and memories shown in base station 910 (and/or in other components not shown), such as sending and receiving ECN messages, as well as other functions described herein above. UE 950 may include one or more modules for receiving signals from base station 910, to, for example, send and receive ECN messages and/or adjust operation in accordance with the various ECN-related functions described herein, including rate adaptation .
[00163] In one embodiment, the base station 910 may adjust the outbound transmissions in response to information received from the UE 950 or the return transport signaling from another base station or a core network (not shown in Figure 9), as described here earlier. This can be done on one or more components (or other components not shown) of base station 910, such as processors 914, 930 and memory 932. Base station 910 can also include a transmission module that includes one or more components (or other components not shown) of the eNB 910, such as transmission modules 924. Base station 910 may include an interference cancellation module that includes one or more components (or other components not shown), such as processors 930, 942, the demodulator module 940 and memory 932 to provide interference cancellation functionality. Base station 910 may include a sub-frame partition coordination module that includes one or more components (or other components not shown), such as processors 930, 914 and memory 932 to perform sub-frame partition functions. as described herein before and/or manage the transmitter module based on the subframe partition information. Base station 910 may also include a control module to control receiver functionality. Base station 910 may include a network connection module 990 to provide networking with other systems, such as backhaul systems in the core network or other components shown in Figures 3 and 4.
[00164] Likewise, the UE 950 may include a receiving module that includes one or more components of the UE 950 (or other components not shown), such as the receivers 954. The UE 950 may also include an information module signal that includes one or more components (or other components not shown) of the UE 950, such as processors 960 and 970 and memory 972. In one embodiment, one or more signals received at UE 950 are processed for estimating channel characteristics , power information, spatial information, and/or other information pertaining to eNBs, such as base station 910 and/or other base stations (not shown). Measurements can be taken during semi-static subframes that are notified to the UE 950 by base station 910. Memories 932 and 972 can be used to store computer code for execution on one or more processors, such as processors 960, 970 and 938, to implement processes associated with determining metering and channel information, power level and/or spatial information, selecting cell IDs, intercellular coordination, interference cancellation control, as well as other functions related to allocation, subframe interlacing and the related transmission and reception, as described herein.
[00165] In operation, at base station 910, traffic data for various data streams is sent from a data source 912 to a transmission data processor (TX) 914, where it can be processed and transmitted to one or more UEs 950. The transmitted data may be controlled as described hereinbefore to obtain interlaced subframe transmissions and/or to perform related signal measurements in one or more UEs 950.
[00166] In one aspect, each data stream is processed and transmitted through a respective transmitter subsystem (shown as transmitters 9241-924Nt) of base station 910. Data processor TX 914 receives, formats, encodes and interleaves the traffic data for each data stream based on a specific encoding scheme selected for that data stream so as to obtain encoded data. In particular, base station 910 may be configured to determine a reference signal and a specific reference signal pattern and generate a transmission signal that includes the reference signal and/or beamforming information in the selected pattern.
[00167] The encoded data for each data stream can be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and can be used in the receiver system to estimate channel response. The pilot data can be sent to the TX 914 data processor, as shown in Figure 9, and multiplexed with the encoded data. The multiplexed coded and pilot data for each data stream can then be modulated (ie, symbol-mapped) based on a specific modulation scheme (such as BPSK, QPSK, M-PSK, M-QAM, etc.) selected for this data stream to obtain modulation symbols, and the data and pilot can be modulated using different modulation schemes. The data rate, encoding and modulation for each data stream can be determined by instructions executed or provided by processor 930 based on instructions stored in memory 932 or in other memory or instruction storage medium of the UE 950 (not shown ).
[00168] The modulation symbols for the data streams can be sent to a MIMO TX 920 processor, which can also process the modulation symbols (for OFDM implementation, for example). The MIMO TX processor 920 then sends Nt modulation symbol streams to Nt transmitters (TMTRs) 9221 to 922Nt. The various symbols can be mapped to connected RBs for transmission.
[00169] The MIMO TX 930 processor can apply beamforming weights to the symbols of the data streams and that correspond to the antenna or antennas from which the symbol is being transmitted. This can be done using information such as channel estimation information provided by or together with reference signals and/or spatial information provided from a network node, such as a UE. For example, a beam B = transposition([b1 b2 ...b Nt]) is composed of a set of weights that correspond to each transmit antenna. Transmission along a beam corresponds to the transmission of an x-modulation symbol across all antennas scaled by the beam weight for that antenna; that is, at antenna t the transmitted signal is bt*x. When several beams are transmitted, the signal transmitted on an antenna is the sum of the signals that correspond to different beams. This can be expressed mathematically as B1x1 + B2x2 + BNSxNS, where NS are transmitted and xi is the modulation symbol sent using Bi. In many implementations, beams can be selected in a variety of ways. For example, beams can be selected based on channel feedback from a UE, channel knowledge available in the eNB, or based on information provided from a UE to facilitate interference attenuation, such as with an adjacent macro cell.
[00170] Each transmitter subsystem 9221 to 922Nt receives and processes a respective stream of symbols in order to generate one or more analog signals and also conditions (amplifies, filters and upconverts, for example) the analog signals in order to obtain a modulated signal suitable for transmission over the MIMO channel. Furthermore, NT modulated signals from transmitters 9221 to 922Nt are transmitted from Nt antennas 9241 to 924Nt, respectively.
At UE 950, the transmitted modulated signals are received by Nr antennas 9521 to 952Nr, and the received signal from each antenna 952 is sent to a respective receiver (RCVR) 9541 to 954 Nr. Each receiver 954 conditions (filters, amplifies and downconverts, for example) a respective received signal, digitizes the conditioned signal to generate samples and also processes the samples to generate a corresponding "received" symbol stream.
[00172] An RX data processor 960 then receives and processes the Nr symbol streams received from the Nr receivers 954 based on a specific receiver processing technique so as to obtain NS "detected" symbol streams to obtain estimates of the NS transmitted symbol streams. The RX data processor 960 then demodulates, deinterleaves and decodes each detected symbol stream so as to retrieve the traffic data for the data stream. The processing by the RX 960 data processor is complementary to that performed by the MIMO TX 920 processor and the TX 914 data processor at base station 910.
[00173] A processor 970 may periodically determine a precoding matrix to be used, as is also described below. Processor 970 then formulates a reverse link message which comprises an array index part and a rank value part. In various respects, the reverse link message can include different types of information regarding the communication link and/or the received data stream. The reverse link message can then be processed by a TX 938 data processor, which can also receive traffic data for various data streams from a 936 data source, which can then be modulated by a 980 modulator, conditioned by 9541 transmitters. at 954Nt and transmitted back to base station 1310. Information transmitted back to base station 910 may include power level and/or spatial information to provide beamforming to attenuate interference from base station 910.
At base station 910, modulated signals from UE 950 are received by antennas 924, conditioned by receivers 922, demodulated by a demodulator 940, and processed by an RX data processor 942 to extract the message by UE 950. 930 then determines which precoding matrix to use to determine the beamforming weights, and then processes the extracted message.
[00175] Figure 10 shows details of an exemplary interworking gateway 1000, which may correspond to gateways 640 or 740 shown in Figures 6 and 7. Gateway 1000 may include one or more 1030 interfaces with the first network to facilitate communication of data and media between the gateway and a first connected network, which may correspond to network 630 or network 730. In some cases, the interworking gateway and related functionality may be incorporated, in whole or in part, into the core network or the other nodes of the first network.
[00176] The data can include data compatible with ECN functionality so that nodes, such as terminals or UEs in the first network, can operate according to an ECN protocol. In addition, gateway 1000 may include one or more interfaces 1020 with the second network to facilitate interfacing between the gateway and one or more other networks, which may correspond to networks 650 or 750 shown in Figures 6 and 7. , gateway 1000 may include one or more processor modules configured to execute instructions that may be stored in one or more program modules 1060. Program modules 1060 may be stored in memory space 1050, which may include one or more physical memories or other data storage devices. In addition, memory 1050 may include other data or information, such as an operating system module 1052, operating or message data 1054, and/or other data or information.
[00177] The program modules may include a first 1064 network interface module configured to facilitate ECN processing between the gateway and local UEs, such as, for example, to process congestion indications and generate rate adjustment messages, a second 1062 network interface module, which can be configured to facilitate ECN processing between the gateway and external networks, such as to respond to rate adaptation requests, adjust ECN packets to a non-ECN network format (undoing ECN bits, such as ECT or CE bits, for example) and/or perform other processing as described herein. In addition, program modules 1060 may include a transcoding module 1066 for transcoding data between two or more networks, as well as other modules for performing processing and interworking functionality as described herein (not shown in Figure 10).
[00178] Figure 11 shows an embodiment of a process 1100 to provide communications using interworking functionality. At stage 1110, an indication of congestion may be received at an interworking gateway, for example, as shown in Figures 6 and 7. The indication may be provided from a node in a first network, where the first network may be, for example, an ECN capable network. The indication may be an indication using ECN congestion message exchange, such as an indication of CE in a data packet associated with media that is sent to another network node, such as a second UE in a second network.
[00179] For example, a first UE in the first network, such as, for example, UE 610 of Fig. 6, which may be ECN capable, may send media to a second UE in a second network, such as, for example , the UE 670, which is not ECN capable. The message can be sent through intermediate nodes, such as routers, switches and/or other nodes of the first network, where congestion may be encountered. In this case, packets can be tagged by the intermediate nodes with, for example, CE bits set according to an ECN protocol, indicating potential congestion. Upon being received at the interworking gateway, packets can be processed to facilitate interworking with the second network in order to make the second network appear transparent to the ECN to the first network node, or in order to make the interworking gateway function acts as an endpoint for congestion indication messages from the first network while maintaining ECN functionality.
[00180] At stage 1120, for example, the media can be set for transmission to the second network in the interworking gateway so that they are in a non-ECN capable format. This can be done, for example, by removing any ECN bits set in packets (discarding ECT bits, CE bits and the like, for example). The trimmed message may then be sent to the second network at stage 1130. In some implementations, media trim stage 1120 may be omitted and media may be sent unadjusted to the second network.
[00181] In addition, a data rate adjustment request can be generated at stage 1140. This can be done to indicate to the first UE that a congestion has been encountered in the first network and a lower data rate is desirable to alleviate the congestion and avoid potential packet loss. The adjustment request can then be sent to the UE and/or intermediate nodes, such as, for example, a serving base station, such as base station 612 shown in Figure 6. In some cases, the data rate adjustment may be done in conjunction with another node, such as base station 612, but in general, the first UE will respond directly to the data rate adjustment request. For example, the UE may adjust the media data rate to be sent to the second UE, which will typically be an adjustment to a lower data rate. In some cases, the UE and/or other nodes, such as serving base stations, may decide not to adjust the data rate.
[00182] In stage 1160, the rate-adjusted media sent by the first UE can be received at the interworking gateway. Similar to stage 1120, the media can be set to a non-ECN capable format for transmission to the second network. For example, ECN bits can be dropped from packets before being sent to the second network. In some cases, no adjustments can be made. In any case, the media can then be sent to the second network, where it can finally be delivered to the second UE.
[00183] Figure 12 shows an embodiment of a process 1200 to provide communications that uses interworking functionality. Process 1200 can be implemented, for example, by a first network UE together with functionality provided by an interworking gateway, as, for example, is shown in Figure 11. In stage 1210, a first network node, ta as an ECN-capable UE operating in an ECN-capable network, it may send media to a node in a second network, such as a second UE in the second network, which may be a non-ECN-capable network. The first and second UEs may be in communication as shown in Figures 6 and 7. The media sent in stage 1210 may be subject to congestion in the first network, where, for example, a congestion indication such as bit setting of CE on packages, can be made by us intermediary. Upon being received at an interworking gateway, a media data rate reduction request can be generated and sent, which can then be received by the first UE at stage 1220. The UE can then adjust the data rate in response to the adjustment request at stage 1230, typically at a lower data rate in order to alleviate congestion in the first network. In some cases, the UE and/or other intermediate nodes, such as a serving base station, may choose not to adjust the data rate.
[00184] In stage 1240, the rate-adjusted media can then be sent to the interworking node for further transmission to the second network and the second UE. The media can be processed by the interworking gateway, as shown in Figure 11, for example, before being also transmitted to the second network and the second UE.
[00185] Figure 13 shows an embodiment of a process 1300 to provide communications using interworking functionality. At stage 1310, media, which can be, for example, voice or audio content, video content, images or other content, can be received at an interworking gateway, for example. Media may be sent from a node on a first network, such as a terminal or UE, which may be ECN capable. Media can be tagged by an intermediate node on the first network, such as a router or switch, where tagging can provide an indication of congestion. An indicator or CE bits can be set in media packages, for example.
[00186] In stage 1320, the media can be modified in order to remove the ECN feedback signaling or marking, for example, by removing the CE flag or bits from the packets. The media can then be sent at stage 1330 to a second network and a second connected network node in a non-ECN format. For example, the second network might not be ECN capable, with media modified accordingly. The media can be modified, for example, by removing ECN signaling such as ECT or CE bits or indicators.
[00187] Figure 14 shows an embodiment of a process 1400 to provide communications using interworking functionality. At stage 1410, media can be received from a second network. For example, media may be sent from a UE in the second network, which may be ECN-capable, and received at an interworking gateway, as shown in Figures 6 and 7, for example. The media can then be sent to a first network at stage 1420. For example, the media can be sent to a first UE in the first network, which may be ECN capable. In addition, the interworking gateway can adjust the medium at stage 1415 so that it is ECN compliant to support ECN functionality, adding ECT tags to media, for example. This can allow nodes within the first network to set CE bits if a congestion is encountered between the interworking gateway and the first UE.
[00188] For example, the first UE may correspond to the UEs 610 and 710 of Figures 6 and 7 respectively. Media can be marked during transmission through intermediate nodes of the first network with an ECN indication, such as a CE marking, for example. The first UE may then send, based on the congestion indication, a rate reduction request, wherein the rate reduction request may be directed to the UE in the second network (designated as a second UE). The interworking gateway may receive the rate adjustment request from the first network at stage 1430. In response to the rate adjustment request, the interworking gateway may process the request so as to provide integration of ECN functionality between the first and second networks. For example, this can be done by providing a decision on the capacity 1440 of the second network, which can be made at the interworking gateway as to how to process the request as well in order to maintain ECN functionality. For example, the interworking gateway may know, or be able to determine, whether the second UE can accommodate the rate reduction request. This can be done, for example, by a trade, which can be defined for certain types of media, such as video. If the gateway knows or can determine that the second UE can accommodate the request, it can then issue the request at stage 1450 to the second network, where it can then be sent to the second UE, as shown in Figures 6 and 7, where UE 670 or 770 may correspond to the second UE. If the gateway does not know or is not able to determine whether the UE can accommodate the request, it may then process incoming messages from the second UE so as to avoid congestion in the first network. At stage 1460, for example, the interworking gateway can transcode the media from the second network in order to alleviate congestion. This can be done, for example, by transcoding the media to a lower data rate so that the amount of data is reduced on the first network. In some cases, media sent from the first network may also be transcoded by the interworking gateway, for example, to accommodate the data rates expected by devices on the second network.
[00189] In some configurations, the apparatus for wireless communication includes means to perform various functions described herein. In one aspect, the mentioned means may be a processor or processors and a related memory, in which the embodiments reside, as shown in Figures 8 to 10, and which are configured to perform the functions enumerated by the mentioned means. There may be, for example, modules or an apparatus that reside in UEs, interworking gateways or other network nodes, such as those shown in Figures 1-4 and 6-10, to perform ECN-related functions described herein. In another aspect, the aforementioned means can be modules or any apparatus configured to perform the functions enumerated by the aforementioned means.
[00190] In one or more exemplary embodiments, the functions, methods and processes described can be implemented in hardware, software, firmware or any combination of them. If implemented in software, functions can be stored in or transmitted via one or more instructions or code in a computer-readable medium. Computer readable media includes both computer storage media and communication media that include any media that facilitates the transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, such computer readable medium may comprise RAM, ROM, EEPROM, CD-ROM or any other optical disk storage, magnetic disk storage or other magnetic storage devices or any other medium that may be used to carry or store desired program code devices in the form of instructions or data structures and which can be accessed by a general purpose or special purpose computer. Furthermore, any connection is appropriately termed a computer-readable medium. For example, if the software is transmitted from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwave , then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the media definition. The term disk (disk and disc in the original), as used herein, includes compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk, and blu-ray disk, in which usually disks (disks ) reproduce data magnetically, while discs (discs) reproduce data optically with lasers. Combinations of them should also be included within the range of computer readable media.
[00191] It should be understood that the specific order or hierarchy of steps or stages in the disclosed processes and methods are examples of exemplary approaches. Based on design preferences, it should be understood that the order or hierarchy of steps in the processes can be rearranged while remaining within the scope of the present disclosure. The attached method claims present elements of the various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.
[00192] Those skilled in the art would understand that information and signals can be represented using any of several different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols and chips referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination their.
[00193] Those skilled in the art would also understand that the various illustrative logical blocks, modules, circuits and algorithm steps described in connection with the present disclosure may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various components, blocks, modules, circuits, and illustrative steps have been described generically above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and design limitations imposed on the system as a whole. Those skilled in the art can implement the described functionality in a variety of ways for each specific application, but such implementation decisions should not be construed as departing from the scope of the present disclosure.
[00194] The various illustrative logic blocks, modules and circuits described in connection with the present disclosure may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an array of field-programmable gates (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but alternatively the processor can be any conventional processor, controller, microcontroller or state machine. A processor can also be implemented as a combination of computing devices, such as, for example, a combination of DSP and microprocessor, a series of microprocessors, one or more microprocessors together with a DSP core, or any other such configuration.
[00195] The steps or stages of a method or algorithm described in connection with the modalities disclosed here can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium can be integral with the processor. The processor and storage medium can reside on an ASIC. The ASIC can reside on a user terminal. Alternatively, the processor and storage medium can reside as discrete components on a user terminal.
[00196] The claims are not intended to be limited to the aspects shown here, but must be given the full scope compatible with the language of the claims, in which the reference to an element in the singular is not intended to mean "one and only one ”, unless specifically so stated, but rather “one or more”. Unless specifically stated otherwise, the term “some” refers to one or more. A phrase that refers to “at least one” of a list of items refers to any combination of those items, including single elements. As an example, “at least one of: a, b or c” is intended to cover: a; B; ç; a and b; a and c; b and c; and a, b and c.
[00197] The foregoing description of the disclosed aspects is presented to enable any person skilled in the art to make or use the present disclosure. Various modifications in these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects of the embodiments without abandoning the inventive concept or scope of the disclosure. Thus, the revelation is not intended to be limited to the aspects shown here, but must receive the widest scope compatible with the unpublished principles and aspects disclosed here. The following claims and their equivalents are intended to define the scope of the disclosure.

权利要求:
Claims (9)
[0001]
1. Method for providing communication, characterized in that it comprises: receiving (1310), in an interworking gateway coupled between a first network and a second network, a first set of media generated at a first data rate, wherein the first media set includes an explicit congestion notification marking of congestion found, ECN-CE, generated within the first network; providing, in response to the ECN-CE marking, a data rate adjustment request to request a lower data rate from a first user equipment, UE, in the first network; receiving, at the interworking gateway, a second media set sent from the first UE at a second data rate in response to the data rate adjustment request, wherein the second media set includes an explicit congestion notification marking , ECN; modify (1320), by the interworking gateway, the second set of media to remove the ECN marking; and sending (1330) from the interworking gateway to the second network the second modified media set.
[0002]
2. Method according to claim 1, characterized in that the first set of media and the second set of media are generated by the first UE in the first network for transmission to a second UE in the second network.
[0003]
3. Method according to claim 1, characterized in that the first network is an ECN capable network and the second network is a non ECN capable network.
[0004]
4. Method according to claim 1, characterized in that the data rate adjustment request comprises a Temporary Maximum Media Stream Bit Rate Request, TMMBR.
[0005]
5. Method according to claim 1, characterized in that the first network and the second network are wireless communication networks.
[0006]
6. Computer-readable memory, characterized in that it contains recorded thereon the method as defined in any one of claims 1 to 6.
[0007]
7. Interworking gateway (840), characterized in that it comprises: means for receiving a first set of media generated at a first data rate, wherein the first set of media includes an explicit congestion notification marking of congestion found , ECN-CE, generated within the first network; means for providing, in response to the ECN-CE marking, a data rate adjustment request to request a lower data rate from a first UE (830) in the first network; means for receiving a second media set sent from the first UE (830) at a second data rate in response to the data rate adjustment request, the second media set including an explicit congestion notification marking, ECN; means (843) for modifying the second set of media to remove the ECN marking; and means for sending, to a second network, the second set of media.
[0008]
8. Gateway (840), according to claim 7, characterized in that the first network and the second network are wireless communication networks.
[0009]
9. Gateway (840), according to claim 7, characterized in that the first network is an ECN capable network and the second network is a non ECN capable network.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112012007131B1|2021-05-18|methods and apparatus to allow rate adaptation through network settings

---

US10856245B2|2020-12-01|Method for transmitting D2D signal and terminal therefor

---

JP6517413B2|2019-05-22|Managing cross carrier scheduling in carrier aggregation using EPDCCH in LTE

---

ES2718508T3|2019-07-02|Reconfiguration for TDD considering DTX / DRX

---

KR101526857B1|2015-06-09|Random access procedure enhancements for heterogeneous networks

---

US10110644B2|2018-10-23|Methods and apparatus for dedicated bearer establishment handling during call setup for LTE

---

BR112012005892B1|2021-03-02|methods and apparatus for subframe interlacing in heterogeneous networks

---

KR20130006603A|2013-01-17|Method and apparatus for enhancing cell-edge user performance and signaling radio link failure conditions via downlink cooperative component carriers

---

US20100260109A1|2010-10-14|Optimized inter-access point packet routing for ip relay nodes

---

KR20130121838A|2013-11-06|Method and apparatus for ecn receiver driven congestion control

---

US10904904B2|2021-01-26|Methods and devices for controlling override of configured grant

---

WO2016025475A1|2016-02-18|Aggregation of wlan carriers to lte

---

AU2017305413A1|2019-01-17|Co-existence of reliable low latency and other services in a wireless network

---

US20160269982A1|2016-09-15|RRC Diversity

---

JP5823633B2|2015-11-25|System information block | message postponed measurement control | read

---

JP6922997B2|2021-08-18|Wireless terminal and its method

---

JP6462573B2|2019-01-30|PMCH / PRS and EPDCCH processing in LTE

---

WO2014059606A1|2014-04-24|Transmission scheduling request method and apparatus, user equipment and base station

---

CA2916348A1|2015-01-29|Method and apparatus for use of a relay schemed to facilitate efficient broadcast communication in device to device environment

---

EP3737198A1|2020-11-11|Method and apparatus for reporting ue | capability information for slrb | configuration in a wireless communication system

---

US20200145817A1|2020-05-07|Refreshing security keys in 5g wireless systems

---

BR112020020794A2|2021-01-12|METHODS FOR HANDLING CONFIGURATION OF PERIODIC UPDATING OF THE RADIO ACCESS NETWORK NOTIFICATION AREA | AFTER REJECTION

同族专利:

---

公开号 | 公开日

---

US20110075563A1|2011-03-31|

---

CN102577498A|2012-07-11|

---

HUE046669T2|2020-03-30|

---

KR20120063541A|2012-06-15|

---

WO2011041519A3|2011-09-29|

---

JP5619904B2|2014-11-05|

---

EP2484147A2|2012-08-08|

---

US9007914B2|2015-04-14|

---

TWI439146B|2014-05-21|

---

ES2706383T3|2019-03-28|

---

JP2013507058A|2013-02-28|

---

EP2584747A1|2013-04-24|

---

BR112012007131A2|2017-06-06|

---

CN102577498B|2015-12-16|

---

WO2011041519A2|2011-04-07|

---

EP2484147B1|2018-11-21|

---

TW201132150A|2011-09-16|

---

KR101502207B1|2015-03-12|

---

EP2584747B1|2019-12-04|

---

ES2770767T3|2020-07-03|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US5633859A|1994-09-16|1997-05-27|The Ohio State University|Method and apparatus for congestion management in computer networks using explicit rate indication|

---

JP3100034B2|1996-03-08|2000-10-16|日本電信電話株式会社|ATM communication network|

---

JP3102393B2|1997-11-14|2000-10-23|日本電気株式会社|Back pressure control method and system|

---

CA2237208A1|1998-05-08|1999-11-08|Northern Telecom Limited|Congestion notification from router|

---

US20020150060A1|1998-09-01|2002-10-17|Marie-Jose Montpetit|Asymmetric formatting system and method for low-earth-orbit satellite data communication|

---

US6876639B1|2000-06-01|2005-04-05|Nortel Networks Limited|Transmission control protocol handoff notification system and method|

---

US6741555B1|2000-06-14|2004-05-25|Nokia Internet Communictions Inc.|Enhancement of explicit congestion notification for wireless network applications|

---

US6839321B1|2000-07-18|2005-01-04|Alcatel|Domain based congestion management|

---

AU7777301A|2000-09-22|2002-04-02|Matsushita Electric Ind Co Ltd|Data transmitting/receiving method, transmitting device, receiving device, transmitting/receiving system, and program|

---

US6819678B2|2000-12-21|2004-11-16|Nortel Networks Limited|Interworking of dissimilar packet networks for telephony communications|

---

US7454527B2|2001-05-02|2008-11-18|Microsoft Corporation|Architecture and related methods for streaming media content through heterogeneous networks|

---

KR100605941B1|2001-11-28|2006-08-02|삼성전자주식회사|Data transmission method and apparatus for guaranteeing quality of service in data communication system|

---

US7020133B2|2002-01-03|2006-03-28|Integrated Device Technology|Switch queue predictive protocol based packet switching method|

---

JP4029670B2|2002-06-11|2008-01-09|日本電気株式会社|Congestion control method and system for wireless access|

---

US9414255B2|2002-09-13|2016-08-09|Alcatel Lucent|Packet flow control in a wireless communications network based on an indication contained in a packet|

---

KR100542401B1|2002-10-23|2006-01-11|한국전자통신연구원|An Admission Control Method in Differentiated Service Networks|

---

US7225267B2|2003-01-27|2007-05-29|Microsoft Corporation|Reactive bandwidth control for streaming data|

---

US7468947B2|2003-03-31|2008-12-23|International Business Machines Corporation|Controlling data packet flows by manipulating data packets according to an actual manipulation rate|

---

US20040196785A1|2003-04-01|2004-10-07|Gopalakrishnan Janakiraman|Congestion notification process and system|

---

AU2003271739A1|2003-05-16|2004-12-03|Telefonaktiebolaget Lm Ericsson |Call admission control in voip systems|

---

GB0321570D0|2003-09-15|2003-10-15|British Telecomm|Inter-domain congestion charging|

---

US8081566B1|2004-04-19|2011-12-20|Rockstar BIDCO, LLP|Method and apparatus for indicating congestion in a source routed network|

---

US7859996B2|2004-10-29|2010-12-28|Broadcom Corporation|Intelligent congestion feedback apparatus and method|

---

US7760646B2|2005-02-09|2010-07-20|Nokia Corporation|Congestion notification in 3G radio access|

---

US7596091B2|2005-02-28|2009-09-29|Microsoft Corporation|Unified congestion notification mechanism for reliable and unreliable protocols by augmenting ECN|

---

US7500010B2|2005-04-07|2009-03-03|Jeffrey Paul Harrang|Adaptive file delivery system and method|

---

US20060250953A1|2005-04-13|2006-11-09|Lucent Technologies, Inc.|Quality of service admission control based on congestion of backhaul connection|

---

US8520517B2|2007-02-21|2013-08-27|Broadcom Corporation|Switch fabric end-to-end congestion avoidance mechanism|

---

EP2154839B1|2007-06-06|2013-05-22|Fujitsu Limited|Relay device and terminal|

---

EP2165481B1|2007-07-09|2011-12-28|Telefonaktiebolaget L M Ericsson |Adaptive rate control in a communications system|

---

KR101421587B1|2007-08-23|2014-07-22|삼성전자주식회사|Method and Apparatus for determining preferred image format in IP-based mobile video telephony|

---

US8155090B2|2007-11-01|2012-04-10|Telefonaktiebolaget L M Ericsson |Method and apparatus for efficient multimedia delivery in a wireless packet network|

---

EP2079205A1|2008-01-14|2009-07-15|British Telecmmunications public limited campany|Network characterisation|

---

WO2009090160A1|2008-01-14|2009-07-23|Telefonaktiebolaget Lm Ericsson |Method and nodes for congestion notification|

---

US8553554B2|2008-05-16|2013-10-08|Alcatel Lucent|Method and apparatus for providing congestion control in radio access networks|

---

WO2010018157A2|2008-08-11|2010-02-18|Nokia Siemens Networks Oy|System, method, program element and computer-accessible medium for forwarding media control messages|

---

PL2359546T3|2008-10-23|2018-08-31|Orange|Method for configuring parameters for managing data packets pertaining to a data flow|

---

US20100246400A1|2009-03-26|2010-09-30|Kyocera Corporation|Communication device and method|

---

US8248936B2|2009-04-01|2012-08-21|Lockheed Martin Corporation|Tuning congestion control in IP multicast to mitigate the impact of blockage|

---

US9584416B2|2009-06-08|2017-02-28|Qualcomm Incorporated|Systems and methods to provide flow control for mobile devices|

---

JP5353494B2|2009-07-03|2013-11-27|富士通株式会社|Communication device and communication method|

---

US8427949B2|2009-08-07|2013-04-23|Future Wei Technologies, Inc.|System and method for adapting a source rate|

---

CN102598642A|2009-11-04|2012-07-18|日本电气株式会社|Gateway apparatus, mobile terminal, mobile communication method and program|

---

US8416690B2|2010-01-11|2013-04-09|Research In Motion Limited|Explicit congestion notification based rate adaptation using binary marking in communication systems|

---

US8982694B2|2010-09-01|2015-03-17|Telefonaktiebolaget L M Ericsson |Localized congestion exposure|

---

US20120087245A1|2010-10-06|2012-04-12|Qualcomm Incorporated|Methods and apparatus for ecn receiver driven congestion control|CN102281587B|2010-06-13|2018-07-17|中兴通讯股份有限公司|The method and system of realizing direct interface between access network nodes|

---

US8982694B2|2010-09-01|2015-03-17|Telefonaktiebolaget L M Ericsson |Localized congestion exposure|

---

US20120087245A1|2010-10-06|2012-04-12|Qualcomm Incorporated|Methods and apparatus for ecn receiver driven congestion control|

---

US8526448B2|2010-10-19|2013-09-03|Cisco Technology, Inc.|Call localization and processing offloading|

---

US9247457B2|2010-12-07|2016-01-26|Nec Corporation|Gateway apparatus and voice communication method|

---

EP2652985B1|2010-12-17|2015-05-20|Telefonaktiebolaget L M Ericsson |Performance monitoring in a mobile communication network|

---

US20120163203A1|2010-12-28|2012-06-28|Tektronix, Inc.|Adaptive Control of Video Transcoding in Mobile Networks|

---

CN103380392B|2011-03-31|2014-12-03|富士胶片株式会社|Imaging device, and focus control method therefor|

---

EP2754314A1|2011-09-06|2014-07-16|NEC Europe Ltd.|Method and system for congestion avoidance in mobile communication networks|

---

WO2013036183A1|2011-09-08|2013-03-14|Telefonaktiebolaget L M Ericsson |Method in a base station, a base station, computer programs and computer readable means|

---

US9270489B1|2012-03-19|2016-02-23|Google Inc.|Explicit congestion notification in mixed fabric networks|

---

CN104429140A|2012-07-06|2015-03-18|日本电气株式会社|Base station device, communication control method, and non-transitory computer-readable medium containing communication control program|

---

CN103581137A|2012-08-02|2014-02-12|中兴通讯股份有限公司|ECN proxy equipment and ECN notification method|

---

US9591513B2|2012-08-06|2017-03-07|Vid Scale, Inc.|Rate adaptation using network signaling|

---

US8923123B2|2012-11-02|2014-12-30|Lockheed Martin Corporation|ECN-enabled multicast protocol for wireless communication systems under blockage|

---

WO2014085983A1|2012-12-04|2014-06-12|华为技术有限公司|Homenodeb gateway and message sending method thereof|

---

US9571403B2|2013-02-07|2017-02-14|Broadcom Corporation|Packet marking for flow management, including deadline aware flow management|

---

US8995278B1|2013-03-12|2015-03-31|Sprint Spectrum L.P.|Managing a wireless device connection in a multioperator communication system|

---

US20140269475A1|2013-03-14|2014-09-18|Qualcomm Incorporated|Apparatus and method for optimizing uplink semi-persistent scheduling activation|

---

US9356869B2|2013-04-10|2016-05-31|Viber Media Inc.|VoIP bandwidth management|

---

EP3008949A1|2013-06-12|2016-04-20|Telefonaktiebolaget LM Ericsson |Ip media rate adaptation|

---

US9148814B2|2013-10-28|2015-09-29|At&T Intellectual Property I, L.P.|Probe mechanism for discovering explicit congestion notification data|

---

US9860791B1|2014-07-02|2018-01-02|Sprint Communications Company L.P.|Long term evolution communication policies based on explicit congestion notification|

---

EP3222014B1|2014-11-17|2019-07-24|Telefonaktiebolaget LM Ericsson |Active queue management for a wireless communication network|

---

US10524179B2|2015-04-10|2019-12-31|Qualcomm Incorporated|Rate adaptation during handoffs|

---

WO2016185649A1|2015-05-20|2016-11-24|パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカ|Communication node, terminal, and communication control method|

---

US10149122B2|2015-09-14|2018-12-04|Qualcomm Incorporated|Techniques for in-band signaling of service description updates in RTP|

---

WO2017169090A1|2016-03-28|2017-10-05|パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカ|User equipment, base station and codec mode switching method|

---

US20200337024A1|2016-04-25|2020-10-22|Guangdong Oppo Mobile Telecommunications Corp., Ltd.|Data transmission method and device|

---

US10104001B2|2016-08-30|2018-10-16|Citrix Systems, Inc.|Systems and methods to early detect link status of multiple paths through an explicit congestion notification based proxy|

---

US9800722B1|2016-11-21|2017-10-24|Athoc, Inc.|Managing a telephone communication system to dynamically throttle call attempts and reduce congestions during mass call events|

---

CN108206925B|2016-12-16|2020-04-14|展讯通信（上海）有限公司|Method and device for realizing multichannel video call and multichannel terminal|

---

FR3065141B1|2017-04-11|2019-07-05|Orange|METHOD FOR ALLOCATING A TRANSMISSION RESOURCE TO A MOBILE TERMINAL|

---

CN109451879A|2017-11-17|2019-03-08|北京小米移动软件有限公司|System information configuration, read method and device, base station and user equipment|

---

US10917348B1|2018-07-06|2021-02-09|Netronome Systems, Inc.|Network interface device that sets an ECN-CE bit in response to detecting congestion at an internal bus interface|

---

US11128682B2|2018-12-03|2021-09-21|At&T Intellectual Property I, L.P.|Video streaming at mobile edge|

---

CN112511323A|2019-09-16|2021-03-16|华为技术有限公司|Method and related apparatus for handling network congestion|

法律状态:
2019-01-08| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|

---

2020-03-10| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|

---

2021-03-16| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|

---

2021-05-18| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 30/09/2010, OBSERVADAS AS CONDICOES LEGAIS. PATENTE CONCEDIDA CONFORME ADI 5.529/DF |

优先权:

---

申请号 | 申请日 | 专利标题

---

US24709509P| true| 2009-09-30|2009-09-30|

---

US61/247,095|2009-09-30|

---

US12/893,980|US9007914B2|2009-09-30|2010-09-29|Methods and apparatus for enabling rate adaptation across network configurations|

---

US12/893,980|2010-09-29|

---

PCT/US2010/050874|WO2011041519A2|2009-09-30|2010-09-30|Methods and apparatus for enabling rate adaptation across network configurations|

---