LAN clients participating in network slicing

Abstract

The present disclosure provides methods, devices and systems for performing the following: sending a multicast message indicating available network slices to one or more local area network clients of the device; receiving a request for access to the available network slice from a first local area network client among the one or more local area network clients based on the multicast message; establishing a connection associated with the available network slice at the device based on receiving the request; and sending a confirmation of access to the available network slice to the first local area network client based on establishing the connection.

Description

[0001] Priority information

[0002] This patent application claims priority to U.S. patent application No. 16 / 740,608, filed on January 13, 2020, entitled “LOCAL AREA NETWORK CLIENT PARTICIPATION IN A NETWORK SLICE,” which is assigned to the assignee thereof and is hereby expressly incorporated by reference. Technical Field

[0003] The following relates generally to wireless communications, and more specifically to local area network (LAN) client participation in network slicing. Background Art

[0004] A wireless local area network (WLAN) can be formed by one or more access points (APs) that provide a shared wireless communication medium for use by a certain number of client devices, also known 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 the like. These systems can be multiple-access systems that can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth-generation (4G) systems, such as long-term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems, which can be referred to as new radio (NR) systems. The AP periodically broadcasts beacon frames so that any STA within the wireless range of the AP can establish or maintain a communication link with the WLAN. Wireless devices can communicate bidirectionally with network devices. For example, in a WLAN, a STA can communicate with an associated AP via downlink and uplink communications. Downlink (or forward link) communication may refer to the communication link from the AP to the station, while uplink (or reverse link) communication may refer to the communication link from the station to the AP. A system (such as a 5G system) may support multiple network slices serving multiple wireless devices. A network slice may be an isolated end-to-end network that supports different features for different applications of wireless devices. However, STAs operating in a WLAN supported by an AP accessing an NR system lack the ability to request or use network slices. Summary of the Invention

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

[0006] One innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication method. The method includes: sending a multicast message indicating an available network slice to one or more local area network (LAN) clients of the device; receiving a request to access the available network slice from a first LAN client among the one or more LAN clients based on the multicast message; establishing a connection associated with the available network slice at the device based on receiving the request; and sending a confirmation of access to the available network slice to the first LAN client based on establishing the connection.

[0007] Another innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication device. The wireless communication device includes: at least one modem; at least one processor; at least one memory, the at least one memory being communicatively coupled to the at least one processor and storing processor-readable code, the processor-readable code being configured, when executed by the at least one processor in conjunction with the at least one modem, to: send a multicast message indicating available network slices to one or more LAN clients of the device; receive a request from a first LAN client among the one or more LAN clients to access the available network slice based on the multicast message; establish a connection associated with the available network slice at the device based on the received request; and send a confirmation of access to the available network slice to the first LAN client based on the establishment of the connection.

[0008] In some embodiments, the method and wireless communication device may be configured to determine one or more data packets associated with an available network slice and determine whether the one or more data packets satisfy a quality of service (QOS) threshold. In some embodiments, establishing a connection associated with the available network slice may be based on determining that the one or more data packets satisfy the QOS threshold.

[0009] In some embodiments, the method and wireless communication device may be configured to send a second request to the network device to access the available network slice based on receiving the request, and receive a confirmation of access to the available network slice from the network device. In some embodiments, establishing a connection associated with the available network slice may be based on receiving the confirmation from the network device. In some embodiments, the confirmation sent to the first LAN client may be based on the confirmation received from the network device.

[0010] In some embodiments, the method and wireless communication device may be configured to receive a second request from the first LAN client to create a new network slice, determine an approval status associated with the new network slice, and send a third request to the network device to access the new network slice based on the determination of the approval status. In some embodiments, the second request may be based on a multicast message.

[0011] In some embodiments, the method and wireless communication device can be configured to receive confirmation of access to the new network slice from the network device based on sending the third request.

[0012] In some embodiments, the method and wireless communication device can be configured to establish a second connection associated with the new network slice at the device based on receiving a confirmation of accessing the new network slice, and send a confirmation of accessing the new network slice to the first LAN client based on establishing the second connection.

[0013] In some embodiments, the method and wireless communication device may be configured to receive a second request from the first LAN client to delete the second network slice. In some embodiments, the second request may be based on a multicast message, and the second network slice is deleted based on receiving the second request.

[0014] In some embodiments, the method and the wireless communication device may be configured to receive a second request to initialize an application from a first LAN client using a first wireless local area network, send a second request to initialize the application of the first LAN client to a network device using the first wireless local area network, and receive information associated with a set of network slices from the network device based on sending the second request.

[0015] In some embodiments, the method and wireless communication device can be configured to send multicast messages based on determining available network slices.

[0016] In some embodiments, the information includes one or more of network slice selection assistance information, configuration slice selection assistance information, or permission slice selection assistance information.

[0017] In some embodiments, the method and wireless communication device can be configured to initiate a new communication session with the application provider in response to sending a confirmation of access to an available network slice, and determine the QOS parameters associated with the available network slice based on initiating the new communication session.

[0018] In some embodiments, the method and wireless communication device may be configured to receive an indication to release a slice from the first LAN client based on sending a confirmation to terminate the new communication session. In some embodiments, the released slice includes an available network slice. In some embodiments, the method and wireless communication device may be configured to send a message to the first LAN client indicating the release of one or more resources associated with the released slice based on receiving the indication to release the slice.

[0019] In some embodiments, the method and wireless communication device may be configured to update the QOS parameters associated with the available network slices based on receiving an indication of releasing the slice. In some embodiments, the multicast message includes one or more of a broadcast message or a universal plug and play message.

[0020] One innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication method. The method includes: sending a multicast message indicating an available network slice to one or more LAN clients of a device; receiving an identifier associated with the available network slice from a first LAN client of the one or more LAN clients based on the multicast message; establishing a connection associated with the available network slice at the device based on successful verification of the identifier; and sending a confirmation of access to the available network slice to the first LAN client based on establishing the connection.

[0021] Another innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication device. The wireless communication device includes: at least one modem; at least one processor; at least one memory, the at least one memory being communicatively coupled to the at least one processor and storing processor-readable code, the processor-readable code being configured, when executed by the at least one processor in conjunction with the at least one modem, to: send a multicast message indicating available network slices to one or more LAN clients of the device; receive an identifier associated with the available network slice from a first LAN client among the one or more LAN clients based on the multicast message; establish a connection associated with the available network slice at the device based on successful verification of the identifier; and send a confirmation of access to the available network slice to the first LAN client based on establishing the connection.

[0022] In some embodiments, the method and wireless communication device may be configured to receive a request from a first LAN client using a first wireless local area network to initialize an application at the first LAN client. In some embodiments, receiving the identifier may be based on receiving the request. In some embodiments, the method and wireless communication device may be configured to determine whether an identifier associated with an available network slice matches a second identifier in response to receiving the request. In some embodiments, establishing a connection associated with the available network slice may be based on determining that the identifier associated with the available network slice matches the second identifier.

[0023] In some embodiments, the method and wireless communication device may be configured to receive a request associated with an available network slice from a first LAN client, wherein receiving an identifier associated with the available network slice may be based on receiving the request. In some embodiments, the method and wireless communication device may be configured to determine, in response to receiving the request, that the request may be associated with an available network slice. In some embodiments, establishing a connection associated with the available network slice may be based on determining that the request may be associated with an available network slice.

[0024] In some embodiments, the method and wireless communication device may be configured to determine one or more data packets associated with an available network slice and determine whether the one or more data packets satisfy a QOS threshold. In some embodiments, establishing a connection associated with the available network slice may be based on determining that the one or more data packets satisfy the QOS threshold.

[0025] In some embodiments, the method and wireless communication device may be configured to send a request to the network device to access the available network slice based on receiving the identifier, and receive a confirmation of access to the available network slice from the network device. In some embodiments, establishing a connection associated with the available network slice may be based on receiving the confirmation from the network device. In some embodiments, the confirmation sent to the first LAN client may be based on the confirmation received from the network device.

[0026] In some embodiments, the method and wireless communication device can be configured to receive a request to initialize an application from a first LAN client using a first wireless local area network, send a request to initialize the application of the first LAN client to a network device using the first wireless local area network, and receive information associated with a set of network slices from the network device based on sending the request.

[0027] In some embodiments, the method and wireless communication device can be configured to send a multicast message based on determining available network slices.

[0028] In some embodiments, the method and wireless communication device can be configured to initiate a new communication session with the application provider in response to sending a confirmation of access to an available network slice, and determine the QOS parameters associated with the available network slice based on initiating the new communication session.

[0029] In some embodiments, the method and wireless communication device can be configured to receive an indication of termination of a new communication session associated with the available network slice from a first LAN client and send a confirmation of termination of the new communication session associated with the available network slice to the first LAN client.

[0030] In some embodiments, the method and wireless communication device may be configured to receive an indication to release a slice from the first LAN client based on sending a confirmation to terminate the new communication session, and based on receiving the indication to release the slice, send a message to the first LAN client indicating the release of one or more resources associated with the released slice. In some embodiments, the released slice includes an available network slice.

[0031] In some embodiments, the method and wireless communication device may be configured to update QOS parameters associated with available network slices based on receiving an indication to release a slice. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Details of one or more embodiments of the subject matter described in this disclosure are set forth in the accompanying drawings and the following description. However, the accompanying drawings illustrate only some typical aspects of the disclosure and should not be considered to limit its scope. Other features, aspects, and advantages will become apparent from the description, drawings, and claims.

[0033] Figure 1 A schematic diagram of an exemplary wireless communication network is shown.

[0034] Figure 2 A schematic diagram of an exemplary wireless communication network is shown.

[0035] Figure 3 An example of a wireless communication system architecture is shown in accordance with some embodiments.

[0036] Figure 4 A block diagram of an exemplary wireless communication device supporting technology for LAN clients to participate in network slicing according to some embodiments is shown.

[0037] Figure 5 An exemplary timing diagram illustrating an exemplary process for a local area network (LAN) client to participate in network slicing according to some embodiments is shown.

[0038] Figure 6 An exemplary timing diagram illustrating an exemplary process for a LAN client to participate in network slicing according to some embodiments is shown.

[0039] Figure 7 An exemplary process for LAN clients to participate in network slicing according to some embodiments is shown.

[0040] Figure 8 A block diagram of an exemplary wireless communication device supporting technology for LAN clients to participate in network slicing according to some embodiments is shown.

[0041] Figure 9A block diagram of an exemplary wireless communication device supporting technology for LAN clients to participate in network slicing according to some embodiments is shown.

[0042] Figure 10 A block diagram of an exemplary communications manager supporting technology for LAN clients to participate in network slicing according to some embodiments is shown.

[0043] Figure 11 A block diagram of an exemplary wireless communication system supporting technology for LAN clients to participate in network slicing according to some embodiments is shown.

[0044] Figure 12 A flowchart illustrating an exemplary process for a LAN client to participate in network slicing according to some embodiments is shown.

[0045] Figure 13 A flowchart illustrating an exemplary process for a LAN client to participate in network slicing according to some embodiments is shown.

[0046] Figure 14 A flowchart illustrating an exemplary process for a LAN client to participate in network slicing according to some embodiments is shown. DETAILED DESCRIPTION

[0047] For the purpose of describing the innovative aspects of the present disclosure, the following description is directed to certain embodiments. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in a variety of different ways. The described embodiments may be implemented in a manner that is capable of being implemented in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, the Bluetooth Special Interest Group (SIG) standard, or any other standard defined by the Bluetooth Special Interest Group (SIG). The present invention relates to any device, system, or network that transmits and receives radio frequency (RF) signals in accordance with one or more of the Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)) standards promulgated by the 3rd Generation Partnership Project (3GPP). The described embodiments may be implemented in any device, system, or network capable of transmitting and receiving RF signals in accordance with one or more of the following technologies: 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 embodiments may also 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.

