TWI709311B - Network initiated packet data network connection - Google Patents

Abstract

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

Description

Packet data network connection technology from the beginning of the network

The present invention relates generally to the field of electronic communications. More specifically, the aspects generally relate to the network-initiated packet data network connection in the communication system.

For example, a technology for implementing network-initiated packet data network connection can be used in an electronic communication system of an electronic device.

According to an embodiment of the present invention, a device of a network entity is specially proposed, which can manage a packet data network (PDN) connection for a user equipment (UE), and the network entity includes a processing circuit system. To: determine to switch the UE from a first PDN connection managed by a first PDN gateway (P-GW) to a second PDN connection; select a second P-GW to manage the second PDN connection ; Generate configuration data for at least one network node in the second PDN connection; and generate configuration data for an evolved NodeB (eNB) in the second PDN connection.

100‧‧‧3GPP LTE network

101‧‧‧Core Network (CN)

102‧‧‧Air interface access network E UTRAN

103‧‧‧Serving GPRS Support Node

104‧‧‧Mobile management entity

105‧‧‧Home User Server (HSS)

106‧‧‧Service Gate (SGW)

107‧‧‧Packet Data Network (PDN) Gateway

108‧‧‧Policy and Charging Rules Function (PCRF) Manager

110, 230A, 230B‧‧‧Evolved NodeB (eNB)

111, 210‧‧‧User Equipment (UE)

200‧‧‧Communication System

220‧‧‧Access Point

230, 914, 920‧‧‧Base Station (BS)

410, 415, 420, 425, 430, 435, 440, 610, 615, 620, 625, 630, 635, 810, 815, 820, 825, 830, 835, 840, 845‧‧‧ operation

900‧‧‧Wireless network

910‧‧‧Internet type network

912, 918‧‧‧Access Service Network (ASN)

916‧‧‧User Station (SS)

922‧‧‧WiMAX type client equipment (CPE)

924‧‧‧Interviewed Connectivity Service Network (CSN)

926‧‧‧Home Connectivity Service Network (CSN)

928‧‧‧Operation Support System (OSS)

1210‧‧‧Application Processor

1212‧‧‧Baseband processor

1214‧‧‧Synchronous Dynamic Random Access Memory (SDRAM)

1216‧‧‧NAND flash memory

1218‧‧‧NOR flash memory

1220‧‧‧Wireless Wide Area Network (WWAN) Transceiver

1222‧‧‧Power Amplifier

1224, 1228, 1410‧‧‧antenna

1226‧‧‧Wireless Local Area Network (WLAN) Transceiver

1230‧‧‧Display

1232‧‧‧Touch screen

1234‧‧‧Ambient Light Sensor

1236‧‧‧Camera

1238‧‧‧Gyro

1240‧‧‧Accelerometer

1242‧‧‧Magnetometer

1244‧‧‧Audio Codec/Decoder (Codec)

1246‧‧‧Global Positioning System (GPS) Controller

1248‧‧‧Global Positioning System (GPS) Antenna

1250‧‧‧Audio port

1252‧‧‧Input/Output (I/O) Transceiver

1254‧‧‧Input/Output (I/O) Port

1256‧‧‧Memory slot

1400‧‧‧User Equipment (UE) Device

1402‧‧‧Application circuit system

1404‧‧‧Baseband circuit system

1404a‧‧‧The second generation (2G) baseband processor

1404b‧‧‧The third generation (3G) baseband processor

1404c‧‧‧Fourth generation (4G) baseband processor

1404d‧‧‧Other baseband processors

1404e‧‧‧Central Processing Unit (CPU)

1404f‧‧‧Audio Digital Signal Processor (DSP)

1406‧‧‧Radio Frequency (RF) Circuit System

1406a‧‧‧Mixer circuit system

1406b‧‧‧Amplifier circuit system

1406c‧‧‧Filter circuit system

1406d‧‧‧Synthesizer circuit system

1408‧‧‧Front End Module (FEM) Circuit System

S1, S3, S4, S5‧‧‧interface

Refer to the drawings to provide a detailed description. Use phases in different graphs Same reference numbers indicate similar or identical objects.

FIG. 1 is a schematic block diagram illustration of components in a 3GPP LTE network that can implement a network-initiated packet data network connection in a communication system according to various examples discussed herein.

FIG. 2 is a schematic illustration of a network architecture that can implement a network-initiated packet data network connection in a communication system according to various examples discussed herein.

3 is a schematic illustration of a first example network architecture that can implement a network-initiated packet data network connection in a communication system according to various examples discussed herein.

FIG. 4 illustrates the high-level operations in the method for implementing the network-initiated packet data network connection in the communication system according to various examples discussed herein.

5 is a schematic illustration of a second example network architecture that can implement network-initiated packet data network connection in a communication system according to various examples discussed herein.

FIG. 6 illustrates the high-level operations in the method for implementing the network-initiated packet data network connection in the communication system according to the various examples discussed herein.

FIG. 7 is a schematic illustration of a third example network architecture that can implement network-initiated packet data network connection in a communication system according to various examples discussed herein.

FIG. 8 illustrates the method for implementing the network-initiated packet data network connection in the communication system according to various examples discussed in this article High-level operations.

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

10 and 11 are respectively schematic block diagrams illustrating the radio interface protocol structure based on the 3GPP-type radio access network standard between the UE and the eNodeB according to one or more exemplary embodiments disclosed herein.

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

FIG. 13 is an isometric view of an exemplary embodiment of an information processing system that may optionally include a touch screen according to one or more embodiments disclosed herein.

FIG. 14 is a schematic block diagram illustration of the components of a wireless device according to one or more exemplary embodiments disclosed herein.

It should be understood that, for the sake of simplicity and/or clarity, the elements illustrated in the figures are not necessarily drawn to scale. For example, for clarity, the size of some elements may be enlarged relative to other elements. In addition, when deemed appropriate, reference numbers have been repeated in the figures to indicate corresponding and/or similar elements.

In the following description, numerous specific details are explained in order to provide a thorough understanding of various examples. However, various examples can be practiced without specific details. In other cases, well-known methods, procedures, components and circuits have not been described in detail so as not to confuse specific examples. In addition, you can use Various components (such as integrated semiconductor circuits ("hardware"), computer readable instructions organized into one or more programs ("software"), or a certain combination of hardware and software) execute various aspects of the instance. For the purpose of the present invention, reference to "logic" shall mean hardware, software or some combination thereof.

Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. Therefore, the phrases "in one embodiment" or "in an embodiment" appearing in different places throughout this specification do not necessarily all refer to the same embodiment. In addition, in one or more embodiments, specific features, structures, or characteristics can be combined 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 better or superior to other embodiments.

The various operations can be described as multiple discrete operations in sequence and in a manner that is most helpful in understanding the claimed subject matter. However, the order of description should not be interpreted as implying that these operations must depend on the order. In detail, these operations need not be performed in the order of presentation. The operations described may be performed in a different order from the described embodiments. Various additional operations may be performed, and/or the described operations may be omitted in additional embodiments.

Continuity of services in mobile networks is sometimes regarded as synonymous with Internet Protocol (IP) addresses. In order to achieve service continuity, the mobile device can be assigned an Internet protocol (IP) address hosted at an "IP anchor" node (that is, a packet gateway (PGW) in the core network). Can be tunneled The traffic between the mobile device and the IP anchor node is transmitted, and the IP routing is only used in the packet data network starting at the IP anchor node. The data path of the tunnel transmission can lead to inefficient resource usage in certain scenarios (for example, two UEs under the same eNB communicate with each other via long hairpins).

Various applications today can withstand IP address changes. An example of these applications includes an application based on the Session Initiation Protocol (SIP), where a "SIP reINVITE" message is sent to update the remote party to a new IP address that will be used as a contact address for future user plane communications. Another example includes applications based on Dynamic Adaptive Streaming (DASH) via HTTP. DASH-based applications can withstand IP address changes and resume content delivery from different content distribution servers. This is achieved by associating the content segment with the globally unique delivery non-dependent tag (URL), so that the streaming client can always determine the next serial content segment and from the content distribution network (including from different servers) ) Request content segmentation.

