Network initiated packet data network connection

Abstract

Apparatus, systems and methods for network initiated packet data network connections in a communication system are described.

Description

[0001] Division Statement

[0002] This application is a divisional application of the Chinese invention patent application with the application date of April 19, 2016, the invention name of which is “NETWORK-INITIATED PACKET DATA NETWORK CONNECTION” and the application number: 201680052149.1.

[0003] Related Applications

[0004] This application claims the benefit of priority under 35 USC §119(e) to U.S. Provisional Application No. 62 / 239,750, filed on October 9, 2015, entitled “[5G, SA2] NETWORK INITIATED PACKET DATA NETWORK CONNECTION IN 5G EVOLVED PACKET SYSTEM,” the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0005] The present disclosure generally relates to the field of electronic communications. More specifically, aspects generally relate to network-initiated packet data network connections in a communication system. Background Art

[0006] Techniques for implementing network initiated packet data network connections may find utility in electronic communications systems, for example, for electronic devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The detailed description is provided with reference to the accompanying drawings.The use of the same reference numbers in different drawings indicates similar or identical items.

[0008] Figure 1 is a schematic block diagram illustration of components in a 3GPP LTE network that may implement a network initiated packet data network connection in a communication system according to various examples discussed herein.

[0009] Figure 2 is a schematic diagram of a network architecture that may implement a network-initiated packet data network connection in a communication system according to various examples discussed herein.

[0010] Figure 3 is a schematic diagram of a first example network architecture that may implement a network-initiated packet data network connection in a communication system according to various examples discussed herein.

[0011] Figure 4 High-level operations in a method for implementing a network-initiated packet data network connection for a communication system are shown according to various examples discussed herein.

[0012] Figure 5is a schematic diagram of a second example network architecture that may implement a network-initiated packet data network connection in a communication system according to various examples discussed herein.

[0013] Figure 6 High-level operations in a method for implementing a network-initiated packet data network connection in a communication system are shown according to various examples discussed herein.

[0014] Figure 7 is a schematic diagram of a third example network architecture that may implement a network-initiated packet data network connection in a communication system according to various examples discussed herein.

[0015] Figure 8 High-level operations in a method for implementing a network-initiated packet data network connection in a communication system are shown according to various examples discussed herein.

[0016] Fig. 9 is a schematic block diagram illustration of a wireless network according to one or more exemplary embodiments disclosed herein.

[0017] Fig.10 and Fig.11 Schematic block diagrams of radio interface protocol structures between a UE and an eNodeB based on a 3GPP type wireless access network standard according to one or more exemplary embodiments disclosed herein.

[0018] Fig.12 is a schematic block diagram illustration of an information processing system according to one or more exemplary embodiments disclosed herein.

[0019] Fig.13 is an isometric view of an exemplary embodiment of an information handling system that may optionally include a touch screen in accordance with one or more embodiments disclosed herein.

[0020] Fig.14 is a schematic block diagram illustration of components of a wireless device according to one or more exemplary embodiments disclosed herein.

[0021] It should be understood that in order to make the description simple and / or clear, the elements shown in the drawings are not necessarily drawn to scale. For example, for clarity, the size of some elements may be exaggerated relative to other elements. In addition, if it is considered appropriate, the reference numerals are repeated in the drawings to indicate corresponding and / or similar elements. DETAILED DESCRIPTION

[0022] In the following description, a large number of specific details are set forth to provide a thorough understanding of various examples. However, various examples can be practiced without these specific details. In other cases, well-known methods, processes, components, and circuits are not described in detail so as not to obscure specific examples. In addition, various aspects of the examples can be implemented using various means such as integrated semiconductor circuits ("hardware"), computer-readable instructions organized into one or more programs ("software"), or some combination of hardware and software. For the purposes of this disclosure, references to "logic" will represent hardware, software, or some combination thereof.

[0023] References throughout this specification to "one embodiment" or "an embodiment" mean that the particular features, structures, or characteristics described in conjunction with the embodiment are included in at least one embodiment. Therefore, the phrases "in one embodiment" or "in an embodiment" that appear in various places throughout this specification do not necessarily all refer to the same embodiment. In addition, the particular features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In addition, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" should not be construed as necessarily being preferred or advantageous over other embodiments.

[0024] Various operations may be described in turn as multiple discrete operations in a manner that is most helpful for understanding the claimed subject matter. However, the order of description should not be interpreted as implying that these operations necessarily rely on the order. In particular, these operations do not need to be performed in the order presented. The described operations may be performed in an order different from the described embodiments. In additional embodiments, various additional operations may be performed and / or the described operations may be omitted.

[0025] Service continuity in mobile networks is sometimes considered synonymous with Internet Protocol (IP) address reservation. In order to make service continuity possible, mobile devices can be assigned Internet Protocol (IP) addresses hosted at "IP anchor" nodes (i.e., packet gateways (PGWs) in the core network). Traffic between mobile devices and IP anchor nodes can be tunneled, and IP routing is only used within the packet data network starting at the IP anchor node. In some situations (e.g., two UEs under the same eNB communicate with each other via a long Hairpin), the tunnel data path may result in inefficient resource usage.

[0026] Various applications today can survive IP address changes. One example of such an application includes an application based on the Session Initiation Protocol (SIP), in which a "SIP reINVITE" message is sent to update the remote party with a new IP address, which will be used as the contact address for future user plane services. Another example includes an application based on Dynamic Adaptive Streaming over HTTP (DASH), which can survive IP address changes and continue content delivery from different content distribution servers. This is achieved by associating content segments with globally unique transport-independent tags (URLs) so that the streaming client can always determine the next content segment in sequence and request it from the content distribution network (including from different servers).

[0027] Service continuity can also be ensured at the transport layer by using an evolved transport protocol, such as Multipath TCP (MPTCP). MPTCP clients can dynamically add or remove sub-streams carried on different IP addresses without affecting the byte stream transmitted on behalf of the application.

[0028] As the amount of multimedia broadband data continues to increase, it may be useful for the 3GPP system to be able to select an IP anchor node (i.e., PGW) close to the edge of the radio access network and the current location of the user equipment (UE). This will allow IP services to be offloaded from the 3GPP system user plane to a traditional IP routing network close to the edge of the network, which reduces the tunnel segment of the data path and increases the IP routing portion. This increases the scalability of the 3GPP system user plane nodes, enhances the end-to-end communication path by avoiding triangular routing via the IP anchor node, and reduces the end-to-end latency of data transmission. In addition, content delivery can be continued from a content distribution server that is geographically closer to the UE, which further reduces the traffic load on the 3GPP network.

[0029] When the existing PGW node is considered suboptimal, the 3GPP communication system can use the Select IP Traffic Offload (SIPTO) feature to offload traffic by dispatching a new geographically closer PGW node. However, with SIPTO, the communication system first releases the existing PGW node before acquiring a new PGW node and a new IP address, which makes it a "break before make" type solution. Although adaptive streaming applications can survive IP address changes, temporary connection loss may still be significant to users, depending on factors such as the amount of buffer segments in the UE, the streaming rate, the time required to reestablish the HTTPS connection, etc.

[0030] It may be useful for a 3GPP communication system to leverage the capabilities of upper layer protocols (i.e., application and / or transport layers) to facilitate surviving IP address changes. By knowing that the application can survive IP address changes, the communication system can establish a connection with the new IP anchor node before releasing the old IP anchor node. This requires the UE to maintain connections with both IP anchor nodes during the transition period. Once the traffic is consolidated onto the new IP address (e.g., by leveraging SIP reINVITE, DASH, or MPTCP mechanisms), the system can release the connection with the old IP anchor node.

