TW201724827A - Providing different Radio Access Networks independent, standardized access to a Core Network - Google Patents

Abstract

A network device may enable a non-3GPP Radio Access Network (RAN) to communicate with a 3GPP Core Network (CN) via the same type of interface that 3GPP RANs use to communicate with the CN. The network device may function as an intermediary with respect to communications between the non-3GPP RAN and the CN. The network device may convert messages, originating from a UE connected to the non-3GPP RAN and carrying information intended for the CN, from a non-3GPP RAN protocol to a 3GPP RAN protocol. The network device may convert messages, originating from the CN and carrying information intended for a UE connected to the non-3GPP RAN, from the 3GPP RAN protocol to the non-3GPP RAN protocol. The network device may provide support services to User Equipment (UE) of the non-3GPP RAN, such as user plane bearer information, Quality of Service (QoS), etc.

Description

Technology for providing independent, standardized access to different core access networks to the core network

The present invention is directed to techniques for providing independent, standardized access to different radio access networks to a core network.

A wireless telecommunications network typically includes a core network (CN) coupled to a plurality of radio access networks (RANs) that enable user equipment (UE) such as smart phones, tablets, laptops, etc. CN. An example of a wireless telecommunications network may include an evolved packet system (EPS) that operates based on the Third Generation Partnership Project (3GPP) communication standard.

An EPS may include an evolved packet core (EPC) network that is coupled to one or more 3GPP RANs (eg, Long Term Evolution (LTE) RAN (also known as the Evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E) - UTRAN), fifth generation (5G) RAN, etc. The LTE networks may each include a RAN having one or more base stations, some or all of which may be in the form of an enhanced Node B (eNB). The LTE network communicates with the EPC network.

Efforts currently being made to further develop wireless telecommunications networks include enabling the UE to connect to the CN (e.g., EPC) regardless of the type of RAN used by the user device. For example, efforts have been made to establish an infrastructure that enables UEs to connect to EPC over a 3GPP RAN or Wi-Fi network. For example, LTE Wireless Local Area Network (WLAN) aggregation (or LWA) and LTE-WLAN Integrated Internet Protocol Secure Tunnel (LWIP) have been proposed to enable the UE to connect to the EPC. However, LWA and LWIP require the LTE network to operate as an umbrella network in order to arrange (through the Radio Resource Control (RRC) connection between the UE and the LTE network) the UE is connected to the CN via the Wi-Fi network.

In another example, a Wi-Fi router can communicate with a Universal Access Network (GAN) architecture to connect to the CN. The GAN architecture may include a controller device (commonly known as the GAN Controller (GANC)), which does not require an LTE umbrella network like LWA and LWIP; however, the GAN architecture introduces a new RAN to CN including a secure tunnel between the GANC and the EPC Interface (called "Wm interface"). Thus, since the LTE network communicates with the CN (eg, EPC) through the S1 interface, the implementation of the GANC requires the CN to use different interfaces/protocols to communicate with different UR/RANs.

According to an embodiment of the present invention, an apparatus for an application processor of a network device is specifically provided, comprising circuitry for implementing a non-third generation partnership project (3GPP) radio access network ( RAN) protocol for communicating with a User Equipment (UE) connected to a non-3GPP RAN; implementing a 3GPP RAN protocol for communicating with a 3GPP Core Network (CN); and by means of the following steps, RAN, for the CN interface, relaying information between the UE and the 3GPP CN: converting a message originating from the UE and carrying information intended for the 3GPP CN from the non-3GPP RAN protocol to the 3GPP RAN protocol; A message originating from the 3GPP CN and carrying information intended for the UE is converted from the 3GPP RAN protocol to the non-3GPP RAN protocol.

The detailed description in the following section refers to the attached drawings. The same element symbols in different figures may identify the same or similar elements. It is understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the disclosure. Therefore, the following detailed description is not to be taken in a limiting

The techniques described herein can be used to enable the core network (CN) of a wireless telecommunications network to communicate with different types of Radio Access Network (RAN) using the same type of interface. For example, a wireless telecommunications network may include a RAN implementing a 3GPP wireless communication standard to communicate with a core network, such as an Evolved Packet Core (EPC). Examples of RANs implementing 3GPP wireless communication standards may include 3GPP RANs (e.g., Long Term Evolution (LTE) RAN, Fifth Generation (5G) RAN, etc.). According to the 3GPP wireless communication standard, the 3GPP RAN can communicate with the core network using an interface called the S1 interface.

Implementing the techniques described herein may enable a wireless telecommunications network to communicate with other types of RANs (i.e., RANs that do not implement the 3GPP communication standard) using the same type of interface (e.g., S1 interface). A RAN that does not implement the 3GPP communication standard may be referred to herein as a "non-3GPP RAN," examples of which may include a wireless local area network implementing the American Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication standard (also known as Wi-Fi) ( WLAN). In order for the non-3GPP RAN to communicate with the core network using the same interface as the 3GPP RAN, the non-3GPP RAN may include a network device (referred to herein as a "non-3GPP access spectrum device" or "N3AS device").

The N3AS device is operable as a communication intermediary between a user equipment (UE) within the non-3GPP RAN and the core network. For example, an N3AS device may implement a new protocol (referred to herein as a Non-3GPP Access Layer (N3AS) protocol) that may enable the UE and CN to use the same interface (eg, S1 interface) that the CN uses to communicate with the 3GPP RAN. Communicate with each other. For example, the N3AS protocol may cause the UE to encapsulate NAS messages inside protocols (eg, 802.11 communication standards) implemented by non-3GPP RANs. The NAS message can be sent to the N3AS device, and the N3AS device can convert the message to a protocol implemented by the CN (e.g., 3GPP communication standard) before transmitting the message to the CN. Similarly, the N3AS device can receive messages (eg, NAS messages) from the CN and can convert the messages to protocols implemented by non-3GPP RANs (eg, 802.11 communication standards) before transmitting the messages to the UE. As such, the N3AS device can operate as an intermediary device to enable UEs within the non-3GPP RAN to communicate with the CN using the same protocol/interface that the 3GPP RAN will use to communicate with the CN.

As described herein, "non-3GPP" may refer to a communication standard (eg, an IEEE communication standard) that is different from the communication standard implemented by the CN. In some embodiments, "non-3GPP" may include communication standards based on non-cellular networks. In addition, 3GPP may refer to communication standards implemented by the CN (eg, third generation (3G) communication standard, fourth generation (4G) communication standard, fifth generation (5G) communication standard, etc.). In several embodiments, "3G)) may include communication standards based on cellular networks.

1 is a schematic diagram of an example of an environment 100 in which the systems and/or methods described herein may be implemented. Environment 100 can include UEs 110 that are linked to a wireless telecommunications network with different RANs.

For example, a wireless telecommunications network may include a core network (CN) that is coupled to a 3GPP RAN (eg, LTE RAN, 5G RAN, etc.) or a non-3GPP RAN (eg, Wi-Fi WLAN). The core network (CN) may include an evolved packet core (EPC) operating based on the 3GPP communication standard. However, it is to be understood that the core network may include another type of core network that can provide wireless telecommunication services to the UE 110. The CN can include a control plane cloud and a user plane cloud. Examples of devices that can be used to implement a planar cloud and a user plane cloud are discussed below with respect to FIG. 2. To implement a planar cloud and/or a user plane cloud, one or more of the devices depicted in FIG. 2 may implement specific communication standards, such as 3GPP communication standards (as may be obtained from the date of this application and/or subsequent development and implementation). By).

The 3GPP RAN may be or may include one or more base stations (some or all of which may be eNB 120) through which UE 110 may communicate with the CN. The non-3GPP RAN may include a non-3GPP access device 130 and/or a non-3GPP access layer (N3AS) device 140 through which the UE 110 may communicate with the core network. Although the LTE RAN is described as a RAN implementing a 3GPP communication standard and a non-3GPP RAN is described as a RAN implementing a Wi-Fi communication standard (eg, IEEE 802.11 communication standard), it is to be understood that the techniques described herein may be applied to different communication standards ( Includes future developments in 3GPP communication standards and/or versions of Wi-Fi communication standards).

