Support of premises radio access station integration with wired residential gateway

Abstract

Embodiments of the present disclosure relate to a method, apparatus, and non-transitory computer readable medium for supporting a premises radio access station integrated with a wired residential gateway. The device may cross-connect sessions for the user equipment from a premises radio access station integrated with the network device over the network, and may authenticate the user equipment based on the sessions. The device may authorize the user equipment to make a session and may provide one or more services to the user equipment as an independent subscriber via the session and a premises radio access station integrated with the network device.

Description

Background Art

[0001] A Premises Radio Access Station (PRAS) is a small indoor base station that is externally connected to a network device (such as a fixed network residential gateway) and supports wireless communications for a user equipment (UE) (eg, located indoors). Summary of the invention

[0002] Some implementations described herein relate to a method. The method may include cross-connecting a session for a UE from a PRAS integrated with a network device using a network address, and authenticating the UE based on the session. The method may include authorizing the UE for the session, and providing one or more services to the UE as an independent subscriber via the session and the PRAS integrated with the network device.

[0003] Some implementations described herein relate to devices that may include one or more memories and one or more processors. One or more processors may be configured to utilize a network address to cross-connect a session for a UE from a PRAS integrated with a network device, wherein the PRAS is integrated with the network device via hardware or hardware connection. One or more processors may be configured to authenticate the UE based on the session and authorize the UE for the session. One or more processors may be configured to provide one or more services to a UE as an independent subscriber via a session and a PRAS integrated with a network device.

[0004] Some implementations described herein relate to a non-transitory computer-readable medium storing an instruction set. The instruction set, when executed by one or more processors of a device, may cause the device to cross-connect a session for a UE from a PRAS integrated with a network device using a network address, and authenticate the UE based on the session. The instruction set, when executed by one or more processors of the device, may cause the device to authorize the UE for the session, and provide one or more services to the UE as an independent subscriber via the session and the PRAS integrated with a residential gateway. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figures 1A to 1D is an illustration of an example associated with supporting a PRAS integrated with a wired residential gateway.

[0006] Figure 2 is an illustration of an example environment in which the systems and / or methods described herein may be implemented.

[0007] Figure 3 and Figure 4 yes Figure 2 An illustration of example components of one or more devices.

[0008] Figure 5 is a flow chart of an example process for supporting a PRAS integrated with a wired residential gateway. DETAILED DESCRIPTION

[0009] The following detailed description of example implementations refers to the accompanying drawings.The same reference numbers in different drawings may identify the same or similar elements.

[0010] Currently, PRAS is externally connected to a fixed network residential gateway, which results in PRAS being located behind the residential gateway. Since PRAS is located behind the residential gateway, the network address translation (NAT) deployed on the customer premises equipment (CPE) results in many restrictions being imposed on PRAS. For example, when PRAS is idle, a short message service (SMS) or text message triggered from the fifth generation (5G) core network cannot pass through the residential gateway due to NAT. In addition, NAT creates other complex issues (e.g., bandwidth sharing, double billing, etc.) for the current configuration of PRAS and residential gateways, because NAT only works on signaling received by PRAS from UE.

[0011] Therefore, the current configuration of PRAS and residential gateway consumes computing resources (e.g., processing resources, memory resources, communication resources, etc.), network resources and / or other resources associated with the following: failure to provide services from the core network to UEs communicating with PRAS, providing a poor user experience for UEs attempting to access services from the core network, processing lost services for UEs attempting to access services from the core network, attempting to recover lost services, etc.

[0012] Some implementations described herein provide a device (e.g., AGF) that supports a PRAS integrated with a wired residential gateway. For example, the AGF can cross-connect a session for a UE from a PRAS integrated with a residential gateway using a network address, and can authenticate the UE based on the session. The AGF can authorize the UE for a session, and can provide one or more services to a UE as an independent subscriber via a session and the PRAS integrated with a residential gateway. The AGF can receive a request from the PRAS integrated with a residential gateway for reestablishing a UE call or UE connection that is switched to the PRAS integrated with a residential gateway, and can reestablish a call or connection based on the request. The AGF can receive a wake-up service for the UE from the core network, and can provide a wake-up service to the PRAS integrated with a residential gateway. The PRAS integrated with a residential gateway can provide a wake-up service to the UE.