[0031] The following references Figures 1 to 14 Techniques for implementing network-initiated packet data network connections in a communication system and features and characteristics of communication systems that may include the techniques are described.

[0032] Figure 1 An exemplary block diagram illustrating the overall architecture of a 3GPP LTE network 100 including one or more devices capable of implementing a method for implementing a network-initiated packet data network connection in a communication system according to the subject matter disclosed herein. Figure 1 Also generally shown are exemplary network elements and exemplary standardized interfaces. At a high level, the network 100 includes a core network (CN) 101 (also referred to as an evolved packet system (EPC)) and an air interface access network E UTRAN 102. The CN 101 is responsible for the overall control of individual user equipments (UEs) connected to the network and for establishing bearers. Although not explicitly depicted, the CN 101 may include functional entities such as a home agent and / or an ANDSF server or entity. The E UTRAN 102 is responsible for all radio-related functions.

[0033] The main exemplary logical nodes of CN 101 include, but are not limited to, a serving GPRS support node 103, a mobility management entity 104, a home subscriber server (HSS) 105, a serving gateway (SGW) 106, a packet data network (PDN) gateway 107, and a policy and charging rules function (PCRF) manager 108. The functions of each network element of CN 101 are well known and will not be described here. Although not described herein, each network element of CN 101 is interconnected through well-known exemplary standardized interfaces, some of which are described in Figure 1 For example, interfaces S3, S4, S5, etc. are shown.

[0034] Although CN 101 includes many logical nodes, E UTRAN access network 102 is formed by at least one node (e.g., evolved Node B (base station (BS), eNB or eNodeB)) 110, which is connected to one or more user equipment (UE) 111 (in Figure 1Only one of them is depicted in FIG. 1 ). UE 111 is also referred to herein as a wireless device (WD) and / or a user station (SS), and may include an M2M type device. In one example, UE 111 may be coupled to an eNB via an LTE-Uu interface. In one exemplary configuration, a single cell of the E UTRAN access network 102 provides a substantially localized geographical transmission point (with multiple antenna devices) that provides access to one or more UEs. In another exemplary configuration, a single cell of the E UTRAN access network 102 provides a plurality of substantially geographically isolated transmission points (each with one or more antenna devices), wherein each transmission point simultaneously provides access to one or more UEs, and signaling bits are defined for a cell so that all UEs share the same spatial signaling dimension. For normal user traffic (not broadcast), there is no centralized controller in the E-UTRAN, and therefore the E-UTRAN architecture is considered to be flat. The eNBs are typically interconnected to each other via an interface called "X2" and to the EPC via an S1 interface. More specifically, the eNB is connected to the MME 104 via an S1 MME interface and to the SGW 106 via an S1 U interface. The protocol running between the eNB and the UE is generally referred to as the “AS protocol.” The details of the various interfaces are well known and are not described herein.

[0035] The eNB 110 manages the physical (PHY) layer, the medium access control (MAC) layer, the radio link control (RLC) layer, and the packet data control protocol (PDCP) layer, which are not in Figure 1 The eNB 110 also provides a radio resource control (RRC) function corresponding to the control plane and implements many functions, including radio resource management, admission control, scheduling, implementation of negotiated uplink (UL) QoS, cell information broadcast, encryption / decryption of user plane and control plane data, and compression / decompression of DL / UL user plane packet headers.

[0036] The RRC layer in the eNB 110 covers all functions related to radio bearers, such as radio bearer control, radio admission control, radio mobility control, scheduling and dynamic allocation of resources to UEs in both uplink and downlink, header compression for efficient use of the radio interface, security of all data sent over the radio interface, and connectivity with the EPC. The RRC layer makes handover decisions based on neighboring cell measurements sent by the UE 111, generates over-the-air paging to the UE 111, broadcasts system information, controls UE measurement reporting (e.g., the periodicity of channel quality information (CQI) reporting), and assigns cell-level temporary identifiers to active UEs 111. The RRC layer also performs the transfer of UE context from the source eNB to the target eNB during handover and provides integrity protection for RRC messages. In addition, the RRC layer is responsible for establishing and maintaining radio bearers.

[0037] Figure 2 2 is a schematic diagram of a network architecture of a communication system 200 that can implement a network-initiated packet data network connection according to various examples discussed herein. The system 200 may include one or more cells, each of which may include one or more sectors. Each cell includes at least one base station (BS) 230. Multiple UEs 210 may be located throughout the system 200. The system 200 may also include one or more access points 220 that can transmit traffic from the UEs 210 to the communication network.

[0038] Base station 210 may be embodied as, but not limited to, an evolved Node B (eNB or eNodeB), a macrocell base station, a picocell base station, a femtocell base station, etc. UE 220 may be embodied as, but not limited to, a mobile station (MS), a subscriber station (SS), a machine-to-machine (M2M) device, a user terminal equipment (CPE), a user equipment (UE), a notebook computer, a tablet device, a cellular phone, a smart device, a smartphone, a personal digital assistant, an information processing system, etc., as described herein. Access point 220 may be embodied as, but not limited to, a WLAN access point.

[0039] Figure 3 to Figure 4 A first example of a network initiated packet data network connection in a communication system is depicted. Figure 3 to Figure 4 In the depicted example, UE 210 may move from a coverage area served by a first eNB 230A to a coverage area served by a second eNB 230B, thereby triggering a change in the packet data network connection of UE 210. Figure 3At a first point in time, UE 210 may be served by a first eNB 230A coupled to a first packet data network gateway PGW-1, which provides a first packet data network connection to an IP network (e.g., the Internet). At a second point in time, UE 210 may move to a different location where coverage is provided by a second eNB 230B coupled to a second packet data network gateway PGW-2, which provides a second packet data network connection to an IP network (e.g., the Internet).

[0040] Figure 4 Depicted in Figure 3 The operation of a network-initiated packet data network connection is implemented in the operating environment described in . Figure 4 , UE 210 is initially in a coverage area served by a first eNB 230A and has an established packet data network connection (PDN1) provided by a first packet data network gateway (PGW-1). The packet data network connection involves the first eNB 230A, the user plane portion of the first packet data network gateway PGW1, and may include one or more intermediate user plane nodes providing SGW functionality. UE 210 is assigned an IP address / prefix (i.e., IP@1). It should be noted that for simplicity, the presence of any intermediate U-plane nodes (including nodes with SGW-U functionality) are omitted from the figures. Furthermore, it should be noted that although Figure 3 GTP-U is depicted as an example of a tunneling protocol in the user plane, but other tunneling protocols (eg, GRE) may be used.

[0041] When UE 210 moves from a coverage area served by a first eNB 230A to a coverage area served by a second eNB 230B, the network determines that backhauling traffic to a first packet data network gateway (PGW-1) is no longer optimal and that changing the IP anchor point may be useful. In some examples, this determination may be made by circuitry in the eNB. In other examples, this determination may be made by circuitry in a different network entity, such as a network entity in a control plane (C-plane) cloud.

[0042] In some examples, the network entity in the C-plane cloud selects a new packet data network function (PGW2) that is geographically closer to the current location of UE 210, and configures (operation 410) the user plane function in a second packet data network gateway (e.g., PGW2 for the new packet data network connection). The configuration parameters may include at least a tunnel endpoint transport address for the tunnel toward the next hop U-plane node (e.g., the SGW node for PDN1). In this process, the packet data network gateway PGW2 allocates a new IP address / prefix (IP@2) and sends it to the network entity in the C-plane cloud.

