Abstract: According to embodiments, a user plane function (UPF) node receives a plurality of packets from an application server. The UPF node identifies one or more packets from the plurality of packets. The one or more packets belong to a session group of media streams for coordinated transmission and having a same value of a media stream coordination identifier (MSCI). The UPF node sends to a base station the one or more packets for the coordinated transmission.

Abstract: An uncrewed aerial system (UAS) receives, from a first network function device of a first network, a network selection policy indicating a second network providing local UAS traffic information. The UAS receives from a second network function device of the second network, uncrewed aerial system traffic management (UTM) support information, and selects the second network in accordance with the network selection policy and the UTM support information. The UAS connects to the second network function device of the second network to receive the local UAS traffic information from the second network function device.

Abstract: A network node receives a packet in an internet protocol (IP) flow; determines that the packet in the IP flow is a media packet using an enhanced media identification filter; obtains a packet priority mark (PPM) for the media packet, the PPM indicating an importance of the media packet; obtains a protocol data unit (PDU) sequence mark (PSM) for the media packet, the PSM indicating a sequence number for a PDU set to which the media packet belongs; and processes the media packet in accordance with the PPM, the PSM, and a congestion level.

Abstract: A method for transporting a Multi-Transport Network Context Identifier (MTNC-ID) over a Segment Routing Version 6 (SRV6) header for fifth generation (5G) transport. The method receives a data packet that includes an MTNC-ID in a data plane header of the data packet. The MTNC-ID is extracted from the data plane header of the data packet, and is encapsulated in an argument field in a last segment of a segment list (SL[0]) of the SRV6 header of the data packet. An instruction for forwarding the MTNC-ID is encapsulated within a function field in the SL[0] of the SRH of the data packet. The data packet is transmitted over a SRV6 enabled data plane domain along a forwarding path corresponding to the MTNC-ID.

Abstract: A method for transporting a Multi-Transport Network Context Identifier (MTNC-ID) over a Segment Routing Version 6 (SRV6) enabled data plane for fifth generation (5G) transport. The method includes setting an indicator in a flags field of a SRV6 header of a data packet that an MTNC-ID type-length-value (TLV) is included in a TLV field of the SRV6 header. The MTNC-ID TLV for the MTNC-ID is inserted in the TLV field of the SRV6 header of the data packet. The data packet with the SRV6 header containing the MTNC-ID is transmitted over the SRV6 enabled data plane to a next node along a forwarding path corresponding to the MTNC-ID.

Abstract: According to embodiments, a user equipment (UE) receives an access credential message, The access credential message indicates an access credential for an on-demand network for the UE to access. The access credential message further indicates a limited lifespan of the access credential. The UE transmits, to the on-demand network, an authentication and authorization request. The authentication and authorization request includes information about the access credential. The UE receives, from the on-demand network, an authentication and authorization response. The UE establishes a session with the on-demand network based on the authentication and authorization response.

Abstract: A method for transporting a Multi-Transport Network Context Identifier (MTNC-ID) over a Segment Routing Version 6 (SRV6) enabled data plane for fifth generation (5G) transport. The method includes setting an indicator in a flags field of a SRV6 header of a data packet that an MTNC-ID type-length-value (TLV) is included in a TLV field of the SRV6 header. The MTNC-ID TLV for the MTNC-ID is inserted in the TLV field of the SRV6 header of the data packet. The data packet with the SRV6 header containing the MTNC-ID is transmitted over the SRV6 enabled data plane to a next node along a forwarding path corresponding to the MTNC-ID.

Abstract: A method and apparatus for optimizing network delivery of fifth generation (5G) edge application services by weighting network latency along with a load, capacity, and preference of an application server to determine where to transmit a new flow of packets. By using the weighted approach, network traffic can be equalized among multiple instances (e.g., applications) with the same address.

Abstract: A method implemented by a network edge node including adding a first header including a flags field and a data field including a first metadata to a first packet. The network edge node sets a first flag in the flags field of the first header to a first value to indicate that the first packet is a forward flow packet. The network edge node transmits the first packet towards a second network edge node. The network edge node receives a second packet including the first metadata in the data field and a second flag in the flags field set to the first value to indicate that the second packet is a reverse flow packet. The network edge generates a second metadata corresponding to receipt of the second packet and transmits an export message that includes the first metadata and second metadata toward a controller.

Abstract: A method used by an egress router is disclosed. The egress router receives a first packet from an initial ingress router addressed to an anycast address of an application server. The egress router transmits the first packet to the application server. The egress router receives a second packet from the application server. The second packet is addressed to the initial ingress router. The egress router inserts a sticky destination sub type length value (Sticky-Dst-SubTLV) into a destination option header of the second packet. The egress router transmits the second packet with the Sticky-Dst-SubTLV to the ingress router.

Abstract: A method for implemented by a user equipment (UE) receiving, by the UE from a home service provider (SP) of the UE, a first message including information associated with one or more target networks, the first message initiating a network switch changing a serving network of the UE from a current network to one target network of the one or more target networks; selecting, by the UE, the one target network of the one or more target networks; and accessing, by the UE, the one target network.

