Abstract: Methods and apparatus for providing L4S support with regard to non-3GPP untrusted/trusted accesses in which a non-3GPP access point, e.g., a WLAN AP or a TNAP, is enabled to monitor for uplink congestion with regard to L4S uplink data traffic flows at the non-3GPP AP, detect congestion, and perform explicit congestion notification (ECN) markings is described. In some embodiments, an innermost IP header field corresponding to an uplink L4S data packet, which typically conveys ECN information, in unavailable to the non-3GPP AP, due to IPsec encapsulation. The non-3GPP AP indicates detected congestion, at the non-3GPP AP, in an uplink (UL) traffic flow via setting bits in an outer IP header ECN field. The AP detected UL congestion information is communicated via the outer IP header ECN field to a core network interface device, e.g., a N3IWF or TNGF, and subsequently communicated to the inner-most IP header field.

Abstract: Methods and apparatus for providing L4S support with regard to non-3GPP untrusted/trusted accesses in which a non-3GPP access point, e.g., a WLAN AP or a TNAP, is enabled to monitor for downlink congestion with regard to L4S downlink data traffic flows at the non-3GPP AP, detect congestion and perform explicit congestion notification (ECN) markings are described. In some embodiments an innermost IP header field corresponding to a downlink L4S data packet, which typically conveys ECN information, in unavailable to the non-3GPP AP, due to IPsec encapsulation. The non-3GPP AP indicates detected congestion, at the non-3GPP AP, in an DL traffic flow via setting bits in an outer IP header ECN field. The AP detected DL congestion information is communicated via the outer IP header ECN field to a destination UE or to a core network interface device, e.g., a N3IWF or TNGF.

Abstract: Methods and apparatus for providing L4S support with regard to non-3GPP untrusted/trusted accesses in which a user equipment (UE) is enabled to monitor for uplink and/or downlink congestion with regard to L4S uplink data traffic flows at the UE, detect congestion, and perform explicit congestion notification (ECN) markings or communicate congestion information to perform ECN marking to another device are described. In some embodiments, the UE device indicates detected congestion, at the UE, in an uplink (UL) traffic flow via performing ECN marking of an innermost IP header ECN field. In some other embodiments, the UE device communicates detected congestion information, via a GRE message to a core network interface device, which communicates, via GTP-U, the detected congestion information to a UPF, which then uses the received UE detected congestion information to performs ECN marking in the innermost IP header of an uplink data packet.

Abstract: A database, e.g. a unified data repository (UDR) which can be accessed by a unified data management (UDM), stores residential gateway (RG) subscription information for each of plurality of RGs. The stored RG subscription information, corresponding to a RG includes information, e.g. 5G-RG L4S information, indicating whether or not the RG is allowed/capable to perform ECN marking. A session management function (SMF) retrieves, e.g., via a UDM, the RG information indicating whether or not the RG is allowed/capable to perform ECN marking and uses the retrieved information to decide whether or not to enable the RG to perform ECN marking for L4S and/or provide congestion information as part of QoS monitoring and/or to select resources including a policy control function (PCF) for supporting a PDU communications session.

Abstract: A residential gateway (RG), e.g., a 5G-RG, indicates its support for ECN marking for L4S in uplink and/or downlink via a PDU Session Request message, e.g., a PDU Session Establishment Request message, communicated from the RG via a wireline access gateway function (W-AGF) to a core network, e.g., a 5GC. The indication, in some embodiments, is provided in either: a Session Management (SM) capability field, e.g., a 5GSM capability field, or as a new indication, which is included as part of a N1 SM container. A RG may, and sometimes does, determine congestion in its buffers/queues and perform ECN marking and report if traffic congestion is being experienced within its own buffers/queues for uplink and/or downlink traffic. In some such embodiments, both an RG and a W-AGF can, and sometimes do, perform ECN marking for L4S simultaneously in both directions (i.e. uplink and downlink).