The UE 110 may include portable computing and communication devices such as a personal digital assistant (PDA), a smart phone, a cell phone, a laptop attached to a wireless telecommunications network, a tablet, and the like. The UE 110 may also include a non-portable computing device, such as a desktop computer, a consumer or commercial appliance, or other device capable of connecting to a RAN of a wireless telecommunications network (eg, LTE RAN and/or non-3GPP RAN). . The UE 110 may also include computing and communication devices (also known as wearable devices) that may be worn by the user, such as watches, fitness bands, necklaces, glasses, monolithic lenses, rings, belts, headphones, or other types of wearable devices. .

UE 110 may include software, firmware, or hardware that enables UE 110 to perform one or more of the operations described herein. For example, in addition to using a known 3GPP request and/or response message to connect to the core network via the LTE RAN, the UE 110 can connect to the EPC through the non-3GPP RAN. For example, the UE 110 can communicate with the N3AS device 140, which connects to the non-3GPP RAN using a typical request and response message consistent with a non-3GPP RAN communication protocol (eg, IEEE 802.11 message); however, the request and response message can have The request and response messages that are consistent with the CN are encapsulated in it.

The eNB 120 may include one or more network devices that receive, process, and/or transmit traffic destined for and/or received by the UE 110 through the null plane. The eNB 120 can be coupled to a network device, such as a web site router, as an intermediary for communicating information between the eNB 120 and the core network.

The non-3GPP access device 130 can include one or more network devices that receive, process, and/or transmit traffic destined for and/or received from the UE 110 (e.g., through an empty interfacing plane). The non-3GPP access device 130 can include a network device, such as a gateway, router, etc., that can implement policies and techniques for communicating information between the UE 110 and the N3AS device 140, which can provide the UE 110 with an access EPC. In one example, the non-3GPP access device 130 can include a wireless router that implements the IEEE 802.11 communication standard.

The N3AS device 140 may include one or more network devices, such as gateways, routers, etc., operable to communicate with the core network between non-3GPP RAN devices (eg, UE 110 and non-3GPP access device 130) The intermediary of information. In some embodiments, the N3AS device 140 can receive messages from the non-3GPP access device 130 that are consistent with non-3GPP RAN communication protocols (eg, IEEE 802.11 communication standards), but include communication protocols with the CN (eg, The 3GPP communication standard) is consistent with the message enclosed. The N3AS device 140 can convert the messages from a non-3GPP RAN protocol to a protocol implemented by the CN (e.g., 3GPP communication standard), and can communicate the messages to the CN using the same protocol/interface as the LTE RAN.

Similarly, the N3AS device 140 can receive messages from the CN intended to be sent to the UE 110 of the non-3GPP RAN. Such messages may be consistent with the CN's communication protocol (eg, 3GPP communication standard). The N3AS device 140 can convert the messages into protocols implemented by the non-3GPP RAN and send messages to the UE. As described in detail later, the N3AS device 140 converts the message from the CN by encapsulating the message (or its content) within a message consistent with the protocol enforced by the non-3GPP RAN.

The number of devices and/or networks illustrated in Figure 1 is for illustrative purposes only. In fact, there may be additional devices and/or networks compared to the ones illustrated in Figure 1; fewer devices and/or networks; different devices and/or networks; or differently arranged devices and/or networks. Additionally or alternatively, one or more of such devices of system 100 can perform one or more functions as performed by one or more of such devices of system 100. Again, although "direct" links are shown in Figure 1, these links must be interpreted as logical communication paths, and in fact, there may be one or more intermediaries (eg, routers, gateways, modems) , exchangers, hubs, etc.).

Figure 2 is a schematic diagram of a CN example. The apparatus depicted in FIG. 2 may be an example of a device used to implement the control plane cloud and user plane cloud discussed above with respect to FIG. The apparatus of Figure 2 can operate in a manner consistent with protocols implemented by the CN, such as the 3GPP communication protocol.

As shown, the CN can include an EPC that includes a service gateway (SGW) 210, a PDN gateway (PGW) 220, an mobility management entity (MME) 230, a home subscriber server (HSS) 240, and/or Policy and Charging Rules Function (PCRF) 250. The CN can be linked to RANs, such as LTE RAN and non-3GPP RAN, and external networks such as Public Land Mobile Network (PLMN), Public Switched Telephone Network (PSTN), and/or Internet Protocol (IP) networks. (for example, the Internet).

The SGW 210 can aggregate traffic received from one or more eNBs 120 and can send aggregated traffic to the external network or device via the PGW 220. In addition, SGW 210 can aggregate traffic received from one or more PGWs 220 and can send aggregated traffic to one or more eNBs 120. The SGW 210 is operable as an anchor for the user plane during handover between eNBs, and as an anchor for inter-telecommunication mobility between different telecommunication networks.

The MME 230 may include other devices that serve as one or more of the control nodes of the eNB 120 and/or provide an air interface to the wireless telecommunications network. For example, MME 230 can operate to register UE 110 in a wireless telecommunications network to establish bearer channels (e.g., traffic flows) associated with the connection phase of UE 110 to hand over UE 110 to a different eNB. , MME, or other network, and/or other traffic policing operations. The MME 230 may regulate the traffic transmitted to and/or received from the UE 110.

PGW 220 may include one or more network devices that may aggregate traffic received from one or more SGWs 210 and may send aggregated traffic to an external network. The PGW 220 may also or additionally receive traffic from the external network and may transmit the traffic (via the SGW 140 and/or the eNB 120) towards the UE 110. The PGW 220 may be responsible for providing billing information for each communication connection phase to the PCRF 250 to assist in ensuring that the charging policy is properly applied to the communication connection phase with the wireless telecommunications network.

The HSS 240 may include one or more devices that may manage, update, and/or store profile information associated with a user (eg, a user associated with the UE 110) in memory associated with the HSS 240. Profile information identifies approved and/or user-accessible applications and/or services; mobile phone number (MDN) associated with the user; bandwidth or data rate threshold associated with the application and/or service Value; and/or other information. A user can be associated with the UE 110. Additionally or alternatively, the HSS 240 can perform authentication, authorization, and/or accounting operations associated with the user and/or communication with the UE 110.

The PCRF 250 may receive information about policies and/or subscriptions from one or more sources, such as a user database, and/or from one or more users. The PCRF 250 can provide these policies to the PGW 220 or other device such that the policies can be executed. As depicted, in several embodiments, PCRF 250 can communicate with PGW 220 to ensure that the charging policy is properly applied to the local routing connection phase within the telecommunications network. For example, after the local routing connection phase is over, the PGW 220 can collect charging information about the connection phase and provide the charging information to the PCRF 250 for execution.

The number of devices and/or networks illustrated in Figure 2 is for illustrative purposes only. In fact, there may be additional devices and/or networks that are exemplified in FIG. 2; fewer devices and/or networks; different devices and/or networks; or differently arranged devices and/or networks. Additionally or alternatively, one or more of such devices of system 100 can perform one or more functions as performed by one or more of such devices of system 100. Again, although "direct" links are shown in Figure 2, such links must be interpreted as logical communication paths, and in fact, there may be one or more intermediaries (eg, routers, gateways, modems) , exchangers, hubs, etc.).

3-6 are a sequence flow diagram of a program instance in which a UE attaches to a CN through a non-3GPP RAN. As shown, the attached program examples of FIGS. 3-6 can include UE 110, non-3GPP access device 130, N3AS device 140, control plane cloud, and HSS 240. The apparatus and cloud examples shown in Figures 3-6 are as described above with reference to Figures 1 and 2. The example of the attachment procedure of Figures 3-6 includes certain operational annotations relating to "standardized RAN to CN interface/telecom" which may indicate the UE due to the functionality of the N3AS protocol and/or N3AS device 140 (as described herein) 110 can be connected to the CN through the same interface used by the 3GPP LTE standard (eg, the S1 interface of the 3GPP communication standard).

