JP2017534216A - Selected IP flow ultra-low latency - Google Patents

Abstract

Methods, systems, and devices for reducing user plane latency in a wireless communication system 200-b are described. This is through the local or serving gateway (LGW) 205-a, 205-b, or within the base station 105-a, 105-b, or through the core network 130-b or the base station 105-b. routing a portion of bearer traffic between user equipment (UE) 115-a, 115-b, 115-c between a, 105-b. In some examples, techniques for selected Internet Protocol Flow Ultra Low Latency (SIPFULL) for systems where a user may be subscribed to extended services may be employed. The network may allow SIP FULL functionality for the UE on a per access point name (APN) basis, for example, based on individual services subscribed by the UE to improve overall quality of service (QoS). In some examples, UE latency requirements or SIPFULL grants can affect mobility operations. A network entity, such as an entity in base station 105-b, LGW 205-b, or EPC 130-b, determines the latency mode of UE 115 (eg, UE 115-a). Some base stations 105-a and 105-b may be configured with collocated LGWs 205-a, 205-b. Regardless of the location of the LGW 205, SIPFULL is enabled based on the determined latency mode of the UE 115-a. The network entity selects an LGW for low latency IP packet routing based on, for example, APN or QoS. Alternatively, traffic may be routed within the common base station 105 or common service gateway 210 or via a direct backhaul (X2) link between the base stations 105-a and 105-b.

Description

Cross reference
[0001] This patent application is filed on Nov. 10, 2015, each assigned to the assignee of the present application, entitled "Selected Ip Ultra Ultra Low Latency", US Patent Application No. 14 937,017, and US Provisional Patent Application No. 62 / 078,210 by Wang et al., Entitled “Selected IP Flow Ultra Low Latency”, filed on November 11, 2014.

  [0002] The following relates generally to wireless communications, and more particularly to selected Internet Protocol (IP) flow ultra-low latency.

  [0003] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and the like. These systems may be multiple access systems that can support communication with multiple users by sharing available system resources (eg, time, frequency, and power). 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, and orthogonal frequency division multiple access (OFDMA) systems (eg, , Long Term Evolution (LTE® system).

  [0004] By way of example, a wireless multiple-access communication system can include a number of base stations, each supporting communication for multiple communication devices simultaneously, sometimes known as user equipment (UE). A base station may communicate with a communication device on a downlink channel (eg, for transmission from the base station to the UE) and an uplink channel (eg, for transmission from the UE to the base station).

  [0005] Data originating from or terminating at the UE may be routed through the base station and through the operator's core network. Thus, the path for data between any two UEs can be circuitous and can adversely affect end-to-end latency associated with such communications. Furthermore, routing cannot fully utilize UE capabilities.

  [0006] Systems, methods, and apparatus for reduced user plane latency are described. These may include techniques for addressing end-to-end user plane latency issues with selected Internet Protocol Flow Ultra Low Latency (SIPFULL). The network may enable SIPFULL for the UE, for example, depending on the capabilities and subscriptions of a particular UE. In some cases, SIPFULL may be enabled on an access point name (APN) unit basis. The network thus meets the UE's quality of service (QoS) requirements by routing bearer traffic through a local gateway or serving gateway, or by routing bearer traffic directly within a base station or between base stations. Can support.

  [0007] A method of wireless communication is described. The method includes determining a latency mode of the first UE and enabling low latency IP packet routing for the first UE based at least in part on the latency mode of the first UE. Selecting a local gateway (LGW) for low latency IP packet routing based at least in part on the low latency mode of the first UE.

  [0008] An apparatus for wireless communication is described. The apparatus enables low latency IP packet routing for a first UE based at least in part on means for determining a latency mode of the first UE and a latency mode of the first UE. Means for selecting and a local gateway (LGW) for low latency IP packet routing based at least in part on the low latency mode of the first UE.

  [0009] A further apparatus for wireless communication is described. The apparatus can include a processor, memory in electronic communication with the processor, and instructions stored in the memory. These instructions determine a latency mode of the first UE and enable low latency IP packet routing for the first UE based at least in part on the latency mode of the first UE, Based at least in part on the low latency mode of the UE, may be executable by the processor to select a local gateway (LGW) for low latency IP packet routing.

  [0010] A non-transitory computer readable medium storing code for wireless communication at a base station is described. The code determines a latency mode of the first UE and enables low latency IP packet routing for the first UE based at least in part on the latency mode of the first UE, Instructions may be included to select a local gateway (LGW) for low latency IP packet routing based at least in part on the low latency mode of the network.

  [0011] In some examples of the above-described method, apparatus, or non-transitory computer readable medium, low latency IP packet routing is enabled for an access point name (APN) associated with the first UE's latency mode. obtain. Additionally or alternatively, in some examples, the LGW is selected based on the APN.

  [0012] Some examples of the above-described method, apparatus, or non-transitory computer readable medium determine a QoS for each bearer configured for a first UE, and at least partially in the determined QoS It may further include features, means, or instructions for selecting an LGW based on it. Additionally or alternatively, in some examples, the LGW is collocated with the base station.

  [0013] In some examples of the methods, apparatus, or non-transitory computer readable media described above, the LGW is collocated with a serving gateway (SGW) in the core network. Additionally or alternatively, some examples may determine that the first UE and the second UE are connected to a common base station, and the second UE's latency mode is the first UE's latency. Based on determining that the latency mode of the second UE is the same as the latency mode of the first UE and determining the second UE and the second UE in the common base station Routing packet data traffic to and from other UEs.

  [0014] In some examples of the methods, apparatus, or non-transitory computer readable media described above, packet data traffic comprises IP packet data and routing is via the LGW. Additionally or alternatively, in some examples, the LGW is collocated with a common base station.

  [0015] In some examples of the methods, apparatus, or non-transitory computer readable media described above, the packet data traffic comprises packet data and the routing is in a packet data convergence protocol (PDCP) or lower layers. Additionally or alternatively, some examples determine that the first UE is connected to the first base station and the second UE is connected to the second base station, where the first And the second base station are communicating via a direct backhaul link. Some examples determine that the second UE's latency mode is the same as the first UE's latency mode, and a direct backhaul link between the first base station and the second base station. Routing packet data traffic between the first UE and the second UE via.

  [0016] In some examples of the methods, apparatus, or non-transitory computer readable media described above, the packet data traffic comprises IP packet data and routing is via the LGW. Additionally or alternatively, in some examples, the LGW includes a first LGW collocated with a first base station, selecting a second LGW collocated with a second base station; Routing packet data traffic through the first LGW and the second LGW.

  [0017] In some examples of the methods, apparatus, or non-transitory computer readable media described above, the LGW is collocated with a serving gateway (SGW) in the core network, and routing may be via the LGW. Additionally or alternatively, in some examples, packet data traffic includes packet data and routing is in packet data convergence protocol (PDCP) traffic or lower layers.

  [0018] Some examples of the above-described method, apparatus, or non-transitory computer-readable medium determine that the first UE and the second UE are connected to a common SGW, and the second UE's Further comprising a feature, means, or instruction for determining that the latency mode is the same as the latency mode of the first UE and receiving packets routed between the first UE and the second UE from the SGW; May be included. Additionally or alternatively, some examples identify a first UE handover from a source base station to a target base station and maintain service continuity for low latency IP packet routing during the handover. Can include.

  [0019] Some examples of the above method, apparatus, or non-transitory computer readable medium are features, means, or for sending a handover request that may include a low latency IP routing indication from a source base station to a target base station. Instructions may further be included. Additionally or alternatively, some examples may include receiving a handover acknowledgment with a low latency IP routing indication at the source base station from the target base station.

  [0020] Some examples of the above-described methods, apparatus, or non-transitory computer-readable media are provided by a source base station based at least in part on the target base station's ability to support low latency IP packet routing. It may further include features, means or instructions for selecting a target base station. Additionally or alternatively, some examples receive data at the source base station and send data to the first UE via the target base station using the IP address allocated by the LGW. And determining that the data transfer for the first UE is complete and receiving a UE context release from the target base station.

  [0021] Some examples of the above-described method, apparatus, or non-transitory computer-readable medium send a handover request with a low latency IP routing indication from a source base station to a target base station, and at the target base station It may further comprise features, means, or instructions for receiving a handover acknowledgment with a low latency IP routing indication and an IP address from the station and transmitting the IP address from the source base station to the UE. Additionally or alternatively, some examples include receiving a context request from the target base station at the source base station, sending a handover request from the source base station to the target base station in response to the context request, and a handover request. And receiving a handover acknowledgment from the target base station at the source base station. Additionally or alternatively, some examples send a status transfer message from the source base station to the target base station in response to a handover acknowledgment and source the context release following the status transfer message during a successful handover. Receiving from the target base station at the base station. Some examples of the methods, apparatus, or non-transitory computer readable media described above may further include features, means, or instructions for caching data at the LGW.

  [0022] A further method of wireless communication at the UE is also described. The method includes transmitting a latency mode signal to the network, receiving an authorization signal for low latency IP packet routing based at least in part on the latency mode signal, and at least receiving an authorization signal. Routing the packet according to the grant signal via a local gateway (LGW) based in part.

  [0023] A further apparatus for wireless communication at a UE is also described. The apparatus includes: means for transmitting a latency mode signal to the network; means for receiving a grant signal for low latency IP packet routing based at least in part on the latency mode signal; Based in part on means for routing packets according to a grant signal via a local gateway (LGW).

  [0024] A further apparatus for wireless communication at a UE is also described. The apparatus can include a processor, memory in electronic communication with the processor, and instructions stored in the memory. These instructions send a latency mode signal to the network, receive a grant signal for low latency IP packet routing based at least in part on the latency mode signal, and at least partially based on the grant signal It may be executable by the processor to route the packet according to the grant signal through the gateway (LGW).

  [0025] A further non-transitory computer readable medium storing code for wireless communication at the UE is also described. This code sends a latency mode signal to the network, receives a grant signal for low latency IP packet routing based at least in part on the latency mode signal, and based at least in part on the grant signal Instructions executable to route the packet according to the grant signal via (LGW) may be included.

  [0026] In some examples of the methods, apparatus, or non-transitory computer readable media described above, low latency IP packet routing is based on an access point name (APN) based on latency mode signals, or subscriber information, or both. ) To be authorized.

  [0027] Some examples of the above-described method, apparatus, or non-transitory computer-readable medium are for transmitting a QoS indication to a network, where the grant signal is based at least in part on the QoS indication. Further features, means, or instructions. Additionally or alternatively, some examples determine that the UE is connected to a common base station, send an intra-base station communication request to the network, and communicate with the UE via the common base station. Packet data traffic with the UE is routed within a common base station.

  [0028] Some examples of the above-described method, apparatus, or non-transitory computer readable medium transmit a measurement report to a source base station and perform service continuity during handover initiated based at least in part on the measurement report It may further include features, means, or instructions for maintaining gender. Additionally or alternatively, some examples utilize the IP address allocated by the source LGW to send uplink data to the target base station, and utilize the IP address allocated by the source LGW, Receiving downlink data from a target base station, wherein receiving a new IP address allocation from a target LGW associated with the target base station, where the downlink data can be routed through the source base station. obtain.

  [0029] Some examples of the above-described method, apparatus, or non-transitory computer-readable medium are for receiving a new IP address allocation from a target LGW associated with a target base station and an IP address allocated by the source LGW To transmit uplink data to the target base station, to receive downlink data from the target base station using an IP address allocated by the source LGW, where downlink data May further include features, means, or instructions for receiving from the mobility management entity (MME) an instruction to utilize a new IP address that may be routed through the source base station. Additionally or alternatively, some examples include receiving a new IP address allocated from a target LGW associated with the target base station, reestablishing a radio resource control (RRC) connection with the target base station; Using a new IP address allocated from the target LGW to communicate with the target base station.

  [0030] Some examples of the above-described method, apparatus, or non-transitory computer-readable medium receive a new IP address allocated from a target LGW associated with the target base station from the MME and RRC with the target base station. It may further include features, means, or instructions for re-establishing the connection and utilizing the new IP address allocated form-the-target LGW to communicate with the target base station.

  [0031] The foregoing has outlined rather broadly the features and technical advantages of the examples according to the present disclosure in order that the detailed description of the invention that follows may be better understood. Additional features and advantages are described below. The disclosed concepts and examples can be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both their organization and manner of operation, together with related advantages, will be better understood when considering the following description with reference to the accompanying drawings. Each of the figures is provided for purposes of illustration and description only and is not provided as a definition of the scope of the claims.

  [0032] A better understanding of the nature and advantages of the present disclosure may be realized by reference to the following drawings. In the appended figures, similar components or features may have the same reference label. In addition, various components of the same type can be distinguished by following the reference label with a dash and a second label that distinguishes between similar components. Where only the first reference label is used herein, the description is applicable to any of the similar components having the same first reference label, regardless of the second reference label. is there.

