Detailed Description
The section headings are used in this patent document only to improve readability, and not to limit the scope of the embodiments and techniques disclosed in each section to only that section. Some features are described using an example of a 5G wireless protocol. However, the applicability of the disclosed technology is not limited to 5G wireless systems.
The development of New generation wireless communication (5G New Radio (NR) communication) is part of a continuous mobile broadband evolution process for meeting the growing network demands. Currently, the 5G system architecture is defined to support data connections and services that enable deployments to use technologies such as network function virtualization and software defined networking. The 5G system architecture may utilize service-based interactions between Control Plane (CP) network functions. FIG. 1 shows an example reference point representation of a 5G system architecture. As shown in fig. 1, the 5G system architecture may include the following network functions: an Authentication Server Function (AUSF) 101, an Authentication and Mobility Management Function (AMF) 102, a Data Network (DN)103 (such as an operator service, internet Access, or third party service), a Structured Data Storage Network Function (SDSF) (not shown), an Unstructured Data Storage Network Function (UDSF) (not shown), a Network open Function (Network export Function, NEF) (not shown), a Network Storage Function (NF) Network Function, NRF), a Policy Control Function (Policy Function, PCF)104, a Session Management Function (SMF) 105, a Unified Data Management Function (AUSF, Management Function, Function 106, Function (Function) 108, a User Plane Selection Function (User interface, AF, Function 107), NSSF)109, User Equipment (UE)110, and Radio Access Network (R) AN 111.
The 5G technology is intended to enable a seamless connected society while integrating people with things, data, applications, transportation systems, and cities in an intelligent networked communication environment. In particular, non-3GPP access (e.g., Wireless Local Area Network (WLAN) access) is an important companion access infrastructure of mobile networks that can help mobile operators to cope with explosive growth in network traffic. Non-3GPP access thus may relieve pressure on the mobile network and may provide fast indoor data connectivity, thus playing an important role in implementing service mode evolution under the 5G framework.
A wired access network refers to a collection of "last mile" data transmission technologies that connect businesses and residences to a public communication network. Fig. 2 shows an example architecture 200 including a fixed network residential gateway for supporting a wired access network accessing a 5G core network. Fig. 3 shows an example architecture 300 that includes a 5G residential gateway (5G-RG) for supporting a wired access network that accesses a 5G core network. Each of the architectures may include one or more network functions as shown below:
residential Gateway (Residential Gateway, RG): the RG is a device capable of providing voice, data, broadcast video, and video on demand designated By Broadband Forum (BBF).
5G-RG: the 5G-RG is an RG that can be connected to a 5G core network. The 5G-RG plays a role of a UE with respect to a 5G core (5G core, 5 GC). It supports secure elements and exchanges N1 (interface) signaling with 5 GC.
Fixed Access Gateway Function (FAGF): the FAGF is a Network function in a wired 5G Access Network (W-5 GAN) that provides connectivity to the 5G core.
Fixed Network RG (Fixed Network RG, FN-RG): the FN-RG 201 (shown in fig. 2) is an RG that does not support N1 (interface) signaling. The FN-RG 201 plays a role similar to that of the UE in the 5G core. FN-RG is BBF-specified RG.
Hybrid access 5G-RG: a Hybrid Access (HA) 5G-RG 301 (shown in fig. 3) is a 5G-RG that is capable of connecting to a 5GC via both a 5G RAN and a wired access network.
Wired 5G access network: the wired 5G Access Network (W-5 GAN) (202, 302 shown in fig. 2 to 3) is a wired Access Network (AN) connected to the 5GC via N2 and N3 reference points.
To support wireless and wireline convergence, the 5G system may support the following functions:
the 1.5G system may support 5G-RG connections to 5GC via a Next Generation Radio Access Network (NG-RAN) or via a W-5 GAN. The 5G system may also support FN-RG connection to the 5GC via a wired AN. Both an RG supporting the N1 interface and an RG not supporting the N1 interface may be supported.
The 2.5G system may support end user equipment with or without a Universal Integrated Circuit Card (UICC) that connects to the converged 5G core network from either the 5G-RG or the FN-RG.
The 3.5G system can support a hybrid access scenario in which the 5G-RG is connected to the 5GC via both the NG RAN and the wired AN at the same time. The system may also support scenarios in which the 5G-RG/FN-RG are connected via a single access technology (NG-RAN or wired AN). The system may further support scenarios where 5G-RG/FN-RG are connected via two access technologies simultaneously. In the latter case, traffic may be split or switched between the two access technologies.
The 4.5G system may support the capability to enable the 5GC to identify UEs with 3GPP credentials configured to access networks behind various types of gateways based on operator policies and inter-operator agreements.
Referring back to fig. 3, a 5G-capable UE gains access to the 5G core network via the HA 5G-RG. From the perspective of a 5G-capable UE, a non-3GPP access network now provides 5GC access. The HA 5G-RG decides to use the 5GAN or NG RAN to send traffic for a 5G-capable UE. A UE supporting 5GC does not know which access technology to use and therefore cannot report its location information according to the access technology. This document discloses techniques that may be implemented in various embodiments in a residential gateway and/or an access network to obtain location information for the residential gateway and use that information to represent location information for a 5G-capable UE. The location information (e.g., 5G-RG and/or FN-RG) of the residential gateway may include any combination of the following:
(1) a Service Set Identifier (SSID) of a UE connected to the 5G-RG/FN-RG,
(2) a basic service set identifier (i.e., a Medium Access Control (MAC) address of an Access Point (AP) function in 5G-RG/FN-RG);
(3) a Homogeneous Extended Service Set Identifier (HESSID);
(4) the city address of 5G-RG/FN-RG;
(5) a line identifier;
(6) a geographic location; or
(7) Identifier information of a Radio Access Network (RAN). In some embodiments, the identifier information may be provided with a timestamp of when the 5G-RG was deployed in the hybrid access scenario. The RAN is either the RAN to which the 5G-RG is currently connected or the RAN to which the 5G-RG was last connected.
Fig. 10 is a flowchart representation of a method 1000 for wireless communication in accordance with one or more embodiments of the present technology. The method 1000 includes, at step 1001, receiving a first message at an access network from a residential gateway that supports a first network access technology and optionally includes a second network access technology. The residential gateway is configured to provide an access connection to a mobile device operating using a first network access technology. The first message includes location information of the residential gateway indicating location information of the mobile device. The method 1000 further includes, at step 1002, sending a second message including the received location information from the access network to the core network.
Fig. 11 is a flowchart representation of another method 1100 for wireless communication in accordance with one or more embodiments of the present technology. The method 1100 includes, at step 1101, sending, by a residential gateway supporting a first network access technology and optionally a second network access technology, a message to an access network. The message includes location information for the residential gateway. The residential gateway is configured to provide an access connection to a mobile device operating using a first network access technology. The location information of the residential gateway indicates location information of the mobile device.
Fig. 12 is a flowchart representation of another method 1200 for wireless communication in accordance with one or more embodiments of the present technology. The method 1200 includes, at step 1201, receiving, at an access network, a message from a core network requesting location information for a mobile device. The mobile device is configured to operate using a first network access technology. The method 1200 also includes, at step 1202, determining, by the access network, location information of the mobile device based on the location information of the residential gateway. The residential gateway supports a first network access technology and optionally a second network access technology and is configured to provide access connectivity to a mobile device.
Some examples of the disclosed technology are described in the following example embodiments.
Example 1
In some embodiments, the 5G-RG/FN-RG provides its location information to the W-5GAN during the process of registering with the 5G core network. Fig. 4 illustrates an example registration procedure for a 5G-RG in accordance with one or more embodiments of the present technology.
Step 421: layer 2 (L2) connection 411 is established between the 5G-RG 401 and a Trusted Non-3GPP Access Point (TNAP) 403 of a Trusted Non-3GPP Access Network (TNAN) 402. The TNAN 402 also includes a Trusted Non-3GPP Gateway Function (TNGF).
An Extensible Authentication Protocol (EAP) Authentication procedure is initiated. EAP messages are encapsulated into layer 2 packets.
Step 422: the TNAP sends an EAP request to the 5G-RG 401.
Step 423 a: the 5G-RG 401 provides a special Network Access Identifier (NAI) to the TNAP 403.
Step 423 b: the NAI triggers the TNAP 403 to send an authentication, authentication and accounting (AAA) request to the TNGF-CP 404, which TNGF-CP 404 operates as an AAA proxy. Between TNAP 403 and TNGF-CP 404, EAP packets are encapsulated into AAA messages.
Step 424: an EAP-request/5G-start packet is transmitted from the TNGF-CP 404. The EAP-request/5G-start packet informs the 5G-RG 401 to initiate an EAP-5G session.
Step 425: the 5G-RG 401 transmits AN EAP-response/5G-NAS packet containing Access Network (AN) parameters, a registration request message, and location information of the 5G-RG 401.
Step 426 a: the TNGF-CP 404 selects the AMF 405 based on the received AN parameters and local policy.
Step 426 b: the TNGF-CP 404 then forwards the registration request received from the RG to the selected AMF 405 within the N2 message.
Step 427 a: the selected AMF 405 may decide to request the RG identity by sending back a NAS identity request message.
Step 427 b: the NAS identity request message is forwarded back to the 5G-RG 401.
Step 428 a: the AMF 405 may decide to authenticate the 5G-RG 401 by calling an authentication server function (AUSF) 406. In this case, the AMF 405 may select the AUSF 406 based on a subscription permanent identifier (SUPI) or a subscription hidden identifier (SUCI).
Step 428 b: the AUSF 406 performs authentication of the 5G-RG 401. The authentication packet is encapsulated within a non-access stratum (NAS) authentication message, which is encapsulated within an EAP/5G-NAS packet.
Step 428 c: the AUSP 406 sends an AAA key response indicating that the EAP was successful.
Step 428 d: the TNGF key is created.
Step 429 a: the AMF 405 may send a NAS security mode command to the 5G-RG 401 to activate NAS security.
Step 429 b: the TNGF-CP 404 may forward the NAS security mode command message to the 5G-RG 401 within the EAP/5G-NAS packet.
Step 429 c: the 5G-RG 401 completes the authentication (if initiated in step 428) and sends a NAS security mode complete message within the EAP/5G-NAS packet. In some embodiments, the EAP/5G-NAS packet includes location information of the 5G-RG 401.
Step 429 d: TNGF-CP 404 passes the NAS security mode complete message to AMF 405.
Step 430 a: upon receiving NAS security mode completion, the AMF 405 may send an NGAP initial context setup request message including the TNGF key.
Step 430 b: TNGF-CP 404 is triggered to send EAP-success to 5G-RG 401.
Step 430 c: the EAP-5G session is complete.
Step 431: the public TNGF key is used by the 5G-RG 401 and TNAP 403 to derive security keys specific to the applied non-3GPP technology and to establish security associations to protect all subsequent traffic.
Step 432: the 5G-RG 401 receives the IP configuration from the TNAN 402, for example using DHCP.
Step 433: at this point, the 5G-RG 401 has successfully connected to the TNAN 402 and has obtained an IP configuration. The 5G-RG 401 establishes NWt-cp connections. Note that NWt is the reference point between the UE/RG and TNGF. This reference point implements two interfaces: a control plane interface called NWt-CP (which terminates at TNGF-CP), a user plane interface called NWt-UP (which terminates at TNGF-UP). The NWt-cp interface is used to convey NAS signaling. The TNGF transparently relays NAS messages between the NWt-cp interface and the associated N2 connection. The NWt-up interface is used to transfer user plane PDU data between the UE/RG and the TNGF. The TNGF transparently relays PDU data between the NWt-up interface and the associated N3 connection.
Step 434: after the NWt-CP connection is successfully established, the TNGF-CP 404 responds to the AMF 405 with an N2 initial context setup response message.
Step 435 a: the AMF 405 transmits a NAS registration accept message.
Step 435 b: the NAS registration accept message is relayed to the 5G-RG 401 over the established NWt-cp connection.
Example 2
In some embodiments, the 5G-RG/FN-RG provides W-5GAN with its location information in Protocol Data Unit (PDU) session management. Fig. 5 illustrates an example procedure for PDU session management between the 5G-RG and the TNAN in accordance with one or more embodiments of the present technology.
Steps 521 through 527 of fig. 5 illustrate an example PDU session setup procedure. After the 5G-RG completes registration with the 5GC, the 5G-RG establishes a connection with the TNAN to send the NAS message.
Step 521: the 5G-RG 501 initiates a PDU session setup procedure by sending a PDU session setup request to TNGF 504 of TNAN 502. TNAN 502 also includes TNAP 503.
Step 522 a: TNGF 504 forwards the PDU session setup request to AMF 505.
Step 522 b: TNGF 504 receives a PDU session setup accept from AMF 505.
Step 523: TNGF 504 requests location information of the RG in an NWt UP connection setup request message.
Step 524: quality of Service (QoS) resources may be reserved in TNAN 502 if supported.
Step 525: the 5G-RG 501 provides its location information in an NWt UP connection setup response message.
Step 526: TNGF 504 sends a PDU session setup accept to 5G-RG 501.
Step 527: TNGF 504 also sends a PDU session request acknowledgement to AMF 505.
User plane traffic 510 is then sent between the 5G-RG 501 and the User Plane Function (UPF) 506.
Steps 528 to 533 of fig. 5 illustrate an example PDU session modification procedure. The location information of the RG can also be retrieved by the network during the PDU session modification procedure.
Step 528: the 5G-RG 501 initiates a PDU session modification procedure by sending a PDU session modification request to TNGF 504. TNGF 504 forwards the PDU session modification request to AMF 505.
Step 529: AMF 505 sends a PDU session modification command to TNGF 504, which is then relayed to 5G-RG 501.
Step 530: after receiving the PDU session modify command from the core network, TNGF 401 requests the location information of 5G-RG 501 in an Nwt UP connection modify request.
Step 531: quality of service (QoS) resources may be modified if supported.
Step 532: the 5G-RG 501 provides its location information to TNGF 504 in an NWt UP connection modification response.
Step 533: the 5G-RG 501 sends a PDU session modify command acknowledgement, which is relayed to the AMF 505. The PDU session modification procedure is then completed.
Steps 534 through 539 of fig. 5 illustrate an example PDU session release procedure. The location information of the RG can also be retrieved by the network during the PDU session release procedure.
Step 534: the 5G-RG initiates a PDU session release by sending a PDU session release request to TNGF 504. TNGF 504 forwards the PDU session release request to AMF 505.
Step 535: AMF 505 sends a PDU session release command to TNGF 504, which is then relayed to 5G-RG 501.
Step 536: after receiving the PDU session release command from the core network, TNGF 401 requests the location information of 5G-RG 501 in an NWt UP connection modify/release request.
Step 537: quality of service (QoS) resources may be modified if supported.
Step 538: the 5G-RG 501 provides TNGF 504 with its location information in an NWt UP connection modify/release response.
Step 539: the 5G-RG 501 transmits a PDU session release command acknowledgement, which is relayed to the AMF 505. The PDU session release procedure is then completed.
Example 3
In some embodiments, when using IPsec for NAS delivery and uplink data delivery, the 5G-RG/FN-RG provides W-5GAN with its location information. Fig. 6 illustrates an example process of using IPsec for NAS delivery in accordance with one or more embodiments of the present technology.
Step 621 a: 5G-RG 601 initiates an Internet Key Exchange (IKE) initiation (IKE INIT) exchange with TNGF 604 of TNAN 502. TNAN 602 also includes TNAP 603.
Step 621 b: subsequently, the 5G-RG 601 initiates the IKE AUTH exchange and provides its SUPI or 5G Globally Unique Temporary Identifier (GUTI). The 5G-RG 501 may include 5G-RG location information in the IKE AUTH request message. The public TNGF key is used for mutual authentication (611).
Step 621 c: negotiate NULL encryption and establish an IPsec Security Association (SA) between 5G-RG 601 and TNGF 604.
Step 622: TNGF 604 sends an initial context response to AMF 605.
Step 623 a: AMF 605 sends a NAS registration accept to TNGF 604.
Step 623 b: the NAS registration acceptance is relayed to the 5G-RG 601.
The IPsec SA (612) is used to pass all subsequent NAS messages. This IPsec SA does not apply encryption but integrity protection may be applied.
Step 624: the 5G-RG 601 initiates the PDU session setup procedure by sending a PDU session setup request to the TNGF 604. The TNGF 604 forwards the PDU session setup request to the AMF 605.
Step 625: the TNGF 604 receives the PDU session setup accept from the AMF 605.
Step 626 a: if the 5G-RG location information needs to be retrieved, the TNGF 604 may include an IKE notification payload in the IKE _ Create _ Child _ SA request message indicating the 5G-RG location information request.
Step 626 b: QoS resources may be reserved in the TNAN 602 if supported by TNAN technology.
Step 626 c: the 5G-RG 601 may include an IKE notification payload indicating 5G-RG location information in an IKE _ Create _ Child _ SA response message.
Step 627: TNGF 604 sends a PDU session setup accept to 5G-RG 601.
Step 628: the TNGF 604 also transmits a PDU session request acknowledgement to the AMF 605.
Step 629: the PDU session data is encapsulated into Generic Routing Encapsulation (GRE) and then encapsulated into Security Payload (ESP)/IP.
Example 4
In some embodiments, the access network may establish an association between the UE and the RG when the UE registers with the core network. Fig. 7 illustrates an example registration procedure of a 5G-capable UE via a 5G-RG in accordance with one or more embodiments of the present technology.
Step 721 a: the UE 707 connects to an untrusted non-3GPP access network through a procedure outside the scope of 3GPP and is assigned an IP address.
Step 721: when the UE 707 decides to connect to the 5GC network, the UE selects the W-5GAN 702. The W-5GAN 702 includes an IPsec endpoint 703.
Step 722 a: the UE 707 continues to establish an IPsec Security Association (SA) with the selected W-5GAN 702 by initiating an IKE initial exchange.
Step 722 b: the W-5GAN establishes an association between the 5G-RG 701 and the 5G capable UE 707. The W-5GAN is also capable of determining location information of the UE 707 based on the location information of the 5G-RG. The W-5GAN may provide the 5G core with location information of the UE 707.
Step 723: the UE 707 initiates an IKE _ AUTH exchange by sending an IKE _ AUTH request message to the 5GAN 702.
Step 724: the W-5GAN 702 responds with an IKE _ AUTH response message that includes an EAP-request/5G-start packet. The EAP-request/5G-start packet informs the UE 707 to initiate an EAP-5G session, i.e., to start sending NAS messages encapsulated within EAP-5G packets.
Step 725: the UE 707 sends AN IKE AUTH request that includes AN EAP-response/5G-NAS packet containing AN parameter and a registration request message. The AN parameters include information used by the W-5GAN 702 to select AN AMF in the 5G core network.
Step 726 a: the W-5GAN 702 selects the AMF 705 based on the received AN parameters and local policy.
Step 726 b: the W-5GAN 702 then forwards the registration request received from the UE 707 to the selected AMF 705 within an N2 message.
Step 727: the selected AMF 705 may decide to request SUCI by sending a NAS identity request message to the UE 707. This NAS message and all subsequent NAS messages encapsulated within the EAP/5G-NAS packet are sent to the UE 707.
Steps 728 a-g: the AMF 705 may decide to authenticate the UE 707 by invoking the AUSF 706. In this case, AMF 705 selects AUSF 706 based on SUPI or SUCI. The AUSF 706 performs authentication of the UE 707. The authentication packet is encapsulated within a NAS authentication message, which is encapsulated within an EAP/5G-NAS packet.
Step 729 a: the AMF 705 sends a NAS security mode command to the UE 707 to activate NAS security.
Step 729 b: the W-5GAN 702 forwards the NAS security mode command message to the UE 707 within the EAP/5G-NAS packet.
Step 729 c: the UE 707 creates a NAS security context and sends a NAS security mode complete message within the EAP/5G-NAS packet.
Step 729 d: the W-5GAN passes the NAS Security mode complete message to the AMF 705.
Step 730 a: upon receiving the NAS security mode completion, the AMF 705 sends an NGAP initial context setup request message.
Step 730 b: the request message triggers the W-5GAN to send an EAP-success to the UE 707, which completes the EAP-5G session.
Step 731 a: an IPsec SA is established between the UE and the 5GAN by using the public key.
Step 731 b: after establishing the signaling IPsec SA, the W-5GAN 702 informs the AMF 705 of the UE context.
Step 732: the AMF 705 sends a NAS registration accept message to the W-5GAN 702.
Step 733: the W-5GAN 702 forwards the NAS registration acceptance to the UE 707 via the established signaling IPsec SA.
In this scenario, all packets from/to the 5G-capable UE through the RG are delivered over the Nwt-up connection between the RG and the 5 GAN. As previously described, the Nwt-up connection is established for 5G-RG user plane traffic transfer between the 5G-RG and the W-5 GAN. Based on the Nwt-up connection information, the W-5GAN can know to which 5G-RG a 5G-capable UE is connecting. The W-5GAN can then determine the location of the 5G capable UE by associating the 5G-RG (e.g., in step 2 b) and provide the location of the 5G capable UE to the 5G core network.
Example 5
Fig. 8 illustrates an example procedure for a 5G-capable UE to access a network via a 5G-RG using IEEE 802.1x with 3GPP credentials in accordance with one or more embodiments of the present technology.
The registration procedure shown in fig. 4 may be used for the case where 5G-RG acts as TNAP and W-5GAN acts as TNGF. In some embodiments, the W-5GAN 802 comprises an IPsec endpoint 803.
Step 821: a second layer (L2) connection 811 is established between the UE 807 and the 5G-RG 801.
An Extensible Authentication Protocol (EAP) Authentication procedure is initiated. EAP messages are encapsulated into layer 2 packets.
Step 822: the 5G-RG 801 sends an EAP request to the UE 807.
Step 823 a: the UE 807 provides a special Network Access Identifier (NAI) to the RG-RG 801. The NAI triggers the 5G-RG 801 to send an authentication, authorization, and accounting (AAA) request to the W-5GAN 802, which W-5GAN 802 operates as an AAA proxy.
Step 823 b: based on the received UE identity, the W-5GAN 802 may establish an association between the 5G capable UE 807 and the RG 801 to which the UE is connected.
Step 824: an EAP-request/5G-start packet is sent from the W-5GAN 802. The EAP-request/5G-start packet informs UE 807 to initiate an EAP-5G session.
Step 825: UE 807 sends AN EAP response/5G-NAS packet containing Access Network (AN) parameters and a registration request message.
Step 826 a: the W-5GAN 802 selects the AMF 805 based on the received AN parameters and local policy.
Step 826 b: the W-5GAN 802 then forwards the registration request received from the RG to the selected AMF 405 within an N2 message.
Step 827 a: the selected AMF 805 may decide to request the UE identity by sending back a NAS identity request message.
Step 827 b: the NAS identity request message is forwarded back to UE 807.
Step 828 a: AMF 405 may decide to authenticate UE 807 by invoking authentication server function (AUSF) 806. In this case, the AMF 805 may select the AUSF 806 based on a subscription permanent identifier (SUPI) or subscription hidden identifier (SUCI).
Step 828 b: the AUSF 806 performs authentication of the UE 807. The authentication packet is encapsulated within a non-access stratum (NAS) authentication message, which is encapsulated within an EAP/5G-NAS packet.
Step 828 c: the AUSP 806 sends an AAA key response indicating EAP success.
Step 828 d: a key is created.
Step 829 a: AMF 805 may send a NAS security mode command to UE 807 to activate NAS security.
Step 829 b: the 2-5GAN 802 may forward the NAS security mode command message to the UE 807 within the EAP/5G-NAS packet.
Step 829 c: the UE 807 completes authentication (if initiated in step 828) and sends a NAS security mode complete message within the EAP/5G-NAS packet.
Step 829 d: the W-5GAN 802 passes the NAS security mode complete message to the AMF 805.
Step 830 a: upon receiving NAS security mode completion, AMF 805 may send an NGAP initial context setup request message including a key.
Step 830 b: the W-5GAN 802 is triggered to send an EAP success to the UE 807.
Step 830 c: the EAP-5G session is complete.
Step 831: public keys are used by UE 807 and W-5GAN 802 to derive security keys specific to the non-3GPP technology being applied and to establish security associations to protect all subsequent traffic.
Step 832: UE 807 receives the IP configuration from 5GAN 802, for example, using DHCP.
Step 833: at this point, the UE 807 has successfully connected to the W-5GAN 802, and has obtained an IP configuration.
Step 834: the W-5GAN 802 responds to the AMF 805 with an N2 initial context setup response message.
Step 835 a: the AMF 805 sends a NAS registration accept message.
Step 835 b: the NAS registration accept message is relayed to UE 807.
Example 6
Fig. 9 illustrates an example process of receiving location information for a 5G-capable UE over a 5G core network in accordance with one or more embodiments of the present technology.
Step 921: the AMF 905 transmits a message (e.g., an N2 signaling message) to the W-5GAN 902 to request location information of the 5G capable UE 907.
Step 922: the W-5GAN 902 identifies an RG to which the 5G capable UE 907 is connected. In some embodiments, the W-5GAN 902 stores the association between the RG 901 and the UE 907 locally. The W-5GAN may proceed directly to step 925 to provide location information for the UE 907. In some embodiments, the W-5GAN needs to request location information from the RG 901.
Step 923: the 5GAN 902 sends a message to the identified RG 901 to request location information of the RG.
Step 924: the RG 901 responds to the W-5GAN 902 with its location information. This location provision is performed by the IKEv2 information exchange procedure when the control plane connection between the RG (e.g., 5G-RG and/or FN-RG) and the W-5GAN is IPSec SA.
Step 925: the W-5GAN 902 transmits the location information of the RG to the core network as the location information of the UE 907 having the 5G function.
Fig. 13 illustrates an example of a wireless communication system 1300 in which techniques in accordance with one or more embodiments of the present technology may be applied. The wireless communication system 1300 may include one or more Base Stations (BSs) 1305a, 1305b, one or more wireless devices 1310a, 1310b, 1310c, 1310d, and a core network 1325. Base stations 1305a, 1305b may provide wireless service to wireless devices 1310a, 1310b, 1310c, and 1310d in one or more wireless sectors. In some embodiments, the base stations 1305a, 1305b include directional antennas to generate two or more directional beams to provide wireless coverage in different sectors.
The core network 1325 may communicate with one or more base stations 1305a, 1305 b. The core network 1325 provides connectivity to other wireless and wireline communication systems. The core network may include one or more service subscription databases to store information related to the subscribed wireless devices 1310a, 1310b, 1310c, and 1310 d. The first base station 1305a may provide wireless service based on a first radio access technology, and the second base station 1305b may provide wireless service based on a second radio access technology. The base stations 1305a and 1305b may be quasi-collocated, or may be installed separately in the field, depending on the deployment scenario. The wireless devices 1310a, 1310b, 1310c, and 1310d may support a plurality of different radio access technologies.
In some embodiments, a wireless communication system may include multiple networks using different wireless technologies. A dual-mode or multi-mode wireless device includes two or more wireless technologies that may be used to connect different wireless networks.
Fig. 14 is a block diagram representation of a portion of a radio station. A radio station 1405, such as a base station or a wireless device (or UE), may include processor electronics 1410, such as a microprocessor, that implement one or more of the radio technologies presented in this document. The radio station 1405 may include transceiver electronics 1415 to transmit and/or receive wireless signals over one or more communication interfaces, such as antenna 1420. The radio station 1405 may include other communication interfaces for transmitting and receiving data. The radio station 1405 may include one or more memories (not explicitly shown) configured to store information, such as data and/or instructions. In some implementations, the processor electronics 1410 may include at least a portion of the transceiver electronics 1415. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using a radio station 1405.
It should be appreciated that this document discloses techniques that may be embodied in a wireless communication system to report location information for UEs connected to a network via a residential gateway that supports 3GPP and/or non-3GPP network access technologies in assisting with transmission and measurement of UEs. Using the techniques disclosed herein, the location information of the residential gateway can be used to represent the location information of the UE, thereby solving the problems caused by the UE not knowing the network access technology used for the connection.
In one example aspect, a method for wireless communication is disclosed. The method includes receiving, at an access network, a first message from a residential gateway that supports a first network access technology and optionally a second network access technology. The residential gateway is configured to provide an access connection to a mobile device operating using a first network access technology. The first message includes location information of the residential gateway indicating location information of the mobile device. The method also includes sending a second message including the received location information from the access network to the core network.
In some embodiments, the location information of the residential gateway includes one or more of: a service set identifier of the mobile device, a basic service set identifier of the residential gateway, a homogeneous extended service set identifier of the residential gateway, a civic address of the residential gateway, a line identifier, a geographical location, or identifier information of the access network.
In some embodiments, the location information of the residential gateway is included in an extensible authentication protocol packet. In some embodiments, the first message comprises a response message to create, modify or release an NWt connection between the residential gateway and the access network. In some embodiments, the first message comprises an authentication request message for Internet Key Exchange (IKE). In some embodiments, the first message comprises a response message to create a Security Association (SA) for an Internet Key Exchange (IKE). The response message for creating a Security Association (SA) for Internet Key Exchange (IKE) may include an IKE payload for indicating location information of the residential gateway.
In some embodiments, the access network comprises a trusted non-3GPP access network. For example, the access network may comprise a wired access network (e.g., W-5 GAN). In some embodiments, the residential gateway comprises a residential gateway (e.g., 5G-RG) that supports N1 (interface) signaling with a core network. In some embodiments, the residential gateway comprises a residential gateway (e.g., FN-RG) that does not support N1 (interface) signaling with the core network.
In some embodiments, the method includes sending, by the access network, a third message to the residential gateway requesting location information of the residential gateway. In some embodiments, the third message comprises a request message to create, modify, or release an NWt connection between the residential gateway and the access network. In some embodiments, the third message comprises a request message to create a Security Association (SA) for an Internet Key Exchange (IKE). The request message for creating a Security Association (SA) for Internet Key Exchange (IKE) may include an IKE payload for requesting location information of the residential gateway.
In some embodiments, the method includes receiving, at the access network, a fourth message from the core network requesting location information of the mobile device. The access network may identify a residential gateway that provides access connectivity to the mobile device. The method also includes determining, by the access network, location information of the mobile device based on the location information of the identified residential gateway. In some embodiments, the fourth message comprises a signaling message over an N2 interface.
In some embodiments, the method includes receiving, by the access network, a fifth message from the mobile device via the residential gateway; and establishing, by the access network, an association between the mobile device and the residential gateway. In some embodiments, the fifth message includes an identifier of the mobile device. In some embodiments, the association between the mobile device and the residential gateway may be used by the access network to identify the residential gateway for subsequent transmission.
In another example aspect, a method for wireless communication is disclosed. The method includes sending, by a residential gateway that supports a first network access technology and optionally a second network access technology, a first message including location information of the residential gateway to an access network. The residential gateway is configured to provide an access connection to a mobile device operating using a first network access technology. The location information of the residential gateway indicates location information of the mobile device.
In some embodiments, the location information of the residential gateway includes one or more of: a service set identifier of the mobile device, a basic service set identifier of the residential gateway, a homogeneous extended service set identifier of the residential gateway, a civic address of the residential gateway, a line identifier, a geographical location, or identifier information of the access network.
In some embodiments, the location information of the residential gateway is included in an extensible authentication protocol packet. In some embodiments, the first message comprises a response message to create, modify or release an NWt connection between the residential gateway and the access network. In some embodiments, the first message comprises an authentication request message for Internet Key Exchange (IKE). In some embodiments, the first message comprises a response message to create a Security Association (SA) for an Internet Key Exchange (IKE). The response message for creating a Security Association (SA) for Internet Key Exchange (IKE) may include an IKE payload for indicating location information of the residential gateway.
In some embodiments, the access network comprises a trusted non-3GPP access network. For example, the access network includes a wired access network (e.g., W-5 GAN). In some embodiments, the residential gateway comprises a residential gateway (e.g., 5G-RG) that supports N1 (interface) signaling with a core network. In some embodiments, the residential gateway comprises a residential gateway (e.g., FN-RG) that does not support N1 (interface) signaling with the core network.
In some embodiments, the method includes receiving, by the residential gateway from the access network, a second message requesting location information of the residential gateway. In some embodiments, the second message comprises a request message for creating, modifying, or releasing an NWt connection between the residential gateway and the access network. In some embodiments, the second message comprises a request message for creating a Security Association (SA) for an Internet Key Exchange (IKE). The request message for creating a Security Association (SA) for Internet Key Exchange (IKE) may include an IKE payload for requesting location information of the residential gateway.
The disclosed and other embodiments, modules, and functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more of them. The term "data processing apparatus" includes all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. The propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
A computer program (also known as a program, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store portions of one or more modules, sub programs, or code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
The processes and logic flows described herein can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer does not require such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks (e.g., internal hard disks or removable disks); magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
While this patent document contains many specifics, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.
Only a few embodiments and examples are described and other embodiments, enhancements and variations can be made based on what is described and shown in this patent document.