[0048] Various embodiments generally relate to techniques for local area network (LAN) clients to participate in network slicing. In some embodiments, customer premises equipment (CPE) with access to one or more systems, such as a fifth generation (5G) wireless communication system, may process network slice requests from one or more LAN clients. In some examples, such CPE may be referred to as 5G-CPE. In some embodiments, the 5G-CPE may enable LAN clients that are unaware of available network slices to request and access network slices. Additionally or alternatively, the 5G-CPE may enable LAN clients that are aware of available network slices to request and access network slices. In some examples where the LAN client and its application are unaware of the available network slices, the 5G-CPE may determine the available network slices (e.g., using techniques such as network slice selection assistance information, configured slice selection assistance information, or enabled slice selection assistance information) and may broadcast indications of the available network slices to the LAN client. In some embodiments, the LAN client may initiate an application session, and the 5G-CPE may verify user credentials associated with the initiation of the application session. In some embodiments, the 5G-CPE may initiate network slice setup on behalf of the LAN client after successfully verifying the user credentials.

[0049] In some examples where the LAN client and its applications are aware of the available network slices, the 5G-CPE may also determine the available network slices and may also broadcast the available network slices to the LAN client. In some embodiments, upon receiving this message, the LAN client may request to create a network slice. In some embodiments, the LAN client may request to access an available network slice. In response to receiving such a request from the LAN client, the 5G-CPE may request to set up a new network slice. In some embodiments, the 5G-CPE may establish a connection (such as a packet data network) as part of the successful network slice setup. In some embodiments, the 5G-CPE may route traffic related to creating or accessing a network slice over the established connection (e.g., over a packet data network).

[0050] Specific embodiments of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. In some embodiments, the described techniques may be used to enable a LAN client supported by a 5G-enabled CPE to request or use one or more network slices. According to one or more embodiments, a 5G wireless communication system may support network slicing. Network slicing may provide for the creation of multiple virtual logical networks (which may be examples of network slices) on a physical infrastructure shared by multiple entities (such as multiple application providers or multiple operators). In some examples, one or more network slices may support different features, or network function optimization, or both. In some embodiments, the techniques and other aspects described in this disclosure may enable one or more LAN clients to support ultra-low latency when communicating over a Wi-Fi interface.

[0051] Various aspects of the present disclosure are first described in the context of a wireless communication system. Additional aspects are described with respect to a wireless communication system architecture and timing diagrams. Various aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow charts related to LAN client participation in network slicing.

[0052] Figure 1 A block diagram of an exemplary wireless communication network 100 is shown. According to some aspects, the wireless communication network 100 may be an example of a wireless local area network (WLAN), such as a Wi-Fi network (and will be referred to as WLAN 100 hereinafter). For example, the WLAN 100 may be a network that implements at least one of the IEEE 802.11 family of wireless communication protocol standards, such as those defined by the IEEE 802.11-2016 specification or its amendments, including but not limited to 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be. The WLAN 100 may include a number of wireless communication devices, such as an access point (AP) 102 and multiple stations (STAs) 104. Although only one AP 102 is shown, the WLAN network 100 may also include multiple APs 102.

[0053] Each of the STAs 104 may also 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, etc. The STAs 104 may represent various devices, such as mobile phones, personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptop computers, display devices (e.g., TVs, computer monitors, navigation systems, etc.), music or other audio or stereo equipment, remote control devices (“remote controls”), printers, kitchen or other home appliances, key fobs (e.g., for passive keyless entry and start (PKES) systems), etc.

[0054] A CPE capable of accessing a 5G wireless communication system may include an AP 102. A single AP 102 and an associated group of STAs 104 may be referred to as a basic service set (BSS), which is managed by the corresponding AP 102. Figure 1 Also shown is an exemplary coverage area 106 of the AP 102, which may represent a basic service area (BSA) of the WLAN 100. A BSS may be identified to users by a service set identifier (SSID), and to other devices by a basic service set identifier (BSSID), which may be the medium access control (MAC) address of the AP 102. The AP 102 periodically broadcasts beacon frames ("beacons") including the BSSID to enable any STA 104 within wireless range of the AP 102 to "associate" or re-associate with the AP 102 to establish or maintain a corresponding communication link 108 (hereinafter also referred to as a "Wi-Fi link") with the AP 102. For example, the beacon may include an identification of a primary channel used by the corresponding AP 102 and a timing synchronization function for establishing or maintaining timing synchronization with the AP 102. The AP 102 may provide access to external networks to the respective STAs 104 in the WLAN via the corresponding communication links 108.

[0055] To establish a communication link 108 with an AP 102, each of the STAs 104 is configured to perform passive or active scanning operations ("scans") on frequency channels in one or more frequency bands (e.g., the 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz bands). To perform a passive scan, the STAs 104 listen for beacons transmitted by the corresponding AP 102 at periodic time intervals (measured in time units (TUs), where one TU may be equal to 1024 microseconds (μs)) called target beacon transmit times (TBTTs). To perform an active scan, the STAs 104 generate and sequentially transmit probe requests on each channel to be scanned and listen for probe responses from the APs 102. Each STA 104 may be configured to identify or select an AP 102 with which to associate based on the scan information obtained through the passive or active scan and perform authentication and association operations to establish a communication link 108 with the selected AP 102. The AP 102 assigns an association identifier (AID) to the STA 104 at the end of the association operation, and the AP 102 uses the association identifier to track the STA 104.

[0056] As wireless networks become increasingly popular, a STA 104 may have the opportunity to select one of multiple BSSs within its range or to choose from multiple APs 102, which together form an extended service set (ESS) comprising multiple connected BSSs. Extended network stations associated with a WLAN 100 may be connected to a wired or wireless distribution system that allows multiple APs 102 to be connected in such an ESS. In this way, a STA 104 may be covered by more than one AP 102 and may associate with different APs 102 at different times for different transmissions. In addition, after associating with an AP 102, the STA 104 may also be configured to periodically scan its surroundings to find a more suitable AP 102 with which to associate. For example, a STA 104 (which is moving relative to its associated AP 102) may perform a "roaming" scan to find another AP 102 with more desirable network characteristics, such as a greater received signal strength indicator (RSSI) or reduced traffic load.

[0057] In some examples, STA 104 can form a network without AP 102 or other devices other than STA 104 itself. Some examples of such networks are ad hoc networks (or wireless ad hoc networks). Ad hoc networks can alternatively be referred to as mesh networks or peer-to-peer (P2P) networks. In some examples, ad hoc networks can be implemented in larger wireless networks such as WLAN 100. In such embodiments, although STA 104 may be able to communicate with each other through AP 102 using communication link 108, STA 104 can also communicate directly with each other via direct wireless link 110. In addition, two STAs 104 can communicate via direct communication link 110, regardless of whether the two STAs 104 are associated with and served by the same AP 102. In such an ad hoc system, one or more of STA 104 can assume the role played by AP 102 in the BSS. Such STA 104 can be called a group owner (GO) and can coordinate transmissions within the ad hoc network. Examples of the direct wireless link 110 include a Wi-Fi Direct connection, a connection established by using a Wi-Fi Tunnel Direct Link Setup (TDLS) link, and other P2P group connections.

[0058] The AP 102 and the STA 104 may operate and communicate (via corresponding communication links 108) in accordance with the IEEE 802.11 family of wireless communication protocol standards, such as those defined by the IEEE 802.11-2016 specification or its amendments, including but not limited to 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be. These standards define WLAN radio and baseband protocols for the PHY and medium access control (MAC) layers. The AP 102 and the STA 104 transmit and receive wireless communications (hereinafter also referred to as "Wi-Fi communications") with each other in the form of PHY protocol data units (PPDUs) (or physical layer convergence protocol (PLCP) PDUs). The AP 102 and the STA 104 in the WLAN 100 may transmit the PPDUs over an unlicensed spectrum, which may be a portion of the spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the 2.4 GHz band, the 5 GHz band, the 60 GHz band, the 3.6 GHz band, and the 900 MHz band. Some embodiments of the AP 102 and STA 104 described herein may also communicate in other frequency bands that may support both licensed and unlicensed communications, such as the 6 GHz band. The AP 102 and STA 104 may also be configured to communicate over other frequency bands, such as shared licensed frequency bands, where multiple operators may have licenses to operate in one or more of the same or overlapping frequency bands.

[0059] Each frequency band may include multiple sub-bands or frequency channels. For example, PPDUs compliant with IEEE 802.11n, 802.11ac, 802.11ax, and 802.11be standard revisions may be sent in the 2.4, 5, or 6 GHz bands, each of which is divided into multiple 20 MHz channels. Thus, these PPDUs are sent on physical channels with a minimum bandwidth of 20 MHz, but larger channels can be formed through channel bonding. For example, by bonding multiple 20 MHz channels together, a PPDU can be sent on a physical channel with a bandwidth of 40 MHz, 80 MHz, 160 MHz, or 320 MHz.

[0060] 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 receiving device can use the information provided in the preamble to decode subsequent data in the PSDU. In an instance where a PPDU is sent over a bonded channel, the preamble field can be copied and sent in each of the multiple component channels. The PHY preamble may include a legacy portion (or "legacy preamble") and a non-legacy portion (or "non-legacy preamble"). Traditional preambles can be used for purposes such as packet detection, automatic gain control, and channel estimation. Traditional preambles can also typically be used to maintain compatibility with legacy devices. The format, decoding, and information provided in the non-legacy portion of the preamble are based on the specific IEEE 802.11 protocol used to send the payload.

[0061] As described above, the AP 102 and the STAs 104 may support multi-user (MU) communications; that is, concurrent transmissions from one device to each of multiple devices (e.g., multiple simultaneous downlink (DL) communications from the AP 102 to the corresponding STAs 104) or concurrent transmissions from multiple devices to a single device (e.g., multiple simultaneous uplink (UL) transmissions from the corresponding STAs 104 to the AP 102). To support MU transmissions, the AP 102 and the STAs 104 may utilize multi-user multiple-input multiple-output (MU-MIMO) and multi-user orthogonal frequency division multiple access (MU-OFDMA) technologies.

[0062] In some embodiments, the AP 102 and STA 104 may support the use of network slicing as described herein. For example, a 5G wireless communication system (such as the wireless communication network 100) may support the creation of multiple network slices (which may be examples of virtual logical networks) on a physical infrastructure shared by multiple application providers. In some examples, the network slices may be isolated end-to-end networks that support different features for different applications. As described in reference Figure 1In some examples, AP 102 may be included in a 5G-enabled CPE (or 5G-CPE), and the STA may be referred to as a LAN client. In some examples, one or more aspects of the present disclosure enable a CPE or other wireless communication device to process a network slice request from a LAN client (e.g., STA 104). In some examples, the LAN client of AP 102 (such as an AP included in a 5G-CPE) and its applications may not be aware of the available network slices. In such examples, AP 102 may handle the initiation of network slicing, while the LAN client is unaware of the slice initiation. In some other examples, the LAN client and its applications may be aware of the available network slices. In such examples, the LAN client may request network slicing initiation through a CPE (such as a 5G-CPE including AP 102) after receiving a message about slice availability from AP 102.

[0063] Figure 2 Schematic diagram of an exemplary wireless communication network 200 is shown. The wireless communication network 200 may be an example of the wireless communication network 100 and may include a 5G-CPE 202 (such as a 5G-CPE including an AP) and UEs 204-a, 204-b, and 204-c (which may also be examples of STAs), which may be reference Figure 1 Examples of corresponding devices described. 5G-CPE 202 can provide network coverage for a coverage area. 5G-CPE 202 and UEs 204-a, 204-b, and 204-c can communicate through one or more communication links. For example, 5G-CPE 202 and UE 204-a can communicate through a wired communication link 206 (such as Ethernet), 5G-CPE 202 and UE 204-b can communicate through a wireless communication link 208 (such as Wi-Fi), and 5G-CPE 202 and UE 204-c can communicate through a wireless communication link 210 (such as a Wi-Fi communication link or a 5G communication link). UEs 204-a, 204-b, and 204-c in conjunction with 5G-CPE 202 can utilize one or more network slices to improve communication efficiency and obtain power advantages of communication and other advantages.