It is also possible to ensure service continuity at the transport layer by using an evolved transport protocol such as Multipath TCP (MPTCP). The MPTCP client can dynamically add or remove substreams carried by different IP addresses without affecting the byte stream sent by the representative application.

As the amount of multimedia broadband data continues to grow, it may be useful for 3GPP systems to select IP anchor nodes (ie, PGW) that are located close to the edge of the radio access network and the current location of the user equipment (UE) . This will allow IP traffic to be shared from the user plane of the 3GPP system to the traditional IP routing network near the edge of the network. This will reduce the tunneling segmentation of the data path and increase the IP routing portion. this This includes increasing the scalability of the user plane nodes of the 3GPP system, enhancing the end-to-end communication path by avoiding triangular path selection through the IP anchor node, and reducing the end-to-end latency of data transmission. In addition, content delivery can be resumed from content distribution servers that are geographically closer to the UE, which further reduces the traffic load on the 3GPP network.

The 3GPP communication system can use the Selected IP Traffic Sharing (SIPTO) feature to share traffic by assigning a new geographically closer PGW node when the existing PGW node is deemed suboptimal. However, in the case of SIPTO, the communication system first disarms the existing PGW node before acquiring the new PGW node and the new IP address, which makes it a "break-before-make" type of solution. Although adjustable streaming applications can withstand IP address changes, it depends on factors such as the amount of buffered segments in the UE, the streaming rate, and the time required to re-establish an HTTPS connection. Temporary wear and tear can still be significant to users.

For 3GPP communication systems, it may be useful to utilize the capabilities of the upper layer protocols (ie, application and/or transport layer) to help withstand IP address changes. By knowing that the application can withstand 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 the connection to the two IP anchor nodes during the transition period. Once the traffic (for example, by using SIP reINVITE, DASH or MPTCP mechanism) is merged to the new IP address, the system can release the connection to the old IP anchor node.

The following describes the implementation of the communication system with reference to Figures 1 to 14 The technology of network-initiated packet data network connection and the features and characteristics of communication systems that can incorporate these technologies.

Figure 1 shows an exemplary block diagram of the overall architecture of a 3GPP LTE network 100 including one or more devices according to the subject matter disclosed herein. One or more devices can be implemented to implement the network in the communication system. The method of initial packet data network connection. Figure 1 also generally shows exemplary network components and exemplary standardized interfaces. At a high level, the network 100 includes a core network (CN) 101 (also known as Evolved Packet System (EPC)) and an air interface access network E UTRAN 102. CN 101 is responsible for the overall control of various user equipment (UE) connected to the network and the establishment of bearers. Although not explicitly depicted, CN 101 may include functional entities (such as home agents and/or ANDSF servers or entities). E UTRAN 102 is responsible for all radio-related functions.

The main exemplary logical nodes of CN 101 include (but are not limited to) the service GPRS support node 103, the mobile management entity 104, the home user server (HSS) 105, the service gate (SGW) 106, and the packet data network (PDN) gate. The router 107 and the policy and charging rules function (PCRF) manager 108. The functionality of each of the network elements of CN 101 is well known and is not described herein. Each of the network elements of CN 101 is interconnected by well-known exemplary standardized interfaces, some of which are indicated in FIG. 1, such as interfaces S3, S4, S5, etc., but are not described in this document.

Although CN 101 includes many logical nodes, E UTRAN access network 102 is composed of at least one node (such as evolution A NodeB (base station (BS), eNB, or eNodeB) 110 is formed, at least one node is connected to one or more user equipment (UE) 111, and only one of the user equipment is depicted in FIG. 1A. The UE 111 is also referred to herein as a wireless device (WD) and/or a subscriber station (SS), and may include an M2M type device. In one example, the UE 111 may be coupled to the eNB through the LTE-Uu interface. In an exemplary configuration, a single cell of the E UTRAN access network 102 provides a substantially regionalized geographic transmission point (with multiple antenna devices), and the transmission point provides access to one or more UEs. In another exemplary configuration, a single cell of the E UTRAN access network 102 provides multiple geographically substantially isolated transmission points (each with one or more antenna devices), wherein each transmission point provides a pair of Access to one or more UEs in which the transmission bit is defined for one cell, so that all UEs share the same spatial transmission size calibration. For ordinary user traffic (compared to broadcasting), there is no centralized controller in E-UTRAN; therefore, the E-UTRAN architecture is called flat. eNBs are usually interconnected to each other through an interface called "X2" and to the EPC through an S1 interface. More specifically, the eNB is connected to the MME 104 through the S1 MME interface and is connected to the SGW 106 through the S1 U interface. The agreement performed between the eNB and the UE is usually called an "AS agreement". The details of the various interfaces are well known and not described in this article.

eNB 110 managed entity (PHY) layer, medium access control (MAC) layer, radio link control (RLC) layer, and packet data control protocol (PDCP) layer. These layers are not shown in Figure 1 and include the use of The functionality of flat header compression and encryption. The eNB 110 also provides radio resource control (RRC) functionality corresponding to the control plane, and performs many functions, including Radio resource management, admission control, scheduling, negotiation of uplink (UL) QoS enforcement, cell information broadcast, user and control plane data encryption/decryption, and DL/UL user plane packet header compression /unzip.

The RRC layer in 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 the UE in both uplink and downlink , The header compression for the effective use of the radio interface, the security of all data sent via the radio interface, and the connectivity to the EPC. The RRC layer makes handover decisions based on the measurement results of neighboring cells sent by UE 111, generates air paging for UE 111, broadcasts system information, and controls the periodicity of UE measurement reports (such as channel quality information (CQI) reports) ), and assign the cell-level temporary identifier to the active UE 111. The RRC layer also performs the transfer of the UE from the source eNB to the target eNB during the handover, and provides integrity protection for the RRC message. In addition, the RRC layer is responsible for the establishment and maintenance of radio bearers.

FIG. 2 is a schematic illustration of a network architecture of a communication system 200 capable of implementing a network-initiated packet data network connection in a communication system according to various examples discussed herein. The system 200 may include one or more cells, and each of the cells may include one or more segments. Each cell contains at least one base station (BS) 230. A plurality of UEs 210 may be located throughout the system 200. The system 200 may further include one or more access points 220 that can transmit traffic from the UE 210 to the communication network.

The base station 210 can be embodied as (but not limited to) evolved NodeB (eNB or eNodeB), giant base station, small base station, ultra Micro base station or the like. UE 220 can be embodied as (but not limited to) mobile station (MS), subscriber station (SS), machine-to-machine (M2M) device, client equipment (CPE), user equipment (UE), notebook computer, Tablet-type devices, cellular phones, smart devices, smart phones, personal digital assistants, information processing systems, or the like as described herein. The access point 220 may be embodied as (but not limited to) a WLAN access point.

