Reporting connectivity status of non-3GPP devices to a network

Abstract

A primary device configured to communicate with a radio access network (RAN) according to a cellular radio access technology (RAT) determines (505B) respective connectivity status for each of multiple secondary devices configured to communicate with the RAN only via the primary device. The primary device transmits (511, 520), to the RAN, a message indicating the respective connectivity status for each of the multiple secondary devices.

Description

PATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00PREPORTING CONNECTIVITY STATUS OF NON-3GPP DEVICES TO A NETWORKCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to and the benefit of the filing date of provisional U.S. Patent Application No. 63 / 718,517 entitled “Reporting Connectivity Status of Non-3GPP devices to a Network,” filed on November 8, 2024. The entire content of the provisional application is hereby expressly incorporated herein by reference.FIELD OF THE DISCLOSURE

[0002] This disclosure relates generally to wireless communications and, more particularly, to reporting the status of non-3GPP devices operating “behind” 3GPP devices such as user equipment units (UEs) or residential gateways (RGs).BACKGROUND

[0003] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0004] The 3rd Generation Partnership Project (3GPP) organization contemplates scenarios in which a non-3GPP device connects to a 3GPP device such as a user equipment (UE) or a fifth generation residential gateway (5G-RG), and the 3GPP device conveys information related to the non-3GPP device to a Session Management Function (SMF) operating in a core network (CN) of a cellular communication system. The SMF in turn conveys this information to a Policy Control Function (PCF) responsible for quality of service (QoS) policy decisions.

[0005] Several aspects of these scenarios remain unclear. For example, when the non-3GPP device disconnects from the 3GP device, the actions of the 3GPP device or the network (e.g., the CN) are unclear. More specifically, if the 3GPP device does not inform the network of the disconnection, the network cannot update the QoS policy. One such update could be providing a higher level of QoS to the 3GPP device, which now serves fewer non-3GPP devices.PATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P

[0006] Further, it is not clear which approaches to the problem of notifying the network would generate a smaller signaling overhead. For example, it is not clear whether and when the 3GPP device should notify the network of changes in the configuration of a non-3GPP device connected to the 3GP device. Further it is not clear when the 3GPP device should convey, to the network, the device identifier of a non-3GPP device. Still further, it is not clear how the network should support scenarios in which the 3GPP device is a 5G residential gateway (5G-RG).SUMMARY

[0007] An example embodiment of the techniques of this disclosure is a method implemented in a primary device configured to communicate with a radio access network (RAN) according to a cellular radio access technology (RAT). The method comprises determining respective connectivity status for each of a plurality of secondary devices configured to communicate with the RAN only via the primary device; and transmitting, to the RAN, a message indicating the respective connectivity status for each of the plurality of secondary devices.

[0008] Another example embodiment of these techniques is a method implemented in a primary device configured to communicate with a RAN according to a cellular RAT. The method comprises: determining that a secondary device configured to communicate with the RAN only via the primary device has become inactive; and transmitting, the RAN, a message indicating inactivity of the secondary device.

[0009] Another example embodiment of these techniques is a device comprising processing hardware and a transceiver. The device is configured to implement one of the methods above.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Fig. 1 is a block diagram of an example communication system, such as a fifthgeneration system (5GS), that provides connectivity to a user equipment (UE) according to a certain set of telecommunication standards (e.g., 3GPP), where the UE in turn provides connectivity to one or more devices (e.g., non-3GPP devices) operating “behind” the UE using other communication schemes (e.g., wireless local area network (WLAN) standards or wireless personal area network (WPAN) standards);PATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P

[0011] Fig. 2A is a messaging diagram of an example scenario in which a UE reports, to the network, a list of non-3GPP devices active behind the UE;

[0012] Fig. 2B is a messaging diagram of an example scenario in which a UE reports, to the network, activity status for one or more non-3GPP devices operating behind the UE;

[0013] Fig. 3 is a service-based representation of the 5GS architecture, including the overall non-roaming reference architecture of the policy and charging control framework for the 5GS;

[0014] Fig. 4 is a reference-point based representation of the 5GS architecture, including overall non-roaming reference architecture of the policy and charging control framework for the 5GS;

[0015] Fig. 5A is a flow diagram of an example method for reporting the active status for one or more non-3GPP devices, which can be implemented in the UE of Fig. 1;

[0016] Fig. 5B is a flow diagram of an example method for reporting the activity status (e.g., active, inactive) for one or more non-3GPP devices, which can be implemented in the UE of Fig. 1;

