Network function selection for QOS differentiation for non-3GPP devices

Abstract

Disclosed herein is a method performed by an AMF (104) and an AMF (104) performing the method for facilitating network function selection for QoS differentiation for non-3GPP device. The method comprises: receiving (111), from a data repository (110), SMF selection subscription information that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is allowed; and selecting (114) an SMF (106), based on the SMF selection subscription information.

Description

Applicant’s Ref. P113325WO01NETWORK FUNCTION SELECTION FOR QoS DIFFERENTIATION FOR NON-3GPP DEVICES TECHNICAL FIELD

[0001] The present disclosure relates to methods and network nodes for facilitating network function selection for Quality of Service (QoS) differentiation for non-Thi rd Generation Partnership Program (3GPP) devices in a wireless communications network.BACKGROUND

[0002] Support for providing Quality of Service (QoS) differentiation for non Third Generation Partnership Program (3GPP) devices behind User Equipment (UE) Fifth Generation (5G) Residential Gateways (RG) has been added to the 3GPP specifications in Rel 19, see for example 3GPP Technical Specification (TS) 23.501 v19.2.1 System Architecture for the 5G System (2025-01) clause 5.52. A UE / 5G-RG can request QoS differentiation for a device behind it by sending a Protocol Data Unit (PDU) session modification request that includes information to identify the device (non-3GPP device identifier) and the device traffic (e.g., IPv4 and port range). When the Session Management Function (SMF) receives the PDU session modification request, it sends the device and traffic identifier to the Policy Control Function (PCF). PCF uses the device identifier to retrieve Non-3GPP Device Identifier Information from UDR and applies changes to Policy and Charging Control (PCC) rules if needed.SUMMARY

[0003] Various embodiments described herein provide methods and network nodes for facilitating network function selection for Quality of Service (QoS) differentiation for non-Third Generation Partnership Program (3GPP) devices. In an embodiment, a method performed by an Access and Mobility Management Function (AMF) is provided that comprises receiving, from a data repository Session Management Function (SMF) selection subscription data that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is allowed, and then the AMF selects an SMF based on the SMF selection subscription information. Another method is provided where an SMF can retrieve information that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is allowed, and then the SMF selects the Policy Control Function (PCF) based on the information. The information can either be received from the AMF that the PDU session supports QoS differentiation, or the SMF can retrieve enhanced UE session management subscription data from the data repository that indicates whether the PDU session supports QoS differentiation.Applicant’s Ref. P113325WO01BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.Figure 1 is a message sequence chart of a method for facilitating network function selection for Quality of Service (QoS) differentiation for non-Third Generation Partnership Program (3GPP) devices in accordance with some embodiments of the present disclosure;Figure 2 shows an example of a communication system in accordance with some embodiments of the present disclosure;Figure 3 is another example of a communication system according to some embodiments of the present disclosure;Figure 4 shows a wireless device, which may be configured to operate in the communication system of Figure 2 or in the communication system of Figure 3;Figure 5 shows a network node in accordance with some embodiments of the present disclosure; and Figure 6 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.DETAILED DESCRIPTION

[0005] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0006] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0007] There currently exist certain challenge(s). As is evident in the previous clause, providing Quality of Service (QoS) differentiation to non-Third Generation Partnership Program (3GPP) devices behind User Equipment (UE) Fifth Generation (5G) Residential Gateways (RG) impacts the Session Management Function (SMF) and Policy Control Function (PCF). Therefore, for the Protocol Data Unit (PDU) session that carries the non-3GPP traffic, it is essential to choose a SMF and a PCF that support this feature. The problem is that the SMF and PCF for the PDU session are chosen in the PDU session establishment procedure, while the request for QoS differentiation for Non-3GPP devices are sent later in the PDU Session Modification request.

[0008] One possible solution is the homogeneous implementation, where all the SMF and PCFs that are used for a certain Data Network Name (DNN) or Single - Network Slice Selection Assistance Information (S-NSSAI) support this feature. However, this either requires enabling the feature for all (or a large number) of the SMFs and PCFs in the network or to add an additional DNN, both of these options are undesirable for operators.Applicant’s Ref. P113325WO01

[0009] Another proposed technique has been suggested, where Support of non-3GPP Device Identifiers is added to the UE 5G Mobility Management (5GMM) Core Network Capability and is signaled to the 5G Core network (5GC) during registration. This solution only covers the SMF selection and not the PCF selection. Furthermore, differentiating the QoS for devices behind UE / 5G-RG is a feature that should be enabled (allowed) in the subscription of the UE and not a UE capability.

[0010] Therefore, the proposed solution in this disclosure is more inline with the nature of the feature. Also, the techniques disclosed herein reduces sending additional parameters in registration and enables the operators to allow the feature for a subset of DNN / S-NSSAIs, which means that if the feature is not needed for a PDU session, the UE can request a different DNN / S-NSSAIs and the network does not need to select a SMF / PCF capable of the feature.