[0013] In this way, AGF supports PRAS integrated with wired residential gateway. For example, AGF can communicate with PRAS physically integrated with residential gateway. PRAS can cross-connect UE sessions from PRAS to AGF using network addresses (e.g., wide area network (WAN) Internet Protocol (IP) addresses). AGF can operate in direct mode (e.g., it supports core network) to authenticate, authorize and provide services to UE connected to PRAS as independent subscribers. Therefore, AGF can save computing resources, network resources and / or other resources that would otherwise be consumed for the following reasons: failure to provide services from the core network to UE communicating with PRAS, providing poor user experience for UE attempting to access services from the core network, processing lost services for UE attempting to access services from the core network, attempting to recover lost services, etc.

[0014] Figures 1A to 1D is a diagram of an example 100 associated with supporting a PRAS integrated with a wired residential gateway. Figures 1A to 1D As shown in , example 100 includes a UE, a radio access network (RAN), a PRAS, a network device, and a core network with an AGF and a user plane function (UPF). Other details of the UE, RAN, PRAS, network device, core network, AG, and UPF are provided elsewhere in this document. Although Figure 1A Only one UE is depicted in the figure, but in some implementations, there may be more than one UE 205 associated with the RAN, PRAS, network equipment, core network, AGF and UPF. In addition, although the implementation described herein relates to AGF, in some implementations, a broadband network gateway (BNG) may be utilized instead of AGF.

[0015] like Figure 1A As shown in , the PRAS can be connected to a network device (e.g., a residential gateway) via a physical link. In some implementations, the PRAS can be physically integrated with the network device via hardware or via a wired (e.g., Universal Serial Bus (USB)) connection. In this way, the PRAS will not be externally connected behind the network device and will not be subject to the limitations caused by NAT. Figure 1A As further shown in , the UE can be connected to the core network via the RAN and UPF. Alternatively or additionally, if the UE is located indoors (eg, close to the PRAS and network equipment), the UE can be connected to the core network via the PRAS, network equipment and AGF.

[0016] like Figure 1AAnd as further shown by reference numeral 105, the AGF can utilize a network address to cross-connect a session (e.g., for a UE) from the PRAS to the AGF. For example, the PRAS and the AGF can utilize a network address to cross-connect a session (e.g., for a UE) from the PRAS and a network device to the AGF. In some implementations, the network address can include a WAN IP address associated with the PRAS.

[0017] like Figure 1B And as shown by reference numeral 110, the AGF can authenticate, authorize and provide services to a UE connected to the PRAS as an independent subscriber via direct mode. For example, the UE can provide a request for a session to the PRAS integrated with the network device, and the PRAS integrated with the network device can provide the request to the AGF. The AGF can receive the request for the session and can authenticate the UE based on the session. In some implementations, the AGF can authenticate the UE by determining whether the UE has the right to use the session (e.g., provided by the core network). If the AGF determines that the UE has the right to use the session, the AGF can authenticate the UE. Alternatively, if the AGF determines that the UE does not have the right to use the session, the AGF may not authenticate the UE.

[0018] When the AGF authenticates the UE, the AG may determine whether the UE is authorized for the session based on the account associated with the UE, the type of UE, etc. In some implementations, if the AGF determines that the UE is authorized for the session, the AGF may authorize the UE for the session. Alternatively, if the AGF determines that the UE is not authorized for the session, the AGF does not authorize the UE for the session. When the AGF authorizes the UE for the session, the AGF may provide one or more services to the UE via the session. In some implementations, the AGF may provide one or more services to a PRAS integrated with a network device, and the PRAS integrated with a network device may provide one or more services to a UE as an independent subscriber.

[0019] like Figure 1C And as indicated by reference numeral 115, the AGF may receive a wake-up service for the UE from the core network. For example, the AGF and / or the network device may be associated with physical location information, which may be utilized by the core network to provide services to the UE (e.g., because the location information may indicate the location of the UE). In some implementations, the core network may utilize the location information to provide one or more wake-up services to the UE. The wake-up service may include a short message service (SMS), an emergency service, a service provided to the UE by the core network via a PRAS integrated with the network device, and the like. The core network may provide the wake-up service to the AGF, and the AGF may receive the wake-up service from the core network based on the location information associated with the AGF and / or the network device.

[0020] like Figure 1C As further shown by reference numeral 120, the AGF may provide a wake-up service to the UE via the PRAS and the network device based on the location of the AGF and the network device. For example, after receiving the wake-up service based on the location information, the AGF may provide the wake-up service to the PRAS integrated with the network device. The PRAS integrated with the network device may receive the wake-up service from the AGF.

[0021] like Figure 1C As further shown by reference numeral 125, the PRAS and the network device may provide a wake-up service to the UE. For example, after receiving the wake-up service, the PRAS integrated with the network device may provide the wake-up service to the UE. The UE may receive the wake-up service and may display the wake-up service to a user of the UE.