[0017] Fig. 5C is a flow diagram of an example method for reporting the activity status for a non-3GPP device in response to detecting a change in the activity status of the non-3GPP device, which can be implemented in the UE of Fig. 1;

[0018] Fig. 5D is a flow diagram of an example method for reporting the active status for one or more non-3GPP devices based on a UE-centric event, such as detecting inadequate QoS associated with the communication between the non-3GPP device and the network, which can be implemented in the UE of Fig. 1;

[0019] Fig. 5E is a flow diagram of an example method for reporting the activity status for a non-3GPP device based on a periodic timer, which can be implemented in the UE of Fig. 1;

[0020] Fig. 5F is a flow diagram of an example method for reporting the activity status for a non-3GPP device in response to a request from the network, which can be implemented in the UE of Fig. 1;

[0021] Fig. 6A is a flow diagram of an example method for reporting inactivity of one or more non-3GPP devices, which can be implemented in the UE of Fig. 1;PATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P

[0022] Fig. 6B is a flow diagram of an example method for reporting, in a shared reporting message, activity statuses for multiple non-3GPP devices, which can be implemented in the UE of Fig. 1;

[0023] Fig. 7A is a flow diagram of an example method for receiving, from a UE, an indication of the active status for one or more non-3GPP devices, which can be implemented in the SMF of Fig. 1; and

[0024] Fig. 7B is a flow diagram of an example method for receiving, from a UE, the activity status (e.g., active, inactive) for one or more non-3GPP devices, which can be implemented in the SMF of Fig. 1.DETAILED DESCRIPTION OF THE DRAWINGSOverview

[0025] Generally speaking, a 3GPP device, such as a UE or a 5G-RG, provides cellular service to one or more non-3GPP devices connected to the 3GPP device via a wireless local area network (WLAN) connection such as WiFi®, a wireless personal area network (WPAN) connection such as Bluetooth®, or ultra-wideband (UWB) for example. An application layer mechanism outside the scope of 3GPP can assign a set of non-3GPP device identifiers to the3GPP device, for allocation to the non-3GPP devices, and the 3GPP device sets up one or more protocol data unit (PDU) sessions with the network (e.g., based on User Equipment Route Selection Policy (URSP) rules or the local configuration of the UE).

[0026] The 3GPP device can be referred to as primary device, because it is configured to communicate with a RAN according to a certain RAT, and the one or more non-3GPP devices behind the 3GPP device can be referred to as secondary devices, because these devices can communicate with the RAN only via the primary device.

[0027] A non-3GPP device can be considered active when the non-3GPP initiates exchange of data with the network (e.g., by sending a request to connect to the 3GPP device or sending data to the 3GPP device). An active non-3GPP device may become inactive when the non-3GPP device has finished its data session. The 3GPP device can detect that the UE is inactive using implementation- specific means (e.g., when the device has not exchanged data for a certain periodPATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P of time). The 3GPP determines and reports, to the network, the connectivity status, such as the activity status, for the one or more non-3GPP devices.

[0028] In addition to sending the device identifier of a non-3GPP device to the network when the non-3GPP device connects to the 3GPP device, according to the techniques discussed below, the 3GPP device notifies the network of other changes in the connectivity status. For example, the 3GPP device can inform the network of disconnecting from a non-3GPP device, and the network can update the quality of service (QoS) policy and, for example, provide a higher level a QoS to the 3GPP device that now serves fewer non-3GPP devices.

[0029] Further, although it is possible for the 3GPP device to transmit a non-access stratum session management (NAS SM) message every time there isa a change in the configuration of connected non-3GPP devices, this approach may result in significant signaling overhead and cause unnecessary power consumption. The techniques discussed below allow the 3GPP device to notify the network efficiently.

[0030] As discussed below, a 3GPP device can specify a device identifier in a PDU Session Establishment Request message or a PDU Session Modification Request message. Further, the 3GPP device can include the device identifier and the user plan address for each non-3GPP device that is connected and actively exchanging information with the relevant PDU session, in the PDU Session Modification request message.