[0011] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.• SMF selection: This disclosure proposes to use a new parameter in UE subscription data in UDM to indicate whether or not a QoS differentiation for non-3GPP devices is supported per S-NSSAI, DNN. The Access and Mobility Management Function (AMF) uses this parameter to selects a SMF that supports this feature during the PDU session establishment.• PCF selection: The SMF also needs to know that the PDU session supports the QoS differentiation for the non-3GPP devices to selects a PCF that supports this feature. Two alternatives are presented:o Alt 1 : The AMF informs the SMF that the PDU session supports the QoS differentiation in the SM context create request;o Alt 2: The UE Session Management Subscription data is enhanced to include an indicator that the PDU session supports QoS differentiation for the non-3GPP devices.

[0012] Furthermore, the PCF and SMF registration in NRF are enhanced to include the capability of supporting QoS differentiation for the non-3GPP devices.

[0013] Certain embodiments may provide one or more of the following technical advantage(s). The proposed solution enables selection of SMF and PCF based on their capability to support QoS differentiation for Non-3GPP Devices, and does not require homogeneous implementation of the PCF and SMFs. Furthermore, the solution uses subscription data, and not UE 5GMM capability which reduces signaling overhead and is more inline with the nature of the feature, which is part of the subscription of the user.

[0014] NRF registration:First, the SMF and PCF registration in NRF are enhanced to indicate their support for QoS differentiation for Non-3GPP Devices. Specifically, the service Nnrf_NFManagement_NFRegister is enhanced so that for SMF or PCF consumer it accepts the indication of support for QoS differentiation for Non-3GPP Devices.

[0015] UE subscription data enhancement:

[0016] To enable AMF to choose the right SMF that supports QoS differentiation for Non-3GPP Devices, the following parameter is added to the SMF selection subscription data.Applicant’s Ref. P113325WO01UE Subscription data

[0017] Furthermore, in Alt 2, the session management subscription data is enhanced to include the following indicator that is similar to the one in the table above and is used by SMF to choose a PCF that supports the feature.UE Subscription data

[0018] PDU Session Establishment:

[0019] Figure 1 shows the call flow for PDU session establishment procedure with the addition of step 111 from step 14 of Figure 4.2.2.2.1-1 which is part of the UE registration call flow where the AMF retrieves the SMF selection subscription data from the UDM 110).

[0020] Steps 112-124 steps are the same as in Figure 4.3.2.2.1-1 of TS 23.502 v19.2.0 with the following changes.

[0021] In step 114, after the PDU Session Establishment request is received from UE 102 in step 112, the AMF 114 uses the parameter QoS differentiation for Non-3GPP Device Identifiers indication in UE subscription data received during the UE registration call flow in step 111, to determine that the SMF 106 should support this feature. The AMF 104 therefore uses a Network Repository Function to select an SMF 106 with this capability.

[0022] In step 116, for Alt 1 the AMF 104 transmits to the SMF the parameter Non-3GPP QoS Differentiation Indicator in a Create Session Management Context Request (Nsmf_PDUSession_CreateSMContext Request) to indicate that the PDU session (and the PCF 108) should support QoS differentiation for Non-3GPP Device Identifiers.

[0023] In step 118 for Alt 2, the SMF retrieves the Differentiated QoS for Non-3GPP Device Identifiers in the SM subscription data. In step 120, the steps 4-6 of Figure 4.3.2.2.1-1 of TS 23.502 are performed.

[0024] In step 122 the SMF 106 selects a PCF 108 that supports the QoS differentiation for Non-3GPP Device Identifiers.

[0025] In step 124, the steps 7b-21 of Fig. 4.3.2.2.1-1 of TS 23.502 are performed.

[0026] What follows is an excerpt of proposed changes to section 6.3.2 of TS 23.501 v19.2.1. The underlined sections represent the proposed changes.

[0027] Begin Excerpt6.3.2 SMF discovery and selectionf) Subscription information from UDM, e.g.Applicant’s Ref. P113325WO01per DNN: whether LBO roaming is allowed.per DNN: whether HR-SBO roaming is allowed.- per S-NSSAI: the subscribed DNN(s).per (S-NSSAI, subscribed DNN): whether LBO roaming is allowed.- per (S-NSSAI, subscribed DNN): whether HR-SBO roaming is allowed.per (S-NSSAI, subscribed DNN): whether EPC interworking is supported.per (S-NSSAI, subscribed DNN): whether selecting the same SMF for all PDU sessions to the same S- NSSAI and DNN is required.- per (S-NSSAI, DNN) associated with 5G VN group: Service Area (LADN service area) for the 5G VN group. In the case of SMF selection for a PDU Session targeting 5G VN group, the AMF may prefer candidate SMF(s) that have an intersection with the LADN service area of the 5G VN group.per (S-NSSAI, subscribed DNN): Additional Parameters for SMF selection in target PLMN as defined in TS 23.502 [3] and may include the target network identifier (i.e. PLMN ID preferred by the operator). per (S-NSSAL subscribed DNN): whether QoS differentiation of traffic for Non-3GPP Device Identifiers is allowed.

[0028] End Excerpt

[0029] What follows is an excerpt of proposed changes to section 6.3.7.1 of TS 23.501 v19.2.1. The underlined sections represent the proposed changes.