The examples provided in Figures 3-6 also include the description of the Extended Authentication Protocol (EAP) operation, which may include various request messages and response messages (labeled "EAP-REQ" and "EAP-RSP", respectively). The EAP operation intent represents an operation specific to a non-3GPP protocol type implemented by a non-3GPP RAN. As mentioned above, one example of a non-3GPP protocol may include the IEEE 802.11 communication standard; however, the techniques illustrated by the EAP operations described in Figures 3-6 may be implemented using other types of non-3GPP communication standards.

As shown, the UE 110 can establish a connection with the non-3GPP access device 130 (block 310). The operations performed by UE 110 and non-3GPP access device 130 to establish a connection may depend on the type of RAN implemented. For example, when the non-3GPP access device 130 includes a Wi-Fi router, the UE 110 and the non-3GPP access device 130 can perform operations consistent with the IEEE 802.11 communication standard.

In some embodiments, the UE 110 may send an inquiry message about the capabilities of the non-3GPP access device 130 and/or the WLAN of the non-3GPP access device 130 (eg, accessing an Internet Query Protocol (ANQP) message) to the non-3GPP. The device 130 is picked up. For example, UE 110 may query the CN for whether non-3GPP access device 130 is capable of causing UE 110 to connect to a wireless telecommunications network. In response to this, the non-3GPP access device 130 can notify the UE 110 that the UE 110 can connect to the CN of the wireless telecommunications network through the non-3GPP access device 130. In several embodiments, this may enable UE 110 to communicate with non-3GPP access device 130 using one or more of the techniques described herein. For example, as described in detail later, the UE 110 may begin to communicate with the non-3GPP access device 130 using the N3AS protocol, which enables the UE 110 to connect to the CN through the N3AS device 140. In several embodiments, UE 110 may notify non-3GPP access device 130 that UE 110 intends to connect to the CN. As such, the N3AS protocol described herein can be dynamically directed into the attach procedure between UE 110 and non-3GPP access device 130 and/or UE 110 and CN.

The non-3GPP access device 130 can transmit an EAP-REQ message regarding the identity of the UE 110 (block 320). In accordance with the N3AS protocol described herein, UE 110 may respond by transmitting an EAP-RES message including identity information requested by the EAP-REQ message. Additionally or alternatively, the EAP-RES message may include (eg, encapsulate) an attach request message. The attach request message may correspond to a specific message of one of the protocols/standards implemented by the CN. For example, the attachment request message may include a [NAS] Attach Request message of the 3GPP communication standard.

The non-3GPP access device 130 may respond to the EAP-RES message from the UE 110 by transmitting an AAA Diameter message to the N3AS device 140. The AAA Diameter message (or "diameter message") may include a Diameter Agreement message that corresponds to an Authentication, Authorization, and Accounting (AAA) agreement. As described herein, the AAA Diameter message can extend the functionality of the EAP Protocol/Message and can be part of the N3AS protocol. As shown, the AAA Diameter message includes (e.g., encapsulates) an EAP-RES message from UE 110.

The N3AS device 140 may extract the attach request message from the AAA diameter message and send an attach request message to the control plane cloud of the CN (line 350). As shown, the attachment request message can be part of a standardized RAN-to-CN signaling protocol, such as the 3GPP communication standard. In other words, the N3AS device 140 can communicate with the CN (eg, the control plane cloud) in the same or similar manner that the eNB of the LTE network may communicate with the CN. In response to the attach request message, the control plane cloud may exchange authentication information request (AIR) messages with HSS 240 (lines 360 and 370), which may include the control plane cloud receiving an authentication key independent variable (AKA) vector from HSS 240 (line 370) ). In response to the AIR message from HSS 240, the control plane cloud may derive keying material 380 for UE 110 (block 380).

Referring to Figure 4, the N3AS device 140 is transmitted by transmitting a downlink (DL) NAS, which may include an authentication request message, and the control plane cloud may continue to normalize the RAN to CN signaling (line 410). The authentication request message may be a [NAS] authentication request message of the 3GPP communication standard. In response, the N3AS device 140 can send an AAA Diameter message to the non-3GPP access device 130, which can include the Encapsulation Authentication Request message in an EAP-REQ message (line 420). The non-3GPP access device 130 may in turn send an EAP-REQ authentication request message to the UE 110 (line 430). The UE 110 may then send an EAP-RSP message by generating an appropriate AKA vector response (block 440), which may include an authentication response message to the non-3GPP access device 130 (line 450). The authentication response message may include a [NAS] authentication response message of the 3GPP communication standard.

As shown, non-3GPP access device 130 may send another AAA diameter message to N3AS device 140, which may include an EAP-RES authentication response message originated by UE 110 (line 460). This may cause the N3AS device 140 to transmit an uplink (UL) NAS transmission message to the CN's control plane cloud (line 470). As shown in the figure, the UL NAS transmission message may include an authentication response message. In addition, the UL NAS transport message may be part of a standardized RAN-to-CN protocol (eg, 3GPP protocol).

Referring to Figure 5, the control plane cloud can continue to standardize the RAN-to-CN signaling protocol. For example, the control plane cloud can verify the response (i.e., the authentication response message) originated by the UE 110 and continue the attach procedure (block 510). The control plane cloud may send an initial context setting request message to the N3AS device 140 (line 520). The initial context setting request message may include an attach accept message. The Attach Accept message may include a [NAS] Attach Accept message for the 3GPP communication standard.

The N3AS device 140 may respond to the request from the control plane cloud by transmitting an AAA diameter message including an EAP-REQ message with an attached accept message. The EAP-REQ message may also include N3AS function (N3ASF) information (line 530). Examples of N3ASF information may include information used to cause UE 110 to continue communicating with N3AS device 140 after completion of the attach procedure (eg, Internet Protocol (IP) address of N3AS device 140, user data package agreement for N3AS device 140 (UDP), security information, etc.).

The non-3GPP access device 130 can send an EAP-REQ message (with an Attach Accept message and N3ASF information) to the UE 110 (line 540). In turn, UE 110 may send an EAP-RSP message (which includes (eg, encapsulate) an Attach Complete message) to non-3GPP access device 130 (line 550). The Attach Complete message may include a [NAS] Attach Complete message of the 3GPP communication standard.

The non-3GPP access device 130 can send an AAA Diameter message including the EAP-RSP message and the Attach Complete message to the N3AS device 140 (line 560). In response, the N3AS device 140 can continue to attach the program using the standardized RAN to signal the CN. For example, as shown, the N3AS device 140 can send an initial context setting response message (which includes an attachment completion message) to the control plane cloud (line 570).

Referring to Figure 6, the control plane cloud can continue to attach procedures using the standardized RAN to signal the CN. For example, the control plane cloud is operable to complete the CN end of the attach procedure (block 610). In addition or in addition, the N3AS device 140 may complete the CN terminal of the attach procedure by transmitting an AAA diameter message to the non-3GPP access device 130, which may include an EAP-RSP success message (line 620), and the non-3GPP access device 130. The EAP-RSP success message may be sent to the UE 110 in response (line 630).

7 is a schematic diagram of a protocol stack that can be used to implement at least some of the techniques described herein. As shown in the figure, the protocol stack can communicate with the UE 110 and the N3AS device 140 through the SUp interface. The protocol stack may include an N3AS protocol layer, a data transport layer security (DTLS) layer, UDP, an IP version 4 (IPv4) and IPv6 layer, and an IEEE 802.11 layer. In several embodiments, the N3AS protocol layer of Figure 7 can include two primary functions. The first primary function may include an additional NAS-transmitted transparent and secure transfer function that may be substituted for at least a portion of the RRC direct transfer procedure. The second primary function may include communicating information about the user plane bearer (e.g., transport address, quality of service (QoS) information, etc.) that may be substituted for at least a portion of the RRC link reassembly procedure.

8 is a schematic diagram of an example of a network architecture that can be utilized to implement at least some of the techniques described herein. The network architecture illustrated in Figure 8 is for illustrative purposes only. In fact, there may be additional devices, networks, and/or interfaces as compared to the exemplified in Figure 8; fewer devices, networks, and/or interfaces; different devices, networks, and/or interfaces; or different Arranged devices, networks, and/or interfaces. In addition, the interface names/indications provided in FIG. 7 (eg, Y1, Y2, Y3, NG2, NG3, etc.) are for illustrative purposes only. In fact, the device shown in Figure 8 can communicate via interfaces with different indications.