[0022] like Figure 1D And as indicated by reference numeral 130, the UE may establish a call or connection with the core network via the RAN. For example, when the UE is located far away from the premises (e.g., when the signal strength of the RAN is stronger than the signal strength of the PRAS), the UE may establish a call or connection with the core network via the RAN (e.g., for receiving services).

[0023] like Figure 1D As further indicated by reference numeral 135, the UE may hand over the call or connection to the PRAS. For example, when the UE is located near or inside a premises (e.g., when the signal strength of the PRAS is stronger than the signal strength of the RAN), the UE may hand over the call or connection to the PRAS integrated with the network device. In some implementations, when the UE is located near or inside a premises, the PRAS integrated with the network device may receive a request from the UE to handle the call or connection.

[0024] like Figure 1D And as further shown by reference numeral 140, the AGF may receive a call or connection and may re-establish a call or connection for the UE. For example, a PRAS integrated with a network device may provide a request for processing a call or connection to the AGF, and the AGF may receive a request for processing a call or connection from a PRAS integrated with a network device. Based on the request for processing the call or connection, the AGF may attempt to re-establish a call or connection with the core network (e.g., for the UE). In some implementations, the attempt to re-establish a call or connection with the core network (e.g., for the UE) may be successful. Alternatively, the attempt to re-establish a call or connection with the core network (e.g., for the UE) may be unsuccessful, and the call or connection may be dropped.

[0025] like Figure 1DAs further shown by reference numeral 145, the AGF may establish a call or connection with the core network. For example, when an attempt to reestablish a call or connection with the core network (e.g., for the UE) is successful, the AGF may establish a call or connection with the core network (e.g., for the UE). The UE may then continue the call or connection with the core network.

[0026] In this way, AGF supports PRAS integrated with wired residential gateway. For example, AGF can communicate with PRAS physically integrated with residential gateway. PRAS can cross-connect UE session from PRAS to AGF using network address. AGF can operate in direct mode to authenticate, authorize and provide services to UE connected to PRAS as independent subscribers. Therefore, AGF can save computing resources, network resources and / or other resources, which would otherwise be consumed for the following reasons: failure to provide services to UE communicating with PRAS from core network, providing poor user experience for UE trying to access service from core network, processing lost business for UE trying to access service from core network, attempting to recover lost business, etc.

[0027] As indicated above, provide Figures 1A to 1D As an example. Other examples can be related to Figures 1A to 1D Different than described. Figures 1A to 1D The number and arrangement of the devices shown in are provided as examples. Figures 1A to 1D There may be additional devices, fewer devices, different devices, or devices arranged differently than those shown. Figures 1A to 1D Two or more of the devices shown in FIG. 1 may be implemented in a single device, or in Figures 1A to 1D The single device shown in can be implemented as multiple distributed devices. Additionally or alternatively, in Figures 1A to 1D The device collection (e.g., one or more devices) shown in FIG. 1 may perform the operations described by Figures 1A to 1D One or more functions performed by another set of devices shown in .

[0028] Figure 2 2 is an illustration of an example environment 200 in which the systems and / or methods described herein may be implemented. Figure 2 As shown in FIG, example environment 200 may include UE 205, RAN 210, core network 215, PRAS 220, network device 225, and data network 280. Devices and / or networks of example environment 200 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0029] UE 205 may include one or more devices capable of receiving, generating, storing, processing, and / or providing information, as described elsewhere herein. UE 205 may include a communication device and / or a computing device. For example, UE 205 may include a wireless communication device, a mobile phone, a user device, a laptop computer, a tablet computer, a desktop computer, a game console, a set-top box, a wearable communication device (e.g., a smart watch, a pair of smart glasses, a head-mounted display, or a virtual reality headset), or a similar type of device.

[0030] The RAN 210 may support, for example, a cellular radio access technology (RAT). The RAN 210 may include one or more base stations (e.g., base transceiver stations, radio base stations, Node Bs, eNodeBs (eNBs), gNodeBs (gNBs), base station subsystems, cell sites, cell towers, access points, transmit receive points (TRPs), radio access nodes, macrocell base stations, microcell base stations, picocell base stations, femtocell base stations, or similar types of devices) and other network entities that may support wireless communications for the UE 205. The RAN 210 may transmit traffic between the UE 205 (e.g., using a cellular RAT), one or more base stations (e.g., using a wireless interface or a backhaul interface, such as a wired backhaul interface), and / or the core network 215. The RAN 210 may provide one or more cells covering a geographic area.