[0030] Begin Excerpt6.3.7.1 PCF discovery and selection for a UE or a PDU SessionWhen the NF service consumer performs PCF discovery and selection for a PDU Session, the following applies:The SMF may utilize the NRF to discover the candidate PCF instance(s) for a PDU Session. In addition, PCF information may also be locally configured in the SMF. The SMF selects a PCF instance based on the available PCF instances obtained from the NRF or locally configured information in the SMF, depending on operator's policies.The following factors may be considered at PCF discovery and selection for a PDU Session:a) Local operator policies.b) Selected Data Network Name (DNN).c) S-NSSAI of the PDU Session. In the LBO roaming case, the SMF selects the PCF instance based on the S-NSSAI of the VPLMN. In the home routed roaming case, the H-SMF selects the H-PCF instance based on the S-NSSAI of the HPLMN.d) SUPI; the SMF selects a PCF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for PCF discovery.e) PCF selected by the AMF for the UE.f) MA PDU Session capability of the PCF, for an MA PDU Session.g) The PCF Group ID provided by the AMF to the SMF.h) PCF Set ID.i) Same PCF Selection Indication.Applicant’s Ref. P113325WO01j) URSP delivery in EPS capability of the PCF.k) PCF capability to support QoS differentiation for traffic associated with Non-3GPP Device Identifiers.

[0031] End Excerpt

[0032] What follows is an excerpt of proposed changes to section 4.3.2.2.1 of TS 23.502 v19.2.0. The underlined sections represent the proposed changes.

[0033] Begin Excerpt4.3.2.2.1 Non-roaming and Roaming with Local Breakout3. From AMF to SMF : Either Nsmf_PDUSession_CreateSMContext Request (SUPI, selected DNN, UE requested DNN, S-NSSAI(s), [Alternative S-NSSAI], [Slice Area Restriction indication], PDU Session ID, AMF ID, Request Type, [PCF ID, Same PCF Selection Indication], Priority Access, [Small Data Rate Control Status], [Non-3GPP QoS Differentiation Indicator], N1 SM container (PDU Session Establishment Request), User location information, Access Type, RAT Type, PEI, GPSI, UE presence in LADN service area, Subscription For PDU Session Status Notification, DNN Selection Mode, Trace Requirements, Control Plane CIoT 5GS Optimisation indication, Control Plane Only indicator, Satellite backhaul category, GEO Satellite ID, [PVS FQDN(s) and / or PVS IP address(es), Onboarding Indication], Disaster Roaming service indication) or Nsmf_PDUSession_UpdateSMContext Request (SUPI, DNN, S-NSSAI(s), SM Context ID, AMF ID, Request Type, N1 SM container (PDU Session Establishment Request), User location information, Access Type, RAT type, PEI, Serving Network (PLMN ID, or PL MN ID and NID, see clause 5.18 of TS 23.501 [2]), Satellite backhaul category, GEO Satellite ID), [PCF binding information, notification of SM Policy Association establishment Indication],The AMF includes Trace Requirements if Trace Requirements have been received in subscription data.If the AMF decides to use the Control Plane CIoT 5GS Optimisation or User Plane CIoT 5GS Optimisation as specified in step 2 or to only use Control Plane CIoT 5GS Optimisation for the PDU session as described in clause 5.31.4 of TS 23.501 [2], the AMF sends the Control Plane CIoT 5GS Optimisation indication or Control Plane Only indicator to the SMF.If the AMF determines that the RAT type is NB-IoT and the number of PDU Sessions with user plane resources activated for the UE has reached the maximum number of supported user plane resources (0, 1 or 2) based on whether the UE supports UP data transfer and the UE's 5GMM Core Network Capability as described in clause 5.31.19 of TS 23.501 [2], the AMF may either reject the PDU Session Establishment Request or continue with the PDU Session establishment and include the Control Plane CIoT 5GS Optimisation indication or Control Plane Only indicator to the SMF.The AMF includes the latest Small Data Rate Control Status if it has stored it for the PDU Session.The AMF may include Non-3GPP QoS Differentiation Indicator to indicate that QoS differentiation for Non- 3GPP Device Identifiers described in clause 5.32 of TS 23.501 [2] is allowed within PDU Session. The SMF may use this information in PCF selection.

[0034] End ExcerptApplicant’s Ref. P113325WO01

[0035] What follows is an excerpt of proposed changes to section 5.2.3.3.1 of TS 23.502 v19.2.0. The underlined sections represent the proposed changes.

[0036] Begin Excerpt

[0037] End Excerpt

[0038] What follows is an excerpt of proposed changes to section 5.27.2.2 of TS 23.502 v19.2.0. The underlined sections represent the proposed changes.

[0039] Begin Excerpt5.2.7.2.2 Nnrf_NFManagement_NFRegister service operationInputs, Optional:Applicant’s Ref. P113325WO01If the consumer NF stores Data Set(s) (e.g. UDR): Range(s) of SUPIs, range(s) of GPSIs, range(s) of external group identifiers, Data Set Identifier(s).If the consumer is BSF : Range(s) of SUPIs, range(s) of GPSIs, Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes, IP domain list as described in clause 6.1.6.2.21 of TS 29.510

[0037] , Range(s) of SUPIs, range(s) of GPSIs.NOTE 3: Range of SUPI(s) is limited in this release to a SUPI type of IMSI as defined in TS 23.003