[0043] In response to determining to switch UE 210 from a first packet data network connection managed by a first packet data network gateway (PGW-1) to a second packet data network connection managed by a second packet data network gateway (PGW-2), the network configures (operation 415) the second packet data network gateway (PGW-2) and any intermediate U-plane nodes. For example, a network entity in the C-plane cloud configures a next-hop U-plane node (in this example, the same SGW-U used for PDN1). The configuration parameters include at least a tunnel endpoint transport address for a tunnel toward the next-hop U-plane node (e.g., an eNB on one side and PGW2 on the other side).

[0044] The network entity in the C-plane cloud configures a new PDN connection in the second eNB 230B (operation 420). In some examples, the configuration parameters may include a tunnel endpoint transport address and a new IP address / prefix (IP@2) of the tunnel toward the next hop U-plane node (e.g., SGW2 node).

[0045] When the new PDN connection (PDN2) is configured, the network entity notifies the UE 210 of the availability of PDN2 and invites the UE 210 to start using the new IP address / prefix (IP@2). Depending on the separation between access stratum (AS) and non-access stratum (NAS) signaling in the 5G Evolved Packet System, the information can be provided from the network entity in the C-plane cloud (operation 425) or from the second eNB 230B (operation 430). For example, AS signaling allows the UE to communicate directly with the eNB using the radio resource control (RRC) protocol. NAS signaling allows the UE to communicate directly with the network entity (e.g., the network entity in the C-plane cloud) using messages carried as transparent containers through RRC (e.g., between the UE and the eNB) and through S1-AP (e.g., between the eNB and the network entity in the C-plane cloud).

[0046] When using IPv6, the eNB 230B, acting as the default IP router, sends (operation 435) a Router Advertisement (RA) message containing the new IPv6 prefix (IP@2), thereby allowing the UE 210 to perform stateless address autoconfiguration with the prefix. The UE may optionally use a Router Solicitation to trigger the RA.

[0047] Based on the information received during the configuration process, UE 210 starts using IP@2 for new services (operation 440) and moves services from existing applications (where possible) over the new IP interface by leveraging upper layer mobility mechanisms (eg, SIP reINVITE, DASH, MPTCP).

[0048] Figures 5 and 6 A second example of a network initiated packet data network connection in a communication system is depicted. Figures 5 and 6 In the depicted example, UE 210 may operate in a mobile edge computing (MEC) environment in which IT and cloud computing capabilities are provided within a radio access network (RAN) in close proximity to user device 210. Mobile edge computing allows for content, service, and application acceleration, thereby improving responsiveness from the edge of the network.

[0049] The MEC server (e.g., a content delivery network (CDN) server) can be co-located with the eNB or located near the eNB. In the latter case, the MEC server can be reached via the local IP network and can be shared by multiple eNBs. In the co-located case, the eNB checks all IP packets and redirects eligible packets to the co-located MEC server. In this case, there is no need to assign a new IP address / prefix to the UE.

[0050] In contrast, when the MEC server is a standalone server, it may be beneficial for the UE to use a different IP address / prefix. If this is not done, the eNB applies NAT functionality, which is generally undesirable, especially for IPv6. In this case, the eNB utilizes the co-sited local gateway (LGW) functionality to initiate a network-initiated PDN connection.

[0051] It should be noted that in some examples, the UE is able to access two different packet data networks (e.g., access to the Internet and access to a local IP network), and a routing policy that helps the UE select an appropriate source IP address / prefix (and subsequently the correct IP network) needs to be provided to the UE. Examples of routing policies (or routing rules) include the use of an application ID (referring to the application in the UE that caused the packet), an FQDN (referring to the FQDN that is being resolved to the target IP address), and selected fields in the IP packet header (particularly the target IP address and protocol). For each of these parameters, the routing policy contains a prioritized list of UE (i.e., "source") IP addresses / prefixes.

[0052] Figure 6 Depicted in Figure 5 The operation of a network-initiated packet data network connection is implemented in the operating environment described in . Figure 6 , UE 210 is initially in a coverage area served by a first eNB 230A and has an established packet data network connection (PDN1) provided by a first packet data network gateway (PGW-1). The packet data network connection involves the first eNB 230A, the user plane portion of the first packet data network gateway PGW1, and may include one or more intermediate user plane nodes providing SGW functionality. UE 210 is assigned an IP address / prefix (IP@1).

[0053] In operation 610, the eNB determines (e.g., based on packet inspection and analysis of the destination IP address in the packet header, the eNB realizes that the packet flow is destined for a server residing in the Internet that provides the same service as the locally resident MEC server) that it may be useful to change the IP anchor point for the traffic flow destined for the local MEC server. In some examples, the determination may be made by circuitry in the eNB 230A. In other examples, the determination may be made by circuitry in a different network entity, such as a network entity in a control plane (C-plane) cloud. In response to the determination, the eNB 230A selects a new packet data network function (PGW2) that includes a co-sited LGW function.

[0054] The eNB 230 notifies (operation 615) the network entity in the C-plane cloud of the new packet data network connection including the assigned IP address / prefix (IP@2) and one or more routing rules. Examples of routing rules may include:

[0055] Rule 1: For FQDN="youtube.*", use IP@2 first, then IP@1.

[0056] Rule 2: For destination IP address = "ff02::1:3", only IP@2 is used.

[0057] Rule 3: For App ID = "XYZ", use IP@2 first, then use IP@1.

[0058] The network entity notifies the UE of the availability of the second packet data network (PDN2) and provides a new IP address / prefix (IP@2) and routing rules. Depending on the separation between AS and NAS signaling in the packet system, this information can be provided from the network entity in the C-plane cloud (operation 620) or from the eNB (operation 625).

[0059] When using IPv6, the NB in ​​the default IP router role (operation 630) sends a router advertisement (RA) message containing a new IPv6 prefix (IP@2) to the UE, allowing the UE to perform stateless address autoconfiguration using the prefix. The UE may optionally use a router solicitation to trigger the RA.

[0060] When using IPv6, the eNB 230B, playing the role of the default IP router, sends a Router Advertisement (RA) message containing the new IPv6 prefix (IP@2), allowing the UE 210 to perform stateless address autoconfiguration with that prefix. The UE may optionally use a Router Solicitation to trigger a RA.

[0061] Based on the information received during the configuration process, UE 210 starts using (operation 635) IP@1 and IP@2 according to the provided routing rules.

[0062] Figures 7 and 8 A third example of a network initiated packet data network connection in a communication system is depicted. Figures 7 and 8 In the depicted example, UE 210 may move from a coverage area served by a first eNB 230A to a coverage area served by a booster cell, such as network access point 220. In some examples, UE 210 may maintain connectivity with both network access point 220 and eNB 230.

[0063] Figure 8 Depicted in Figure 7 The operation of a network-initiated packet data network connection is implemented in the operating environment described in . Figure 4 , UE 210 is initially in a coverage area served by eNB 230 and has an established packet data network connection (PDN) provided by a first packet data network gateway (PGW). The packet data network connection involves eNB 230A, the user plane portion of the first packet data network gateway PGW1, and may include one or more intermediate user plane nodes providing SGW functionality. UE 210 is assigned an IP address / prefix (IP@1).

[0064] When the UE moves from a coverage area served by the eNB 230 to an area covered by a network access point 220 such as a booster cell (also referred to herein as a secondary eNB or SeNB), the eNB 230 determines (operation 810) to add the network access point 220 in a dual connectivity (DC) configuration. When the DC mode is active, the UE still has only one radio resource control (RRC) connection, which is provided by the eNB 230. In other words, the network access point 220 is used only for user plane traffic, and the bearers routed via the network access point 220 are under the control of the eNB 230. Traffic exchanged via the network access point 220 is backhauled to / from the packet core network via an X2 communication link. In other examples, user plane traffic may be exchanged on a direct interface between the network access point 220 and the serving gateway. In some deployment scenarios, it may be beneficial to offload selected traffic flows at the network access point 220 (i.e., at the secondary eNB).