[0033] FIG. 7 is an illustration of an example wireless communication system in accordance with various aspects of the present disclosure. [0034] FIG. 7 illustrates an example of one or more wireless communication systems in accordance with various aspects of the disclosure. 1 illustrates an example of one or more wireless communication systems in accordance with various aspects of the present disclosure. FIG. 1 illustrates an example of one or more wireless communication systems in accordance with various aspects of the present disclosure. FIG. [0035] FIG. 7 illustrates an example call flow for supporting very low latency in accordance with various aspects of the disclosure. [0036] FIG. 8 illustrates an example call flow for supporting very low latency in accordance with various aspects of the disclosure. FIG. 4 illustrates an example call flow for supporting ultra-low latency according to various aspects of the disclosure. [0037] FIG. 7 illustrates an example call flow for handover to support ultra-low latency, according to various aspects of the disclosure. FIG. 4 illustrates an example call flow for handover to support ultra-low latency according to various aspects of the disclosure. FIG. 4 illustrates an example call flow for handover to support ultra-low latency according to various aspects of the disclosure. FIG. 4 illustrates an example call flow for handover to support ultra-low latency according to various aspects of the disclosure. [0038] FIG. 7 is a block diagram of a user equipment (UE) in accordance with various aspects of the present disclosure. [0039] FIG. 7 is a block diagram of a UE according to various aspects of the disclosure. [0040] FIG. 9 is a block diagram of a communication management module according to various aspects of the disclosure. [0041] FIG. 10 is a block diagram of a system including a UE according to various aspects of the disclosure. [0042] FIG. 7 is a block diagram of a network entity in accordance with various aspects of the present disclosure. [0043] FIG. 7 is a block diagram of a network entity in accordance with various aspects of the present disclosure. [0044] FIG. 7 is a block diagram of a low latency management module according to various aspects of the disclosure. [0045] FIG. 9 is a block diagram of a handover management module according to various aspects of the disclosure. [0046] FIG. 7 is a block diagram of a system including a base station configured in accordance with various aspects of the disclosure. [0047] FIG. 9 is a flowchart illustrating a method according to various aspects of the disclosure. [0048] FIG. 9 is a flowchart illustrating a method according to various aspects of the present disclosure. [0049] FIG. 9 is a flowchart illustrating a method according to various aspects of the present disclosure. [0050] FIG. 7 is a flowchart illustrating a method according to various aspects of the present disclosure. [0051] FIG. 9 is a flowchart illustrating a method according to various aspects of the disclosure. [0052] FIG. 9 is a flowchart illustrating a method according to various aspects of the present disclosure.

  [0053] Several factors may contribute to end-to-end latency within a wireless communication system. For example, each interface and each component between components can affect the latency of communication between devices. In addition to the latency associated with transmissions between user equipment (UE) and the base station, the physical interface between the base station and various entities in the core network may cause delays. For example, a backhaul link between a radio access network (RAN) (eg, a base station) with a core network and an entity may impart. Furthermore, physical interfaces between devices in the core network (eg, physical connections between gateways in the core network) can similarly introduce delays. However, modern communications often benefit from low latency operation or may require low latency operation than may be achievable from the RAN and by transmitting data through the core network. Furthermore, the UE can have advanced capabilities, such as ultra-low latency capabilities, and existing routing techniques cannot take advantage of these capabilities. For example, the network may not be aware of the UE capabilities and may route data regardless of the UE capabilities.

  [0054] This disclosure thus provides techniques that may allow some traffic in the system to be routed away from the core network and via alternative paths that may be available to various UEs. To do. These techniques may be described as a selected Internet Protocol (IP) for very low latency (SIPFULL). In various examples, traffic may be routed via a local gateway, within a serving gateway, within a base station, directly between base stations, and so on. Routing may depend on the latency mode of one or more UEs. For example, the network can determine the latency mode of the UE, and then the network can select an alternate data routing path. In some cases, the UE can inform the network about its capabilities. In some cases, the network, or network operator, can enable SIPFULL on an access point name (APN) basis for various UEs capable of SIPFULL operation.

  [0055] The network may also employ mobility procedures that support low latency (eg, SIPFULL) operation. For example, for a SIPFULL capable UE, the network, or network entity (eg, RAN), can maintain service continuity during handover in an attempt to ensure low latency operation. Such mobility procedures may include various methods of IP address utilization and allocation by different entities of the system.

  [0056] The following description provides examples and is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and configuration of the elements described without departing from the scope of the present disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the described methods may be performed in a different order than the described order, and various steps may be added, omitted, or combined. Also, features described in connection with some examples may be combined in other examples.

  [0057] FIG. 1 illustrates an example of a wireless communication system 100 in accordance with various aspects of the present disclosure. System 100 includes base station 105, UE 115, and core network 130. Core network 130 may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. Base station 105 interfaces with core network 130 through backhaul link 132 (eg, S1). Base station 105 may perform radio configuration and scheduling for communication with UE 115 or may operate under the control of a base station controller (not shown). In various examples, the base stations 105 are directly or indirectly (eg, through the core network 130) with each other via a backhaul link 134 (eg, X1 etc.), which can be a wired communication link or a wireless communication link. Can communicate.

  [0058] Base station 105 may communicate wirelessly with UE 115 via one or more base station antennas. Each base station 105 may provide communication coverage for a respective geographic coverage area 110. In some examples, base station 105 may be a base transceiver station, a radio base station, an access point, a radio transceiver, a Node B, an eNode B (eNB), a Home Node B, a Home eNode B, or some other suitable Sometimes called terminology. The geographic coverage area 110 for the base station 105 may be divided into sectors that comprise only a portion of the coverage area (not shown). The wireless communication system 100 may include different types of base stations 105 (eg, macro base stations or small cell base stations). There may be overlapping geographic coverage areas 110 for different technologies. In some examples, a local gateway (LGW) may be collocated with the base station 105, as described in more detail below.

  [0059] Base station 105 may be connected to core network 130 by an S1 interface. The core network 130 may include a mobility management entity (MME) 135, a home subscriber server (HSS) 140, a serving gateway (SGW) 145, and a packet data network (PDN) gateway (PGW) 150. It can be a core (EPC). User IP packets may be forwarded via SGW 145 that may itself be connected to PGW 150. The PGW 150 may provide IP address allocation as well as other functions. The PGW 150 may be connected to the network operator's IP service. The operator's IP service may include the Internet, an intranet, an IP Multimedia System (IMS), and a Packet-Switched (PS) Streaming Service (PSS). The functions of various network entities, including MME 135 and HSS 140, are described in further detail below.

  [0060] A macro cell generally covers a relatively large geographic area (eg, a few kilometers in radius) and may allow unrestricted access by UEs 115 that subscribe to the service of a network provider. A small cell is a low power base station that can operate in the same or different (eg, licensed, unlicensed, etc.) frequency band as compared to a macrocell. Small cells may include pico cells, femto cells, and micro cells, according to various examples. A pico cell may cover, for example, a small geographic area and may allow unrestricted access by UEs 115 subscribing to network provider services. A femto cell may also cover a small geographic area (eg, home), and UE 115 (eg, UE 115 in a closed subscriber group (CSG), home user) that has an association with the femto cell. Limited access by a UE 115, etc.). An eNB for a macro cell may be referred to as a macro eNB. An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB may support one or more (eg, 2, 3, 4, etc.) cells (eg, component carriers).

  [0061] The wireless communication system 100 may be capable of supporting synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately aligned in time. For asynchronous operation, base stations 105 may have different frame timings, and transmissions from different base stations 105 may not be time aligned. The techniques described herein may be used for either synchronous or asynchronous operations.

  [0062] A communication network that may accommodate some of the various disclosed examples may be a packet-based network that operates according to a layered protocol stack, and data in the user plane may be based on IP. A radio link control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. A medium access control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer can also use hybrid automatic repeat request (HARQ) to perform retransmissions at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer may establish, configure and maintain an RRC connection between the UE 115 and the base station 105. The RRC protocol layer may also be used for radio bearer core network 130 support for user plane data. At the physical (PHY) layer, transport channels can be mapped to physical channels.

  [0063] The UEs 115 may be distributed throughout the wireless communication system 100, and each UE 115 may be fixed or mobile. UE 115 is a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, A remote terminal, handset, user agent, mobile client, client, or some other suitable term may be included or so called by those skilled in the art. UE 115 may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, and so on. A UE may be able to communicate with various types of base stations and network equipment, including macro eNBs, small cell eNBs, relay base stations, and the like.

  [0064] The communication link 125 shown in the wireless communication system 100 may include an uplink (UL) transmission from the UE 115 to the base station 105, or a downlink (DL) transmission from the base station 105 to the UE 115. Downlink transmissions are sometimes referred to as forward link transmissions, and uplink transmissions are sometimes referred to as reverse link transmissions. Each communication link 125 may include one or more carriers, and each carrier may be a signal composed of multiple subcarriers (eg, waveform signals of different frequencies) modulated according to the various radio technologies described above. . Each modulated signal may be sent on a different subcarrier and may carry control information (eg, reference signal, control channel, etc.), overhead information, user data, etc. Communication link 125 may use frequency division duplex (FDD) operation (eg, using anti-spectral resources) or time division duplex (TDD) operation (eg, use unpaired spectrum resources). Two-way communication can be transmitted. Frame structures for FDD (eg, frame structure type 1) and TDD (eg, frame structure type 2) may be defined.

  [0065] The wireless communication system 100 may support operation on multiple cells or carriers, ie, a function sometimes referred to as carrier aggregation (CA) or multi-carrier operation. Carriers that can be represented by communication link 125 may be referred to as component carriers (CCs), layers, channels, and so on. The terms “carrier”, “component carrier”, “cell”, and “channel” may be used interchangeably herein. The UE 115 may be configured with multiple downlink CCs and one or multiple uplink CCs for carrier aggregation. Carrier aggregation may be used with both FDD component carriers and TDD component carriers.

  [0066] In some cases, data (eg, Internet or Voice over LTE (VoLTE) traffic) may be routed through the system through several intermediate entities. For example, data from UE 115 is routed to base station 105 via communication link 125 and then separated from base station 105 to core network 130 via backhaul link 132 (eg, S1 interface) via the Internet. To a user (not shown). The latency associated with this communication may be a function of different entities and physical connections between each end of the communication, eg, between the UE 115 and the receiver of data at the other end. , And may have a round trip time (RTT) on the order of 30 ms.

  [0067] However, in some cases, data may be routed over shorter paths using SIPFULL, which may reduce end-to-end latency. For example, data can be routed directly to the Internet via the LGW to avoid paths to and through the core network 130. In such cases, the latency is the transmission time interval (TTI) for transmission from UE 115 to the base station plus the delay associated with the HARQ RTT, the time for communication between base station 105 and LGW, and The time can be reduced to the time added for communication from the LGW to the Internet. With this approach, the delay associated with the backhaul 132 can be at least avoided, and this delay depends on the physical attributes of the backhaul 132 (eg, fiber or microwave) and can therefore be relatively large. . This is discussed more fully below with reference to FIGS. 2A-2C.

  [0068] In other cases, two UEs 115 may both be in the system 100, and data may be routed between the UEs without having to first navigate the core network. For example, two UEs 115 connected to a common base station 105 may have traffic between them routed in the base station 105 or LGW. In such a case, the latency may be reduced to a value equal to 2 (2) times the TTI plus HARQ RTT plus the time for communication between the base station 105 and the LGW. Again, using this approach, the delay associated with the backhaul 132 can be avoided. This is also discussed more fully below with reference to FIGS. 2A-2C.

  [0069] Unlike some other selective IP routing protocols, SIPFULL may depend on UE latency requirements and authorizations rather than best effort IP traffic offloading. In other words, the system 100 can determine the UE's latency mode, and the network can select the routing based on the UE's latency mode. In some cases, SIPFULL can be enabled in system 100 for a given UE 115 based on an access point name (APN), eg, SIPFULL determines latency requirements for UE 115. (Upon) can be activated.

  [0070] APN may be the name of a gateway between a wireless network and another computer network (eg, the Internet). For example, as opposed to a circuit switched voice connection, a UE 115 that makes a data connection may be configured with an APN that it communicates when accessing the network. The core network 130 server then determines what type of network connection is to be created (eg, what IP or Internet Protocol Multimedia System (IMS) address should be assigned, or what security method is used). APN can be examined to determine if it should be done. In other words, the APN can identify the packet data network (PDN) with which the UE 115 wishes to communicate. In addition to identifying the PDN, the APN may be used to define a service type (eg, wireless application protocol (WAP) server or multimedia messaging service (MMS)) provided by the PDN. In some examples, the HSS 140 may enable (eg, allow) SIPFULL on a per APN basis for the UE 115. Additionally or alternatively, the MME 135 may select the LGW on an APN unit basis for the UE 115. In other words, the MME 135 may select the LGW based on the QoS for each bearer configured for the UE 115. Once enabled, UE 115 may be charged for use of the LGW, which may be different from charges that accrue for normal (eg, non-SIPFULL operations).

  [0071] In some cases, UE 115 may be transferred from one base station 105 (eg, source base station) to another base station 105 (eg, target base station) using a mobility procedure, such as a handover. A network entity such as source base station 105 or MME 135 can identify the handover of UE 115 enabled for SIPFULL, and the network entity maintains service continuity for UE 115 and the latency requirements for UE 115 are met. You can make sure or try to make sure.

  [0072] FIGS. 2A-2C illustrate an example wireless communication system 200 for SIPFULL, in accordance with various aspects of the present disclosure. Wireless communication system 200 may include UE 115 and base station 105, which may be communicating via communication link 125 and may be an example of UE 115 and base station 105 described above with reference to FIG. . The wireless communication system 200 may include one or more LGWs 205 and an evolved packet core (EPC) 130-a. The EPC 130-a may be the exemplary core network 130 described above with reference to FIG. Evolved packet core 130-a may include SGW 210 and PGW 215, which may be examples of SGW 210 and PGW 140, respectively, in FIG. LGW 205 and PGW 215 may provide UE 115 with access to PDN (eg, the Internet) 220.

  [0073] The EPC 130-a may include an MME 135 (FIG. 1) and an HSS (FIG. 1). The MME may be a control node that handles signaling between the UE 115 and the EPC 130-a. For example, the MME may provide bearer and connection management to the UE 115. The MME may be responsible for tracking and paging, bearer activation and deactivation, and selection of serving gateway 210 or local gateway 205 for UE 115 for idle mode UE 115. In some examples, the MME may select the local gateway 205 on a per APN basis. In another example, the MME may select an LGW based on the QoS for each bearer. The MME can communicate with the base station 105, further authenticate the UE 115, and implement non-access layer (NAS) signaling with the UE 115. The HSS can store subscriber data, manage roaming restrictions, manage accessible APNs for subscribers, and associate subscribers with MMEs, among other functions.

  [0074] User IP packets sent through the EPC 130-a may be forwarded through the serving gateway 210. In accordance with the architecture of system 200, serving gateway 210 may be an aspect user plane and may serve as a mobility anchor for inter-eNB handover and handover between different radio access technologies (RATs). PGW 215 may provide connectivity to one or more external packet data networks, such as PDN 220. The PDN 220 may include the Internet, an intranet, an IP multimedia system (IMS), a packet switched (PS) streaming service (PSS), and / or other types of PDNs.

  [0075] When SIPFULL is enabled, user plane traffic between the UE 115 and the PDN 220-b is derived from the EPC 130-a to the SGi connection between the local gateway 205 base station 105-a and the PDN 220-a. Can be offloaded. In order to support bearer traffic over the SGi connection between the local gateway 205 and the PDN 220-a, the local gateway 205 can communicate with the serving gateway 210 via the S5 interface. SIP FULL is used for the PDN connection of UE 115 during connectivity activation if the MME determines that SIP FULL is allowed for the connection of UE 115 based on a set of network policies and / or subscription information for UE 115. Can be validated. Upon determining that SIPFULL is allowed for the connection, the MME may set up a SIPFULL bearer for the connection using the network address of the local gateway 205. The MME may communicate with the base station 105-a (eg, via an S1 control message), one or more operation administration and management (OAM) messages, or other communication sources based on the network address of the local gateway 205. Can be determined.

  [0076] As shown in FIG. 2A, some base stations 105, such as base station 105-a, may be configured with a collocated LGW 205. The base station 105-a can communicate with the neighbor base station 105-b using the X2 common control message. Thus, the base station 105-a can provide the network address of its local gateway 205 to the neighbor base station 105-b during X2 interface setup. As a result, UE 115-c connected to neighbor base station 105-b can be adapted to utilize SIPFULL by redirecting data traffic to PDN 220-a via local gateway 205. A network entity, such as an entity in base station 105-a, LGW 205, or EPC 130-a, can determine the latency mode of UE 115 (eg, UE 115-a). As shown in FIG. 2B, some base stations 105, such as base stations 105-a and 105-b, may be configured with a collocated LGW 205. In other examples, such as shown in FIG. 2C, the LGW 205 may be associated with or collocated with the SGW 210 and may be referred to as a stand-alone LGW.

  [0077] However, as described below with reference to FIG. 3, regardless of the location of the LGW 205, SIPFULL can be enabled and the LGW 205 can be selected on a per APN basis. For example, the network entity can enable low latency IP packet routing (eg, SIPFULL) for the APN of UE 115-a based on the latency mode, and the network entity can enable low latency IP packet routing based on the APN. LGW for can be selected. In some cases, the network entity may determine a QoS for each bearer configured for UE 115 and select an LGW based on the determined QoS.

  [0078] In addition or alternatively, traffic may be routed within the common base station 105. For example, traffic between UEs 115-a and 115-b may be routed within base station 105-a. For example, UE 115-a may request to establish communication with peer UE 115-b served by a common base station 105-a. For example, a network entity such as an entity in base station 105-a, LGW 205, or EPC 130-a may determine that UEs 115-a and 115-b are connected to a common base station 105-a. The network entity may also determine that UEs 115-a and 115-b have the same latency mode (eg, both are enabled for SIPFULL), which therefore uses base station 105-a to make UE115 Packet data traffic can be routed between -a and 115-b.

  [0079] In some examples, UE 115-a may determine that it is connected to a common base station with UE 115-b. The UE 115-a can therefore transmit the intra-base station communication request to the base station 105-a or to the EPC 130-a via the base station 105-a. UE 115-a may then communicate with UE 115-b, which may be upon receipt of a grant for intra-base station communication.

  [0080] In other examples, traffic between UEs 115 may be routed between base stations 105 without passing through EPC 130-a. For example, traffic between UEs 115-a and 115-c may be routed via an X2 interface between base stations 105-a and 105-b. As described above, the network entity may determine that UEs 115-a and 115-c are connected to base stations 105-a and 105-b, respectively. The network entity may also determine that UEs 115-a and 115-c have the same latency mode, so that it can communicate with UE 115-a via the X2 interface between base stations 105-a and 105-b. Packet data traffic can be routed between 115-c, or traffic can be routed between LGWs 205-a and 205-b.

  [0081] In yet a further example, traffic between UEs 115 may be routed via SGW 210 without passing through PGW 215. Thus, for example, traffic between UEs 115-b and 115-c may be routed via SGW 210 via base stations 105-a and 105-b and the S1 interface. Thus, the network entity can determine that UEs 115-b and 115-c are connected to a common SGW, as described above. The network entity may also determine that UEs 115-b and 115-c have the same latency mode, so it routes packet data traffic between UEs 115-a and 115-c via SGW 210. Or traffic can be routed between LGWs 205-a and 205-b. Routing between UEs 115 may be performed at the packet data convergence protocol (PDCP) layer, or lower layers. In some cases, the network entity may receive packets routed between UEs 115-a and 115-c from the SGW.

  [0082] In some examples, for example, content caching near the edge of the EPC 130-a may be employed to help reduce latency for content delivery. For example, LGW 205, SGW 210, or PGW 215 may include a local server for cached content. In another example, a standalone content server (not shown) may be included in EPC 130-b. Popular or frequently accessed content can be stored at these servers. For example, a network operator can build a cache at these servers based on requests from several UEs 115. Thus, in some examples, when a user performs a Domain Name System (DNS) lookup for content (eg, video) via UE 115, the DNS directs UE 115 to a cache at the local server of the network entity. Can do. This may further help reduce latency by avoiding backhaul transmission and processing delays, and may be employed with the SIPFULL procedure discussed above.

  [0083] Various SIPFULL procedures that may be implemented in the system 200 are described with reference to FIGS. 3-4B. FIG. 3 illustrates an example call flow 300 for supporting very low latency in accordance with various aspects of the present disclosure. Call flow 300 may include UE 115-d, which may be an example of UE 115 described above with reference to FIGS. The communication diagram 300 may also include a base station 105-c that may be an example of the base station 105 described above with reference to FIGS. 3 may further include LGW 205-d, MME 305, and HSS 310, which may be examples of LGW 205, MME 135, or HSS 140, respectively, described with reference to FIGS. 1-2C. The LGW 205-d may be variously located as described with reference to FIGS. 2A-2C.

  [0084] The UE 115-d may make an initial attach request 312 with the MME 305. The initial attach request 312 can optionally identify an APN for which SIPFULL can be granted for UE 115-d. In some examples, the UE 115-d can indicate a SIPFULL request in the initial attach request 312. Additionally or alternatively, the UE 115-d can identify the QoS requirements associated with the SIPFULL request in the initial attach request 312. MME 305 receives the request from UE 115-d and verifies whether UE 115-d is allowed to use SIPFULL for PDN connection with the requested APN based on subscription information for UE 115-d. can do. In some cases, the MME 305 may perform per flow based authorization for SIPFULL associated with the QoS requirements received from the UE 115-d. The MME 305 may receive subscription information for the UE 115-d from, for example, the HSS 310 to verify whether a PDN connection with the requested APN is allowed.

  [0085] Based on subscription information obtained from the HSS 310, the MME 305 may indicate whether traffic associated with the APN or other APNs may be permitted or prohibited. If the MME 305 determines that the UE 115-d is allowed to use SIPFULL for the associated APN, the MME 305 determines that the SIP FULL collocated LGW 205-d should be established for the UE 115-d. Can be directed 314. Additionally or alternatively, the MME 305 can select a stand-alone LGW 205-d for SIPFULL PDN connection establishment. In response, the base station 105-c can send an RRC connection reconfiguration message 316 to the UE 115-d. The RRC connection reconfiguration message 316 can configure the UE 115-d for a new PDN connection using SIPFULL by establishing a radio bearer with the UE 115-d. Thereafter, the base station 105-c may enable a direct user plane path 318 to the LGW 205-d for the UE 115-d. The UE 115-d can transmit and receive data via the data links 322 and 324 via the base station 105-c and LGW 205-d. In some examples, the SIP FULL service can be associated with increased costs to the user, so the local gateway 205-d is billed based on the amount of data offloaded using the SIP FULL service. A charging record 326 can be created.

  [0086] FIGS. 4A and 4B illustrate an example call flow 400 for supporting ultra-low latency in accordance with various aspects of the present disclosure. The example of FIG. 4A may include UEs 115-e and 115-f and base station 105-d, which may be examples of UE 115 and base station 105 described above with reference to FIGS. Call flow 400-a may also include MME 305-a and HSS 310-a, which may be examples of MME 135 or 305, or HSS 140 or 310, respectively, described with reference to FIGS.

  [0087] A first UE (eg, UE 115-f) may send a registration message 402, which may include a latency mode, to MME 305-a to obtain permission for SIPFULL or to enable SIPFULL. . In some examples, the registration request may be associated with an APN. Based on the subscriber information obtained from the HSS 310-a, the MME 305-a can either allow or reject the UE 115-f request for SIPFULL. When the MME 305-a permits the registration request, the MME 305-a can notify the base station 105-d of the permission.

  [0088] The second UE (eg, 115-e) may also send 404 a registration request to the MME 305-a to obtain SIPFULL functionality. Based on the authorization of the registration request issued from the second UE 115-e, the MME 305-a may store 406 information associated with the first and second UEs 115. In some examples, the stored UE information may include first and second UE identification (UEID), first and second UE IP addresses, and associated base station 105-d.

  [0089] A first UE (eg, UE 115-f) directs communication intended for a second UE (eg, UE 115-e) to establish an RRC connection with base station 105-d. Can 408. As soon as the base station 105-d receives the RRC connection request 408 and identifies the UE 115-e as the target of interest, it can forward the service request 412 to the MME 305-a. In response, the MME 305-a can detect 414 that the target UE 115-e shares a common base station 105-d with the first UE 115-f. In some examples, the MME 305-a may further determine that both the first UE 115-f and the second UE 115-e are authorized with the SIP FULL function based on subscriber data associated with each UE 115. Can do. Based on this determination, the MME 305-a can forward the detected information to the base station 105-d to establish intra-base station routing.

  [0090] Accordingly, the base station 105-d can page 415 to the second UE 115-e to establish a second RRC connection 416 with the base station 105-d. The first UE 115-f and the second UE 115-e may then perform inter-eNB communication via the base station 105-d without routing data to the core network 418.

  [0091] The example of FIG. 4B includes UEs 115-e and 115-f and base station 105-d, which may be examples of UE 115 and base station 105, described above with reference to FIGS. May be included. Call flow 400-b may also include MME 305-a and HSS 310-a, which may be MME 135 or 305, or HSS 140 or 310, respectively, described with reference to FIGS.

  [0092] The UE 115 registers its SIPFULL capability with the MME 305-a in steps 402-a and 404-a, respectively, as described above with reference to FIG. 4A. In some examples, the first UE 115-f may discover 422 that the second UE 115-f is located on a common base station 105-d. This discovery may be based on either the first or second UE 115 sending a message to the base station 105-d to discover a nearby UE 115 served by the base station 105-d. In another example, the first UE 115-f may change the base station 105-d to allow the second UE 115-e to discover the first UE 115-d on the base station 105-d. Broadcast or announce its presence via As a result, the first UE 115-f identifies the first UE's 115-f intention to establish communication with the second UE 115-e and establishes an RRC connection 424 with the base station 105-d. can do. In response, the base station 105-d pages 425 the second UE 115-e and prompts the second UE 115-e to establish an RRC connection 426 with the base station 105-d. Based on the established RRC connection, the first and second UEs 115 can establish the inter-eNB communication 428 via the base station 105-d without routing data packets through the core network.

  [0093] FIGS. 5A-5D illustrate an example call flow 500 for a handover to support ultra-low latency in accordance with various aspects of the disclosure. A similar procedure can be applied to handovers to support SIPTO (selected IP traffic offloading). The examples of FIGS. 5A-5D may be examples of UE 115, base station 105, LGW 205, and PDN 220 described above with reference to FIGS. 1-2C, UE 115-g, base station 105, and LGW 205. , PDN220-c.

  [0094] In the example of FIG. 5A, UE 115-g may maintain the IP address assigned by base station 105-e or LGW 205-e until the handover to base station 105-f is completed. UE 115-g may send measurement report 502 to source base station 105-e. Measurement report 502 may identify a mobility scenario that may relate to signal strength or channel quality between source base station 105-e and UE 115-g. Based on the measurement report 502, the source base station 105-e can send a handover request 504 to the target base station 105-f. In some examples, sending the handover request 504 comprises a low latency IP routing indication from the source base station 105-e to the target base 105-f. In another example, the handover request 504 may include a SIP FULL identifier for instructing the target base station 105-f to permit SIP FULL for the UE 115-g. Additionally or alternatively, the source base station 105-e may select the target base station based at least in part on the target base station's ability to support low latency IP packet routing.

  [0095] Based on receiving the handover request 504, the target base station 105-f may send a handover request acknowledgment (ACK) 506 to the source base station 105-e. The handover ACK 506 may comprise a low latency IP routing indication from the target base station 105-f at the source base station 105-e. In some examples, the source base station 105-e may send a status transfer message 508 to the target base station 105-f. The source base station 105-e may also issue a handoff command 512 to the UE 115-g to trigger a handoff from the source base station 105-e to the target base station 105-f. The extended access procedure 514 may thus be implemented between the UE 115-g and the target base station 105-f. As part of the extended access procedure, UE 115-g may initiate RRC re-establishment procedure 516 and send a handover complete message 518 to target base station 105-f.

  [0096] During handover, based on the destination IP address and the need to bypass ingress address filtering, the uplink data 522 from the UE 115-g is passed through the target base station 105-f to the PDN 220-c. Can be routed directly to 524. However, during this process, the UE 115-g can maintain the IP address previously assigned to it by the source local gateway 205-e. In some examples, uplink data 522 may be transmitted from target base station 105-f to source base station 105-e prior to 524 routed to PDN 220-c. Conversely, downlink data 526 from PDN 220-c addressed to UE 115-g using the previously assigned IP address is first routed to UE 115-g by passing through source base station 105-e. Can be done. Downlink data 526 may then be re-routed 528 to target base station 105-f prior to being transmitted from target base station 105-f to UE 115-g.

  [0097] Upon completion of data communication 534, the target base station 105-f or LGW 205-f may allocate a new or updated IP address to the UE 115-b. Target base station 105-f may detect completion of data communication by monitoring an inactivity timer associated with UE 115-g in some examples. Thus, the target base station 105-f can instruct the LGW 205-f for data completion and request a new IP address for the UE 115-g from the LGW 205-f. Additionally or alternatively, data completion may be detected by the source base station 105-e by monitoring inactivity time. In some examples, the source base station may instruct the target base station 105-f for data completion. In another example, upon completion of a pending data communication session, the UE 115-g itself can request a new IP address allocation 536 from the target local gateway 205-f. In some examples, source base station 105-e can then receive UE context release 538 and UE 115 -g can return to idle state 542. In some examples, a hysteresis timer is utilized to prevent rapid IP address assignment when UE 115-g shuttles between the coverage areas of source base station 105-e and target base station 105-f. Can be done.

  [0098] In the example of FIG. 5B, UE 115-g may continue to use the IP address assigned by source local gateway 205-e until the data communication session is completed. Communication in messages 502-a through 518-a may be similar to steps 502 through 518 described with reference to FIG. 5A. However, the UE 115-g may establish 544 a PDN connection with the target LGW 205-f when it forwards the handover complete message 518-a to the target base station 105-f. As a result, a new IP address associated with the target LGW 205-f may be assigned to the UE 115-g. Regardless of the new IP address assignment, until the completion of the data communication session 546, the UE 115-g may continue to utilize the previous IP address associated with the source local gateway 205-e.

  [0099] UE 115-g may receive a message 548 from MME 505 requesting UE 115-g to switch to a new IP address. Additionally or alternatively, the UE 115-g can request the MME 505 to switch to the new IP address once its buffered data has been completely transmitted through the previous IP address. Accordingly, UE 115-g may communicate 552 with target base station 105-f utilizing a new IP address associated with target local gateway 205-f. Additionally or alternatively, the MME 505 may further send a UE contest release command 554 to the source base station 105-e.

  [0100] In the example of FIG. 5C, UE 115-g may be assigned a new IP address from target LGW 205-f before initiating the handover procedure. As a result, when the handover process is completed, the UE 115-g can quickly switch to the new IP address. The UE 115-g can transmit the measurement report 502-b to the source base station 105-e. Measurement report 502 may identify a mobility scenario that may relate to signal strength or channel quality between source base station 105-e and UE 115-g. In some examples, receipt of the measurement report 502 may trigger a handover. Based on the measurement report 502, the source base station 105-e can send a handover request 504-b to the target base station 105-f.

  [0101] The target base station 105-f may receive a new IP address for the UE 115-g from the target local gateway 205-f. Accordingly, the target base station 105-f can allocate a new IP address 556 and send a handover request ACK message 558 to the source base station 105-e. The handover request ACK message may include, for example, a newly allocated IP address for UE 115-g. In response, the source base station 105-e may send a handover command 562 to the UE 115-g that may further comprise a newly allocated IP address. In one example, the source base station 105-e can send a status transfer message 564 to the target base station 105-f.

  [0102] Following the allocation of a new IP address, UE 115-g may initiate extended access procedure 566 and initiate RRC re-establishment procedure 568. In some examples, the UE 115-g sends a handover (or handoff) completion command 572 to the target base station 105-f and then utilizes the newly assigned IP address received from the target LGW 205-f. Thus, data communication 574 with the target base station 105-f can be established. As discussed above, in some examples, the target base station 105-f may issue a UE context release command 576 to the source base station 105-e.

  [0103] Next, in the example of FIG. 5D, the UE 115-g may complete the handover before the connection with the source base station 105-e is lost. The UE 115-g can transmit the measurement report 502-c to the source base station 105-e. UE 115-g may then determine 578 that the signal strength between source base station 105-e and UE 115-g is below a preconfigured threshold. In some examples, the network may identify threshold limits through RRC signaling and send to UE 115-g. Based on the detected signal quality, UE 115-g can initiate an extended access procedure 582 with target base station 105-f. Extended access procedure 582 may include the SIP FULL capability of UE 115-g. In accordance with this disclosure, the target base station 105-f can contact 584 to verify the SIP FULL capability of UE 115-g to MME 505.

  [0104] In some examples of this disclosure, the target base station 105-f may request a new IP address for the UE 115-g from the target LGW 205-f upon receiving a grant from the MME 505. The target base station 105-f can transmit the allocated IP address 586 to the UE 115-g. The target base station 105-f may also send a UE context release command 588 to the source base station 105-e. The source base station 105-e may send 592 a handover request 592 to the target base station based at least in part on the received UE context release 588. In some examples, the target base station 105-f can respond to the handover request 592 with a handover request ACK message 594. Continuously, the target base station 105-f can also issue an RRC connection re-establishment message 596 to the UE 115-g from which the UE 115-g can initiate the RRC re-establishment procedure 516-c. In one or more examples, the source base station 105-e can send a status transfer message 598 to the target base station 105-f.

  [0105] UE 115-g can thus establish data communication 522-b with target base station 105-f using the IP address allocated by target base station 105-f. In some examples, upon establishment of data communication with UE 115-g, target base station 105-f may send a UE context release 554-b message to source base station 105-e. When the IP address of UE 115-g is changed, the socket (eg, TCP socket) may close quickly in some cases, thereby causing data loss in the pipeline. In order to reduce data loss, the present disclosure may allow both IP addresses (ie, previous IP address and new IP address) to remain active during handover. In some examples, when the buffered data is transmitted through the previous IP address, UE 115-g can switch to the new IP address. Alternatively, UE 115-g can utilize the previous IP address until pending data transmission is complete. In such a case, the network can assign a new IP address prior to UE 115-g entering idle state. As a result, the socket associated with the previous IP address can be closed and the new socket associated with the new IP address can be opened.

  [0106] FIG. 6 shows a block diagram 600 of a UE 115-h configured for selected IP flow ultra-low latency according to various aspects of the disclosure. UE115-h may be an example of the aspect of UE115 demonstrated with reference to FIGS. The UE 115-h may include a receiver 605, a communication management module 610, and a transmitter 615. UE 115-h may also include a processor. Each of these components can communicate with each other.

  [0107] Receiver 605 may provide information such as packets, user data, or control information related to various information channels (eg, information related to control channels, data channels, and selected IP flow ultra-low latency, etc.). Can be received. Information may be passed to the communication management module 610 and to other components of the UE 115-h. In some examples, the receiver 605 can receive downlink data from the target base station utilizing an IP address allocated by the source LGW, where the downlink data is routed via the source base station. Routed. The receiver 605 can also receive downlink data from the target base station using the IP address allocated by the source LGW, where the downlink data is routed through the source base station. In some examples, the receiver 605 can receive data at the source base station.

  [0108] The communication management module 610 transmits a latency mode signal to the network, receives a grant signal for low latency IP packet routing based at least in part on the latency mode signal, and at least partially in the grant signal. Based on this, the packet can be routed according to the grant signal via the local gateway (LGW). In some cases, low latency IP packet routing is allowed for an APN based on latency mode signals, or subscriber information, or both. In some examples, the latency mode signal is a request for permission or activation of SIPFULL. Additionally or alternatively, the latency mode signal may be an indication that the UE 115-h can operate in a low latency mode.

  [0109] The transmitter 615 may transmit multiple signals received from other components of the UE 115-h. In some examples, transmitter 615 may be collocated with receiver 605 within a transceiver module. The transmitter 615 may include a single antenna or it may include multiple antennas. In some examples, the transmitter 615 can utilize the IP address allocated by the source LGW to transmit uplink data to the target base station. In some examples, the transmitter 615 can utilize the IP address allocated by the source LGW to transmit uplink data to the target base station. In another example, the transmitter 615 can communicate with the target base station using a new IP address allocated form the target LGW.

  [0110] FIG. 7 shows a block diagram 700 of UE 115-i for selected IP flow ultra-low latency, in accordance with various aspects of the present disclosure. UE115-i may be an example of the aspect of UE115 demonstrated with reference to FIGS. The UE 115-i may include a receiver 605-a, a communication management module 610-a, or a transmitter 615-a. UE 115-i may also include a processor. Each of these components can communicate with each other. The communication management module 610-a can also include a latency mode transmission module 705, a permission reception module 710, and a communication module 715.

  [0111] The receiver 605-a may receive information that may be passed to the communication management module 610-a and to other components of the UE 115-i. The communication management module 610-a can execute the operation described above with reference to FIG. The transmitter 615-a may transmit signals received from other components of the UE 115-i.

  [0112] The latency mode transmission module 705 may transmit a latency mode signal to the network as described above with reference to FIGS. The latency mode signal may be, for example, a request for SIPFULL authorization or validation. The grant receiving module 710 may be configured for low latency IP packet routing with respect to the APN based at least in part on latency mode signals, subscriber information, or both, as described above with reference to FIGS. A permission signal can be received. The communication module 715 can route packets according to the grant signal via the LGW based at least in part on the grant signal, as described above with reference to FIGS.

  [0113] FIG. 8 shows a block diagram 800 of a communication management module 610-b for selected IP flow ultra-low latency in accordance with various aspects of the present disclosure. The communication management module 610-b may be an example of the aspect of the communication management module 610 described with reference to FIGS. The communication management module 610-b may include a latency mode transmission module 705-a, a permission reception module 710-a, and a communication module 715-a. Each of these modules can perform the functions described above with reference to FIG. The communication management module 610-b includes a QoS identification module 805, an inter-base station identification module 810, a communication establishment module 815, a routing module 820, a measurement report module 825, a continuity establishment module 830, and an IP address allocation module. 835, an IP address directive module 840, and a communication re-establishment module 845 may be included.

  [0114] The QoS identification module 805 can send a QoS indication to the network, where the grant signal is at least partially in response to the QoS indication, as described above with reference to FIGS. Based. The inter-base station identification module 810 can determine that the UE is connected to a common base station, as described above with reference to FIGS. The communication establishment module 815 can transmit the intra-base station communication request to the network as described above with reference to FIGS.

  [0115] The routing module 820 can communicate with the UE via a common base station, and packet data traffic with the UE can be transmitted to the common base station as described above with reference to FIGS. Routed within the station. The routing module 820 can also communicate with the target base station using the new IP address allocated from the target LGW.

  [0116] The measurement report module 825 may transmit the measurement report to the source base station, as described above with reference to FIGS. The continuity establishment module 830 may maintain service continuity during a handover initiated based at least in part on the measurement report, as described above with reference to FIGS.

  [0117] The IP address allocation module 835 may receive a new IP address allocation from the target LGW associated with the target base station, as described above with reference to FIGS. The IP address allocation module 835 may also receive a new IP address allocation from the target LGW associated with the target base station. The IP address allocation module 835 may also receive a new IP address allocated from the target LGW associated with the target base station. The IP address allocation module 835 may also receive a new IP address allocated from the target LGW associated with the target base station from the MME.

  [0118] The IP address directivity module 840 may receive an instruction to use a new IP address from the MME, as described above with reference to FIGS. The communication re-establishment module 845 can re-establish the RRC connection with the target base station as described above with reference to FIGS. The communication re-establishment module 845 can also re-establish a radio resource control (RRC) connection with the target base station.

  [0119] A component of UE 115-h, UE 115-i, or communication management module 610-b is at least one specific adapted to perform some or all of the applicable functions in hardware. It can be implemented individually or collectively using an application specific integrated circuit (ASIC). Alternatively, those functions may be performed by one or more other processing units (or cores) on at least one integrated circuit (IC). In other embodiments, other types of integrated circuits (eg, structured / platform ASIC, field programmable gate array (FPGA), or another semi-custom IC) that can be programmed in any manner known in the art. Can be used. The functionality of each unit may also be implemented in whole or in part using instructions embedded in memory formatted to be executed by one or more general purpose or application specific processors.

  [0120] FIG. 9 illustrates a system 900 that includes a UE 115 configured for selected IP flow ultra-low latency according to various aspects of the disclosure. System 900 can include UE 115-j, which can be an example of UE 115 described above with reference to FIGS. The UE 115-j may include a communication management module 910 that may be an example of the communication management module 610 described with reference to FIGS. UE 115-j may also include a service maintenance module 925. UE 115-j may also include components for two-way voice and data communication, including components for transmitting communications and components for receiving communications. For example, UE 115-j may communicate bi-directionally with UE 115-k or base station 105-g.

  [0121] In some examples, the service maintenance module 925 may receive an instruction from the MME to utilize a new IP address, as described above with reference to FIGS. Additionally or alternatively, when the service maintenance module 925 should switch from the assigned IP address before the UE 115-j is associated with the source local gateway to the newly assigned IP address associated with the target local gateway during the handover period Can be determined. In one or more examples, the service maintenance module 925 may assist in maintaining service continuity related to low latency IP packet routing during a handover procedure.

  [0122] The UE 115-j may also include a processor module 905, a memory 915 (including software (SW) 920), a transceiver module 935, and one or more antennas 940, each of which , May communicate with each other directly (eg, via bus 945) or indirectly. The transceiver module 935 may communicate bi-directionally with one or more networks via an antenna 940 or a wire drink or wireless link, as described above. For example, the transceiver module 935 may communicate bi-directionally with the base station 105 or another UE 115. Transceiver module 935 may include a modem for modulating the packet, providing the modulated packet to antenna 940 for transmission, and demodulating the packet received from antenna 940. Although UE 115-j may include a single antenna 940, UE 115-j may also have multiple antennas 940 capable of transmitting or receiving multiple wireless transmissions simultaneously.

  [0123] Memory 915 may include random access memory (RAM) and read only memory (ROM). Memory 915, when executed, includes computer-readable, computer-executable software / firmware that includes instructions that, when executed, cause processor module 905 to perform various functions described herein (eg, selected IP flow ultra-low latency, etc.) A code 920 can be stored. Alternatively, software / firmware code 920 may not be directly executable by processor module 905, but may cause a computer to perform the functions described herein (eg, when compiled and executed). it can. The processor module 905 may include intelligent hardware devices (eg, central processing unit (CPU), microcontroller, ASIC, etc.).

  [0124] FIG. 10 shows a block diagram 1000 of network entities configured for selected IP flow ultra-low latency, according to various aspects of the disclosure. The network entity may generally be described in terms of the base station 105-h, but the functions described with reference to FIG. 10 may be implemented by LGW, SGW, MME, etc. as described above. I want you to understand that. Accordingly, the base station 105-h or the network entity may be an example of the aspects of the base station 105, LGW 205, SGW 145 or 210, or MME 135 or 305 described with reference to FIGS. Base station 105-h may include a receiver 1005, a network communication management module 1010, and a transmitter 1015. Base station 105-h may also include a processor. Each of these components can communicate with each other.

  [0125] The receiver 1005 may receive information such as packets, user data, or control information related to various information channels (eg, information related to control channels, data channels, and selected IP flow ultra-low latency). Can be received. Information may be passed to the network communication management module 1010 and to other components of the base station 105-h. In some examples, the receiver 1005 may be an aspect of a source base station that can receive downlink data from a target base station utilizing an IP address allocated by the source LGW, where The downlink data is routed through the source base station. In some examples, the receiver 1005 can receive downlink data from the target base station utilizing an IP address allocated by the source LGW, where the downlink data is routed through the source base station. Routed. In some examples, the receiver 1005 may receive data at the source base station.

  [0126] The network communication management module 1010 determines a latency mode of the first UE, and based on at least in part on the latency mode of the first UE, the low latency IP packet routing (low latency IP) of the first UE. packet routing the first UE) can be enabled and the LGW for low latency IP packet routing can be selected based at least in part on the low latency mode of the first UE. In some examples, low latency IP packet routing may be enabled for the APN associated with the latency mode of the first UE. Further, the LGW can be selected based on the APN.

  [0127] The transmitter 1015 may transmit signals received from other components of the base station 105-h. In some embodiments, the transmitter 1015 may be collocated with the receiver 1005 within the transceiver module. The transmitter 1015 can include a single antenna, or it can include several antennas. In some examples, transmitter 1015 may be an aspect of a source base station, which may transmit uplink data to a target base station utilizing an IP address allocated by the source LGW. In some examples, the transmitter 1015 may transmit uplink data to the target base station using the IP address allocated by the source LGW as part of the handover procedure. In some examples, the transmitter 1015 can communicate with the target base station utilizing the new IP address allocated form-the-target LGW.

  [0128] FIG. 11 shows a block diagram 1100 of network entities for selected IP flow ultra-low latency in accordance with various aspects of the present disclosure. The network entity may be generally described in terms of a base station 105-i that may be an example of aspects of the base station 105 described with reference to FIGS. Alternatively, the functionality described with reference base station 105-i may be implemented in a network entity other than the base station, such as LGW 205, SGW 145 or 210, or MME 135 or 305 described in the previous figure. . The base station 105-i may include a receiver 1005-a, a network communication management module 1010-a, or a transmitter 1015-a. The network communication module 1010-a may include a low latency management module 1102 and a handover management module 1104. Base station 105-i may also include a processor. Each of these components can communicate with each other. The low latency management module 1102 may include a mode identification module 1105, a low latency authentication module 1110, and a local gateway selection module 1115.

  [0129] The receiver 1005-a may receive information that may be passed to the network communication management module 1010-a and to other components of the base station 105-i. The network communication management module 1010-a can execute the operation described above with reference to FIG. The low latency module 1102 and its various submodules can manage SIPFULL operations. The handover management module 1104 can manage or implement a handover operation of a SIP FULL allowed UE, for example. The transmitter 1015-a can transmit signals received from other components of the base station 105-i.

  [0130] The mode identification module 1105 may determine the latency mode of the first UE, as described above with reference to FIGS. For example, the mode identification module 1105 can determine whether the UE is SIPFULL capable or authorized for SIPFULL. The low latency grant module 1110 enables low latency IP packet routing for the first UE based at least in part on the latency mode of the first UE, as described above with reference to FIGS. Can be In some cases, low latency IP packet routing may be enabled for the APN associated with the first UE's latency mode.

  [0131] The local gateway selection module 1115, as described above with reference to FIGS. 2-5, is based on the low latency mode of the first UE, the local gateway (LGW) for low latency IP packet routing. ) Can be selected. In some cases, the LGW may be selected based on the APN. The local gateway selection module 1115 can also select an LGW based on the determined QoS. In some examples, the LGW selected by the local gateway selection module 1115 includes a first LGW that is collocated with a first base station. The local gateway selection module 1115 may also select a second LGW that is collocated with the second base station.

  [0132] FIG. 12A shows a block diagram 1200-a of a low latency management module 1102-a for selected IP flow ultra-low latency according to various aspects of the disclosure. The low latency management module 1102-a may be an example of the aspect of the low latency management module 1102 described with reference to FIG. In some examples, the low latency management module 1102-a is a component of the base station 105 as described in the preceding figures. In other examples, the low latency management module 1102-a is a component of the MME, such as the MME 135 or 305 described in the previous figure. In yet another example, the low latency management module 1102-a may be an example of an aspect of the LGW 205 or SGW 145 or 210 described in the previous figure.

  [0133] The low latency management module 1102-a may include a mode identification module 1105-a, a low latency authentication module 1110-a, and a local gateway selection module 1115-a. Each of these modules can perform the functions described above with reference to FIG. The low latency management module 1102-a includes a QoS determination module 1205, a communication management module 1210, a shared eNB connectivity module 1215, a latency mode identification module 1220, a packet routing module 1225, a neighbor eNB connectivity module 1230, A shared gateway identification module 1235 can also be included.

  [0134] The QoS determination module 1205 may determine the QoS for each bearer configured for the first UE, as described above with reference to FIGS. The communication management module 1210 may be configured such that the LGW can be collocated with the base station, as described above with reference to FIGS. In some examples, the LGW may be collocated with the SGW in the core network. The shared eNB connectivity module 1215 may determine that the first UE and the second UE are connected to a common base station, as described above with reference to FIGS.

  [0135] The latency mode identification module 1220 may determine that the latency mode of the second UE is the same as the latency mode of the first UE, as described above with reference to FIGS. it can. The latency mode identification module 1220 can determine that the latency mode of the second UE is the same as the latency mode of the first UE.

  [0136] The packet routing module 1225 determines at least that the latency mode of the second UE is the same as the latency mode of the first UE, as described above with reference to FIGS. Based in part, packet data traffic can be routed between the first UE and the second UE within a common base station. In some examples, packet data traffic includes IP packet data and routing may be via the LGW. Packet data traffic may include packet data and routing may be at the packet data convergence protocol (PDCP) layer or lower layers. In some examples, the LGW may be collocated with a common base station.

  [0137] In addition or as an alternative, the packet routing module 1225 transmits packets between the first UE and the second UE via a direct backhaul link between the first base station and the second base station. Data traffic can be routed. In some examples, packet data traffic includes IP packet data and routing may be via the LGW. In some examples, the packet routing module 1225 may route packet data traffic via the first and second LGW. The LGW may be collocated with a serving gateway (SGW) in the core network, for example, and routing may be through the LGW. The packet routing module 1225 may route packet data traffic between the first UE and the second UE in the SGW, in another example. In yet a further example, the packet routing module 1225 may cache data at the LGW or SGW as described above with reference to FIGS. The packet routing module 1225 may receive packets routed between the first UE and the second UE from the SGW in some examples.

  [0138] The neighbor eNB connectivity module 1230 can determine that the first UE is connected to the first base station and the second UE is connected to the second base station, where The first and second base stations are communicating via a direct backhaul link as described above with reference to FIGS. In some examples, the shared gateway identification module 1235 may determine that the first and second UEs are connected to a common SGW, as described above with reference to FIGS. it can.

  [0139] FIG. 12B shows a block diagram 1200-b of a handover management module 1104-a for selected IP flow ultra-low latency according to various aspects of the disclosure. The handover management module 1104-a may be an example of the aspect of the handover management module 1104 described with reference to FIG. In some examples, the handover management module 1104-a is a component of the base station 105 as described in the previous figure. In other examples, the handover management module 1104-a is a component of the MME, such as the MME 135 or 305 described in the previous figure. In yet another example, the handover management module 1104-a may be an example of an aspect of LGW 205 or SGW 145 or 210.

  [0140] The handover management module 1104-a includes a handover identification module 1240, a service continuity module 1245, a handover request transmission module 1250, a handover acknowledgment module 1255, a target base station selection module 1260, a data transmission module 1265, and a transmission completion module 1270. , A context release module 1275, an IP address assignment module 1280, and a context request module 1285.

  [0141] The handover identification module 1240 may identify the handover of the first UE from the source base station to the target base station, as described above with reference to FIGS. The service continuity module 1245 may help maintain service continuity for low latency IP packet routing during handover, as described above with reference to FIGS. The handover request transmission module 1250 sends or identifies a handover request including a low latency IP routing indication from the source base station to the target base station, as described above with reference to FIGS. Can do. The handover request transmission module 1250 may also send or identify a handover request that may include a low latency IP routing indication from the source base station to the target base station. In some examples, the handover request transmission module 1250 can send or identify a handover request from the source base station to the target base station in response to the context request.

  [0142] The handover acknowledgment module 1255 receives a handover acknowledgment that may include a low latency IP routing indication from the target base station at the source base station, as described above with reference to FIGS. Or can be recognized. The handover acknowledgment module 1255 may also receive or recognize a handover acknowledgment at the source base station that may include a low latency IP routing indication and an IP address from the target base station. The handover acknowledgment module 1255 may receive or recognize a handover acknowledgment from the target base station at the source base station, in some examples, in response to the handover request.

  [0143] The target base station selection module 1260 determines the source base station based on the target base station's ability to support low latency IP packet routing, as described above with reference to FIGS. The target base station of or of the source base station can be selected. The data transmission module 1265 transmits data to the first UE via the target base station using the IP address allocated by the LGW as described above with reference to FIGS. Can do.

  [0144] The transmission completion module 1270 may determine that the data transfer to the first UE has been completed, as described above with reference to FIGS. In some examples, the transmission completion module may send a status transfer message, eg, in response to a handover acknowledgment, as described above with reference to FIGS. The context release module 1275 can receive or recognize a UE context release from the target base station, as described above with reference to FIGS. The context release module 1275 may also receive or recognize a context release at the source base station from the target base station following the status transfer message and upon successful handover.

  [0145] The IP address assignment module 1280 may send an IP address from the source base station to the UE, as described above with reference to FIGS. The context request module 1285 may receive a context request at the source base station from the target base station, as described above with reference to FIGS.

  [0146] The components of the base station 105-h, the base station 105-i, the low latency management module 1102-a, or the handover management module 1104-a execute part or all of the applicable functions in hardware. It can be implemented individually or collectively using at least one ASIC adapted to do so. Alternatively, those functions may be performed on at least one IC by one or more other processing units (or cores). In other embodiments, other types of integrated circuits (eg, structured / platform ASIC, FPGA, or another semi-custom IC) that can be programmed in any manner known in the art may be used. The functionality of each unit may also be implemented in whole or in part using instructions embedded in memory formatted to be executed by one or more general purpose or application specific processors.

  [0147] FIG. 13 illustrates a system 1300 that includes a base station 105 configured for selected IP flow ultra-low latency in accordance with various aspects of the present disclosure. System 1300 can include a base station 105-j, which can be an example of base station 105 described above with reference to FIGS. The base station 105-j may include a network communication management module 1310 that may be an example of the network communication management module 1010 described with reference to FIGS. Base station 105-j may also include components for two-way voice and data communication, including components for transmitting communications and components for receiving communications. For example, base station 105-j may communicate bi-directionally with UE 115-1 or UE 115-m.

  [0148] In some cases, base station 105-j may have one or more wired backhaul links. Base station 105-j may have a wired backhaul link (eg, an S1 interface, etc.) to core network 130-d, which may be an example of core network or EPC 130 described with reference to the previous figure. Base station 105-j can also communicate with other base stations 105, such as base station 105-k and base station 105-l, via an inter-base station backhaul link (eg, an X2 interface). Each of the base stations 105 can communicate with the UE 115 using the same or different wireless communication technologies. In some cases, base station 105-j can also communicate with other base stations, such as 105-k or 105-l, using base station communication module 1325. In some embodiments, the base station communication module 1325 can provide an X2 interface within LTE / LTE-A wireless communication network technology to communicate between some of the base stations 105. In some embodiments, base station 105-j can communicate with other base stations through core network 130. In some cases, the base station 105-j can communicate with the core network 130 through the network communication module 1330.

  [0149] Base station 105-j may include a processor module 1305, a memory 1315 (including software (SW) 1320), a transceiver module 1335, and an antenna 1340, each of which (eg, bus system 1345). May be communicating with each other directly or indirectly. Transceiver module 1335 may be configured to communicate bi-directionally with UE 115, which may be a multi-mode device, via antenna 1340. Transceiver module 1335 (or other components of base station 105-k) is also configured to communicate bi-directionally with one or more other base stations (not shown) via antenna 1340. obtain. Transceiver module 1335 may include a modem configured to modulate the packet, provide the modulated packet to antenna 1340 for transmission, and demodulate the packet received from antenna 1340. Base station 105-j may include a plurality of transceiver modules 1335, each with one or more associated antennas 1340. The transceiver module may be an example of the combined receiver 1005 and transmitter 1015 of FIG.

  [0150] Memory 1315 may include RAM and ROM. Memory 1315 also includes instructions that, when executed, cause processor module 1305 to perform various functions described herein (eg, selected IP flow ultra-low latency, message routing, etc.). Computer readable, computer executable software code 1320 can be stored. Alternatively, software 1320 may not be directly executable by processor module 1305, but may be configured to cause a computer to perform the functions described herein, for example, when compiled and executed. The processor module 1305 may include intelligent hardware devices such as a CPU, microcontroller, ASIC, and the like. The processor module 1305 may include various dedicated processors such as encoders, queue processing modules, baseband processors, wireless head controllers, digital signal processors (DSPs) and the like.

  [0151] The base station communication module 1325 may manage communication with other base stations 105. The communication management module may include a controller or scheduler for controlling communication with the UE 115 in cooperation with other base stations 105. For example, base station communication module 1325 may coordinate scheduling for transmission to UE 115 for various interference mitigation techniques such as beamforming or joint transmission.

  [0152] FIG. 14 shows a flowchart illustrating a method 1400 for selected IP flow ultra-low latency according to various aspects of the disclosure. The operations of method 1400 may be implemented by a network entity including a base station, MME, LGW, SGW, etc., or components thereof, as described with reference to FIGS. For example, the operations of method 1400 may be performed by network communication management module 1010 as described with reference to FIGS. In some examples, the network entity may execute a set of code for controlling functional elements of the network entity to perform the functions described below. Additionally or alternatively, the network entity can perform the aspect functions described below using dedicated hardware.

  [0153] At block 1405, the network entity may determine the latency mode of the first UE, as described above with reference to FIGS. In some examples, the operation of block 1405 may be performed by the mode identification module 1105 as described above with reference to FIG.

  [0154] At block 1410, the network entity may configure a low for the first UE based at least in part on the latency mode of the first UE, as described above with reference to FIGS. Latency IP packet routing can be enabled. In some cases, low latency IP packet routing may be enabled for the APN associated with the first UE's latency mode. In some examples, the operation of block 1410 may be performed by the low latency authentication module 1110 as described above with reference to FIG.

  [0155] At block 1415, the network entity for low latency IP packet routing based at least in part on the low latency mode of the first UE, as described above with reference to FIGS. Local gateways (LGW) can be selected. In some cases, the LGW may be selected based on the APN. In some examples, the operation of block 1415 may be performed by the local gateway selection module 1115, as described above with reference to FIG.

  [0156] FIG. 15 shows a flowchart illustrating a method 1500 for selected IP flow ultra-low latency according to various aspects of the disclosure. The operations of method 1800 may be implemented by a network entity including a base station, MME, LGW, SGW, etc., as described with reference to FIGS. For example, the operations of method 1500 may be performed by network communication management module 1010 as described with reference to FIGS. In some examples, the network entity may execute a set of code for controlling functional elements of the network entity to perform the functions described below. Additionally or alternatively, the network entity can perform the aspect functions described below using dedicated hardware. The method 1500 may also incorporate aspects of the method 1400 of FIG.

  [0157] At block 1505, the network entity may determine the latency mode of the first UE, as described above with reference to FIGS. In some examples, the operation of block 1505 may be performed by the mode identification module 1105, as described above with reference to FIG.

  [0158] At block 1510, the network entity may configure a low for the first AP based at least in part on the latency mode of the first UE, as described above with reference to FIGS. Latency IP packet routing can be enabled. In some cases, low latency IP packet routing may be enabled for the APN associated with the first UE's latency mode. In some examples, the operation of block 1510 may be performed by the low latency authentication module 1110 as described above with reference to FIG.

  [0159] At block 1515, the network entity may determine a QoS for each bearer configured for the first UE, as described above with reference to FIGS. In some examples, the operation of block 1515 may be performed by the QoS determination module 1205 as described above with reference to FIG.

  [0160] At block 1520, the network entity may be based at least in part on the low latency mode of the first UE and the determined QoS, as described above with reference to FIGS. A local gateway (LGW) for low latency IP packet routing can be selected. In some cases, the LGW may be similarly selected based on the APN. In some examples, the operation of block 1520 may be performed by the local gateway selection module 1115, as described above with reference to FIG. In some examples, the network entity may also cache data at the LGW.

  [0161] FIG. 16 shows a flowchart illustrating a method 1600 for selected IP flow ultra-low latency according to various aspects of the disclosure. The operations of method 1600 may be implemented by a network entity including a base station, MME, LGW, SGW, etc., as described with reference to FIGS. For example, the operations of method 1600 may be performed by network communication management module 1010 as described with reference to FIGS. In some examples, the network entity may execute a set of code for controlling functional elements of the network entity to perform the functions described below. Additionally or alternatively, the network entity can perform the aspect functions described below using dedicated hardware. The method 1600 may also incorporate aspects of the method 1400 and method 1500 of FIG.

  [0162] At block 1605, the network entity may determine the latency mode of the first UE, as described above with reference to FIGS. In some examples, the operation of block 1605 may be performed by the mode identification module 1105 as described above with reference to FIG.

  [0163] At block 1610, the network entity may configure a low for the first UE based at least in part on the latency mode of the first UE, as described above with reference to FIGS. Latency IP packet routing can be enabled. In some cases, low latency IP packet routing may be enabled for the APN associated with the first UE's latency mode. In some examples, the operation of block 1610 may be performed by the low latency authentication module 1110 as described above with reference to FIG.

  [0164] At block 1615, the network entity may perform low latency IP packet routing based at least in part on the low latency mode of the first UE, as described above with reference to FIGS. Local gateways (LGW) can be selected. In some cases, the LGW may be similarly selected based on the APN. In some examples, the operation of block 1615 may be performed by the local gateway selection module 1115, as described above with reference to FIG.

  [0165] At block 1620, the network entity determines that the first UE and the second UE are connected to a common base station, as described above with reference to FIGS. Can do. In some examples, the operation of block 1620 may be performed by the shared eNB connectivity module 1215 as described above with reference to FIG.

  [0166] At block 1625, the network entity determines that the latency mode of the second UE is the same as the latency mode of the first UE, as described above with reference to FIGS. Can do. In some examples, the operation of block 1625 may be performed by the latency mode identification module 1220 as described above with reference to FIG.

  [0167] At block 1630, the network entity determines that the latency mode of the second UE is the same as the latency mode of the first UE, as described above with reference to FIGS. Based at least in part, packet data traffic can be routed between the first UE and the second UE within a common base station. In some examples, the operation of block 1630 may be performed by the packet routing module 1225 as described above with reference to FIG.

  [0168] The method includes determining a quality of service (QoS) for each bearer configured for the first UE and selecting an LGW based at least in part on the determined QoS. You can also. In some examples, the method determines that the first UE and the second UE are connected to a common base station, and the latency mode of the second UE is the latency mode of the first UE. And determining that the second UE's latency mode is the same as the first UE's latency mode and the first UE and the second UE within the common base station. Routing packet data traffic to and from the UE. In another example, the method determines that a first UE is connected to a first base station and a second UE is connected to a second base station, where the first and Determining that the second UE's latency mode is the same as the first UE's latency mode, in which the second base station is communicating via the direct backhaul link; Routing packet data traffic between the first UE and the second UE via a direct backhaul link between the two base stations. In some cases, the routing is via the LGW, the LGW comprises a first LGW that is co-located with the first base station, and the method is to select a second LGW that is co-located with the second base station. And routing packet data traffic via the first LGW and the second LGW.

  [0169] The method also determines that the first UE and the second UE are connected to a common service gateway (SGW), and the latency mode of the second UE is the latency of the first UE. Determining to be the same as the mode and receiving packets routed between the first UE and the second UE from the SGW. In some cases, the method identifies a first UE handover from a source base station to a target base station, maintains service continuity for low latency IP packet routing during the handover, and low latency IP. Sending a handover request comprising a routing indication from the source base station to the target base station and receiving a handover acknowledgment comprising a low latency IP routing indication from the target base station at the source base station. In a further example, the method includes selecting a target base station by a source base station based at least in part on the target base station's ability to support low latency IP packet routing, and providing a low latency IP routing indication. Sending a handover request comprising a source base station to a target base station; receiving a handover acknowledgment comprising a low latency IP routing indication and an IP address from the target base station at the source base station; Sending an IP address to the UE.

  [0170] FIG. 17 shows a flowchart illustrating a method 1700 for selected IP flow ultra-low latency according to various aspects of the disclosure. The operations of method 1700 may be implemented by a UE or its components as described with reference to FIGS. For example, the operations of method 1700 may be performed by communication management module 610 as described with reference to FIGS. In some examples, the UE may execute a set of codes for controlling functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may perform the aspect functions described below using dedicated hardware.

  [0171] At block 1705, the UE may send a latency mode signal to the network as described above with reference to FIGS. In some examples, the operation of block 1705 may be performed by the latency mode transmission module 705, as described above with reference to FIG.

  [0172] At block 1710, the UE receives a grant signal for low latency IP packet routing based at least in part on the latency mode signal, as described above with reference to FIGS. be able to. In some cases, low latency IP packet routing may be allowed for an APN based on latency mode signals, or subscriber information, or both. In some examples, the operation of block 1710 may be performed by the permission receiving module 710 as described above with reference to FIG.

  [0173] In block 1715, the UE routes the packet according to the grant signal via the local gateway (LGW) based at least in part on the grant signal, as described above with reference to FIGS. can do. In some examples, the operation of block 1715 may be performed by the communication module 715, as described above with reference to FIG.

  [0174] FIG. 18 shows a flowchart illustrating a method 1800 for selected IP flow ultra-low latency according to various aspects of the disclosure. The operations of method 1800 may be implemented by a UE or its components as described with reference to FIGS. For example, the operations of method 1800 may be performed by communication management module 610 as described with reference to FIGS. In some examples, the UE 115 may execute a set of codes for controlling functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may perform the aspect functions described below using dedicated hardware.

  [0175] At block 1805, the UE may send a latency mode signal to the network as described above with reference to FIGS. In some examples, the operation of block 1805 may be performed by the latency mode transmission module 705, as described above with reference to FIG.

  [0176] At block 1810, the UE receives a grant signal for low latency IP packet routing based at least in part on the latency mode signal, as described above with reference to FIGS. be able to. In some cases, low latency IP packet routing may be allowed for an APN based on latency mode signals, or subscriber information, or both. In some examples, the operation of block 1810 may be performed by the permission receiving module 710 as described above with reference to FIG.

  [0177] In block 1815, the UE routes the packet according to the grant signal via the local gateway (LGW) based at least in part on the grant signal, as described above with reference to FIGS. can do. In some examples, the operation of block 1815 may be performed by the communication module 715, as described above with reference to FIG.

  [0178] At block 1820, the UE may determine that the UE is connected to a common base station, as described above with reference to FIGS. In some examples, the operation of block 1820 may be performed by the inter-base station identification module 810, as described above with reference to FIG.

  [0179] In block 1825, the UE may send an intra-base station communication request to the network as described above with reference to FIGS. In some examples, the operation of block 1825 may be performed by the communication establishment module 815, as described above with reference to FIG.

  [0180] In block 1830, the UE may communicate with the UE via a common base station, and packet data traffic with the UE may be shared as described above with reference to FIGS. Can be routed within a base station. In some examples, the operation of block 1830 may be performed by the routing module 820 as described above with reference to FIG.

  [0181] FIG. 19 shows a flowchart illustrating a method 1900 for selected IP flow ultra-low latency according to various aspects of the disclosure. The operations of method 1900 may be implemented by a UE or its components as described with reference to FIGS. For example, the operations of method 1800 may be performed by communication management module 610 as described with reference to FIGS. In some examples, the UE may execute a set of codes for controlling functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may perform the aspect functions described below using dedicated hardware.

  [0182] At block 1905, the UE may send a latency mode signal to the network as described above with reference to FIGS. In some examples, the operation of block 1905 may be performed by the latency mode transmission module 705, as described above with reference to FIG.

  [0183] At block 1910, the UE receives a grant signal for low latency IP packet routing based at least in part on the latency mode signal, as described above with reference to FIGS. be able to. In some cases, low latency IP packet routing may be allowed for an APN based on latency mode signals, or subscriber information, or both. In some examples, the operation of block 1910 may be performed by the permission receiving module 710 as described above with reference to FIG.

  [0184] At block 1915, the UE routes the packet according to the grant signal via the local gateway (LGW) based at least in part on the grant signal, as described above with reference to FIGS. can do. In some examples, the operation of block 1915 may be performed by the communication module 715, as described above with reference to FIG.

  [0185] At block 1920, the UE may send a measurement report to the source base station, as described above with reference to FIGS. In some examples, the operation of block 1920 may be performed by the measurement reporting module 825, as described above with reference to FIG.

  [0186] At block 1925, the UE may maintain service continuity during a handover initiated based at least in part on the measurement report, as described above with reference to FIGS. . In some examples, the operation of block 1925 may be performed by the continuity establishment module 830, as described above with reference to FIG.

  [0187] In some examples, the method may further include sending a quality of service (QoS) indication to the network, where the grant signal is based at least in part on the QoS indication. In some cases, the LGW comprises a source LGW associated with the source base station, and the method receives a new IP address allocation from the target LGW associated with the target base station and receives an IP address allocated by the source LGW. Use to transmit uplink data to the target base station, to receive downlink data from the target base station using an IP address allocated by the source LGW, wherein the downlink data is Receiving from the mobility management entity (MME) an instruction to utilize the new IP address routed through the source base station. In another example, the method receives a new IP address allocated from a target LGW associated with the target base station, re-establishes a radio resource control (RRC) connection with the target base station, and the target LGW. Communicating with the target base station using the new IP address allocated from. In yet a further example, the method receives a new IP address allocated from a target LGW associated with a target base station from a mobility management entity (MME) and re-establishes a radio resource control (RRC) connection with the target base station. Establishing and communicating with the target base station utilizing a new IP address allocated from the target LGW.

  [0188] Thus, the methods 1400, 1500, 1600, 1700, 1800, and 1900 may provide selected IP flow ultra-low latency. The methods 1400, 1500, 1600, 1700, 1800, and 1900 represent possible implementations, and the operations and steps may be reordered or possibly modified as other implementations are possible. Please note that. In some examples, aspects from two or more of the methods 1400, 1500, 1600, 1700, 1800, and 1900 may be combined.

  [0189] The detailed description set forth above with respect to the accompanying drawings describes exemplary embodiments and may not represent all embodiments that may be implemented or fall within the scope of the claims. As used herein, the term “exemplary” means “serving as an example, instance, or illustration” and does not mean “preferred” or “advantageous over other embodiments”. The detailed description includes specific details for providing an understanding of the techniques described. However, these techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described embodiments.

  [0190] Information and signals may be represented using any of a wide variety of techniques and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any of them Can be represented by a combination.

  [0191] Various exemplary blocks and modules described in connection with the disclosure herein may be a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, individual gate or transistor logic, individual hardware component, or book It may be implemented or performed using any combination thereof designed to perform the functions described in the specification. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (eg, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors associated with a DSP core, or any other such configuration). Can be done.

  [0192] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features that implement functions may also be physically located at various locations, including being distributed such that portions of the functions are implemented at various physical locations. Also, as used herein, including the claims, an enumeration of items (eg, items ending in a phrase such as “at least one of” or “one or more of”). As used herein, “or” means, for example, that at least one of A, B, or C is A or B or C or AB or AC or BC or ABC (ie, A and B and C A comprehensive enumeration is meant.

  [0193] Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, computer-readable media includes RAM, ROM, electrically erasable programmable read only memory (EEPROM®), compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic Comprising a storage device or any other medium that can be used to carry or store the desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor Can do. Any connection is also properly termed a computer-readable medium. For example, software can be sent from a website, server or other remote source using coaxial technology, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, wireless, and microwave. Wireless technologies such as coaxial cable, fiber optic cable, twisted pair, DSL, or infrared, radio, and microwave are included in the definition of media. Discs and discs used in this specification are CD, laser disc (registered trademark), optical disc (disc), digital versatile disc (DVD), floppy (registered trademark). Discs and Blu-ray discs, where the discs typically reproduce data magnetically, and the discs optically data with a laser To play. Combinations of the above are also included within the scope of computer-readable media.

  [0194] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure should not be limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

  [0195] The techniques described herein include code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access. It can be used for various wireless communication systems such as connectivity (SC-FDMA) and other systems. The terms “system” and “network” are often used interchangeably. A CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000 Release 0 and A are generally called CDMA2000 1X, 1X, and the like. IS-856 (TIA-856) is generally called CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), or the like. UTRA includes wideband CDMA (WCDMA®) and other variants of CDMA. A TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM). The OFDMA system includes Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)). Wireless technologies such as IEEE 802.20, Flash-OFDM may be implemented. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP® Long Term Evolution (LTE) and LTE Advanced (LTE-A) are new releases of Universal Mobile Telecommunications System (UMTS) that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and Global System for Mobile Communications (GSM) are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). Yes. CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies. However, while the above description describes an LTE system as an example and LTE terminology is used in much of the above description, the techniques are applicable to applications other than LTE applications.