Abstract: A residential gateway (RG), e.g., a 5G-RG, indicates its support for ECN marking for L4S in uplink and/or downlink via a PDU session request message, e.g., a PDU session establishment request message, communicated from the RG via a 3GPP radio access network (RAN) to a core network, e.g., a 5GC. The indication, in some embodiments, is provided in either: a Session Management (SM) capability field, e.g., a 5GSM capability field, or as a new indication, which is included as part of a N1 SM container. A RG may, and sometimes does, determine congestion in its buffers/queues and perform ECN marking and report if traffic congestion is being experienced within its own buffers/queues for uplink and/or downlink traffic. In some such embodiments, both an RG and a RAN can, and sometimes do, perform ECN marking for L4S simultaneously in both directions (i.e. uplink and downlink).

Abstract: The standards organization 3GPP is exploring new small data delivery techniques for machine-type communications (MTC). It is recognized herein that existing approaches leave the “small data” decision to the service capability server (SCS) for downlink data and to the user equipment (UE) for uplink data. A user equipment (UE) or the core network can identify the services (or flows) that should be characterized as Small Data, and can make decisions as to when to employ optimized Small Data procedures.

Abstract: Methods and apparatus for using a QUIC connection established between a user equipment (UE) and a Trusted Non-3GPP Gateway Function (TNGF) to support trusted non-3GPP access which facilitates Access Traffic Steering, Switching, and Splitting (ATSSS) are described. An exemplary TGNF, implements Multiplexed Application Substrate over QUIC Encryption (MASQUE) over QUIC. In some embodiments, QUIC connection IDs are used to delineate control plane (CP) traffic and user plane traffic being communicated over the established QUIC connection. In other embodiments, a new 3GPP Payload type header is used to delineate between control plane (CP) traffic and user plane traffic communicated over the established QUIC connection.

Abstract: Methods and apparatus for using a QUIC connection established between a user equipment (UE) and a Non-3GPP InterWorking Function (N3IWF) to support untrusted non-3GPP access which facilitates Access Traffic Steering, Switching, and Splitting (ATSSS) are described. An exemplary N3IWF, implemented in accordance with features of the present invention, implements MASQUE over QUIC. In some embodiments, the Multiplexed Application Substrate over QUIC Encryption (MASQUE) over QUIC implementation as the transport for NAS. In some embodiments, QUIC connection IDs are used to delineate control plane (CP) traffic and user plane traffic being communicated over the established QUIC connection. In other embodiments, a new 3GPP Payload type header is used to delineate between control plane (CP) traffic and user plane traffic communicated over the established QUIC connection.

Abstract: The standards organization 3GPP is exploring new small data delivery techniques for machine-type communications (MTC). It is recognized herein that existing approaches leave the “small data” decision to the service capability server (SCS) for downlink data and to the user equipment (UE) for uplink data. A user equipment (UE) or the core network can identify the services (or flows) that should be characterized as Small Data, and can make decisions as to when to employ optimized Small Data procedures.

Abstract: Methods and apparatus for supporting EAP re-authentication for devices, e.g., UEs, connecting to APs such as WiFi APs, which are not 3GPP base stations such as gNBs are described. In accordance with the invention an ER service which supports EAP re-authentication is incorporated into an NSWOF which is coupled to multiple different APs. Once authenticated through the NSWOF via an EAP authorization process the ER service in the NSWOF stores UE re-authorization information and uses the information to re-authenticate a UE when it attaches to another AP to which the NSWOF is coupled. By supporting EAP re-authentication the need to contact an AUSF as part of a full authentication process is avoided and a UE can rapidly move between APs without having to perform a full EAP authentication involving contacting the AUSF each time the UE moves.

Abstract: Data packet congestion marking is supported in devices which may form part of a communications path. The devices which can perform marking can, and in some embodiments do, include non-gNB devices and non-anchor point UPFs, e.g., devices other than gNBs and PSA UPFs such as intermediate UPFs, N3IWFs, TNGFs, and W-AGFs, in addition to gNBs and anchor UPFs. Intermediate UPFs corresponding to a communications session will set the congestion indicator value in a data packet's IP header, of a data packet passing through the UPF, to indicate congestion, if it is not already set to indicate congestion when congestion is detected at the intermediate UPF. A session management function in some embodiments controls which devices perform congestion marking and enables/disables congestion marking, e.g., on a per communications session basis while the session is ongoing and/or at various times during a session establishment or device registration process.

