Enhanced Residential Gateway for 5G
The enhanced residential gateway (eRG) addresses handset mobility challenges by managing 5GS registration and CPN identification, ensuring seamless and high-quality service delivery within the customer premises network through efficient QoS management and communication.
Patent Information
- Application Number
- JP2024526760
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-11-05
- Filing Date
- 2022-11-04
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2042-11-04
AI Technical Summary
Handset mobility in wireless systems poses challenges in handling service transitions and ensuring quality of service (QoS) as handsets move, necessitating streamlined functions to be managed at specific locations.
An enhanced residential gateway (eRG) performs registration for 5GS and Customer Premises Network (CPN) identification, handling the user plane of a 5G wireless transmit-receive unit (WTRU), including procedures for WTRU registration and PDU session establishment for local breakout in the CPN, supporting seamless QoS management and communication within the customer premises network.
The eRG ensures consistent and high-quality service delivery as users move within the CPN by managing registration and user plane functions, maintaining QoS and enabling efficient communication between devices, even when transitioning between different radio access technologies.
Smart Images

Figure 2024542120000001_ABST
Abstract
Description
[Technical field]
[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 276,329, filed November 5, 2021, the contents of which are incorporated herein by reference. Summary of the Invention [Problem to be solved by the invention]
[0002] In wireless systems, handset mobility always presents a problem of how services are handled as the handset moves. With an increasing number of use cases requiring higher quality of service (QoS), there is a need to ensure that some functions related to handset mobility are made efficient by moving them as far as possible to a specific location, even while services transition as the handset moves.
[0003] In one or more systems, methods, and / or devices, an enhanced residential gateway (eRG) may perform registration for 5GS and Customer Premises Network (CPN) identification. This may include registration procedures for the eRG and / or service request procedures for the eRG. Additionally, the eRG may handle the user plane for 5G wireless transmit-receive units (WTRUs). This may include procedures for eRG for WTRU registration and / or protocol data unit (PDU) session establishment for local breakout in the CPN. [Brief description of the drawings]
[0004] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which like reference numbers indicate similar elements and in which: [Figure 1A] FIG. 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] FIG. 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A, according to one embodiment. [Figure 1C] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 1D] FIG. 1D is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communications system illustrated in FIG. 1A, according to one embodiment. [Diagram 2] FIG. 2 illustrates an example overview of a customer premises network. [Diagram 3] FIG. 3 is a diagram illustrating an example of a non-roaming architecture for a 5G core network for a 5G-RG with a wireline 5G access network and a Next Generation Radio Access Network (NG RAN). [Figure 4] FIG. 4 is a diagram illustrating an example of an AGF (Access Gateway Function) in 5G WWC (wireline and wireless convergence). [Diagram 5] FIG. 5 is a diagram illustrating an example of a UPF (User Plane Function) installed in the eRG. [Figure 6] FIG. 6 is a diagram illustrating an alternative example of functionality splitting. [Figure 7] FIG. 7 is a diagram illustrating an example of the NG N2 / N3 interface. [Figure 8] FIG. 8 is a diagram illustrating an example of a user plane protocol in an eRG. [Figure 9] FIG. 9 is a diagram illustrating an example of a control plane protocol in an eRG. [Figure 10] FIG. 10 is a diagram illustrating an example of the control and user plane from a WTRU perspective. [Figure 11] FIG. 11 is a diagram illustrating an example of a control plane protocol stack between an eRG and a 5GC. [Figure 12] FIG. 12 is a diagram illustrating an example of an extended user plane protocol in an eRG. [Figure 13] FIG. 13 is a diagram illustrating an example of a registration procedure for an eRG. [Figure 14] FIG. 14 is a diagram illustrating an example of a WTRU registration process with an eRG. [Figure 15] FIG. 15 is a diagram illustrating an aspect of a WTRU registration process. [Figure 16] FIG. 16 is a diagram illustrating an example of an aspect of a WTRU registration process. [Figure 17] FIG. 17 illustrates an example of establishing a default PDU session within a CPN. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0005] 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. Communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcasts, etc., to multiple wireless users. Communications system 100 may enable multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communications system 100 may use one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multicarrier (FBMC), and the like.
[0006] 1A, communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a station (STA), may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, landline or mobile subscriber units, subscription-based units, pagers, mobile phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain contexts), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.
[0007] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each illustrated as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.
[0008] The base station 114a may be part of the RAN 104, which may also include other base stations, such as a base station controller (BSC), a radio network controller (RNC), relay nodes, and / or network elements (not shown). The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage for a particular geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell, for example, using beamforming to transmit and / or receive signals in a desired spatial direction.
[0009] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d via an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).
[0010] More specifically, as noted above, the communications system 100 may be a multiple access system, but may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base stations 114a and the WTRUs 102a, 102b, 102c of the RAN 104 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communications protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed Uplink (UL) Packet Access (HSUPA).
[0011] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).
[0012] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using NR.
[0013] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, e.g., using a dual connectivity (DC) principle. Thus, the radio interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to and from multiple types of base stations (e.g., eNBs and gNBs).
[0014] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a wireless technology such as IEEE 802.11 (i.e., Wireless Fidelity, WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access, WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), or the like.
[0015] 1A may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point, but may utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as a location of a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 through the CN 106.
[0016] The RAN 104 may communicate with the CN 106, which may be any type of network configured to provide voice, data, application, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various quality of service (QoS) requirements, such as, for example, different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 may provide call control, charging services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. Although not shown in FIG. 1A, it will be understood that the RAN 104 and / or the CN 106 may communicate directly or indirectly with other RANs that use the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may utilize NR radio technology, the CN 106 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.
[0017] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network providing plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), the user datagram protocol (UDP), and / or the internet protocol (IP) of the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs that may use the same RAT as the RAN 104 or a different RAT.
[0018] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a, which may employ a cellular-based wireless technology, and a base station 114b, which may employ an IEEE 802 wireless technology.
[0019] 1B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1B, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be understood that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
[0020] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although FIG. 1B illustrates the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0021] The transmit / receive element 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via the wireless interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.
[0022] 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
[0023] The transceiver 120 may be configured to modulate signals transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As mentioned above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as, for example, NR and IEEE 802.11.
[0024] The processor 118 of the WTRU 102 may be coupled to, and may receive user-entered data from, a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In other embodiments, the processor 118 may access information from and store data in memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown).
[0025] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control the power to other components in the WTRU 102. The power source 134 may be any suitable device for providing power to the WTRU 102. For example, the power source 134 may include one or more dry batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.
[0026] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may obtain location information by way of any suitable location determination method while remaining consistent with an embodiment.
[0027] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors. The sensor may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor, and the like.
[0028] The WTRU 102 may include a full-duplex radio where the transmission and reception of some or all of the signals (e.g., associated with a particular subframe of both the UL (e.g., for transmission) and DL (e.g., for reception)) may be simultaneous and / or together. The full-duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., via a separate processor (not shown) or via processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio where the transmission and reception of some or all of the signals (e.g., associated with a particular subframe of either the UL (e.g., for transmission) or DL (e.g., for reception)) may be simultaneous and / or together.
[0029] 1C is a system diagram illustrating the RAN 104 and the CN 106, according to one embodiment. As mentioned above, the RAN 104 may employ E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also communicate with the CN 106.
[0030] The RAN 104 may include eNode-Bs 160a, 160b, 160c, although it will be understood that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO techniques. Thus, the eNode-B 160a may, for example, use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.
[0031] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling, etc. in the UL and / or DL. As shown in FIG 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.
[0032] 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN), packet data gateway (PGW) 166. Although the foregoing elements are illustrated as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0033] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may function as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, activating / deactivating bearers, selecting a particular serving gateway during initial attachment of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.
[0034] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-eNode B handovers, triggering paging when DL data is available to the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c.
[0035] The SGW 164 may be connected to a PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0036] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.
[0037] Although the WTRU is depicted in FIGS. 1A-1D as a wireless terminal, in certain representative embodiments it is contemplated that such a terminal may use a wired communications interface (e.g., temporarily or permanently) with the communications network.
[0038] In an exemplary embodiment, the other network 112 may be a WLAN.
[0039] A WLAN in infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic within the BSS and / or outside the BSS. Traffic originating from outside the BSS to the STA may arrive through the AP and be delivered to the STA. Traffic originating from the STA to a destination outside the BSS may be sent to the AP and transmitted to the respective destination. Traffic between STAs within the BSS may be sent, for example, through the AP, where the source STA may send traffic to the AP, which may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent between (e.g., directly between) the source STA and the destination STA using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may be referred to herein as an "ad-hoc" communication mode.
[0040] When using an 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be the operating channel of the BSS, but may be used by STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. With CSMA / CA, STAs (e.g., all STAs), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.
[0041] A High Throughput (HT) STA may use a 40 MHz wide channel for communication, which may be formed, for example, through a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels.
[0042] A Very High Throughput (VHT) STA may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. A 40 MHz and / or 80 MHz channel may be formed by combining multiple contiguous 20 MHz channels. A 160 MHz channel may be formed by combining eight contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, after channel encoding, the data may pass through a segment parser that may split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing may be performed separately on each stream. The streams may be mapped to two 80 MHz channels and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration may be reversed and the combined data may be transmitted to the Medium Access Control (MAC).
[0043] Sub-1 GHz operation modes are supported by 802.11af and 802.11ah. The channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter-type control / machine-type communications (MTC), such as MTC devices in macro coverage areas. MTC devices may have limited capabilities, including specific functions, for example, support for (e.g., only support for) specific bandwidths and / or limited bandwidths. The MTC device may include a battery that has a battery life above a threshold (eg, to maintain a very long battery life).
[0044] WLAN systems that may support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that may be designated as a primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be configured and / or limited by the STAs among all STAs operating in the BSS that support the smallest bandwidth operating mode. In an 802.11ah example, the primary channel may be 1 MHz wide for STAs (e.g., MTC-type devices) that support (e.g., only) 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. For example, if a STA (that only supports 1 MHz mode of operation) transmitting to an AP has a busy primary channel, all of the available frequency bands may be considered busy even if most of the available frequency bands are idle.
[0045] In the United States, the available frequency bands that can be used by 802.11ah are 902MHz to 928MHz. In South Korea, the available frequency bands are 917.5MHz to 923.5MHz. In Japan, the available frequency bands are 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz depending on the country code.
[0046] 1D is a system diagram illustrating the RAN 104 and the CN 106, according to one embodiment. As mentioned above, the RAN 104 may employ NR radio technology and communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also communicate with the CN 106.
[0047] The RAN 104 may include gNBs 180a, 180b, 180c, although it will be understood that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO techniques. For example, the gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may transmit and / or receive wireless signals to and from the WTRU 102a, for example, using multiple antennas. In one embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In one embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) techniques. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and 180b (and / or gNB 180c).
[0048] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., including varying numbers of OFDM symbols and / or varying lengths of absolute time durations).
[0049] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing another RAN (e.g., e-NodeBs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate with and connect to a gNB 180a, 180b, 180c while also communicating with and connecting to another RAN, such as an eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.
[0050] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support for network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Functions (UPFs) 184a, 184b, routing of control plane information towards Access and Mobility Management Functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.
[0051] 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although the foregoing elements are illustrated as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0052] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may function as a control node. For example, the AMF 182a, 182b may be responsible for user authentication of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selection of a particular SMF 183a, 183b, management of registration areas, termination of non-access stratum (NAS) signaling, mobility management, etc. Network slicing may be used by the AMF 182a, 182b to customize the CN support of the WTRUs 102a, 102b, 102c based on the type of service utilizing the WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, etc. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.
[0053] The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 106 via an N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 106 via an N4 interface. The SMFs 183a, 183b may select and control the UPFs 184a, 184b and configure the routing of traffic through the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions, such as managing and assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0054] The UPFs 184a, 184b may connect to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPFs 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, etc.
[0055] The CN 106 may facilitate communication with other networks. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the local DNs 185a, 185b through the UPFs 184a, 184b via an N3 interface to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185b.
[0056] 1A-1D and the corresponding description thereof, one or more or all of the functions described herein with respect to one or more of the WTRUs 102a-102d, base stations 114a-114b, eNode-Bs 160a-160c, MMEs 162, SGWs 164, PGWs 166, gNBs 180a-180c, AMFs 182a-182b, UPFs 184a-184b, SMFs 183a-183b, DNs 185a-185b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.
[0057] The emulation device may be designed to perform one or more tests of other devices in a lab environment and / or an operator network environment. For example, one or more emulation devices may perform one or more or all functions while fully or partially running and / or deployed as part of a wired and / or wireless communication network to test other devices in the communication network. One or more emulation devices may perform one or more or all functions while temporarily running / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for the purpose of testing and / or performing tests using over-the-air wireless communication.
[0058] The one or more emulation devices may perform one or more functions, inclusive, while not running / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in test scenarios in a test lab and / or in an undeployed (e.g., test) wired and / or wireless communication network to perform testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, for example, one or more antennas) may be used by the emulation devices to transmit and / or receive data.
[0059] In general, references to a "network" or any other non-entity specific term (e.g., 5GC) may inherently refer to one or more devices, nodes, functions, and / or base stations. These terms may be interchangeable unless otherwise specified.
[0060] FIG. 2 illustrates an example overview of a customer premises network. In an example scenario, there may be a residential gateway (e.g., a residential gateway deployed with a 5G system, etc.) 203 that connects a customer premises network (CPN) 201 to a core network (e.g., 5GC) 210 via radio (e.g., 208), wireline connection (e.g., 207), and / or some other access (e.g., 209). In general, the CPN includes a set of networking equipment located in a residence, office, or store that is owned, installed, and / or configured by a customer of a public network provider. This networking equipment can be broadly categorized into Premises Radio Access Stations (PRAS) 205 that are similar / same as home base stations, WTRUs 206 that can wirelessly connect to base stations (e.g., have 5G network capabilities), and non-3GPP devices 204 that use non-3GPP access technologies (e.g., 802.11 radio protocols, or other such non-3GPP access) to access 5GC. In some cases, the WTRU 202 may have a wired connection to the 5G-RG 203. A user or other entity may be authorized to partially configure and manage network nodes in a CPN (e.g., a PRAS or an eRG). They may be authorized administrators. The CPN may be owned, installed, and / or configured (at least in part) by a customer of a public network operator.
[0061] In some cases, the actual hardware used for the gateway (e.g., an enhanced residential gateway, a 5G gateway, etc.) may be similar or the same as any of the examples of WTRUs enumerated herein (or multiple WTRUs used in a distributed manner with a centralized controller). Additionally, there may be devices in the CPN that function as multiple entities. For example, a gateway device may also be a controller (e.g., virtualized within one device or separate computing units within one hardware device), a router, a switch, a network function, an access point, a residential wireless access station (PRAS), and / or a base station for a particular location.
[0062] 3 illustrates an example of a non-roaming architecture for a 5G core network for a 5G-RG having a wireline 5G access network and an NG RAN. As shown, the 5G-RG 307 can support both wireless 309A and wired 309B connections to the 5GC, such as a radio interface (Uu) through a next generation radio access network (NG-RAN) using 3GPP access 305, and a wireline interface (Y4) through a wireline 5G access network (W-5GAN) 308 to the 5GC (e.g., a node AMF 304 of the 5GC). For example, the W-5GAN 308 provides an N2 interface to the 5GC AMF 304 and an N3 interface to the UPF 302 (e.g., in a similar / same manner as a 5G base station); the W-5GAN enables untrusted and trusted non-3GPP WTRUs to connect to the 5GC via a Non-3GPP Inter-Working Function (N3IWF) and a Trusted Non-3GPP Gateway Function (TNGF), respectively; and / or the 5G-RG exchanges N1 signaling with the 5GC.
[0063] In some cases, the 5G-RG may be connected via an NG-RAN, which may operate as a WTRU connected via an NG-RAN, and there may be configuration for network selection, identification and authentication, policy control, lawful intercept, authorized access control, and barring for the 5G-RG similar to that for the WTRU.
[0064] In some cases, the 5G-RG may be connected via a W-5GAN. The 5G-RG may act as a WTRU connected via the W-5GAN and initiate a Protocol Data Unit (PDU) session and request Quality of Service (QoS) from the 5GC. An individual PDU session may serve multiple WTRUs behind the 5G-RG and provide connectivity to the 5GC with a granularity of one PDU session per slice.
[0065] The 5G-RG may first register with the AMF and establish a PDU session. The PDU session may include several QoS flows to support various services provided by the 5G network. Data from the data network may be passed to the UPF through the N6 interface and then forwarded to the W-5GAN through the N3 interface using the GPRS Tunnelling Protocol (GTP). From this point onwards, the 5G-RG may forward information to multiple WTRUs behind the 5G-RG using Ethernet or Wi-Fi access in the CPN.
[0066] FIG. 4 illustrates an example of an Access Gateway Function (AGF) in 5G Wireline and Wireless Convergence (WWC). In some cases, wireline and wireless may have one or more convergence points. With wireline access function to 5GC, current broadband services may access the Internet through 5G-RG. Considering the possibility of future use cases for devices in CPN, services and systems need to be defined to support Wireless and Wireless Convergence (WWC) in 5G systems. These specifications may define an Access Gateway Function (AGF) capable of providing AAA services (authentication, authorization, and accounting), traffic shaping, and regulation for fixed network (FN) and 5G-RG from standard 3GPP user plane functions in a common 5GC, as shown in FIG. 4. For example, AGF 411 may have a user plan connection to UPF 407 of 5GC 408, which in turn connects to data network 409. The AGF 411 may be part of a wireline access network 410 that connects with control and user signaling to the WAN 412, which in turn connects to other residential gateways (e.g., 5G-RG 415 and FN-RG 413). In an example scenario, the 5G-RG 415 may also be connected to a base station (e.g., gNB 414), which in turn connects to the CPF 406 of the 5GC 408.
[0067] In general, given the growing number of residential 5G uses, including bringing new experiences to users at home, leading 5G vendors may work to continuously improve residential 5G solutions. For example, one scenario may be to use mid-band spectrum (2.5 GHz and 3.5 GHz) and high-gain antennas to extend the capacity and coverage of fixed wireless access compared to traditional LTE-based fixed wireless solutions. Another scenario may have 180 million fixed wireless access connections by the end of 2026, providing CPNs with 5G access that enables high capacity and robust QoS capabilities. In another scenario, fixed wireless coverage may be extended up to 7 kilometers via 26 GHz mmWave frequency connections.
[0068] More than 70 percent of the world's mobile operators currently offer both mobile and fixed network services. Some examples of these services include fixed network, broadband Internet, mobile communications, and IPTV. The WWC initiative allows network operators to optimally integrate the provision of these services via a common 5GC. Along with other benefits of 5G, such as increased data rates, ultra-low latency, and improved reliability, the use of a common 5GC may reduce maintenance costs for network operators offering quadruple-play services.
[0069] Mobile network operators with only single-play services can also benefit from 5G residential services. One of the exemplary benefits that 5G brings to consumers is that it offers higher bit rates. These higher bit rates can enable or improve eMBB services such as mobile TV, AR / VR, mobile gaming, etc. Of note, such "mobile" services may be primarily used by users who are not on the move, but are sometimes mobile / fixed in a specific location (e.g., at home). In addition to higher bit rates, ultra-low latency and enhanced reliability may enhance the user experience for AR / VR, gaming, surveillance, and security applications. 5G residential gateways can serve as a platform for future localized services, home entertainment, AR / VR, etc., enabling 5G+ / 6G use cases.
[0070] There may be multiple use cases and traffic scenarios in residential environments that may require related new potential functional requirements, key performance requirements to support WWC, fixed LAN-5G LAN integration, and expansion for indoor small base stations. Some of these use cases are summarized here.
[0071] In one exemplary case, there may be efficient routing for WTRU-to-WTRU communication over an eRG. This use case assumes that multiple PRASs are already deployed in rooms behind an eRG to provide better cellular coverage in the home. This use case enables efficient routing for communication between two WTRUs over an eRG. For example, Alice is sitting in the attic and her smartphone connects to the PRAS in the attic. A security sensor detects fire and smoke in the basement and then sends an alert to Alice. Through the PRAS in the basement, the alarm message reaches the eRG, which then routes the message through the PRAS in the attic to Alice's smartphone. This use case highlights the "switching element" in the eRG that may switch local traffic between 3GPP devices as well as between 3GPP and non-3GPP devices.
[0072] In one exemplary case, there can be E2E QoS monitoring. This use case assumes that multiple PRASs are already deployed in rooms behind an eRG to provide better cellular coverage in a home. This use case enables E2E QoS monitoring of the entire communication path, i.e., from WTRU to 5GC / 5GC to WTRU via PRAS and eRG. For example, Alice is sitting in the living room and her smartphone connects to the PRAS in the living room. She starts streaming video in real time from a video application server on the cloud. After some time, the download speed slows down and the video stream stops. Alice calls the network operator and reports the network performance degradation. When the network operator checks the E2E QoS status, it detects high interference on the PRAS and reconfigures the PRAS to restore the E2E QoS. This use case highlights the capability of the eRG to measure the observed QoS for an individual user and take action to configure the QoS for that user. This document describes how the eRG measures and configures the QoS for an individual user.
[0073] In one exemplary case, there may be QoS maintenance from outdoor to indoor. Due to 5G outdoor to indoor coverage issues, the WTRU may access the 5GC through the eRG as it moves from outdoor to indoor. This use case allows for omni-directional QoS control guarantees even for ongoing high bandwidth or low latency consuming service (e.g., video game) users as they move from outdoor to indoor. For example, Tom is playing a video game on his smartphone on his way back to his house. When Tom arrives home, he continues playing the game as he enters the house. When Tom enters the house, his smartphone is identified and connected to the eRG. The eRG is also informed of the relevant QoS characteristics of Tom's smartphone at this point, and the 5GS provides the corresponding QoS to Tom. This use case highlights how Tom is identified in the 3GPP 5GC and continues to be identified as he moves around the house. His service continues at the desired level of QoS. The eRG is expected to identify Tom and provide the same QoS as he moves around the house.
[0074] In one exemplary case, there may be a seamless path switch from WTRU-to-WTRU direct communication to indirect communication via an eRG. This use case allows two WTRUs to seamlessly switch from a direct communication path to an indirect communication path via an eRG as the distance between the WTRUs increases. For example, two WTRUs (WTRU1 and WTRU2) are connected via a 3GPP direct communication path. An event occurs that triggers WTRU1 to move away from WTRU2. To seamlessly continue the service with the same QoS, an indirect communication path via an eRG is established.
[0075] To support use cases such as those described herein, the following requirements have been identified for the eRG: the 5G system must be able to support authentication of WTRUs with 3GPP authentication information for communications with entities in the CPN (WTRUs, devices); the 5G system must be able to support efficient data paths through the eRG for intra-CPN data traffic to or from the WTRU; the 5G system must be able to support real-time E2E QoS monitoring and control for any intra-CPN data traffic to or from the WTRU (e.g., via the eRG or PRAS and eRG); the 5G system must be able to support real-time E2E QoS monitoring and control for any data communications between a WTRU in the CPN and the 5G network (e.g., via the eRG or PRAS and eRG). the 5G system may support QoS monitoring and control, the 5G system may minimize service interruptions for WTRUs moving between the CPN access and operator provided mobile access, the 5G system may support a mechanism for the network operator to configure one or more parameters in the eRG (e.g., different negotiated QoS levels, authentication information, identification, initial OA&M information, and / or policies on which communication means (e.g., wireless, cable, etc.) are most preferred for the associated subscription), the 5GS may enable the network operator to provide 5G services to any WTRU via a PRAS connected via the eRG, and / or the 5GS may support applications on application servers connected to the CPN. One or more of these requirements may require identification and visibility of WTRUs by the 5GC, the ability to enforce more granular QoS for each WTRU, and / or individual policy enforcement per WTRU, link or application service, etc.
[0076] 5 illustrates an example of a User Plane Function (UPF) carried on an enhanced residential gateway (eRG). As shown, eRG 501 may include various functions such as UPF 503 in addition to 5G-RG 502. For illustrative purposes, dotted lines may indicate example data flow paths and solid lines may indicate connections and / or interfaces. eRG 501 may be expected to differentiate QoS requirements of each WTRU (e.g., 504, 505, 507, 508) connected to the 5GC via its interfaces.
[0077] According to an example of an eRG architecture, WTRUs behind an eRG may not be identified independently, but instead, the PDU session identifies them as slices. The eRG may be able to differentiate the QoS requirements of each WTRU to access the respective QoS flows from the 5GC to provide a consistent policy-driven service experience. The 5GC may implement QoS control and policies through the SMF and UPF. If functions such as the SMF and UPF are loaded in the eRG (e.g., as partially illustrated in FIG. 5), the functional requirements defined above may be met. When the UPF and SMF are loaded in the eRG, it may be possible to identify individual user planes, perform measurements on the user plane, and set QoS parameters for a desired user experience. This is an architectural assumption that may be made for one or more embodiments described herein.
[0078] FIG. 6 illustrates an example of a functional splitting alternative. There may be one or more deployment options for eRG with functional splitting. In some cases, eRG and PRAS architectures may use split function techniques. In one exemplary deployment option, eRG and PRAS scenarios may be similar to a split architecture of distributed base stations (e.g., gNBs) in a network (e.g., NG-RAN). In a distributed gNB architecture, a centralized unit base station (e.g., gNB-CU (centralized unit)) controls one or more distributed units (gNB-DU (distributed unit)) through an F1 interface. The distributed units are connected to remote radio heads (RRHs), remote radio transceivers. The gNB-CU is split into two parts, one for control plane functions (gNB-CU-CP (control plane)) and one for user plane functions (gNB-CU-UP (user plane)). As shown, 601-620 illustrate different layers of processing in an exemplary uplink or downlink process. This functional split may be done in any of the eight split options shown between UL / DL layers (e.g., options 1-8). The PRAS may be assumed to be a gNB-DU and the eRG may be assumed to be a gNB-CU. The exact point of splitting may be left open for implementation. In at least one embodiment described herein, the CU-UP and CU-CP techniques may be employed with the eRG.
[0079] Figure 7 illustrates an example of a NG N2 / N3 interface model split. There may be a WTRU 701 with a connection to a cell 702, which in turn is connected to a network employing a split function architecture system. The example shows a deployment of a control plane 711 and a user plane 712 within an eRG 709. The techniques described with respect to Figure 6 apply equally to the diagram of Figure 7.
[0080] FIG. 8 illustrates an example of user plane protocols in an eRG. For the user plane deployment option, an example protocol stack for the user plane from WTRU 801 to eRG 802 is shown. These protocol stacks (e.g., 803-807) are intended to illustrate only the user plane without detailing the split. The user plane protocols may perform the actual PDU session services, such as carrying user data through the access stratum. The user plane may be assumed to be terminated in the eRG to enable local routing to the CPN. The SDAP 803 layer in the user plane stack may be assumed to be a termination point in the eRG. In summary, in some examples where a central unit user plane (CU-UP) technique is considered for the WTRU, there may be a GTP-U / N3 over a local data link towards the local UPF, and / or the WTRU may act as a relay to forward UP packets over the user plane established in the 5GC (e.g., through the eRG).
[0081] FIG. 9 illustrates an example of a control plane protocol in an eRG. For the control plane option, an example control plane protocol stack is shown for a WTRU 901 to a 5GC (e.g., AMF 903) through an eRG 902. The control plane protocol may control the PDU session and the connection between the WTRU 901 and the 5GC. It may support the setup of services requested by a user (e.g., WTRU 901), control of different transmission resources, handover, etc. As shown, the eRG may forward NAS messages from the WTRU 901 to the 5GC / AMF 903. In some examples, a CU-CP deployment option may be possible for the WTRU, an NGAP / N2 on the user plane may be established by the eRG with the 5GC, and / or NAS-MM messages may be forwarded transparently between the WTRU and the NG-RAN over the eRG (e.g., the eRG acts as a relay node).
[0082] FIG. 10 illustrates an example of a control plane and user plane from a WTRU perspective. As shown, the WTRU 1001 has a control plane 1012 link to a base station (e.g., gNB 1003), and the control plane extends to the AMF 1002. The user plane 1011 extends from the base station through the UPF 1004 to the DN 1005. In some cases, there may be transparent forwarding of NAS-MM message options for the WTRU within the CPN. Transparent forwarding of NAS-MM messages may occur over an N1 interface towards a 5GC set up by an eRG that is a WTRU for its own use. FIG. 10 may show a logical N1 interface from the WTRU 1001 to the AMF 1002, which may be used for NAS message forwarding from the WTRU within the CPN. The Nr-Uu may carry both the control plane and the user plane from the WTRU. The user plane then egresses from the base station towards the DN via N3, N6 / N9.
[0083] Figure 11 illustrates an example of a control plane protocol stack between an eRG and a 5GC. There may be an eRG 1101, a 5G-AN 1102, an AMF 1103, and an SMF 1104. In this example, it may be assumed that the eRG 1101 deploys the following control plane protocols as shown to support the N1 interface: N1 is the control plane interface with the AMF 1103, whose messages are delivered through the gNB via the NR-Uu and N2 interfaces. The N1 NAS signaling connection is either a concatenation of the RRC connection over the Uu reference point and the NG connection over the N2 reference point for 3GPP access, or a concatenation of the IPsec tunnel over the NWu reference point and the NG connection over the N2 reference point for non-3GPP access.
[0084] The NAS protocol for MM functions (NAS-MM) may support registration management functions, connection management functions, and user plane connection activation and deactivation. It may also be responsible for ciphering and integrity protection of NAS signaling.
[0085] Based on one or more of the architecture scenarios described in this specification, one or more of the following issues may be addressed: eRG registration and CPN identification, and / or handling of UP termination from the WTRU and CPN in the eRG.
[0086] Any user device, such as an eRG or a WTRU, may be capable of providing the CPN service. In general, it may be beneficial if a personal device can provide the CPN service, especially in a PIN network. Thus, the CPN may be considered as a service provided by any user device. To enable a user device to provide the CPN service, one or more approaches (as described herein) may be considered, i.e., how does a CPE subscribe to the 5GC and inform it about the capability and pre-configuration (e.g., by an authorized administrator) for providing the CPN service? What does the 5GC do to enable / allow the CPE to provide the CPN service? What configuration information needs to be provided? How is the CPN identified by the 5GC? How can the CPN service be continued when the anchor CPE leaves the premises? etc.
[0087] FIG. 12 illustrates an example of an enhanced user plane protocol in an eRG. As shown, there is an example of a user plane termination from a WTRU 1201 to an eRG 1202. The SDAP protocol on the left is the termination point where user plane packets are available. User plane packets can be forwarded to either a 5GC 1207 or a CPN 1206. The diagram shows enhanced user plane services in a dotted box (e.g., comparable / similar to a switching function), which may include a UP handler 1203 that makes the decision, and a local UPF 1205. These enhanced user plane services may represent one of the extensions to the residential gateway. The eRG may handle the forwarding of user plane packets towards the 5GC and CPN, and to do so may use one or more functions that were previously external to the residential gateway. The 5GC may configure one or more aspects of the eRG, for example, to enable forwarding of packets between the 5GC and the CPN.
[0088] Regarding eRG / CPN registration and identification, an eRG can be considered as a WTRU type device from the 5GC perspective, and thus can register with the 5G network, provide capability information, and perform other related actions. An eRG may be partially configured by an authorized administrator. An eRG can handle (e.g., determine, route, switch, etc.) communications routed to the 5G-AN as well as communications routed locally towards the CPN. An eRG can provide home PLMN and local PLMN services, which allow destinations in the customer premises network to be reached. An eRG may register with a 5GS to provide local PLMN services. Then, when a local WTRU registers with a 5GC, the WTRU can be provided with available PLMNs, such as the home PLMN and local PLMN. A local WTRU can register with both PLMNs. The 5GC can provide configuration information to the WTRU in the CPN using a NAS message over N1.
[0089] For management of the user plane from the WTRU and the CPN, the 5GC may maintain one or more lists of CPN_ID->DEVICE_ID (e.g., currently registered and / or active) subscriptions. The WTRU may initiate user plane setup towards another WTRU or a non-3GPP device in the CPN and / or towards another WTRU in the operator network. The 5GC may use the N1-eRG interface to indicate how the user plane needs to be transferred. For example, the WTRU may request to connect to a particular WTRU that is not connected to a CPN. The 5GC may instruct the WTRU to connect to the CPN and set up the user plane.
[0090] 13 illustrates an example of an eRG registration procedure. As illustrated, there is an eRG 1321, a 5G-AN 1322, and a 5GC / AMF 1323. At 1301, the eRG sends a transmission including "5G CPN" capabilities as part of an updated "5GMM Capabilities" in a registration request message. The "5G CPN Capabilities" indicates pre-configured information by the network operator and / or authorized administrator, i.e., configurable CPN name or CPN ID (e.g., 5GC may provide a configurable "CPN-PLMN" that can be used by the PRAS or N3IWF), 5G non-3GPP remote WTRU using N3IWF, offloading CPN->local UPF or other, local service information such as local DNN, QoS capabilities in the CPN, use of unlicensed spectrum by the PRAS connected to the eRG, and / or support for visitor access.
[0091] [Table 1]
[0092] There may be one or more capability information bits. For example, configurable CPN name: 5GC allows the eRG to recognize that it may support two or more CPN_Names that are configurable to enable different services and service levels for each CPN_Name. The "CPN with UPF" bit indicates a capability of CPN communication that allows the eRG to switch communications originating from a WTRU behind the eRG to a local UPF. The "CPN with Relay" bit indicates a capability of CPN communication that allows the eRG to relay traffic originating from a WTRU behind the eRG to the 5GC. Offloading to CPN indicates a capability to offload incoming traffic to a local UPF. N3IWF support indicates a capability to enable users of untrusted non-3GPP access to connect to the 5GC through the eRG. Local DNN capability indicates a capability to connect to a local or external IP network through the eRG. The 5GC may use the QoS capability in the CPN capability to prioritize specific service data flows to provide the expected QoS. "Unlicensed spectrum usage" indicates a capability to use unlicensed spectrum in the PRAS connected to the eRG. The "Visitor Access Support" bit indicates whether the eRG / PRAS supports access for all visitors, denies access, or allows only certain visitors. This feature may be pre-configured by an authorized administrator (e.g., according to operator policy).
[0093] At 1302, the registration request message may be forwarded to the AMF.
[0094] At 1303, there may be one or more message exchanges related to identity requests and / or security procedures.
[0095] In some cases, the AMF may store "5G CPN" capabilities for 5G CPN operation. The AMF may obtain "5G CPN" subscription data as part of user subscription data from the UDM during an eRG registration procedure using the Nudm_SDM service. The AMF may determine whether the eRG is authorized to provide 5G CPN services based on the 5G CPN capabilities of the eRG together with pre-configuration by an authorized administrator and the "CPN service authorization" included in the subscription data received from the UDM. The AMF may store the authorized "5G CPN" capabilities. The AMF may send the authorized 5G CPN capabilities for 5G CPN operation to the PCF. Based on the 5G CPN capabilities received from the AMF, the PCF may provide QoS parameters for 3GPP devices in the CPN, non-3GPP devices in the CPN, service-specific QoS, and / or promised QoS for the eRG. The AMF may store such information as part of the eRG context.
[0096] At 1304, the AMF may initiate a session setup with a gNB (e.g., of 5G-AN 1322). The message may include a registration accept NAS message. The message may carry one or more PDU session setup requests. Each PDU session may be addressed with a "PDU session ID". The message may also carry uplink TEIDs for all PDU sessions.
[0097] Additionally / alternatively, the AMF may send an NGAP message, such as, for example, a "Registration Accept" message, to the NG-RAN together with a session setup message, such as an "Initial Context Setup Request", or as a separate message, if the eRG is authorized to use "5G CPN Authorization" information including one or more of the following: QoS details as part of the eRG context; CPN_PLMN_ID; whether the eRG is authorized to act as a 5G Layer 2 WTRU-Network Relay; and / or whether the eRG is authorized to act as a 5G ProSe Layer 3 WTRU-Network Relay.
[0098] The purpose of the "Initial Context Setup" procedure may be to establish the required entire initial eRG context in the NG-RAN node, when needed, including PDU session context from the eRG (e.g., CPN relay L3 / l2 ETC), security keys, mobility restriction lists, eRG radio capabilities, and / or eRG security capabilities.
[0099] At 1305, the 5G AN may send a registration accept message to the eRG, which may include CPN settings, such as PLMN ID / CPN ID to the eRG, and / or radio parameters to be used within the CPN.
[0100] [Table 2-1]
[0101] [Table 2-2]
[0102] An eRG may use "CPN_Info" to configure itself and the PRAS.
[0103] The following PRAS configuration may be performed: PLMN ID and CPN ID are configured in the PRAS to be broadcast as part of the system information (e.g., the WTRU may select a PLMN ID to join the CPN); lists of cells to be added, existing cells to be modified, or cells to be deleted; cells to be activated or deactivated; and / or user plane functions between the PRAS and the eRG (e.g., flow control, fast retransmission of PDCP (Packet Data Convergence Control) PDUs lost due to radio link outage, discarding redundant PDUs, retransmission data indication, and status reporting).
[0104] At 1306, the eRG may receive a capability information inquiry. At 1307, the capability information may be sent to the 5G-AN. The eRG may inform the 5GC about its capabilities to support CPN call forwarding and routing, and available services such as direct connection through local UPF, support for transition from D2D to connectivity through the eRG and vice versa, relay / pass-through for public network, and / or available supported services. See Table 3 for an example of capability information. The template for the eRG may use a template similar to the WTRU template as shown in Table 3, but it would be an eRG network capability IEI.
[0105] [Table 3]
[0106] At 1308, the 5G-AN may send the capability information to the 5GC / AMF. The 5GC / AMF may use the capability information for: direct connection through a local UPF, where the AMF is aware of the local UPF and selects the local UPF to enforce any policy / QoS for the WTRU connected to the CPN if the AMF is aware of the local UPF and maintains an association with the remote SMF; support for transition from D2D to connection through an eRG and vice versa, where the 5GC may instruct the eRG to transition the user session from D2D to "intra-routing" within the eRG based on reported measurements and available QOS; support for pass-through / relay for public networks, where the AMF maintains an association with other AMFs for the WTRU and is aware of and supports relay for control plane and user plane; and / or available services, which may allow such services in accordance with a subscription database for the user and / or advertise the availability of the services through the service enablement layer (SA6).
[0107] At 1309, the eRG and the 5G-AN may perform security mode and / or RRC reconfiguration. In some examples, this may be performed based on the previous steps of this process.
[0108] At 1310, the 5G-AN may send an NGAP initial context setup response to the 5GC / AMF. At 1311, the 5G-AN may send a message regarding NGAP registration being completed (e.g., see box 1102 of FIG. 11 where the context is set up for the 5G-AN protocol and NGAP layers).
[0109] A service request procedure for an eRG in CM-IDLE state may be performed, and if the eRG is authorized to use CPN services, the AMF may include "CPN Authorization" information in the NGAP message indicating which CPN services the eRG is authorized to use. These authorized CPN services may or may not be used by the eRG to visit the WTRU, depending on the preferences of the authorized administrator. The AMF may also send "Remote WTRU" QoS parameters to the NG-RAN via N2 signaling.
[0110] For user plane processing in the eRG (-WTRU and CPN), the user plane setup and processing can be divided into two parts: registration procedure and PDU establishment.
[0111] FIG. 14 illustrates an example of a WTRU registration process with an eRG. In this example, there may be a WTRU (e.g., 5G) 1421, a PRAS 1422, an eRG 1423, a 5G-AN 1424, and a 5GC / AMF 1425. As shown, at 1401, there may be a PLMN and cell selection, and the WTRU may select a CPN_PLMN_ID and cell based on a Closed Access Group (CAG) ID. The CPN_PLMN_ID may uniquely identify the CPN network from the 5GC. The base station (e.g., eNB / gNB) may select an AMF based on the WTRU's 5G-S-TMSI. The selected AMF (e.g., for the WTRU) may need to determine the AMF that serves the eRG. There may be more than one technique for determining the serving eRG.
[0112] FIG. 15 illustrates an example of an aspect of a WTRU registration process, such as part of eRG configuration / determination. In this example scenario, there may be a base station (e.g., eNB / gNB) 1521, a selected AMF 1522, and an eRG_AMF 1523 (e.g., an AMF serving an eRG). In general, the base station may first identify its own serving AMF and send a NAS message of the WTRU with the AMF ID of the AMF serving the eRG. As shown, at 1501, the base station may select an AMF based on the WTRU's 5G-S-TMSI, and at 1502, the base station may provide the AMF ID (of the AMF serving the eRG) to the selected AMF (e.g., serving the WTRU) along with the WTRU's NAS. At 1503, the selected AMF (serving the WTRU) retrieves CPN information from the AMF (serving the eRG) based on the received AMF ID. At 1504, the selected AMF may provide information to the WTRU, which may trigger eRG configuration at 1505. In one example, the trigger is based on WTRU information, capabilities, services requested by the WTRU, and / or policies. This information triggers that the eRG needs to be configured so that it can support the requested services. Thus, a configuration request is sent to the AMF serving the eRG. The AMF serving the eRG may send a configuration message to the eRG to set up control information, policies, and / or user plane.
[0113] FIG. 16 illustrates an example of an aspect of a WTRU registration process, such as part of eRG configuration / determination. In this example scenario, there may be a base station 1621, a selected AMF 1622, an eRG_AMF 1623, and a CPN mapping function 1624. As shown, at 1601, the base station may select an AMF (e.g., selected_AMF) based on the WTRU's 5G-S-TMSI. At 1602, there may be a NAS message (e.g., related to AMF selection) from the base station to the selected AMF. At 1603, interaction between the selected AMF and the "CPN mapping function" may determine the eRG_AMF. At 1604, the selected AMF (serving WTRU) retrieves information of the CPN from the AMF (serving eRG). At 1605, the selected AMF may provide the CPN information to the WTRU. At 1606, the selected AMF may trigger eRG configuration (e.g., the AMF serving the eRG may configure the eRG).
[0114] Referring again to FIG. 14, at 1402, the WTRU may send a NAS registration with its CPN_PLMN_ID as part of the updated "5GMM Capabilities" in a registration request message. In some cases, the registration request message may be forwarded to the selected AMF. The "5G CPN User" capability may indicate multi-RAT, such as dual connectivity to the CPN (5GNR and WiFi), and / or CPN guest mode capability. See Table 4 for example details of 5GMM information elements that include capability information as described herein.
[0115] [Table 4]
[0116] The purpose of the 5GMM Capabilities information element may be to provide the network with information about aspects of the WTRU related to interaction with the 5GCN or EPS. The content may affect how the network handles the operation of the WTRU.
[0117] The "CPN Multi-RAT and Guest Access" bit may indicate the capability of the WTRU to connect to a PRAS / eRG over 5GNR or WiFi and / or the capability of the WTRU to operate in guest mode, which the 5G system uses for a seamless and flawless user experience regardless of whether the user is staying in a RAT or the user is moving between RATs. The 5G system may use this capability of the WTRU to prevent or allow the (guest) WTRU to discover and / or use services provided by eRGs over the CPN.
[0118] The AMF may receive one or more NAS messages from the WTRU via the N1-WTRU interface and associate the WTRU's context with the eRG's context based on the eRG's ID or CPN_PLMN_ID. The AMF may store "5G CPN User" capabilities for 5G CPN operation. The AMF may obtain the "5G CPN User" subscription data as part of the user subscription data from the UDM during the eRG registration procedure using the Nudm_SDM service.
[0119] The AMF may determine whether the WTRU is authorized to use the 5G CPN service based on the WTRU's CPN capabilities and "CPN service authorization" included in the subscription data received from the UDM. The AMF may store the authorized "5G CPN user" capabilities.
[0120] The AMF may send the authorized "5G CPN user" capabilities for 5G CPN operation to the PCF. Based on the 5G CPN user capabilities received from the AMF, the PCF may provide QoS parameters for the remote WTRU and / or service-specific QoS to the AMF. The AMF may store such information as part of the WTRU context.
[0121] At 1403, the AMF may initiate a session setup with the PRAS (e.g., relayed from the NG-RAN and eRG). The message may comprise a registration accept NAS message and one or more other elements. The message may carry one or more PDU session setup requests, with each PDU session addressed with a "PDU Session ID". The message may also carry uplink TEIDs for all PDU sessions. Additionally, the AMF may provide the WTRU with CPN local service information, such as a local DNN. Additionally / alternatively, the AMF may send an NGAP message that may include an "Initial Context Setup Request" and a "Registration Accept" sent to the PRAS (e.g., relayed from the NG-RAN and eRG) if the WTRU is authorized to use "5G CPN User Authorization" information including one or more of the following: QoS details as part of the WTRU context, and / or whether the WTRU is authorized to connect to the PRAS / eRG via multi-RAT.
[0122] The purpose of the "Initial Context Setup" procedure may be to establish the required entire initial WTRU context in the PRAS / eRG, when needed, including a PDU session context from the eRG (e.g., a PDU session to the 5GC), security keys, mobility restriction list, WTRU radio capabilities, and / or WTRU security capabilities.
[0123] At 1404, the PRAS may send a registration accept message to the WTRU, which may include WTRU settings such as radio parameters used in the CPN. To illustrate this, Table 5 shows example details of a registration accept message.
[0124] [Table 5-1]
[0125] [Table 5-2]
[0126] The WTRU may use the received "CPN_User_Info" to configure itself.
[0127] The following WTRU configuration may be performed: UPF configuration between the WTRU and the PRAS / eRG, which may include flow control, fast retransmission of PDCP PDUs lost due to radio link outage, discarding redundant PDUs, retransmission data indication, and status reporting; a local DN name may be configured in the WTRU, and the WTRU may select a local DN name to join the CPN; a list of available CPN services, such as 5G LAN, direct communication, direct discovery, etc., may be used by the WTRU; and / or the WTRU may request a specific QoS for a specific service data flow.
[0128] At 1405, the AMF may send the authorization information of the WTRU to the eRG via NAS signaling (e.g., N1-eRG interface), such as a UCU with a CPN configuration IE. This CPN configuration may be used to configure the PRAS using the F1 interface between the PRAS and the eRG in a manner similar to the central unit and distributed unit architecture (e.g., as described herein with respect to the gNB-DU and gNB-CU in the NG-RAN architecture). For example, at 1406, there may be internal configuration, relay setup, and / or addressing of any default bearers, which may be performed between the eRG and the PRAS. The maximum number of PRASs connected to an eRG may only be limited by a given implementation. The F1 interface may support signaling exchange and data transmission between endpoints, separate protocol layers depending on the splitting selection used, and may enable exchange of signaling associated with the WTRU and signaling not associated with the WTRU.
[0129] For example, the one or more internal settings may include F1 interface management functions, which may include F1 setup, eRG settings update, PRAS settings update, error indication, and / or reset functions.
[0130] For example, one or more internal configurations may include system information management functions. For example, the PRAS may be responsible for scheduling and broadcasting system information. For system information broadcasting, encoding of NR-MIB and SIB1 may be performed by the PRAS, while encoding of other SI messages may be performed by the eRG. The F1 interface also provides signaling support for on-demand SI delivery and enables WTRU power saving.
[0131] For example, one or more internal configurations may include F1 WTRU context management functions, which may be responsible for establishing and modifying the necessary WTRU context. The establishment of the F1 WTRU context may be initiated by the eRG, and the PRAS may accept or reject the establishment based on admission control criteria. In addition, an F1 WTRU context modification request may be initiated by either the eRG or the PRAS. The receiving node (e.g., the eRG or PRAS) may accept or reject the modification. The F1 WTRU context management functions may also be used to establish, modify, and release Data Radio Bearers (DRBs) and Signaling Radio Bearers (SRBs).
[0132] For example, the one or more internal configurations may include an RRC message forwarding function, which may be responsible for forwarding RRC messages from the eRG to the PRAS and vice versa.
[0133] At 1407 and 1408, the WTRU may perform a capability information exchange (eg, the WTRU receives the inquiry and responds with its capability information).
[0134] At 1408, the WTRU may inform the 5GC (e.g., through the PRAS) of its capabilities to support features such as multi-RAT, ProSE, and / or other available / supported services in response to a user capability inquiry received from / via the PRAS. Table 6 shows an example of WTRU network capabilities.
[0135] [Table 6]
[0136] The 5GC / AMF may use the capability information for: multi-RAT and ProSE, where the AMF is aware of the WTRU's multi-RAT and ProSE capabilities, and / or the 5GC / AMF provides an indication to the eRG about the WTRU authorization status for 5G ProSe direct discovery / ProSe direct communication or multi-RAT communication; and / or the 5GC may also instruct the eRG to set up PDU sessions distributed across multiple RATs based on measurements and available QoS, and / or transition the WTRU's connection from D2D to be internally routed through the eRG.
[0137] At 1409, a PDU session may be established between the WTRU and the 5GC. In one example, this may be different from the PDU session establishment procedure for connecting two WTRUs with a local network or CPN.
[0138] At 1410, after the PDU session between the WTRU and the 5GC is set up, the 5GC may perform one or more of the following actions: identify the eRG and associated AMF based on the CPN information of which WTRU is connected; the AMF instructs the eRG via the N1 interface to modify and activate the existing PDU session between the eRG and 5GC so that the WTRU's PDU session can be supported; and / or the AMF may send the 5GC WTRU identity and associated PDU session (e.g., PDU session details), the existing PDU session between the eRG and 5GC, and / or authorized QoS, etc. to the eRG via the N1 interface.
[0139] For PDU session establishment for local breakout in the CPN, after the WTRU is registered and connected to the CPN, the WTRU can establish a PDU session to access devices and services in the CPN via the eRG as described herein. When the WTRU establishes a PDU session to the DN, it can also set up a default non-Guaranteed Bit Rate (GBR) QoS flow without packet filters to carry the WTRU's traffic to the DN and back. Both the WTRU (e.g., WTRU-initiated) and the network (e.g., network-initiated) can create additional QoS flows with different QoS characteristics than the default QoS flows using a WTRU-initiated or network-initiated PDU session modification request to the SMF.
[0140] 17 illustrates an example of establishing a default PDU session within a CPN (e.g., toward a local DDN). In this example scenario, there may be a WTRU 1721, a PRAS 1722, an eRG 1723, a 5G-AN 1724, and a 5GC / AMF / SMF 1725.
[0141] In 1701, the WTRU may initiate a PDU session establishment procedure, including sending a request by providing the PRAS / AMF with the following IEs that may be included in the SMF's "nsm-pdusession_CreateSM-Context" message, such as the WTRU's SUPI (Subscriber Permanent Identifier); target DNN (Data Network Name), which is a local DNN name provided to the WTRU during registration; service name or service identifier, which is a service in the local DNN; authorization information for using the service; anType (Access Network Type), which is a CPN_ID or CPN_NAME; and / or sNssai (Single Network Slice Service Assistance Identifier). Table 7 shows an example message of a PDU establishment request used by the WTRU.
[0142] [Table 7]
[0143] At 1702, the AMF may perform SMF / PCF selection. UPF selection may then be made. Once selected, the SMF may obtain WTRU subscription details from the UDM and PCF. Based on the "target DNN" and "anTYPE", it may be determined that a local UPF in the eRG needs to be programmed. The SMF may identify the correct AMF for the eRG and obtain the UPF information in the eRG.
[0144] At 1703, the SMF may request that the AMF for the eRG program the local UPF. The SMF may formulate the equivalent of a Packet Forward Control Packet (PFCP) session establishment request to program the local UPF to create a Session Management (SM) context (e.g., PDU session) for the WTRU. In one example, a pseudo N4 session with a remote local UPF may exist between the eRG, 5G-AN, and 5GC / AMF / SMF (e.g., N4 session establishment / modification).
[0145] At 1704, the SMF may send configuration information indirectly (e.g., via the AMF of the eRG and the N1 interface to the eRG). In some cases, the information may take into account QoS configuration for PDU sessions and default QoS flow establishment, which triggers eRG configuration. The eRG configuration may include SDF templates for UPF in the eRG, DL and UL traffic classification (e.g., switching parameters), and / or QoS rules in the eRG. In one example, the QoS rules may include queuing and scheduling, including application to GBR and non-GBR WTRU traffic, such as UL / DL bandwidth, delay, traffic priority, and the like; and / or marking / remarking, which marks mobile traffic (e.g., sets DSCP of packets) so that traffic priority and QoS can be respected at the DN and gNB as the traffic egresses towards the local DN (e.g., UL traffic) and PRAS (e.g., DL traffic). In some cases, this user plane configuration information may be sent to the eRG via N1. In some cases, the configuration information may relate to the PDU session of the WTRU.
[0146] The eRG may configure one or more of the following: an N3 GTP-U tunnel towards the local UPF, which sets up an IP address for the N3 GTP-U tunnel towards the local UPF and provides that information to the PRAS; a QFI to some value that allows identifying a default QoS flow from the WTRU to the DN; an UL and DL WTRU-AMBR (Aggregated Maximum Bit Rate) at the PRAS, which will cause the PRAS to drop any non-GBR AMBR traffic for the WTRU that exceeds the limits for UL and DL; and / or the WTRU's gTP-TEID or TEID_cn (Tunnel Endpoint ID Core Node) at the PRAS, which is information that the PRAS can use to forward the WTRU's UL traffic to the local UPF for the DN.
[0147] The SMF may request the local UPF to assign an IP address to the WTRU, which may obtain the assigned IP address and send it to the WTRU.
[0148] At 1705, the SMF may configure the PRAS and the WTRU by sending one or more messages, such as an N2 Request and / or a PDU Session Update (e.g., via an N1 message from the AMF to the PRAS with the WTRU). For example, one message may include the following parameters: QoS configuration for PDU session and default QoS flow establishment, such as a QoS profile to the PRAS, QoS rules to the WTRU (e.g., queuing and scheduling for application to GBR and non-GBR WTRU traffic, such as UL / DL bandwidth, latency, traffic priority, etc.), and / or UL traffic classification in the WTRU.
[0149] The SMF can advise the WTRU (eRG) via the N1 HTTP / 2 interface to set up a packet filter to classify UL traffic to the local DN, which is associated with the CPN that is a local DN service.
[0150] The WTRU (WTRU in a CPN) may use the same QFIs used to identify the default QoS flow for the PDU session. These QFIs are configured by the eRG, which may forward them to the SMF and then send them to the WTRU.
[0151] In some cases, the SMF may send configuration to the WTUR, and may send configuration to the eRG, such as UL / DL session AMBR to the WTRU (eRG), which the WTRU may apply to its SDF UL traffic and drop traffic that exceeds the limit.
[0152] The IP address of the WTRU (WTRU in CPN) as obtained in step 4 may be sent to the WTRU (WTRU in CPN) by the SMF.
[0153] Alternatively, the QoS profile for the PRAS may be sent to the eRG in step 4 and / or the eRG may configure the PRAS.
[0154] At 1706, the RRC configuration may be used to establish a radio bearer (DRB) between the WTRU and the PRAS. The DRB may be associated with a previously established N3 GTP-U tunnel toward a local UPF in the eRG.
[0155] The WTRU can now transmit the UL packet to the DN at 1707. In one example, the WTRU has a default QoS flow to match its UL traffic to the DRB (Data Radio Bearer) identified by the QFI to the PRAS, and / or the PRAS can know the UPF's IP address and the WTRU's TEID_cn to forward the UL traffic to the local UPF and DN. Upon receiving the packet, the eRG (also) must determine where the packet should be directed based on information from the WTRU and / or from previous configuration, effectively acting as a switch.
[0156] At 1708, the eRG may first set up an N4 session between the local UPF and the SMF by sending the equivalent of a Packet Forwarding Control Packet (PFCP) session establishment request to create a session management (SM) context (e.g., a PDU session) for the WTRU.
[0157] At 1709, downlink (DL) setup information may be sent from the 5GC / AMF / SMF to the eRG. The UPF may not yet know the AN_Tunnel on the PRAS (e.g., PRAS IP address and TEID_an of the WTRU). The SMF may update the AN_Tunnel information for the SM context on the local UPF using the provided AN_Tunnel information of the PRAS so that the UPF can start sending DL traffic to the WTRU via the PRAS, and / or the AMF may invoke an Nsmf-PDU_Session_UpdateSMContext service call of the SMF, so that the SMF can update the SM context on the UPF for the AN_Tunnel for the eRG, and the SMF may send this information to the eRG by identifying the AMF for the eRG via the N1 interface. In one example, there may be a pseudo N4 session (e.g., NF session establishment / modification procedure) with a remote local UPF.
[0158] At 1710, DL data may be directed from the eRG to the WTRU based on one or more aspects of the previous configuration.
[0159] As described herein, a higher layer may refer to one or more layers in a protocol stack or a particular sublayer within a protocol stack. The protocol stack may be comprised of one or more layers in a WTRU or a network node (e.g., eNB, gNB, other functional entity, etc.), where each layer may have one or more sublayers. Each layer / sublayer may be responsible for one or more functions. Each layer / sublayer may directly or indirectly communicate with one or more of the other layers / sublayers. In some cases, these layers may be numbered as Layer 1, Layer 2, and Layer 3. For example, Layer 3 may be comprised of one or more of the following: Non-Access Stratum (NAS), Internet Protocol (IP), and / or Radio Resource Control (RRC). For example, Layer 2 may be comprised of one or more of the following: Packet Data Convergence Control (PDCP), Radio Link Control (Radio Link Control, RLC), and / or Medium Access Control (MAC). For example, Layer 3 may consist of physical (PHY) layer type operations. The higher the layer number, the higher the layer is relative to other layers (e.g., Layer 3 is higher than Layer 1). In some cases, the above examples may be referred to as layers / sublayers themselves, regardless of layer number, and may be referred to as higher layers as described herein. For example, higher layers may refer to one or more of the following layers / sublayers, from highest to lowest: NAS layer, RRC layer, PDCP layer, RLC layer, MAC layer, and / or PHY layer. Any reference to higher layers herein in connection with a process, device, or system will refer to a layer that is higher than the layer of the process, device, or system. In some cases, reference to higher layers herein may refer to functions or operations performed by one or more layers described herein.In some cases, references herein to higher layers may refer to information transmitted or received by one or more layers described herein. In some cases, references herein to higher layers may refer to configurations transmitted and / or received by one or more layers described herein.
[0160] Although the features and elements are described above in certain combinations, one skilled in the art will understand that each feature or element may be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.
Claims
1. 1. A method implemented by an extended residential gateway (eRG), the method comprising: receiving configuration information from a session management function (SMF) via an N1 interface, the configuration information including switching information that determines whether one or more packets from a first wireless transmit / receive unit (WTRU) go to a customer premises network (CPN) or a core network, the eRG being operatively connected to the CPN, the core network, and the first WTRU; receiving, from the first WTRU, a packet associated with a PDU session established by the first WTRU; and transmitting the packet to the CPN or the core network based on the configuration information.
2. The method of claim 1 , wherein the configuration information is associated with the PDU session established by the first WTRU.
3. 2. The method of claim 1, wherein the configuration information further comprises packet forwarding information for the first WTRU in the CPN to forward the packet to a second WTRU in the CPN.
4. 2. The method of claim 1, wherein the configuration information further comprises QoS parameters associated with the PDU session.
5. 2. The method of claim 1, wherein the configuration information further comprises QoS information including a guaranteed bit rate (GBR) associated with the PDU session.
6. 2. The method of claim 1, wherein the configuration information further comprises QoS information including a buffer size associated with the PDU session.
7. An enhanced residential gateway (eRG), comprising: means for receiving configuration information from a session management function (SMF) over an N1 interface, the configuration information including switching information that determines whether one or more packets from a first wireless transmit / receive unit (WTRU) go to a customer premises network (CPN) or a core network, the eRG being operatively connected to the CPN, the core network, and the first WTRU; means for receiving, from the first WTRU, a packet associated with a PDU session established by the first WTRU; and means for transmitting the packet to the CPN or the core network based on the configuration information.
8. The eRG of claim 7 , wherein the configuration information is related to the PDU session established by the first WTRU.
9. The eRG of claim 7 , wherein the configuration information further includes packet forwarding information for the first WTRU in the CPN to forward the packet to a second WTRU in the CPN.
10. The eRG of claim 7 , wherein the configuration information further includes QoS parameters associated with the PDU session.
11. The eRG of claim 7, wherein the configuration information further includes QoS information including a guaranteed bit rate (GBR) associated with the PDU session.
12. The eRG of claim 7, wherein the configuration information further includes QoS information including a buffer size associated with the PDU session.
Citation Information
Patent Citations
Data transmission link establishment method and apparatus, and computer-readable storage medium
EP3989673A1
Establishing a new QOS flow for a data connection
WO2021052573A1