[0031] Thus, the 3GPP can initiate a PDU Session Modification procedure by transmitting a NAS message (N1 SM container (PDU Session Modification Request (PDU session ID, Packet Filters, Operation, Requested QoS. Segregation, 5GSM Core Network Capability, Number Of Packet Filters, [URSP ride enforcement reports], [Always-on PDU Session Requested], [Requested Non-3GPP Delay Budget], [non-3GPP Device Connection Information])), PDU Session ID, UE Integrity Protection Maximum Data Rate, [Port Management Information Container) message.

[0032] If the 3GPP device supports identification of traffic of a connected non-3GPP device, and the 3GPP device determines that the QoS differentiation for a connected non-3GPP device is required, the 3GPP device includes a list of non-3GPP device identifiers and their associated user plane addresses for all non-3GPP devices that are connected and active (for the PDU session).PATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00PThe 3GPP device can include this information in a non-3GPP Device Connection Information field, within a PDU Session Modification Request. The 3GPP device can determines QoS differentiation and whether a non-3GPP device is active using a scheme specific to the 3GPP device, in some implementations.Example system

[0033] Referring to Fig. 1, an example cellular communication system 100 can be for example a fifth-generation system (5GS), in which a device 102 communicates with a radio access network (RAN) 105 using a certain cellular radio access technology (RAT) such as Evolved UMTS Terrestrial Radio Access (EUTRA) associated with Long-Term-Evolution (LTE) cells, 5G new radio (NR) associated with NR cells, a 6G RAT, etc. The device 102 in these examples can access the cellular communication system 100 according to a certain set of telecommunication standards (e.g., 3GPP), and can be understood as a 3GPP device 102 (referred to below simply as “the device 102”). The device 102 can be for example a user equipment (UE) or a 5G residential gateway (5G-RG).

[0034] The device 102 can provide connectivity between one or more non-3GPP devices, such as non-3GPP devices 130A and 130B, and the cellular communication system 100. The non-3GPP devices 130A and 130B in general cannot access the RAN 105 directly. Instead, the 3GPP devices 130A and 130B can connect to the device 102 via such WLAN, WPAN, etc. technologies as WiFi™, Bluetooth™, UWB, etc. The device 102 includes a 3GPP modem 110 to communicate with the RAN 105 and a non-3GPP modem 111 to communicate with the non- 3GPP devices 130 A and 130B. The device 102 thus can support protocol data unit (PDU) sessions established between the devices 130A and 130B and the core network of the cellular communication system 100.

[0035] In operation, the device 102 can receive, using an application-layer mechanism, a set of non-3GPP device identifiers. An Application Function (AF) 158 can update a Unified Data Repository (UDR) UDR 152 with the QoS profile corresponding to the non-3GPP device identifiers which the device 102 is authorized to use. The device 102 can assign a non-3GPP device identifier to a non-3GPP device in order to provide differentiated QoS. For example, the 3GPP device 102 can assign device identifier ID1 to the non-3GPP device 130 A and device identifier ID2 to the non-3GPP device 130B. The device 102 sets up one or more PDU sessionsPATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P with the network (e.g., based on UE route selection policy (URSP) rules or UE local configuration).

[0036] The non-3GPP device 130A or 130B can be considered active when it initiates exchange of data with the network 100 (e.g., by sending a request to connect to the device 102 or sending data to the device 102). An active non-3GPP device may become inactive when it has completed its data session. The device 102 may detect that the non-3GPP device 130A is inactive using any suitable techniques (e.g., by detecting when the non-3GPP device 130A has not exchanged data with the network for a certain period of time).

[0037] With continued reference to Fig. 1, the RAN 105 can include any suitable number of base stations implemented as eNBs, gNBs, etc. The core network can include such control-plane functions as an Access & Mobility Management Function (AMF) 164, a Session Management Function (SMF) 166, a Policy Control Function (PCF) 160, a Unified Data Repository (UDR) 152, and application function (AF) 158. At the user plane, the core network can include a User Plane Function (UPF) 170 connecting the RAN 105 to a data network 130. These and other functions of a core network (CN) are discussed in more detail with reference to Fig. 3, where similar functions are labeled with similar reference numbers that share two least significant digits (e.g., UDR 352 is similar to the UDR 152, the SMF 366 is similar to the SMF 166).Example scenarios and methods for reporting the connectivity status

[0038] Next, example scenarios in which a 3GPP device reports the connectivity status for one or more non-3GPP devices are discussed with reference to Figs. 2 A and 2B, followed by a discussion of several example methods. Generally speaking, similar events in Figs. 2A-7B are labeled with similar reference numbers that share two least significant digits, with differences discussed below where appropriate. For simplicity, in the discussion of Figs. 2A-7B below, the 3GPP device 102 is referred to as “the UE 102.” However, as discussed above, the 3GPP device 102 can also be a 5G-RG device or another suitable 3GPP device.

[0039] The connectivity status of the non-3GPP device 130A can indicate whether this device is connected to the UE 102. The connectivity status also can be (or include) an activity status that indicates whether the device is exchanging information with the cellular network via the UE 102. PDU sessions in general last for a relatively long time, and the non-3GPP device 130A atPATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P different stages can connect, become active, become inactive, and then disconnect. In addition to reporting when the non-3GPP device 130A has become active, it is desirable for the UE 102 to indicate, to the network, that one or more of the non-3GPP devices 130A, 130B, etc. are no longer using the PDU session because these devices are now inactive or disconnected. The network can use this information to modify the QoS policy in order to serve the devices that are currently active.

[0040] In the scenarios of Fig. 2A and Fig. 2B, when the 3GPP device 102 determines to send device connection information or connectivity status to the network in a NAS SM message (e.g., PDU session establishment request, PDU session modification request, or PDU session release request) for a specific PDU Session identified by a PDU Session ID, the 3GPP device 102 includes a list of non-3GPP device identifiers and their associated user plane addresses for all non-3GPP devices that are connected and active (for the PDU session).

[0041] In the scenario of Fig. 2A, the UE 102 can initiate 205 a status report transmit this information in an NAS SM message and based on the following conditions: (i) the UE 102 has assigned 203 the non-3GPP device identifier to one of the non-3GPP devices 130A that are served by the UE 102; (ii) the UE 102 has determined that a non-3GPP device is connected if the non-3GPP device is actively exchanging 202 data with the network; and (iii) the UE 102 has or will route the data for the traffic of the non-3GPP device identifier to the PDU session. The UE 102 transmits 220, to the SMF 166, the list of non-3GPP identifiers of connected and active non- 3GPP identifiers, along with the associated user-plane addresses.

[0042] In particular, when the UE 102 transmits 220 a PDU session modification request, the user plane address of a non-3GPP device can include the following information: (i) for the Ethernet PDU Session Type, the user plane address can be the MAC address and / or the VLAN tag ID that is associated with the Non-3GPP Device Identifier, (ii) for the IPv4 PDU Session Type, the user plane address is the IP Address and / or port ranges associated with the Non-3GPP Device Identifier, or (iii) for the IPv6 PDU Session Type, the user plane address is the IPv6 Address / prefix(sub) that is associated with the Non-3GPP Device Identifier to the SMF in PDU Session Modification procedure.

[0043] The UE 102 can implement any suitable scheme to determine when a particular non- 3GPP device (such as the non-3GPP device 130A) is active. For example, the UE 102 canPATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P determine that the non-3GPP device 130A is active when this device attempts to connect, or when this transmits or receives data from the network.

[0044] The SMF 166 stores the received list of all connected and active non-3GPP device identifiers, replacing the “old,” prior list (if any) with the new list. Further, the SMF 166 may send 224 a notification including the list of all connected and active non-3GPP device identifiers to other network functions, for example (i) to the PCF 160, if the PCF 160 subscribes to changes of the connected non-3GPP device information for managing UE policy and network resources, or (ii) to the CHF, if the CHF subscribes to changes of the connected non-3GPP device information for handling charging records.

[0045] In the scenario of Fig. 2A, the PCF 160 queries 230 the UDR 152 to determine the QoS policy, and the PCF 160 transmits 240, to the SMF 166, the updated QoS Policy including the relevant PCC rule. The SMF 166 and the UPF 170 perform 250 an N4 session management procedure to install N4 rules, and then the UE 102 and the PCF 160 perform 260 a UE Configuration Update procedure to install the URSP roles.

[0046] Now referring to Fig. 2B, when the UE 102 determines to send device connection information to the network in an NAS SM message (e.g., PDU session establishment request, PDU session modification request, or PDU session release request) for a specific PDU Session identified by a PDU Session ID, the UE 102 includes one or more non-3GPP device identifiers and the associated user plane addresses, along with the corresponding connectivity or activity status, similar to the scenario Fig. 2A .

[0047] In this scenario, the UE 102 determines 204 that the non-3GPP device 130A becomes inactive. The UE 102 102 initiates 205 a status report and transmits 221, to the SMF 166, a message that includes the non-3GPP identifier of the non-3GPP device and the user-plane address of the non-3GPP device 130A. The SMF may send 225, to the PCF 160 or the CHF, a notification including the list of all disconnected non-3GPP device identifiers.

[0048] Importantly, the scenario of Fig. 2B, the UE 102 can indicate 221 not only active devices but also inactive devices. When the non-3GPP device 130A is no longer active, the UE 102 can use 221 a NAS SM message to indicate that the device identifier associated with thePATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P non-3GPP device 130 A is no longer active, and the SMF 166 can relay this information to other network functions such as the PCF and CHF.

[0049] In some implementations or scenarios, the UE 102 transmits 221 a PDU session release request rather than a PDU Session Modification Request to send device identifier information if, for example, the UE 102 intends to signal that all the non-3GPP devices associated with the PDU session have become inactive. Alternatively, the network can regard all the non-3GPP devices as disconnected if the associated PDU session is released.

[0050] Fig. 3 is a service-based representation 300 of the 5GS architecture, which the system of Fig. 1A can implement. In the representation 300, the overall non-roaming reference architecture of the policy and charging control (PCC) framework for the 5GS includes components illustrated using solid lines, and the other components are illustrated using dashed lines. According to this representation, network functions enable other authorized network functions to access their services. The components that are outside the PCC framework include a Network Slicing Selection Function (NSSF) 302, a Network Repository Function (NRF) 306. a Unified Data Management (UDM) 308, an Edge Application Server Discovery Function (EASDF) 310, a Network Slice Specific Authentication and Authorization Function (NSAAF) 312, an Authentication Server Function (AUSF) 314, a Service Communication Proxy (SCP) 316, and a Network Slice Admission Control Function (NSACF) 318. The non-PCC architecture further includes the UE 102, the RAN 105, and a data network (DN) 330. An application server (AS) 190 operates in the DN 330.

[0051] The PCC framework in the architecture 300 includes a UDR 352, a Network Exposure Function (NEF) 354, a network data analytics function (NWDAF) 356, an Application Function (AF) 358, a PCF 360, a Charging Function (CHF) 362, an AMF 364, an SMF 366, and a User Plane Function (UPF) 370.

[0052] Fig. 4 is a reference-point based representation 400 of the 5GS architecture. In Fig. 4, the non-roaming reference architecture of the PCC framework for the 5GS is illustrated as blocks and connections with solid lines, and components and connections outside the PCC framework are illustrated using dashed lines.PATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P

[0053] Several techniques for triggering the NAS SM message to report connectivity status of non-3GPP device behind a UE or 5G-RG are discussed next.

[0054] Referring to a method 500A of Fig. 5 A, a 3GPP device such as the 3GPP device 102 can determine, at block 505A, that one or more non-3GPP devices behind the 3GPP device are active. At block 510, the 3GPP device generates a list of non-3GPP device identifiers corresponding to the active non-3GPP devices as well as the corresponding user-plane addresses (see Fig. 2A). At block 520, the 3GPP device transmits the message to the network.

[0055] According to a method 500B of Fig. 5B, a 3GPP device determines 505B the activity status for one or more non-3GPP devices connected to the 3GPP device. At block 511, the 3GPP device generates a message including a list of non non-3GPP device identifiers, corresponding user-plane addresses, and status indicators (e.g.. active, not inactive) (see Fig. 2B).

[0056] Fig. 5C is a flow diagram of an example method 500C, where a 3GPP device at block 505C determines that a non-3GPP device connected to the 3GPP device changes its activity status. When a non-3GPP device assigned to a non-3GPP device identifier becomes active or inactive, the 3GPP device at block 512 generates a NAS SM message. The generating and the transmitting of the NAS SM message can be consistent with the approaches illustrated in Figs. 2 A and 2B.

[0057] Fig. 5D is a flow diagram of an example method 500D. In this solution, the 3GPP device 102 decides (block 505D) when to send non-3GPP device identifier information. For example, the 3GPP device may decide to invoke a NAS SM message carrying non-3GPP device identifier information only when the QoS received by the device is inadequate.

[0058] Fig. 5E is a flow diagram of an example method 500E for reporting the activity status for a non-3GPP device based on a periodic timer. At block 505E, the 3GPP device detects timer expiration and proceeds to block 510, 511, or 512.

[0059] More specifically, here the 3GPP device periodically sends a NAS-SM message including non-3GPP device connection information to the network, as described with reference to Fig. 2A. The periodicity can be determined according to one of the following options: (i) a fixed value specified or “hard-coded” in the relevant specification; or (ii) a value the network provides in an NAS SM message. For example, the SMF 166 can indicate the periodic reportingPATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P timer for reporting connected non-3GPP devices in a NAS-SM message (e.g. PDU Session Establishment Accept message or PDU Session Modification Accept message) for a specific PDU session identified by a PDU Session ID; or (iii) a value the network provides in a mobility management (MM) message. For example, the AMF can indicate the periodic reporting timer for reporting connected non-3GPP devices in an MM message, e.g. Registration Accept message or a UE configuration update command message. In this case, the 3GPP device sends a UL NAS Transport message including a list of all connected non-3GPP device identifiers per PDU Session ID.

[0060] Fig. 5F is a flow diagram of an example method 500F for reporting the activity status for a non-3GPP device in response to a request. At block 505F, the 3GPP device receives, from the network, a request for device status information (e.g., the connectivity status) and proceeds to block 510, 511, or 512. According to this solution, the network requests the 3GPP device to send non-3GPP device connection information.

[0061] According to one such implementation, the SMF 166 or 366 sends, to the 3GPP device, a DL NAS Transport message including a reporting indication and a PDU Session ID, to request the 3GPP device to send information about all of the connected non-3GPP devices for a specific PDU Session identified by the PDU Session ID. When responding to the request message, the 3GPP device may send the list of all connected non-3GPP device identifiers in a NAS-SM message of the specific PDU Session (as Solution 1) or a UL NAS Transport message including a list of all connected non-3GPP device identifiers and its corresponding PDU Session ID.

[0062] According to another implementation, the SMF sends a DL NAS Transport message including a reporting indication, target non-3GPP device identifiers, and a target PDU Session ID in order to request the 3GPP device information pertaining to one or more specific non-3GPP device identifiers. When responding to the request message, the 3GPP device may send a list of target non-3GPP device identifiers and its corresponding connectivity status in a NAS-SM message of the specific PDU Session or a UL NAS Transport message including a list of target non-3GPP device identifiers, and their connectivity status, and target PDU Session ID.

[0063] Fig. 6A is a flow diagram of an example method 600A for reporting inactivity of one or more non-3GPP devices. At block 605A, a 3GPP device determines inactivity of one or morePATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P non-3GPP devices and, at block 621, transmits an indication that the one or more 3GPP device is inactive.

[0064] Fig. 6B is a flow diagram of an example method 600B for reporting, in a shared reporting message, activity statuses for multiple non-3GPP devices. At block 605B, a 3GPP device determines inactivity of one or more non-3GPP devices and, at block 622, transmits a shared message indicating the corresponding statuses. The single shared message can indicate, for example, that the non-3GPP device 130A is active, and that the non-3GPP device 130B is inactive.

[0065] Fig. 7 A is a flow diagram of an example method 700 A that can be implemented in a node of a core network such as the SMF 166 or 366 for example. At block 720, the SMF receives, from a 3GPP device, an indication of the active status for one or more non-3GPP devices. At block 724, the SMF transmits, to the PCF, a list of non-3GPP device identifiers and the corresponding user-plane addresses.

[0066] Fig. 7B is a flow diagram of another example method 700B that can be implemented in the SMF 166 or 366. At block 721, the SMF receives, from a 3GPP device, a list of tuples each including a non-3GPP device identifier, the corresponding user-plane address, and an activity status of the non-3GPP device. At block 725, the SMF transmits, to the PCF, a list of non-3GPP device identifiers, the corresponding user-plane addresses, and the corresponding activity statuses.Example QoS differentiation of traffic for a Non-3GPP Device Identifier

[0067] In an example scenario, QoS differentiation of traffic can apply to the traffic that originates from or is directed to a non-3GPP device. The non-3GPP device, or a UE, does not use NAS and is not authenticated by 5GC. The support of identification of traffic for non-3GPP devices connecting behind a 5G-RG can be implemented as specified in TS 23.316. The non- 3GPP device identifier is unique within the scope of the Subscription Permanent Identifier (SUPI) of the UE.

[0068] Regarding traffic identification, when a non-3GPP device connected to a UE, the UE may bind the non-3GPP device identifier to a non-3GPP device, for the traffic of non-3GPP devices that require differentiated QoS. This binding enables the 5G System to distinguishPATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P between the traffic generated by different non-3GPP devices connected through the same UE. How the UE identifies the non-3GPP device and binds the Non-3GPP Device Identifier to a non- 3GPP device can be implementation specific. Further, at any point in time, the non-3GPP device identifier can be bound to only one non-3GPP device. Still further, how the UE is configured with the maximum number of simultaneously active non-3GPP devices, and the enforcement of such a limit, if configured, can be implementation specific. Non-3GPP device identifier information can be stored in the UDR and can include a non-3GPP device identifier and QoS information.

[0069] Regarding session management enhancement, the UE can implement the following. For the traffic of non-3GPP devices requiring differentiated QoS: (i) for Ethernet PDU Session Type, the UE sends the Non-3GPP Device Identifier and the MAC address and / or the VLAN tag ID that is associated with the Non-3GPP Device Identifier to the SMF in PDU Session Modification procedure: (ii) for IPv4 PDU Session Type, the UE sends the Non-3GPP Device Identifier and the IP Address and / port ranges associated with the Non-3GPP Device Identifier to the SMF in PDU Session Modification procedure; and (iii) for IPv6 PDU Session Type, the UE sends the Non-3GPP Device Identifier and the IPv6 Address / prefix(sub) that is associated with the Non-3GPP Device Identifier to the SMF in PDU Session Modification procedure. When the UE reports non-3GPP Device Connection Information in PDU session Modification procedure, the UE includes non-3GPP Device Identifier and user plane address of each non-3GPP device that is connected and active for the concerned PDU session. QoS differentiation and policy control can be implemented as described in TS 23.503.Further implementations

[0070] According to some implementations, device identifiers are not used to determine if a particular network slice / DNN is available.

[0071] According to some implementations, the existing traffic descriptors in URSP are considered to be sufficient to achieve traffic differentiation, and thus there is no need for a new traffic descriptor corresponding to device identifier.PATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P

[0072] According to some implementations, no change to the PDU session establishment procedure is required to providing differentiated QoS for non-3GPP device connecting via a UE / 5G-RG.

[0073] According to some implementations, a provisioning mechanism of device identifiers is also used to configure the maximum number of device identifiers, and the enforcement is implemented in the UE or 5G-RG.

[0074] According to some implementations, the maximum number of simultaneously active non-3GPP devices that can be served by a UE or 5G-RG is limited to a certain fixed number.

[0075] The following list of examples reflects a variety of the embodiments explicitly contemplated by the present disclosure.

[0076] Example 1. A method implemented in a primary device configured to communicate with a radio access network (RAN) according to a cellular radio access technology (RAT), the method comprising: determining respective connectivity status for each of a plurality of secondary devices configured to communicate with the RAN only via the primary device; and transmitting, to the RAN, a message indicating the respective connectivity status for each of the plurality of secondary devices.

[0077] Example 2. The method of example 1, wherein the message includes a list of non- 3GGP device identifiers for the plurality of secondary devices.

[0078] Example 3. The method of example 2, wherein the message further includes userplane addresses for the plurality of secondary devices.

[0079] Example 4. The method of example 3, wherein the user-plane addresses include Internet Protocol (IP) addresses.

[0080] Example 5. The method of example 3 or 3, wherein the user-plane addresses include port ranges.

[0081] Example 6. The method of any of examples 2-5, wherein the list of non-3GPP device identifiers is included in response to determining that quality of service (QoS) differentiation is required for a secondary device included in the plurality of secondary devices.PATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P

[0082] Example 7. The method of any of the preceding examples, wherein: the primary device is a 3rd Generation Partnership Project (3GPP) device, and each of the plurality of secondary devices is a non-3GPP device.

[0083] Example 8. The method of any of the preceding examples, wherein the primary device is one of a user equipment (UE) or a 5G residential gateway (5G-RG).

[0084] Example 9. The method of any of the preceding examples, wherein the message is a protocol data unit (PDU) Session Modification Request.

[0085] Example 10. The method of any of the preceding examples, further comprising: transmitting, to the RAN, a PDU Session Establishment request including a respective non-3GPP device identifier for each of the plurality of secondary devices.

[0086] Example 11. The method of any of the preceding examples, wherein the message indicates that one of the plurality of secondary devices is active, and that another one of the plurality of secondary devices is inactive.

[0087] Example 12. The method of any examples 1-10. wherein the transmitting of the message is in response to determining that one of the plurality of secondary devices became active.

[0088] Example 13. The method of any of examples 1-10, wherein the transmitting of the message is in response to determining that the primary device is receiving inadequate QoS.

[0089] Example 14. The method of any of examples 1-10, wherein the transmitting of the message is in response to detecting expiration of a periodic timer.

[0090] Example 15. The method of any of examples 1-10, wherein the transmitting of the message is in response to receiving a request for the activity information from the network.

[0091] Example 16. The method of any of the preceding clams, wherein the connectivity status includes an activity status.

[0092] Example 17. The method of any of the preceding examples, wherein one or more of the plurality of secondary devices communicates with the primary device using a RAT of a wireless local area network (WLAN).PATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P

[0093] Example 18. The method of any of examples 1-16, wherein one or more of the plurality of secondary devices communicates with the primary device using a RAT of wireless personal area network (WPAN).

[0094] Example 19. The method of any of examples 1-16, wherein one or more of the plurality of secondary devices communicates with the primary device using a RAT associated with ultra- wideband (UWB) communications.

[0095] Example 20. A method implemented in a primary device configured to communicate with a radio access network (RAN) according to a cellular radio access technology (RAT), the method comprising: determining that a secondary device configured to communicate with the RAN only via the primary device has become inactive; and transmitting, the RAN, a message indicating inactivity of the secondary device.

[0096] Example 21. The method of example 20, wherein: the primary device is a 3rd Generation Partnership Project (3GPP) device, and the secondary device is a non-3GPP device.

[0097] Example 22. The method of example 20 or 21, wherein the secondary device communicates with the primary device using a RAT of a wireless local area network (WLAN).

[0098] Example 23. The method of example 20 or 21, wherein the secondary device communicates with the primary device using a RAT of wireless personal area network (WPAN).

[0099] Example 24. The method of example 20 or 21, wherein the secondary device communicates with the primary device using a RAT associated with ultra- wideband (UWB) communications.

[0100] Example 25. The method of any of examples 20-24, wherein the primary device is one of a user equipment (UE) or a 5G-RG.

[0101] Example 26. A device comprising: processing hardware; and a transceiver; the device configured to implement a method of any of the preceding examples.

[0102] The following description may be applied to the description above.

[0103] A user device in which the techniques of this disclosure can be implemented (e.g., the UE 102) can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, aPATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P health monitoring device, a drone, a camera, a media- streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an internet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0104] Certain embodiments are described in this disclosure as including logic or a number of components or modules. Modules may can be software modules (e.g., code stored on non- transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application- specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

[0105] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general-purpose processors or one or more specialpurpose processors.

[0106] As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A orPATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00PB is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present)