[0065] The eNB 230 forwards (operation 815) a request to establish a packet data network connection (PDN2) with the co-sited LGW to the network access point 220 using X2 signaling. In response to the request, the network access point 220 allocates (operation 820) a new IP address / prefix (IP@2), and in response to the eNB 230, notifies (operation 825) the network entity in the C-plane cloud of a new PDN connection including the assigned IP address / prefix (IP@2), thereby also indicating that this is a PDN connection from the network access point 220.

[0066] In some examples, the network entity in the C-plane cloud notifies (operation 830) UE 210 of the availability of the second packet data network (PDN2) and provides a new IP address / prefix (IP@2), thereby also indicating that this is a PDN connection from network access point 220. In other examples, depending on the separation between AS and NAS signaling in the 5G Evolved Packet System, this information can be provided from eNB 230.

[0067] When the new PDN connection (PDN2) is configured, the network entity notifies the availability of PDN2 (operation 835) to UE 210 and invites UE 210 to start using the new IP address / prefix (IP@2). Depending on the separation between AS and NAS signaling in the 5G Evolved Packet System, this information can be provided from the network entity in the C-plane cloud or from the second eNB 230B.

[0068] When using IPv6, the eNB 230B, acting as the default IP router, sends (operation 840) a Router Advertisement (RA) message containing the new IPv6 prefix (IP@2), thereby allowing the UE 210 to perform stateless address autoconfiguration with the prefix. The UE may optionally use a Router Solicitation to trigger the RA.

[0069] Based on the information received during the configuration process, UE 210 starts using (operation 845) IP@2 for new traffic and moves traffic from existing applications (where possible) over the new IP interface by leveraging upper layer mobility mechanisms (e.g., SIP reINVITE, DASH, MPTCP).

[0070] Fig. 9 is a schematic block diagram illustrating a wireless network 900 according to one or more exemplary embodiments disclosed herein. According to the subject matter disclosed herein, one or more elements of the wireless network 900 may be capable of implementing a method for identifying a victim and an interference source. Fig. 9 As shown, the network 900 may be an Internet Protocol type (IP type) network including an Internet type network 910 or the like, which can support mobile wireless access and / or fixed wireless access to the Internet 910 .

[0071] In one or more examples, the network 900 may operate in accordance with the Worldwide Interoperability for Microwave Access (WiMAX) standard or future generations of WiMAX, and in a specific example, may conform to an Institute of Electrical and Electronics Engineers 802.16-based standard (e.g., IEEE 802.16e) or an IEEE 802.11-based standard (e.g., IEEE 802.11a / b / g / n standard), etc. In one or more alternative examples, the network 900 may conform to the Third Generation Partnership Project Long Term Evolution (3GPP LTE), the 3GPP2 Air Interface Evolution (3GPP2 AIE) standard, and / or the 3GPP LTE-Advanced standard. Generally, network 900 may include any type of orthogonal frequency division multiple access (OFDMA-based) wireless network, such as a WiMAX-compliant network, a Wi-Fi Alliance-compliant network, a digital subscriber line-type (DSL-type) network, an asymmetric digital subscriber line-type (ADSL-type) network, an ultra-wideband (UWB)-compliant network, a wireless universal serial bus (USB)-compliant network, a fourth generation (4G)-type network, etc., and the scope of the claimed subject matter is not limited in these respects.

[0072] As an example of mobile wireless access, an access service network (ASN) 912 can be coupled with a base station (BS) 914 to provide wireless communication between a user station (SS) 916 (also referred to herein as a wireless terminal) and the Internet 910. In one example, the user station 916 may include a mobile device or information processing system capable of wireless communication via the network 900, such as a notebook computer, a cellular phone, a personal digital assistant, an M2M type device, etc. In another example, according to the subject matter disclosed herein, the user station can provide an uplink transmission power control technology that reduces the interference experienced at other wireless devices. The ASN 912 can implement a configuration file that can define the mapping of network functions to one or more physical entities on the network 900. The base station 914 may include a radio device to provide radio frequency (RF) communication with the user station 916, and may include, for example, a physical layer (PHY) and a medium access control (MAC) layer device that conforms to the IEEE 802.16e type standard. The base station 914 may also include an IP backplane coupled to the Internet 910 via the ASN 912, but the scope of the claimed subject matter is not limited in these respects.

[0073] The network 900 may also include a visitor connectivity service network (CSN) 924 that can provide one or more network functions, including but not limited to proxy and / or relay-type functions (e.g., authentication, authorization, and accounting (AAA) functions, dynamic host configuration protocol (DHCP) functions, or domain name service control, etc.), domain gateways (e.g., public switched telephone network (PSTN) gateways or voice over Internet Protocol (VoIP) gateways), and / or Internet Protocol-type (IP-type) server functions, etc. However, these are merely examples of the types of functions that can be provided by a visitor CSN or home CSN 926, and the scope of the claimed subject matter is not limited in these respects.

[0074] For example, visited CSN 924 may be referred to as a visited CSN where it is not part of the regular service provider for user station 916 (e.g., user station 916 is roaming away from its home CSN (e.g., home CSN 926)), or where network 900 is part of the regular service provider for the user station, but network 900 may be in another location or state that is not the home or home location of user station 916.

[0075] In a fixed wireless arrangement, WiMAX-type customer premises equipment (CPE) 922 may be located in a home or business to provide the home or business user with broadband access to the Internet 910 via base station 920, ASN 918 and home CSN 926 in a manner similar to the access of user station 916 via base station 914, ASN 912 and access CSN 924, except that the WiMAX CPE 922 is typically deployed at a fixed location, although it may be moved to different locations as needed, whereas the user station 916 is utilized at one or more locations if, for example, it is within range of base station 914.

[0076] It should be noted that CPE 922 need not necessarily include WiMAX type terminals, and may include other types of terminals or devices that conform to one or more standards or protocols, such as discussed herein, and may generally include fixed devices or mobile devices. In addition, in an exemplary embodiment, in accordance with the subject matter disclosed herein, CPE 922 can provide uplink transmit power control techniques that reduce interference experienced at other wireless devices.

[0077] According to one or more examples, operations support system (OSS) 928 may be part of network 900 to provide management functions for network 900 and to provide interfaces between functional entities of network 900 . Fig. 9Network 900 is merely one type of wireless network illustrating a certain number of components of network 900 , however, the scope of the claimed subject matter is not limited in these respects.

[0078] Fig.10 and Fig.11 An exemplary radio interface protocol structure between a UE and an eNodeB according to the subject matter disclosed herein is respectively depicted, which is based on a 3GPP-type wireless access network standard and is capable of providing an uplink transmission power control technique that reduces interference experienced at other wireless devices. More specifically, Fig.10 Describes the various layers of the radio protocol control plane, and Fig.11 The various layers of the user plane of the radio protocol are depicted. Based on the lower three layers of the widely known OSI reference model in communication systems, Fig.10 and Fig.11 The protocol layers of a network are classified into L1 layer (first layer), L2 layer (second layer) and L3 layer (third layer).

[0079] The physical (PHY) layer as the first layer (LI) provides information transmission services to the upper layer using physical channels. The physical layer is connected to the medium access control (MAC) layer located above the physical layer through a transport channel. Data is transmitted between the MAC layer and the PHY layer through the transport channel. The transport channel is classified into a dedicated transport channel and a common transport channel according to whether the channel is shared. Data transmission between different physical layers, specifically, data transmission between the corresponding physical layers of the transmitter and the receiver is performed through the physical channel.

