Patent Description:
A wireless local area network (WLAN) may be formed by one or more access points (APs) that provide a shared wireless communication medium for use by a quantity of client devices also referred to as stations (STAs). Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing available system resources (for example, time, frequency, power). An AP periodically broadcasts beacon frames to enable any STAs within wireless range of the AP to establish or maintain a communication link with the WLAN. A wireless device may communicate with a network device bi-directionally. For example, in a WLAN, a STA may communicate with an associated AP via downlink and uplink communications. The downlink (or forward link) communication may refer to the communication link from the AP to the station, and the uplink (or reverse link) communication may refer to the communication link from the station to the AP. A system, such as a <NUM> system, may support multiple network slices serving multiple wireless devices. The network slices may be isolated end-to-end networks supporting different features for different applications for the wireless devices. However, STAs operating in a WLAN supported by an AP accessing NR systems lack the ability to request or use network slices.

<CIT> relates to systems and methods for providing virtualization functions in the control and data planes and for operating a communication network with network slicing.

The systems, methods and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

However, the accompanying drawings illustrate only some typical aspects of this disclosure and are therefore not to be considered limiting of its scope.

The following description is directed to certain implementations for the purposes of describing innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. The described implementations can be implemented in any device, system or network that is capable of transmitting and receiving radio frequency (RF) signals according to one or more of the Institute of Electrical and Electronics Engineers (IEEE) <NUM> standards, the IEEE <NUM> standards, the Bluetooth® standards as defined by the Bluetooth Special Interest Group (SIG), or the Long Term Evolution (LTE), <NUM>, <NUM> or <NUM> (New Radio (NR)) standards promulgated by the 3rd Generation Partnership Project (3GPP), among others. The described implementations can be implemented in any device, system or network that is capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), single-user (SU) multiple-input multiple-output (MIMO) and multi-user (MU) MIMO. The described implementations also can be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless personal area network (WPAN), a wireless local area network (WLAN), a wireless wide area network (WWAN), or an internet of things (IOT) network.

Various implementations relate generally to techniques for local area network (LAN) client participation in a network slice. In some implementations, a customer premises equipment (CPE) having capabilities to access one or more systems, such as fifth generation (<NUM>) wireless communication systems, may handle a network slice request from one or more LAN clients. In some examples, such a CPE may be referred to as a <NUM>-CPE. In some implementations, the <NUM>-CPE may enable LAN clients that are unaware of the available network slices to request and access the network slices. Additionally or alternatively, the <NUM>-CPE may enable LAN clients that are aware of the available network slices to request and access the network slices. In some examples in which the LAN clients and their applications are unaware of the available network slices, a <NUM>-CPE may determine available network slices (for example, using network slice selection assistance information, configured slice selection assistance information, or allowed slice selection assistance information, among other techniques), and may broadcast indications of the available network slices to the LAN clients. In some implementations, a LAN client may initiate an application session and the <NUM>-CPE may validate the user credentials associated with the initiation of the application session. In some implementations, the <NUM>-CPE may initiate the setup of a network slice on behalf of the LAN client upon successful validation of the user credentials.

In some examples in which the LAN clients and their applications are aware of the available network slices, the <NUM>-CPE may also determine available network slices and may also broadcast the available network slices to the LAN clients. In some implementations, upon receiving the message, a LAN client may request a creation of a network slice. In some implementations, the LAN client may request to access the available network slice. In response to receiving such a request from the LAN client, the <NUM>-CPE may request a new network slice to be setup. In some implementations, the <NUM>-CPE may establish a connection (such as a packet data network) as part of a successful network slice setup. In some implementations, the <NUM>-CPE may route traffic related to the created or accessed network slice over the established connection (for example, over the packet data network).

Particular implementations of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some implementations, the described techniques can be used to enable LAN clients supported by a <NUM>-enabled CPE to request or use one or more network slices. According to one or more implementations, a <NUM> wireless communication system may support network slicing. Network slicing may provide for a creation of multiple virtual logical networks (which may be examples of network slices) over a physical infrastructure shared by multiple entities (such as multiple application providers or multiple operators). In some examples, the one or more network slices may support different features, or network function optimizations, or both. In some implementations, the techniques and other aspects described in this disclosure may enable one or more LAN clients to support ultra-low latency while communicating over a Wi-Fi interface.

Aspects of the disclosure are initially described in the context of a wireless communication system. Additional aspects are described with respect to a wireless communication system architecture and timing diagrams. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to the participation of LAN clients in a network slice.