[0033] , - If the consumer is UDM, UDR, PCF, BSF or AUSF, they can include UDM Group ID, UDR Group ID, PCF Group ID, BSF Group ID, AUSF Group ID respectively.For UDM and AUSF, Routing Indicator, or Routing Indicator and Home Network Public Key identifier; Home Network Identifier: PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN.Optionally, some NFs may additionally include a Home Network Identifier (including the identification of the CH with AAA Server or DCS with AAA Server) in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using a DCS with AAA Server.For NSSAAF, Home Network Identifier in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using credentials from a DCS with AAA Server.- If the consumer is AMF, it includes list of GUAMI(s). In addition, AMF may include list of GUAMI(s) for which it can serve as backup for failure / maintenance.If the consumer is CHF, it may include Range(s) of SUPIs, Range(s) of GPSIs, or Range(s) of PLMNs as defined in TS 32.290

[0042] ,If the consumer is CHF, primary CHF instance and the secondary CHF instance pair. If the CHF does not provide NF set ID or NF Service Set ID, it shall provide a primary CHF instance and the secondary CHF instance pair and otherwise it may do so.- If the consumer is P-CSCF, the P-CSCF IP address(es) to be provided to the UE by SMF.- If the consumer is HSS, IMPI range, IMPU range, HSS Group ID (as defined in TS 23.228

[0055] ) can be used as optional input parameters.For the UPF Management: UPF Provisioning Information as defined in clause 4.17.6.S-NSSAI(s) and the associated NSI ID(s) (if available).- DNN(s) if the consumer is PCF or BSF. DNN(s) per S-NSSAI if the consumer is SMF, UPF or TSCTSF. If the consumer is a trusted AF it may include one or multiple combination(s) of S-NSSAI and DNN corresponding to the AF. In addition, it may include supported Application Id(s), Event ID(s) and Internal - Group Identifier. It may include an indication whether it supports mapping between UE IP address (IPv4 address or IPv6 prefix) and UE ID (i.e. SUPI).Information about the location or serving scope of the NF consumer (operator specific information, e.g. geographical location, data centre).- TAI(s).- NF Set ID.- NF Service Set ID.If the consumer is PCF or SMF, it includes the MA PDU Session capability to indicate if the NF instance supports MA PDU session or not.If the consumer is PCF or SMF, it may indicate the capability to support QoS differentiation for traffic associated with Non-3GPP Device Identifiers.Applicant’s Ref. P113325WO01

[0040] End Excerpt

[0041] What follows is an excerpt of proposed changes to section 5.2.8.2.5 of TS 23.502 v19.2.0. The underlined sections represent the proposed changes.

[0042] Begin Excerpt5.2.8.2.5 Nsmf_PDUSession_CreateSMContext service operationService operation name: Nsmf_PDUSession_CreateSMContext.Description: It creates an AMF-SMF association to support a PDU Session.Input, Required: SUPI or PEI, DNN, AMF ID (AMF Instance ID), RAT Type, Serving Network (PLMN ID, or PLMN ID andNID, see clause 5.18 of TS 23.501 [2]).Input, Optional: PEI, S-NSSAI(s), Alternative S-NSSAI, Slice Area Restriction indication, PDU Session ID, N1 SM container, UE location information, UE Time Zone, AN type, H-SMF identifier / address, list of alternative H-SMF(s) if available, old PDU Session ID (if the AMF also received an old PDU Session ID from the UE as specified in clause 4.3.5.2), Subscription For PDU Session Status Notification, Subscription for DDN Failure Notification, NEF Correlation ID, indication that the SUPI has not been authenticated, PCF ID, PCF Group ID, Same PCF Selection Indication, DNN Selection Mode, UE PDN Connection Context, GPSI, UE presence in LADN service area, indication that "the PDU Session is subject to LADN per LADN DNN and S-NSSAI", GUAMI, backup AMF(s) (if NF Type is AMF), Trace Requirements, Control Plane CIoT 5GS Optimisation indication, Small Data Rate Control Status, Non-3GPP QoS Differentiation Indicator. APN Rate Control Status. Backup AMF(s) sent only once by the AMF to the SMF in its first interaction with the SMF, UE's Routing Indicator optionally with Home Network Public Key identifier or UDM Group ID for the UE, EPS Interworking indication, EPS Bearer Status. Target ID (for EPS to 5GS handover), "Invoke NEF" flag, target DNAI, additional following for SM context transfer: SMF transfer indication, Old SMF ID, SM context ID in old SMF (see clause 4.26.5.3), HO Preparation Indication, indication of no NG-RAN change. MA PDU request indication, MA PDU Network -Upgrade Allowed indication, Indication on whether the UE is registered in both accesses, Satellite backhaul category, GEO Satellite ID, PVS FQDN(s) and / or PVS IP address(es) and Onboarding Indication in the case of ON-SNPN, Disaster Roaming service indication, HR-SBO allowed indication, Local Offloading Management allowed indication, Indication of UE supports non-3GPP access path switching, NG RAN QoS monitoring capability (as defined in clause 5.45.1 of TS 23.501 [2],

[0043] End Excerpt