[0080] There are various layers in the second layer (L2 layer). For example, the MAC layer maps various logical channels to various transport channels and performs logical channel multiplexing to map various logical channels to one transport channel. The MAC layer is connected to a radio link control (RLC) layer serving as an upper layer through a logical channel. According to the category of transmission information, the logical channel can be classified into a control channel for transmitting information of a control plane and a traffic channel for transmitting information of a user plane.

[0081] The RLC layer of the second layer (L2) performs segmentation and concatenation on the data received from the upper layer, and adjusts the size of the data to be suitable for the lower layer to send the data to the radio interval. In order to guarantee various service qualities (QoS) requested by the corresponding radio bearer (RB), three operation modes are provided, namely, transparent mode TM, unacknowledged mode (UM) and acknowledged mode (AM). Specifically, AM RLC performs a retransmission function using an automatic repeat request (ARQ) function to achieve reliable data transmission.

[0082] The Packet Data Convergence Protocol (PDCP) layer of the second layer (L2) performs a header compression function to reduce the size of an IP packet header having relatively large and unnecessary control information so as to efficiently transmit an IP packet (e.g., an IPv4 or IPv6 packet) in a radio section of a narrow bandwidth. As a result, only information required for the data header portion can be transmitted, so that the transmission efficiency of the radio section can be improved. In addition, in a system based on LTE, the PDCP layer performs a security function, which includes an encryption function for preventing a third party from eavesdropping on data and an integrity protection function for preventing a third party from processing data.

[0083] The Radio Resource Control (RRC) layer located at the top of the third layer (L3) is defined only in the control plane, and is responsible for controlling the logical channels, transport channels, and physical channels associated with the configuration, reconfiguration, and release of radio bearers (RBs). RBs are logical paths provided by the first and second layers (LI and L2) for data communication between UE and UTRAN. Generally, radio bearer (RB) configuration means that the radio protocol layers and channel characteristics required for providing a specific service are defined, and their detailed parameters and operation methods are configured. Radio bearers (RBs) are classified into signaling RBs (SRBs) and data RBs (DRBs). SRBs are used as transmission channels for RRC messages in the C plane, while DRBs are used as transmission channels for user data in the U plane.

[0084] The downlink transmission channel used to send data from the network to the UE can be classified into a broadcast channel (BCH) for transmitting system information and a downlink shared channel (SCH) for transmitting user traffic or control messages. Traffic or control messages for downlink multicast or broadcast services can be transmitted through the downlink SCH and can also be transmitted through the downlink multicast channel (MCH). The uplink transmission channel used to send data from the UE to the network includes a random access channel (RACH) for transmitting initial control messages and an uplink SCH for transmitting user traffic or control messages.

[0085] A downlink physical channel for transmitting information transmitted to a downlink transport channel to a radio section between a UE and a network is classified into a physical broadcast channel (PBCH) for transmitting BCH information, a physical multicast channel (PMCH) for transmitting MCH information, a physical downlink shared channel (PDSCH) for transmitting downlink SCH information, and a physical downlink control channel (PDCCH) (also referred to as a DL L1 / L2 control channel) for transmitting control information received from the first layer and the second layer (L1 and L2) (e.g., DL / UL scheduling approval information). Meanwhile, an uplink physical channel for transmitting information transmitted to an uplink transport channel to a radio section between a UE and a network is classified into a physical uplink shared channel (PUSCH) for transmitting uplink SCH information, a physical random access channel for transmitting RACH information, and a physical uplink control channel (PUCCH) for transmitting control information received from the first layer and the second layer (L1 and L2) (e.g., hybrid automatic repeat request (HARQ) ACK or NACK scheduling request (SR) and channel quality indication (CQI) report information).

[0086] Fig.12 An exemplary functional block diagram of an information processing system 1200 capable of implementing a method of identifying a victim party and a source of interference according to the subject matter disclosed herein is depicted. Fig.12 The information processing system 1200 may tangibly embody one or more of any of the exemplary devices, exemplary network elements, and / or functional entities in the network shown and described herein. In one example, the information processing system 1200 may represent components of a UE 111 or an eNB 110 and / or a WLAN access point 120, and may have more or fewer components depending on the hardware specifications of the particular device or network element. In another example, the information processing system may provide M2M type device capabilities. In yet another exemplary embodiment, in accordance with the subject matter disclosed herein, the information processing system 1200 is capable of providing uplink transmit power control techniques that reduce interference experienced at other wireless devices. Although the information processing system 1200 represents an example of several types of computing platforms, the information processing system 1200 may include more than Fig.12 Greater or fewer elements and / or different arrangements of elements may be shown, and the scope of claimed subject matter is not limited in these respects.

[0087] In one or more examples, the information processing system 1200 may include one or more application processors 1210 and a baseband processor 1212. In accordance with the subject matter disclosed herein, the application processor 1210 may be used as a general purpose processor to run applications and various subsystems of the information processing system 1200, and may be capable of providing uplink transmit power control techniques that reduce interference experienced at other wireless devices. The application processor 1210 may include a single core, or alternatively, may include multiple processing cores, wherein one or more cores may include a digital signal processor or digital signal processing core. In addition, the application processor 1210 may include a graphics processor or coprocessor disposed on the same chip, or alternatively, a graphics processor coupled to the application processor 1210 may include a separate discrete graphics chip. The application processor 1210 may include onboard memory such as cache memory, and may also be coupled to an external memory device such as a synchronous dynamic random access memory (SDRAM) 1214 for storing and / or executing applications, such as being capable of providing uplink transmit power control techniques in accordance with the subject matter disclosed herein that reduce interference experienced at other wireless devices. During operation, NAND flash memory 1216 is used to store applications and / or data even when information handling system 1200 is powered off.

[0088] In one example, the list of candidate nodes may be stored in SDRAM 1214 and / or NAND flash memory 1216. In addition, application processor 1210 may execute computer-readable instructions stored in SDRAM 1214 and / or NAND flash memory 1216 that implement uplink transmit power control techniques in accordance with the subject matter disclosed herein that reduce interference experienced at other wireless devices.

[0089] In one example, the baseband processor 1212 can control broadband radio functions for the information processing system 1200. The baseband processor 1212 can store code for controlling such broadband radio functions in the NOR flash memory 1218. The baseband processor 1212 controls a wireless wide area network (WWAN) transceiver 1220, which is used to modulate and / or demodulate broadband network signals, such as for communicating via a 3GPP LTE network, etc., as described herein. Fig.12The WWAN transceiver 1220 is coupled to one or more power amplifiers 1222, which are respectively coupled to one or more antennas 1224 for transmitting and receiving radio frequency signals via the WWAN broadband network. The baseband processor 1212 may also control a wireless local area network (WLAN) transceiver 1226 coupled to one or more suitable antennas 1228, which may be able to communicate via the following standards: standards based on Bluetooth, standards based on IEEE 802.11, standards based on IEEE 802.16, wireless network standards based on IEEE 802.18, 3GPP-based protocol wireless networks, wireless network standards based on the Third Generation Partnership Project Long Term Evolution (3GPP LTE), wireless network standards based on 3GPP2 Air Interface Evolution (3GPP2 AIE), wireless networks based on 3GPP-LTE-Advanced, UMTS-based protocol wireless networks, CDMA2000-based protocol wireless networks, GSM-based protocol wireless networks, cellular digital packet data (CDPD-based) protocol wireless networks, Mobitex-based protocol wireless networks, near field communication (NFC-based) links, WiGig-based networks, ZigBee-based networks, and the like. It should be noted that these are merely exemplary implementations for application processor 1210 and baseband processor 1212, and the scope of the claimed subject matter is not limited in these respects. For example, any one or more of SDRAM 1214, NAND flash memory 1216, and / or NOR flash memory 1218 may include other types of memory technologies, such as magnetic-based memory, chalcogenide-based memory, phase change-based memory, optical-based memory, or bidirectional-based memory, and the scope of the claimed subject matter is not limited in this respect.