Claims

PATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00PCLAIMS:

1. A method implemented in a primary device configured to communicate with a radio access network (RAN) according to a cellular radio access technology (RAT), the method comprising: determining respective connectivity status for each of a plurality of secondary devices configured to communicate with the RAN only via the primary device; and transmitting, to the RAN, a message indicating the respective connectivity status for each of the plurality of secondary devices.

2. The method of claim 1, wherein the message includes a list of non-3GGP device identifiers for the plurality of secondary devices.

3. The method of claim 2, wherein the message further includes user-plane addresses for the plurality of secondary devices.

4. The method of claim 3, wherein the user-plane addresses include Internet Protocol (IP) addresses.

5. The method of claim 3, wherein the user-plane addresses include port ranges.

6. The method of any of claims 2-5, wherein the list of non-3GPP device identifiers is included in response to determining that quality of service (QoS) differentiation is required for a secondary device included in the plurality of secondary devices.

7. The method of any of the preceding claims, wherein: the primary device is a 3rd Generation Partnership Project (3GPP) device, and each of the plurality of secondary devices is a non-3GPP device.

8. The method of any of the preceding claims, wherein the primary device is one of a user equipment (UE) or a 5G residential gateway (5G-RG).PATENT APPLICATIONAttorney Docket No.: 31730 / 308609-00P9. The method of any of the preceding claims, wherein the message is a protocol data unit (PDU) Session Modification Request.

10. The method of any of the preceding claims, further comprising: transmitting, to the RAN, a PDU Session Establishment request including a respective non-3GPP device identifier for each of the plurality of secondary devices.

11. The method of any of the preceding claims, wherein the message indicates that one of the plurality of secondary devices is active, and that another one of the plurality of secondary devices is inactive.

12. The method of any claims 1-10, wherein the transmitting of the message is in response to determining that one of the plurality of secondary devices became active.

13. The method of any of claims 1-10. wherein the transmitting of the message is in response to determining that the primary device is receiving inadequate QoS.

14. The method of any of claims 1-10, wherein the transmitting of the message is in response to receiving a request for the connectivity status from a network.

15. The method of any of the preceding clams, wherein the connectivity status includes activity status.

16. A device comprising: processing hardware; a transceiver; the device configured to implement a method of any of the preceding claims.

Images