[0064] In some examples, 5G-CPE 202 can communicate with base station 214 using wireless communication link 212. Base station 214 can be a base station that provides or accesses a 5G or NR network. Base station 214 can communicate with radio access network (RAN) 218 ​​using wired or wireless communication link 216. Figure 2As shown, RAN 218 can communicate with user plane function (UPF) 222 using communication link 220. UPF 222 can communicate with data network 226 using communication link 224. In some embodiments, data network 226 can be configured to access multiple content providers (or application providers). Data network 226 can communicate with a first content provider (Content Provider 1) using communication link 236. Additionally or alternatively, data network 226 can communicate with a second content provider (Content Provider 2) using communication link 228 and can communicate with a third content provider (Content Provider 2) using communication link 232. The wireless communication network 200 is configured to perform the operations described above with reference to the respective Figure 12 、 13 In some embodiments, one or more of the devices in the wireless communication network 200 may be one or more of the processes 1200, 1300, and 1400 described herein. Figure 1 、 3 and 4 are exemplary embodiments of the apparatus described.

[0065] According to some embodiments, wireless communication network 200 may support network slicing. In some examples, a wireless communication network (such as wireless communication network 200) may support 5G technology. The 5G communication network may be configured to provide different services for applications based on network slicing. In some embodiments, network slicing may be described as an end-to-end tunnel between an application hosted on a UE (such as UE 204-a, 204-b, and 204-c) and the application provider. The 5G core network and RAN (such as base station 214 combined with RAN 218) may support network slicing. However, solutions that support network slicing (with the ability for user applications to request or use network slices) are not available to LAN clients (such as UEs or STAs). More specifically, for example, LAN clients supported by 5G-enabled CPE typically lack the ability to request or use network slicing. In addition, due to the inability to access network slices, 5G-CPE (such as a home router that uses 5G WAN / 5G WLAN / 5G networks and Wi-Fi / Ethernet for wireless broadband services) has difficulty supporting ultra-low latency when operating using a Wi-Fi interface.

[0066] In some examples, current network slice types can be classified according to Table 1.

[0067]

[0068]

[0069] Table 1

[0070] As shown in Table 1, each of the network slice types or service types can 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 a user plane latency value of 0.5 ms for uplink communications and a user plane latency value of 0.5 ms for downlink communications. In addition, for the URLLC service type, the latency value can support the use of next-generation access technologies as wireless transmission technologies that can be used in the next-generation access architecture. In some examples, the reliability key performance indicator can provide a latency value with an associated reliability parameter. In some examples, the latency value can be an average value without an associated high reliability parameter. In some examples, for the eMBB service type, the network slice provides a user plane latency value of 4 ms for uplink communications and a user plane latency value of 4 ms for downlink communications. In some examples, the latency value of the eMBB service type can be based on all typical delays associated with the delivery of data packets (e.g., applicable process delays when resources are not pre-allocated, average hybrid automatic repeat request retransmission delays, and network architecture-related delays). In some embodiments, for URLLC service types, the QOS parameters associated with latency may have higher thresholds (0.5 ms for uplink communications and 0.5 ms for downlink communications). To support URLLC service types, conventional wireless communication networks may support higher thresholds for QOS parameters associated with latency between a 5G core network (such as a RAN) and a UE.

[0071] In addition to the network slice type or service type, one or more operators may also define a slice type or service type with characteristics associated with the operator. Specifically, existing wireless communication networks allow customized network slices to be created and served. Additionally or alternatively, existing wireless communication networks that support network slicing may consider end-to-end latency. In some examples, end-to-end latency may include application latency on the UE. In some examples, for URLLC service types, the application latency for different applications may be 3ms to 5ms. In some embodiments, it may be important to consider application latency as part of the overall end-to-end latency (e.g., end-to-end latency between the application and the 5G core network). In the example of live audio performance that may be associated with an application and a 5G core network, there may be a deterministic latency for receiving live audio over the wireless communication network and an application latency associated with processing the live audio in the UE.

[0072] In one or more embodiments, the wireless communication network 200 may enable LAN clients (such as UEs 204-a, 204-b, and 204-c) to use network slicing. Specifically, the wireless communication network 200 may process network slicing requests from one or more of the LAN clients. In some aspects, the wireless communication network 200 may handle access and creation of network slices in two scenarios. In an example of the first scenario, the LAN client (e.g., UE 204-a) and its applications may not be aware of the available network slices. In such an example, the 5G-CPE 202 may handle the initiation of network slicing without one or more of the LAN clients being aware of the slice initiation. In an example of the second scenario, the LAN client (e.g., UE 204-b and 204-c) and its applications may be aware of the available network slices. In such an example, the LAN client may request network slicing initiation through the 5G-CPE 202 after receiving a broadcast or multicast message indicating that the network slice is available.

[0073] As reference Figure 2 As shown, UE 204-a, 204-b, and 204-c can host different applications. For example, the application hosted in UE 204-a can be associated with content provider 238 (content provider 1). Similarly, the application hosted in UE 204-b can be associated with content provider 230 (content provider 2), and the application hosted in UE 204-c can be associated with content provider 234 (content provider 3). According to some embodiments, UE 204-a, 204-b, and 204-c can utilize different network slices to access different client applications. In some examples, the wireless communication network 200 supports signaling between 5G-CPE 202 and LAN clients (e.g., UE 204-a, 204-b, and 204-c) to enable LAN clients to use network slices. With reference to Figure 2 The described framework allows LAN clients to benefit from requesting and accessing network slices from the 5G core network.

[0074] Figure 3 An example of a wireless communication system architecture 300 according to some embodiments is shown. The wireless communication system architecture 300 may include a UE 360, a RAN 365, a UPF 305, a data network 310, an authentication server function (AUSF) 315, an access and mobility management function (AMF) 320, a session management function (SMF) 325, a network slice selection function (NSSF) 330, a PCF 345, a unified data management (UDM) 350, and an application function (AF) 355. In addition, the wireless communication system architecture 300 may include other components not referenced herein. Figure 3Other functions or entities may be shown, or one or more of the shown functions or entities may be excluded.

[0075] As reference Figure 3 As shown, the wireless communication system architecture 300 can support LAN clients (such as one or more UEs 360) to participate in network slicing. Specifically, the wireless communication system architecture 300 supports the use of network slicing to support additional features and network function optimization. For example, a network slice defined within a public land mobile network (PLMN) may include core network control plane and 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 to provide the same features but for different UE groups (for example, because different UE groups may provide different provisioning services, or because different UE groups may be dedicated to customers). A single UE 360 can be served by one or more network slice instances simultaneously. In some examples, the threshold associated with multiple concurrent slices is set to eight slices, which means that a single UE 360 can be served by up to eight network slices at a time. The AMF 320 instance serving the UE 360 can logically belong to each of the network slice instances serving the UE 360 (for example, the AMF 320 instance can be common to the network slice instances serving the UE 360).

[0076] The set of network slice instances is selected for the UE 360, wherein each of the network slice instances corresponding to the network slice selection assistance information may be triggered by the first contact 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 interaction with the NSSF 330 and may result in a change of the AMF 320. The network slice selection assistance information may be used to uniquely identify the network slice. The SMF discovery and selection within the selected network slice instance may be initiated by the AMF 320 in response to receiving a session management message from the UE 360. The session management message may include a message for establishing a PDU session. In some embodiments, different network slice instances may not share a PDU session, but different slices may have slice-specific PDU sessions using the same data network name.

[0077] As described above, network slice selection assistance information can be used to determine the network slice and can include a slice or service type (SST) and a slice distinguisher (SD), among other examples. The SST can refer to the expected network slice behavior in terms of features and services, and the SD can be optional information that supplements the SST to distinguish multiple network slices of the same SST. Selecting the network slice instance serving the UE 360 and the core network control plane and user plane network functions corresponding to the network slice instance may be the responsibility of the 5G core network. Before the 5GC notifies the RAN 365 of the allowed network slice selection assistance information, the RAN 365 may use the network slice selection assistance information requested in the access layer signaling to handle the UE control plane connection. When the UE 360 successfully registers, the 5G core network may notify the RAN 105 by providing the allowed network slice selection assistance information for the control plane aspect. When a PDU session is established using a specific network slice instance, the 5G core network may provide the network slice selection assistance information corresponding to the network slice instance to the RAN 365 to enable the RAN 365 to perform access-specific functions.

[0078] In some embodiments, establishing user plane connectivity to the data network via the network slice instance may include selecting an AMF 320 that supports network slicing and establishing one or more PDU sessions to the data network 310 via the network slice instance. When the AMF 320 is selected, the AMF 320 may query the UDM 350 to retrieve UE subscription information, including subscribed network slice selection assistance information.

[0079] In some examples, the AMF 320 may be allowed to determine whether it can serve the UE 360 based on a configuration associated with the UE 360. For example, the AMF 320 may be allowed to determine that it can serve the UE 360 based on satisfying at least one parameter associated with the configuration. Additionally, the AMF 320 may query the NSSF 330 for 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 360. Based on such information, local configuration, and other locally available information including RAN capabilities in the registration area, the NSSF 330 may perform one or more operations to select a network slice instance to serve the UE 360. Alternatively, the NSSF 330 may defer selection of a network slice instance until at least one network slice instance in the registration area is capable of serving the UE 360.

[0080] In some examples, the group network slice for UE 360 can be changed dynamically when UE 360 registers with the network. In such examples, the change of the group network slice for UE 360 can be initiated by the network or the UE under various conditions. Based on the operator's operation or deployment plan, multiple network slice instances associated with common network slice selection assistance information can be deployed in the same registration area or different registration areas. In some examples, the registration area assigned to UE 360 by AMF 320 can have homogeneous support for network slicing. When the network slice for one or more protocol data unit sessions is no longer available to UE 360 under the same AMF 320, AMF 320 can instruct SMF 325 to autonomously release UE 360. In some examples, establishing a protocol data unit session to data network 310 in the network slice can allow data to be sent in the network slice.

[0081] Figure 4 A block diagram of an exemplary wireless communication device 400 supporting techniques for LAN clients to participate in network slicing according to some embodiments is shown. In some embodiments, the wireless communication device 400 is configured to perform the above-mentioned respective references to Figure 12 、 13 In some embodiments, the wireless communication device 400 may be one or more of the processes 1200, 1300, and 1400 described herein. Figure 8 The wireless communication device described or referred to herein Figure 9 1. An exemplary embodiment of a wireless communication device is described. For example, the wireless communication device 400 may be a chip, SoC, chipset, package, or device that includes at least one processor, a Wi-Fi (IEEE 802.11) modem, and a cellular modem. In some embodiments, the wireless communication device 400 may be a CPE or a device used in a CPE (thus, the wireless communication device 400 may be referred to as CPE 400 hereinafter). In some embodiments, the CPE 400 may be or may include an AP (such as AP 102) for serving one or more WLANs, such as using a Wi-Fi network or a 5G network.

[0082] The wireless communication device 400 (or CPE 400) includes a QOS manager 410, a CPE data path manager 425, a CPE connection manager 430, a 5G connection manager 435, a digital subscriber line (DSL) / gigabit passive optical network (GPON) connection manager 440, a WLAN connection manager 445, a LAN or Ethernet connection manager 450, a 5G modem 455, a DSL / GPON modem 460, a WLAN chipset 465, and an Ethernet chipset 470. Portions of one or more of the modules 410, 425, 430, 435, 440, 445, 450, 455, 460, 465, and 470 may be implemented at least in part in hardware or firmware. In some embodiments, at least some of the modules 410, 425, 430, 435, 440, 445, 450, 455, 460, 465, and 470 are implemented at least in part as software stored in memory. For example, portions of one or more of modules 410, 425, 430, 435, 440, 445, 450, 455, 460, 465, and 470 may be implemented as non-transitory instructions (or "code") executable by a processor to perform the functions or operations of the corresponding module.

[0083] The CPE connection manager 430 may be configured to set up connections between LAN and wide area network (WAN) interfaces. Figure 4 As shown, the WAN interference may include a 5G WAN interface and a DSL / GPON WAN interface. In some embodiments, the 5G WAN and the DSL / GPON WAN may be referred to as a hybrid WAN. In some examples, the CPE 400 may use such a hybrid WAN. In some embodiments, the CPE connection manager 430 may be configured to perform traffic switching and traffic steering. Additionally or alternatively, the CPE connection manager 430 may be configured to set up one or more channels across multiple LAN and WAN interfaces. In some embodiments, the CPE connection manager 430 may be configured to set up or terminate (e.g., tear down) a connection with a network or with one or more WLAN clients (such as STA 104). According to some embodiments, the CPE connection manager 430 in conjunction with the QOS manager 410 may set up or terminate one or more connections (as described in reference Figure 5 and 6 further described).