Figures 3 to 4 depict a first example of a network-initiated packet data network connection in a communication system. In the example depicted in FIGS. 3 to 4, the UE 210 can move from the coverage area served by the first eNB 230A to the coverage area served by the second eNB 230B, thereby triggering the change of the packet data network connection of the UE 210 . 3, at a first point in time, UE 210 can be served by the first eNB 230A coupled to the first packet data network gateway PGW-1, and PGW-1 provides access to the IP network (for example, Internet Way) the first packet data network connection. At the second point in time, the UE 210 can move to a different location in the coverage area provided by the second eNB 230B coupled to the second packet data network gateway PGW-2, which is provided to the IP network ( For example, the second packet data network connection of the Internet.

FIG. 4 depicts the operation of implementing a network-initiated packet data network connection in the operating environment depicted in FIG. 3. Referring to FIG. 4, the UE 210 is first in the coverage area served by the first eNB 230A, and has an established packet data network connection (PDN1) provided by the first packet data network gateway (PGW-1). The packet data network connection involves the first eNB 230A, the user plane part of the first packet data network gateway PGW1, and may include one or more intermediate user plane nodes that provide SGW functionality. The UE 210 is assigned an IP address/preamble (ie, IP@1). It should be noted that the existence of any intermediate U-plane nodes (including nodes with SGW-U functionality) is omitted from the figures for simplicity. In addition, it should be noted that although FIG. 3 depicts GTP-U as an example of a tunneling protocol in the user plane, other tunneling protocols (for example, GRE) may be used.

When the UE 210 moves from the coverage area served by the first eNB 230A to the coverage area served by the second eNB 230B, the network determines that the traffic is no longer loaded to the first packet data gateway (PGW-1) Best, and changing the IP anchor can be useful. In some instances, this determination can be made by circuitry in the eNB. In other examples, the circuit system can be used in different network entities, for example, the network entity can make this determination in the control plane (C-plane) cloud.

In some instances, the network entity in the C-plane cloud selects the new packet data network function (PGW2) that is geographically closer to the current location of the UE 210, and responds (operation 410) to the second packet data network gateway ( For example, the user plane function in PGW2) is configured for new packet data network connection. The configuration parameter may include at least one tunnel endpoint transmission address used for tunneling toward the next-hop U-plane node (for example, the SGW node for PDN1). In this process, the packet data network gateway PGW2 allocates a new IP address/preamble (IP@2) and sends it to the network entity in the C-plane cloud.

In response to switching the UE 210 free first packet data network connection managed by the first packet data network gateway (PGW-1) to the second packet data network connection managed by the second packet data network gateway (PGW-2) Packet Data Network To determine the path connection, the network (operation 415) configures the second packet data network gateway (PGW-2) and any intermediate U-plane node. For example, the network entity in the C-plane cloud configures the next-hop U-plane node (in this example, the same SGW-U used for PDN1). The configuration parameters include at least one tunnel endpoint transmission address for tunneling towards the next-hop U-plane node (for example, eNB on one side and PGW2 on the other side).

The network entity in the C-plane cloud configures the new PDN connection in the second eNB 230B (operation 420). In some examples, the configuration parameters may include the tunnel endpoint transfer address and the new IP address/preamble (IP@2) for tunneling towards the next-hop U-plane node (for example, the SGW2 node) .

When a new PDN connection (PDN2) is configured, the network entity informs 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 the access stratum (AS) and non-access stratum (NAS) transmissions in the 5G evolved packet system, it can be from the network entity in the C-plane cloud (operation 425) or from the second eNB 230B ( Operation 430) Provide this information. For example, AS messaging allows the UE to directly communicate with the eNB using the Radio Resource Control (RRC) protocol. NAS messaging allows the UE to pass through (for example, between the UE and eNB) RRC and through (for example, between the eNB and a network entity in the C-plane cloud) S1- The AP communicates directly with (for example, in the C-plane cloud) network entities.

When IPv6 is used for eNB 230B (as the default IP route (Operation 435), sending (operation 435) a router advertisement (RA) message containing a new IPv6 prefix (IP@2) to allow the UE 210 to perform stateless address auto-configuration with this prefix. The UE may use router solicitation to trigger RA as appropriate.

Based on the information received during the configuration process, UE 210 starts (operation 440) to use IP@2 for new traffic, and by using upper-layer mobility mechanisms (for example, SIP reINVITE, DASH, MPTCP) (in When possible) Mobile communications from existing applications on the new IP interface.

Figures 5 to 6 depict a second example of the network-initiated packet data network connection in the communication system. In the example depicted in FIGS. 5-6, the UE 210 can operate in a mobile edge computing (MEC) environment, where IT and cloud are provided in a radio access network (RAN) closely adjacent to the user equipment 210 Calculate ability. Mobile edge computing allows acceleration of content, services and applications, thereby increasing responsiveness from the edge of the network.

The MEC server (for example, a content distribution network (CDN) server) can be co-located with the eNB, or it can be located at a neighboring eNB. In the case that the MEC server is located near an eNB, the MEC server is reachable through the local IP network and can be shared by multiple eNBs. In the case of colocation, the eNB detects all IP packets and redirects appropriate packets to the colocation MEC server. In this case, there is no need to assign a new IP address/preamble to the UE.

In contrast, when the MEC server is an independent server, it may be beneficial for the UE to use different IP addresses/preambles. If the MEC server is not a standalone server, the eNB applies generally (and in particular, for IPv6) NAT functionality that is not required. In this case, the eNB starts Initiate PDN connection with the functional network of the local gateway (LGW).

It should be noted that in some instances, the UE may use two different packet data networks (for example, the Internet and the local IP network), and the UE needs to be equipped to assist the UE to select the appropriate source IP address/preamble The path selection strategy, the appropriate source IP address/preamble and the correct IP network are selected. Examples of routing strategies (or routing rules) include the use of application ID (refers to the application in the UE that initiates the packet), FQDN (refers to the FQDN resolved into the destination IP address), and IP packet header ( Specifically, the selected field in the destination IP address and protocol). For each of these parameters, the path selection strategy lies in a prioritized list of UE (ie, "source") IP addresses/preambles.

FIG. 6 depicts the operation of implementing a network-initiated packet data network connection in the operating environment depicted in FIG. 5. Referring to FIG. 6, UE 210 is first in the coverage area served by the first eNB 230A, and has an established packet data network connection (PDN1) provided by the first packet data network gateway (PGW-1). The packet data network connection involves the first eNB 230A, the user plane part of the first packet data network gateway PGW1, and may include one or more intermediate user plane nodes that provide SGW functionality. The UE 210 is assigned an IP address/preamble (IP@1).

At operation 610, the eNB determines (for example, based on packet detection and analysis of the destination IP address in the packet header, that the eNB realizes that the packet flows to the Internet that provides the same service as the local MEC server The server in the road) can be useful for changing the IP anchor for the traffic flow to the local MEC server. In some instances, the eNB 230A can borrow The circuit system makes this determination. In other examples, the circuit system can be used in different network entities, for example, the network entity can make this determination in the control plane (C-plane) cloud. In response to the determination, the eNB 230A selects a new packet data network function (PGW2) that includes co-located LGW functionality.

The eNB 230 (operation 615) informs 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 path selection rules may include:

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

Rule 2: For the destination IP address="ff02::1:3" only use IP@2.

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

The network entity informs 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 transmissions 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).

When IPv6 is used for NB (acts as a default IP router), (operation 630) sends a router advertisement (RA) message containing a new IPv6 prefix (IP@2) to the UE to allow the UE to perform statelessness with this prefix The address is automatically configured. The UE may use router solicitation to trigger RA as appropriate.

When IPv6 is used for eNB 230B (acting as a default IP router), sending a router advertisement (RA) message containing a new IPv6 prefix (IP@2) allows UE 210 to perform stateless address automatic grouping with this prefix Match. The UE may use router solicitation to trigger RA as appropriate.

Based on the information received during the assembly process, the UE 210 starts to use (operation 635) IP@1 and IP@2 according to the provided path selection rules.

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

FIG. 8 depicts the operation of implementing a network-initiated packet data network connection in the operating environment depicted in FIG. 7. Referring to FIG. 4, the UE 210 is first in the coverage area served by the eNB 230 and has an established packet data network connection (PDN) provided by the first packet data network gateway (PGW). The packet data network connection involves the eNB 230A, the user plane part of the first packet data network gateway PGW1, and may include one or more intermediate user plane nodes that provide SGW functionality. The UE 210 is assigned an IP address/preamble (IP@1).

When the UE is moved from the coverage area served by the eNB 230 to the area covered by the network access point 220 such as the booster cell (also referred to as a secondary eNB or SeNB herein), the eNB 230 determines (operation 810) Add the network access point 220 in the dual connectivity (DC) configuration. When the DC mode is active, the UE still has only one radio resource control (RRC) connection, and the RRC connection is provided via the eNB 230. In other words, the network access point 220 is only used for user plane traffic, and the bearers routed through the network access point 220 are controlled by the eNB 230. The traffic exchanged via the network access point 220 is empty to/from the packet core network via the X2 communication link. In other examples, user plane traffic can be exchanged on the direct interface between the network access point 220 and the service gateway. In some deployment scenarios, it may be beneficial to share the selected traffic flow at the network access point 220 (ie, at the secondary eNB).

The eNB 230 forwards (operation 815) a request to establish a packet data network connection (PDN2) with the co-located 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/preamble (IP@2), and responds to the eNB 230, and the eNB 230 (operation 825) reports to the network entity in the C-plane cloud Notify the new PDN connection including the assigned IP address/prefix (IP@2), and also indicate that this is a PDN connection from the network access point 220.

In some instances, the network entity in the C-plane cloud notifies the UE 210 (operation 830) of the availability of the second packet data network (PDN2), and provides a new IP address/prefix (IP@2), and also Indicates that this is a PDN connection from the network access point 220. In other examples, depending on the separation between AS and NAS transmissions in the 5G evolved packet system, the eNB 230 may provide this information.

When the new PDN connection (PDN2) is configured, the network entity notifies the UE 210 (operation 835) of the availability of PDN2, and invites the UE 210 Start using the new IP address/prefix (IP@2). Depending on the separation between AS and NAS transmissions 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.

When IPv6 is used for eNB 230B (acting as a default IP router), sending (operation 840) a router advertisement (RA) message containing a new IPv6 prefix (IP@2) allows UE 210 to perform statelessness with this prefix The address is automatically configured. The UE may use router solicitation to trigger RA as appropriate.

Based on the information received during the configuration process, UE 210 starts to use (operation 845) IP@2 for the new traffic, and by using upper-layer mobility mechanisms (for example, SIP reINVITE, DASH, MPTCP) (in When possible) Mobile communications from existing applications on the new IP interface.

FIG. 9 is a schematic block diagram illustration of a wireless network 900 according to one or more exemplary embodiments disclosed herein. One or more of the components of the wireless network 900 may be capable of implementing methods for identifying victims and intruders based on the subject matter disclosed herein. As shown in Figure 9, the network 900 can be an Internet Protocol (IP-type) network (including the Internet-type network 910), or can support mobile wireless access to the Internet 910 and/or Similar to fixed wireless access.

In one or more instances, the network 900 can operate in compliance with the Worldwide Interoperability for Microwave Access (WiMAX) standard or its descendant WiMAX, and in a specific instance, can comply with the IEEE 802.16-based standard (for example, , IEEE 802.16e), or standards based on IEEE 802.11 (for example, IEEE 802.11 a/b/g/n standards), etc. In one or more alternative instances, the network 900 can comply with the third-generation partner program leader Future Evolution (3GPP LTE), 3GPP2 Air Interface Evolution (3GPP2 AIE) standards and/or 3GPP LTE-advanced standards. Generally speaking, the network 900 can include any type of wireless network based on orthogonal frequency division multiple access (based on OFDMA), for example, WiMAX compatible networks, Wi-Fi Alliance compatible networks, and digital users Line type (DSL type) network, asymmetric digital subscriber line type (ADSL type) network, ultra-wideband (UWB) compatible network, wireless universal serial bus (USB) compatible network, 4th generation (4G) Type network, etc., and the scope of the claimed subject matter is not limited to these aspects.

As an example of mobile wireless access, the access service network (ASN) 912 can be coupled with the base station (BS) 914 to provide a subscriber station (SS) 916 (also referred to as a wireless terminal in this article) and the Internet Wireless communication between networks 910. In one example, the user station 916 may include a mobile device or an information processing system capable of wireless communication via the network 900, for example, a notebook computer, a cellular phone, a personal digital assistant, an M2M type device, or the like . In another example, the subscriber station can provide uplink transmission power control techniques that reduce interference experienced at other wireless devices in accordance with the subject matter disclosed herein. The ASN 912 may 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 radio equipment that provides radio frequency (RF) communication with the subscriber station 916, for example, and may include physical layer (PHY) and medium access control (MAC) layer equipment that comply with the IEEE 802.16e type standard. The base station 914 may further include an IP backplane to be coupled to the Internet 910 via the ASN 912, but the scope of the claimed subject matter is not limited to these aspects.

The network 900 may further include a visited connectivity service network (CSN) 924, which can provide one or more network functions (including but not limited to proxy and/or relay-type functions (for example, authentication , Authorization and account processing (AAA) functions, dynamic host configuration protocol (DHCP) functions or domain name service control or the like), domain gateways (such as public switched telephone network (PSTN) gateways or the Internet) Voice over protocol (VoIP) gateway) and/or Internet protocol type (IP type) server functions, or the like). However, these are only examples of the types of functions that can be provided by the interviewed CSN or the native CSN 926, and the scope of the claimed subject matter is not limited to these aspects.