[0031] In some implementations, the RAN 210 may perform scheduling and / or resource management for UEs 205 covered by the RAN 210 (e.g., UEs 205 covered by cells provided by the RAN 210). In some implementations, the RAN 210 may be controlled or coordinated by a network controller, which may perform load balancing, network-level configuration, and / or other operations. The network controller may communicate with the RAN 210 via a wireless or wired backhaul. In some implementations, the RAN 210 may include a network controller, a self-organizing network (SON) module or component, or a similar module or component. In other words, the RAN 210 may perform network control, scheduling, and / or network management functions (e.g., for uplink, downlink, and / or sidelink communications for UEs 205 covered by the RAN 210).

[0032] PRAS 220 may support, for example, a cellular RAT, and may include a base station (e.g., a base transceiver station, a radio base station, an access point, a transmit receive point (TRP), a microcell base station, a picocell base station, a femtocell base station, or a similar type of device) that may support wireless communications for UE 205. In some implementations, PRAS 220 may include an indoor base station that connects UE 205 via a new radio wireless air interface. In some implementations, PRAS 220 is physically integrated with network device 225 via hardware or via a wired (e.g., Universal Serial Bus (USB)) connection.

[0033] The network device 225 may include one or more devices capable of receiving, processing, storing, routing and / or providing services (e.g., packets and / or other information or metadata) in a manner described herein. For example, the network device 225 may include a router, such as a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router (e.g., a provider edge router or a provider core router), a virtual router, or another type of router. Additionally or alternatively, the network device 225 may include a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a cloud server, or a data center server), a load balancer, and / or similar devices. In some implementations, the network device 225 may be a physical device implemented in a housing (such as a chassis). In some implementations, the network device 225 may be a virtual device implemented by one or more computing devices of a cloud computing environment or a data center. In some implementations, the network device group 225 may be a data center node group for routing traffic flows through the network. In some implementations, the network device 225 may include a residential gateway that provides, for example, voice, data, broadcast video, video on demand, etc. to other devices in the user's premises. In some implementations, the network device 225 may include a 5G residential gateway that can be connected to the core network 215 via fixed broadband access, wired access, etc.

[0034] In some implementations, the core network 215 may include an example functional architecture in which the systems and / or methods described herein may be implemented. For example, the core network 215 may include an example architecture of a 5G next generation (NG) core network included in a 5G wireless telecommunications system. Figure 2 The example architecture of the core network 215 shown in can be an example of a service-based architecture, but in some implementations, the core network 215 can be implemented as a reference point architecture and / or a 4G core network, among other examples.

[0035] like Figure 2As shown in , the core network 215 may include multiple functional elements. The functional elements may include, for example, a network slice selection function (NSSF) 230, an authentication server function (AUSF) 235, a unified data management (UDM) component 240, a policy control function (PCF) 245, an application function (AF) 250, an access and mobility management function (AMF) 255, a session management function (SMF) 260, a UPF 265, and / or an AGF 270. These functional elements may be communicatively connected via a message bus 275. Figure 2 Each of the functional elements shown in the embodiment is implemented on one or more devices associated with the wireless telecommunications system. In some implementations, one or more of the functional elements may be implemented on a physical device (such as an access point, a base station, and / or a gateway, etc.). In some implementations, one or more of the functional elements may be implemented on a computing device in a cloud computing environment.

[0036] NSSF 230 includes one or more devices that select a network slice instance for UE 205. By providing network slicing, NSSF 230 allows operators to potentially deploy multiple essentially independent end-to-end networks using the same infrastructure. In some implementations, each slice can be customized for different services.

[0037] The AUSF 235 includes one or more devices that act as an authentication server and support the process of authenticating the UE 205 in the wireless telecommunications system.

[0038] The UDM 240 includes one or more devices that store user data and profiles in a wireless telecommunications system. The UDM 240 may be used for fixed access and / or mobile access in the core network 215.

[0039] PCF 245 includes one or more devices that provide a policy framework that incorporates examples such as network slicing, roaming, packet processing, and / or mobility management.

[0040] AF 250 includes one or more devices that support application influence on traffic routing, access to network exposed functions, and / or policy control, among other examples.

[0041] The AMF 255 includes one or more devices that serve as termination points for, for example, non-access stratum (NAS) signaling and / or mobility management.

[0042] SMF 260 includes one or more devices that support establishing, modifying, and releasing communication sessions in a wireless telecommunications system. For example, SMF 260 can configure traffic steering policies at UPF 265 and / or can implement user equipment Internet Protocol (IP) address allocation and policies, among other examples.

[0043] The UPF 265 includes one or more devices that serve as an anchor point for intra-RAT and / or inter-RAT mobility. The UPF 265 may apply rules to packets, such as rules related to packet routing, service reporting, and / or handling user plane QoS, among other examples.