[0195] The techniques described herein include code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access. It can be used for various wireless communication systems such as connectivity (SC-FDMA) and other systems. The terms “system” and “network” are often used interchangeably. A CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000 Release 0 and A are generally called CDMA2000 1X, 1X, and the like. IS-856 (TIA-856) is generally called CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), or the like. UTRA includes wideband CDMA (WCDMA®) and other variants of CDMA. A TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM). The OFDMA system includes Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)). Wireless technologies such as IEEE 802.20, Flash-OFDM may be implemented. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP® Long Term Evolution (LTE) and LTE Advanced (LTE-A) are new releases of Universal Mobile Telecommunications System (UMTS) that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and Global System for Mobile Communications (GSM) are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). Yes. CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies. However, while the above description describes an LTE system as an example and LTE terminology is used in much of the above description, the techniques are applicable to applications other than LTE applications.
The invention described in the scope of claims at the beginning of the application of the present application will be added below.
[C1] A wireless communication method,
Determining a latency mode of a first user equipment (UE);
Enabling low latency Internet Protocol (IP) packet routing for the first UE based at least in part on the latency mode of the first UE;
Selecting a local gateway (LGW) for the low latency IP packet routing based at least in part on the latency mode of the first UE.
[C2] The low latency IP packet routing is enabled with respect to an access point name (APN) associated with the latency mode of the first UE, and the LGW is selected based at least in part on the APN. The method according to C1.
[C3] determining a quality of service (QoS) for each bearer configured for the first UE;
Selecting the LGW based at least in part on the determined QoS;
The method of C1, further comprising:
[C4] determining that the first UE and the second UE are connected to a common base station;
Determining that the latency mode of the second UE is the same as the latency mode of the first UE;
The first UE and the second in the common base station based at least in part on determining that the latency mode of the second UE is the same as the latency mode of the first UE. Routing packet data traffic to and from other UEs
The method of C1, further comprising:
[C5] determining that the first UE is connected to a first base station and a second UE is connected to a second base station, wherein the first base station and the A second base station is communicating via a direct backhaul link;
Determining that the latency mode of the second UE is the same as the latency mode of the first UE;
Routing packet data traffic between the first UE and the second UE via the direct backhaul link between the first base station and the second base station;
The method of C1, further comprising:
[C6] the routing comprises via the LGW, the LGW comprising a first LGW collocated with the first base station, the method comprising:
Selecting a second LGW collocated with the second base station;
The method of C5, further comprising routing the packet data traffic through the first LGW and the second LGW.
[C7] determining that the first UE and the second UE are connected to a common serving gateway (SGW);
Determining that the latency mode of the second UE is the same as the latency mode of the first UE;
Receiving from the SGW a packet routed between the first UE and the second UE;
The method of C1, further comprising:
[C8] identifying the handover of the first UE from the source base station to the target base station;
Maintaining service continuity for the low latency IP packet routing during the handover;
The method of C1, further comprising:
[C9] sending a handover request with a low latency IP routing indication from the source base station to the target base station;
Receiving a handover acknowledgment with the low latency IP routing indication from the target base station at the source base station;
The method of C8, further comprising:
[C10] selecting the target base station by the source base station based at least in part on the target base station's ability to support the low latency IP packet routing.
The method of C8, further comprising:
[C11] sending a handover request with a low latency IP routing instruction from the source base station to the target base station;
Receiving a handover acknowledgment with the low latency IP routing indication and an IP address from the target base station at the source base station;
Transmitting the IP address from the source base station to the first UE;
The method of C8, further comprising:
[C12] A device for wireless communication,
Means for determining a latency mode of a first user equipment (UE);
Means for enabling low latency internet protocol (IP) packet routing for the first UE based at least in part on the latency mode of the first UE;
Means for selecting a local gateway (LGW) for the low latency IP packet routing based at least in part on the latency mode of the first UE.
[C13] means for enabling the low latency IP packet routing for an access point name (APN) associated with the latency mode of the first UE;
Means for selecting the LGW based at least in part on the APN;
The apparatus according to C12, further comprising:
[C14] means for determining quality of service (QoS) for each bearer configured for the first UE;
Means for selecting the LGW based at least in part on the determined QoS;
The apparatus according to C12, further comprising:
[C15] means for determining that the first UE and the second UE are connected to a common base station;
Means for determining that the latency mode of the second UE is the same as the latency mode of the first UE;
With the first and second UEs in the common base station based at least in part on determining that the latency mode of the second UE is the same as the latency mode of the first UE Means for routing packet data traffic between and
The apparatus according to C12, further comprising:
[C16] means for determining that the first UE is connected to a first base station and a second UE is connected to a second base station, wherein the first and second Base stations are communicating via direct backhaul links,
Means for determining that the latency mode of the second UE is the same as the latency mode of the first UE;
Means for routing packet data traffic to and from the first and second UEs via the direct backhaul link between the first and second base stations;
The apparatus according to C12, further comprising:
[C17] The means for routing data traffic to and from the first and second UEs via the direct backhaul link between the first and second base stations, Comprising a first LGW co-located with a base station of
Means for selecting a second LGW collocated with the second base station;
The apparatus of C16, further comprising means for routing the packet data traffic through the first LGW and the second LGW.
[C18] means for determining that the first UE and the second UE are connected to a common serving gateway (SGW);
Means for determining that the latency mode of the second UE is the same as the latency mode of the first UE;
Means for routing packet data traffic between the first and second UEs within the SGW;
The apparatus according to C12, further comprising:
[C19] means for identifying a handover of the first UE from a source base station to a target base station;
Means for maintaining service continuity during said handover;
The apparatus according to C12, further comprising:
[C20] means for sending a handover request with a low latency IP routing indication from the source base station to the target base station;
Means for receiving a handover acknowledgment with the low latency IP routing indication from the target base station at the source base station;
The apparatus according to C19, further comprising:
[C21] means for selecting the target base station by the source base station based at least in part on the ability of the target base station to support the low latency IP packet routing
The apparatus according to C19, further comprising:
[C22] means for sending a handover request with a low latency IP routing indication from the source base station to the target base station;
Means for receiving a handover acknowledgment comprising the low latency IP routing indication and an IP address from the target base station at the source base station;
Means for transmitting the IP address from the source base station to the first UE;
The apparatus according to C19, further comprising:
[C23] A method of wireless communication in a user equipment (UE),
Sending a latency mode signal to the network;
Receiving a grant signal for low latency Internet Protocol (IP) packet routing based at least in part on the latency mode signal;
Routing a packet according to the grant signal via a local gateway (LGW) based at least in part on the grant signal.
[C24] The method of C23, wherein the low latency IP packet routing is allowed for an access point name (APN) based at least in part on the latency mode signal, or subscriber information, or both.
[C25] sending a quality of service (QoS) indication to the network, wherein the grant signal is based at least in part on the QoS indication;
The method of C23, further comprising:
[C26] sending a measurement report to the source base station;
Maintaining service continuity during a handover initiated based at least in part on the measurement report;
The method of C23, further comprising:
[C27] the LGW comprises a source LGW associated with a source base station, the method comprising:
Receiving a new IP address allocation from a target LGW associated with the target base station;
Using the IP address allocated by the source LGW to transmit uplink data to the target base station;
Receiving downlink data from the target base station using the IP address allocated by the source LGW, wherein the downlink data is routed through the source base station;
Receiving the indication to utilize the new IP address from a mobility management entity (MME).
[C28] receiving a new IP address allocated from the target LGW associated with the target base station;
Re-establishing a radio resource control (RRC) connection with the target base station;
Communicating with the target base station using the new IP address allocated from the target LGW;
The method of C26, further comprising:
[C29] receiving a new IP address allocated from the target LGW associated with the target base station from the mobility management entity (MME);
Re-establishing a radio resource control (RRC) connection with the target base station;
Communicating with the target base station using the new IP address allocated from the target LGW;
The method of C23, further comprising:
[C30] An apparatus for wireless communication in a user equipment (UE) comprising:
Means for transmitting a latency mode signal to the network;
Means for receiving a grant signal for low latency internet protocol (IP) packet routing based at least in part on the latency mode signal;
Means for communicating with the network via a local gateway (LGW) based at least in part on the permission signal.