[0044] Figure 2 shows an example of a communication system 200 in accordance with some embodiments.

[0045] In the example, the communication system 200 includes a telecommunications network 202 that includes an access network 204, such as a radio access network (RAN), and a core network 206, which includes one or more core network nodes 208. The access network 204 includes one or more access network nodes or base stations of various types, access network nodes 210A and 210B are depicted (which may be collectively referred to as network nodes 210), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 204 may include more than one access network technology. The network nodes 210 of access network 204 facilitate direct or indirect connection of wireless devices, alsoApplicant’s Ref. P113325WO01referred to as user equipments (UEs), such as by connecting UEs 212A, 212B, 212C, and 212D (one or more of which may be generally referred to as UEs 212) to the core network 206 over one or more wireless connections.

[0046] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 202 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 202 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 202, including one or more access network nodes 210 and / or core network nodes 208.

[0047] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective "open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0048] The network nodes 210 facilitate direct or indirect connection of one or more UEs 212 to the core network 206 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 200 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 200 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0049] The UEs 212 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 210 and other communication devices. Similarly, the network nodes 208, 210 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 202) with the UEs 212 and / or with other network nodes or equipment in the telecommunications network 202 to enable and / or provide network access, suchApplicant’s Ref. P113325WO01as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 202. More specifically, UEs 212 may send messages, data, and / or other signals to network nodes 208, 210 or other elements of the telecommunications network 202 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 208, 210 may send messages, data, and other signals to UEs 2122, other network nodes 208, 210, and other devices in telecommunications network 202 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 212 by transmitting the message to an access network node 210 that will then transmit the message to the intended UE 212. Similarly, a core network node 108 may receive a particular message from a UE 212 by receiving the message from an access network node 210 that itself received the message from the UE 212.

[0050] In the depicted example, the core network 206 connects elements of the access network 204 (e.g., one or more of the network nodes 210) to one or more host computing systems, such as host 216. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 206 includes one or more core network nodes (e.g., core network node 208) of various types, one or more of which may be generally referred to as network nodes 208. Network nodes 208 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 208. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0051] The host 216 may be under the ownership or control of a service provider other than an operator or provider of the access network 204 and / or the telecommunications network 202. The host 216 may be operated by the service provider or on behalf of the service provider. The host 216 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0052] As a whole, the communication system 200 of Figure 2 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 200 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wirelessApplicant’s Ref. P113325WO01local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 200 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 200 supporting different standards, protocols, or rule sets.

[0053] As one example, in certain embodiments, access network 204 may contain some access network nodes 210 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 210 support (or the same access network nodes 210 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 202 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0054] Telecommunications network 202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 202. For example, the telecommunications network 202 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0055] In some examples, one or more of the UEs 212 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 204. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0056] In the example, the hub 214 communicates with the access network 204 to facilitate indirect communication between one or more UEs (e.g., UE 212C and / or 212D) and network nodes (e.g., network node 210B). In some examples, the hub 214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 214 may be a broadband router enabling access to the core network 206 for the UEs. As another example, the hub 214 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 210, or by executable code, script, process, or other instructions in the hub 214.

[0057] As another example, the hub 214 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 214 may beApplicant’s Ref. P113325WO01a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 214 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 214 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0058] The hub 214 may have a constant / persistent or intermittent connection to the network node 21 OB. The hub 214 may also allow for a different communication scheme and / or schedule between the hub 214 and UEs (e.g., UE 212C and / or 212D), and between the hub 214 and the core network 206. In other examples, the hub 214 is connected to the core network 206 and / or one or more UEs via a wired connection. Moreover, the hub 214 may be configured to connect to an M2M service provider over the access network 204 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 210 while still connected via the hub 214 via a wired or wireless connection. In some embodiments, the hub 214 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 210B. In other embodiments, the hub 214 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 210B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0059] Figure 3 is another example of a communication system 300 according to some embodiments. As used herein, the communication system 300 includes multiple access points (APs) 310 (with four exemplary APs 310A, 310B, 310C, and 310D being depicted) and multiple wireless devices, referred to in the context of communication system 300 as stations (STAs) 312 (referred to individually as STA 312A, STA 312B, STA 312C, STA 312D, and STA 312E). STA 312A is served by AP 310A in a first basic service set (BSS) 320A. STA 310B and STA 310C are served by AP 310B in a second BSS, BSS 320B. STA 312D is served by AP 310C in a third BSS, BSS 320C. STA 312E is served by AP 310D in a fourth BSS, BSS 320D. Stations 312 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 312 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0060] Each of STAs 312 may connect through a radio link to one of APs 310. For example, depending on location or channel conditions experienced by a given STA 312, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0061] Each AP 310 may provide data connectivity to STAs 312 connected to a particular AP 310. As illustrated, APs 310 may be connected to a data network 330. In this way, APs 310 may also provide data connectivity betweenApplicant’s Ref. P113325WO01STAs 312 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 312 and its serving AP 310 may be used for providing various kinds of services to STA 312, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 312 and / or on a device linked to STA 312. By way of example, Figure 3 illustrates an application service platform 332 provided in data network 330. The application (s) executed on STA 312 and / or on one or more other devices linked to STA 312 may use the radio link for data communication with one or more other STA 312 and / or the application service platform 332, thereby enabling utilization of the corresponding service(s) at STA 312.