As shown, the UE 110 can communicate with the non-3GPP access device 130 via a Y1 interface based on the implemented non-3GPP RAN type. For example, when the non-3GPP RAN is a Wi-Fi network, the Y1 interface may include an IEEE 802.11 interface. The non-3GPP access device 130 can communicate with the N3AS device 140 over the Y2 interface, which can include any type of convenient wireless or wired link (e.g., an Ethernet interface).

UE 110 may communicate with N3AS device 140 via a Y3 interface that implements some or all of the N3AS protocols (also referred to as "non-3GPP RAN protocol links") described herein. In several embodiments, the N3AS protocol may be functionally similar to the RRC protocol implemented by the UTRAN; however, it should be noted that the N3AS protocol may have different and/or additional functionality. For example, the N3AS protocol can enable transparent transmission of NAS messages between the UE 110 and the CN, as well as exchange of user plane carrier information between the UE 110 and the N3AS device 140, including security information.

As described herein, transparent transmission may include the CN confirming that a particular UE is linked to the CN through a non-3GPP RAN, which may include the CN confirming that certain services (eg, certain RRC services) may not be applicable to a particular UE. For example, when the UE 110 is connected to the CN through the Wi-Fi network, the CN may confirm that the UE 110 may not need certain services/programs, such as UE idle mode service, transition between UE idle mode and UE connected mode. , UE mobility services, UE messaging services, Tracking Area Update (TAU) services, etc. This may be the result of the nature of the connection between the UE and the WLAN (and/or the protocol implemented by the WLAN). For example, when connected to a Wi-Fi network, the UE can consider the infinite mode of operation (ie, not entering the idle mode). As another example, the UE may not require mobile services because the UE is unable to seamlessly transition between Wi-Fi networks (eg, experience handover) when the UE moves from one location to another.

The N3AS device 140 can communicate with the control plane cloud through the NG3 interface. The NG3 interface can be an EPS-like S1-MME interface. The N3AS device 140 can communicate with the user plane cloud through the NG4 interface, which can be an EPS-like S1-U interface. The user plane cloud and the control plane cloud may communicate via the NG5 interface, which may be an Sxa, Sxb, and/or Sxc interface similar to the 3GPP Technical Report TR 23.714.

As used herein, a non-3GPP RAN protocol may include a protocol that includes EAP to communicate 3GPP Non-Access Stratum (NAS) messages (related to the attach procedure) between the UE 110 and the N3AS device 140. Additionally or alternatively, the EAP message may be used by the N3AS device 140 to provide the UE 110 with the IP address and UDP port number of the N3AS device 140, along with appropriate security information, to establish a non-3GPP access layer between the UE 110 and the N3AS device 140. (N3-AS) Agreement link. An N3-AS protocol link (also referred to herein as a non-3GPP RAN protocol link) may be used to relay NAS messages between the UE 110 and the CN and/or between the UE 110 and the N3AS device 140 (not related to the attach procedure), Information about the carrier and so on.

9 and 10 are flow diagrams of an example of a method 900 for enabling a non-3GPP RAN UE to access a CN through a standardized communication interface. The method examples of FIGS. 9 and 10 can be implemented by the N3AS device 140.

Referring to FIG. 9, method 900 can include receiving an EAP-RES message originating from UE 110, including an attach request intended for delivery to the CN (block 910). For example, the non-3GPP access device 130 may encapsulate an attach request corresponding to a communication protocol implemented by the CN (eg, the 3GPP communication standard) within an EAP response message. In addition, the non-3GPP access device 130 can send an EAP response message to the N3AS device 140.

Method 900 can also include generating a 3GPP Attach Request message based on the EAP-RES message from UE 110, and transmitting the 3GPP Attach Request message to CN (block 920). For example, the N3AS device 140 may extract the attach request message encapsulated in the EAP-RES message from the UE 110 and send the attach request message to the CN. The Attach Request message may be part of a standardized form of communication implemented by the CN design, such as the 3GPP communication standard.

As described above, the attach request message can trigger an attach procedure with the CN whereby the UE 110 can establish a connection with the CN. In addition, the 3GPP Attach Request message may include a [NAS] Attach Request message. In addition, the eNB (or other type of 3GPP RAN device) will use to send an attach request message to the same type interface (eg, S1 interface) of the CN, and the N3AS device 140 may send the 3GPP Attach Request message to the CN.

Method 900 can include receiving a 3GPP authentication request from the CN and transmitting the authentication request to UE 110 (block 930). For example, in response to transmitting a 3GPP Attach Request to the CN, the N3AS device 140 may receive a 3GPP Authentication Request message from the CN and may notify the UE 110 of the authentication request message. As described above, the N3AS device 140 may accomplish this by transmitting an AAA Diameter message to the UE 110 through the non-3GPP access device 130. In some embodiments, the 3GPP authentication request message can include a [NAS] authentication request message. In addition, the same type of interface (e.g., S1 interface) that the CN will use to send an authentication request message to the eNB or other type of 3GPP RAN device, the CN may send the 3GPP authentication request to the N3AS device 140.

Method 900 can include receiving an EAP-RES message originating from UE 110, including an authentication response message (block 940). For example, the N3AS device 140 can receive an AAA diameter message from the non-3GPP access device 130, including an EAP-RES message having an authentication response message encapsulation therein.

Method 900 can include generating a 3GPP authentication response message based on the EAP-RES message and transmitting the 3GPP authentication response message to the CN (block 950). For example, the N3AS device 140 may extract an authentication response message encapsulated within the EAP-RES message and generate a 3GPP authentication response message from the content of the EAP-RES message. In some embodiments, the 3GPP authentication response message can include a [NAS] authentication response message. In addition, the same type of interface (eg, S1 interface) used by the eNB (or other type of 3GPP RAN device) to send an attach response message to the CN may be sent by the N3AS device 140 to the 3GPP attach response message. CN.

Method 900 can include receiving a 3GPP Attach Receive from the CN and transmitting the Attach Accept and N3 AWSF information to UE 110 (block 960). For example, in response to transmitting the 3GPP authentication response to the CN, the N3AS device 140 can receive a 3GPP Attach Accept message from the CN and can notify the UE 110 of the Attach Accept message. As described above, the N3AS device 140 may accomplish this by transmitting an AAA Diameter message to the UE 110 through the non-3GPP access device 130.

As also previously described, the N3 AWSF information may include information to cause the UE 110 to continue communicating with the N3 AWS device 140 after the UE 110 has successfully attached to the CN (eg, the IP address of the N3AWS device 140, the UDP of the N3AS device 140, security information) Wait). In some embodiments, the 3GPP Attach Accept message may include a [NAS] Attach Accept message. In addition, the CN may send an Attach Accept message to the eNB or other type of 3GPP RAN device (eg, S1 interface) via the CN, and the CN may send a 3GPP Attach Accept message to the N3AS device 140.

Referring now to FIG. 10, method 900 can include receiving an EAP-RES message originating from UE 110, including an attach completion message (block 1010). For example, the N3AS device 140 can receive an AAA Diameter message from the non-3GPP access device 130, including an EAP-RES message having an Attach Complete message envelope.

Method 900 can include generating a 3GPP Attach Complete message based on the EAP-RES message and transmitting the 3GPP Attach Complete message to the CN (block 1020). For example, the N3AS device 140 may extract an attach completion message inside the encapsulated EAP-RES message and generate a 3GPP Attach Complete message from the content of the EAP-RES message. In some embodiments, the 3GPP Attach Complete message can include a [NAS] Authentication Response message. In addition, the same type of interface (eg, S1 interface) used by the eNB (or other type of 3GPP RAN device) to send an attach complete message to the CN, the N3AS device 140 may send the 3GPP Attach Complete message to CN.