[0044] AGF 270 includes one or more devices that provide authentication, authorization, and accounting (AAA) services and hierarchical traffic shaping and supervision for fixed networks and 5G residential gateways (e.g., network device 225). Fixed networks and 5G residential gateways are served by UPF 265.

[0045] The message bus 275 represents a communication structure for communication between functional elements. In other words, the message bus 275 can allow communication between two or more functional elements.

[0046] Data network 280 includes one or more wired and / or wireless data networks. For example, data network 280 may include an Internet Protocol Multimedia Subsystem (IMS) network, a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a private network (such as a company intranet), an ad hoc network, the Internet, a fiber-based network, a cloud computing network, a third-party service network, an operator service network, and / or a combination of these or other types of networks.

[0047] Figure 2 The number and arrangement of devices and networks shown in the figure are provided as examples. In practice, there may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or different Figure 2 In addition, the devices and / or networks are arranged differently as shown in FIG. Figure 2 Two or more of the devices shown in may be implemented in a single device, or Figure 2 The single device shown in the example environment 200 may be implemented as multiple distributed devices. Additionally or alternatively, a set of devices (eg, one or more devices) of the example environment 200 may perform one or more functions described as being performed by another set of devices of the example environment 200.

[0048] Figure 32 is an illustration of example components of device 300, which components may correspond to UE 205, RAN 210, PRAS 220, network device 225, NSSF 230, AUSF 235, UDM 240, PCF 245, AF 250, AMF 255, SMF 260, UPF 265, and / or AGF 270. In some implementations, UE 205, RAN 210, PRAS 220, network device 225, NSSF 230, AUSF 235, UDM 240, PCF 245, AF 250, AMF 255, SMF 260, UPF 265, and / or AGF 270 may include one or more devices 300 and / or one or more components of device 300. Figure 3 As shown in , device 300 may include a bus 310 , a processor 320 , a memory 330 , an input component 340 , an output component 350 , and a communication component 360 .

[0049] The bus 310 includes one or more components that enable wired and / or wireless communication between components of the device 300. The bus 310 may be coupled, such as via an operational coupling, a communicative coupling, an electronic coupling, and / or an electrical coupling. Figure 3 Two or more components in are coupled together. Processor 320 includes a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field programmable gate array, an application-specific integrated circuit, and / or another type of processing component. Processor 320 is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor 320 includes one or more processors that can be programmed to perform one or more operations or processes described elsewhere in this document.

[0050] Memory 330 includes volatile and / or non-volatile memory. For example, memory 330 may include random access memory (RAM), read-only memory (ROM), hard disk drive and / or other types of memory (e.g., flash memory, magnetic memory and / or optical memory). Memory 330 may include internal memory (e.g., RAM, ROM or hard disk drive) and / or removable memory (e.g., removable via a universal serial bus connection). Memory 330 may be a non-transitory computer-readable medium. Memory 330 stores information, instructions and / or software (e.g., one or more software applications) related to the operation of device 300. In some implementations, memory 330 includes one or more memories such as coupled to one or more processors (e.g., processor 320) via bus 310.

[0051] Input component 340 enables device 300 to receive input (such as user input and / or sensed input). For example, input component 340 may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system sensor, an accelerometer, a gyroscope, and / or an actuator. Output component 350 enables device 300 to provide output such as via a display, a speaker, and / or a light emitting diode. Communication component 360 enables device 300 to communicate with other devices via a wired connection and / or a wireless connection. For example, communication component 360 may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and / or an antenna.

[0052] The device 300 may perform one or more operations or processes described herein. For example, a non-transitory computer-readable medium (e.g., memory 330) may store an instruction set (e.g., one or more instructions or codes) executed by a processor 320. The processor 320 may execute an instruction set to perform one or more operations or processes described herein. In some implementations, the execution of an instruction set by one or more processors 320 causes one or more processors 320 and / or the device 300 to perform one or more operations or processes described herein. In some implementations, hard-wired circuits may be used instead of instructions or in combination with instructions to perform one or more operations or processes described herein. Additionally or alternatively, the processor 320 may be configured to perform one or more operations or processes described herein. Therefore, the implementation described herein is not limited to any particular combination of hardware circuits and software.

[0053] Figure 3 The number and arrangement of components shown in FIG. 3 are provided as examples. Device 300 may include Figure 3 The components shown in the figure may be additional components, fewer components, different components, or components arranged differently. Additionally or alternatively, a set of components (e.g., one or more components) of the device 300 may perform one or more functions described as being performed by another set of components of the device 300.