Abstract: A method includes receiving, by a control plane (CP) from an application function (AF), a traffic influence routing rule comprising a service address representing a destination address of a route to an application server, the traffic influence routing rule specifying a breakout rule for packets of a communicating device addressed to the application server; storing, by the CP, the traffic influence routing rule in a policy control function (PCF); and generating, by the CP, a traffic filter for packets of at least one traffic flow associated with the communicating device, the traffic filter directing packets of the at least one traffic flow that are addressed to the application server to the service address, the traffic filter being generated in accordance with the traffic influence routing rule.

Abstract: A method for operating a user equipment (UE) includes transmitting, by the UE, a registration request message to establish a connection for onboarding, the registration message comprising an onboarding and provisioning indication information; and completing, by the UE with a network entity, provisioning in accordance with the onboarding and provisioning indication information.

Abstract: A method performed by a Next Generation Node B (gNB) in a communications system implementing User Datagram Protocol (UDP) comprises indicating that a data packet comprises a multi-transport network context-identifier (MTNC-ID) corresponding to a forwarding path and being associated with a set of resource provisioning requirements for one or more transport networks on the forwarding path to provision transport resources for traffic forwarding on the forwarding path, inserting the MTNC-ID into a Generic UDP Encapsulation (GUE) header of the data packet, and transmitting the data packet to a network element (NE) in the communications system based on the forwarding path corresponding to the MTNC-ID.

Abstract: Traffic data is divided into data streams corresponding to workloads, and the data streams are multiplexed onto slice segments based on a multiplexing requirement or rule. Each slice segment is a physical or virtual processing element in a wireless network supporting network slicing. In one example, the data streams are multiplexed onto the slice segments such that data streams having different utility definitions are assigned to different slice segments. In another example, the data streams are multiplexed onto the slice segments such that workloads in the same cluster partitioned in a T-dimensional vector space are assigned to different slice segments.

Abstract: A method for resolving an identifier of a path between a first user plane entity (UPE) and a second UPE includes receiving a translation request comprising a network slice selection assistance information (S-NSSAI), a first transport interface address, a second transport interface address, and one or more quality of service (QoS) parameters associated with the transport path between the first UPE and the second UPE; selecting the identifier of the transport path from a translation table in accordance with the S-NSSAI, the first transport interface address and the second transport interface address; and sending a translation response comprising an indicator of the identifier.

Abstract: A method for transporting a Multi-Transport Network Context Identifier (MTNC-ID) over a Segment Routing Version 6 (SRV6) enabled data plane for fifth generation (5G) transport. The method includes setting an indicator in a flags field of a SRV6 header of a data packet that an MTNC-ID type-length-value (TLV) is included in a TLV field of the SRV6 header. The MTNC-ID TLV for the MTNC-ID is inserted in the TLV field of the SRV6 header of the data packet. The data packet with the SRV6 header containing the MTNC-ID is transmitted over the SRV6 enabled data plane to a next node along a forwarding path corresponding to the MTNC-ID.

Abstract: A method for transporting a Multi-Transport Network Context Identifier (MTNC-ID) over a Segment Routing Version 6 (SRV6) header for fifth generation (5G) transport. The method receives a data packet that includes an MTNC-ID in a data plane header of the data packet. The MTNC-ID is extracted from the data plane header of the data packet, and is encapsulated in an argument field in a last segment of a segment list (SL[0]) of the SRV6 header of the data packet. An instruction for forwarding the MTNC-ID is encapsulated within a function field in the SL[0] of the SRH of the data packet. The data packet is transmitted over a SRV6 enabled data plane domain along a forwarding path corresponding to the MTNC-ID.

Abstract: System and method embodiments are provided for accessing a wireless network. The embodiments enable establishing and releasing session resources in a wireless local area network (WLAN) corresponding to packet data network (PDN) connections in a 3 GPP enhanced packet core (EPC). In an embodiment, a method in a network component for establishing a control channel with a user equipment (UE) includes setting up, by the network component, a link layer channel, sending, by the network component, an identifier of the link layer channel to the UE; and communicating, by the network component, with the UE over the link layer channel using a WLAN control protocol (WLCP), wherein the WLAN comprises a trusted WLAN Access Network (TWAN).

Abstract: System and method embodiments are provided for accessing a wireless network. The embodiments enable establishing and releasing session resources in a wireless local area network (WLAN) corresponding to packet data network (PDN) connections in a 3 GPP enhanced packet core (EPC). In an embodiment, a method in a network component for establishing a control channel with a user equipment (UE) includes setting up, by the network component, a link layer channel, sending, by the network component, an identifier of the link layer channel to the UE; and communicating, by the network component, with the UE over the link layer channel using a WLAN control protocol (WLCP), wherein the WLAN comprises a trusted WLAN Access Network (TWAN).