Claims (30)

A wireless communication method,
Determining a latency mode of a first user equipment (UE);
Enabling low latency Internet Protocol (IP) packet routing for the first UE based at least in part on the latency mode of the first UE;
Selecting a local gateway (LGW) for the low latency IP packet routing based at least in part on the latency mode of the first UE.   The low latency IP packet routing is enabled with respect to an access point name (APN) associated with the latency mode of the first UE, and the LGW is selected based at least in part on the APN. The method described in 1. Determining a quality of service (QoS) for each bearer configured for the first UE;
The method of claim 1, further comprising: selecting the LGW based at least in part on the determined QoS. Determining that the first UE and the second UE are connected to a common base station;
Determining that the latency mode of the second UE is the same as the latency mode of the first UE;
The first UE and the second in the common base station based at least in part on determining that the latency mode of the second UE is the same as the latency mode of the first UE. The method of claim 1, further comprising routing packet data traffic to and from the UEs. Determining that the first UE is connected to a first base station and a second UE is connected to a second base station, wherein the first base station and the second UE The base station is communicating via a direct backhaul link,
Determining that the latency mode of the second UE is the same as the latency mode of the first UE;
Routing packet data traffic between the first UE and the second UE via the direct backhaul link between the first base station and the second base station; The method of claim 1 comprising. The routing comprises via the LGW, the LGW comprising a first LGW collocated with the first base station, the method comprising:
Selecting a second LGW collocated with the second base station;
6. The method of claim 5, further comprising routing the packet data traffic via the first LGW and the second LGW. Determining that the first UE and the second UE are connected to a common serving gateway (SGW);
Determining that the latency mode of the second UE is the same as the latency mode of the first UE;
The method of claim 1, further comprising: receiving from the SGW a packet routed between the first UE and the second UE. Identifying a handover of the first UE from a source base station to a target base station;
The method of claim 1, further comprising maintaining service continuity for the low latency IP packet routing during the handover. Sending a handover request with a low latency IP routing indication from the source base station to the target base station;
9. The method of claim 8, further comprising: receiving a handover acknowledgment with the low latency IP routing indication from the target base station at the source base station. 9. The method of claim 8, further comprising: selecting the target base station by the source base station based at least in part on the target base station's ability to support the low latency IP packet routing. Sending a handover request with a low latency IP routing indication from the source base station to the target base station;
Receiving a handover acknowledgment with the low latency IP routing indication and an IP address from the target base station at the source base station;
9. The method of claim 8, further comprising: transmitting the IP address from the source base station to the first UE. A device for wireless communication,
Means for determining a latency mode of a first user equipment (UE);
Means for enabling low latency internet protocol (IP) packet routing for the first UE based at least in part on the latency mode of the first UE;
Means for selecting a local gateway (LGW) for the low latency IP packet routing based at least in part on the latency mode of the first UE. Means for enabling the low latency IP packet routing for an access point name (APN) associated with the latency mode of the first UE;
13. The apparatus of claim 12, further comprising: means for selecting the LGW based at least in part on the APN. Means for determining a quality of service (QoS) for each bearer configured for the first UE;
13. The apparatus of claim 12, further comprising: means for selecting the LGW based at least in part on the determined QoS. Means for determining that the first UE and the second UE are connected to a common base station;
Means for determining that the latency mode of the second UE is the same as the latency mode of the first UE;
With the first and second UEs in the common base station based at least in part on determining that the latency mode of the second UE is the same as the latency mode of the first UE. 13. The apparatus of claim 12, further comprising: means for routing packet data traffic between the devices. Means for determining that the first UE is connected to a first base station and a second UE is connected to a second base station, wherein the first and second base stations Is communicating via a direct backhaul link,
Means for determining that the latency mode of the second UE is the same as the latency mode of the first UE;
And means for routing packet data traffic to and from the first and second UEs via the direct backhaul link between the first and second base stations. The device described in 1. Said means for routing data traffic to and from said first and second UEs via said direct backhaul link between said first and second base stations; A first LGW that is collocated with
Means for selecting a second LGW collocated with the second base station;
The apparatus of claim 16, further comprising means for routing the packet data traffic through the first LGW and the second LGW. Means for determining that the first UE and the second UE are connected to a common serving gateway (SGW);
Means for determining that the latency mode of the second UE is the same as the latency mode of the first UE;
13. The apparatus of claim 12, further comprising: means for routing packet data traffic between the first and second UEs within the SGW. Means for identifying a handover of the first UE from a source base station to a target base station;
13. The apparatus of claim 12, further comprising means for maintaining service continuity during the handover. Means for sending a handover request with a low latency IP routing indication from the source base station to the target base station;
20. The apparatus of claim 19, further comprising: means for receiving a handover acknowledgment with the low latency IP routing indication from the target base station at the source base station. The means for selecting the target base station by the source base station based at least in part on the ability of the target base station to support the low latency IP packet routing. apparatus. Means for sending a handover request with a low latency IP routing indication from the source base station to the target base station;
Means for receiving a handover acknowledgment comprising the low latency IP routing indication and an IP address from the target base station at the source base station;
20. The apparatus of claim 19, further comprising: means for transmitting the IP address from the source base station to the first UE. A method of wireless communication in a user equipment (UE) comprising:
Sending a latency mode signal to the network;
Receiving a grant signal for low latency Internet Protocol (IP) packet routing based at least in part on the latency mode signal;
Routing a packet according to the grant signal via a local gateway (LGW) based at least in part on the grant signal.   24. The method of claim 23, wherein the low latency IP packet routing is allowed for an access point name (APN) based at least in part on the latency mode signal, or subscriber information, or both. Sending a quality of service (QoS) indication to the network, wherein the grant signal is based at least in part on the QoS indication;
24. The method of claim 23, further comprising: Sending a measurement report to the source base station;
24. The method of claim 23, further comprising maintaining service continuity during a handover initiated based at least in part on the measurement report. The LGW comprises a source LGW associated with a source base station, the method comprising:
Receiving a new IP address allocation from a target LGW associated with the target base station;
Using the IP address allocated by the source LGW to transmit uplink data to the target base station;
Receiving downlink data from the target base station using the IP address allocated by the source LGW, wherein the downlink data is routed through the source base station;
24. The method of claim 23, further comprising receiving an instruction to utilize the new IP address from a mobility management entity (MME). Receiving a new IP address allocated from a target LGW associated with the target base station;
Re-establishing a radio resource control (RRC) connection with the target base station;
27. The method of claim 26, further comprising communicating with the target base station utilizing the new IP address allocated from the target LGW. Receiving a new IP address allocated from a target LGW associated with the target base station from a mobility management entity (MME);
Re-establishing a radio resource control (RRC) connection with the target base station;
24. The method of claim 23, further comprising communicating with the target base station using the new IP address allocated from the target LGW. An apparatus for wireless communication in a user equipment (UE) comprising:
Means for transmitting a latency mode signal to the network;
Means for receiving a grant signal for low latency internet protocol (IP) packet routing based at least in part on the latency mode signal;
Means for communicating with the network via a local gateway (LGW) based at least in part on the permission signal.

Images