[0054] Figure 4 4 is an illustration of example components of device 400 that may correspond to network device 225. In some implementations, network device 225 may include one or more devices 400 and / or one or more components of device 400. Figure 4 As shown in , the device 400 may include one or more input components 410-1 to 410-B (B≥1) (hereinafter collectively referred to as input component 410, and individually referred to as input component 410), a switching component 420, one or more output components 430-1 to 430-C (C≥1) (hereinafter collectively referred to as output component 430, and individually referred to as output component 430), and a controller 440.

[0055] The input component 410 may be one or more connection points for a physical link and may be one or more entry points for incoming traffic, such as packets. The input component 410 may process incoming traffic, such as by performing data link layer encapsulation or decapsulation. In some implementations, the input component 410 may send and / or receive packets. In some implementations, the input component 410 may include an input line card, which includes one or more packet processing components (e.g., in the form of an integrated circuit) (such as one or more interface cards (IFCs)), a packet forwarding component, a line card controller component, an input port, a processor, a memory, and / or an input queue. In some implementations, the device 400 may include one or more input components 410.

[0056] The switching component 420 can interconnect the input component 410 with the output component 430. In some implementations, the switching component 420 can be implemented via one or more crossbar switches, via a bus, and / or using a shared memory. The shared memory can be used as a temporary buffer to store packets from the input component 410 before the packets are ultimately scheduled for transmission to the output component 430. In some implementations, the switching component 420 can enable the input component 410, the output component 430, and / or the controller 440 to communicate with each other.

[0057] The output component 430 can store packets and can schedule packets for transmission on an output physical link. The output component 430 can support data link layer encapsulation or decapsulation, and / or various higher-level protocols. In some implementations, the output component 430 can send packets and / or receive packets. In some implementations, the output component 430 may include an output line card, which includes one or more packet processing components (e.g., in the form of an integrated circuit) (such as one or more IFCs), a packet forwarding component, a line card controller component, an output port, a processor, a memory and / or an output queue. In some implementations, the device 400 may include one or more output components 430. In some implementations, the input component 410 and the output component 430 can be implemented by the same component set (e.g., and the input / output component can be a combination of the input component 410 and the output component 430).

[0058] Controller 440 includes a processor in the form of, for example, a CPU, GPU, APU, microprocessor, microcontroller, DSP, FPGA, ASIC, and / or other types of processors. The processor is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, controller 440 may include one or more processors that can be programmed to perform a function.

[0059] In some implementations, controller 440 may include RAM, ROM, and / or another type of dynamic or static storage device (eg, flash memory, magnetic memory, optical memory, etc.) that stores information and / or instructions for use by controller 440 .

[0060] In some implementations, the controller 440 can communicate with other devices, networks, and / or systems connected to the device 400 to exchange information about the network topology. The controller 440 can create a routing table based on the network topology information, can create a forwarding table based on the routing table, and can forward the forwarding table to the input component 410 and / or the output component 430. The input component 410 and / or the output component 430 can use the forwarding table to perform a route lookup for incoming and / or outgoing packets.

[0061] The controller 440 may perform one or more processes described herein. The controller 440 may perform these processes in response to executing software instructions stored by a non-transitory computer readable medium. The computer readable medium is defined herein as a non-transitory memory device. The memory device includes a memory space within a single physical storage device or a memory space spread across multiple physical storage devices.

[0062] The software instructions may be read from another computer-readable medium or from another device into a memory and / or storage component associated with the controller 440 via a communication interface. When executed, the software instructions stored in the memory and / or storage component associated with the controller 440 may cause the controller 440 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Therefore, the implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0063] Figure 4 The number and arrangement of components shown in FIG. 4 are provided as examples. In practice, device 400 may include Figure 4 Components shown in the figure may be additional components, fewer components, different components, or differently arranged components than those shown in the figure. Additionally or alternatively, a component set (e.g., one or more components) of the device 400 may perform one or more functions described as being performed by another component set of the device 400.

[0064] Figure 5 is a flow chart of an example process 500 for supporting PRAS integrated with a wired residential gateway. In some implementations, Figure 5 One or more process blocks of may be performed by a device (e.g., AGF 270). In some implementations, Figure 5One or more process blocks of may be performed by another device, or a group of devices separate from or including the device, such as a PRAS (e.g., PRAS 220), a network device (e.g., network device 225), etc. Additionally or alternatively, Figure 5 One or more process blocks of may be performed by one or more components of device 300, such as processor 320, memory 330, input component 340, output component 350, and / or communication component 360. Additionally or alternatively, Figure 5 One or more process blocks of may be performed by one or more components of device 400 , such as input component 410 , switching component 420 , output component 430 , and / or controller 440 .