[0062] Figure 4 shows a wireless device 400, which may be configured to operate in communication system 200 of Figure 2 or in communication system 300 of Figure 3. The wireless device 400 may be alternatively referred to as a UE 400, like a UE 212 within the context of communication system 200, or as a station (STA) 400 or as a non-access-point station (non-AP STA) 400, like a STA 312 within the context of the communication system 300, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0063] A wireless device 400 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everythi ng (V2X). In other examples, wireless device 400 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 400 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).Alternatively, wireless device 400 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0064] In particular embodiments, wireless device 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a power source 408, a memory 410, a communication interface 412, and / or any other component, or any combination thereof. Certain embodiments of wireless device 400 may include all or a subset of the components shown in Figure 4. The level of integration between the components may vary from one embodiment of wireless device 400 to another. In general, in a particular embodiment of wireless device 400, processing circuitry 402, input / output interface 406, power source 408, memory 410, and communication interfaceApplicant’s Ref. P113325WO01412 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 400. Further, certain embodiments of wireless devices 400 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0065] The processing circuitry 402 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 410. The processing circuitry 402 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 402 may include multiple central processing units (CPUs).

[0066] In the example, the input / output interface 406 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 400. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0067] In some embodiments, the power source 408 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 408 may further include power circuitry for delivering power from the power source 408 itself, and / or an external power source, to the various parts of wireless device 400 via input circuitry or an interface such as an electrical power cable. Power source 408 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 400 to which power is supplied.

[0068] The memory 410 may be or be configured to include memory such as random access memory (RAM), readonly memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 410 includes one or more programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416. The memory 410 may store, for use by wireless device 400, any of a variety of various operating systems or combinations of operating systems.Applicant’s Ref. P113325WO01

[0069] The memory 410 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (IUICC) or a removable UICC commonly known as ‘SIM card.' The memory 410 may allow wireless device 400 to access instructions, programs, and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 410, which may be or comprise a device-readable storage medium.

[0070] The processing circuitry 402 may be configured to communicate with an access network or other network via or using the communication interface 412. The communication interface 412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 422. The communication interface 412 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 418 and / or a receiver 420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).Moreover, the transmitter 418 and receiver 420 may be coupled to one or more antennas (e.g., antenna 422) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0071] In the illustrated embodiment, communication functions of the communication interface 412 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / ! nternet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0072] In particular embodiments, wireless device 400 may provide an output of data captured via a sensor, through its communication interface 412, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 400 can be communicated through a wireless connection to a network node via another wireless device 400. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors),Applicant’s Ref. P113325WO01in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0073] As another example, wireless device 400 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 400 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0074] Wireless device 400, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a planter animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 400 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 400 shown in Figure 4.

[0075] As yet another specific example, in an loT scenario, wireless device 400 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 400 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 400 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 400 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0076] In practice, any number of wireless devices 400 may be used together with respect to a single use case. For example, a first wireless device 400 might be or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second wireless device 400 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 400 may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or the second wireless device 400 can also include more than one of the functionalities described above. For example, wireless device 400 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.Applicant’s Ref. P113325WO01

[0077] Figure 5 shows a network node 500 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 500 may be configured to operate in communication system 200 of Figure 2, like network nodes 208 or 210, or in communication system 300 of Figure 3, like an AP 310 or a station 312. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0078] Network nodes 500 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 500 may be a relay node or a relay donor node controlling a relay. Network nodes 500 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0079] Other examples of network nodes 500 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0080] In particular embodiments, network node 500 includes a processing circuitry 502, a memory 504, a communication interface 506, and a power source 508. In general, in a particular embodiment of network node 500, processing circuitry 502, memory 504, communication interface 506, and power source 508 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 500.

[0081] The network node 500 may be composed of multiple distinct network entities (e.g., a NodeB entity and an RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 500 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 500 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 504 or portions of memory 504 for different RATs) and some components may be reused (e.g., a same antenna 510 may be shared by different RATs). The network node 500 may also include multiple setsApplicant’s Ref. P113325WO01of the various illustrated components for different wireless technologies integrated into network node 500, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 500.

[0082] The processing circuitry 502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 504, to provide network node 500 functionality.

[0083] In some embodiments, the processing circuitry 502 includes a system on a chip (SOC). In some embodiments, the processing circuitry 502 includes one or more of radio frequency (RF) transceiver circuitry 512 and baseband processing circuitry 514. In some embodiments, the RF transceiver circuitry 512 and the baseband processing circuitry 514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 512 and baseband processing circuitry 514 may be on the same chip or set of chips, boards, or units.

[0084] The memory 504 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 502. The memory 504 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 502 and utilized by the network node 500. The memory 504 may be used to store any calculations made by the processing circuitry 502 and / or any data received via the communication interface 506. In some embodiments, the processing circuitry 502 and memory 504 is integrated.