For example, in the part where the visited CSN 924 is not the regular service provider of the subscriber station 916, for example, the subscriber station 916 roams away from its home CSN (such as the home CSN 926), or for example, the network 900 is the subscriber station The visited CSN 924 may be referred to as a visited CSN when the network 900 may be in another location or another state that is not the main or home location of the subscriber station 916.

In a fixed wireless configuration, the WiMAX-type customer premise equipment (CPE) 922 can be located in a home or enterprise in a manner similar to the access by the user station 916 through the base station 914, ASN 912, and visited CSN 924. 920, ASN 918 and native CSN 926 have broadband access to Internet 910 for home or business users. The difference is that WiMAX CPE 922 is usually placed in a static location, but it can be moved to different locations as needed. For example, If the user station 916 is within the range of the base station 914, the user station can be used at one or more locations.

It should be noted that CPE 922 does not necessarily include WiMAX type Terminals, for example, may include other types of terminals or devices that are compatible with one or more standards or protocols as discussed herein, and may generally include fixed or mobile devices. In addition, in an exemplary embodiment, CPE 922 can provide uplink transmission power control techniques that reduce interference experienced at other wireless devices according to the subject matter disclosed herein.

According to one or more examples, the operation support system (OSS) 928 may be part of the network 900 to provide management functions for the network 900 and provide an interface between the functional entities of the network 900. The network 900 of FIG. 9 is only one type of wireless network showing a certain number of components of the network 900; however, the scope of the claimed subject matter is not limited to these aspects.

Figures 10 and 11 respectively depict an exemplary radio interface protocol structure between UE and eNodeB, which is based on the 3GPP-type radio access network standard and can provide the reduction of the subject matter disclosed in this article as experienced in other wireless devices Interference uplink transmission power control technology. More specifically, FIG. 10 depicts individual layers of the radio protocol control plane, and FIG. 11 depicts individual layers of the radio protocol user plane. The protocol layers in FIGS. 10 and 11 can be classified into the L1 layer (the first layer), the L2 layer (the second layer), and the L3 layer (the third layer) based on the lower three layers of the OSI reference model widely known in the communication system.

The physical (PHY) layer (which is the first layer (L1)) uses physical channels to provide information transfer services to the upper layer. The physical layer is connected to the media access control (MAC) layer via the transport channel, and the MAC layer is located above the physical layer. Data is transferred between the MAC layer and the PHY layer via the transmission channel. Transmission channels are classified into dedicated transmission channels and common transmission channels according to whether the channels are shared. Do not The data transfer between the same physical layer (in particular, between the respective physical layers of the transmitter and the receiver) is performed through the physical channel.

Various layers exist in the second layer (L2 layer). For example, the MAC layer maps various logical channels to various transmission channels, and performs logical channel multiplexing for mapping various logical channels to one transmission channel. The MAC layer is connected to a radio link control (RLC) layer serving as an upper layer via a logical channel. Logical channels can be classified into control channels for transmitting control plane information and traffic channels for transmitting user plane information according to the type of transmission information.

The RLC layer of the second layer (L2) performs segmentation and concatenation of the data received from the upper layer, and adjusts the size of the data to be suitable for transmitting the data to the lower layer of the radio interval. In order to guarantee various quality of service (QoS) requested by individual radio bearers (RB), three operation modes are provided, namely, transparent mode (TM), unconfirmed mode (UM) and confirmed mode (AM). In particular, AM RLC uses an automatic repeat and request (ARQ) function to perform a retransmission function in order to implement reliable data transmission.

The Packet Data Aggregation Protocol (PDCP) layer of the second layer (L2) performs header compression to reduce the size of the IP packet header with relatively large and unnecessary control information, so that there is a radio interval with a narrow bandwidth Efficiently transmit IP packets (such as IPv4 or IPv6 packets). Therefore, only the information required by the header part of the data can be transmitted, so that the transmission efficiency of the radio interval can be increased. In addition, in LTE-based systems, the PDCP layer performs security functions including encryption functions to prevent third parties from eavesdropping on data and integrity protection functions to prevent third parties from handling data.