[0084] The QOS manager 410 can be configured to determine whether a new QOS flow can be admitted to an existing flow. For example, the QOS manager 410 can be configured to control the admission of new QOS flows and maintain submitted QOS flows. In some examples, the QOS manager 410 can be configured to determine one or more QOS parameters associated with a 5G network (such as a 5G WAN or 5G WLAN). In such embodiments, the QOS manager 410 can be configured to coordinate QOS flows on a LAN (such as Ethernet and Wi-Fi) and a 5G WAN or 5G WLAN (such as DSL / GPON). In some examples, the QOS manager 410 can be configured to use one or more submitted QOS parameters to coordinate QOS flows. In some embodiments, the QOS manager 410 can be configured to determine resource allocation (such as buffer resource allocation) within the CPE 400. In some examples, the QOS manager 410 can be configured to determine the random access memory (RAM) supported by various interfaces and the data rates supported by the various interfaces. In some examples, the QOS manager 410 can be configured to optimize resources within the CPE 400. In some examples, the QOS manager 410 can be configured to periodically mark resources into multiple states (such as green, yellow, and red) to facilitate decision making during the entry of QOS flows associated with a session or network slice. Additionally or alternatively, the QOS manager 410 can be configured to mark resources into multiple states to effectively maintain a session or network slice.

[0085] As reference Figure 4As shown, the CPE connection manager 430, the QOS manager 410, and the CPE data path manager 425 can be coupled to each other and can be configured to send and receive one or more commands and notifications. In some embodiments, the CPE data path manager 425 can be configured to handle traffic, including traffic switching, maintaining traffic statistics, and sending and receiving traffic on various interfaces. In some examples, the CPE data path manager 425 can be configured to manage received or sent traffic using a combination of the 5G connection manager 435, the DSL / GPON connection manager 440, the WLAN connection manager 445, the LAN or Ethernet connection manager 450, the 5G modem 455, the DSL / GPON modem 460, the WLAN chipset 465, and the Ethernet chipset 470. In some examples, the 5G modem 455 can be coupled to a URSP daemon (not shown). The URSP daemon can be configured to manage routing policies for UEs. In some examples, the URSP daemon can be configured to receive one or more updates to routing policies resulting from network changes, including changes initiated by the Policy and Charging Framework (PCF). In some examples, the URSP daemon can be configured to receive one or more updates at runtime. Additionally or alternatively, the URSP daemon can be configured to track all slice selection assistance information (such as network slice selection assistance information, configuration slice selection assistance information, or permission slice selection assistance information).

[0086] Figure 5 An exemplary timing diagram 500 illustrating an exemplary process for a LAN client to participate in network slicing according to some embodiments is shown. The timing diagram 500 may be implemented by a combination of a UE 502 (such as a STA 104 or a LAN client), a 5G-CPE 518 (such as an AP 102), a wireless communication network (such as a 5G network 514), and an application provider 516. The UE 502 and the 5G-CPE 518 may be reference Figure 1 and 2 5G-CPE 518 may include a CPE connection manager 504, a 5G connection manager 506, a QOS manager 508, a URSP daemon 510, and a 5G modem 512. Each of the components included in 5G-CPE 518 may be a reference Figure 4 Examples of corresponding devices described. Although not in Figure 5 Although not depicted in FIG, UE 502 may include or host one or more applications.

[0087] In some embodiments, 5G-CPE 518 may be an example of an AP having the ability to access a 5G network, such as 5G network 514. UE 502 and 5G-CPE 518 may access network slices, such as those available in 5G networks, to improve communication efficiency and end-to-end latency. Figure 5 In the example of FIG5 , UE 502 may be unaware of one or more network slices supported by 5G network 514. Alternative examples of timing diagram 500 may be implemented in which some steps may be performed in an order different from that described, some steps may be added, or some steps may not be performed at all. In some embodiments, the steps may include additional features not described below.

[0088] At 520, the UE 502 may initialize an application (such as an application hosted on the UE 502). In some embodiments, the UE 502 may send a request to initialize the application to the 5G-CPE 518 using a first wireless local area network. In some examples, the first wireless local area network may include a default packet data network. Additionally or alternatively, the first local area network may include a WAN. In some embodiments, upon receiving the request from the UE 502, the 5G-CPE 518 may send another request (such as a second request) to the network device (such as to the application provider 516) using the default packet data network or the default WAN, requesting the application provider 516 to initialize the application of the UE 502. In some examples, the 5G-CPE 518 may receive information associated with the network slice based on the request at 520.

[0089] At 522, UE 502 may receive an indication of successful initialization of an application hosted by UE 502. In some examples, 5G-CPE 518 may receive the indication from application provider 516, and 5G-CPE 518 may forward the information (or a message based on the received information) to UE 502.

[0090] At 524, the 5G-CPE 518 may analyze the received information (once or iteratively) to determine available network slices from a set of network slices supported by the 5G network 514. In some embodiments, the URSP daemon 510 may receive the network slice selection assistance information and may forward the network slice selection assistance information to the 5G connection manager 506. The 5G connection manager 506 may analyze the network slice selection assistance information and determine available network slices.

[0091] At 526, the 5G-CPE 518 may populate the available network slices on a web interface for display to the UE 502. In some embodiments, the 5G connection manager 506 may indicate the available network slices to the CPE connection manager 504, and the CPE connection manager 504 may populate the available network slices. For example, the CPE connection manager 504 may program one or more rules and may generate a message to be sent to the UE 502.

[0092] In some embodiments, 5G-CPE 518 may provide an option to a user operating UE 502 to provide credentials for accessing or establishing a network slice. In some exemplary embodiments, the message may be a multicast message or a broadcast message.

[0093] At 528, the UE 502 may determine whether a plugin is available to communicate with the 5G-CPE 518. In some embodiments, the UE 502 may determine that a plugin to communicate with the 5G-CPE 518, such as a plugin to communicate with the CPE connection manager 504 or the 5G connection manager 506, is not available at the UE 502.

[0094] At 530, the UE 502 may send one or more credentials (such as one or more identifiers) to the 5G-CPE 518. If the user of the 5G-CPE 518 (e.g., the UE 502 or a user operating the UE 502) provides credentials for accessing available network slices, the 5G-CPE 518 may program one or more rules in the CPE connection manager 504 to filter requests associated with configuring services or configuring network slices. The rules may filter the requests and may forward the requests to the CPE connection manager 504.

[0095] In some embodiments, the 5G-CPE 518 can determine that an application on the UE 502 has initiated an application session (e.g., using a domain name system or deep packet inspection or both). The 5G-CPE 518 can be configured to track requests and share the requests with the CPE connection manager 504. The CPE connection manager 504 can then request the 5G connection manager 506 to verify the credentials to determine whether the provided credentials match one or more pre-configured credentials. In the example where the credentials do not match, the CPE connection manager 504 can assign a data flow (such as a data flow associated with the initiated application session) to a default packet data network.

[0096] At 534 , the CPE connection manager 504 may verify the credentials or identifier received at 530 , and the CPE connection manager 504 may send a request including the identifier to the 5G connection manager 506 .

[0097] At 536, the 5G connection manager 506 may send a request for an available network slice or a new network slice to the QOS manager 508. For example, the 5G connection manager 506 may send the request to determine approval for establishing a new network slice. The QOS manager 508 may determine one or more data packets associated with the available network slice and may also determine whether the one or more data packets meet a QOS threshold. To determine the QOS threshold, the QOS manager 508 may send a request to the URSP daemon 510 at 538.

[0098] In some embodiments, the QOS manager 508 can determine whether a data flow associated with an available network slice or a new network slice can be admitted to a data queue based on a policy associated with the available network slice. Additionally or alternatively, the QOS manager 508 can determine whether one or more data packets associated with the network slice meet a QOS threshold. At 540, the 5G connection manager 506 can receive an approval from the URSP daemon 510 indicating that the one or more data packets meet the QOS threshold.

[0099] After receiving the approval, the 5G connection manager 506 may send a request to the application provider 516 to set up a network slice (such as an available network slice or a new network slice) at 542. In some embodiments, the 5G connection manager 506 may send one or more requests (such as an iteration request) to the CPE connection manager 504 at 544. In some embodiments, the request sent to the CPE connection manager 504 may include a request to set up a network slice. In response to the request received by the CPE connection manager 504, the CPE connection manager 504 may send a confirmation of the successful setup of the network slice at 546.

[0100] In some examples, the 5G network and application provider can set up the network slice at 548. At 550, the 5G connection manager 506 can receive confirmation of access to the available network slice, and at 552, the 5G connection manager 506 can establish a connection associated with the available network slice.

[0101] At 554, the 5G connection manager 506 may send an indication of the successful setup of the network slice to the CPE connection manager 504. At 556, the CPE connection manager 504 may send a confirmation of access to the available network slice to the UE 502. At 558, the UE 502 may map the data session to the new packet data network. In some embodiments, the 5G-CPE 518 may route traffic associated with the established network slice over the new packet data network. At 560, the 5G-CPE 518 (at the URSP daemon 510) may be configured to automatically learn and set one or more QOS rules or parameters associated with the established or accessed network slice.

[0102] At 562, the UE 502 may send an indication to the CPE connection manager 504 to close the communication session with the one or more other devices. At 564, the CPE connection manager 504 may send an indication to the 5G connection manager 506.

[0103] At 566, the 5G-CPE 518 (at the CPE connection manager 504) may receive an indication of the released network slice from the UE 502. For example, the UE 502 may release the network slice in response to closing the communication session and may send an indication of the released network slice to the 5G-CPE 518. In some examples, the released network slice may include an available network slice. At 568, the CPE connection manager 504, in conjunction with the 5G network 514, may terminate the packet data network (or connection) associated with the available network slice. At 570, the 5G network 514, in conjunction with the application provider 516, may use an iterative process to confirm the termination of the packet data network.

[0104] At 572, the 5G network 514 may send an indication of successful termination of the packet data network to the 5G connection manager 506. At 574, the 5G connection manager 506 may send a message to release network slice resources (such as frequency resources and time resources) to the QOS manager 608. At 576, upon receiving the message, the QOS manager 508 may update the QOS parameters associated with the released network slice.

[0105] At 578, the 5G connection manager 506 may send a message indicating the release of one or more resources associated with the release of the network slice to the CPE connection manager 504. At 580, the CPE connection manager 504 may send a message indicating the release of one or more resources associated with the release of the network slice to the UE 502.

[0106] Figure 6An exemplary timing diagram 600 illustrating an exemplary process for a LAN client to participate in network slicing according to some embodiments is shown. The timing diagram 600 may be associated with a combination of a UE 602 (such as a STA 104 or a LAN client), a 5G-CPE 618 (such as an AP 102), a wireless communication network (such as a 5G network 614), and an application provider 616. The UE 602 and the 5G-CPE 618 may be reference Figure 1 and 2 5G-CPE 618 may include a CPE connection manager 604, a 5G connection manager 606, a QOS manager 608, a URSP daemon 610, and a 5G modem 612. Each of the components included in 5G-CPE 618 may be a reference Figure 4 Examples of corresponding devices described. Although not in Figure 6 Although not depicted in FIG, UE 602 may include or host one or more applications.

[0107] In some embodiments, 5G-CPE 618 may be an example of an AP having the capability to access 5G network 614. UE 602 and 5G-CPE 618 may access network slices (such as those available in 5G networks) to improve communication efficiency and end-to-end latency. Figure 6 In the example of FIG6 , UE 602 may be aware of one or more network slices supported by 5G network 614. Alternative examples of timing diagram 600 may be implemented in which some steps may be performed in an order different from that described, some steps may be added, or some steps may not be performed at all. In some embodiments, the steps may include additional features not described below.