[0085] The communication interface 506 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 506 comprises port(s) / terminal(s) 516 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 400 may be capable of wireless communication and communication interface 506 may also include radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, an antenna 510. Particular embodiments of radio front-end circuitry 518 include filter(s) 520 and amplifier(s) 522. The radio front-end circuitry 518 may be connected to an antenna 510 and processing circuitry 502. The radio front-end circuitry may be configured to condition signals communicated between antenna 510 and processing circuitry 502. The radio front-end circuitry 518 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 518 may convert the digital data into aApplicant’s Ref. P113325WO01radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 520 and / or amplifiers 522. The radio signal(s) may then be transmitted via the antenna 510. Similarly, when receiving data, the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518. The digital data may be passed to the processing circuitry 502. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0086] In certain alternative embodiments, network node 500 may be capable of wireless communication but does not include separate radio front-end circuitry 518, instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 512 is part of the communication interface 506. In still other embodiments, the communication interface 506 includes one or more ports or terminals 516, the radio front-end circuitry 518, and the RF transceiver circuitry 512, as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).

[0087] The antenna 510 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 510 may be coupled to the radio front-end circuitry 518 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 510 is separate from the network node 500 and connectable to the network node 500 through one or more interfaces or ports.

[0088] The antenna 510, communication interface 506, and / or the processing circuitry 502 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 500. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 510, the communication interface 506, and / or the processing circuitry 502 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 500. Any information, data and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0089] The power source 508 provides power to the various components of network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein. For example, the network node 500 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 508. As a further example, the power source 508 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0090] Embodiments of the network node 500 may include additional components beyond those shown in Figure 5 for providing certain aspects of the network node's functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network nodeApplicant’s Ref. P113325WO01500 may include user interface equipment to allow input of information into the network node 500 and to allow output of information from the network node 500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 500.

[0091] Figure 6 is a block diagram illustrating a virtualization environment 600 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 600 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 600 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0092] Applications 602 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0093] Hardware 604 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 608A and VM 608B (which may be collectively referred to as VMs 608), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 606 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 608.

[0094] The VMs 608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 606. Different embodiments of the instance of a virtual appliance 602 may be implemented on one or more of VMs 608, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0095] In the context of NFV, each of the VMs 608 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 608, and that part of hardware 604 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function isApplicant’s Ref. P113325WO01responsible for handling specific network functions that run in one or more of the VMs 608 on top of the hardware 604 and corresponds to an application 602.

[0096] Hardware 604 may be implemented in a standalone network node with generic or specific components. Hardware 604 may implement some functions via virtualization. Alternatively, hardware 604 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 610, which, among others, oversees lifecycle management of applications 602. In some embodiments, hardware 604 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 612 which may alternatively be used for communication between hardware nodes and radio units.

[0097] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.SOME EMBODIMENTSSome of the embodiments that have been described above can be summarized in the following manner:1. A method performed by an Access and Mobility Management Function, AMF, (104) for facilitating network function selection for Quality of Service, QoS, differentiation for non-Third Generation Partnership Program, 3GPP, device, the method comprising:receiving (111), from a data repository (110), Session Management Function, SMF, selection subscriptionApplicant’s Ref. P113325WO01information that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is allowed; and selecting (114) an SMF (106), based on the on the SMF selection subscription information.2. The method of embodiment 1 , further comprising:providing (116), to the SMF, information that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is allowed.3. The method of embodiment 2, wherein the information is provided in a parameter entitled Non-3GPP QoS Differentiation indicator.4. The method of embodiment 2, wherein the parameter is in a Create Session Management Context Request message.5. The method of any one of embodiment 1 to 4, wherein the SMF selection subscription information is associated with a User Equipment, UE (102).6. The method of any one of embodiment 1 to 5, wherein the SMF selection subscription information is per Single - Network Slice Selection Assistance Information, S-NSSAI, and per Data Network Name, DNN.7. The method of any one of embodiment 1 to 6, wherein in response to the SMF selection subscription information indicating that QoS differentiation for non-3GPP device identifiers is allowed, the selected SMF (106) supports QoS differentiation for non-3GPP device identifiers.8. The method of any one of embodiment 1 to 7, wherein the selecting the SMF (106) is based on SMF information from a Network Repository Function, NRF.9. The method of any one of embodiment 1 to 8, wherein the data repository is a Unified Data Management, UDM (110).10. A network node implementing an Access and Mobility Management Function, AMF, (104) for facilitating network function selection for Quality of Service, QoS, differentiation for non-Third Generation Partnership Program, 3GPP, devices, the network node comprising processing circuitry configured to:receive (111), from a data repository, Session Management Function, SMF, selection subscription information that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is allowed; and select (114) an SMF, (106) based on the on the SMF selection subscription information.Applicant’s Ref. P113325WO0111. The network node of embodiment 10, wherein the processing circuitry is further configured to perform any one of embodiment 2 to 10.12 A method performed by a Session Management Function, SMF, (106) for facilitating network function selection for Quality of Service, QoS, differentiation for non-Third Generation Partnership Program, 3GPP, device, the method comprising:retrieving (116, 118) information that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is supported in a Protocol Data Unit, PDU, session; andselecting (122) a Policy Control Function, PCF, (108) based on the information.13. The method of embodiment 12, wherein the retrieving the information comprises receiving (116) the information from an Access and Mobility Management Function, AMF, (104) in a parameter entitled Non-3GPP QoS Differentiation indicator.14. The method of embodiment 13, wherein the parameter is in a Create Session Management Context Request message.15. The method of embodiment 12, wherein the retrieving the information comprises receiving (118) session management subscription information from a data repository (110).16. The method of embodiment 15, wherein the session management subscription information is per Single -Network Slice Selection Assistance Information, S-NSSAI, and per Data Network Name, DNN.17. The method of any one of embodiment 15 to 16, wherein the data repository is a Unified Data Management, UDM (110).18. The method of any one of embodiment 12 to 17, wherein in response to information indicating that QoS differentiation for non-3GPP device identifiers is allowed, the selected PCF (108) supports QoS differentiation for non-3GPP device identifiers.19. A network node implementing a Session Management Function, SMF, (106) for facilitating network function selection for Quality of Service, QoS, differentiation for non-Third Generation Partnership Program, 3GPP, device, the network node comprising processing circuitry configured to:retrieve (116, 118) information that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is supported in a Protocol Data Unit, PDU, session; andselect (122) a Policy Control Function, PCF, (108) based on the information.Applicant’s Ref. P113325WO0120. The network node of embodiment 19, wherein the processing circuitry is further configured to perform any one of embodiment 13 to 18.