Method 900 can include notifying the UE that the attachment is successful via the EAP-RSP message (block 1030). For example, the N3AS device 140 can generate an EAP-RSP message including an attach success message. The attach success message may notify the UE 110 that the UE 110 has successfully linked to the CN.

Method 900 can include communicating with UE 110 over an N3AS protocol and providing radio resource control support to the UE (block 1040). For example, at some point after the UE 110 has successfully connected to the CN, the N3AS device 140 and the UE 110 may communicate with each other through the N3AS protocol, which may involve the Y3 interface discussed above with respect to FIG. In addition, N3AS device 140 may provide radio resource control support to UE 110, which may include N3AS device 140 and UE 110 communicating with respect to a user plane carrier (e.g., transport address, QoS, etc.).

As used herein, the term "circuit" or "processing circuit" may mean, as part of, or include an application-specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or group), and/or Or memory (shared, dedicated, or group) that executes one or more software or firmware programs, combinational logic circuits, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry can be implemented in one or more software or firmware modules, or the related functions of the circuitry can be implemented by the modules. In some embodiments, the circuitry can include logic that is at least partially operable in hardware.

The embodiments described herein can be implemented as a system using any suitably assembled hardware and/or software. FIG. 11 illustrates a component example of an electronic device 1100 for one embodiment. In an embodiment, the electronic device 1100 can be a UE, an eNB, a WLAN AP, or some other suitable electronic device. In some embodiments, the electronic device 1100 can include an application circuit 1102, a baseband circuit 1104, a radio frequency (RF) circuit 1106, a front end module (FEM) circuit 1108, and one or more antennas 1160, at least coupled together as shown. . In other embodiments, any of the circuits can be included in different devices.

Application circuit 1102 can include one or more application processors. For example, application circuit 1102 can include circuitry such as, but not limited to, one or more single core or multi-core processors. The (or) processor can include any combination of a general purpose processor and a special purpose processor (eg, a graphics processor, an application processor, etc.). The processor can be coupled and/or can include a memory/storage device and can be configured to execute instructions stored in the memory/storage device to enable the application and/or operating system to run on the system. In some embodiments, storage medium 1103 can include non-transitory computer readable media. The memory/storage device can include, for example, a computer readable medium 1103, which can be a non-transitory computer readable storage medium. In some embodiments, the application circuit 1102 can be coupled to or include one or more sensors, such as environmental sensors, cameras, and the like.

The baseband circuit 1104 can include circuitry such as, but not limited to, one or more single core or multi-core processors. The baseband circuit 1104 can include one or more baseband processors and/or control logic for processing the baseband signals received from the receive signal path of the RF circuitry 1106 and generating a baseband signal for the transmit signal path of the RF circuitry 1106. . The baseband processing circuit 1104 can interface the application circuit 1102 for the generation and processing of the baseband signal, and for the control operation of the RF circuit 1106. For example, in some embodiments, the baseband circuit 1104 can include a second generation (2G) baseband processor 1104a, a third generation (3G) baseband processor 1104b, and a fourth generation (4G) baseband processor. 1104c, and/or other baseband processors 1104d for other existing generations, evolving generations, or generations to be developed in the future (eg, fifth generation (5G), 6G, etc.). The baseband circuitry 1104 (e.g., one or more of the baseband processors 1104a-d) can handle various radio control functions such that it can communicate with one or more radio networks via the RF circuitry 1106. Radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like. In some embodiments, the baseband circuit 1104 can be associated with the storage medium 1103 or with other storage media.

In several embodiments, the modulation/demodulation circuitry of the baseband circuit 1104 can include fast Fourier transform (FFT), precoding, and/or clustering mapping/de-interlacing functionality. In some embodiments, the encoding/decoding circuitry of the baseband circuit 1104 can include convolution, tail biting convolution, turbo boost, Viterbi, and/or low density parity check (LDPC) encoder/decoder. Features. Embodiments of the modulation/demodulation and encoder/decoder functions are not limited to such examples, and other suitable functions may be included in other embodiments. In several embodiments, the baseband circuit 1104 can include elements of a protocol stack such as elements of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) protocol including, for example, physical (PHY), MAC, Radio Link Control (RLC). , PDCP, and/or Radio Resource Control (RRC) components. The central processing unit (CPU) 1104e of the baseband circuit 1104 can be configured to run the protocol stacked components for PHY, MAC, RLC, PDCP, and/or RRC layer signaling. In some embodiments, the baseband circuit can include one or more audio digital signal processors (DSPs) 1104f. The audio DSP 1104f may include elements for compression/decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

The baseband circuit 1104 can further include a memory/storage device 1104g. The memory/storage device 1104g can be used to load and store data and/or instructions for operation by the processor of the baseband circuit 1104. Memory/storage devices for one embodiment may include any combination of suitable electrical memory and/or non-electrical memory. The memory/storage device 1104g can include any combination of various hierarchical memory/storage devices including, but not limited to, read only memory (ROM), random access memory (with firmware) embedded in software instructions (eg, firmware) ( For example, dynamic random access memory (DRAM), cache memory, buffers, and the like. The memory/storage device 1104g may be shared among various processors or may be dedicated to a particular processor.

In some embodiments, the components of the baseband circuit can be conveniently combined on a single wafer, a single wafer set, or on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 1104 and the application circuit 1102 can be implemented together on, for example, a single-chip system (SOC).

In several embodiments, the baseband circuit 1104 can provide communications for compatibility with one or more radio technologies. For example, in some embodiments, the baseband circuit 1104 can support communication with E-UTRAN and/or other wireless metropolitan area networks (WMANs), WLANs, wireless personal area networks (WPANs). Embodiments in which the baseband circuit 1104 is configured to support more than one wireless protocol for radio communication may be referred to as a multimode baseband circuit.

The RF circuit 1106 can enable communication with a wireless network using modulated electromagnetic radiation via a non-solid medium. In various embodiments, RF circuitry 1106 can include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. The RF circuit 1106 can include a receive signal path that can include circuitry to downconvert the RF signal received from the FEM circuit 1108 and provide a baseband signal to the baseband circuit 1104. The RF circuit 1106 can also include a transmit signal path that can include circuitry to upconvert the baseband signal provided by the baseband circuit 1104 and provide an RF output signal to the FEM circuit 1108 for transmission.

In several embodiments, RF circuit 1106 can include a receive signal path and a transmit signal path. The receive signal path of the RF circuit 1106 can include a mixer circuit 1106a, an amplifier circuit 1106b, and a filter circuit 1106c. The transmit signal path of RF circuit 1106 can include filter circuit 1106c and mixer circuit 1106a. The RF circuit 1106 can also include a synthesizer circuit 1106d for synthesizing a frequency for use by the mixer circuit 1106a that receives the signal path and transmits the signal path. In several embodiments, the mixer circuit 1106a that receives the signal path can be assembled to downconvert the RF signal received from the FEM circuit 1108 based on the synthesized frequency provided by the synthesizer circuit 1106d. Amplifier circuit 1106b can be configured to amplify the downconverted signal, and filter circuit 1106c can be a low pass filter (LPF) or a band pass filter (BPF) that is configured to convert from the downconverted signal The undesired signal is removed to produce an output baseband signal.

The output baseband signal can be provided to the baseband circuit 1104 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, but is not necessary. In several embodiments, the mixer circuit 1106a that receives the signal path can include a passive mixer, although the scope of the embodiments is not limited to this aspect.

In several embodiments, the mixer circuit 1106a that transmits the signal path can be configured to upconvert the input baseband signal based on the synthesized frequency provided by the synthesizer circuit 1106d to generate an RF output signal for the FEM circuit 1108. The baseband signal can be provided by the baseband circuit 1104 and can be filtered by the filter circuit 1106c. The filter circuit 1106c may include a low pass filter (LPF), but the scope of the embodiment is not limited to this aspect.

In several embodiments, the mixer circuit 1106a that receives the signal path and the mixer circuit 1106a that transmits the signal path may include two or more mixers and may be configured for quadrature down conversion and/or upconversion, respectively. In several embodiments, the mixer circuit 1106a that receives the signal path and the mixer circuit 1106a that transmits the signal path may include two or more mixers and may be configured for image carrier suppression (eg, Hartley) Image carrier suppression). In several embodiments, the mixer circuit 1106a and the mixer circuit 1106a that receive the signal path can be configured for direct down conversion and/or direct up conversion, respectively. In several embodiments, the mixer circuit 1106a that receives the signal path and the mixer circuit 1106a that transmits the signal path can be assembled for superheterodyne operation.

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 to this aspect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In alternative embodiments, RF circuit 1106 can include an analog to digital converter (ADC) and a digital to analog converter (DAC) circuit, and base frequency circuit 1104 can include a digital fundamental interface in communication with RF circuit 1106.