[0065] like Figure 5 As shown in , process 500 may include cross-connecting sessions for user equipment from a residential radio access station integrated with a network device using a network address (block 510). For example, as described above, the device may cross-connect sessions for user equipment from a residential radio access station integrated with a network device using a network address. In some implementations, the network device is a residential gateway. In some implementations, the residential radio access station is integrated with the network device via hardware or a hardware connection. In some implementations, the device is an access gateway function of a core network. In some implementations, the network address is a wide area network Internet Protocol address.

[0066] like Figure 5 As further shown in FIG. 5 , process 500 may include authenticating the user device based on the session (block 520). For example, as described above, the device may authenticate the user device based on the session.

[0067] like Figure 5 As further shown in FIG. 5 , process 500 may include authorizing the user device for the session (block 530). For example, as described above, the device may authorize the user device for the session.

[0068] like Figure 5 As further shown in FIG. 5 , process 500 may include providing one or more services to a user device as an independent subscriber via a session and a residential radio access station integrated with a network device (block 540). For example, as described above, the device may provide one or more services to a user device as an independent subscriber via a session and a residential radio access station integrated with a network device. In some implementations, providing the one or more services to the user device as an independent subscriber includes providing the one or more services to the user device via a direct mode supported for the core network. In some implementations, providing the one or more services to the user device includes providing the one or more services to the user device without utilizing network address translation.

[0069] In some implementations, the process 500 includes receiving a request from a residential radio access station integrated with a network device to reestablish a call of a user equipment that was handed over to the residential radio access station integrated with the network device, and reestablishing the call based on the request. In some implementations, the process 500 includes receiving a request from a residential radio access station integrated with a network device to reestablish a connection of a user equipment that was handed over to the residential radio access station integrated with the network device, and reestablishing a connection with a core network based on the request.

[0070] In some implementations, process 500 includes receiving a wake-up service for a user device from a core network, and providing the wake-up service to a residential radio access station integrated with a network device, wherein the wake-up service is provided to the user device by the residential radio access station integrated with the network device. In some implementations, providing the wake-up service to the residential radio access station integrated with the network device includes providing the wake-up service to the residential radio access station integrated with the network device based on a location of the device and a location of the network device. In some implementations, the wake-up service is one of a short message service or an emergency service. In some implementations, providing the wake-up service to the residential radio access station integrated with the network device includes providing the wake-up service to the residential radio access station integrated with the network device without utilizing network address translation.

[0071] Although Figure 5 An example block diagram of process 500 is shown, but in some implementations, process 500 may include Figure 5 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 500. Additionally or alternatively, two or more blocks of the process 500 can be performed in parallel.

[0072] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in different forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not a limitation to implementation. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code-it should be understood that software and hardware can be used to implement the systems and / or methods described herein.

[0073] As used herein, satisfying a threshold may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0074] To the extent that the above implementations collect, store, or use an individual's personal information, it should be understood that such information should be used in accordance with all applicable laws concerning the protection of personal information. Additionally, the collection, storage, and use of such information may be subject to the individual's consent to such activities, for example, through well-known "opt-in" or "opt-out" processes that may be appropriate to the circumstances and type of information. The storage and use of personal information may be conducted in an appropriately secure manner that reflects the type of information, for example, through various encryption and anonymization techniques for particularly sensitive information.

[0075] Even though specific combinations of features are listed in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various implementations. In fact, many of these features can be combined in ways that are not specifically listed in the claims and / or disclosed in the specification. Although each dependent claim listed below may be directly subordinate to only one claim, the disclosure of various implementations includes each dependent claim combined with the remaining claims in the claim set. As used herein, a phrase referring to "at least one of" in a list of items refers to any combination of those items, including single members. As an example, "at least one of: a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiple identical items.

[0076] The elements, actions or instructions used in this article should not be interpreted as critical or necessary unless explicitly described as such. In addition, as used herein, the articles "one" and "an" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more projects related to the article "the", and can be used interchangeably with "the one or more". In addition, as used herein, the term "set" is intended to include one or more projects (for example, a combination of related projects, unrelated projects, or related and unrelated projects), and can be used interchangeably with "one or more". In the case of only meaning one project, the phrase "only one" or similar language is used. In addition, as used in this article, the term "having" etc. is intended to be an open term. In addition, the phrase "based on" is intended to represent "based at least in part", unless otherwise clearly stated. In addition, as used herein, the term "or" is intended to be inclusive when used in a series, and can be used interchangeably with "and / or", unless otherwise clearly stated (for example, if used in combination with "either" or "only one").