[0098] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0099] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

1. Applicant’s Ref. P113325WO01CLAIMSWhat is claimed is:

1. A method performed by an Access and Mobility Management Function, AMF, (104) for facilitating network function selection for Quality of Service, QoS, differentiation for non-Third Generation Partnership Program, 3GPP, device, the method comprising:receiving (111), from a data repository (110), Session Management Function, SMF, selection subscription information that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is allowed; and selecting (114) an SMF (106), based on the on the SMF selection subscription information.

2. The method of claim 1 , further comprising:providing (116), to the SMF, information that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is allowed.

3. The method of claim 2, wherein the information is provided in a parameter entitled Non-3GPP QoS Differentiation indicator.

4. The method of claim 2, wherein the parameter is in a Create Session Management Context Request message.

5. The method of any one of claim 1 to 4, wherein the SMF selection subscription information is associated with a User Equipment, UE (102).

6. The method of any one of claim 1 to 5, wherein the SMF selection subscription information is per Single -Network Slice Selection Assistance Information, S-NSSAI, and per Data Network Name, DNN.

7. The method of any one of claim 1 to 6, wherein in response to the SMF selection subscription information indicating that QoS differentiation for non-3GPP device identifiers is allowed, the selected SMF (106) supports QoS differentiation for non-3GPP device identifiers.

8. The method of any one of claim 1 to 7, wherein the selecting the SMF (106) is based on SMF information from a Network Repository Function, NRF.

9. The method of any one of claim 1 to 8, wherein the data repository is a Unified Data Management, UDM (110).26Applicant’s Ref. P113325WO0110. A network node implementing an Access and Mobility Management Function, AMF, (104) for facilitating network function selection for Quality of Service, QoS, differentiation for non-Third Generation Partnership Program, 3GPP, devices, the network node comprising processing circuitry configured to:receive (111), from a data repository, Session Management Function, SMF, selection subscription information that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is allowed; and select (114) an SMF, (106) based on the on the SMF selection subscription information.

11. The network node of claim 10, wherein the processing circuitry is further configured to perform any one of claim 2 to 10.12 A method performed by a Session Management Function, SMF, (106) for facilitating network function selection for Quality of Service, QoS, differentiation for non-Third Generation Partnership Program, 3GPP, device, the method comprising:retrieving (116, 118) information that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is supported in a Protocol Data Unit, PDU, session; andselecting (122) a Policy Control Function, PCF, (108) based on the information.

13. The method of claim 12, wherein the retrieving the information comprises receiving (116) the information from an Access and Mobility Management Function, AMF, (104) in a parameter entitled Non-3GPP QoS Differentiation indicator.

14. The method of claim 13, wherein the parameter is in a Create Session Management Context Request message.

15. The method of claim 12, wherein the retrieving the information comprises receiving (118) session management subscription information from a data repository (110).

16. The method of claim 15, wherein the session management subscription information is per Single - Network Slice Selection Assistance Information, S-NSSAI, and per Data Network Name, DNN.

17. The method of any one of claim 15 to 16, wherein the data repository is a Unified Data Management, UDM (110).

18. The method of any one of claim 12 to 17, wherein in response to information indicating that QoS differentiation for non-3GPP device identifiers is allowed, the selected PCF (108) supports QoS differentiation for non-3GPP deviceApplicant’s Ref. P113325WO01identifiers.

19. A network node implementing a Session Management Function, SMF, (106) for facilitating network function selection for Quality of Service, QoS, differentiation for non-Third Generation Partnership Program, 3GPP, device, the network node comprising processing circuitry configured to:retrieve (116, 118) information that indicates whether QoS differentiation of traffic for non-3GPP device identifiers is supported in a Protocol Data Unit, PDU, session; andselect (122) a Policy Control Function, PCF, (108) based on the information.

20. The network node of claim 19, wherein the processing circuitry is further configured to perform any one of claim 13 to 18.

Images