The radio resource control (RRC) layer located at the top of the third layer (L3) is only defined in the control plane, and is responsible for controlling the logic, transmission and transmission of the configuration, reconfiguration, and deassociation of the radio bearer (RB). Physical channel. RB is the logical path provided by the first and second layers (L1 and L2) for data communication between UE and UTRAN. Generally speaking, radio bearer (RB) configuration means that the radio protocol layer and channel characteristics required to provide a specific service are defined and its detailed parameters and operation methods are configured. Radio bearer (RB) is classified into transmission RB (SRB) and data RB (DRB). The SRB is used as a transmission channel for RRC messages in the C plane, and the DRB is used as a transmission channel for user data in the U plane.

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

The downlink physical channel used to transmit the information transferred to the downlink transmission channel to the radio interval between the UE and the network is classified into a physical broadcast channel (PBCH) used to transmit BCH information, and a physical broadcast channel (PBCH) used to transmit MCH information. Physical Multicast Channel (PMCH), Physical Downlink Shared Channel (PDSCH) for transmitting downlink SCH information, and for transmission The physical downlink control channel (PDCCH) (also called DL L1/L2 control channel) of the control information (such as DL/UL scheduling grant information) received from the first and second layers (L1 and L2). At the same time, the uplink physical channel used to transmit the information transferred to the uplink transmission channel to the radio interval between the UE and the network is classified into the physical uplink shared channel used to transmit uplink SCH information (PUSCH), the physical random access channel used to transmit RACH information, and the control information (such as hybrid automatic repeat request (HARQ) ACK or NACK) received from the first and second layers (L1 and L2) The physical uplink control channel (PUCCH) of the scheduling request (SR) and channel quality indicator (CQI) report information).

FIG. 12 depicts an exemplary functional block diagram of an information processing system 1200 capable of implementing the method for identifying victims and intruders according to the subject matter disclosed herein. The information processing system 1200 of FIG. 12 may tangibly embody one or more of any of the exemplary devices, exemplary network elements, and/or functional entities of the network as shown and described herein. In one example, the information processing system 1200 may represent the components of the UE 111 or the eNB 110 and/or the WLAN access point 120, which may have more or less components depending on the hardware specifications of a specific device or network element. In another example, the information processing system can provide M2M type device capabilities. In yet another exemplary embodiment, the information handling system 1200 can provide an uplink transmission power control technique based on the subject matter disclosed herein to 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 or fewer components and/or different component configurations than those shown in FIG. The scope of Zhang's subject matter is not limited to these aspects.

In one or more examples, the information processing system 1200 may include one or more application processors 1210 and baseband processors 1212. The application processor 1210 can be used as a general-purpose processor to execute application programs and various subsystems of the information processing system 1200, and can provide uplink transmissions based on the subject matter disclosed herein to reduce interference experienced by other wireless devices. Power control technology. The application processor 1210 may include a single core or alternatively may include multiple processing cores, wherein one or more of the cores may include a digital signal processor or a digital signal processing core. In addition, the application processor 1210 may include a graphics processor or a co-processor placed on the same chip, or alternatively the 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 be further coupled to an external memory device (such as synchronous dynamic random access memory (SDRAM) 1214) for storing and/or executing applications Programs, such as the ability to provide uplink transmission power control techniques based on the subject matter disclosed herein to reduce interference experienced at other wireless devices. During operation, even when the information processing system 1200 is powered off, the NAND flash memory 1216 is used to store application programs and/or data.

In one example, the list of candidate nodes can be stored in SDRAM 1214 and/or NAND flash memory 1216. In addition, the application processor 1210 can execute computer-readable instructions stored in the SDRAM 1214 and/or NAND flash memory 1216, which can reduce the interference experienced by other wireless devices according to the subject matter disclosed herein. on Uplink transmission power control technology.

In one example, the baseband processor 1212 can control the broadband radio function for the information processing system 1200. The baseband processor 1212 can store program codes for controlling these broadband radio functions in the NOR flash memory 1218. As discussed herein with respect to FIG. 12, the baseband processor 1212 controls a wireless wide area network (WWAN) transceiver 1220 for modulating and/or demodulating broadband network signals, for example, for passing through a 3GPP LTE network Or similar to communicate. The WWAN transceiver 1220 is coupled to one or more power amplifiers 1222 respectively coupled to one or more antennas 1224 for transmitting and receiving radio frequency signals via the WWAN broadband network. The baseband processor 1212 can also control a wireless local area network (WLAN) transceiver 1226. The WLAN transceiver 1226 is coupled to one or more suitable antennas 1228 and can be used via Bluetooth-based standards, IEEE 802.11 standards, Standards based on IEEE 802.16, wireless network standards based on IEEE 802.18, wireless networks based on 3GPP agreements, wireless network standards based on the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE), 3GPP2 Air Interface Evolution (3GPP2 AIE) ) Wireless network standard, based on 3GPP LTE-advanced wireless network, based on UMTS protocol wireless network, based on CDMA2000 protocol wireless network, based on GSM protocol wireless network, based on cellular digital packet data (based on CDPD) protocol wireless network, Mobitex-based protocol wireless network, near field communication (based on NFC) link, WiGig-based network, ZigBee-based network, or the like for communication. It should be noted that these are only exemplary implementations of the application processor 1210 and the baseband processor 1212, and the scope of the claimed subject matter Not limited to these aspects. 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, memory based on phase change, memory based on optical or memory based on bidirectional, and the scope of the claimed subject matter is not limited to this aspect.

In one or more embodiments, the application processor 1210 can drive the display 1230 for displaying various information or data, and can further receive touch input from the user via the touch screen 1232 (for example, via fingers or Stylus). In an exemplary embodiment, the screen 1232 displays to the user menus and/or options that can be selected via a finger and/or stylus for entering information into the information processing system 1200.

The ambient light sensor 1234 can be used to detect the amount of ambient light. For example, the information processing system 1200 operates in ambient light to control the display 1230 according to the intensity of the ambient light detected by the ambient light sensor 1234. Brightness or contrast value. One or more cameras 1236 can be utilized to capture images processed by the application processor 1210 and/or at least temporarily stored in the NAND flash memory 1216. In addition, the application processor can be coupled to a gyroscope 1238, an accelerometer 1240, a magnetometer 1242, an audio codec/decoder (codec) 1244 and/or a global positioning system (GPS) coupled to an appropriate GPS antenna 1248 ) The controller 1246 detects various environmental characteristics, including the position, movement and/or orientation of the information processing system 1200. Alternatively, the controller 1246 may include a global navigation satellite system (GNSS) controller. The audio codec 1244 can be used internally and/or via the audio port 1250 For example, via a headset and microphone jack, it is coupled to an external device of the information processing system and coupled to one or more audio ports 1250 to provide microphone input and speaker output. In addition, the application processor 1210 may be coupled to one or more input/output (I/O) transceivers 1252 to be coupled to one or more I/O ports 1254, such as a universal serial bus (USB) port, High-definition multimedia interface (HDMI) port, serial port, etc. In addition, one or more of the I/O transceivers 1252 can be coupled to one or more memories for optional removable memory (such as a secure digital (SD) card or a subscriber identification module (SIM) card) Body tank 1256, but the scope of the claimed subject matter is not limited to these aspects.

15 depicts an isometric view of an exemplary embodiment of the information processing system of FIG. 12 that may optionally include a touch screen according to one or more embodiments disclosed herein. Figure 11 shows an example implementation of an information processing system 1500 tangibly embodied as a cellular phone, smart phone, smart device, or tablet-type device or the like. The information processing system 1500 can implement the subject matter disclosed herein The method used to identify victims and intruders. In one or more embodiments, the housing 1510 of the information processing system may include controls and commands for receiving tactile input via a user's finger 1516 and/or via a stylus 1518 to control one or more application processors 1210 touch screen 1032 display 1030. The housing 1510 can accommodate one or more components of the information processing system 1000, for example, one or more application processors 1210, SDRAM 1214, NAND flash memory 1216, NOR flash memory 1218, and baseband processor 1212 And/or one or more of WWAN transceivers 1220. The information processing system 1500 may additionally include a physical actuator area 1520, and area 1520 may include a keyboard or button for controlling the information processing system 1000 via one or more buttons or switches. The information processing system 1000 may also include a memory port or slot for receiving non-electrical memory (such as flash memory, for example in the form of a secure digital (SD) card or a subscriber identification module (SIM) card) 1056. Optionally, the information processing system 1000 may further include one or more speakers and/or microphones 1524 and a connection port 1554 for connecting the information processing system 1500 to another electronic device, docking station, display, battery charger, etc. In addition, the information handling system 1500 may include a headset or speaker jack 1528 and one or more cameras 1536 on one or more sides of the housing 1510. It should be noted that, compared to what is shown, the information processing system 1500 of FIG. 15 may include more or less components in various configurations, and the scope of the claimed subject matter is not limited in this respect.