<FIG> shows a block diagram of an example wireless communication network <NUM>. According to some aspects, the wireless communication network <NUM> can be an example of a wireless local area network (WLAN) such as a Wi-Fi network (and will hereinafter be referred to as WLAN <NUM>). For example, the WLAN <NUM> can be a network implementing at least one of the IEEE <NUM> family of wireless communication protocol standards (such as that defined by the IEEE <NUM>-<NUM> specification or amendments thereof including, but not limited to, <NUM>. 11ay, <NUM> ax, <NUM>. 11az, <NUM>. 11ba and <NUM>. The WLAN <NUM> may include numerous wireless communication devices such as an access point (AP) <NUM> and multiple stations (STAs) <NUM>. While only one AP <NUM> is shown, the WLAN network <NUM> also can include multiple APs <NUM>.

Each of the STAs <NUM> also may be referred to as a LAN client, a mobile station (MS), a mobile device, a mobile handset, a wireless handset, an access terminal (AT), a user equipment (UE), a subscriber station (SS), or a subscriber unit, among other possibilities. The STAs <NUM> may represent various devices such as mobile phones, personal digital assistant (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, display devices (for example, TVs, computer monitors, navigation systems, among others), music or other audio or stereo devices, remote control devices ("remotes"), printers, kitchen or other household appliances, key fobs (for example, for passive keyless entry and start (PKES) systems), among other possibilities.

A CPE having capabilities to access <NUM> wireless communication systems may include the AP <NUM>. A single AP <NUM> and an associated set of STAs <NUM> may be referred to as a basic service set (BSS), which is managed by the respective AP <NUM>. <FIG> additionally shows an example coverage area <NUM> of the AP <NUM>, which may represent a basic service area (BSA) of the WLAN <NUM>. The BSS may be identified to users by a service set identifier (SSID), as well as to other devices by a basic service set identifier (BSSID), which may be a medium access control (MAC) address of the AP <NUM>. The AP <NUM> periodically broadcasts beacon frames ("beacons") including the BSSID to enable any STAs <NUM> within wireless range of the AP <NUM> to "associate" or re-associate with the AP <NUM> to establish a respective communication link <NUM> (hereinafter also referred to as a "Wi-Fi link"), or to maintain a communication link <NUM>, with the AP <NUM>. For example, the beacons can include an identification of a primary channel used by the respective AP <NUM> as well as a timing synchronization function for establishing or maintaining timing synchronization with the AP <NUM>. The AP <NUM> may provide access to external networks to various STAs <NUM> in the WLAN via respective communication links <NUM>.

To establish a communication link <NUM> with an AP <NUM>, each of the STAs <NUM> is configured to perform passive or active scanning operations ("scans") on frequency channels in one or more frequency bands (for example, the <NUM>, <NUM>, <NUM> or <NUM> bands). To perform passive scanning, a STA <NUM> listens for beacons, which are transmitted by respective APs <NUM> at a periodic time interval referred to as the target beacon transmission time (TBTT) (measured in time units (TUs) where one TU may be equal to <NUM> microseconds (µs)). To perform active scanning, a STA <NUM> generates and sequentially transmits probe requests on each channel to be scanned and listens for probe responses from APs <NUM>. Each STA <NUM> may be configured to identify or select an AP <NUM> with which to associate based on the scanning information obtained through the passive or active scans, and to perform authentication and association operations to establish a communication link <NUM> with the selected AP <NUM>. The AP <NUM> assigns an association identifier (AID) to the STA <NUM> at the culmination of the association operations, which the AP <NUM> uses to track the STA <NUM>.

As a result of the increasing ubiquity of wireless networks, a STA <NUM> may have the opportunity to select one of many BSSs within range of the STA or to select among multiple APs <NUM> that together form an extended service set (ESS) including multiple connected BSSs. An extended network station associated with the WLAN <NUM> may be connected to a wired or wireless distribution system that may allow multiple APs <NUM> to be connected in such an ESS. As such, a STA <NUM> can be covered by more than one AP <NUM> and can associate with different APs <NUM> at different times for different transmissions. Additionally, after association with an AP <NUM>, a STA <NUM> also may be configured to periodically scan its surroundings to find a more suitable AP <NUM> with which to associate. For example, a STA <NUM> that is moving relative to its associated AP <NUM> may perform a "roaming" scan to find another AP <NUM> having more desirable network characteristics such as a greater received signal strength indicator (RSSI) or a reduced traffic load.

In some examples, STAs <NUM> may form networks without APs <NUM> or other equipment other than the STAs <NUM> themselves. Some examples of such a network is an ad hoc network (or wireless ad hoc network). Ad hoc networks may alternatively be referred to as mesh networks or peer-to-peer (P2P) networks. In some examples, ad hoc networks may be implemented within a larger wireless network such as the WLAN <NUM>. In such implementations, while the STAs <NUM> may be capable of communicating with each other through the AP <NUM> using communication links <NUM>, STAs <NUM> also can communicate directly with each other via direct wireless links <NUM>. Additionally, two STAs <NUM> may communicate via a direct communication link <NUM> regardless of whether both STAs <NUM> are associated with and served by the same AP <NUM>. In such an ad hoc system, one or more of the STAs <NUM> may assume the role filled by the AP <NUM> in a BSS. Such a STA <NUM> may be referred to as a group owner (GO) and may coordinate transmissions within the ad hoc network. Examples of direct wireless links <NUM> include Wi-Fi Direct connections, connections established by using a Wi-Fi Tunneled Direct Link Setup (TDLS) link, and other P2P group connections.

The APs <NUM> and STAs <NUM> may function and communicate (via the respective communication links <NUM>) according to the IEEE <NUM> family of wireless communication protocol standards (such as that defined by the IEEE <NUM>-<NUM> specification or amendments thereof including, but not limited to, <NUM>. 11ay, <NUM> ax, <NUM>. 11az, <NUM>. 11ba and <NUM>. These standards define the WLAN radio and baseband protocols for the PHY and medium access control (MAC) layers. The APs <NUM> and STAs <NUM> transmit and receive wireless communications (hereinafter also referred to as "Wi-Fi communications") to and from one another in the form of PHY protocol data units (PPDUs) (or physical layer convergence protocol (PLCP) PDUs). The APs <NUM> and STAs <NUM> in the WLAN <NUM> may transmit PPDUs over an unlicensed spectrum, which may be a portion of spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the <NUM> band, the <NUM> band, the <NUM> band, the <NUM> band, and the <NUM> band. Some implementations of the APs <NUM> and STAs <NUM> described herein also may communicate in other frequency bands, such as the <NUM> band, which may support both licensed and unlicensed communications. The APs <NUM> and STAs <NUM> also can be configured to communicate over other frequency bands such as shared licensed frequency bands, where multiple operators may have a license to operate in the same or overlapping frequency band or bands.

Each of the frequency bands may include multiple sub-bands or frequency channels. For example, PPDUs conforming to the IEEE <NUM>. 11n, <NUM>. 11ac, <NUM>. 11ax and <NUM>. 11be standard amendments may be transmitted over the <NUM>, <NUM> or <NUM> bands, each of which is divided into multiple <NUM> channels. As such, these PPDUs are transmitted over a physical channel having a minimum bandwidth of <NUM>, but larger channels can be formed through channel bonding. For example, PPDUs may be transmitted over physical channels having bandwidths of <NUM>, <NUM>, <NUM> or <NUM> by bonding together multiple <NUM> channels.

Each PPDU is a composite structure that includes a PHY preamble and a payload in the form of a PHY service data unit (PSDU). The information provided in the preamble may be used by a receiving device to decode the subsequent data in the PSDU. In instances in which PPDUs are transmitted over a bonded channel, the preamble fields may be duplicated and transmitted in each of the multiple component channels. The PHY preamble may include both a legacy portion (or "legacy preamble") and a non-legacy portion (or "non-legacy preamble"). The legacy preamble may be used for packet detection, automatic gain control and channel estimation, among other uses. The legacy preamble also may generally be used to maintain compatibility with legacy devices. The format of, coding of, and information provided in the non-legacy portion of the preamble is based on the particular IEEE <NUM> protocol to be used to transmit the payload.

As described above, the APs <NUM> and the STAs <NUM> can support multi-user (MU) communications; that is, concurrent transmissions from one device to each of multiple devices (for example, multiple simultaneous downlink (DL) communications from an AP <NUM> to corresponding STAs <NUM>), or concurrent transmissions from multiple devices to a single device (for example, multiple simultaneous uplink (UL) transmissions from corresponding STAs <NUM> to an AP <NUM>). To support the MU transmissions, the APs <NUM> and STAs <NUM> may utilize multi-user multiple-input, multiple-output (MU-MIMO) and multi-user orthogonal frequency division multiple access (MU-OFDMA) techniques.

In some implementations, the APs <NUM> and the STAs <NUM> can support the use of network slices, as described herein. For example, <NUM> wireless communication systems (such as wireless communication network <NUM>) may support the creation of multiple network slices (which may be examples of virtual logical networks) over a physical infrastructure shared by multiple application providers. In some examples, the network slices may be isolated end-to-end networks supporting different features for different applications. As described with reference to <FIG>, an AP <NUM> may, in some examples, be included in a <NUM>-enabled CPE (or <NUM>-CPE) and STAs may be referred to as LAN clients. In some examples, one or more aspects of the present disclosure enable a CPE or other wireless communication device to handle a network slice request from a LAN client (for example, a STA <NUM>). In some examples, LAN clients of an AP <NUM> (such as an AP included in a <NUM>-CPE) and their applications may be unaware of the available network slices. In such examples, the AP <NUM> may handle an initiation of a network slice without the LAN clients being aware of the slice initiation. In some other examples, the LAN clients and their applications may be aware of the available network slices. In such examples, a LAN client may solicit a network slice initiation through the CPE (such as the <NUM>-CPE including the AP <NUM>) after receiving messages on the slice availability from the AP <NUM>.

<FIG> shows a pictorial diagram of an example wireless communication network <NUM>. The wireless communications network <NUM> may be an example of a wireless communication network <NUM> and may include an <NUM>-CPE <NUM> (such as a <NUM>-CPE including an AP) and UEs <NUM>-a, <NUM>-b, and <NUM>-c (which may also be examples of STAs), which may be examples of the corresponding devices described with reference to <FIG>. The <NUM>-CPE <NUM> may provide network coverage for a coverage area. The <NUM>-CPE <NUM> and the UEs <NUM>-a, <NUM>-b, and <NUM>-c may communicate over one or more communication links. For example, the <NUM>-CPE <NUM> and the UE <NUM>-a may communicate over a wired communication link <NUM> (such as Ethernet), the <NUM>-CPE <NUM> and the UE <NUM>-b may communicate over a wireless communication link <NUM> (such as Wi-Fi), and the <NUM>-CPE <NUM> and the UE <NUM>-c may communicate over a wireless communication link <NUM> (such as a Wi-Fi communication link or a <NUM> communication link). The UEs <NUM>-a, <NUM>-b, and <NUM>-c in conjunction with the <NUM>-CPE <NUM> may utilize one or more network slices to improve communication efficiency and to obtain a power advantage for communications, among other advantages.

In some examples, the <NUM>-CPE <NUM> may communicate with a base station <NUM> using a wireless communication link <NUM>. The base station <NUM> may be a base station providing or accessing a <NUM> or NR network. The base station <NUM> may communicate with a radio access network (RAN) <NUM> using a wired or wireless communication link <NUM>. As shown with reference to <FIG>, the RAN <NUM> may communicate with a user plane function (UPF) <NUM> using communication link <NUM>. The UPF <NUM> may communicate with a data network <NUM> using communication link <NUM>. In some implementations, the data network <NUM> may be configured to access multiple content providers (or application providers). The data network <NUM> may communicate with a first content provider (Content Provider <NUM>) using communication link <NUM>. Additionally or alternatively, the data network <NUM> may communicate with a second content provider (Content Provider <NUM>) using communication link <NUM>, and may communicate with a third content provider (Content Provider <NUM>) using communication link <NUM>. The wireless communication network <NUM> is configured to perform one or more of the processes <NUM>, <NUM>, and <NUM> described above with reference to <FIG>, <FIG>, and <FIG>, respectively. In some implementations, one or more of the devices in wireless communication network <NUM> can be an example implementation of the devices described herein with reference to <FIG>, <FIG>, and <FIG>.

According to some implementations, the wireless communication network <NUM> may support network slicing. In some examples, wireless communication network (such as the wireless communication network <NUM>) may support <NUM> technology. The <NUM> communication network may be configured to offer different services to applications based on network slices. In some implementations, a network slice can be described as an end-to-end tunnel between an application hosted on a UE (such as UEs <NUM>-a, <NUM>-b, and <NUM>-c) and the application-provider. The network slicing may be supported by the <NUM> core network and the RAN (such as the base station <NUM> in conjunction with the RAN <NUM>). However, solutions for supporting a network slice (with the ability of a user-application requesting or using a network slice) is unavailable for LAN clients (such as UEs or STAs). More specifically, for example, LAN clients supported by a <NUM>-enabled CPE conventionally lack the ability to request or use network slices. Additionally, without the ability to access the network slices, it is challenging for a <NUM>-CPE (such as a home router for wireless broadband service using a <NUM> WAN/<NUM> WLAN/<NUM> network and Wi-Fi/Ethernet) to support ultra-low latency while operating using a Wi-Fi interface.

In some examples, the current network slicing types may be categorized according to Table <NUM>.

As shown in Table <NUM>, each of the network slice type or service type may be associated with different quality of service (QOS) requirements or parameters including latency and performance parameters. In some examples, for the URLLC service type, the network slice provides for a user plane latency value of <NUM> for uplink communications and <NUM> for downlink communications. Furthermore, for the URLLC service type, the latency value may support the use of the next generation access technologies as a wireless transport technology that can be used within the next generation access architecture. In some examples, a reliability key performance indicator may provide a latency value with an associated reliability parameter. In some examples, the latency value may be an average value that does not have an associated high reliability parameter. In some examples, for the eMBB service type, a network slice provides for a user plane latency value of <NUM> for uplink communications and <NUM> for downlink communications. In some examples, a latency value for the eMBB service type may be based on all typical delays associated with the transfer of data packets (for example, an applicable procedural delay when resources are not pre-allocated, an average hybrid automatic repeat request retransmission delay, and delays associated with the network architecture). In some implementations, for the URLLC service type, the QOS parameter associated with the latency may have a higher threshold (<NUM> for uplink communications and <NUM> for downlink communications). To support the URLLC service type, a conventional wireless communication network may support the higher threshold for the QOS parameter associated with the latency between the <NUM> core network (such as the RAN) and the UE.

In addition to the network slice type or service type, one or more operators can define a slice type or service type with the characteristics associated with the operators. Specifically, existing wireless communication networks allow for customized network slices to be created and serviced. Additionally or alternatively, existing wireless communication networks that support network slicing may account for end-to-end latencies. In some examples, end-to-end latencies may include the application latencies on a UE. In some examples, the application latencies for different applications may be <NUM>-<NUM> for the URLLC service type. In some implementations, it may be important to account for application latency as part of an overall end-to-end latency (for example, an end-to-end latency between an application and a <NUM> core network). In an example of a live audio performance that may be associated with an application and a <NUM> core network, there may exist a deterministic latency to receive the live audio over a wireless communication network and an application latency associated with processing a live audio at a UE.

In one or more implementations, the wireless communication network <NUM> may enable the use of network slices by LAN clients (such as UEs <NUM>-a, <NUM>-b, and <NUM>-c). Specifically, the wireless communication network <NUM> may handle a network slice request from one or more of the LAN clients. In some aspects, the wireless communication network <NUM> may handle the access and creation of network slices in two scenarios. In an example of a first scenario, the LAN clients (for example, UE <NUM>-a) and their applications may be unaware of the available network slices. In such an example, the <NUM>-CPE <NUM> may handle an initiation of a network slice without one or more of the LAN clients being aware of a slice initiation. In an example of a second scenario, the LAN clients (for example, UEs <NUM>-b and <NUM>-c) and their applications may be aware of the available network slices. In such an example, the LAN clients may solicit a network slice initiation through the <NUM>-CPE <NUM> after receiving broadcast or multicast messages indicating that network slices are available.

As shown with reference to <FIG>, the UEs <NUM>-a, <NUM>-b, and <NUM>-c may host different applications. For example, an application hosted in the UE <NUM>-a may be associated with the content provider <NUM> (Content Provider <NUM>). Likewise, an application hosted in the UE <NUM>-b may be associated with the content provider <NUM> (Content Provider <NUM>) and an application hosted in the UE <NUM>-c may be associated with the content provider <NUM> (Content Provider <NUM>). According to some implementations, the UEs <NUM>-a, <NUM>-b, and <NUM>-c may utilize different network slices to access different client applications. In some examples, the wireless communication network <NUM> supports signaling between the <NUM>-CPE <NUM> and the LAN clients (for example, the UEs <NUM>-a, <NUM>-b, and <NUM>-c) to enable the use of network slices by the LAN clients. With the framework described with reference to <FIG>, the LAN clients may benefit from requesting and accessing network slices from a <NUM> core network.

<FIG> illustrates an example of a wireless communication system architecture <NUM> according to some implementations. The wireless communication system architecture <NUM> may include a UE <NUM>, a RAN <NUM>, an UPF <NUM>, a data network <NUM>, an authentication server function (AUSF) <NUM>, an access and mobility management function (AMF) <NUM>, a session management function (SMF) <NUM>, a network slice selection function (NSSF) <NUM>, a PCF <NUM>, a unified data management (UDM) <NUM>, and an application function (AF) <NUM>. In addition, the wireless communication system architecture <NUM> may include other functions or entities not displayed with reference to <FIG> or may not include one or more of the functions or entities shown.

As shown with reference to <FIG>, the wireless communication system architecture <NUM> may support LAN clients (such as one or more UEs <NUM>) to participate in a network slice. Specifically, the wireless communication system architecture <NUM> support the use of network slices to support additional features and network function optimizations. For example, a network slice defined within a public land mobile network (PLMN) may include the core network control plane and the user plane network functions. Network slices may differ for different supported features and different network optimizations. In some examples, an operator may deploy multiple network slice instances delivering the same features but for different groups of UEs (for example, as the different groups of UEs may deliver a different committed service or because the different groups of UEs may be dedicated to a customer). A single UE <NUM> can simultaneously be served by one or more network slice instances. In some examples, a threshold associated with a number of concurrent slices be set to eight slices, meaning that a single UE <NUM> may be served by at most eight network slices at a time. The AMF <NUM> instance serving the UE <NUM> may logically belong to each of the network slice instances serving the UE <NUM> (for example, the AMF <NUM> instance may be common to the network slice instances serving a UE <NUM>).

The selection of the set of network slice instances for a UE <NUM> (where each of the network slice instances corresponding to network slice selection assistance information, may be triggered by a first contacted AMF as part of one or more procedures, such as a registration procedure. In some examples, the selection of the set of network slice instances may be triggered by interacting with the NSSF <NUM>, and may lead to a change of the AMF <NUM>. Network slice selection assistance information may be used to uniquely determine a network slice. SMF discovery and selection within the selected network slice instance may be initiated by the AMF <NUM> in response to receiving a session management message from the UE <NUM>. The session management message may include a message to establish a PDU session. In some implementations, different network slice instances may not share a PDU session, though different slices may have slice-specific PDU sessions using the same data network name.

As described above, network slice selection assistance information may be used to determine a network slice and may include a slice or service type (SST) and a slice differentiator (SD), among other examples. The SST may refer to the expected network slice behavior in terms of features and services, and the SD may be optional information that complements the SST to differentiate amongst multiple network slices of the same SST. The selection of a network slice instance serving a UE <NUM> and the core network control plane and user plane network functions corresponding to the network slice instance may be the responsibility of a <NUM> core network. The RAN <NUM> may use requested network slice selection assistance information in access stratum signaling to handle the UE control plane connection before the 5GC informs the RAN <NUM> of the allowed network slice selection assistance information. When a UE <NUM> is successfully registered, the <NUM> core network may inform the RAN <NUM> by providing the allowed network slice selection assistance information for the control plane aspects. When a PDU Session is established using a specific network slice instance, the <NUM> core network may provide to the RAN <NUM>, network slice selection assistance information corresponding to the network slice instance to enable the RAN <NUM> to perform access specific functions.

In some implementations, the establishment of user plane connectivity to a data network via a network slice instance may include selecting an AMF <NUM> that supports the network slices and establishing one or more PDU sessions to the data network <NUM> via the network slice instances. When the AMF <NUM> is selected, the AMF <NUM> may query the UDM <NUM> to retrieve UE subscription information including the subscribed network slice selection assistance information.

In some examples, the AMF <NUM> may be allowed to determine whether it can serve the UE <NUM> based on a configuration associated with the UE <NUM>. For example, the AMF <NUM> may be allowed to determine that it can serve the UE <NUM> based on satisfying at least one parameter associated with the configuration. In addition, the AMF <NUM> may query the NSSF <NUM> with requested network slice selection assistance information, an identifier of a subscription permanent identifier (SUPI), location information, and an indication of the access technology used by the UE <NUM>. Based on such information, a local configuration, and other locally available information including RAN capabilities in a registration area, the NSSF <NUM> may perform one or more operations to select the network slice instances to serve the UE <NUM>. Alternatively, the NSSF <NUM> may defer the selection of the network slice instance until at least one network slice instance in the registration area are able to serve the UE <NUM>.

In some examples, the set of network slices for a UE <NUM> may be dynamically changed while the UE <NUM> is registered with a network. In such examples, the changing of the set of network slices for the UE <NUM> may be initiated by the network or the UE under various conditions. Based on the operational or deployment plans of an operator, multiple network slice instances associated with common network slice selection assistance information may be deployed in the same registration areas or in different registration areas. In some examples, the registration area allocated by the AMF <NUM> to the UE <NUM> may have homogenous support for network slices. When a network slice used for one or multiple protocol data unit sessions becomes no longer available for a UE <NUM> under the same AMF <NUM>, the AMF <NUM> may indicate to the SMF <NUM> to autonomously release the UE <NUM>. In some examples, the establishment of a protocol data unit session in a network slice to the data network <NUM> may allow data transmission in a network slice.

<FIG> shows a block diagram of an example wireless communication device <NUM> that supports techniques for LAN clients participation in a network slice according to some implementations. In some implementations, the wireless communication device <NUM> is configured to perform one or more of the processes <NUM>, <NUM>, and <NUM> described above with reference to <FIG>, <FIG>, and <FIG>, respectively. In some implementations, the wireless communication device <NUM> can be an example implementation of a wireless communication device described herein with reference to <FIG> or a wireless communication device described herein with reference to <FIG>. For example, the wireless communication device <NUM> can be a chip, SoC, chipset, package or device that includes at least one processor, a Wi-Fi (IEEE <NUM>) modem, and a cellular modem. In some implementations, the wireless communication device <NUM> can be a CPE or a device for use in a CPE (as such, the wireless communication device <NUM> may hereinafter be referred to as CPE <NUM>). In some implementations, the CPE <NUM> can be, or can include, an AP (such as AP <NUM>) for serving one or more WLANs such as using a Wi-Fi network or a <NUM> network.

The wireless communication device <NUM> (or CPE <NUM>) includes a QOS manager <NUM>, a CPE data-path manager <NUM>, a CPE connection manager <NUM>, a <NUM> connection manager <NUM>, a digital subscriber line (DSL)/gigabit passive optical network (GPON) connection manager <NUM>, a WLAN connection manager <NUM>, a LAN or Ethernet connection manager <NUM>, a <NUM> modem <NUM>, a DSL/GPON modem <NUM>, a WLAN chipset <NUM>, and an Ethernet chipset <NUM>. Portions of one or more of the modules <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may be implemented at least in part in hardware or firmware. In some implementations, at least some of the modules <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are implemented at least in part as software stored in a memory. For example, portions of one or more of the modules <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> can be implemented as non-transitory instructions (or "code") executable by a processor to perform the functions or operations of the respective module.

The CPE connection manager <NUM> may be configured to setup connections between the LAN and wide area network (WAN) interfaces. As depicted with reference to <FIG>, the WAN interferes may include a <NUM> WAN interface and a DSL/GPON WAN interface. In some implementations, the <NUM> WAN and the DSL/GPON WAN may be referred to as hybrid WANs. In some examples, such hybrid WANs may be used by the CPE <NUM>. In some implementations, the CPE connection manager <NUM> may be configured to perform traffic switching and traffic steering. Additionally or alternatively, the CPE connection manager <NUM> may be configured to setup one or more channels across multiple LAN and WAN interfaces. In some implementations, the CPE connection manager <NUM> may be configured to setup or terminate (for example, tear down) connections with the network or with one or more WLAN clients (such as STA <NUM>). According to some implementations, the CPE connection manager <NUM> in conjunction with the QOS manager <NUM>, may setup or terminate one or more connections (as further described with reference to <FIG> and <FIG>).

The QOS manager <NUM> may be configured to determine whether new QOS flows may be admitted into an existing flow. For example, the QOS manager <NUM> may be configured to control admission of new QOS flows and sustain the committed QOS flows. In some examples, the QOS manager <NUM> may be configured to determine one or more QOS parameters associated with a <NUM> network (such as a <NUM> WAN or a <NUM> WLAN). In such implementations, the QOS manager <NUM> may be configured to coordinate the QOS flows on the LAN (such as Ethernet and Wi-Fi) as well as the <NUM> WAN or the <NUM> WLAN (such as DSL/GPON). In some examples, QOS manager <NUM> may be configured to coordinate the QOS flows using one or more committed QOS parameters. In some implementations, the QOS manager <NUM> may be configured to determine resource allocations (such as a buffer resource allocation) within CPE <NUM>. In some example, the QOS manager <NUM> may be configured to determine random access memory (RAM) supported by various interfaces and data rates supported by various interfaces. In some examples, the QOS manager <NUM> may be configured to optimize the resources within the CPE <NUM>. In some examples, the QOS manager <NUM> may be configured to tag the resources to multiple states (such as green, yellow, and red) on a periodic basis to facilitate decision making during an admission of a QOS flow associated with a session or a network slice. Additionally or alternatively, the QOS manager <NUM> may be configured to tag the resources to multiple states to effectively sustain a session or a network slice.

As shown with reference to <FIG>, the CPE connection manager <NUM>, the QOS manager <NUM>, and the CPE data-path manager <NUM> may be coupled with each other, and may be configured to transmit and receive one or more commands and notifications. In some implementations, the CPE data-path manager <NUM> may be configured to handle traffic, including traffic switching, maintaining traffic statistics, and transmitting and receiving traffic on various interfaces. In some examples, the CPE data-path manager <NUM> may be configured to manage traffic received or transmitted using a combination of the <NUM> connection manager <NUM>, the DSL/GPON connection manager <NUM>, the WLAN connection manager <NUM>, the LAN or Ethernet connection manager <NUM>, the <NUM> modem <NUM>, the DSL/GPON modem <NUM>, the WLAN chipset <NUM>, and the Ethernet chipset <NUM>. In some example, the <NUM> modem <NUM> may be coupled with a URSP daemon (not shown). The URSP daemon may be configured to manage a route selection policy for a UE. In some examples, the URSP daemon may be configured to receive one or more updates to the route selections resulting from network changes including changes initiated by a Policy and Charging Framework (PCF). In some examples, the URSP daemon may be configured to receive one or more updates at a run-time. Additionally or alternatively, the URSP daemon may be configured to track all the slice selection assistance information (such as network slice selection assistance information, configured slice selection assistance information, or allowed slice selection assistance information).

<FIG> shows an example timing diagram <NUM> illustrating an example process for LAN clients to participate in a network slice according to some implementations. The timing diagram <NUM> may be implemented by a combination of a UE <NUM> (such as STA <NUM> or a LAN client), a <NUM>-CPE <NUM> (such as AP <NUM>), a wireless communication network (such as <NUM> network <NUM>), and an application provider <NUM>. The UE <NUM> and the <NUM>-CPE <NUM> may be examples of the corresponding devices described with reference to <FIG> and <FIG>. The <NUM>-CPE <NUM> may include a CPE connection manager <NUM>, a <NUM> connection manager <NUM>, a QOS manager <NUM>, a URSP daemon <NUM>, and a <NUM> modem <NUM>. Each of the components included in the <NUM>-CPE <NUM> may be examples of the corresponding devices described with reference to <FIG>. Although not depicted in <FIG>, the UE <NUM> may include or host one or more applications.

In some implementations, the <NUM>-CPE <NUM> maybe an example of an AP having a capability to access the <NUM> network (such as <NUM> network <NUM>). The UE <NUM> and the <NUM>-CPE <NUM> may access network slices (such as network slices available in a <NUM> network) to improve communication efficiency and end-to-end latency. In the example of <FIG>, the UE <NUM> may not be aware of one or more network slices supported by the <NUM> network <NUM>. Alternative examples of the timing diagram <NUM> may be implemented, in which some steps may be performed in a different order than described, some steps may be added, or some steps may not be performed at all. In some implementations, steps may include additional features not described below.

At <NUM>, the UE <NUM> may initialize an application (such as an application hosted on the UE <NUM>). In some implementations the UE <NUM> may transmit, to the <NUM>-CPE <NUM>, a request to initialize the application using a first wireless area network. In some examples, the first wireless area network may include a default packet data network. Additionally or alternatively, the first area network may include a WAN. In some implementations, upon receiving the request from the UE <NUM>, the <NUM>-CPE <NUM> may transmit another request (such as a second request) to a network device (such as to the application provider <NUM>) to request the application provider <NUM> to initialize the application of the UE <NUM> using the default packet data network or the default WAN. In some examples, the <NUM>-CPE <NUM> may receive information associated with network slices based on the request at <NUM>.

At <NUM>, the UE <NUM> may receive an indication of a successful initialization of the application hosted by the UE <NUM>. In some examples, the <NUM>-CPE <NUM> may receive the indication from the application provider <NUM>, and the <NUM>-CPE <NUM> may forward the information (or a message based on the received information) to the UE <NUM>.

At <NUM>, the <NUM>-CPE <NUM> may analyze (one time or iteratively) the received information to determine an available network slice from a set of network slices supported by the <NUM> network <NUM>. In some implementations, the URSP daemon <NUM> may receive the network slice selection assistance information and may forward the network slice selection assistance information to the <NUM> connection manager <NUM>. The <NUM> connection manager <NUM> may analyze the network slice selection assistance information and determine the available network slices.

At <NUM>, the <NUM>-CPE <NUM> may populate the available network slices on a web interface for display to the UE <NUM>. In some implementations, the <NUM> connection manager <NUM> may indicate the available network slice to the CPE connection manager <NUM>, and the CPE connection manager <NUM> populate the available network slices. For example, the CPE connection manager <NUM> may program one or more rules and may generate a message to be transmitted to the UE <NUM>.

In some implementations, the <NUM>-CPE <NUM> may provide an option to a user operating the UE <NUM> to provide credentials for accessing or establishing a network slice. In some example implementations, the message may be a multicast message or a broadcast message.

At <NUM>, the UE <NUM> may determine whether there is a plug-in available to communicate with the <NUM>-CPE <NUM>. In some implementations the UE <NUM> may determine that the plug-in to communicate with the <NUM>-CPE <NUM> (such as a plug-in to communicate with the CPE connection manager <NUM> or the <NUM> connection manager <NUM>) is not available at the UE <NUM>.

At <NUM>, the UE <NUM> may transmit one or more credentials (such as one or more identifiers) to the <NUM>-CPE <NUM>. If the user of the <NUM>-CPE <NUM> (for example, the UE <NUM> or a user operating the UE <NUM>) provides the credentials for accessing the available network slices, then the <NUM>-CPE <NUM> may program one or more rules in the CPE connection manager <NUM> to filter requests associated with configured services or configured network slices. The rules may filter the request and may forward the requests to the CPE connection manager <NUM>.

In some implementations, the <NUM>-CPE <NUM> may determine that an application on the UE <NUM> has initiated an application session (for example, using domain name system or deep packet inspection or both). The <NUM>-CPE <NUM> may be configured to track the request and share the request with the CPE connection manager <NUM>. The CPE connection manager <NUM> may then request validation of the credentials with <NUM> connection manager <NUM> to determine whether the provided credentials match one or more pre-configured credentials. In an example in which the credentials do not match, the CPE connection manager <NUM> may allocate the data flow (such as the data flow associated with the initiated application session) to a default packet data network.

At <NUM>, the CPE connection manager <NUM> may validate the credentials or identifiers received at <NUM>, and the CPE connection manager <NUM> may transmit a request including the identifier to the <NUM> connection manager <NUM>.

At <NUM>, the <NUM> connection manager <NUM> may transmit a request for an available network slice or a new network slice to the QOS manager <NUM>. For example, the <NUM> connection manager <NUM> may transmit the request to determine approval for establishing the new network slice. The QOS manager <NUM> may determine one or more data packets associated with the available network slice and may further determine whether the one or more data packets satisfy a QOS threshold. In order to determine the QOS threshold, the QOS manager <NUM> may transmit a request to the URSP daemon <NUM> at <NUM>.

In some implementations, the QOS manager <NUM> may determine whether a data flow associated with an available network slice or a new network slice can be admitted into a data queue, based on a policy associated with the available network slice. Additionally or alternatively, the QOS manager <NUM> may determine whether one or more data packets associated with a network slice satisfy the QOS threshold. At <NUM>, the <NUM> connection manager <NUM> may receive an approval from the URSP daemon <NUM> indicating that the one or more data packets satisfy the QOS threshold.

Upon receiving the approval, the <NUM> connection manager <NUM> may transmit a request at <NUM> to setup a network slice (such as an available network slice or a new network slice) to the application provider <NUM>. In some implementations, at <NUM>, the <NUM> connection manager <NUM> may transmit one or more requests (such as iterative requests) to the CPE connection manager <NUM>. In some implementations, a request transmitted to the CPE connection manager <NUM> may include a request to setup a network slice. In response to the request received by the CPE connection manager <NUM>, the CPE connection manager <NUM> may transmit at <NUM> a confirmation of a successful setup of the network slice.

In some examples, at <NUM>, the <NUM> network and the application provider may setup a network slice. At <NUM>, the <NUM> connection manager <NUM> may receive a confirmation to access an available network slice, and at <NUM>, the <NUM> connection manager <NUM> may establish a connection associated with the available network slice.

At <NUM>, the <NUM> connection manager <NUM> may transmit an indication of a successful setup of a network slice to the CPE connection manager <NUM>. At <NUM>, the CPE connection manager <NUM> may transmit, to the UE <NUM>, a confirmation to access the available network slice. At <NUM>, the UE <NUM> may map a data session to a new packet data network. In some implementations, the <NUM>-CPE <NUM> may route traffic related to the established network slice over the new packet data network. At <NUM>, the <NUM>-CPE <NUM> (at the URSP daemon <NUM>) may be configured to auto-learn and setup one or more QOS rules or parameters associated with the established or accessed network slice.

At <NUM>, the UE <NUM> may transmit, to the CPE connection manager <NUM>, an indication to close the communication session with the one or more other devices. At <NUM>, the CPE connection manager <NUM> may transmit the indication to the <NUM> connection manager <NUM>.

At <NUM>, the <NUM>-CPE <NUM> (at the CPE connection manager <NUM>) may receive an indication of a released network slice from the UE <NUM>. For example, the UE <NUM> may release a network slice in response to closing the communication session, and may transmit the indication of the released network slice to the <NUM>-CPE <NUM>. In some examples, the released network slice may include the available network slice. At <NUM>, the CPE connection manager <NUM>, in conjunction with the <NUM> network <NUM>, may terminate the packet data network (or connection) associated with the available network slice. At <NUM>, the <NUM> network <NUM>, in conjunction with the application provider <NUM>, may confirm the termination of the packet data network using an iterative process.

At <NUM>, the <NUM> network <NUM> may transmit to the <NUM> connection manager <NUM> an indication of a successful termination of the packet data network. At <NUM>, the <NUM> connection manager <NUM> may transmit a message to release network slice resources (such as frequency resources and time resources) to the QOS manager <NUM>. At <NUM>, upon receiving the message, the QOS manager <NUM> may update the QOS parameter associated with the released network slice.

At <NUM>, the <NUM> connection manager <NUM> may transmit a message to the CPE connection manager <NUM> indicating a release of one or more resources associated with the released network slice. At <NUM>, the CPE connection manager <NUM> may transmit, to the UE <NUM>, a message indicating a release of one or more resources associated with the released network slice.

<FIG> shows an example timing diagram <NUM> illustrating an example process for LAN clients to participate in a network slice according to some implementations. The timing diagram <NUM> may be associated with a combination of a UE <NUM> (such as STA <NUM> or a LAN client), a <NUM>-CPE <NUM> (such as AP <NUM>), a wireless communication network (such as <NUM> network <NUM>), and an application provider <NUM>. The UE <NUM> and the <NUM>-CPE <NUM> may be examples of the corresponding devices described with reference to <FIG> and <FIG>. The <NUM>-CPE <NUM> may include a CPE connection manager <NUM>, a <NUM> connection manager <NUM>, a QOS manager <NUM>, a URSP daemon <NUM>, and a <NUM> modem <NUM>. Each of the components included in the <NUM>-CPE <NUM> may be examples of the corresponding devices described with reference to <FIG>. Although not depicted in <FIG>, the UE <NUM> may include or host one or more applications.

In some implementations, the <NUM>-CPE <NUM> may be an example of an AP having a capability to access the <NUM> network <NUM>. The UE <NUM> and the <NUM>-CPE <NUM> may access network slices (such as network slices available in a <NUM> network) to improve communication efficiency and end-to-end latency. In the example of <FIG>, the UE <NUM> may be aware of one or more network slices supported by the <NUM> network <NUM>. Alternative examples of the timing diagram <NUM> may be implemented, in which some steps may be performed in a different order than described, some steps may be added, or some steps may not be performed at all. In some implementations, steps may include additional features not described below.

At <NUM>, the UE <NUM> may initialize an application (such as an application hosted on the UE <NUM>). As part of the initialization, the UE <NUM> may transmit, to the <NUM>-CPE <NUM>, a request to initialize the application using a first wireless area network. In some implementations, the first wireless area network may include a default packet data network. Additionally or alternatively, the first area network may include a default WAN/WLAN. In some implementations, upon receiving the request from the UE <NUM>, the <NUM>-CPE <NUM> may transmit another request (such as a second request) to a network device (such as to the application provider <NUM>). In some examples, the <NUM>-CPE <NUM> may request the application provider <NUM> to initialize the application of the UE <NUM> using the default packet data network or the default WAN/WLAN. In some examples, the <NUM>-CPE <NUM> may receive information associated with a set of network slices based on transmitting the second request.

At <NUM>, the UE <NUM> may receive an indication of a successful initialization of the application hosted at the UE <NUM>. In some examples, the <NUM>-CPE <NUM> may receive the indication of the successful initialization of the application from the application provider <NUM>, and the <NUM>-CPE <NUM> may forward the information (or a message based on the received information) to the LAN client <NUM>.

At <NUM>, the <NUM>-CPE <NUM> may analyze the received information to determine an available network slice from the set of network slices. In some implementations, the <NUM>-CPE <NUM> may receive at least one of network slice selection assistance information, configured slice selection assistance information, or allowed slice selection assistance information. In some examples, the URSP daemon <NUM> may receive the network slice selection assistance information. The <NUM> connection manager <NUM> may analyze the network slice selection assistance information and determine the available network slice. The <NUM> connection manager <NUM> may then indicate the available network slice to the CPE connection manager <NUM>.

At <NUM>, the <NUM>-CPE <NUM> may populate the available network slices (such as network slices obtained from the URSP daemon <NUM>) on a web interface for display to the UE <NUM>. The <NUM>-CPE <NUM> may provide an option to a user operating the UE <NUM> to provide credentials for accessing or establishing a network slice. In some examples, the CPE connection manager <NUM> may program one or more rules and may generate a message to be transmitted to the UE <NUM>. In some example implementations, the message may be a multicast message or a broadcast message.

At <NUM>, the UE <NUM> may determine whether there is a plug-in available to communicate with the <NUM>-CPE <NUM>. In some implementations the UE <NUM> may identify a plug-in to communicate with the <NUM>-CPE <NUM> (such as a plug-in to communicate with the CPE connection manager <NUM> or the <NUM> connection manager <NUM>).

At <NUM>, the <NUM>-CPE <NUM> (such as the CPE connection manager <NUM>) may transmit a messages, such as a multicast message or a broadcast message, indicating an available network slice. For example, the <NUM>-CPE <NUM> may transmit the multicast message or the broadcast message to one or more LAN clients served by the <NUM>-CPE <NUM> (such as the UE <NUM>). In some examples, the multicast message or the broadcast message may be referred to as discovery messages. In some examples, the <NUM>-CPE <NUM> may broadcast one or more discovered or configured network slices (such as available network slices) to the UE <NUM> using a universal plug-and-play message or one or more other multicast messages.

At <NUM>, the UE <NUM> may request to access the available network slice (such as the available network slice indicated in the multicast message or the broadcast message). For example, the CPE connection manager <NUM> may receive the request to access the available network slice from the UE <NUM>. In some implementations, the request may be based on the multicast message or broadcast message transmitted at <NUM>. In some examples, an application hosted on the UE <NUM> may use a universal plug-and-play message to request a creation of a network slice through the CPE Connection Manager <NUM>.

At <NUM>, the CPE connection manager <NUM> may transmit the request to access the available network slice to the <NUM> connection manager <NUM>. In some implementations, the CPE connection manager <NUM> may determine that the received request (such as the request received from the UE <NUM>) includes a request to create a new network slice. In such an example, the CPE connection manager <NUM> may forward the request to create the new network slice to the <NUM> connection manager <NUM>.

At <NUM>, the <NUM> connection manager <NUM> may transmit a request for an available network slice or a new network slice to the QOS manager <NUM>. The QOS manager <NUM> may determine one or more data packets associated with the available network slice and may further determine whether the one or more data packets satisfy a QOS threshold. To determine the QOS threshold, the QOS manager <NUM> may transmit a request to the URSP daemon <NUM> at <NUM>. In some implementations, the QOS manager <NUM> may determine whether a data flow associated with an available network slice or a new network slice can be admitted into a data queue. In some examples, the request transmitted to the URSP daemon <NUM> may include a request to check a policy associated with the available network slice. Additionally or alternatively, the QOS manager <NUM> may determine one or more data packets associated with the a new network slice and may determine whether the one or more data packets satisfy the QOS threshold. At <NUM>, the <NUM> connection manager <NUM> may receive an approval from the URSP daemon <NUM> indicating that the one or more data packets (such as one or more data packets associated with the available network slice or one or more data packets associated with a new network slice) satisfy the QOS threshold.

Upon receiving the approval from the QOS manager <NUM>, the <NUM> connection manager <NUM> may transmit a request at <NUM> to setup a network slice (such as an available network slice or a new network slice). As described with reference to <FIG>, the <NUM> connection manager <NUM> may transmit the request to setup the network slice to the application provider <NUM>. In some implementations, the CPE connection manager <NUM> may request a new network slice to be setup through the <NUM> connection manager <NUM>. For example, at <NUM>, the <NUM> connection manager <NUM> may transmit one or more requests (such as iterative requests) to the CPE connection manager <NUM>. In some implementations, a request transmitted to the CPE connection manager <NUM> may include a request to setup a network slice. In response to the request received by the CPE connection manager <NUM>, the CPE connection manager <NUM> may transmit at <NUM> a confirmation of a successful setup of the network slice.

In some examples, at <NUM>, the <NUM> network and the application provider may setup a network slice (for example using an iterative method to request a setup associated with a network slice and confirm the setup associated with the network slice). At <NUM>, the <NUM> connection manager <NUM> may receive a confirmation to access an available network slice (such as the available network slice requested by the UE t <NUM>). For example, the <NUM> connection manager <NUM> may receive the confirmation from a network device (such as the application provider <NUM>).

At <NUM>, once the network slice setup is successful, the <NUM> connection manager <NUM> may establish a connection associated with the available network slice. For example, the <NUM> connection manager <NUM> alone or in conjunction with the <NUM> modem may establish a packet data network associated with a requested network slice (such as available network slice or new network slice). At <NUM>, the <NUM> connection manager <NUM> may transmit an indication of a successful setup of a network slice to the CPE connection manager <NUM>.

At <NUM>, the CPE connection manager <NUM> may transmit, to the UE <NUM>, a confirmation to access the available network slice. At <NUM>, the UE <NUM> may access a new data session with the application provider <NUM>. For example, upon a successful establishment of a connection (such as a packet data network) at the <NUM>-CPE <NUM>, the connection may then be forwarded to the UE <NUM> for further usage. In some implementations, the <NUM>-CPE <NUM> may route traffic related to the established network slice over the established packet data network by programming one or more rules in a dataflow associated with the traffic. In some implementations, the <NUM>-CPE <NUM> may program the dataflow at an acceleration or data-path engine of the <NUM>-CPE <NUM> (not shown). In some examples, at <NUM>, the <NUM>-CPE <NUM> (at the URSP daemon <NUM>) may be configured to auto-learn and setup one or more QOS rules (or QOS parameters) associated with the established or accessed network slice. For example, the URSP daemon <NUM> may determine at least one QOS parameter associated with the available network slice based on initiating the new communication session.

At <NUM>, the UE <NUM> may transmit, to the application provider <NUM>, an indication to terminate the new communication session (for example, the communication session established using available network slices). In some implementations, the <NUM>-CPE <NUM> may receive an indication of a termination of the new communication session associated with the available network slice. At <NUM>, the application provider <NUM> may indicate, the UE <NUM> , that the communication session has successfully closed. In some examples, the <NUM>-CPE <NUM> may transmit, to the UE <NUM>, a confirmation to terminate the new communication session associated with the available network slice.

At <NUM>, the <NUM>-CPE <NUM> (at the CPE connection manager <NUM>) may receive an indication of a released network slice from the UE <NUM>. In some implementations, the <NUM>-CPE <NUM> may receive the indication based on transmitting the confirmation to terminate the new communication session. For example, the UE <NUM> may release a network slice in response to termination of the communication session, and may transmit the indication of the released network slice to the <NUM>-CPE <NUM>. In some examples, the released network slice may include the available network slice (such as the available network slice determined by the <NUM>-CPE <NUM>). At <NUM>, the CPE connection manager <NUM> may transmit the indication of the released network slice to the <NUM> connection manager <NUM>. In some examples, the CPE connection manager <NUM> may forward the indication received from the UE <NUM>. Alternatively, the CPE connection manager <NUM> may transmit a second indication based on the indication received from the UE <NUM>.

At <NUM>, the <NUM>-CPE <NUM> in conjunction with the <NUM> network <NUM> may terminate the packet data network (or connection) associated with the available network slice. At <NUM>, the <NUM> network <NUM> in conjunction with the application provider <NUM> may confirm the termination of the packet data network using an iterative process.

At <NUM>, the <NUM> network <NUM> may transmit to the <NUM> connection manager <NUM>, an indication of a successful termination of the packet data network. At <NUM>, the <NUM> connection manager <NUM> may transmit a message to the QOS manager <NUM>. The message may include an indication to release network slice resources (such as frequency resources and time resources). At <NUM>, upon receiving the message from the <NUM> connection manager <NUM>, the QOS manager <NUM> may update the QOS parameter associated with the released network slice.

At <NUM>, the <NUM> connection manager <NUM> may transmit a message to the CPE connection manager <NUM> indicating a release of one or more resources associated with the released network slice. In some examples, the message to the CPE connection manager <NUM> may be the same as or based on the message described at <NUM>. At <NUM>, the CPE connection manager <NUM> may transmit, to the UE <NUM>, a message indicating a release of one or more resources associated with the released network slice. As described herein, the message to the UE <NUM> may be the same as or based on the message described at <NUM>.

<FIG> illustrates an example process <NUM> for LAN clients to participate in a network slice according to some implementations. The process <NUM> may be associated with a <NUM>-CPE (such as AP <NUM>), which may be an example of a wireless communication device. The <NUM>-CPE may be configured to perform one or more of the processes <NUM>, <NUM>, and <NUM> described above with reference to <FIG>, <FIG>, and <FIG>, respectively. In some implementations, the <NUM>-CPE can be an example implementation of a wireless communication device <NUM> described herein with reference to <FIG>, or a wireless communication device described herein with reference to <FIG> or a wireless communication device described herein with reference to <FIG>. For example, the <NUM>-CPE can be a chip, SoC, chipset, package or device that includes at least one processor, a Wi-Fi (IEEE <NUM>) modem, and a cellular modem.

Alternative examples of the process <NUM> may be implemented, in which some steps may be performed in a different order than described, some steps may be added, or some steps may not be performed at all. In some implementations, steps may include additional features not described below.

In some implementations, in block <NUM>, the <NUM>-CPE (such as a CPE having a capability to access a <NUM> network) is initialized (or started). In block <NUM>, the <NUM>-CPE may initialize multiple components. In block <NUM>, the <NUM>-CPE may determine whether network slices are available. In block <NUM>, in response to determining that network slices are available, the <NUM>-CPE may broadcast or multicast the network slice information to one or more UEs (such as STAs or LAN clients). In block <NUM>, in response to determining that network slices are available, the <NUM>-CPE may configure corresponding flow rules to trap (or collect) traffic associated with a network slice. As described with reference to <FIG>, the process described in block <NUM> may be associated with UEs unaware of network slices. Additionally or alternatively, the process described in block <NUM> may be associated with UEs aware of network slices.

In some implementations, in block <NUM>, the <NUM>-CPE may receive a request to add a network slice or delete a network slice. In block <NUM>, in response to collecting traffic associated with the network slice, the <NUM>-CPE may determine whether one or more credentials match an existing credential. Additionally or alternatively, the <NUM>-CPE may determine whether one or more credentials match an existing credential in response to receiving the request to add the network slice or delete the network slice. If the <NUM>-CPE determines that the one or more credentials do not match the existing credential, in block <NUM>, the <NUM>-CPE may terminate slice initiation and route the application through a default data network.

In some implementations, in response to determining that the one or more credentials match the existing credential, in block <NUM>, the <NUM>-CPE may determine whether the network slice may be admitted in a data flow. In block <NUM>, in response to determining that the network slice may be admitted, the <NUM>-CPE may initiate the network slice. Alternatively, in block <NUM>, in response to determining that the network slice may not be admitted, the <NUM>-CPE may stop (or terminate) slice initiation and route the application through a default data network. In block <NUM>, the <NUM>-CPE may communicate success or failure of slice creation to clients and create flow mappings if slice creation is successful.

In some implementations, initializing multiple components in block <NUM> includes initializing multiple components of the <NUM>-CPE. For example, the <NUM>-CPE initializes a CPE connection manager, a <NUM> connection manager, a QOS manager, and a URSP daemon, each of which may be examples of modules described with reference to <FIG>.

<FIG> shows a block diagram of an example wireless communication device that supports techniques for LAN clients participation in a network slice according to some implementations. In some implementations, the wireless communication device is configured to perform one or more of the processes <NUM>, <NUM>, and <NUM> described above with reference to <FIG>, <FIG>, and <FIG>, respectively. In some implementations, the wireless communication device can be an example implementation of a wireless communication device <NUM> described herein with reference to <FIG> or a wireless communication device described herein with reference to <FIG>. For example, the wireless communication device can be a chip, SoC, chipset, package or device that includes at least one processor, a Wi-Fi (IEEE <NUM>) modem, and a cellular modem.

In some implementations, the wireless communication device can be a CPE or a device for use in a CPE (as such, the wireless communication device may hereinafter be referred to as CPE). In some implementations, the CPE can be, or can include, an AP (such as AP <NUM>) for serving one or more WLANs such as using a Wi-Fi network or a <NUM> network.

The wireless communication device may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. Portions of one or more of the modules <NUM>, <NUM>, and <NUM> may be implemented at least in part in hardware or firmware. In some implementations, at least some of the modules <NUM>, <NUM>, and <NUM> are implemented at least in part as software stored in a memory. For example, portions of one or more of the modules <NUM>, <NUM>, and <NUM> can be implemented as non-transitory instructions (or "code") executable by a processor to perform the functions or operations of the respective module.

The receiver <NUM> is configured to receive information such as packets, user data, or control information associated with various information channels (for example, control channels, data channels, and information related to participation of LAN clients in a network slice). Information may be passed on to other components of the device. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The receiver <NUM> may utilize a single antenna or a set of antennas.

The communications manager <NUM> may transmit, to one or more LAN clients of the device, a multicast message indicating an available network slice. The communications manager <NUM> may then receive, from a first LAN client of the one or more LAN clients based on the multicast message, a request to access the available network slice and establish, at the wireless communication device based on receiving the request, a connection associated with the available network slice. The communications manager <NUM> may transmit, to the first LAN client based on establishing the connection, a confirmation to access the available network slice.

The communications manager <NUM> may also transmit, to one or more LAN clients of the device, a multicast message indicating an available network slice. The communications manager <NUM> may receive, from a first LAN client of the one or more LAN clients based on the multicast message, an identifier associated with the available network slice, establish, at the device based on a successful validation of the identifier, a connection associated with the available network slice, and transmit, to the first LAN client based on establishing the connection, a confirmation to access the available network slice. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

The transmitter <NUM> may transmit signals generated by other components of the device.

<FIG> shows a block diagram of an example wireless communication device that supports techniques for LAN clients participation in a network slice according to some implementations. In some implementations, the wireless communication device is configured to perform one or more of the processes <NUM>, <NUM>, and <NUM> described above with reference to <FIG>, <FIG>, and <FIG>, respectively. In some implementations, the wireless communication device can be an example implementation of a wireless communication device <NUM> described herein with reference to <FIG> or a wireless communication device described herein with reference to <FIG>. For example, the wireless communication device can be a chip, SoC, chipset, package or device (such as a CPE) that includes at least one processor, a Wi-Fi (IEEE <NUM>) modem, and a cellular modem).

In some implementations, the wireless communication device can be a CPE or a device for use in a CPE (as such, the wireless communication device may hereinafter be referred to as CPE). In some implementations, the CPE can be, or can include, an AP (such as AP <NUM>) for serving one or more WLANs such as using a Wi-Fi network or a <NUM> network.

The wireless communication device includes a receiver <NUM>, a communications manager <NUM>, a message component <NUM>, a request processing component <NUM>, a connection establishment component <NUM>, a confirmation component <NUM>, an identifier component <NUM>, and a transmitter <NUM>. Portions of one or more of the modules <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may be implemented at least in part in hardware or firmware. In some implementations, at least some of the modules <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are implemented at least in part as software stored in a memory. For example, portions of one or more of the modules <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> can be implemented as non-transitory instructions (or "code") executable by a processor to perform the functions or operations of the respective module.

The receiver <NUM> may receive information such as packets, user data, or control information associated with various information channels (for example, control channels, data channels, and information related to participation of LAN clients in a network slice). Information may be passed on to other components of the device. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The receiver <NUM> may utilize a single antenna or a set of antennas.

The communications manager <NUM> may be an example of aspects of the communications manager <NUM> as described herein. The communications manager <NUM><NUM> is configured to include a message component <NUM>, a request processing component <NUM>, a connection establishment component <NUM>, a confirmation component <NUM>, and an identifier component <NUM>. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

The message component <NUM> is configured to transmit, to one or more LAN clients of the device, a multicast message indicating an available network slice. The request processing component <NUM> is configured to receive, from a first LAN client of the one or more LAN clients based on the multicast message, a request to access the available network slice.

The connection establishment component <NUM> is configured to establish, at the device based on receiving the request, a connection associated with the available network slice. The confirmation component <NUM> is configured to transmit, to the first LAN client based on establishing the connection, a confirmation to access the available network slice.

The message component <NUM> is configured to transmit, to one or more LAN clients of the device, a multicast message indicating an available network slice. The identifier component <NUM> is configured to receive, from a first LAN client of the one or more LAN clients based on the multicast message, an identifier associated with the available network slice.

The connection establishment component <NUM> is configured to establish, at the device based on a successful validation of the identifier, a connection associated with the available network slice. The confirmation component <NUM> is configured to transmit, to the first LAN client based on establishing the connection, a confirmation to access the available network slice.

The transmitter <NUM> is configured to transmit signals generated by other components of the device.

<FIG> shows a block diagram of an example wireless communication device that supports techniques for LAN clients participation in a network slice according to some implementations. In some implementations, the wireless communication device is configured to perform one or more of the processes <NUM>, <NUM>, and <NUM> described above with reference to <FIG>, <FIG>, and <FIG>, respectively. In some implementations, the wireless communication device can be an example implementation of a wireless communication device <NUM> described herein with reference to <FIG> or a wireless communication device described herein with reference to <FIG> or a wireless communication device described herein with reference to <FIG>. For example, the wireless communication device can be a chip, SoC, chipset, package or device (such as a CPE) that includes at least one processor, a Wi-Fi (IEEE <NUM>) modem, and a cellular modem.

The wireless communication device includes a message component <NUM>, a request processing component <NUM>, a connection establishment component <NUM>, a confirmation component <NUM>, a network slice component <NUM>, a QOS component <NUM>, an approval component <NUM>, an information component <NUM>, a communication session component <NUM>, and an identifier component <NUM>. Portions of one or more of the modules <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may be implemented at least in part in hardware or firmware. In some implementations, at least some of the modules <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are implemented at least in part as software stored in a memory. For example, portions of one or more of the modules <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> can be implemented as non-transitory instructions (or "code") executable by a processor to perform the functions or operations of the respective module.

The message component <NUM> is configured to transmit, to one or more LAN clients of the device, a multicast message indicating an available network slice. In some examples, the message component <NUM> is configured to transmit, to one or more LAN clients of the device, a multicast message indicating an available network slice. In some implementations, the multicast message includes one or more of a broadcast message, or a universal plug-and-play message.

The request processing component <NUM> is configured to receive, from a first LAN client of the one or more LAN clients based on the multicast message, a request to access the available network slice. The connection establishment component <NUM> is configured to establish, at the device (such as a CPE) based on receiving the request, a connection associated with the available network slice. The confirmation component <NUM> may transmit, to the first LAN client based on establishing the connection, a confirmation to access the available network slice.

The network slice component <NUM> is configured to determine one or more data packets associated with the available network slice. The QOS component <NUM> is configured to determine whether the one or more data packets satisfy a QOS threshold, where establishing the connection associated with the available network slice is based on determining that the one or more data packets satisfy the QOS threshold.

In some examples, the request processing component <NUM> is configured to transmit, to a network device based on receiving the request, a second request to access the available network slice. In some examples, the confirmation component <NUM> is configured to receive, from the network device, a confirmation to access the available network slice, where establishing the connection associated with the available network slice is based on receiving the confirmation from the network device, and where the confirmation transmitted to the first LAN client is based on the confirmation received from the network device.

In some examples, the network slice component <NUM> is configured to receive, from the network device, information associated with a set of network slices based on transmitting the request. In some examples, the network slice component <NUM> is configured to delete the second network slice based on receiving the second request.

In some examples, the request processing component <NUM> is configured to receive, from the first LAN client, a second request to create a new network slice, where the second request is based on the multicast message. The approval component <NUM> is configured to determine an approval status associated with the new network slice. In some examples, the request processing component <NUM> is configured to transmit, to a network device based on determining the approval status, a third request to access the new network slice. In some examples, the confirmation component <NUM> is configured to receive, from the network device based on transmitting the third request, a confirmation to access the new network slice.

In some examples, the message component <NUM> is configured to transmit the multicast message is based on determining the available network slice. In some examples, the message component <NUM> is configured to transmit, to the first LAN client based on receiving the indication of the released slice, a message indicating a release of one or more resources associated with the released slice.

In some examples, the request processing component <NUM> is configured to receive, from the first LAN client, a second request to delete a second network slice, where the second request is based on the multicast message. In some examples, the request processing component <NUM> is configured to receive, from the first LAN client, a second request to initialize an application using a first wireless area network. In some examples, the request processing component <NUM> is configured to receive, from the first LAN client, a request to initialize an application at the first LAN client using a first wireless area network, where receiving the identifier is based on receiving the request.

In some examples, the request processing component <NUM> is configured to receive, from the first LAN client, a request associated with the available network slice. In some examples, receiving the identifier associated with the available network slice is based on receiving the request. In some examples, the request processing component <NUM> is configured to determine, in response to receiving the request, that the request is associated with the available network slice, where establishing the connection associated with the available network slice is based on determining that the request is associated with the available network slice.

In some examples, the request processing component <NUM> is configured to transmit, to a network device based on receiving the identifier, a request to access the available network slice. In some examples, the request processing component <NUM> is configured to receive, from the first LAN client, a request to initialize an application using a first wireless area network.

In some examples, the request processing component <NUM> is configured to transmit, to a network device, the request to initialize the application of the first LAN client using the first wireless area network. In some examples, the connection establishment component <NUM> is configured to establish, at the device based on a successful validation of the identifier, a connection associated with the available network slice.

In some examples, the connection establishment component <NUM> is configured to establish, at the device based on receiving the confirmation to access the new network slice, a second connection associated with the new network slice. In some examples, the confirmation component <NUM> is configured to transmit, to the first LAN client based on establishing the connection, a confirmation to access the available network slice.

In some examples, the confirmation component <NUM> is configured to transmit, to the first LAN client based on establishing the second connection, the confirmation to access the new network slice. In some examples, the confirmation component <NUM> is configured to transmit, to the first LAN client, a confirmation to terminate the new communication session associated with the available network slice.

In some examples, the confirmation component <NUM> is configured to receive, from the network device, a confirmation to access the available network slice, where establishing the connection associated with the available network slice is based on receiving the confirmation from the network device, and where the confirmation transmitted to the first LAN client is based on the confirmation received from the network device. In some examples, the confirmation component <NUM> is configured to transmit, to the first LAN client, a confirmation to terminate the new communication session associated with the available network slice.

The identifier component <NUM> is configured to receive, from a first LAN client of the one or more LAN clients based on the multicast message, an identifier associated with the available network slice. In some examples, the identifier component <NUM> may determine, in response to receiving the request, whether the identifier associated with the available network slice matches a second identifier, where establishing the connection associated with the available network slice is based on determining that the identifier associated with the available network slice matches the second identifier.

In some examples, receiving, from the first LAN client, an indication of a released slice based on transmitting the confirmation to terminate the new communication session, where the released slice includes the available network slice. In some examples, receiving, from the first LAN client, an indication of a released slice based on transmitting the confirmation to terminate the new communication session, where the released slice includes the available network slice.

In some examples, the QOS component <NUM> is configured to determine a QOS parameter associated with the available network slice based on initiating the new communication session. In some examples, the QOS component <NUM> is configured to update the QOS parameter associated with the available network slice based on receiving the indication of the released slice.

In some examples, the QOS component <NUM> is configured to determine whether the one or more data packets satisfy a QOS threshold, where establishing the connection associated with the available network slice is based on determining that the one or more data packets satisfy the QOS threshold. In some examples, the QOS component <NUM> is configured to determine a QOS parameter associated with the available network slice based on initiating the new communication session. In some examples, the QOS component <NUM> is configured to update the QOS parameter associated with the available network slice based on receiving the indication of the released slice.

The information component <NUM> is configured to receive, from the network device, information associated with a set of network slices based on transmitting the second request. In some implementations, the information includes one or more of network slice selection assistance information, configured slice selection assistance information, or allowed slice selection assistance information. The communication session component <NUM> is configured to initiate, in response to transmitting the confirmation to access the available network slice, a new communication session with an application provider. In some examples, the communication session component <NUM> is configured to receive, from the first LAN client, an indication of a termination of the new communication session associated with the available network slice.

In some examples, the communication session component <NUM> is configured to initiate, in response to transmitting the confirmation to access the available network slice, a new communication session with an application provider. In some examples, the communication session component <NUM> is configured to receive, from the first LAN client, an indication of a termination of the new communication session associated with the available network slice.

<FIG> shows a block diagram of an example wireless communication system that supports techniques for LAN clients participation in a network slice according to some implementations. A wireless communication device <NUM> may be configured to perform one or more of the processes <NUM>, <NUM>, and <NUM> described above with reference to <FIG>, <FIG>, and <FIG>, respectively. In some implementations, the wireless communication device <NUM> can be an example implementation of wireless communication device <NUM> described herein with reference to <FIG> or a wireless communication device described herein with reference to <FIG> or a wireless communication device described herein with reference to <FIG>. For example, the wireless communication device <NUM> can be a chip, SoC, chipset, package or device that includes at least one processor, a Wi-Fi (IEEE <NUM>) modem, and a cellular modem.

In some implementations, the wireless communication device <NUM> can be a CPE or a device for use in a CPE (as such, the wireless communication device <NUM> may hereinafter be referred to as CPE). In some implementations, the CPE can be, or can include, an AP (such as AP <NUM>) for serving one or more WLANs such as using a Wi-Fi network or a <NUM> network.

The wireless communication device <NUM> includes a communications manager <NUM>, network communications manager <NUM>, a transceiver <NUM>, one or more antennas <NUM>, memory <NUM>, a processor <NUM>, and an inter-station communications manager <NUM>. Portions of one or more of the modules <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may be implemented at least in part in hardware or firmware. For example, the communications manager <NUM> at least in part by a modem. In some implementations, at least some of the modules <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are implemented at least in part as software stored in a memory. For example, portions of one or more of the modules <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> can be implemented as non-transitory instructions (or "code") executable by a processor to perform the functions or operations of the respective module.

The communications manager <NUM> is configured to transmit, to one or more LAN clients (such as UEs or STAs) of the device, a multicast message indicating an available network slice and receive, from a first LAN client of the one or more LAN clients based on the multicast message, a request to access the available network slice. The communications manager <NUM> is configured to establish, at the device based on receiving the request, a connection associated with the available network slice, and transmit, to the first LAN client based on establishing the connection, a confirmation to access the available network slice. The communications manager <NUM> is further configured to transmit, to one or more LAN clients of the device, a multicast message indicating an available network slice.

The communications manager <NUM> is configured to receive, from a first LAN client of the one or more LAN clients based on the multicast message, an identifier associated with the available network slice, and establish, at the device based on a successful validation of the identifier, a connection associated with the available network slice The communications manager <NUM> is configured to transmit, to the first LAN client based on establishing the connection, a confirmation to access the available network slice.

The network communications manager <NUM> is configured to manage communications with the core network (for example, via one or more wired backhaul links). For example, the network communications manager <NUM> is configured to manage the transfer of data communications for client devices, such as one or more UEs <NUM>.

The transceiver <NUM> is configured to communicate bi-directionally, via one or more antennas, wired, or wireless links as described above. For example, the transceiver <NUM> is configured to represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.

In some implementations, the wireless device may include a single antenna <NUM>. However, in some implementations, the device may have more than one antenna <NUM>, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.

The memory <NUM> may include RAM and ROM. In some implementations, the memory <NUM> may contain, among other things, a basic input/output system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor <NUM> may include an intelligent hardware device, (for example, general-purpose processor, a digital signal processor (DSP), a CPU, a microcontroller, an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor <NUM> may be configured to operate a memory array using a memory controller. In other implementations, a memory controller may be integrated into processor <NUM>. The processor <NUM> may be configured to execute computer-readable instructions stored in a memory to perform various functions (for example, functions or tasks supporting participation of LAN clients in a network slice).

The inter-station communications manager <NUM> is configured to manage communications with other wireless communication devices (for example, the APs <NUM> or the STAs <NUM>), and may include a controller or scheduler for controlling communications. For example, the inter-station communications manager <NUM> may coordinate scheduling for transmissions for various interference mitigation techniques such as beamforming or joint transmission.

<FIG> shows a flowchart illustrating an example process <NUM> for LAN clients to participate in a network slice according to some implementations. The process <NUM> may be implemented by a wireless communication device (such as a CPE, or an AP) such as the wireless communication device described above with reference to <FIG>. In some implementations, the process <NUM> begins in block <NUM> with transmitting a multicast message. In block <NUM>, the process <NUM> proceeds with receiving a request to access the available network slice. In block <NUM>, the process <NUM> proceeds with establishing a connection associated with the available network slice. In block <NUM>, the process <NUM> further proceeds with transmitting a confirmation to access the available network slice.

In some implementations, transmitting the multicast message in block <NUM> includes transmitting, to one or more LAN clients (such as UEs) of the device, the multicast message indicating an available network slice. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a message component as described with reference to <FIG>.

In some implementations, receiving the request to access the available network slice in block <NUM> includes receiving the request from a first LAN client of the one or more LAN clients. In some examples, the request may be based on the transmitted multicast message. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a request processing component as described with reference to <FIG>.

In some implementations, establishing the connection associated with the available network slice in block <NUM> includes establishing, at the device, the connection associated with the available network slice. In some examples, the device may include the wireless communication device. In some examples, the wireless communication device may establish the connection based on receiving the request. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a connection establishment component as described with reference to <FIG>.

In some implementations, transmitting the confirmation to access the available network slice in block <NUM> includes transmitting the confirmation to the first LAN client. In some implementations, transmitting the confirmation to access the available network slice in block <NUM> includes transmitting the confirmation based on establishing the connection. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a confirmation component as described with reference to <FIG>.

<FIG> shows a flowchart illustrating an example process <NUM> for LAN clients to participate in a network slice according to some implementations. The process <NUM> may be implemented by a wireless communication device (such as a CPE, or an AP) such as the wireless communication device described above with reference to <FIG>. In some implementations, the process <NUM> begins in block <NUM> with transmitting a multicast message. In block <NUM>, the process <NUM> proceeds with receiving a request to access the available network slice. In block <NUM>, the process <NUM> proceeds with determining one or more data packets. In block <NUM>, the process <NUM> further proceeds with determining whether the one or more data packets satisfy a QOS threshold. In block <NUM>, the process <NUM> further proceeds with establishing a connection. In block <NUM>, the process <NUM> further proceeds with transmitting a confirmation to access the available network slice.

In some implementations, receiving the request to access the available network slice in block <NUM> includes receiving, from a first LAN client of the one or more LAN clients based on the multicast message, a request to access the available network slice. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a request processing component as described with reference to <FIG>.

In some implementations, determining one or more data packets slice in block <NUM> includes determining one or more data packets associated with the available network slice. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a network slice component as described with reference to <FIG>.

In some implementations, determining whether the one or more data packets satisfy the QOS threshold in block <NUM> includes determining whether the one or more data packets satisfy a QOS threshold. In some implementations, establishing the connection associated with the available network slice is based on determining that the one or more data packets satisfy the QOS threshold. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a QOS component as described with reference to <FIG>.

In some implementations, establishing a connection in block <NUM> includes establishing at the device based on receiving the request, a connection associated with the available network slice. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a connection establishment component as described with reference to <FIG>.

In some implementations, transmitting the confirmation to access the available network slice in block <NUM> includes transmitting, to the first LAN client based on establishing the connection, the confirmation to access the available network slice. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a confirmation component as described with reference to <FIG>.

<FIG> shows a flowchart illustrating an example process <NUM> for LAN clients to participate in a network slice according to some implementations. The process <NUM> may be implemented by a wireless communication device (such as a CPE, or an AP) such as the wireless communication device described above with reference to <FIG>. In some implementations, the process <NUM> begins in block <NUM> with transmitting a multicast message. In block <NUM>, the process <NUM> proceeds with receiving an identifier. In block <NUM>, the process <NUM> further proceeds with establishing a connection. In block <NUM>, the process <NUM> further proceeds with transmitting a confirmation to access the available network slice.

In some implementations, receiving the identifier in block <NUM> includes receiving, from a first LAN client of the one or more LAN clients based on the multicast message, the identifier associated with the available network slice. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by an identifier component as described with reference to <FIG>.

In some implementations, establishing a connection in block <NUM> includes establishing, at the device based on a successful validation of the identifier, a connection associated with the available network slice. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a connection establishment component as described with reference to <FIG>.

As used herein, "or" is used intended to be interpreted in the inclusive sense, unless otherwise explicitly indicated. For example, "a or b" may include a only, b only, or a combination of a and b. As used herein, a phrase referring to "at least one of" or "one or more of" a list of items refers to any combination of those items, including single members. For example, "at least one of: a, b, or c" is intended to cover the possibilities of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.

Various modifications to the implementations described in this disclosure may be readily apparent to persons having ordinary skill in the art, and the generic principles defined herein may be applied to other implementations without departing from the scope of this disclosure. Thus, the claims are not intended to be limited to the implementations shown herein, but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.

Additionally, various features that are described in this specification in the context of separate implementations also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple implementations separately or in any suitable subcombination. As such, although features may be described above as acting in particular combinations, and even initially claimed as such, one or more features from a claimed combination can in some examples be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Claim 1:
A method (<NUM>) for wireless communication at a wireless communication device, the method (<NUM>) comprising:
transmitting (<NUM>), to one or more local area network clients of the wireless communication device, a multicast message indicating an available network slice;
receiving (<NUM>), from a first local area network client of the one or more local area network clients based at least in part on the multicast message, a request to access the available network slice;
determining (<NUM>) one or more data packets associated with the available network slice;
determining (<NUM>) whether the one or more data packets satisfy a quality of service threshold;
establishing (<NUM>), at the device based at least in part on receiving the request, a connection associated with the available network slice, wherein establishing the connection associated with the available network slice is based at least in part on determining that the one or more data packets satisfy the quality of service threshold; and
transmitting (<NUM>), to the first local area network client based at least in part on establishing the connection, a confirmation to access the available network slice.