In several dual mode embodiments, separate radio IC circuits may be provided for processing signals of various frequency spectra, although the scope of the embodiments is not limited to this aspect.

In some embodiments, the synthesizer circuit 1106d may be a fractional-N synthesizer or a fractional N/N+6 synthesizer, although the scope of the embodiments is not limited to this aspect, as other types of frequency synthesizers may be suitable. . For example, the synthesizer circuit 1106d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer with a phase-locked loop with a frequency divider.

The synthesizer circuit 1106d can be assembled to synthesize the output frequency for use by the mixer circuit 1106a of the RF circuit 1106 based on the frequency input and the divider control input. In several embodiments, the synthesizer circuit 1106d can be a fractional N/N+6 synthesizer.

In several embodiments, the frequency input can be provided by a voltage controlled oscillator (VCO), but is not necessary. The divider control input can be provided by the baseband circuit 1104 or the application circuit 1102, depending on the desired output frequency. In some embodiments, the divider control input (eg, N) may be determined from the lookup table based on the channel indicated by the application circuit 1102.

The synthesizer circuit 1106d of the RF circuit 1106 can include a divider, a delay locked loop (DLL), a multiplier, and a phase accumulator. In some embodiments, the divider can be a dual mode divider (DMD), and the phase accumulator can be a digital phase accumulator (DPA). In several embodiments, the DMD can be assembled with an input signal divided by N or N+6 (eg, based on a carry output) to provide a fractional division ratio. In several embodiments, the DLL can include a set of cascaded tunable delay elements, phase detectors, charge pumping, and D-type flip-flops. In such embodiments, the delay elements can be configured to break a 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 a negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuit 1106d can be assembled to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of a carrier frequency (eg, twice the carrier frequency, four of the carrier frequency) And a joint quadrature generator and divider circuit is used to generate a plurality of signals at a carrier frequency having a plurality of different phases with respect to each other. In several embodiments, the output frequency can be the LO frequency (fLO). In several embodiments, RF circuit 1106 can include an IQ/polarity converter.

FEM circuit 1108 can include a receive signal path that can include circuitry configured to operate on an RF signal received from one or more antennas 1160, amplify the received signal, and provide an amplified version of the received signal to RF circuit 1106 is for further processing. The FEM circuit 1108 can also include a transmit signal path that can include circuitry that is configured to amplify the transmit signal provided by the RF circuit 1106 for transmission by one or more of the one or more antennas 1160.