As used herein, the term "circuit system" can refer to, belong to, or include application-specific integrated circuits (ASIC), electronic circuits, processors (shared, dedicated, or group), and/or execute one or more software or Firmware program memory (shared, dedicated or group), combinational logic circuit, and/or other hardware components that provide the described functionality. In some embodiments, the circuit system can be implemented by one or more software or firmware modules, or the functions associated with the circuit system can be implemented by one or more software or firmware modules. In some embodiments, the circuit system may include logic at least partially operable by hardware.

The embodiments described herein can be implemented as a system using any appropriately configured hardware and/or software. For one embodiment, FIG. 14 illustrates example components of a user equipment (UE) device 1400. In some real In an embodiment, the UE device 1400 may include an application circuit system 1402, a baseband circuit system 1404, a radio frequency (RF) circuit system 1406, a front-end module (FEM) circuit system 1408, and one or more antennas 1410. These components are at least Coupled together as shown.

The application circuitry 1402 may include one or more application processors. For example, the application circuitry 1402 may include circuitry such as (but not limited to) one or more single-core or multi-core processors. The processor may include any combination of a general-purpose processor and a special-purpose processor (for example, a graphics processor, an application processor, etc.). The processor may be coupled to the memory/storage 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 Execute on the system.

The baseband circuitry 1404 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1404 may include one or more baseband processors and/or control logic to process the baseband signals received from the receive signal path of the RF circuitry 1406 and generate a transmission signal path for the RF circuitry 1406 The fundamental frequency signal. The baseband processing circuitry 1404 can interface with the application circuitry 1402 for generating and processing baseband signals and for controlling the operation of the RF circuitry 1406. For example, in some embodiments, the baseband circuitry 1404 may include a second-generation (2G) baseband processor 1404a, a third-generation (3G) baseband processor 1404b, and a fourth-generation (4G) baseband processor. The processor 1404c and/or other baseband processors 1404d of other existing generations, under development or future generations to be developed (for example, fifth generation (5G), 6G, etc.). The baseband circuitry 1404 (for example, one or more of the baseband processors 1404a to 1404d) can be processed to communicate with one or more radio networks via the RF circuitry 1406 Various radio control functions. Radio control functions may include (but are not limited to) signal modulation/demodulation, encoding/decoding, radio frequency shifting, and so on. In some embodiments, the modulation/demodulation circuitry of the baseband circuitry 1404 may include fast Fourier transform (FFT), precoding, and/or cluster mapping/demapping functionality. In some embodiments, the encoding/decoding circuitry of the baseband circuitry 1404 may include convolution, tail-biting convolution, turbo code, Viterbi, and/or low density parity checking (LDPC) encoder/decoder functionality. The embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples, and other suitable functionality may be included in other embodiments.

In some embodiments, the baseband circuitry 1404 may include elements of protocol stacking, for example, such as elements of the Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocol including the following: physical (PHY), media Access control (MAC), radio link control (RLC), packet data aggregation protocol (PDCP) and/or radio resource control (RRC) elements. The central processing unit (CPU) 1404e of the baseband circuit system 1404 can be configured to execute the elements of protocol stacking for signaling PHY, MAC, RLC, PDCP, and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processors (DSP) 1404f. The audio DSP 1404f may include components for compression/decompression and echo cancellation, and may include other suitable processing components in other embodiments. The components of the baseband circuit system can be suitably combined in a single chip, a single chip group, or in some embodiments are placed on the same circuit board. In some embodiments, some or all of the constituent components of the baseband circuitry 1404 and the application circuitry 1402 may be implemented together, such as on a system-on-chip (SOC).

In some embodiments, the baseband circuitry 1404 can provide communications compatible with one or more radio technologies. For example, in some In an embodiment, the baseband circuit system 1404 can support and Evolve Universal Terrestrial Radio Access Network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), wireless local area networks (WLAN), and wireless personal area networks (WPAN) communications. The embodiment in which the baseband circuitry 1404 is configured to support radio communications of more than one wireless protocol can be referred to as a multi-mode baseband circuitry.

The RF circuit system 1406 can use modulated electromagnetic radiation to communicate with the wireless network via non-solid media. In various embodiments, the RF circuitry 1406 may include switches, filters, amplifiers, etc. to facilitate communication with wireless networks. The RF circuitry 1406 may include a receiving signal path, and the receiving signal path may include circuitry to down-convert the RF signal received from the FEM circuitry 1408 and provide the baseband signal to the baseband circuitry 1404. The RF circuit system 1406 may also include a transmission signal path, and the transmission signal path may include a circuit system to up-convert the base frequency signal provided by the base frequency circuit system 1404 and provide the RF output signal to the FEM circuit system 1408 for transmission.

In some embodiments, the RF circuitry 1406 may include a receiving signal path and a transmission signal path. The receiving signal path of the RF circuit system 1406 may include a mixer circuit system 1406a, an amplifier circuit system 1406b, and a filter circuit system 1406c. The transmission signal path of the RF circuit system 1406 may include a filter circuit system 1406c and a mixer circuit system 1406a. The RF circuitry 1406 may also include a synthesizer circuitry 1406d for synthesizing frequencies for use by the mixer circuitry 1406a of the receiving signal path and the transmission signal path. In some embodiments, the mixer circuit system 1406a of the receive signal path can be configured to down-convert the received signal from the FEM circuit system based on the synthesized frequency provided by the synthesizer circuit system 1406d. System 1408 RF signal. The amplifier circuit system 1406b can be configured to amplify the down-converted signal, and the filter circuit system 1406c can be a low-pass filter configured to remove undesired signals from the down-converted signal to generate an output baseband signal Filter (LPF) or Band Pass Filter (BPF). The output baseband signal can be provided to the baseband circuitry 1404 for further processing. In some embodiments, the output fundamental frequency signal may be a zero frequency fundamental frequency signal, but this is not a requirement. In some embodiments, the mixer circuit system 1406a of the receive signal path may include a passive mixer, but the scope of the embodiment is not limited to this aspect.

In some embodiments, the mixer circuit system 1406a of the transmission signal path can be configured to up-convert the input fundamental frequency signal based on the synthesized frequency provided by the synthesizer circuit system 1406d to generate the FEM circuit system 1408 The RF output signal. The baseband signal can be provided by the baseband circuitry 1404 and can be filtered by the filter circuitry 1406c. The filter circuit system 1406c may include a low-pass filter (LPF), but the scope of the embodiment is not limited to this aspect.

In some embodiments, the mixer circuitry 1406a of the receive signal path and the mixer circuitry 1406a of the transmission signal path may include two or more mixers, and may be configured for four-phase Down conversion and/or up conversion. In some embodiments, the mixer circuitry 1406a of the receive signal path and the mixer circuitry 1406a of the transmission signal path may include two or more mixers, and may be configured for image suppression ( For example, Hartley image suppression). In some embodiments, the mixer circuitry 1406a and the mixer circuitry 1406a of the receive signal path can be configured for direct down conversion and/or direct up conversion, respectively. In some embodiments, the mixer circuit of the receive signal path is The system 1406a and the mixer circuit system 1406a of the transmission signal path can be configured for superheterodyne operation.

In some embodiments, the output fundamental frequency signal and the input fundamental frequency signal may be analog fundamental frequency signals, but the scope of the embodiment is not limited to this aspect. In some alternative embodiments, the output fundamental frequency signal and the input fundamental frequency signal may be digital fundamental frequency signals. In these alternative embodiments, the RF circuit system 1406 may include an analog/digital converter (ADC) and a digital/analog converter (DAC) circuit system, and the base frequency circuit system 1404 may include a digital base frequency interface to communicate with the RF circuit System 1406 communication.