[0108] At 620, the UE 602 may initialize an application (such as an application hosted on the UE 602). As part of the initialization, the UE 602 may send a request to the 5G-CPE 618 to initialize the application using a first wireless local area network. In some embodiments, the first wireless local area network may include a default packet data network. Additionally or alternatively, the first local area network may include a default WAN / WLAN. In some embodiments, upon receiving the request from the UE 602, the 5G-CPE 618 may send another request (such as a second request) to a network device (such as to the application provider 616). In some examples, the 5G-CPE 618 may request the application provider 616 to initialize the UE 602's application using the default packet data network or the default WAN / WLAN. In some examples, the 5G-CPE 618 may receive information associated with a set of network slices based on sending the second request.

[0109] At 622, the UE 602 may receive an indication of successful initialization of the application hosted at the UE 602. In some examples, the 5G-CPE 618 may receive an indication of successful initialization of the application from the application provider 616, and the 5G-CPE 618 may forward the information (or a message based on the received information) to the LAN client 602.

[0110] At 624, the 5G-CPE 618 may analyze the received information to determine available network slices from the set of network slices. In some embodiments, the 5G-CPE 618 may receive at least one of network slice selection assistance information, configuration slice selection assistance information, or permission slice selection assistance information. In some examples, the URSP daemon 610 may receive the network slice selection assistance information. The 5G connection manager 606 may analyze the network slice selection assistance information and determine the available network slices. The 5G connection manager 606 may then indicate the available network slices to the CPE connection manager 604.

[0111] At 626, the 5G-CPE 618 may populate a web interface with available network slices (such as the network slices obtained from the URSP daemon 610) for display to the UE 602. The 5G-CPE 618 may provide an option to the user operating the UE 602 to provide credentials for accessing or establishing a network slice. In some examples, the CPE connection manager 604 may program one or more rules and may generate a message to be sent to the UE 602. In some exemplary embodiments, the message may be a multicast message or a broadcast message.

[0112] At 628, the UE 602 may determine whether there is a plugin available for communicating with the 5G-CPE 618. In some embodiments, the UE 602 may identify a plugin for communicating with the 5G-CPE 618 (such as a plugin for communicating with the CPE connection manager 604 or the 5G connection manager 606).

[0113] At 630, the 5G-CPE 618 (such as the CPE connection manager 604) may send a message, such as a multicast message or a broadcast message, indicating the available network slices. For example, the 5G-CPE 618 may send a multicast message or a broadcast message to one or more LAN clients (such as the UE 602) served by the 5G-CPE 618. In some examples, the multicast message or the broadcast message may be referred to as a discovery message. In some examples, the 5G-CPE 618 may broadcast one or more discovered or configured network slices (such as the available network slices) to the UE 602 using a universal plug and play message or one or more other multicast messages.

[0114] At 632, UE 602 may request access to an available network slice (such as an available network slice indicated in a multicast message or a broadcast message). For example, CPE connection manager 604 may receive a request to access an available network slice from UE 602. In some embodiments, the request may be based on the multicast message or broadcast message sent at 630. In some examples, an application hosted on UE 602 may use Universal Plug and Play messaging to request creation of a network slice by CPE connection manager 604.

[0115] At 634, the CPE connection manager 604 may send a request to access an available network slice to the 5G connection manager 606. In some embodiments, the CPE connection manager 604 may determine that a received request, such as a request received from the UE 602, includes a request to create a new network slice. In such an example, the CPE connection manager 604 may forward the request to create a new network slice to the 5G connection manager 606.

[0116] At 636, the 5G connection manager 606 may send a request for an available network slice or a new network slice to the QOS manager 608. The QOS manager 608 may determine one or more data packets associated with the available network slice and may also determine whether the one or more data packets meet a QOS threshold. To determine the QOS threshold, the QOS manager 608 may send a request to the URSP daemon 610 at 638. In some embodiments, the QOS manager 608 may determine whether a data flow associated with the available network slice or the new network slice can be admitted to a data queue. In some examples, the request sent to the URSP daemon 610 may include a request to check a policy associated with the available network slice. Additionally or alternatively, the QOS manager 608 may determine one or more data packets associated with the new network slice and may determine whether the one or more data packets meet a QOS threshold. At 640, the 5G connection manager 606 may receive an approval from the URSP daemon 610 indicating that the one or more data packets (such as the one or more data packets associated with the available network slice or the one or more data packets associated with the new network slice) meet the QOS threshold.

[0117] After receiving the approval from the QOS manager 608, the 5G connection manager 606 may send a request to set up a network slice (such as an available network slice or a new network slice) at 624. Figure 6As described above, the 5G connection manager 606 may send a request to the application provider 616 to set up a network slice. In some embodiments, the CPE connection manager 604 may request the 5G connection manager 606 to set up a new network slice. For example, at 644, the 5G connection manager 606 may send one or more requests (such as iteration requests) to the CPE connection manager 604. In some embodiments, the request sent to the CPE connection manager 504 may include a request to set up a network slice. In response to the request received by the CPE connection manager 604, the CPE connection manager 604 may send a confirmation of the successful setup of the network slice at 646.

[0118] In some examples, at 648, the 5G network and application provider can set up the network slice (e.g., using an iterative method to request settings associated with the network slice and confirm the settings associated with the network slice). At 650, the 5G connection manager 606 can receive confirmation of access to an available network slice, such as the available network slice requested by the UE at 602. For example, the 5G connection manager 606 can receive the confirmation from a network device, such as the application provider 616.

[0119] At 652, once the network slice is successfully set up, the 5G connection manager 606 can establish a connection associated with the available network slice. For example, the 5G connection manager 606, alone or in conjunction with the 5G modem, can establish a packet data network associated with the requested network slice (such as an available network slice or a new network slice). At 654, the 5G connection manager 606 can send an indication of the successful setup of the network slice to the CPE connection manager 604.

[0120] At 656, the CPE connection manager 604 may send a confirmation to the UE 602 of accessing the available network slice. At 658, the UE 602 may access a new data session with the application provider 616. For example, when a connection (such as a packet data network) is successfully established at the 5G-CPE 618, the connection may then be forwarded to the UE 602 for further use. In some embodiments, the 5G-CPE 618 may route traffic associated with the established network slice over the established packet data network by programming one or more rules in a data flow associated with the traffic. In some embodiments, the 5G-CPE 618 may program the data flow at an acceleration or data path engine of the 5G-CPE 618 (not shown). In some examples, at 660, the 5G-CPE 618 (at the URSP daemon 610) may be configured to automatically learn and set one or more QOS rules (or QOS parameters) associated with the established or accessed network slice. For example, the URSP daemon 610 may determine at least one QOS parameter associated with an available network slice based on initiating a new communication session.

[0121] At 662, the UE 602 may send an indication to the application provider 616 to terminate the new communication session (e.g., a communication session established using the available network slice). In some embodiments, the 5G-CPE 618 may receive the indication of termination of the new communication session associated with the available network slice. At 664, the application provider 616 may indicate to the UE 602 that the communication session has been successfully closed.

[0122] In some examples, the 5G-CPE 618 can send a confirmation to the UE 602 to terminate the new communication session associated with the available network slice.

[0123] At 666, the 5G-CPE 618 (at the CPE connection manager 604) may receive an indication of the released network slice from the UE 603. In some embodiments, the 5G-CPE 618 may receive the indication based on sending a confirmation of terminating the new communication session. For example, the UE 602 may release the network slice in response to terminating the communication session and may send an indication of the released network slice to the 5G-CPE 618. In some examples, the released network slice may include an available network slice (such as an available network slice determined by the 5G-CPE 618). At 668, the CPE connection manager 604 may send an indication of the released network slice to the 5G connection manager 606. In some examples, the CPE connection manager 604 may forward the indication received from the UE 602. Alternatively, the CPE connection manager 604 may send a second indication based on the indication received from the UE 602.

[0124] At 670, the 5G-CPE 618, in conjunction with the 5G network 614, may terminate the packet data network (or connection) associated with the available network slice. At 672, the 5G network 614, in conjunction with the application provider 616, may use an iterative process to confirm the termination of the packet data network.

[0125] At 674, the 5G network 614 may send an indication of successful termination of the packet data network to the 5G connection manager 606. At 676, the 5G connection manager 606 may send a message to the QOS manager 608. The message may include an indication of released network slice resources (such as frequency resources and time resources). At 678, upon receiving the message from the 5G connection manager 606, the QOS manager 608 may update the QOS parameters associated with the released network slice.

[0126] At 680, the 5G connection manager 606 may send a message to the CPE connection manager 604 indicating the release of one or more resources associated with the release of the network slice. In some examples, the message to the CPE connection manager 604 may be the same as or based on the message described at 676. At 682, the CPE connection manager 604 may send a message to the UE 602 indicating the release of one or more resources associated with the release of the network slice. As described herein, the message to the UE 602 may be the same as or based on the message described at 680.

[0127] Figure 7 An exemplary process 700 for a LAN client to participate in network slicing according to some embodiments is shown. The process 700 may be associated with a 5G-CPE (such as AP 102), which may be an example of a wireless communication device. The 5G-CPE may be configured to perform the aforementioned respective Figure 12 、 13 In some embodiments, the 5G-CPE may be one or more of the processes 1200, 1300, and 1400 described herein. Figure 4 The wireless communication device 400 described herein, or referenced herein Figure 8 Wireless communication devices described or referenced herein Figure 9 Example embodiments of wireless communication devices described herein. For example, a 5G-CPE may be a chip, SoC, chipset, package, or device that includes at least one processor, a Wi-Fi (IEEE 802.11) modem, and a cellular modem.

[0128] Alternative examples of process 700 may be implemented in which some steps may be performed in an order different from that described, some steps may be added, or some steps may not be performed at all. In some embodiments, the steps may include additional features not described below.

[0129] In some embodiments, in box 705, a 5G-CPE (such as a CPE with the ability to access a 5G network) is initialized (or started). In box 710, the 5G-CPE may initialize multiple components. In box 715, the 5G-CPE may determine whether a network slice is available. In box 720, in response to determining that a network slice is available, the 5G-CPE may broadcast or multicast network slice information to one or more UEs (such as STAs or LAN clients). In box 725, in response to determining that a network slice is available, the 5G-CPE may configure corresponding flow rules to capture (or collect) traffic associated with the network slice. As shown in reference Figure 7 Description, the process described in block 725 may be associated with a UE that is not aware of network slicing. Additionally or alternatively, the process described in block 720 may be associated with a UE that is aware of network slicing.

[0130] In some embodiments, in block 730, the 5G-CPE may receive a request to add a network slice or to delete a network slice. In block 735, in response to collecting traffic associated with the network slice, the 5G-CPE may determine whether the one or more credentials match existing credentials. Additionally or alternatively, the 5G-CPE may determine whether the one or more credentials match existing credentials in response to receiving the request to add a network slice or to delete a network slice. If the 5G-CPE determines that the one or more credentials do not match the existing credentials, then in block 745, the 5G-CPE may terminate the slice initiation and route the application over the default data network.

[0131] In some embodiments, in response to determining that one or more credentials match existing credentials, the 5G-CPE may determine whether the network slice can be admitted in the data flow in block 740. In response to determining that the network slice can be admitted, the 5G-CPE may initiate the network slice in block 750. Alternatively, in response to determining that the network slice may not be admitted, the 5G-CPE may stop (or terminate) the slice initiation and route the application through the default data network in block 745. In block 755, the 5G-CPE may communicate the success or failure of the slice creation to the client and create a flow mapping if the slice creation was successful.

[0132] In some embodiments, initializing the plurality of components in block 710 includes initializing the plurality of components of the 5G-CPE. For example, the 5G-CPE initializes the CPE connection manager, the 5G connection manager, the QOS manager, and the URSP daemon, each of which may be referenced Figures 4 to 6 An example of the module described.

[0133] Figure 8 A block diagram of an exemplary wireless communication device supporting techniques for LAN clients to participate in network slicing according to some embodiments is shown. In some embodiments, the wireless communication device is configured to perform the above-mentioned respective references to Figure 12 、 13 In some embodiments, the wireless communication device may be one or more of the processes 1200, 1300, and 1400 described herein. Figure 4 The wireless communication device described or referred to herein Figure 9 An exemplary embodiment of a wireless communication device 400 is described. 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 802.11) modem, and a cellular modem.

[0134] In some embodiments, the wireless communication device may be a CPE or a device used in a CPE (thus, the wireless communication device may be referred to as a CPE hereinafter). In some embodiments, the CPE may be or include an AP (such as AP 102) for serving one or more WLANs, such as using a Wi-Fi network or a 5G network.