[0090] In one or more embodiments, the application processor 1210 may drive a display 1230 for displaying various information or data, and may also receive touch input from a user, for example, via a finger or a stylus through a touch screen 1232. In an exemplary embodiment, the screen 1232 displays menus and / or options for inputting information to the information processing system 1200 to the user, which may be selected by a finger and / or a stylus.

[0091] The ambient light sensor 1234 may be used to detect the amount of ambient light in which the information handling system 1200 is operating, for example, to control the brightness or contrast value of the display 1230 based on the intensity of the ambient light detected by the ambient light sensor 1234. One or more cameras 1236 may be used to capture images processed by the application processor 1210 and / or images stored at least temporarily in the NAND flash memory 1216. In addition, the application processor may be coupled to a gyroscope 1238, an accelerometer 1240, a magnetometer 1242, an audio encoder / decoder (CODEC) 1244, and / or a GPS controller 1246 coupled to an appropriate global positioning system (GPS) antenna 1248 for detecting various environmental attributes, including the location, movement, and / or orientation of the information handling system 1200. Alternatively, the controller 1246 may include a global navigation satellite system (GNSS) controller. The audio CODEC 1244 may be coupled to one or more audio ports 1250 to provide microphone input and speaker output via internal devices and / or via external devices coupled to the information processing system through the audio ports 1250 (e.g., through headphone and microphone jacks). In addition, the application processor 1210 may be coupled to one or more input / output (I / O) transceivers 1252 to couple to one or more I / O ports 1254, such as a universal serial bus (USB) port, a high-definition multimedia interface (HDMI) port, a serial port, etc. In addition, one or more of the I / O transceivers 1252 may be coupled to one or more memory slots 1256 for optional removable memory, such as a secure digital (SD) card or a subscriber identity module (SIM) card, although the scope of the claimed subject matter is not limited in these respects.

[0092] Fig.13 Describes one or more embodiments disclosed herein. Fig.12 An isometric view of an exemplary embodiment of an information handling system that may optionally include a touch screen. Fig.13An exemplary implementation of an information handling system 1300 tangibly embodied as a cellular phone, a smart phone, a smart-type device, or a tablet-type device, etc., is shown, which can implement the method for identifying a victim party and a source of interference according to the subject matter disclosed herein. In one or more embodiments, the information handling system has a housing 1310 having a display 1330, which may include a touch screen 1332 for receiving tactile input controls and commands via a user's finger 1316 and / or via a stylus 1315 to control one or more application processors 1210. The housing 1310 may house one or more components of the information handling system 1300, such as one or more application processors 1210 and one or more of SDRAM 1214, NAND flash memory 1216, NOR flash memory 1218, baseband processor 1212, and / or WWAN transceiver 1220. The information handling system 1300 may also optionally include a physical actuator area 1320, which may include a keyboard or buttons for controlling the information handling system 1300 via one or more buttons or switches. The information handling system 1300 may also include a memory port or slot 1356 for receiving non-volatile memory (e.g., flash memory) in the form of, for example, a secure digital (SD) card or a subscriber identity module (SIM) card. Optionally, the information handling system 1300 may also include one or more speakers and / or microphones 1324 and a connection port 1354 for connecting the information handling system 1300 to another electronic device, a dock, a display, a battery charger, etc. In addition, the information handling system 1300 may include a headphone or speaker jack 1328 and one or more cameras 1336 on one or more sides of the housing 1310. It should be noted that Fig.13 Information handling system 1300 may include more or fewer elements than shown, in various arrangements, and the scope of the claimed subject matter is not limited in this respect.

[0093] As used herein, the term "circuit" may refer to, be part of, or include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and / or memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, and / or other suitable hardware components that provide the described functionality. In some embodiments, the circuit may be implemented in one or more software or firmware modules, or the functionality associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, the circuit may include logic that is at least partially operable in hardware.

[0094] The embodiments described herein may be implemented into a system using any suitably configured hardware and / or software. Fig.14Example components of a user equipment (UE) device 1400 are shown with respect to one embodiment. In some embodiments, the UE device 1400 may include application circuitry 1402, baseband circuitry 1404, radio frequency (RF) circuitry 1406, front end module (FEM) circuitry 1408, and one or more antennas 1410, coupled together at least as shown.

[0095] The application circuit 1402 may include one or more application processors. For example, the application circuit 1402 may include circuits such as, but not limited to, one or more single-core processors or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to and / or may include memory / storage, and may be configured to: execute instructions stored in the memory / storage to enable various applications and / or operating systems to run on the system.

[0096] The baseband circuit 1404 may include circuits such as, but not limited to, one or more single-core processors or multi-core processors. The baseband circuit 1404 may include one or more baseband processors and / or control logic to process baseband signals received from the receive signal path of the RF circuit 1406 and generate baseband signals for the transmit signal path of the RF circuit 1406. The baseband processing circuit 1404 may interface with the application circuit 1402 to generate and process baseband signals and control the operation of the RF circuit 1406. For example, in some embodiments, the baseband circuit 1404 may include a second generation (2G) baseband processor 1404a, a third generation (3G) baseband processor 1404b, a fourth generation (4G) baseband processor 1404c, and / or other baseband processors 1404d for other existing generations, generations under development, or generations to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 1404 (e.g., one or more of the baseband processors 1404a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1406. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 1404 may include fast Fourier transform (FFT), precoding, and / or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 1404 may include convolution, tail-biting convolution, turbo, Viterbi, and / or low-density parity check (LDPC) encoder / decoder functions. The embodiments of the modulation / demodulation and encoder / decoder functions are not limited to these examples, and may include other suitable functions in other embodiments.

[0097] In some embodiments, the baseband circuit 1404 may include elements of a protocol stack, such as elements of an Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocol, including, for example, physical (PHY) elements, medium access control (MAC) elements, radio link control (RLC) elements, packet data convergence protocol (PDCP) elements, and / or radio resource control (RRC) elements. A central processing unit (CPU) 1404e of the baseband circuit 1404 may be configured to run elements of the protocol stack for signaling of the PHY layer, the MAC layer, the RLC layer, the PDCP layer, and / or the RRC layer. In some embodiments, the baseband circuit may include one or more audio digital signal processors (DSPs) 1404f. The audio DSP 1404f may include elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, the components of the baseband circuit may be suitably combined in a single chip, a single chipset, or be arranged on the same circuit board. In some embodiments, some or all constituent components of the baseband circuit 1404 and the application circuit 1402 may be implemented together, for example, on a system on a chip (SOC).

[0098] In some embodiments, baseband circuitry 1404 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 1404 may support communications with an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and / or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), wireless personal area networks (WPANs). Embodiments in which baseband circuitry 1404 is configured to support radio communications of more than one radio protocol may be referred to as multi-mode baseband circuitry.

[0099] RF circuit 1406 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, RF circuit 1406 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 1406 may include a receive signal path, which may include circuitry for down-converting an RF signal received from FEM circuit 1408 and providing a baseband signal to baseband circuit 1404. RF circuit 1406 may also include a transmit signal path, which may include circuitry for up-converting a baseband signal provided by baseband circuit 1404 and providing an RF output signal to FEM circuit 1408 for transmission.