In several embodiments, FEM circuit 1108 can include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuit can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit can include a low noise amplifier (LNA) to amplify the received RF signal and provide an amplified received RF signal as an output (e.g., to RF circuit 1106). The transmit signal path of FEM circuit 1108 can include a power amplifier (PA) to amplify the input RF signal (eg, provided by RF circuit 1106), and one or more filters to generate an RF signal for subsequent transmission (eg, by One or more of the one or more antennas 1160.

In some embodiments, electronic device 1100 can include additional components such as a memory/storage device, a display, a camera, a sensor, and/or an input/output (I/O) interface. In some embodiments, the electronic device of FIG. 11 can be assembled to perform one or more methods, processes, and/or techniques, such as those described herein.

12 is a block diagram illustrating one or more of the steps of reading instructions and performing the methods discussed herein from a machine readable or computer readable medium (eg, machine readable storage medium) in accordance with some embodiments. s component. In particular, FIG. 12 shows a representative diagram of a hardware resource 1200 that includes one or more processors (or processor cores) 1210, one or more memory/storage devices 1220, and one or more communication resources 1230, wherein Each of them is communicatively coupled through a busbar 1240.

A processor 1210 (eg, a central processing unit (CPU), a reduced instruction set computer (RISC) processor, a complex instruction set computer (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband A processor, an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), other processors, or any suitable combination thereof, can include, for example, a processor 1212 and a processor 1214. Memory/storage device 1220 can include a primary memory, a disk storage device, or any suitable combination thereof.

Communication resources 1230 can include interconnect and/or network interface components or other suitable means for communicating with one or more peripheral devices 1204 and/or one or more databases 1206 via network 1208. For example, communication resource 1230 can include wired communication components (eg, for coupling through a universal serial bus (USB)), cellular communication components, near field communication (NFC) components, Bluetooth® components (eg, Bluetooth®) Low energy), Wi-Fi® components, and other communication components.

The instructions 1250 can include software, programs, applications, mini-apps, mobile applications, or other executables that cause at least one of the processors 1210 to perform any one or more of the methods discussed herein. code. The instructions 1250 may reside entirely or partially in any of the processors 1210 (eg, within the cache memory of the processor), the memory/storage device 1220, or any suitable combination thereof. Again, any portion of the instruction 1250 can be transferred to the hardware resource 1200 from any combination of the peripheral device 1204 and/or the repository 1206. Thus, the memory of processor 1210, memory/storage device 1220, peripheral device 1204, and database 1206 are examples of computer readable and machine readable media.

Next, a plurality of examples relating to the technical embodiments described above will be described.

In a first example, an apparatus for an application processor of a network device can include circuitry for implementing a non-third generation partnership project (3GPP) Radio Access Network (RAN) protocol for Linking to a non-3GPP RAN user equipment (UE) communication; implementing a 3GPP RAN protocol for communicating with a 3GPP core network (CN); and by accessing the independent RAN to the CN interface by using the following steps, Relaying information between the UE and the 3GPP CN: converting a message originating from the UE and carrying information intended for the 3GPP CN from the non-3GPP RAN protocol to the 3GPP RAN protocol; and will originate from the 3GPP The CN and the message carrying the information intended for the UE are converted from the 3GPP RAN protocol to the non-3GPP RAN protocol.

In Example 2, the subject matter of Example 1, or any one of the examples herein, wherein, according to the non-3GPP RAN protocol, the circuit is used to communicate a 3GPP non-related to an attachment procedure between the UE and the 3GPP CN Access layer (NAS) information.

In Example 3, the subject matter of Example 1, or any one of the examples herein, wherein the circuit is used to use an Extensible Authentication Protocol (EAP), in addition to security information, to the UE An Internet Protocol (IP) address and a User Datagram Protocol (UDP) number of the network device enable a non-3GPP RAN protocol connection between the network device and the UE.

In Example 4, the subject matter of Example 3 or any one of the examples herein, wherein the circuitry is to use the non-3GPP RAN protocol link to carry information for a data carrier in the non-3GPP RAN.

In Example 5, the subject matter of Example 1 or any one of the examples herein, wherein the non-3GPP RAN protocol is implemented as part of an attach procedure between the UE and the 3GPP CN.

In Example 6, the subject matter of Example 1, or any one of the examples herein, wherein the circuit is configured to: receive a first extendable authentication protocol (EAP) response from the UE according to the non-3GPP RAN protocol One of the 3GPP attach requests in (EAP-RSP), and one of the 3GPP attaches received from the UE in a second EAP-RSP is completed.

In Example 7, the subject matter of Example 1, or any one of the examples herein, wherein the circuit is configured to: pass an extendable authentication protocol (EAP) request (EAP-REQ) according to the non-3GPP RAN protocol The communication is received from the 3GPP CN of the 3GPP CN and is accepted by the UE.

In the example 8, the subject matter of the example 7 or any one of the examples herein, wherein the EAP-REQ also includes an internet protocol (IP) of the network device of the UE in addition to security information. The address and the User Datagram Protocol (UDP) port number enable a non-3GPP RAN protocol connection between the network device and the UE.

In any one of the preceding claims, wherein the circuit is configured to: receive a query message relating to the capabilities of the non-3GPP RAN; and notify the query message in response to the query The UE may communicate with the 3GPP CN through the non-3GPP RAN.

In a tenth example, a non-transitory computer readable medium having program instructions for causing one or more processors to: cause a link to a non-3rd Generation Partnership Project (3GPP) radio connection by the following steps A user equipment (UE) of a network (RAN) capable of connecting to the core network through a standardized RAN-to-core network (CN) interface that can be applied to both a 3GPP RAN and a non-3GPP RAN of a wireless telecommunications network a CN of a telecommunications network: converting a message originating from the UE and carrying information intended for the 3GPP CN from the non-3GPP RAN protocol to the 3GPP RAN protocol; and will originate from the 3GPP CN and carry A message having information intended for the UE is converted from the 3GPP RAN protocol to the non-3GPP RAN protocol.

In the example 11, the subject matter of the example 10, or any one of the examples herein, wherein, according to the non-3GPP RAN protocol, the program instructions cause the one or more processors to: use the UE with the 3GPP CN Inter-communication-attached 3GPP Non-Access Layer (NAS) information.

In the example 12, the subject matter of example 10, or any one of the examples herein, wherein, according to the non-3GPP RAN protocol, the program instructions cause the one or more processors to: use a deferrable authentication protocol ( EAP) is used to provide an Internet Protocol (IP) address and a User Datagram Protocol (UDP) number of the network device to the UE in addition to the security information, such that the network device and the UE There can be a non-3GPP RAN protocol link.

In any one of the preceding claims, wherein the program instructions, in accordance with the non-3GPP RAN protocol, cause the one or more processors to: use the non-3GPP RAN protocol link to The information carrier carries information for the non-3GPP RAN.

In Example 14, the subject matter of Example 10, or any one of the examples herein, wherein the non-3GPP RAN protocol is implemented as part of an attach procedure between the UE and the CN.

In any of the examples of the example 10, or any one of the examples herein, wherein, according to the non-3GPP RAN protocol, the program instructions cause the one or more processors to: receive from the UE One of the 3GPP attach requests in an extendable authentication protocol (EAP) response (EAP-RSP), and one of the 3GPP attaches received from the UE in a second EAP-RSP is completed.

In any one of the embodiments of the present invention, wherein the program instructions cause the one or more processors to: pass a deferrable authentication protocol, according to the non-3GPP RAN protocol (EAP) Request (EAP-REQ), communication originated from one of the CN 3GPP attachments received by the UE.

In any one of the embodiments of the present invention, wherein the EAP-REQ includes, in addition to the security information, an Internet Protocol (IP) of the network device of the UE. The address and the User Datagram Protocol (UDP) port number enable a non-3GPP RAN protocol connection between the network device and the UE.

In Example 18, the subject matter of Example 1 or 10, or any one of the examples herein, wherein the non-3GPP RAN protocol link is implemented on top of a Packet Transport Layer Security (DTLS) protocol.

In a nineteenth example, a network device can include a non-third generation partnership project (3GPP) radio access network (RAN) protocol for interfacing with a user equipment (UE) coupled to a non-3GPP RAN a means for communicating; a means for implementing a 3GPP RAN protocol for communicating with a 3GPP core network (CN); and for accessing the CN interface through an access independent RAN by the following steps, at the UE and the A component of 3GPP CN relay information: converting a message originating from the UE and carrying information intended for the 3GPP CN from the non-3GPP RAN protocol to the 3GPP RAN protocol; and will originate from the 3GPP CN and The message carrying the information intended for the UE is converted from the 3GPP RAN protocol to the non-3GPP RAN protocol.

In the example 20, the subject matter of the example 19 or any one of the examples herein, wherein the messages originating from the UE and the non-3GPP RAN protocol include, and one of the UE and the 3GPP CN The extended protocol (EAP) message encapsulated in the 3GPP Non-Access Layer (NAS) information.

In the example 21, the subject matter of the example 19, or any one of the examples herein, wherein the means for relaying information comprises: for extracting an encapsulation in an extendable authentication protocol (EAP) by extracting from the UE The 3GPP Non-Access Layer (NAS) information related to one of the UE and the 3GPP CN attachment procedure is internal to the message and the message is converted from the non-3GPP RAN protocol to the 3GPP RAN protocol.

In the example 22, the subject matter of the example 21 or any one of the examples herein, wherein the NAS message that is not related to the attachment program communicates via the non-3GPP RAN protocol.

In the example 23, the subject of example 19 or any one of the examples herein, further comprising: for receiving from the UE in a first extendable authentication protocol (EAP) response (EAP-RSP) a component of a 3GPP Attach Request; and means for receiving a 3GPP Attachment from a UE in a second EAP-RSP.

In Example 24, the subject matter of Example 19 or any of the examples herein is for transmitting an EAP-request (EAP-REQ) according to the non-3GPP RAN protocol, the communication originating from the A 3GPP CN of 3GPP CN attaches to the components of the UE.

In the example 25, the subject matter of the example 24 or any one of the examples herein, wherein the EAP-REQ also includes an internet protocol (IP) of the network device of the UE in addition to security information. The address and the User Datagram Protocol (UDP) port number enable a non-3GPP RAN protocol connection between the network device and the UE.

In the foregoing specification, various embodiments have been described with reference to the drawings. However, it is apparent that various modifications and changes can be made thereto, and additional embodiments can be practiced without departing from the scope of the invention. Accordingly, the specification and drawings are to be regarded as

For example, although the signal series has been described in terms of one or more figures, the ordering of the signals may be modified in other embodiments. Also, non-dependent signals can be performed in parallel.

It will be apparent that the examples as described above are implemented in many different forms of software, firmware, and hardware that may be employed in the embodiments illustrated in the drawings. However, the actual software code or specialized control hardware used to implement such aspects should not be interpreted as limiting. As such, such operations and performance are not described with reference to specific software code descriptions - the software and control hardware may be designed to implement such aspects based on the description herein.

Also, some parts may be implemented as "logic" that performs one or more functions. Such logic may include hardware, such as an application specific integrated circuit (ASIC) or field programmable gate array (FPGA), or a combination of hardware and software.

That is, a particular combination of features recited in the claims and/or disclosed in the specification is not intended to be limiting. In fact, many of these features may be combined in ways that are not specifically recited and/or not specifically disclosed in the specification.

The elements, acts, or instructions used in the present disclosure should not be construed as a limitation or limitation unless otherwise. As used herein, the use of the term "and" does not necessarily exclude the use of the phrase "and/or" intended to be interpreted in the context. In the same vein, as used herein, the use of the term "or" does not necessarily exclude the use of the phrase "and/or" intended to be interpreted in the context. Also, as used herein, the <RTI ID=0.0>"a" </ RTI> is intended to encompass one or more items and may be used interchangeably with the phrase "one or more". When only one item is expected, the terms "one", "single", "only", or similar text are used.

100... environment, system
110... User Equipment (UE)
120...Evolved Node B (eNB)
130...non-3GPP access device
140...non-3GPP access layer (N3AS) device
210...service gateway (SGW)
220...PDN Gateway (PGW)
230...Action Management Entity (MME)
240...Home User Server (HSS)
250...Policy and Charging Rules Function (PCRF)
310, 380, 440, 510, 610, 910-960, 1010-1040...
320-370, 410-430, 450-470, 520-570, 620, 630... line
900...method
1100...electronic device
1102...application circuit
1103...computer readable media
1104... fundamental frequency circuit
1104a... second generation (2G) baseband processor
1104b... third generation (3G) baseband processor
1104b... fourth generation (4G) baseband processor
1104d...other baseband processor
1104e... central processing unit (CPU)
1104f... audio digital signal processor (DSP)
1104g, 1220...memory/storage device
1106...radio frequency (RF) circuit
1106a... mixer circuit
1106b...amplifier circuit
1106c...filter circuit
1106d... synthesizer circuit
1108... Front End Module (FEM) Circuit
1160...antenna
1200...hard resources
1204... peripheral device
1206...Database
1208...network
1210, 1212, 1214... processor
1230... communication resources
1240... Busbar
1250... instruction
NG2-5, Y1-3... interface

Examples of the present embodiment will be readily understood by the following detailed description in conjunction with the drawings. To assist in the description herein, similar component symbols may identify similar structural components. The embodiments are illustrated by way of example and not limitation. 1 is a schematic diagram illustrating an example of a system in which the systems and/or methods described herein may be implemented; FIG. 2 is a schematic diagram of an example of a core network (CN); and FIG. 3-6 is between a user equipment (UE) and the CN. A sequence flow diagram of one of the attached program instances; FIG. 7 is a schematic diagram of a protocol stack that can be used to implement at least some of the techniques described herein; FIG. 8 is a diagram of one of the techniques that can be used to implement at least one of the techniques described herein. FIG. 9 and FIG. 10 are flowcharts showing an example of a method for causing a UE of a non-3GPP RAN to access the CN through a standardized communication interface; and FIG. 11 illustrates an example of an electronic device component for one embodiment. Figure 12 is a block diagram illustrating components capable of reading instructions from a machine readable or computer readable medium.

110‧‧‧User Equipment (UE)

120‧‧‧Evolved Node B (eNB)

130‧‧‧ Non-3GPP access device

140‧‧‧N3AS installation

Claims (24)

An apparatus for an application processor of a network device, comprising circuitry for: implementing a non-third generation partnership project (3GPP) radio access network (RAN) protocol to interface with a non-3GPP RAN User equipment (UE) communication; implementing a 3GPP RAN protocol to communicate with a 3GPP core network (CN); and through a separate operation of the RAN to CN interface, at the UE and the 3GPP CN Inter-relay information: converting a message originating from the UE and carrying information intended for the 3GPP CN from the non-3GPP RAN protocol to the 3GPP RAN protocol; and using the 3GPP CN and carrying the intended The information of the UE's information is converted from the 3GPP RAN protocol to the non-3GPP RAN protocol. The device of claim 1, wherein the circuit is operative to transmit 3GPP Non-Access Layer (NAS) information related to an attach procedure between the UE and the 3GPP CN according to the non-3GPP RAN protocol. The device of claim 1, wherein the circuit is configured to: use an extendable authentication protocol (EAP) to provide an Internet Protocol (IP) bit of the network device to the UE in addition to the security information. The address and the User Datagram Protocol (UDP) number are such that one of the network devices and the UE is not a 3GPP RAN protocol. The device of claim 3, wherein the circuit is configured to: use the non-3GPP RAN protocol link to carry information for the data carrier in the non-3GPP RAN. The device of claim 1, wherein the circuit is configured to: receive a 3GPP attach request from the UE in a first extendable authentication protocol (EAP) response (EAP-RSP) according to the non-3GPP RAN protocol And receiving one of the 3GPP attachments from the UE in a second EAP-RSP is completed. The device of claim 1, wherein the circuit is configured to: transmit a 3GPP attachment originating from the 3GPP CN through an extendable authentication protocol (EAP) request (EAP-REQ) according to the non-3GPP RAN protocol Accepted to the UE. The device of claim 6, wherein the EAP-REQ includes, in addition to the security information, an internet protocol (IP) address and a user data packet protocol (UDP) number of the network device, to enable The network device is connected to one of the UEs that is not a 3GPP RAN protocol. The device of claim 1, wherein the circuit is further configured to: receive an inquiry message about the capability of the non-3GPP RAN; and, in response to the inquiry message, notify the UE that the UE can communicate with the 3GPP CN through the non-3GPP RAN . A non-transitory computer readable medium containing program instructions for causing one or more processors to: be coupled to a non-3rd Generation Partnership Project (3GPP) radio access network by: a User Equipment (UE) of the RAN), coupled to the core network (CN) interface through a standardized RAN-to-core network (CN) interface that can be applied to both the 3GPP RAN and the non-3GPP RAN of a wireless telecommunications network a CN: converting a message originating from the UE and carrying information intended for the CN from the non-3GPP RAN protocol to a 3GPP protocol of the CN; and will originate from the CN and carry the intended use for the UE The information message is converted from the CN's 3GPP protocol to the non-3GPP RAN protocol. The non-transitory computer readable medium of claim 9, wherein, according to the non-3GPP RAN protocol, the program instructions cause the one or more processors to: pass between the UE and the 3GPP CN The 3GPP Non-Access Layer (NAS) information of the program. The non-transitory computer readable medium of claim 9, wherein, according to the non-3GPP RAN protocol, the program instructions cause the one or more processors to: use an extendable authentication protocol (EAP), in addition to In addition to the security information, an Internet Protocol (IP) address and a User Datagram Protocol (UDP) number provided to the UE of the network device to enable the network device of the one or more processors Connected to one of the UEs that is not a 3GPP RAN protocol. The non-transitory computer readable medium of claim 9, wherein the program instructions cause the one or more processors to: use the non-3GPP RAN protocol link to carry information for the data carrier in the non-3GPP RAN . The non-transitory computer readable medium of claim 9, wherein the program instructions cause the one or more processors to: pass an extendable authentication protocol (EAP) request (EAP) according to the non-3GPP RAN protocol -REQ), the delivery is received from the 3GPP CN, which is accepted by the 3GPP CN to the UE. The non-transitory computer readable medium of claim 13, wherein the EAP-REQ also includes, in addition to the security information, an internet protocol (IP) address and a user data package agreement of the network device ( UDP) 埠 number to enable the non-3GPP RAN protocol connection between the network device and the UE. The non-transitory computer readable medium of claim 9, wherein the non-3GPP RAN protocol is implemented as part of an attach procedure between the UE and the CN. The non-transitory computer readable medium of claim 9 wherein the non-3GPP RAN protocol link is implemented over a Packet Transport Layer Security (DTLS) agreement. A network device comprising: a network interface component; and circuitry for: performing a non-third generation partnership project (3GPP) radio access network (RAN) protocol to link to a non- a User Equipment (UE) communication of the 3GPP RAN; implementing a 3GPP RAN protocol to communicate with a 3GPP Core Network (CN); and through a separate access RAN to the CN interface, at the UE and the 3GPP CN relay information: converting a message originating from the UE and carrying information intended for the 3GPP CN from the non-3GPP RAN protocol to the 3GPP RAN protocol; and will originate from the 3GPP CN and carry the intended The information for the UE's information is converted from the 3GPP RAN protocol to the non-3GPP RAN protocol. The network device of claim 17, wherein the circuit is operative to communicate 3GPP Non-Access Layer (NAS) information associated with an attach procedure between the UE and the 3GPP CN according to the non-3GPP RAN protocol. The network device of claim 17, wherein the circuit is configured to: use an extendable authentication protocol (EAP) to provide an internet protocol (IP) to the UE of the network device in addition to the security information. The address and the User Datagram Protocol (UDP) number are such that one of the network devices and the UE is not a 3GPP RAN protocol. The network device of claim 19, wherein the circuit is configured to: use the non-3GPP RAN protocol link to carry information for the data carrier in the non-3GPP RAN. The network device of claim 17, wherein the circuit is configured to: receive one of the first extensible authentication protocol (EAP) responses (EAP-RSP) from the UE, in accordance with the non-3GPP RAN protocol The request is received, and one of the 3GPP attachments received from the UE in a second EAP-RSP is completed. The network device of claim 17, wherein the circuit is configured to: pass a 3GPP CN derived from the 3GPP CN through an extensible authentication protocol (EAP) request (EAP-REQ) according to the non-3GPP RAN protocol The attachment is accepted to the UE. The network device of claim 22, wherein the EAP-REQ also includes an Internet Protocol (IP) address and a User Datagram Protocol (UDP) port number of the network device in addition to the security information. So that the network device and one of the UEs are not connected to the 3GPP RAN protocol. The network device of claim 17, wherein the circuit is further configured to: receive an inquiry message about the capability of the non-3GPP RAN; and, in response to the inquiry message, notify the UE that the UE is permeable to the 3GPP RAN and the 3GPP CN communication.