[0135] The wireless communication device may include a receiver 802, a UE communication manager 804, and a transmitter 806. Portions of one or more of modules 802, 804, and 806 may be implemented at least in part in hardware or firmware. In some embodiments, at least some of modules 802, 804, and 806 are implemented at least in part as software stored in a memory. For example, portions of one or more of modules 802, 804, and 806 may be implemented as non-transitory instructions (or "code") that can be executed by a processor to perform the functions or operations of the corresponding module.

[0136] The receiver 802 is configured to receive information such as data packets, user data, or control information associated with various information channels (e.g., control channels, data channels, information related to LAN clients participating in network slicing). The information can be passed to other components of the device. The receiver 802 can be a reference Figure 11 Examples of various aspects of the transceiver 1120 are described. The receiver 802 may utilize a single antenna or a group of antennas.

[0137] The communication manager 804 may send a multicast message indicating available network slices to one or more LAN clients of the device. The communication manager 804 may then receive a request from a first LAN client among the one or more LAN clients to access the available network slice based on the multicast message, and establish a connection associated with the available network slice at the wireless communication device based on receiving the request. The communication manager 804 may send a confirmation of access to the new network slice to the first LAN client based on establishing the connection.

[0138] The communication manager 804 may also send a multicast message indicating an available network slice to one or more LAN clients of the device. The communication manager 804 may receive an identifier associated with the available network slice from a first LAN client among the one or more LAN clients based on the multicast message, establish a connection associated with the available network slice at the device based on successful verification of the identifier, and send a confirmation of access to the available network slice to the first LAN client based on establishing the connection. The communication manager 804 may be an example of aspects of the communication manager 1110 described herein.

[0139] The transmitter 806 can transmit signals generated by other components of the device. In some examples, the transmitter 806 can be collocated with the receiver 802 in the transceiver module. For example, the transmitter 806 can be a reference Figure 11 Examples of various aspects of the transceiver 1120 are described. The transmitter 806 may utilize a single antenna or a group of antennas.

[0140] Figure 9 A block diagram of an exemplary wireless communication device supporting techniques for LAN clients to participate in network slicing according to some embodiments is shown. In some embodiments, the wireless communication device is configured to perform the above-mentioned respective references to Figure 12 、 13 In some embodiments, the wireless communication device may be one or more of the processes 1200, 1300, and 1400 described herein. Figure 4 The wireless communication device described or referred to herein Figure 8 An exemplary embodiment of a wireless communication device 400 is described. For example, the wireless communication device may be a chip, SoC, chipset, package, or device (such as a CPE) that includes at least one processor, a Wi-Fi (IEEE 802.11) modem, and a cellular modem.

[0141] In some embodiments, the wireless communication device may be a CPE or a device used in a CPE (thus, the wireless communication device may be referred to as a CPE hereinafter). In some embodiments, the CPE may be or include an AP (such as AP 102) for serving one or more WLANs, such as using a Wi-Fi network or a 5G network.

[0142] The wireless communication device includes a receiver 910, a communication manager 915, a message component 920, a request processing component 925, a connection establishment component 930, a confirmation component 935, an identifier component 940, and a transmitter 945. Portions of one or more of modules 910, 915, 920, 925, 930, 935, 940, and 945 may be implemented at least in part in hardware or firmware. In some embodiments, at least some of modules 910, 915, 920, 925, 930, 935, 940, and 945 are implemented at least in part as software stored in a memory. For example, portions of one or more of modules 910, 915, 920, 925, 930, 935, 940, and 945 may be implemented as non-transitory instructions (or "code") that can be executed by a processor to perform the functions or operations of the corresponding module.

[0143] The receiver 910 may be configured to receive information such as data packets, user data, or control information associated with various information channels (e.g., control channels, data channels, information related to LAN client participation in network slicing). The information may be passed to other components of the device. The receiver 910 may be a reference Figure 11 Examples of various aspects of the transceiver 1120 are described. The receiver 910 may utilize a single antenna or a group of antennas.

[0144] The communication manager 915 may be an example of aspects of the communication manager 804 as described herein. The communication manager 915 804 is configured to include a message component 920, a request processing component 925, a connection establishment component 930, an acknowledgement component 935, and an identifier component 940. The communication manager 915 may be an example of aspects of the communication manager 1110 described herein.

[0145] The message component 920 is configured to send a multicast message indicating available network slices to one or more LAN clients of the device. The request processing component 925 is configured to receive a request to access the available network slice from a first LAN client of the one or more LAN clients based on the multicast message.

[0146] The connection establishing component 930 is configured to establish a connection associated with the available network slice at the device based on receiving the request. The confirmation component 935 is configured to send a confirmation of access to the new network slice to the first LAN client based on establishing the connection.

[0147] The message component 920 is configured to send a multicast message indicating available network slices to one or more LAN clients of the device. The identifier component 940 is configured to receive an identifier associated with the available network slice from a first LAN client of the one or more LAN clients based on the multicast message.

[0148] The connection establishment component 930 is configured to establish a connection associated with the available network slice at the device based on successful verification of the identifier. The confirmation component 935 is configured to send a confirmation of access to the new network slice to the first LAN client based on the establishment of the connection.

[0149] The transmitter 945 is configured to transmit signals generated by other components of the device. In some examples, the transmitter 945 can be collocated with the receiver 910 in the transceiver module. For example, the transmitter 945 can be a reference Figure 11 Examples of various aspects of the transceiver 1120 are described. The transmitter 945 can utilize a single antenna or a group of antennas.

[0150] Figure 10 A block diagram of an exemplary wireless communication device supporting techniques for LAN clients to participate in network slicing according to some embodiments is shown. In some embodiments, the wireless communication device is configured to perform the above-mentioned respective references to Figure 12 、 13 In some embodiments, the wireless communication device may be one or more of the processes 1200, 1300, and 1400 described herein. Figure 4 The wireless communication device 400 described herein, or referenced herein Figure 8 Wireless communication devices described or referenced herein Figure 9 Example embodiments of wireless communication devices are described. For example, the wireless communication device may be a chip, SoC, chipset, package, or device (such as CPE) that includes at least one processor, a Wi-Fi (IEEE 802.11) modem, and a cellular modem.

[0151] In some embodiments, the wireless communication device may be a CPE or a device used in a CPE (thus, the wireless communication device may be referred to as a CPE hereinafter). In some embodiments, the CPE may be or include an AP (such as AP 102) for serving one or more WLANs, such as using a Wi-Fi network or a 5G network.

[0152] The wireless communication device includes a messaging component 1010, a request processing component 1015, a connection establishment component 1020, a confirmation component 1025, a network slice component 1030, a QOS component 1035, an approval component 1040, an information component 1045, a communication session component 1050, and an identifier component 1055. Portions of one or more of modules 1010, 1015, 1020, 1025, 1030, 1035, 1040, 1045, 1050, and 1055 can be implemented at least in part in hardware or firmware. In some embodiments, at least some of modules 1010, 1015, 1020, 1025, 1030, 1035, 1040, 1045, 1050, and 1055 are implemented at least in part as software stored in memory. For example, portions of one or more of modules 1010, 1015, 1020, 1025, 1030, 1035, 1040, 1045, 1050, and 1055 may be implemented as non-transitory instructions (or "code") executable by a processor to perform the functions or operations of the corresponding module.

[0153] The message component 1010 is configured to send a multicast message indicating available network slices to one or more LAN clients of the device. In some examples, the message component 1010 is configured to send a multicast message indicating available network slices to one or more LAN clients of the device. In some embodiments, the multicast message includes one or more of a broadcast message or a universal plug and play message.

[0154] The request processing component 1015 is configured to receive a request for access to an available network slice from a first LAN client among one or more LAN clients based on a multicast message. The connection establishment component 1020 is configured to establish a connection associated with the available network slice at the device (such as a CPE) based on receiving the request. The confirmation component 1025 can send a confirmation of access to the new network slice to the first LAN client based on the establishment of the connection.

[0155] The network slicing component 1030 is configured to determine one or more data packets associated with an available network slice. The QOS component 1035 is configured to determine whether the one or more data packets satisfy a QOS threshold, wherein establishing a connection associated with the available network slice is based on determining that the one or more data packets satisfy the QOS threshold.

[0156] In some examples, the request processing component 1015 is configured to send a second request to the network device to access the available network slice based on receiving the request. In some examples, the confirmation component 1025 is configured to receive a confirmation from the network device to access the available network slice, wherein establishing the connection associated with the available network slice is based on receiving the confirmation from the network device, and wherein the confirmation sent to the first LAN client is based on the confirmation received from the network device.

[0157] In some examples, the network slicing component 1030 is configured to receive information associated with a set of network slices from the network device based on sending the request. In some examples, the network slicing component 1030 is configured to delete the second network slice based on receiving the second request.

[0158] In some examples, the request processing component 1015 is configured to receive a second request from the first LAN client to create a new network slice, wherein the second request is based on a multicast message. The approval component 1040 is configured to determine an approval status associated with the new network slice. In some examples, the request processing component 1015 is configured to send a third request to the network device to access the new network slice based on determining the approval status. In some examples, the confirmation component 1025 is configured to receive a confirmation from the network device to access the new network slice based on sending the third request.

[0159] In some examples, the message component 1010 is configured to send a multicast message based on determining an available network slice. In some examples, the message component 1010 is configured to send a message to the first LAN client indicating the release of one or more resources associated with the released slice based on receiving an indication to release the slice.

[0160] In some examples, the request processing component 1015 is configured to receive a second request from the first LAN client to delete the second network slice, wherein the second request is based on a multicast message. In some examples, the request processing component 1015 is configured to receive a second request from the first LAN client to initialize an application using the first wireless local area network. In some examples, the request processing component 1015 is configured to receive a request from the first LAN client to initialize an application at the first LAN client using the first wireless local area network, wherein receiving the identifier is based on receiving the request.

[0161] In some examples, the request processing component 1015 is configured to receive a request associated with an available network slice from a first LAN client. In some examples, receiving an identifier associated with the available network slice is based on receiving the request. In some examples, the request processing component 1015 is configured to determine, in response to receiving the request, that the request is associated with the available network slice, wherein establishing a connection associated with the available network slice is based on determining that the request is associated with the available network slice.

[0162] In some examples, the request processing component 1015 is configured to send a request to the network device to access an available network slice based on receiving the identifier. In some examples, the request processing component 1015 is configured to receive a request to initialize an application from a first LAN client using a first wireless local area network.

[0163] In some examples, the request processing component 1015 is configured to send a request to the network device to initialize an application of the first LAN client using the first wireless local area network. In some examples, the connection establishing component 1020 is configured to establish a connection associated with an available network slice at the device based on successful verification of the identifier.

[0164] In some examples, the connection establishing component 1020 is configured to establish a second connection associated with the new network slice at the device based on receiving the confirmation of accessing the new network slice. In some examples, the confirmation component 1025 is configured to send a confirmation of accessing the new network slice to the first LAN client based on establishing the connection.

[0165] In some examples, the confirmation component 1025 is configured to send a confirmation to the first LAN client of accessing the new network slice based on establishing the second connection. In some examples, the confirmation component 1025 is configured to send a confirmation to the first LAN client of terminating the new communication session associated with the available network slice.

[0166] In some examples, the confirmation component 1025 is configured to receive a confirmation from the network device to access the available network slice, wherein establishing the connection associated with the available network slice is based on receiving the confirmation from the network device, and wherein the confirmation sent to the first LAN client is based on the confirmation received from the network device. In some examples, the confirmation component 1025 is configured to send a confirmation to the first LAN client to terminate the new communication session associated with the available network slice.

[0167] The identifier component 1055 is configured to receive an identifier associated with an available network slice from a first LAN client among the one or more LAN clients based on the multicast message. In some examples, the identifier component 1055 can determine whether the identifier associated with the available network slice matches a second identifier in response to receiving the request, wherein establishing a connection associated with the available network slice is based on determining that the identifier associated with the available network slice matches the second identifier.

[0168] In some examples, an indication to publish a slice is received from the first LAN client based on sending a confirmation to terminate the new communication session, wherein the published slice includes the available network slice. In some examples, an indication to publish a slice is received from the first LAN client based on sending a confirmation to terminate the new communication session, wherein the published slice includes the available network slice.