[0100] In some embodiments, the RF circuit 1406 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuit 1406 may include a mixer circuit 1406a, an amplifier circuit 1406b, and a filter circuit 1406c. The transmit signal path of the RF circuit 1406 may include a filter circuit 1406c and a mixer circuit 1406a. The RF circuit 1406 may also include a synthesizer circuit 1406d for synthesizing the frequencies used by the mixer circuit 1406a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 1406a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1408 based on the synthesized frequency provided by the synthesizer circuit 1406d. The amplifier circuit 1406b may be configured to amplify the down-converted signal, and the filter circuit 1406c may be a low pass filter (LPF) or a band pass filter (BPF), which are configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 1404 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, but this is not a requirement. In some embodiments, the mixer circuit 1406a of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited thereto.

[0101] In some embodiments, the mixer circuit 1406a of the transmit signal path can be configured to up-convert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 1406d to generate an RF output signal for the FEM circuit 1408. The baseband signal can be provided by the baseband circuit 1404 and can be filtered by the filter circuit 1406c. The filter circuit 1406c can include a low pass filter (LPF), but the scope of the embodiment is not limited in this regard.

[0102] In some embodiments, the mixer circuit 1406a of the receive signal path and the mixer circuit 1406a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and / or up-conversion, respectively. In some embodiments, the mixer circuit 1406a of the receive signal path and the mixer circuit 1406a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 1406a of the receive signal path and the mixer circuit 1406a of the transmit signal path may be arranged for direct down-conversion and / or direct up-conversion, respectively. In some embodiments, the mixer circuit 1406a of the receive signal path and the mixer circuit 1406a of the transmit signal path may be configured for superheterodyne operation.

[0103] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, but the scope of the embodiments is not limited thereto. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 1406 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 1404 may include a digital baseband interface to communicate with the RF circuit 1406.

[0104] In some dual-mode embodiments, separate radio IC circuits may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this regard.

[0105] In some embodiments, synthesizer circuit 1406d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this regard, as other types of frequency synthesizers may be suitable. For example, synthesizer circuit 1406d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0106] The synthesizer circuit 1406d may be configured to synthesize, based on the frequency input and the divider control input, an output frequency used by the mixer circuit 1406a of the RF circuit 1406. In some embodiments, the synthesizer circuit 1406d may be a fractional-N / N+1 synthesizer.

[0107] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), but this is not required. Depending on the desired output frequency, the divider control input may be provided by the baseband circuit 1404 or the application processor 1402. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application processor 1402.

[0108] The synthesizer circuit 1406d of the RF circuit 1406 may include a divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay element may be configured to decompose the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0109] In some embodiments, the synthesizer circuit 1406d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency), and used in conjunction with the quadrature generator and divider circuits to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be an LO frequency (fLO). In some embodiments, the RF circuit 1406 can include an IQ / polar converter.

[0110] FEM circuitry 1408 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 1410, amplify the received signals, and provide an amplified version of the received signals to RF circuitry 1406 for further processing. FEM circuitry 1408 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by RF circuitry 1406 for transmission by one or more of the one or more antennas 1410.

[0111] In some embodiments, the FEM circuit 1408 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include a low noise amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 1406). The transmit signal path of the FEM circuit 1408 may include: a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 1406); and one or more filters for generating an RF signal for subsequent transmission (e.g., by one or more of the one or more antennas 1410).

[0112] In some embodiments, the UE device 1400 may include additional elements, such as memory / storage, displays, cameras, sensors, and / or input / output (I / O) interfaces.

[0113] The following are further examples.

[0114] Example 1 is a device of a network entity capable of managing a packet data network (PDN) connection for a user equipment (UE), comprising a processing circuit for: determining to switch the UE from a first PDN connection managed by a first PDN gateway (P-GW) to a second PDN connection; selecting a second P-GW to manage the second PDN connection; generating configuration data for at least one network node in the second PDN connection; and generating configuration data for an evolved Node B (eNB) in the second PDN connection.

[0115] In Example 2, the subject matter of Example 1 may further include: a sending circuit configured to: send an invitation to the UE to use the second PDN connection using at least one of access stratum signaling and non-access stratum signaling.

[0116] In Example 3, the subject matter of any of Examples 1-2 may include: the processing circuit is configured to: determine that the UE has moved from a first position close to the first P-GW to a second position close to the second P-GW.

[0117] In Example 4, the subject matter of any of Examples 3-4 may include: the transmitting circuit is configured to: provide a tunnel endpoint transport address for at least one network node in the second PDN connection to the second P-GW.

[0118] In Example 5, the subject matter of any one of Examples 1-4 may include the processing circuit being configured to: allocate at least one of a new Internet Protocol (IP) address and an IP prefix for the second PDN connection.

[0119] In Example 6, the subject matter of any one of Examples 1-5 may include the processing circuit being configured to provide a tunnel endpoint transport address for the eNB to at least one network node in the second PDN connection.

[0120] In Example 7, the subject matter of any of Examples 1-6 may include: the processing circuit is configured to: provide the eNB with a tunnel endpoint transport address for at least one network node in the second PDN connection and at least one of a new IP address and an IP prefix for the UE.

[0121] In Example 8, the subject matter of any one of Examples 1-7 may include the sending circuit being configured to send a router advertisement (RA) message including at least a portion of a new IP prefix for the UE to the UE.

[0122] In Example 9, the subject matter of any one of Examples 1-8 may include an arrangement wherein the second PDN connection is established before the first PDN connection is terminated.

[0123] Example 10 is an apparatus of an evolved Node B (eNB) capable of managing a packet data network (PDN) connection for a user equipment (UE), the eNB comprising a processing circuit for: determining to switch a portion of data traffic from the UE from a first PDN connection managed by a first packet data network gateway (P-GW) to a second PDN connection; and selecting a second P-GW to manage the second PDN connection.

[0124] In Example 11, the subject matter of Example 10 may also include: a sending circuit for: forwarding at least a portion of an Internet Protocol (IP) address for the second PDN connection and a set of routing rules to a network entity associated with a control plane for the second PDN connection; sending the at least a portion of the IP address for the second PDN connection and the routing rules to the UE; and using at least one of access stratum signaling and non-access stratum signaling to send an invitation to the UE to use the second PDN connection for a selected data service determined by the set of routing rules.

[0125] In Example 12, the subject matter of any one of Examples 10-11 may include an arrangement wherein the processing circuit is configured to: allocate a new IP address or IP prefix for the second PDN connection.

[0126] In Example 13, the subject matter of any of Examples 10-12 may include an arrangement wherein the processing circuit is configured to send a router advertisement (RA) message including at least a portion of the new IP prefix for the UE.

[0127] In Example 14, the subject matter of any of Examples 10-13 may include an arrangement wherein the second PDN connection is established before the first PDN connection is terminated.

[0128] In Example 15, the subject matter of any of Examples 10-14 may include an arrangement wherein the second PDN connection provides access to a mobile edge computing server located near the eNB.

[0129] In Example 16, the subject matter of any of Examples 10-15 may include an arrangement wherein the set of routing rules for the second PDN connection includes a prioritized list of IP addresses of UEs associated with a service selection filter, the prioritized list including one or more IP header fields and / or a list of fully qualified domain names and / or a list of application identifiers.

[0130] Example 17 is an apparatus of a network access point, comprising a processing circuit for: receiving, from an evolved Node B (eNB) that manages a first packet data network (PDN) connection with a user equipment (UE) using a first packet data network gateway (P-GW), a request to establish a second PDN connection with the UE using a second P-GW located near the network access point; and in response to the request, allocating an Internet Protocol (IP) address or an IP prefix to the second P-GW located near the network access point.