[0077] In the foregoing description, various exemplary embodiments have been described with reference to the accompanying drawings. However, it will be apparent that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the present invention as set forth in the following claims. Accordingly, the description and drawings are to be regarded as illustrative rather than restrictive.

Claims

1. A method, include: cross-connecting, by the device, sessions for the user device from a residential radio access station integrated with the network device using the network address; authenticating, by the device, the user device based on the session; authorizing, by the device, the user equipment for the session; as well as One or more services are provided by the device to the user equipment as a standalone subscriber via the session and the residential radio access station integrated with the network device. The method according to claim 1 , wherein the network device is a residential gateway.

3. The method of claim 1, wherein the premises radio access station is integrated with the network device via hardware or a hardware connection.

4. The method of claim 1, wherein the one or more services are provided to the user equipment as the independent subscriber include: The one or more services are provided to the user equipment via a direct mode supported for a core network. The method of claim 1 , wherein the device is an access gateway function of a core network.

6. The method according to claim 1, further comprising: include: receiving a request from the residential radio access station integrated with the network device, the request being for reestablishing a call of the user equipment, the call being handed over to the residential radio access station integrated with the network device; as well as The call is reestablished based on the request.

7. The method according to claim 1, further comprising: include: receiving a request from the residential radio access station integrated with the network device, the request being for re-establishing a connection of the user equipment, the connection being switched to the residential radio access station integrated with the network device; as well as The connection with the core network is reestablished based on the request.

8. A device, include: one or more memories; as well as One or more processors for: cross-connecting sessions for user equipment from a residential radio access station integrated with the network equipment using the network address, wherein the residential radio access station is integrated with the network device via hardware or hardware connection; authenticating the user device based on the session; authorizing the user equipment for the session; as well as One or more services are provided to the user equipment as a standalone subscriber via the session and the residential radio access station integrated with the network device.

9. The apparatus of claim 8, wherein the network address is a wide area network Internet Protocol address.

10. The device of claim 8, wherein in order to provide the one or more services to the user equipment, the one or more processors are configured to: The one or more services are provided to the user equipment without utilizing network address translation.

11. The device of claim 8, wherein the one or more processors are further configured to: receiving a wake-up service for the user equipment from a core network; and providing the wake-up service to the residential radio access station integrated with the network device, The wake-up service is provided to the user equipment by the residential radio access station integrated with the network device.

12. The device of claim 11, wherein to provide the wake-up service to the residential radio access station integrated with the network device, the one or more processors are configured to: The wake-up service is provided to the residential radio access station integrated with the network device based on the location of the device and the location of the network device.

13. The apparatus of claim 11, wherein the wake-up service is one of a short message service or an emergency service.

14. The device of claim 11, wherein to provide the wake-up service to the residential radio access station integrated with the network device, the one or more processors are configured to: The wake-up service is provided to the residential radio access station integrated with the network device without utilizing network address translation.

15. A non-transitory computer readable medium storing an instruction set, the instruction set include: One or more instructions that, when executed by one or more processors of a device, cause the device to: cross-connecting sessions for user equipment from a residential radio access station integrated with a residential gateway using a network address; authenticating the user device based on the session; authorizing the user equipment for the session; as well as One or more services are provided to the user equipment as a standalone subscriber via the session and the residential radio access station integrated with the residential gateway.

16. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions that cause the device to provide the one or more services to the user device that is the independent subscriber cause the device to: The one or more services are provided to the user equipment via a direct mode supported for a core network.

17. The non-transitory computer readable medium of claim 15, wherein the one or more instructions further cause the device to: receiving a request from the residential radio access station integrated with the residential gateway, the request being for re-establishing a call of the user equipment, the call being handed over to the residential radio access station integrated with the residential gateway; and The call is reestablished based on the request.

18. The non-transitory computer readable medium of claim 15, wherein the one or more instructions further cause the device to: receiving a request from the residential radio access station integrated with the residential gateway, the request being for re-establishing a connection of the user equipment, the connection being switched to the residential radio access station integrated with the residential gateway; and The connection with the core network is reestablished based on the request.

19. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions that cause the device to provide the one or more services to the user device cause the device to: The one or more services are provided to the user equipment without utilizing network address translation.

20. The non-transitory computer readable medium of claim 15, wherein the one or more instructions further cause the device to: receiving a wake-up service for the user equipment from a core network; and providing the wake-up service to the residential radio access station integrated with the residential gateway, The wake-up service is provided to the user equipment by the residential radio access station integrated with the residential gateway.

Images