[0169] In some examples, the QOS component 1035 is configured to determine QOS parameters associated with the available network slice based on initiating the new communication session. In some examples, the QOS component 1035 is configured to update the QOS parameters associated with the available network slice based on receiving an indication to release the slice.

[0170] In some examples, the QOS component 1035 is configured to determine whether the one or more data packets satisfy a QOS threshold, wherein establishing a 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 1035 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 1035 is configured to update the QOS parameter associated with the available network slice based on receiving an indication to release the slice.

[0171] The information component 1045 is configured to receive information associated with a set of network slices from the network device based on sending the second request. In some embodiments, 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 1050 is configured to initiate a new communication session with the application provider in response to sending a confirmation of access to the available network slice. In some examples, the communication session component 1050 is configured to receive an indication of termination of the new communication session associated with the available network slice from the first LAN client.

[0172] In some examples, the communication session component 1050 is configured to initiate a new communication session with the application provider in response to sending a confirmation of access to the available network slice. In some examples, the communication session component 1050 is configured to receive an indication of termination of the new communication session associated with the available network slice from the first LAN client.

[0173] Figure 11 A block diagram of an exemplary wireless communication system supporting techniques for LAN clients to participate in network slicing according to some embodiments is shown. The wireless communication network 1105 may be configured to perform the operations described above with reference to Figure 12 、 13 In some embodiments, the wireless communication device 1105 may be one or more of the processes 1200, 1300, and 1400 described herein. Figure 4 The wireless communication device 400 described herein, or referenced herein Figure 8 Wireless communication devices described or referenced herein Figure 9 Example embodiments of wireless communication devices are described. For example, the wireless communication device 1105 can be a chip, SoC, chipset, package, or device that includes at least one processor, a Wi-Fi (IEEE 802.11) modem, and a cellular modem.

[0174] In some embodiments, the wireless communication device 1105 may be a CPE or a device used in a CPE (thus, the wireless communication device 1105 may be referred to as a CPE hereinafter). In some embodiments, the CPE may be or include an AP (such as AP 102) for serving one or more WLANs, such as using a Wi-Fi network or a 5G network.

[0175] The wireless communication device 1105 includes a communication manager 1110, a network communication manager 1115, a transceiver 1120, one or more antennas 1125, a memory 1130, a processor 1140, and an inter-station communication manager 1145. Portions of one or more of modules 1110, 1115, 1120, 1125, 1130, 1014, 1140, and 1145 may be implemented at least in part in hardware or firmware. For example, the communication manager 1110 may be implemented at least in part via a modem. In some embodiments, at least some of modules 1110, 1115, 1120, 1125, 1130, 1014, 1140, and 1145 may be implemented at least in part as software stored in memory. For example, portions of one or more of modules 1110, 1115, 1120, 1125, 1130, 1014, 1140, and 1145 may be implemented as non-transitory instructions (or "code") executable by a processor to perform the functions or operations of the corresponding module.

[0176] The communication manager 1110 is configured to send a multicast message indicating available network slices to one or more LAN clients (such as UEs or STAs) of the device, and receive a request to access the available network slice from a first LAN client among the one or more LAN clients based on the multicast message. The communication manager 1110 is configured to establish a connection associated with the available network slice at the device based on receiving the request, and send a confirmation of access to the available network slice to the first LAN client based on establishing the connection. The communication manager 1110 is also configured to send a multicast message indicating available network slices to the one or more LAN clients of the device.

[0177] The communication manager 1110 is configured to receive an identifier associated with the available network slice from a first LAN client among the one or more LAN clients based on the multicast message, and to establish a connection associated with the available network slice at the device based on successful verification of the identifier. The communication manager 1110 is configured to send a confirmation of access to the new network slice to the first LAN client based on the establishment of the connection.

[0178] The network communications manager 1115 is configured to manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communications manager 1115 is configured to manage the transmission of data communications for client devices, such as one or more UEs 115.

[0179] As described above, transceiver 1120 is configured to communicate bidirectionally via one or more antennas, wired or wireless links. For example, transceiver 1120 is configured to represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1120 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, as well as demodulate packets received from the antenna.

[0180] In some embodiments, a wireless device may include a single antenna 1125. However, in some embodiments, the device may have more than one antenna 1125, which may be capable of transmitting or receiving multiple wireless transmissions simultaneously.

[0181] The memory 1130 may include RAM and ROM. The memory 1130 may store computer-readable, computer-executable code 1135 including instructions that, when executed, cause the processor to perform the various functions described herein. In some embodiments, the memory 1130 may include, among other things, a basic input / output system (BIOS), which may control basic hardware or software operations, such as interacting with peripheral components or devices.