[0131] In Example 18, the subject matter of Example 17 may include: a sending circuit for: forwarding the IP address of a P-GW located near the network access point to the eNB for further forwarding to a network entity associated with a control plane for the second PDN; and sending an invitation to the UE to use the second PDN connection for a portion of the UE's data service.

[0132] In Example 19, the subject matter of any one of Examples 17-18 may include an arrangement wherein the transmitting circuit is configured to: notify the eNB via X2 signaling that the network access point is communicatively coupled to the second P-GW.

[0133] In Example 20, the subject matter of any one of Examples 17-19 may include an arrangement wherein the P-GW is co-located with the network access point.

[0134] In Example 21, the subject matter of any one of Examples 17-20 may include an arrangement wherein the second network access point comprises a booster cell located within a service area covered by the eNB.

[0135] In Example 22, the subject matter of any one of Examples 17-21 may include the sending circuit being configured to send a router advertisement (RA) message including at least a portion of a new IP prefix for the UE.

[0136] In Example 23, the subject matter of any of Examples 17-22 may include an arrangement wherein the second PDN connection is established before the first PDN connection is terminated.

[0137] Example 24 is an apparatus of an evolved Node B (eNB) capable of managing a packet data network (PDN) connection for a user equipment (UE), the eNB comprising processing circuitry for determining to switch the UE from a first packet data network gateway (P-GW) managed by a first PDN connection communicatively coupled to the eNB to a second PDN connection managed by a second P-GW communicatively coupled to a network access point; and receiving from the network access point at least one of an Internet Protocol (IP) address and an IP prefix for the second P-GW located near the network access point.

[0138] In Example 25, the subject matter of Example 24 may include: a sending circuit for: forwarding at least one of the IP address and the IP prefix for the second P-GW to a network entity associated with a control plane for the second PDN connection; forwarding the at least one of the IP address and the IP prefix for the second PDN connection and a routing rule to the UE; and sending an invitation to the UE to use the second PDN connection using at least one of access stratum signaling and non-access stratum signaling.

[0139] In Example 26, the subject matter of any one of Examples 24-25 may include the processing circuit being configured to: detect that the UE has entered a coverage area of ​​the network access point.

[0140] In Example 27, the subject matter of any of Examples 24-26 may include an arrangement wherein the second PDN connection is established before the first PDN connection is terminated.

[0141] In various examples, the operations discussed herein may be implemented as hardware (e.g., circuits), software, firmware, microcode, or a combination thereof, which may be provided as a computer program product, such as including a tangible (e.g., non-transitory) machine-readable or computer-readable medium having stored thereon instructions (or software programs) for programming a computer to perform the processes discussed herein. Additionally, as an example, the term "logic" may include software, hardware, or a combination of software and hardware. A machine-readable medium may include a storage device, such as those discussed herein.

[0142] References in the specification to "one example" or "example" mean that a particular feature, structure, or characteristic described in conjunction with the example may be included in at least one implementation. The phrase "in one example" appearing in various places in the specification may or may not all refer to the same example.

[0143] In addition, in the specification and claims, the terms "coupled" and "connected" and their derivatives may be used. In some examples, "connected" may be used to indicate that two or more elements are in direct physical or electrical contact with each other. "Coupled" may mean that two or more elements are in direct physical or electrical contact. However, "coupled" may also mean that two or more elements may not be in direct contact with each other, but may still cooperate or interact with each other.

[0144] Therefore, although the examples have been described in language specific to structural features and / or methodological acts, it should be understood that the subject matter claimed may not be limited to the specific features or acts described. Instead, the specific features and acts are disclosed as example forms of implementing the subject matter claimed.

Claims

1. One or more non-transitory computer-readable media having instructions that, when executed by one or more processors, cause a control plane network node to: Determine to switch the user equipment UE from a first user plane function node used to anchor a first connection with a data network, wherein: The first connection is associated with a first Internet Protocol (IP) address or prefix, selecting a second user plane function node for anchoring a second connection with the data network, wherein the second connection is associated with a second IP address or prefix; and sending an instruction to cause the UE to switch to the second user plane function node, One or more existing service flows are moved from the first connection to the second connection, and the first connection at least partially overlaps with the second connection in time.

2. One or more non-transitory computer-readable media according to claim 1, wherein: The instructions, when executed, further cause the control plane network node to: send the instructions in a non-access stratum (NAS) message.

3. The one or more non-transitory computer-readable media of claim 1, wherein: The instructions, when executed, further cause the control plane network node to: send at least a portion of the second IP address or prefix to the UE.

4. The one or more non-transitory computer-readable media of claim 1, wherein: When the instructions are executed, the control plane network node or the radio access network node further causes the control plane network node or the radio access network node to determine to establish the second connection.

5. The one or more non-transitory computer-readable media of claim 1, wherein: When executed, the instructions further cause the control plane network node to: instruct one or more user plane nodes to establish the second connection.

6. The one or more non-transitory computer-readable media of claim 1, wherein: When executed, the instructions further cause the control plane network node to determine, based on the geographical proximity of the UE to the second user plane function node, to switch the UE from the first user plane function node to the second user plane function node.

7. The one or more non-transitory computer readable media of claim 6, wherein: To send at least a portion of the second IP address or prefix, the control plane network node is configured to send a router advertisement message including an IPv6 prefix.

8. One or more non-transitory computer-readable media having instructions, which when executed by one or more processors, cause a user equipment UE to: communicating with a data network via a first connection anchored by a first user plane function node, the first connection being associated with a first Internet Protocol (IP) address or prefix; receiving an instruction from a network node to establish a second connection to communicate with the data network; establishing the second connection based on the instruction, wherein the second connection is anchored by a second user plane function node and is associated with a second IP address or prefix; and One or more existing traffic flows are moved from the first connection to the second connection, wherein the first connection at least partially overlaps in time with the second connection.

9. The one or more non-transitory computer readable media of claim 8, wherein: The instructions, when executed, further cause the UE to: process a non-access stratum (NAS) message to receive the instructions.

10. The one or more non-transitory computer readable media of claim 8, wherein: The instructions, when executed, further cause the UE to: receive at least a portion of the second IP address or prefix from the network node.

11. The one or more non-transitory computer readable media of claim 10, wherein: To receive at least a portion of the second IP address or prefix, the UE is configured to process a router advertisement message.

12. The one or more non-transitory computer readable media of claim 11, wherein: The second IP address or prefix comprises an IPv6 prefix.

13. One or more non-transitory computer readable media according to any one of claims 8-12, wherein: When the instructions are executed, the UE: receiving routing rules; and Based on the routing rule, data from the application is sent via the second connection.

14. A method of operating a user equipment (UE), the method comprising: communicating with a data network via a first connection anchored by a first user plane function node, the first connection being associated with a first Internet Protocol (IP) address or prefix; receiving, from a network node, an instruction to establish a second connection for communication with the data network; establishing the second connection based on the instruction, wherein the second connection is anchored by a second user plane function node and is associated with a second IP address or prefix; and One or more existing traffic flows are moved from the first connection to the second connection, wherein the first connection at least partially overlaps in time with the second connection.

15. The method according to claim 14, further comprising: At least a portion of the second IP address or prefix is ​​received from the network node.

16. The method according to claim 15, further comprising: The router advertisement message is processed to receive at least a portion of the second IP address or prefix.

17. The method according to claim 14, wherein: The second IP address or prefix comprises an IPv6 prefix.

18. The method according to any one of claims 14 to 17, further comprising: The service flow created after the second connection is established is routed to the second connection.

19. The method according to claim 18, further comprising: determining that the first connection does not support any active service flows; as well as Based on the determination that the first connection does not support any active traffic flows, the first connection is released.

Images