Abstract: A UE is supplied with one or more UE Route Selection Policy (URSP) rules which include an indicator indicating support for a “L4S” Connection Capability. The use of an L4S connection capability indicator allows a UE to obtain L4S support for application traffic data requiring L4S support. The connection capabilities option in the URSP rule or rules allows a UE to select an appropriate route selection for matching L4S connection capability. By allowing a UE to indicate that a packet or packet flow is to be matched to a PDU session which has an L4S connection capability, the UE can trigger establishment of a new PDU session to support a flow of application data packets requiring L4S support or can cause the packet flow to be assigned to an existing PDU session or trigger a modification of an existing PDU Session which supports L4S.

Abstract: In various embodiments an explicit congestion feedback capabilities indication, e.g., information indicating a UE's support or lack of support for low latency, low loss and scalable throughput services (L4S), is communicated in a message sent from a UE to device in a network core. In some embodiments the communicated UE capability information provides information about the capability of the UE sending the message to support the use of feedback (e.g., congestion feedback) for scalable throughput services (e.g., (L4S services) or other explicit congestion notification (ECN) services which use congestion feedback for encoding and/or data rate control). In some embodiments the message or messages communicating the UE capability information include a PDU Session Establishment Request message, a PDU Session Modification Request message, and/or a Registration Request message.

Abstract: A network node may be configured to receive a request for an authentication and key establishment procedure from a machine to machine (M2M) device. The network node may be configured to determine a key agreement between the network node and the M2M device using the authentication and key establishment procedure. The network node may be configured to receive a request from an M2M server for the key agreement to be used to communicate with the M2M device. The network node may be configured to send the key agreement to the M2M server.

Abstract: Methods and apparatus for supporting efficient switching of data paths corresponding to a communications session between different non-3GPP access networks, e.g., networks including WiFi access points, using network core functionality are described. A novel registration process in which UE and AMF capability information is exchanged at an early stage in the registration process is described. An initial registration request message from a UE, via a 3GPP or N3GPP access network, includes an indicator as to whether or not the UE supports path switching for MA PDU sessions between N3GPP access paths. This allows, for a UE which supports the path switching, a AMF to be selected and assigned to the UE, which also supports the path switching, thus matching capabilities and eliminating the need for interrupting communications to change AMFs at a later point.

Abstract: Methods and apparatus for supporting efficient switching of data paths corresponding to a communications session between different non-3GPP access networks, e.g., networks including WiFi access points, using network core functionality are described. A novel registration process in which UE and AMF capability information is exchanged at an early stage in the registration process is described. An initial registration request message from a UE, via a 3GPP or N3GPP access network, includes an indicator as to whether or not the UE supports path switching for MA PDU sessions between N3GPP access paths. This allows, for a UE which supports the path switching, a AMF to be selected and assigned to the UE, which also supports the path switching, thus matching capabilities and eliminating the need for interrupting communications to change AMFs at a later point.

Abstract: Disclosed are methods and systems for Semantics Node functions which provide semantics support in machine-to-machine systems. In an example, a Semantic node may manage semantics resources capable of being discovered, retrieved, or validated by other devices. In another example, the Semantics Node may be discovered by other nodes, and semantics resources may be discovered with subscription mechanisms.

Abstract: A network node is configured to initiate a first authentication and key establishment procedure with a machine to machine (M2M) device. The network node is configured to determine a key agreement between the network node and the M2M device using the first authentication and key establishment procedure. The network node is configured to initiate a second authentication and key establishment procedure with an M2M server. The network node is configured to receive a request from the M2M server for the key agreement to be used to communicate with the M2M device using the second authentication and key establishment procedure. The network node is configured to send the key agreement to the M2M server using the second authentication and key establishment procedure.

Abstract: A machine-to-machine (M2M) node is configured to provide a communication management function to facilitate communication between a first service layer in a first network and a second service layer in a second network. The M2M node is configured to store a plurality of attributes for use by the communication management function and to receive via the first network, a first message from a first application in the first service layer. The M2M node is configured to determine, based on at least a first attribute identifying an expiration time after which the communication management function does not facilitate communication, that the communication management function is available to process the first message. The M2M node is configured to determine, based on at least a second attribute defining an access control list identifying applications in the first service layer, that the communication management function is available to process the first message.