[0182] The processor 1140 may include an intelligent hardware device (e.g., a 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 embodiments, the processor 1140 may be configured to operate a memory array using a memory controller. In other embodiments, the memory controller may be integrated into the processor 1140. The processor 1140 may be configured to execute computer-readable instructions stored in the memory to perform various functions (e.g., functions or tasks that support LAN clients to participate in network slicing).

[0183] The inter-station communication manager 1145 is configured to manage communications with other wireless communication devices (e.g., AP 102 or STA 104) and may include a controller or scheduler for controlling communications. For example, the inter-station communication manager 1145 may coordinate the scheduling of transmissions for various interference mitigation techniques such as beamforming or joint transmission.

[0184] Figure 12 A flow chart illustrating an exemplary process 1200 for a LAN client to participate in network slicing according to some embodiments is shown. The process 1200 may be performed by, for example, a LAN client as described above with reference to FIG. Figures 8 to 10 In some embodiments, process 1200 begins at block 1205 by sending a multicast message. In block 1210, process 1200 continues by receiving a request to access an available network slice. In block 1215, process 1200 continues by establishing a connection associated with the available network slice. In block 1220, process 1200 further continues by sending a confirmation of access to the available network slice.

[0185] In some embodiments, sending the multicast message in block 1205 includes sending a multicast message indicating the available network slices to one or more LAN clients of the device (such as UEs). Operation 1205 may be performed according to the methods described herein. In some examples, the multicast message may be sent by a user as described in reference to Figures 8 to 11 The messaging components are described to perform various aspects of the operations of 1205.

[0186] In some embodiments, receiving a request to access an available network slice in block 1210 includes receiving a request from a first LAN client of one or more LAN clients. In some examples, the request may be based on a sent multicast message. Operation 1210 may be performed according to methods described herein. In some examples, the request may be received by a first LAN client of the one or more LAN clients. Figures 8 to 11 The request processing components are described to perform various aspects of the operation of 1210.

[0187] In some embodiments, establishing a connection associated with an available network slice in block 1215 includes establishing a connection associated with an available network slice at the device. In some examples, the device may include a wireless communication device. In some examples, the wireless communication device may establish the connection based on receiving the request. Operation 1215 may be performed according to the methods described herein. In some examples, the method may be performed by a user as described in reference to FIG. Figures 8 to 11 The connection establishment components are described to perform various aspects of the operations of 1215.

[0188] In some embodiments, sending the confirmation of access to the available network slice in block 1220 includes sending the confirmation to the first LAN client. In some embodiments, sending the confirmation of access to the available network slice in block 1220 includes sending the confirmation based on establishing the connection. Operation 1220 can be performed according to the methods described herein. In some examples, the operation can be performed by, for example, Figures 8 to 11 The confirmation components are described to perform various aspects of the operation of 1220.

[0189] Figure 13 A flow chart illustrating an exemplary process 1300 for a LAN client to participate in network slicing according to some embodiments is shown. The process 1300 may be performed by a process such as that described above with reference to Figures 8 to 10 In some embodiments, process 1300 begins in block 1305 by sending a multicast message. In block 1310, process 1300 continues with receiving a request to access an available network slice. In block 1315, process 1300 continues with determining one or more data packets. In block 1320, process 1300 further continues with determining whether the one or more data packets meet a QOS threshold. In block 1325, process 1300 further continues with establishing a connection. In block 1330, process 1300 further continues with sending a confirmation of access to the available network slice.

[0190] In some embodiments, sending the multicast message in block 1305 includes sending a multicast message indicating the available network slices to one or more LAN clients of the device (such as UEs). Operation 1305 may be performed according to the methods described herein. In some examples, the multicast message may be sent by a user as described in reference to Figures 8 to 11 The messaging components are described to perform various aspects of the operations of 1305.

[0191] In some embodiments, receiving a request to access an available network slice in block 1310 includes receiving a request to access an available network slice from a first LAN client of one or more LAN clients based on a multicast message. Operation 1310 may be performed according to the methods described herein. In some examples, the method may be performed by a user as described in reference to Figures 8 to 11 The request processing components are described to perform various aspects of the operation of 1310.

[0192] In some embodiments, determining one or more data packet slices in block 1315 includes determining one or more data packets associated with available network slices. Operation 1315 may be performed according to methods described herein. In some examples, the method may be performed by, for example, Figures 8 to 11 The described network slicing components are used to perform various aspects of the operations of 1315.

[0193] In some embodiments, determining whether one or more data packets satisfy a QOS threshold in block 1320 includes determining whether one or more data packets satisfy a QOS threshold. In some embodiments, establishing a connection associated with an available network slice is based on determining that one or more data packets satisfy a QOS threshold. Operation 1320 may be performed according to methods described herein. In some examples, the process may be performed by, for example, Figures 8 to 11 The QOS components are described to perform various aspects of the operation of 1320.

[0194] In some embodiments, establishing a connection in block 1325 includes establishing a connection associated with an available network slice at the device based on receiving the request. Operation 1325 may be performed according to methods described herein. In some examples, the process may be performed by, for example, Figures 8 to 11 The connection establishment components are described to perform various aspects of the operations of 1325.

[0195] In some embodiments, sending a confirmation of access to the available network slice in block 1330 includes sending a confirmation of access to the available network slice to the first LAN client based on establishing the connection. Operation 1330 may be performed according to the methods described herein. In some examples, the method may be configured as described in reference to Figures 8 to 11 The confirmation component is described to perform various aspects of the operation of 1330.

[0196] Figure 14 A flow chart illustrating an exemplary process 1400 for a LAN client to participate in network slicing according to some embodiments is shown. The process 1400 may be performed by a process such as that described above with reference to Figures 8 to 10In some embodiments, process 1400 begins at block 1405 by sending a multicast message. In block 1410, process 1400 continues with receiving an identifier. In block 1415, process 1400 further continues with establishing a connection. In block 1420, process 1400 further continues with sending a confirmation of access to an available network slice.

[0197] In some embodiments, sending the multicast message in block 1405 includes sending a multicast message indicating the available network slices to one or more LAN clients of the device (such as UEs). Operation 1405 may be performed according to the methods described herein. In some examples, the multicast message may be sent by a user as described in reference to Figures 8 to 11 The messaging components are described to perform various aspects of the operations of 1405.

[0198] In some embodiments, receiving the identifier in block 1410 includes receiving an identifier associated with an available network slice from a first LAN client of the one or more LAN clients based on a multicast message. Operation 1410 may be performed according to the methods described herein. In some examples, the method may be configured as described in reference to Figures 8 to 11 The identifier components are described to perform various aspects of the operations of 1410.

[0199] In some embodiments, establishing a connection in block 1415 includes establishing a connection associated with an available network slice at the device based on successful verification of the identifier. Operation 1415 may be performed according to the methods described herein. In some examples, the connection may be established by a user as described in reference to Figures 8 to 11 The connection establishment components are described to perform various aspects of the operations of 1415.

[0200] In some embodiments, sending a confirmation of access to an available network slice in block 1420 includes sending a confirmation of access to an available network slice to the first LAN client based on establishing a connection. Operation 1420 may be performed according to the methods described herein. In some examples, the method may be configured as described in reference to Figures 8 to 11 The confirmation component is described to perform various aspects of the operation of 1420.

[0201] As used herein, unless expressly indicated otherwise, "or" is intended to be interpreted as inclusive. For example, "a or b" may include only a, only b, or a combination of a and b. As used herein, phrases referring to "at least one" or "one or more" in a list of items refer to any combination of those items, including individual members. For example, "at least one of a, b, or c" is intended to encompass the following possibilities: only a, only b, only c, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a, b, and c.

[0202] The various illustrative components, logic, logic blocks, modules, circuits, operations, and algorithmic processes described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, firmware, software, or a combination of hardware, firmware, or software, including the structures disclosed in this specification and their structural equivalents. The interchangeability of hardware, firmware, and software has been generally described in terms of functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and design constraints imposed on the overall system.

[0203] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the embodiments shown herein, but rather should be accorded the widest scope consistent with the principles and novel features disclosed in this disclosure.

[0204] In addition, various features described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, individual features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable subcombination. Thus, although features may be described above as functioning in a particular combination and even initially claimed as such, in some examples, one or more features from a claimed combination may be removed from that combination, and a claimed combination may involve a subcombination or a variation of a subcombination.

[0205] In some embodiments, the present invention provides a plurality of system components and the plurality of system components of the present invention are shown in Figure 1. Similarly, although operations are shown in a particular order in the figures, this should not be understood as requiring such operations to be performed in the particular order shown or in a sequential order or to perform all operations shown to achieve the desired result. In addition, the accompanying drawings may schematically describe one or more exemplary processes in the form of a flow chart (flowchart / flow diagram). However, other operations that are not depicted can be incorporated into the exemplary processes schematically shown. For example, one or more other operations can be performed before, after, simultaneously or therebetween any operation in the shown operations. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of the various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, but it should be understood as described program components and system can usually be integrated together in a single software product, or be packaged as multiple software products.

Claims

1. A method for wireless communication at a device, comprising: sending a multicast message indicating available network slices to one or more local area network clients of the device; Based at least in part on the multicast message, receiving a request from a first local area network client of the one or more local area network clients to access the available network slice; establishing, at the device, a connection associated with the available network slice based at least in part on receiving the request, wherein the connection comprises an end-to-end connection between the one or more local area network clients and a second network corresponding to the available network slice; as well as Based at least in part on establishing the connection, sending a confirmation of access to the available network slice to the first local area network client.

2. The method according to claim 1, further comprising: determining one or more data packets associated with the available network slice; as well as Determining whether the one or more data packets satisfy a quality of service threshold, 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.

3. The method according to claim 1, further comprising: Based at least in part on receiving the request, sending a second request to a network device to access the available network slice; as well as Receiving a confirmation of access to the available network slice from the network device, wherein establishing the connection associated with the available network slice is based at least in part on receiving the confirmation from the network device, and wherein the confirmation sent to the first local area network client is based at least in part on the confirmation received from the network device.

4. The method according to claim 1, further comprising: receiving a second request from the first local area network client to create a new network slice, wherein the second request is based at least in part on the multicast message; determining an approval status associated with the new network slice; as well as Based at least in part on determining the approval status, sending a third request to the network device to access the new network slice.

5. The method of claim 4 further comprises receiving a confirmation of access to the new network slice from the network device based at least in part on sending the third request.

6. The method according to claim 5, further comprising: establishing, at the device, a second connection associated with the new network slice based at least in part on receiving a confirmation of access to the new network slice; as well as Based at least in part on establishing the second connection, sending a confirmation of access to the new network slice to the first local area network client.

7. The method according to claim 1, further comprising: receiving, from the first local area network client, a second request to delete a second network slice, wherein the second request is based at least in part on the multicast message; as well as Deleting the second network slice based at least in part on receiving the second request.

8. The method according to claim 1, further comprising: Using the first wireless local area network, receiving a second request to initialize the application from the first local area network client; Using the first wireless local area network, sending the second request for initializing the application of the first local area network client to a network device; as well as Based at least in part on sending the second request, information associated with multiple network slices is received from the network device.

9. The method of claim 8, further comprising determining the available network slice from the plurality of network slices based at least in part on the information, wherein sending the multicast message is based at least in part on determining the available network slice.

10. The method according to claim 8, wherein: The information includes one or more of network slice selection assistance information, configuration slice selection assistance information, or permission slice selection assistance information.

11. The method according to claim 1, further comprising: initiating a new communication session with the application provider in response to sending a confirmation of access to the available network slice; as well as Determining a quality of service parameter associated with the available network slice based at least in part on initiating the new communication session.

12. The method according to claim 11, further comprising: receiving, from the first local area network client, an indication of termination of the new communication session associated with the available network slice; as well as Sending a confirmation to the first local area network client to terminate the new communication session associated with the available network slice.

13. The method according to claim 12, further comprising: Receiving an indication of published slices from the first local area network client based at least in part on sending a confirmation to terminate the new communication session, wherein the published slices include the available network slices; as well as Sending a message to the first local area network client indicating the publication of one or more resources associated with the published slice based at least in part on receiving the indication of the published slice.

14. The method of claim 13, further comprising updating the quality of service parameters associated with the available network slice based at least in part on receiving the indication of the released slice.

15. The method according to claim 1, wherein: The multicast message includes one or more of a broadcast message or a universal plug and play message.

16. A method for wireless communication at a device, comprising: sending a multicast message indicating available network slices to one or more local area network clients of the device; receiving, based at least in part on the multicast message, from a first local area network client of the one or more local area network clients, an identifier associated with the available network slice; establishing, at the device, a connection associated with the available network slice based at least in part on successful verification of the identifier, wherein the connection comprises an end-to-end connection between the one or more local area network clients and a second network corresponding to the available network slice; as well as Based at least in part on establishing the connection, sending a confirmation of access to the available network slice to the first local area network client.

17. The method according to claim 16, further comprising: receiving, using a first wireless local area network, from the first local area network client a request to initialize an application at the first local area network client, wherein receiving the identifier is based at least in part on receiving the request; as well as In response to receiving the request, determining whether the identifier associated with the available network slice matches a second identifier, wherein establishing the connection associated with the available network slice is based at least in part on determining that the identifier associated with the available network slice matches the second identifier.

18. The method according to claim 16, further comprising: receiving, from the first local area network client, a request associated with the available network slice, wherein receiving the identifier associated with the available network slice is based at least in part on receiving the request; as well as In response to receiving the request, determining that the request is 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 request is associated with the available network slice.

19. The method according to claim 16, further comprising: determining one or more data packets associated with the available network slice; as well as Determining whether the one or more data packets satisfy a quality of service threshold, 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.

20. The method of claim 16, further comprising: Based at least in part on receiving the identifier, sending a request to a network device to access the available network slice; as well as Receiving a confirmation of access to the available network slice from the network device, wherein establishing the connection associated with the available network slice is based at least in part on receiving the confirmation from the network device, and wherein the confirmation sent to the first local area network client is based at least in part on the confirmation received from the network device.

21. The method of claim 16, further comprising: Using a first wireless local area network, receiving a request to initialize an application from a client of the first local area network; Using the first wireless local area network, sending the request for initializing the application of the first local area network client to a network device; as well as Based at least in part on sending the request, information associated with multiple network slices is received from the network device.

22. The method of claim 21 further comprises determining the available network slice from the plurality of network slices based at least in part on the information, wherein sending the multicast message is based at least in part on determining the available network slice.

23. The method of claim 16, further comprising: initiating a new communication session with the application provider in response to sending a confirmation of access to the available network slice; as well as Determining a quality of service parameter associated with the available network slice based at least in part on initiating the new communication session.

24. The method according to claim 23, further comprising: receiving, from the first local area network client, an indication of termination of the new communication session associated with the available network slice; as well as Sending a confirmation to the first local area network client to terminate the new communication session associated with the available network slice.

25. The method according to claim 24, further comprising: Receiving an indication to release a slice from the first local area network client based at least in part on sending a confirmation to terminate the new communication session, wherein the released slice includes the available network slice; as well as Sending a message to the first local area network client indicating the publication of one or more resources associated with the published slice based at least in part on receiving the indication of the published slice.

26. The method of claim 25, further comprising updating the quality of service parameters associated with the available network slice based at least in part on receiving the indication of the released slice.

27. A wireless communication device, comprising: at least one modem; at least one processor; at least one memory communicatively coupled to the at least one processor and storing processor readable code that, when executed by the at least one processor in conjunction with the at least one modem, is configured to: sending a multicast message indicating available network slices to one or more local area network clients of the wireless communication device; Based at least in part on the multicast message, receiving a request from a first local area network client of the one or more local area network clients to access the available network slice; establishing, at the wireless communication device, a connection associated with the available network slice based at least in part on receiving the request, wherein the connection comprises an end-to-end connection between the one or more local area network clients and a second network corresponding to the available network slice; as well as Based at least in part on establishing the connection, sending a confirmation of access to the available network slice to the first local area network client.

28. The wireless communication device according to claim 27, wherein: The code for determining distributed resource units may be executed by the processor to cause the wireless communication device to: determining one or more data packets associated with the available network slice; and Determining whether the one or more data packets satisfy a quality of service threshold, 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.

29. A wireless communication device, comprising: at least one modem; at least one processor; at least one memory communicatively coupled to the at least one processor and storing processor readable code that, when executed by the at least one processor in conjunction with the at least one modem, is configured to: sending a multicast message indicating available network slices to one or more local area network clients of the device; receiving, based at least in part on the multicast message, from a first local area network client of the one or more local area network clients, an identifier associated with the available network slice; establishing, at the device, a connection associated with the available network slice based at least in part on successful verification of the identifier, wherein the connection comprises an end-to-end connection between the one or more local area network clients and a second network corresponding to the available network slice; as well as Based at least in part on establishing the connection, sending a confirmation of access to the available network slice to the first local area network client.

30. The wireless communication device of claim 29, wherein: The code for determining distributed resource units may be executed by the processor to cause the wireless communication device to: receiving, using a first wireless local area network, from the first local area network client a request to initialize an application at the first local area network client, wherein receiving the identifier is based at least in part on receiving the request; as well as In response to receiving the request, determining whether the identifier associated with the available network slice matches a second identifier, wherein establishing the connection associated with the available network slice is based at least in part on determining that the identifier associated with the available network slice matches the second identifier.

31. A system for wireless communication at a device, comprising: means for sending a multicast message indicating available network slices to one or more local area network clients of the device; means for receiving, based at least in part on the multicast message, a request from a first local area network client of the one or more local area network clients to access the available network slice; means for establishing, at the device, a connection associated with the available network slice based at least in part on receiving the request, wherein the connection comprises an end-to-end connection between the one or more local area network clients and a second network corresponding to the available network slice; as well as A component for sending a confirmation of access to the available network slice to the first local area network client based at least in part on establishing the connection.

32. A system for wireless communication at a device, comprising: means for sending a multicast message indicating available network slices to one or more local area network clients of the device; means for receiving, based at least in part on the multicast message, from a first local area network client of the one or more local area network clients, an identifier associated with the available network slice; means for establishing, at the device, a connection associated with the available network slice based at least in part on successful verification of the identifier, wherein the connection comprises an end-to-end connection between the one or more local area network clients and a second network corresponding to the available network slice; as well as A component for sending a confirmation of access to the available network slice to the first local area network client based at least in part on establishing the connection.

33. A non-transitory computer readable medium storing computer instructions that, when executed by a processor, perform a method for wireless communication at a device, the method comprising: sending a multicast message indicating available network slices to one or more local area network clients of the device; Based at least in part on the multicast message, receiving a request from a first local area network client of the one or more local area network clients to access the available network slice; establishing, at the device, a connection associated with the available network slice based at least in part on receiving the request, wherein the connection comprises an end-to-end connection between the one or more local area network clients and a second network corresponding to the available network slice; as well as Based at least in part on establishing the connection, sending a confirmation of access to the available network slice to the first local area network client.

34. A non-transitory computer readable medium storing computer instructions that, when executed by a processor, perform a method for wireless communication at a device, the method comprising: sending a multicast message indicating available network slices to one or more local area network clients of the device; receiving, based at least in part on the multicast message, from a first local area network client of the one or more local area network clients, an identifier associated with the available network slice; establishing, at the device, a connection associated with the available network slice based at least in part on successful verification of the identifier, wherein the connection comprises an end-to-end connection between the one or more local area network clients and a second network corresponding to the available network slice; as well as Based at least in part on establishing the connection, sending a confirmation of access to the available network slice to the first local area network client.

Images