In some dual-mode embodiments, a separate radio IC circuit system may be provided for processing signals of each spectrum, but the scope of the embodiment is not limited to this aspect.

In some embodiments, the synthesizer circuit system 1406d can be a fractional N synthesizer or a fractional N/N+1 synthesizer, but the scope of the embodiment is not limited to this aspect, because other types of frequency synthesizers can be suitable. For example, the synthesizer circuit system 1406d can be a delta-delta synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

The synthesizer circuit system 1406d can be configured to synthesize the output frequency based on the frequency input and the frequency divider control input for use by the mixer circuit system 1406a of the RF circuit system 1406. In some embodiments, the synthesizer circuitry 1406d is a fractional N/N+1 synthesizer.

In some embodiments, the frequency input can be provided by a voltage controlled oscillator (VCO), but this is not a requirement. The frequency divider control input can be provided by the baseband circuit system 1404 or the application processor 1402, depending on the desired output frequency. In some embodiments, the divider control input (for example, N) may be determined based on the channel self-lookup table indicated by the application processor 1402.

The synthesizer circuit system 1406d of the RF circuit system 1406 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured (for example, based on a carry output) to divide the input signal by N or N+1 to provide a frequency 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 elements can be configured to break the VCO period into Nd equal-phase packets, 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.

In some embodiments, the synthesizer circuit system 1406d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (for example, twice the carrier frequency, four Times the carrier frequency) and used in conjunction with a quadrature generator and frequency divider circuit system to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuitry 1406 may include an IQ/polarity converter.

The FEM circuit system 1408 may include a receiving signal path, and the receiving signal path may include a circuit system configured to perform the following operations: operate on RF signals received from one or more antennas 1410, amplify the received signals, and provide the received signals The amplified version is sent to the RF circuit system 1406 for further processing. The FEM circuit system 1408 may also include a transmission signal path. The transmission signal path may include a signal configured to amplify the signal provided by the RF circuit system 1406 for transmission for one or more antennas 1410. One or more transmission circuits.

In some embodiments, FEM circuitry 1408 may include a TX/RX switch to switch between transmission mode operation and reception mode operation. The FEM circuit system may include a receiving signal path and a transmission signal path. The receive signal path of the FEM circuit system may include a low noise amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (for example, to the RF circuit system 1406). The transmission signal path of FEM circuit system 1408 may include a power amplifier (PA) to amplify (for example, provided by RF circuit system 1406) input RF signal, and one or more filters to generate RF signal for subsequent transmission ( For example, by one or more of one or more antennas 1410).

In some embodiments, the UE device 1400 may include additional components, such as memory/storage, display, camera, sensor, and/or input/output (I/O) interface, for example.

The following is about another example.

Example 1 is a device of a network entity that can manage a packet data network (PDN) connection of a user equipment (UE). The network entity includes a processing circuit system to: determine that the UE is first free PDN gateway (P-GW) manages a first PDN connection to switch to a second PDN connection; selects a second P-GW to manage the second PDN connection; generates at least one of the second PDN connections Configuration data of a network node; and generating configuration data for an evolved NodeB (eNB) in the second PDN connection.

In Example 2, the subject matter of Example 1 may further include a transmission circuit system to use at least one of an access layer message or a non-access layer message to transmit an invitation to use the second PDN connection to the UE.

In Example 3, the subject matter of any one of Examples 1 to 2 may include a processing circuit system configured to determine that the UE has moved from a first position adjacent to the first P-GW To a second location adjacent to the second P-GW.

In Example 4, the subject matter of any one of Examples 3 to 4 may include a transmission circuit system configured to provide the second P-GW with the at least one used in the second PDN connection The transmission address of a tunnel endpoint of a network node.

In Example 5, the subject matter of any one of Examples 1 to 4 may include a processing circuit system, which is configured to allocate a new Internet Protocol (IP) address or IP for the second PDN connection At least one of the prefixes.

In Example 6, the subject matter of any one of Examples 1 to 5 may include a processing circuit system configured to provide at least one network node in the second PDN connection for the eNB A tunnel endpoint transmission address.

In Example 7, the subject matter of any one of Examples 1 to 6 may include a processing circuit system configured to provide the eNB with the at least one network node used in the second PDN connection The at least one of a tunnel endpoint transmission address and a new IP address or IP prefix for the UE.

In Example 8, the subject matter of any one of Examples 1 to 7 may include a transmission circuit system that is configured to advertise a router containing at least a portion of the new IP header for the UE (RA) The message is sent to the UE.

In Example 9, the subject matter of any one of Examples 1 to 8 The thing may include a configuration in which the second PDN connection is established before the first PDN connection is terminated.

Example 10 is a device of an evolved NodeB (eNB) that can manage a packet data network (PDN) connection of a user equipment (UE). The eNB includes a processing circuit system to: determine a part of the data traffic A first packet data gateway (P-GW) manages a first PDN connection to switch to a second PDN connection; and selects a second P-GW to manage the second PDN connection.

In Example 11, the subject matter of Example 10 may further include a transmission circuit system to forward at least a part of an Internet Protocol (IP) address and a set of routing rules to the second PDN. Connect a network entity associated with a control plane; transmit the at least part of an IP address and routing rules of an IP address of the second PDN connection to the UE; and use an access layer messaging or a non-access layer At least one of the messages transmits to the UE an invitation to use the second PDN connection for the selected data traffic determined by the set of routing rules.

In Example 12, the subject matter of any of Examples 10 to 11 may include a configuration in which the processing circuitry is configured to allocate a new IP address or IP prefix for the second PDN connection.

In Example 13, the subject matter of any one of Examples 10 to 12 may include a configuration in which the processing circuitry is configured to send a router advertisement containing at least a portion of the new IP header for the UE (RA) Message.

In Example 14, the subject matter of any one of Examples 10 to 13 may include a configuration in which the second PDN connection is established before the first PDN connection is terminated.

In Example 15, the subject matter of any one of Examples 10 to 14 may include a configuration in which the second PDN connection provides access to a mobile edge computing server located adjacent to the eNB.

In Example 16, the subject matter of any one of Examples 10 to 15 may include a configuration in which the set of routing rules for the second PDN connection includes an IP of the UE associated with a traffic selection filter The address prioritization list includes one or more IP header fields and/or a list of full domain names and/or a list of application identifiers.

Example 17 is a device of a network access point, the network access point includes a processing circuit system to: receive a request from an evolved NodeB (eNB), the request using a first packet data network gateway (P-GW) to manage a first packet data network (PDN) connection with a user equipment (UE) to use a second P-GW located near the network access point to establish Connecting to a second PDN of the UE; and in response to the request, assign an Internet Protocol (IP) address or IP prefix to the second P-GW located adjacent to the network access point .

In Example 18, the subject matter of Example 17 may include a transmission circuit system that forwards the IP address of the P-GW located adjacent to the network access point to the eNB for further Forward to a network entity associated with a control plane of the second PDN connection; and transmit to the UE an invitation to use the second PDN connection as part of the data traffic for the UE.

In Example 19, the subject matter of any one of Examples 17 to 18 may include a configuration in which the transmission circuit system is configured to inform the eNB that the network access point is communicatively coupled to the eNB via X2 transmission. The second P-GW.

In Example 20, the subject matter of any one of Examples 17 to 19 may include a configuration in which the P-GW is co-located with the network access point.

In Example 21, the subject matter of any one of Examples 17 to 20 may include a configuration in which the second network access point includes an enhancer cell located in a service area covered by the eNB.

In Example 22, the subject matter of any of Examples 17 to 21 may include transmission circuitry configured to send a router advertisement containing at least a portion of the new IP header for the UE (RA) Message.

In Example 23, the subject matter of any one of Examples 17 to 22 may include a configuration in which the second PDN connection is established before the first PDN connection is terminated.

Example 24 is a device of an evolved NodeB (eNB) that can manage a packet data network (PDN) connection of a user equipment (UE). The eNB includes a processing circuit system to: determine that the UE is free to communicate A first PDN connection managed by a first packet data gateway (P-GW) of the eNB is switched to a second P-GW that is communicatively coupled to a network access point A second PDN connection managed; and receiving from the network access point an Internet Protocol (IP) address or IP prefix of the second P-GW located adjacent to the network access point At least one of them.

In Example 25, the subject matter of Example 24 may include a transmission circuit system that is configured to: forward the at least one of an IP address or IP header of the second P-GW to and The second PDN is connected to a network entity associated with a control plane; the second PDN is connected to the at least one of an IP address or IP prefix and the path selection rule Send to the UE; and use at least one of an access layer message or a non-access layer message to transmit to the UE an invitation to use the second PDN connection.

In Example 26, the subject matter of any one of Examples 24 to 25 may include a processing circuit system configured to detect that the UE has entered a coverage area of the network access point.

In Example 27, the subject matter of any one of Examples 24 to 26 may include a configuration in which the second PDN connection is established before the first PDN connection is terminated.

In various examples, the operations discussed in this article can be implemented as hardware (for example, circuit systems), software, firmware, microcode, or a combination thereof, which can be provided by computer program products. For example, It includes a tangible (for example, non-transitory) machine-readable or computer-readable medium on which instructions (or software programs) used to program a computer to execute the procedures discussed in this article are stored. In addition, the term "logic" can include software, hardware, or a combination of software and hardware by way of example. Machine-readable media may include storage devices, such as the storage devices discussed herein.

Reference in the specification to "an example" or "an example" means that a particular feature, structure, or characteristic described in combination with the example can be included in at least one implementation. The appearance of the phrase "in one instance" in various places in this specification may or may not all refer to the same instance.

In addition, in the description and the scope of patent application, the terms "coupled" and "connected" and their derivatives can be used. In some instances, "connected" may be used to indicate that two or more elements are in direct physical or electrical contact with each other. "Coupling" can mean that two or more components are in direct physical or electrical contact. However, “coupled” can also mean that two or more components may not directly contact each other, but can still cooperate or interact with each other.

Therefore, although the examples have been described in language specific to structural features and/or method actions, it should be understood that the claimed subject matter may not be limited to the specific features or actions described. The fact is that the specific features and actions are revealed as a sample form of implementing the claimed subject matter.

100‧‧‧3GPP LTE network

101‧‧‧Core Network (CN)

102‧‧‧Air interface access network E UTRAN

103‧‧‧Serving GPRS Support Node

104‧‧‧Mobile management entity

105‧‧‧Home User Server (HSS)

106‧‧‧Service Gate (SGW)

107‧‧‧Packet Data Network (PDN) Gateway

108‧‧‧Policy and Charging Rules Function (PCRF) Manager

110‧‧‧Evolved NodeB (eNB)

111‧‧‧User Equipment (UE)

S1, S3, S4, S5‧‧‧interface

Claims (24)

A network entity capable of managing a packet data network (PDN) connection for a user equipment (UE). The network entity includes a processing circuit system for determining whether the UE is removed from a first PDN gate. Switch the first PDN connection managed by the P-GW to a second PDN connection; select a second P-GW to manage the second PDN connection; connect the second PDN to an Internet protocol ( IP) at least a part of the address and a set of path selection rules are forwarded to a network entity associated with a control plane of the second PDN connection; the second PDN is connected to the at least part and path of an IP address The selection rule is transmitted to the UE; and at least one of an access layer transmission or a non-access layer transmission is used to transmit to the UE for the selected data traffic determined by the set of path selection rules using the second An invitation for PDN connection. Such as the network entity of claim 1, which further includes a transmission circuit system for using at least one of an access layer communication or a non-access layer communication to transmit an invitation to the UE to use the second PDN connection. Such as the network entity of claim 1, wherein the processing circuit system is configured to: determine that the UE has moved from a first position adjacent to the first P-GW to one adjacent to the second P-GW The second position. Such as the network entity of claim 3, wherein the transmission circuit system is configured to: provide the second P-GW with a tunnel endpoint transmission bit for the at least one network node in the second PDN connection site. For example, the network entity of claim 4, wherein the processing circuit system is configured to: allocate at least one of a new Internet Protocol (IP) address or a new IP prefix for the second PDN connection. Such as the network entity of claim 1, wherein the processing circuit system is configured to: At least one network node in the second PDN connection is provided with a tunnel endpoint transmission address for the eNB. Such as the network entity of claim 1, wherein the processing circuit system is configured to: provide the eNB with a tunnel endpoint transmission address for the at least one network node in the second PDN connection and for The at least one of a new IP address or a new IP prefix of the UE. Such as the network entity of claim 7, wherein the transmission circuit system is configured to: send a router advertisement (RA) message containing at least a part of the new IP prefix for the UE to the UE. Such as the network entity of claim 1, wherein the second PDN connection is established before the first PDN connection is terminated. An evolved NodeB (eNB) equipment capable of managing a packet data network (PDN) connection for a user equipment (UE). The eNB includes a processing circuit system for determining whether to transfer data from the UE. Part of the service is switched from a first PDN connection managed by a first packet data network gateway (P-GW) to a second PDN connection; select a second P-GW to manage the second PDN connection ; Forward at least a part of an Internet Protocol (IP) address of the second PDN connection and a set of path selection rules to a network entity associated with a control plane of the second PDN connection; The at least a part of the IP address and the path selection rule of one of the two PDN connections are transmitted to the UE; and at least one of an access layer transmission or a non-access layer transmission is used to transmit to the UE through the set of paths The selected data traffic determined by the selection rule uses an invitation for the second PDN connection. Such as the device of claim 10, wherein the processing circuit system is configured to: allocate a new IP address or a new IP prefix for the second PDN connection. Such as the device of claim 10, wherein the processing circuit system is configured to: send a data containing at least a part of the new IP prefix for the UE Router Advertisement (RA) message. Such as the device of claim 10, wherein the second PDN connection is established before the first PDN connection is terminated. Such as the device of claim 10, wherein the second PDN connection provides access to a mobile edge computing server located adjacent to the eNB. For example, the device of claim 10, wherein the set of routing rules for the second PDN connection includes a prioritized list of IP addresses of the UE associated with a traffic selection filter, the list including one or more IP labels A list of header fields and/or full domain names and/or a list of application identifiers. A device for a network access point, the network access point includes a processing circuit system for: receiving a request from an evolved NodeB (eNB) to use one located adjacent to the network access point The second P-GW establishes a second PDN connection with a user equipment (UE), and the request uses a first packet data gateway (P-GW) to manage a first packet data with the UE Network (PDN) connection; in response to the request, assign an Internet Protocol (IP) address or a new IP prefix to the second P-GW located adjacent to the network access point; The IP address of the P-GW located adjacent to the network access point is forwarded to the eNB for further forwarding to a network entity associated with a control plane of the second PDN connection; and The UE transmits an invitation to use the second PDN connection for a part of the data traffic of the UE. Such as the equipment of claim 16, wherein the transmission circuit system is configured to: communicate the network access point to the second P-GW via X2 messaging to inform the eNB. Such as the device of claim 16, wherein the second P-GW and the network access point are co-located. Such as the device of claim 16, wherein the network access point includes an enhancer cell located in a service area covered by the eNB. Such as the device of claim 16, wherein the transmission circuit system is configured to: send a router advertisement (RA) message containing at least a part of the new IP prefix for the UE. Such as the device of claim 16, wherein the second PDN connection is established before the first PDN connection is terminated. An evolved NodeB (eNB) equipment that can manage a packet data network (PDN) connection for a user equipment (UE). The eNB includes a processing circuit system for determining whether the UE is to communicate from a router A first PDN connection managed by a first packet data gateway (P-GW) of the eNB is switched to a second P- which is communicatively coupled to a network access point A second PDN connection managed by the GW; receiving an Internet Protocol (IP) address or IP prefix of the second P-GW located adjacent to the network access point from the network access point At least one of them forwards the at least one of an IP address or IP prefix of the second P-GW to a network entity associated with a control plane of the second PDN connection; Two PDN connections: forward the at least one of an IP address or IP prefix and routing rules to the UE; and use at least one of an access layer communication or a non-access layer communication to transmit to the UE Use one of the second PDN connections to invite. Such as the equipment of claim 22, wherein the processing circuit system is configured to detect that the UE has entered a coverage area of the network access point. Such as the device of claim 22, wherein the second PDN connection is established before the first PDN connection is terminated.

Images