Device and method for wireless communication based on back-off timer

Abstract

An apparatus for wireless communication includes a memory and a processor coupled to the memory. The processor is configured to send a data session establishment request to establish a data session with a network device using a wireless communication network. The data session establishment request has a first field indicating a requested network slice for the data session. The processor is also configured to receive an indication of an authorized network slice for the data session and receive an indication of a backoff timer value from the network device. The processor is also configured to: after a backoff timer based on the backoff timer value expires, send a first message associated with the authorized network slice, and send a second message having a second field corresponding to the first field of the data session establishment request.

Description

[0001] This application claims priority to U.S. patent application No. 17 / 185,309, entitled “Device and method for wireless communication based on back-off timer,” filed on February 25, 2021, and U.S. patent application No. 62 / 983,506, entitled “Device and method for wireless communication based on back-off timer,” filed on February 28, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0002]

[0006] Generally, aspects of the present disclosure relate to wireless communication systems, and more particularly, to wireless communication systems that communicate based on back-off timers. Background Art

[0003] Wireless communication networks are widely deployed to provide various communication services, such as voice, video, packet data, messaging, broadcasting, etc. These wireless networks can be multiple access networks that can support multiple users by sharing available network resources. Such a network (which is usually a multiple access network) supports the communication of multiple users by sharing available network resources. An example of such a network is the Universal Terrestrial Radio Access Network (UTRAN). UTRAN is a radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), which is a third generation (3G) mobile phone technology supported by the Third Generation Partnership Project (3GPP). Examples of multiple access network formats include code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, and single carrier FDMA (SC-FDMA) networks.

[0004] A wireless communication network may include several base stations or Node Bs that can support communication for several user equipments (UEs). A UE may communicate with a base station via a downlink and an uplink. A downlink (or forward link) refers to the communication link from a base station to a UE, while an uplink (or reverse link) refers to the communication link from a UE to a base station.

[0005] The base station may send data and control information to the UE on the downlink, and / or may receive data and control information from the UE on the uplink. On the downlink, transmissions from the base station may encounter interference due to transmissions from neighboring base stations or from other wireless radio frequency (RF) transmitters. On the uplink, transmissions from the UE may encounter interference from uplink transmissions of other UEs communicating with neighboring base stations or from other wireless RF transmitters. This interference may degrade performance on both the downlink and uplink.

[0006] As the demand for mobile broadband access continues to increase, the potential for interference and congested networks grows as more UEs access long-range wireless communication networks and more short-range wireless systems are deployed in communities. Research and development continues to advance wireless technologies, not only to meet the growing demand for mobile broadband access, but also to advance and enhance the user experience of mobile communications. Summary of the invention

[0007] In some aspects of the present disclosure, an apparatus for wireless communication includes a memory and a processor coupled to the memory. The processor is configured to send a data session establishment request to establish a data session with a network device using a wireless communication network. The data session establishment request has a first field indicating a requested network slice for the data session. The processor is also configured to receive an indication of an authorized network slice for the data session and receive an indication of a backoff timer value from the network device. The processor is also configured to send a first message associated with the authorized network slice after a backoff timer based on the backoff timer value expires, and send a second message having a second field corresponding to the first field of the data session establishment request after a backoff timer based on the backoff timer value expires.

[0008] In some other aspects of the present disclosure, a method of wireless communication includes: sending a data session establishment request by a user equipment (UE) device to establish a data session with a network device using a wireless communication network. The data session establishment request has a first field indicating a requested data network name (DNN) for the data session. The method also includes receiving an indication of an authorized DNN for the data session at the UE device, and receiving an indication of a backoff timer value from the network device at the UE device. The method also includes: after a backoff timer based on the backoff timer value expires, sending a first message associated with the authorized DNN, and sending a second message having a second field corresponding to the first field of the data session establishment request.

[0009] In some other aspects of the present disclosure, a device for wireless communication includes a memory and a processor coupled to the memory. The processor is configured to receive a data session establishment request to establish a data session with a user equipment (UE) device using a wireless communication network, and to send an indication of an authorized network slice for the data session. The processor is also configured to send a congestion notification message, the congestion notification message indicating one or more network slices associated with a backoff timer value. The one or more network slices indicate one or both of an authorized network slice or a requested network slice specified by the UE device. The processor is also configured to: in response to the expiration of a backoff timer based on the backoff timer value, receive a message associated with at least one of the one or more network slices.

[0010] In some other aspects of the present disclosure, a method of wireless communication includes: receiving, by a network device, a data session establishment request to establish a data session with a user equipment (UE) device using a wireless communication network. The method also includes sending, by the network device, an indication of an authorized data network name (DNN) for the data session, and sending, by the network device, a congestion notification message indicating one or more DNNs associated with a backoff timer value. The one or more DNNs indicate one or both of an authorized DNN or a requested DNN specified by the UE device. The method also includes: receiving, at the network device, a message associated with at least one of the one or more DNNs in response to expiration of a backoff timer based on the backoff timer value.

[0011] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as the basis for modifying or designing other structures for performing the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] A further understanding of the nature and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar components or features may have the same reference numerals. In addition, various components of the same type may be distinguished by following the reference numeral with a dash and a second reference numeral that distinguishes between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second reference numeral.

[0013] Figure 1 is a block diagram illustrating details of a wireless communication system configured to perform wireless communications based on a backoff timer in accordance with some aspects of the present disclosure.

[0014] Figure 2 is a block diagram showing a design of a base station and a UE configured to perform wireless communication based on a back-off timer in accordance with some aspects of the present disclosure.

[0015] Figure 3 is a block diagram illustrating a wireless communication system including a base station that performs wireless communication using a directional wireless beam and based on a back-off timer according to some aspects of the present disclosure.

[0016] Figure 4is a block diagram illustrating an example of a wireless communication system configured to perform wireless communications related to network slicing based on a backoff timer in accordance with some aspects of the present disclosure.

[0017] Figure 5 is a block diagram illustrating an example of a wireless communication system configured to perform wireless communications related to a domain name (DNN) based on a backoff timer according to some aspects of the present disclosure.

[0018] Figure 6 is a block diagram illustrating an example of a congestion notification message indicating a network slice indication message according to some aspects of the present disclosure.

[0019] Figure 7 is a block diagram illustrating an example of a congestion notification message indicating a DNN indication message according to some aspects of the present disclosure.

[0020] Figure 8 is a block diagram illustrating an example of a method of operation of a UE that may be performed to send messages associated with a network slice based on operation of a backoff timer in accordance with some aspects of the present disclosure.

[0021] Fig. 9 is a block diagram illustrating an example of a method of operation of a UE that may be performed to send a message associated with a DNN based on operation of a backoff timer in accordance with some aspects of the present disclosure.

[0022] Fig.10 is a block diagram illustrating another example of a method of operation of a UE that may be performed to send a message associated with a network slice based on operation of a backoff timer in accordance with some aspects of the present disclosure.

[0023] Fig.11 is a block diagram illustrating another example of a method of operation of a UE that may be performed to send a message associated with a DNN based on operation of a backoff timer in accordance with some aspects of the present disclosure.

[0024] Fig.12 is a block diagram illustrating an example of a method of operation of a network device that may be performed to indicate an association of a backoff timer with one or more network slices in accordance with some aspects of the present disclosure.

[0025] Fig.13 is a block diagram illustrating an example of a method of operation of a network device that may be performed to indicate an association of a backoff timer with one or more DNNs in accordance with some aspects of the present disclosure.

[0026] Fig.14 is a block diagram illustrating an example of a UE configured to perform wireless communications based on a backoff timer according to some aspects of the present disclosure.

[0027] Fig.15 is a block diagram illustrating an example of a base station configured to perform wireless communications based on a backoff timer in accordance with some aspects of the present disclosure. DETAILED DESCRIPTION

[0028] A wireless communication system may include devices that use data sessions to communicate messages, data, and other information. A data session may be conducted by a user equipment (UE) device and a network device (e.g., a base station) to enable communication between the UE and a device (e.g., a server) of a data network associated with a data network name (DNN). An example of a data session is a protocol data unit (PDU) session (also referred to herein as a packet data unit session).

[0029] In some examples, the UE device and the network equipment perform operations for the data session according to a protocol that specifies a network "slice" of the wireless communication system (e.g., a fifth generation session management (5GSM) communication protocol). Network slicing can refer to the selection or allocation of network resources. For example, to support a data session, the network equipment can select and allocate a set (or "slice") of network resources of the wireless communication system to the UE.

[0030] During a data session, in some cases, the network device may provide a back-off timer value to the UE. The back-off timer value may indicate a duration during which the UE will avoid sending certain communications (such as communications associated with the data session) to the network device. In some examples, the network device provides the back-off timer value to the UE in response to detecting one or more network congestion conditions associated with the wireless communication system (such as an amount or type of network congestion).

[0031] In some cases, the network slice may change during a data session. For example, newer wireless communication protocols may allow (or encourage) changing network slices to achieve efficient allocation of network resources. As an example, a data session establishment request sent by a UE to a network device may specify a requested network slice (or no network slice), and a data session establishment accept message sent by the network device to the UE may establish an authorized network slice that is different from the requested network slice (e.g., due to unavailability of the requested network slice). Therefore, in some wireless communication systems, one or more devices may not "agree" on which network slice (e.g., the requested network slice or the authorized network slice) the backoff timer value applies to, resulting in poor network resource allocation in some cases (e.g., where the device avoids sending a message associated with a certain network slice despite being eligible to send the message, or where the device sends a message associated with a certain network slice despite not being eligible to do so).

[0032] A first example of technology according to some aspects of the present disclosure applies a backoff timer value to both the requested network slice (if any) and the authorized network slice. For example, when counting down from the backoff timer value (or counting up to the backoff timer value), the UE may delay sending one or more messages associated with the requested network slice (if any), and may also delay sending one or more messages associated with the authorized network slice. When the backoff timer expires, the UE may send one or more messages associated with the requested network slice, one or more messages associated with the authorized network slice, or both. In the first example, the UE device may be configured to "assume" that the backoff timer value applies to both the requested network slice (if any) and the authorized network slice.

[0033] In a second example of a technique according to some aspects of the present disclosure, a network device provides at least one indication of a network slice to which a backoff timer value applies or does not apply. For example, certain bits of a 5GSM Congestion Retry Information Element (IE) message may indicate whether a backoff timer value applies (or does not apply) to a requested network slice, whether a backoff timer value applies (or does not apply) to an authorized network slice, or both.

[0034] Alternatively or additionally, operations associated with the first example or the second example may be performed with respect to the DNN. For example, in some cases, the DNN may change during a data session (e.g., where the authorized DNN is different from the requested DNN). In one example, the UE device may be configured to "assume" that the backoff timer value applies to both the requested DNN (if any) and the authorized DNN. In some other examples, the network device provides at least one indication of the network slice to which the backoff timer value applies or does not apply. For example, certain bits of the 5GSM Congestion Retry IE message may indicate whether the backoff timer value applies (or does not apply) to the requested DNN, whether the backoff timer value applies (or does not apply) to the authorized DNN, or both.

[0035] In some implementations, a network entity (e.g., a base station or other device) may dynamically select the first example or the second example based on one or more criteria. In some deployments, the first example may be more advantageous in conjunction with a first wireless communication protocol that does not allow changes to network slices (or DNNs) during a data session. In this case, the network entity may choose to operate based on the first example in response to detecting a threshold number of UEs communicating using the first wireless communication protocol. In some other deployments, the second example may be more advantageous in conjunction with a second wireless communication protocol that allows changes to network slices (or DNNs) during a data session. In this case, the network entity may choose to operate according to the second example in response to detecting a threshold number of UEs communicating using the second wireless communication protocol.

[0036] Alternatively or additionally, in some implementations, the network entity may select the first example or the second example based at least in part on the number of default session management functions (SMFs) of the network that handle requests that do not specify a network slice (or DNN). For example, in a situation where there is a larger number of SMFs in the network, it may be unnecessary to block requests that do not specify a network slice (or DNN), which may in some cases make operation according to the second example more advantageous than operation according to the first example. As a result, the network entity may be configured to select operation according to the first example in response to detecting that the number of default SMFs in the network does not satisfy (e.g., is less than) a threshold, and to select operation according to the second example in response to detecting that the number of default SMFs in the network satisfies (e.g., is greater than or equal to) a threshold.

[0037] By determining or indicating one or more network slices or DNNs according to some aspects of the present disclosure, network resource allocation can be improved. For example, a wireless communication system according to some aspects of the present disclosure can reduce or avoid situations where a device avoids sending a message associated with a certain network slice (e.g., before a backoff timer expires) despite being eligible to send the message. As another example, a wireless communication system according to some aspects of the present disclosure can reduce or avoid situations where a device sends a message associated with a certain network slice despite being inappropriate to do so (e.g., before a backoff timer expires).

[0038] In addition, in some cases, according to some aspects of the present disclosure, the user experience can be improved by determining or indicating one or more network slices or DNNs. To illustrate, a user may initiate an operation that is subject to a backoff timer, such as by loading an application that is to use a requested network slice, an authorized network slice, a requested DNN, or an authorized DNN. In this case, in response to determining that the operation initiated by the user is subject to the operation of the backoff timer, the UE may present a notification that alerts the user that the operation initiated by the user is subject to the operation of the backoff timer. In some cases, the notification may indicate the time until the operation can be completed (e.g., by indicating the current value of the backoff timer). As a result, the user can be warned more quickly than certain conventional techniques that attempt to perform an operation and then wait until the operation fails or "times out" (e.g., due to failure to receive a response to a message indicating a network slice or DNN that is subject to a backoff timer).

[0039] The detailed description in conjunction with the drawings is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. Instead, the detailed description includes specific details for the purpose of providing a thorough understanding of the subject matter of the present invention. It is clear to those skilled in the art that these specific details are not required in every case, and in some cases, well-known structures and components are shown in block diagram form for clarity of presentation.

[0040] The present disclosure generally relates to wireless communication systems, which are also referred to as wireless communication networks. In various examples, these techniques and devices can be used for wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth generation (5G) or new radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0041] OFDMA network can realize radio technology such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE802.20, flash-OFDM, etc. UTRA, E-UTRA and Global System for Mobile Communications (GSM) are part of Universal Mobile Telecommunication System (UMTS). In particular, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between telecommunication association groups that aims to define globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project that aims to improve the Universal Mobile Telecommunication System (UMTS) mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution of wireless technologies from LTE, 4G, 5G, NR and beyond, where access to the wireless spectrum is shared between networks using a new and different set of radio access technologies or radio air interfaces.

[0042] Specifically, 5G networks are expected to enable various deployments, various spectrums, and various services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to provide coverage for: (1) Massive Internet of Things (IoT) with ultra-high density (e.g., ~1M nodes / km^2), ultra-low complexity (e.g., ~10s bits / second), ultra-low energy (e.g., ~10+ years battery life), and deep coverage with the ability to reach challenging locations; (2) including mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1ms), and users with extensive mobility or lack of mobility; and (3) with enhanced mobile broadband including extremely high capacity (e.g., ~10Tbps / km^2), extreme data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness with advanced discovery and optimization.

[0043] 5G NR can be implemented using an optimized OFDM-based waveform with scalable parameter sets and transmission time intervals (TTIs); with a common, flexible framework to efficiently multiplex services and features using dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and with advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of parameter sets in 5G NR with scaling of subcarrier spacing can effectively address the operation of different services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, the subcarrier spacing can occur at 15kHz, such as on bandwidths of 1, 5, 10, 20MHz, etc. For other various outdoor and small cell coverage deployments of TDD greater than 3GHz, the subcarrier spacing can occur at 30kHz on 80 / 100MHz bandwidths. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5GHz band, subcarrier spacing can occur at 60kHz over a 160MHz bandwidth. Finally, for various deployments transmitting with the mmWave component at 28GHz TDD, subcarrier spacing can occur at 120kHz over a 500MHz bandwidth.

[0044] 5G NR's scalable parameter sets facilitate scalable TTIs for different latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long TTIs and short TTIs allows transmissions to start on symbol boundaries. 5G NR also contemplates a self-contained integrated subframe design with uplink / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink / downlink, which can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current business needs.

[0045] Various other aspects and features of the present disclosure are further described below. It should be clear that the teachings herein can be implemented in various forms, and any specific structure, function, or both disclosed herein are merely representative and not restrictive. Based on the teachings herein, it should be understood by those of ordinary skill in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice a method. In addition, other structures, functionality, or structures and functionality other than one or more of the aspects set forth herein or different from one or more of the aspects set forth herein can be used to implement this device or practice this method. For example, the method can be implemented as a part of a system, device, device, and / or implemented as instructions stored on a computer-readable medium for execution on a processor or computer. In addition, aspects can include at least one element of a claim.

[0046] Figure 1 1 is a block diagram illustrating a 5G network 100 including various base stations and UEs configured according to various aspects of the present disclosure. The 5G network 100 includes multiple base stations 105 and other network entities. A base station may be a station that communicates with a UE and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each base station 105 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the specific geographic coverage area of ​​a base station and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0047] A base station may provide communication coverage for macro cells or small cells (such as pico cells or femto cells), and / or other types of cells. A macro cell generally covers a relatively large geographic area (e.g., several thousand meters in radius) and may allow unrestricted access by UEs that have a service subscription with a network provider. A small cell (such as a pico cell) will generally cover a relatively small geographic area and may allow unrestricted access by UEs that have a service subscription with a network provider. A small cell (e.g., a femto cell) will also typically cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown in FIG. 1 , base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations that enable one of 3-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 105a-105c utilize their higher-dimensional MIMO capabilities to utilize 3D beamforming in both elevation beamforming and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station that can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0048] The 5G network 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time.

[0049] UE 115 is scattered throughout the wireless network 100, and each UE can be stationary or mobile. UE can also be referred to as a terminal, a mobile station, a subscriber unit, a station, etc. UE can be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc. In one aspect, the UE can be a device including a universal integrated circuit card (UICC). On the other hand, the UE can be a device that does not include a UICC. In some aspects, a UE that does not include a UICC can also be referred to as an Internet of Everything (IoE) or Internet of Things (IoT) device. UE 115a-115d is an example of a mobile smart phone type device that accesses the 5G network 100. UE can also be a machine that is specifically configured for connecting communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. UE 115e-115k is an example of various machines configured for accessing communications of the 5G network 100. The UE may be able to communicate with any type of base station, whether macro base station, small cell, etc. Figure 1 In the present invention, lightning (e.g., communication link) indicates wireless transmission between the UE and a serving base station (which is a base station designated to serve the UE on the downlink and / or uplink), or expected transmission between base stations, and backhaul transmission between base stations.

[0050] In operation at the 5G network 100, base stations 105a-105c use 3D beamforming and collaborative spatial techniques (such as coordinated multi-point (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cell base station 105f. Macro base station 105d also transmits multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber Alerts or Gray Alerts.

[0051] The 5G network 100 also supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices, such as UE 115e, which is a drone. The redundant communication links with UE 115e include from macro base stations 105d and 105e and small cell base station 105f. Other machine-type devices, such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device), can communicate directly with base stations, such as small cell base station 105f and macro base station 105e, through the 5G network 100, or communicate in a multi-hop configuration by communicating with another user device that relays its information to the network, such as UE 115f conveying temperature measurement information to smart meter UE 115g, which is then reported to the network through small cell base station 105f. The 5G network 100 may also provide additional network efficiencies through dynamic, low latency TDD / FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between UEs 115i-115k communicating with a macro base station 105e.

[0052] Figure 2 A block diagram showing a design of a base station 105 and a UE 115 is shown, and the base station 105 and the UE 115 may be Figure 1 One of the base stations and one of the UEs in the base station 105. At the base station 105, the transmit processor 220 can receive data from the data source 212 and control information from the controller / processor 240. The control information can be for PBCH, PCFICH, PHICH, PDCCH, EPDCCH, MPDCCH, etc. The data can be for PDSCH, etc. The transmit processor 220 can process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The transmit processor 220 can also generate reference symbols, such as for PSS, SSS, and cell-specific reference signals. The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide output symbol streams to modulators (MOD) 232a to 232t. Each modulator 232 can process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (eg, convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a through 232t may be transmitted via antennas 234a through 234t, respectively.

[0053] At the UE 115, antennas 252a to 252r may receive downlink signals from the base station 105 and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all demodulators 254a to 254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data to the UE 115 to the data sink 260, and provide decoded control information to the controller / processor 280.

[0054] On the uplink, at the UE 115, a transmit processor 264 may receive and process data (e.g., for the PUSCH) from a data source 262 and control information (e.g., for the PUCCH) from the controller / processor 280. The transmit processor 264 may also generate reference symbols for a reference signal. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. The processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240.

[0055] The controller / processors 240 and 280 may direct the operation at the base station 105 and the UE 115, respectively. The controller / processor 240 and / or other processors and modules at the base station 105 may perform or direct the execution of various processes for the techniques described herein. The controller / processor 280 and / or other processors and modules at the UE 115 may also perform or direct the execution of various processes for the techniques described herein. Figure 8-13 The functional blocks shown in and / or other processes for the techniques described herein may be executed. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

[0056] Wireless communication systems operated by different network operating entities (e.g., network operators) may share spectrum. In some instances, a network operating entity may be configured to use the entire designated shared spectrum for at least one time period before another network operating entity uses the entire designated shared spectrum for a different time period. Thus, to allow network operating entities to use the entire designated shared spectrum and to mitigate interfering communications between different network operating entities, certain resources (e.g., time) may be partitioned and allocated to different network operating entities for certain types of communications.

[0057] For example, a network operating entity may be allocated certain time resources that are reserved for exclusive communication by that network operating entity using the entire shared spectrum. Other time resources may also be allocated to a network operating entity where that entity is given priority over other network operating entities to communicate using the shared spectrum. Those time resources prioritized for use by the network operating entity may be utilized on an opportunistic basis by other network operating entities if the prioritized network operating entity does not utilize the resources. Additional time resources may be allocated to any network operator for use on an opportunistic basis.

[0058] Access to the shared spectrum and arbitration of time resources between different network operating entities may be centrally controlled by a separate entity, autonomously determined by a predefined arbitration scheme, or dynamically determined based on interactions between wireless nodes of the network operator.

[0059] In this case, the 5G network 100 ( Figure 1A UE 115 and a base station 105 (in a shared RF spectrum band) may operate in a shared RF spectrum band that may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared RF spectrum band, the UE 115 or the base station 105 may conventionally perform a media sensing process to compete for access to the spectrum. For example, the UE 115 or the base station 105 may perform a listen-before-talk (LBT) process (such as a clear channel assessment (CCA)) before communicating to determine whether the shared channel is available. CCA may include an energy detection process to determine whether there are any other active transmissions. For example, the device may infer that a change in a received signal strength indicator (RSSI) of a power meter indicates that the channel is occupied. Specifically, a signal power concentrated in a particular bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include detection of a particular sequence that indicates use of a channel. For example, another device may send a particular preamble before sending a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel and / or acknowledgement / negative acknowledgement (ACK / NACK) feedback for its own transmitted packets as a proxy for collisions.

[0060] Generally, four categories of LBT procedures have been proposed for sensing a shared channel to obtain a signal that may indicate that the channel has been occupied. In the first category (CAT 1 LBT), no LBT or CCA is applied to detect occupancy of a shared channel. The second category (CAT 2 LBT) (which may also be referred to as abbreviated LBT, single-shot LBT, or 25-μs LBT) provides for a node to perform CCA to detect energy above a predetermined threshold or to detect a message or preamble occupying a shared channel. CAT 2 LBT performs CCA without using a random backoff operation, which results in its shortened length relative to the next category.

[0061] The third category (CAT 3LBT) performs CCA to detect energy or messages on a shared channel, but also uses random backoffs and fixed contention windows. Therefore, when a node initiates CAT 3LBT, it performs a first CCA to detect occupancy of the shared channel. If the shared channel is idle for the duration of the first CCA, the node can continue to transmit. However, if the first CCA detects a signal occupying the shared channel, the node selects a random backoff based on the fixed contention window size and performs an extended CCA. If the shared channel is detected to be idle during the extended CCA and the random number has been decremented to 0, the node can start transmitting on the shared channel. Otherwise, the node decrements the random number and performs another extended CCA. The node will continue to perform extended CCAs until the random number reaches 0. If the random number reaches 0 and no extended CCA detects channel occupancy, the node can transmit on the shared channel. If at any extended CCA, the node detects channel occupancy, the node can reselect a new random backoff based on the fixed contention window size to start the countdown again.

[0062] The fourth category (CAT 4 LBT) (which may also be referred to as a full LBT process) performs CCA with energy or message detection using random backoff and a variable contention window size. The sequence of CCA detection is performed similarly to the process of CAT 3 LBT, except that the contention window size is variable for the CAT 4 LBT process.

[0063] Using a media sensing process to compete for access to an unlicensed shared spectrum can result in communication inefficiencies. This can be particularly evident when multiple network operating entities (e.g., network operators) are trying to access shared resources. In a 5G network 100, base stations 105 and UEs 115 can be operated by the same or different network operating entities. In some examples, individual base stations 105 or UEs 115 can be operated by more than one network operating entity. In other examples, each base station 105 and UE 115 can be operated by a single network operating entity. Requiring each base station 105 and UE 115 of different network operating entities to compete for shared resources can result in increased signaling overhead and communication latency.

[0064] Figure 3 An example of a timing diagram 300 for coordinated resource partitioning is shown. The timing diagram 300 includes a superframe 305, which may represent a fixed duration (e.g., 20 ms). The superframe 305 may repeat for a given communication session and may be used by a processor such as a reference processor. Figure 1The wireless system of the described 5G network 100 is used. The superframe 305 can be divided into intervals, such as an acquisition interval (A-INT) 310 and an arbitration interval 315. As described in more detail below, the A-INT 310 and the arbitration interval 315 can be subdivided into sub-intervals designated for certain resource types and allocated to different network operating entities to facilitate coordinated communication between different network operating entities. For example, the arbitration interval 315 can be divided into multiple sub-intervals 320. In addition, the superframe 305 can be further divided into multiple subframes 325 with a fixed duration (e.g., 1 ms). Although the timing diagram 300 shows three different network operating entities (e.g., operator A, operator B, operator C), the number of network operating entities using the superframe 305 for coordinated communication can be greater or less than the number shown in the timing diagram 300.

[0065] A-INT 310 can be a dedicated interval of superframe 305, which is reserved for exclusive communication by network operation entities. In some examples, certain resources within A-INT 310 can be allocated to each network operation entity for exclusive communication. For example, resources 330-a can be reserved for exclusive communication of operator A (such as through base station 105a), resources 330-b can be reserved for exclusive communication of operator B (such as through base station 105b), and resources 330-c can be reserved for exclusive communication of operator C (such as through base station 105c). Since resource 330-a is reserved for exclusive communication of operator A, neither operator B nor operator C can communicate during resource 330-a, even if operator A chooses not to communicate during these resources. That is, access to exclusive resources is limited to designated network operators. Similar restrictions apply to resources 330-b for operator B and resources 330-c for operator C. A wireless node of operator A (eg, UE 115 or base station 105) may transmit any information desired, such as control information or data, during its exclusive use of resource 330-a.

[0066] When communicating on exclusive resources, the network operating entity does not need to perform any media sensing procedures (e.g., listen before talk (LBT) or clear channel assessment (CCA)) because the network operating entity knows that the resources are reserved. Because only designated network operating entities can communicate on exclusive resources, the possibility of interfering communications is reduced compared to relying solely on media sensing techniques (e.g., no hidden node problem). In some examples, A-INT 310 is used to send control information, such as synchronization signals (e.g., SYNC signals), system information (e.g., system information blocks (SIBs), paging information (e.g., physical broadcast channel (PBCH) messages), or random access information (e.g., random access channel (RACH) signals). In some examples, all wireless nodes associated with the network operating entity can transmit simultaneously during their exclusive resources.

[0067] In some examples, resources can be classified as being preferentially used for certain network operation entities. Resources assigned with a priority for a certain network operation entity can be referred to as a guaranteed interval (G-INT) for the network operation entity. The interval of resources used by the network operation entity during G-INT can be referred to as a priority sub-interval. For example, resource 335-a can be preferentially used by operator A, and therefore can be referred to as G-INT for operator A (e.g., G-INT-OpA). Similarly, resource 335-b can be preferentially used for operator B (e.g., G-INT-OpB), resource 335-c (e.g., G-INT-OpC) can be preferentially used for operator C, resource 335-d can be preferentially used for operator A, resource 335-e can be preferentially used for operator B, and resource 335-f can be preferentially used for operator C.

[0068] Figure 3 The various G-INT resources shown in the diagram appear to be interleaved to illustrate their association with their respective network operating entities, but these resources may all be on the same frequency bandwidth. Thus, if viewed along the time-frequency grid, the G-INT resources may appear as continuous lines within the superframe 305. This division of data may be an example of time division multiplexing (TDM). Additionally, when resources appear in the same subinterval (e.g., resource 340-a and resource 335-b), these resources represent the same time resources with respect to the superframe 305 (e.g., these resources occupy the same subinterval 320), but these resources are designated separately to illustrate that the same time resources can be classified differently for different operators.

[0069] When resources are preferentially allocated to a certain network operation entity (e.g., G-INT), the network operation entity can use those resources for communication without having to wait for or perform any media sensing process (e.g., LBT or CCA). For example, the wireless node of operator A can freely transmit any data or control information during resource 335-a without interference from the wireless nodes of operator B or operator C.

[0070] The network operating entity may additionally signal another operator that it intends to use a particular G-INT. For example, with reference to resource 335-a, operator A may signal to operator B and operator C that it intends to use resource 335-a. Such signaling may be referred to as an activity indication. In addition, since operator A has a higher priority than resource 335-a, operator A may be considered to be a higher priority operator than both operator B and operator C. However, as discussed above, operator A does not have to signal to other network operating entities to ensure interference-free transmission during resource 335-a because resource 335-a is assigned a priority to operator A.

[0071] Similarly, a network operating entity may signal another network operating entity that it intends not to use a particular G-INT. This signaling may also be referred to as an activity indication. For example, with reference to resource 335-b, operator B may signal to operator A and operator C that it does not intend to use resource 335-b for communication, even if these resources are assigned a priority to operator B. With reference to resource 335-b, operator B may be considered to be a network operating entity with a higher priority than operator A and operator C. In this case, operators A and C will attempt to use the resources of subinterval 320 on an opportunistic basis. Therefore, from the perspective of operator A, a subinterval 320 containing resource 335-b may be considered to be an opportunistic interval (O-INT) for operator A (e.g., O-INT-OpA). In addition, from the perspective of operator C, the same subinterval 320 may represent the O-INT of operator C with corresponding resource 340-b. Resources 340-a, 335-b, and 340-b all represent the same time resource (e.g., a particular subinterval 320), but are individually identified to represent that the same resource may be considered G-INT for some network operating entities and also considered O-INT for other network operating entities.

[0072] In order to utilize resources on an opportunistic basis, Operator A and Operator C may perform a media sensing process to check for communications on a particular channel before sending data. For example, if Operator B decides not to use resources 335-b (e.g., G-INT-OpB), Operator A may use those same resources (e.g., represented by resources 340-a) by first checking the channel for interference (e.g., LBT) and then sending data if the channel is determined to be idle. Similarly, if Operator C wants to access resources on an opportunistic basis during subinterval 320 (e.g., using O-INT represented by resources 340-b) in response to an indication that Operator B will not use its G-INT (e.g., resources 335-b), Operator C may perform a media sensing process and access those resources if available. In some cases, two operators (e.g., Operator A and Operator C) may attempt to access the same resources, in which case the operators may employ a contention-based process to avoid interfering communications. Operators may also have sub-priorities assigned to them that are designed to determine which operator may gain access to a resource if more than one operator is attempting access simultaneously. For example, operator A may have priority over operator C during sub-interval 320 when operator B is not using resource 335-b (e.g., G-INT-OpB). Note that in another sub-interval (not shown), operator C may have priority over operator A when operator B is not using its G-INT.

[0073] In some examples, a network operating entity may intend not to use a particular G-INT allocated to it, but may not send an activity indication conveying an intent not to use the resource. In such a case, for a particular subinterval 320, a lower priority operating entity may be configured to monitor the channel to determine whether a higher priority operating entity is using the resource. If a lower priority operating entity determines, through LBT or a similar method, that a higher priority operating entity will not use its G-INT resources, the lower priority operating entity may attempt to access the resource on an opportunistic basis as described above.

[0074] In some examples, access to G-INT or O-INT may be preceded by a reservation signal (e.g., request to send (RTS) / clear to send (CTS)), and the contention window (CW) may be randomly selected between one and the total number of operating entities.

[0075] In some examples, the operating entity may employ or be compatible with coordinated multi-point (CoMP) communications. For example, the operating entity may employ CoMP and dynamic time division duplexing (TDD) in G-INT as needed, and employ opportunistic CoMP in O-INT.

[0076] exist Figure 3 In the example shown in , each sub-interval 320 includes a G-INT for one of operators A, B, or C. However, in some cases, one or more sub-intervals 320 may include resources that are neither reserved for exclusive use nor reserved for prioritized use (e.g., unallocated resources). Such unallocated resources may be considered O-INT for any network operating entity and may be accessed on an opportunistic basis as described above.

[0077] In some examples, each subframe 325 can contain 14 symbols (e.g., 250-μs for a 60 kHz frequency modulation interval). These subframes 325 can be independent, self-contained interval-Cs (ITCs), or the subframe 325 can be part of a long ITC. An ITC can be a self-contained transmission that starts with a downlink transmission and ends with an uplink transmission. In some examples, an ITC can contain one or more subframes 325 that operate continuously while the medium is occupied. In some cases, assuming a 250-μs transmission opportunity, there can be up to eight network operators in an A-INT 310 (e.g., with a duration of 2 ms).

[0078] Despite Figure 3 Three operators are shown in the figure, but it should be understood that fewer or more network operating entities may be configured to operate in a coordinated manner as described above. In some cases, the location of the G-INT, O-INT, or A-INT within the superframe 305 for each operator is autonomously determined based on the number of network operating entities active in the system. For example, if there is only one network operating entity, each subinterval 320 may be occupied by the G-INT of that single network operating entity, or the subinterval 320 may alternate between G-INT and O-INT for that network operating entity to allow other network operating entities to enter. If there are two network operating entities, the subinterval 320 may alternate between G-INT for the first network operating entity and G-INT for the second network operating entity. If there are three network operating entities, the subinterval 320 may alternate between G-INT for the first network operating entity and G-INT for the second network operating entity. Figure 3, the G-INT and O-INT for each network operation entity are designed as shown in . If there are four network operation entities, the first four sub-intervals 320 may include continuous G-INT for the four network operation entities, and the remaining two sub-intervals 320 may contain O-INT. Similarly, if there are five network operation entities, the first five sub-intervals 320 may include continuous G-INT for the five network operation entities, and the remaining sub-intervals 320 may contain O-INT. If there are six network operation entities, all six sub-intervals 320 may include continuous G-INT for each network operation entity. It should be understood that these examples are for illustrative purposes only, and other autonomously determined interval allocations may be used.

[0079] It should be understood that reference Figure 3 The coordination framework described is for illustration purposes only. For example, the duration of superframe 305 can be greater or less than 20 ms. In addition, the number, duration, and location of subintervals 320 and subframes 325 can be different from the configuration shown. In addition, the type of resource designation (e.g., exclusive, priority, unallocated) can be different or include more or fewer sub-designations.

[0080] Reference Figure 4 , a specific illustrative example of a wireless communication system for performing wireless communication based on a backoff timer is depicted and generally designated as 400. The wireless communication system 400 may include a network device (e.g., a base station 105) and a UE 115. Although not shown for purposes of illustration, Figure 4 Although a single base station 105 and a single UE 115 are shown in FIG. 4 , the wireless communication system 400 may include a different number of base stations 105, a different number of UEs 115, or a combination thereof.

[0081] During operation, the UE 115 may communicate with the base station 105 via one or more wireless communication channels of the wireless communication system 400. For example, the UE 115 may place a call via the base station 105, may communicate with one or more servers (e.g., to access the Internet or another network) via the base station 105, may perform one or more other operations, or a combination thereof. Alternatively or additionally, the base station 105 may push data, notifications, or other information to the UE via one or more wireless communication channels of the wireless communication system 400.

[0082] In this case, the base station 105 or the UE 115 may initiate a data session 418 between the UE 115 and a device (e.g., a server) of the data network. An example of a data session 418 is a protocol data unit (PDU) session (also referred to herein as a packet data unit session). The data network may be associated with or may correspond to a data network name (DNN). In some examples, the base station 105 and the UE 115 perform operations for the data session 418 according to a fifth generation session management (5GSM) communication protocol.

[0083] The base station 105 may be configured to support the data session 418 by allocating a network slice to the UE 115. A network slice may refer to the selection or allocation of network resources. For example, to support the data session 418, the base station 105 may select and allocate a set of network resources of the wireless communication system 400 to the UE 115.

[0084] To further illustrate, UE 115 may send data session establishment request 402 (e.g., PDU session establishment request message) to a base station to establish data session 418. As an illustrative example, UE 115 may send data session establishment request 402 in response to executing some application or program specifying establishment of data session 418.

[0085] In some examples, the data session establishment request 402 indicates a requested network slice 404. For example, the data session establishment request 402 may include a first single network slice selection assistance information (S-NSSAI) 406 indicating the requested network slice 404. In some other examples, the data session establishment request 402 does not indicate any requested network slice. In this case, the data session establishment request 402 may not include the first S-NSSAI 406. For example, the data session establishment request 402 may include a first field that can be used or configured to indicate the requested network slice 404 (e.g., by including the first S-NSSAI 406). In some cases, the UE 115 may omit the first S-NSSAI 406 from the first field (e.g., where the first field is "empty" and does not specify the requested network slice 404).

[0086] The base station 105 may send a data session setup accept message 412 (e.g., a PDU session setup accept message) to the UE 115 indicating the authorized network slice 414 for the data session 418. In some examples, the data session setup accept message includes a second S-NSSAI 416 indicating the authorized network slice 414. The authorized network slice 414 may be different from the requested network slice 404, and the second S-NSSAI 416 may be different from the first S-NSSAI 406.

[0087] The UE 115 and the base station 105 may perform one or more operations associated with the data session 418 based on the authorized network slice 414. For example, the authorized network slice 414 may be associated with one or more quality of service (QoS) parameters, and the operations of the data session 418 may be performed based on the one or more QoS parameters.

[0088] In response to receiving the data session establishment accept message 412, the UE 115 may be configured to store an indication 452 of the requested network slice 404 to a memory of the UE 115, such as Figure 2 Memory 282.

[0089] In some cases, the UE 115 may detect a session event (e.g., a session modification or termination event) associated with the data session 418. The session event may be initiated by the base station 105 or by the UE 115. The session event may be a congestion-based event (e.g., based on the number of UEs 115 accessing resources of the wireless communication system 400).

[0090] To illustrate, in one example, the session event includes receiving a data session release command 422 from the base station 105. In some cases, the base station 105 sends the data session release command 422 to the UE 115 in response to a threshold inactivity period of the data session 418. In this example, the base station 105 can terminate the data session 418 by sending the data session release command 422 to the UE 115.

[0091] In another example, the session event includes sending a data session modification request 428 by the UE 115 to the base station 105. For example, the execution of a certain program or application may specify that the UE 115 will modify (or request modification of) the data session 418. To further illustrate, as an illustrative example, the UE 115 may generate the data session modification request 428 in response to executing a certain program or application that specifies a change in one or more QoS parameters, such as in response to modifying a voice call to a video call. Depending on the specific example, the base station 105 may accept the data session modification request 428 or may reject the data session modification request 428, such as by sending a data session modification rejection message 426 to the UE 115.

[0092] In some cases, the handover event may trigger one or more of the data session release command 422 or the data session modification request 428. For example, a handover from a 4G cell to a 5G cell (or vice versa) may be associated with a change in QoS parameters. As a result, in some cases, the base station 105 may terminate the data session 418 by sending the data session release command 422, or the UE 115 may request to modify the data session 418 by sending the data session modification request 428.

[0093] The base station 105 is configured to indicate the back-off timer value 424 to the UE 115. For example, the base station 105 can detect a network congestion event associated with the wireless communication system 400, and can send the back-off timer value 424 to the UE 115 in response to detecting the network congestion event. To further illustrate, in one example, the data session release command 422 indicates the back-off timer value 424. In another example, the data session modification reject message 426 indicates the back-off timer value 424.

[0094] UE 115 is configured to initiate operation of a back-off timer 454 of UE 115 in response to receiving an indication of the back-off timer value 424. For example, UE 115 may reset the value 456 of the back-off timer 454. In some examples, operating the back-off timer 454 includes initializing the value 456 to zero (or another number) and counting up to the back-off timer value 424. In this case, the back-off timer 454 may expire when the value 456 reaches the back-off timer value 424. In some other examples, operating the back-off timer 454 includes initializing the value 456 to the back-off timer value 424 and counting down to zero (or another number). In this case, the back-off timer 454 may expire when the value 456 reaches zero (or another number).

[0095] In some examples, UE 115 is configured to delay sending one or more messages associated with requested network slice 404 or granted network slice 414 during a time interval that begins when operation of backoff timer 454 is initiated and ends when backoff timer 454 expires. In some examples, delaying sending one or more messages can reduce network congestion at wireless communication system 400.

[0096] To further illustrate, the UE 115 may store a message 458 associated with the requested network slice 404 or the granted network slice 414 during operation of the backoff timer 454. For example, the message 458 may correspond to one or more messages stored at a queue, buffer, or cache of the UE 115. Figure 4 In the example, message 458 includes a first message 460 associated with the authorized network slice 414.

[0097] Figure 4It is also shown that the message 458 may include a second message 462 associated with the requested network slice 404. The second message 462 may have a second field that corresponds to (e.g., matches) the first field of the data session establishment request 402. For example, if the first field indicates the requested network slice 404, then the second field matches the first field if the second field also indicates the requested network slice 404. As another example, if the first field fails to indicate the requested network slice 404 (e.g., where the first field is "null"), then the second field matches the first field if the second field also fails to indicate the requested network slice 404 (e.g., where the second field is "null").

[0098] Message 458 may include or correspond to messages (e.g., requests) to be avoided during the operation of backoff timer 454. For example, message 458 may include a 5GSM request associated with a network slice for data session 418, and the 5GSM communication protocol may specify that UE 115 is to avoid sending requests associated with the network slice for data session 418 during the operation of backoff timer 454. In some aspects of the present disclosure, both requested network slice 404 and granted network slice 414 may be considered network slices for data session 418.

[0099] In some examples, UE 115 is configured to present the message during a delay period associated with message 458. For example, a user may initiate an operation associated with message 458, such as by loading an application to use requested network slice 404 or authorized network slice 414. In this case, in response to determining that the user-initiated operation is subject to operation of backoff timer 454, UE 115 may present a notification alerting the user that the user-initiated operation is subject to operation of backoff timer 454. In some cases, the notification may indicate a time until the operation can be completed (e.g., by indicating a value 456 of backoff timer 454). Thus, the user may be alerted more quickly than certain conventional techniques of attempting to perform an operation (e.g., by sending message 458) and then waiting until the operation fails or "times out" (e.g., due to a failure to receive a response to message 458).

[0100] In response to the expiration of the back-off timer 454, the UE 115 may send a message 458 to the base station 105. For example, upon detecting that the value 456 reaches the back-off timer value 424 (or another number), the UE 115 may send the message 458 to the base station 105 (e.g., by flushing a queue, buffer, or cache storing the message 458). The UE 115 may be configured to terminate the operation of the back-off timer 454 in response to detecting the expiration of the back-off timer 454.

[0101] In one example, UE 115 includes a control circuit coupled to backoff timer 454 and a memory (e.g., a queue, a buffer, or a cache) configured to store message 458. The control circuit can be configured to provide a control signal to the memory. During operation of backoff timer 454, the control signal can have a first value (e.g., a logical "0" value or a logical "1" value). The memory can be configured to suppress outputting message 458 based on the first value of the control signal. When backoff timer 454 expires, the control circuit can change the control signal from the first value to a second value (e.g., a logical "1" value or a logical "0" value). The memory can be configured to output message 458 in response to the second value of the control signal.

[0102] Although certain examples have been described with reference to storing the messages 458 at a memory (e.g., a queue, a buffer, or a cache), other implementations are also within the scope of the present disclosure. In some examples, one or more of the messages 458 can be generated after checking the backoff timer 454 (e.g., by generating one or more of the messages 458 "just in time"). For example, before generating one or more of the messages 458, an application or application layer associated with the data session 418 may issue a request for data transfer using the data session 418. In response to the request, the UE 115 may perform a check on the backoff timer 454 (e.g., to determine whether the request is subject to the backoff timer 454). In response to the check indicating that the backoff timer 454 is running, the UE 115 may provide an indication to the application (or application layer) that the request is denied. The indication may include the value 456 of the backoff timer 454. In this case, the application or application layer may repeat the request at a later time (e.g., upon expiration of the backoff timer 454). Alternatively, if the check indicates that backoff timer 454 is not running, the application or application layer may generate (e.g., assemble) one or more of messages 458 based on the request, and UE 115 may send one or more messages 458 to base station 105.

[0103] In some examples, UE 115 is configured to access indication 452 stored at memory 282 to determine that operation of backoff timer 454 applies to the requested network slice 404. For example, UE 115 can be configured to check the network slice indicated by the message in message 458 to determine whether the transmission of the message should be delayed until the backoff timer 454 expires.

[0104] In some examples, backoff timer value 424 may be selected from a range of values ​​that may include a zero value. In some examples, UE 115 is configured to detect that backoff timer value 424 is greater than zero and initiate operation of backoff timer 454 in response to detecting that backoff timer value 424 is greater than zero. Alternatively, in some other examples, UE 115 may be configured to avoid initiating operation of backoff timer 454 in response to detecting that backoff timer value 424 corresponds to zero.

[0105] In some examples, one or both of the data session release command 422 or the data session modification rejection message includes a reason value 430 indicating a first type of backoff timer value 424 or a second type of backoff timer value. The first type may indicate that the backoff timer value 424 is associated with a network slice. In this example, the UE 115 may delay sending a message associated with the requested network slice 404, and may further delay sending a message associated with the authorized network slice 414 during the operation of the backoff timer 454. The second type may indicate that the backoff timer value 424 is associated with a network slice and a DNN. In this example, the UE 115 may delay sending a message associated with the network slice, and may further delay sending a message associated with the DNN of the data session 418 during the operation of the backoff timer 454. To further illustrate, in response to the first type of indication, the backoff timer 454 may correspond to a timer T3485 specified by a third generation partnership project (3GPP) communication protocol, and in response to the second type of indication, the backoff timer 454 may correspond to a timer T3484 specified by a 3GPP communication protocol.

[0106] Reference Figure 5 , another example of a wireless communication system is depicted and generally designated 500. Figure 5 In the wireless communication system 500, certain operations may generally be performed as described with reference to Figure 4 The wireless communication system 400 is described in detail. Figure 5 4, data session establishment request 402 indicates a requested DNN 504 for data session 418. In an alternative example, data session establishment request 402 does not indicate any DNN.

[0107] In addition, Figure 5 In the data session establishment accept message 412, the authorized DNN 508 is indicated for the data session 418. The authorized DNN 508 may be different from the requested DNN 504. Figure 5 In the example of , the data session establishment request 402 includes a first DNN field 502 indicating a requested DNN 504, and the data session establishment acceptance message 412 includes a second DNN field 506 indicating an authorized DNN 508.

[0108] exist Figure 5 In the example of , the operation of the backoff timer 454 can be associated with the requested DNN 504 and the authorized DNN 508. The UE 115 can be configured to delay sending a message 558 associated with the requested DNN 504, the authorized DNN 508, or both until the backoff timer 454 expires (e.g., during a time interval that begins when the operation of the backoff timer 454 is initiated and ends when the backoff timer 454 expires). For example, the message 558 can include a first message 560 associated with the requested DNN 504.

[0109] Figure 5 It is also shown that the message 558 may include a second message 562 associated with the requested DNN 504. The second message 562 may have a second field that corresponds to (e.g., matches) the first field (e.g., the first DNN field 502) of the data session establishment request 402. For example, if the first field indicates the requested DNN 504, then the second field matches the first field if the second field also indicates the requested DNN 504. As another example, if the first field fails to indicate the requested DNN 504 (e.g., where the first field is "null"), then the second field matches the first field if the second field also fails to indicate the requested DNN 504 (e.g., where the second field is "null").

[0110] Message 558 may include or correspond to a message (e.g., a request) to be avoided during the operation of backoff timer 454. For example, message 558 may include a 5GSM request associated with a DNN for data session 418, and the 5GSM communication protocol may specify that UE 115 is to avoid sending requests associated with a DNN for data session 418 during the operation of backoff timer 454. In some aspects of the present disclosure, both requested DNN 504 and granted DNN 508 may be considered to be a DNN for data session 418.

[0111] In some examples, UE 115 is configured to present the message during a delay period associated with message 558. For example, a user may initiate an operation associated with message 558, such as by loading an application to use the requested DNN 504 or the authorized DNN 508. In this case, in response to determining that the user-initiated operation is subject to operation of backoff timer 454, UE 115 may present a notification alerting the user that the user-initiated operation is subject to operation of backoff timer 454. In some cases, the notification may indicate a time until the operation can be completed (e.g., by indicating a value 456 of backoff timer 454). Thus, the user may be alerted more quickly than certain conventional techniques of attempting to perform an operation (e.g., by sending message 558) and then waiting until the operation fails or "times out" (e.g., due to a failure to receive a response to message 558).

[0112] Although certain examples have been described with reference to storing the messages 558 at a memory (e.g., a queue, a buffer, or a cache), other implementations are also within the scope of the present disclosure. In some examples, one or more of the messages 558 can be generated after checking the backoff timer 454 (e.g., by generating one or more of the messages 558 "just in time"). For example, before generating one or more of the messages 558, an application or application layer associated with the data session 418 may issue a request for data transfer using the data session 418. In response to the request, the UE 115 may perform a check on the backoff timer 454 (e.g., to determine whether the request is subject to the backoff timer 454). In response to the check indicating that the backoff timer 454 is running, the UE 115 may provide an indication to the application (or application layer) that the request is denied. The indication may include the value 456 of the backoff timer 454. In this case, the application or application layer may repeat the request at a later time (e.g., upon expiration of the backoff timer 454). Alternatively, if the check indicates that the backoff timer 454 is not running, the application or application layer may generate (e.g., assemble) one or more of the messages 558 based on the request, and the UE 115 may send the one or more messages 558 to the base station 105.

[0113] In some examples, the UE 115 is configured to store an indication 552 of the requested DNN 504 at the memory 282. The UE 115 can be configured to access the indication 552 to determine that the operation of the backoff timer 454 applies to the requested DNN 504.

[0114] In some examples, one or both of the data session release command 422 or the data session modification rejection message includes a reason value 530 indicating a first type of backoff timer value 424 or a second type of backoff timer value. The first type may indicate that the backoff timer value 424 is associated with the DNN. In this example, the UE 115 may delay sending messages associated with the requested DNN 504, and may further delay sending messages associated with the authorized DNN 508 during the operation of the backoff timer 454. The second type may indicate that the backoff timer value 424 is associated with a network slice and a DNN. In this example, the UE 115 may delay sending messages associated with one or more network slices (e.g., the requested network slice 404 and the authorized network slice 414) of the data session 418, and may further delay sending messages associated with the requested DNN 504 and the authorized DNN 508 during the operation of the backoff timer 454. To further illustrate, in response to the first type of indication, the back-off timer 454 may correspond to timer T3396 specified by the 3GPP communication protocol, and in response to the second type of indication, the back-off timer 454 may correspond to timer T3484 specified by the 3GPP communication protocol.

[0115] Figure 6 An illustrative example of a congestion notification message 600 is shown. In one example, the congestion notification message 600 corresponds to a fifth generation session management (5GSM) congestion retry information element (IE). The base station 105 may be configured to send the congestion notification message 600 to the UE 115. For example, in some implementations, the base station 105 is configured to include the congestion notification message 600 in the data session release command 422, in the data session modification reject message 426, or in both.

[0116] The congestion notification message 600 may include a type field 601, a length field 602, and a plurality of bits 603. In one example, the type field 601 indicates that the congestion notification message 600 is a 5GSM congestion retry IE. In one example, the length field indicates the length of the congestion notification message 600. In some examples, the type field 601, the length field 602, and the plurality of bits 603 each include eight bits (e.g., Figure 6 The corresponding bit octet of bits 1, 2, 3, 4, 5, 6, 7 and 8) shown in the example of .

[0117] In some examples, a first bit (e.g., bit 1) in the plurality of bits 603 is associated with the backoff timer 454. For example, the first bit in the plurality of bits 603 may have a first value (e.g., a logical "0" value) or a second value (e.g., a logical "1" value). The first value may indicate that the backoff timer value 424 applies to a public land mobile network (PLMN) registered to the UE 115 (e.g., a registered PLMN). The second value may indicate that the backoff timer value applies to multiple PLMNs.

[0118] According to some aspects of the present disclosure, one or more of the plurality of bits 603 are used to indicate a network slice indication message 610. The network slice indication message 610 may indicate one or more network slices associated (or not associated) with the operation of the backoff timer 454, such as one or both of the requested network slice 404 or the authorized network slice 414.

[0119] To illustrate, in a first example, a second bit (e.g., bit 2) in the plurality of bits 603 has a first value or a second value. The first value may indicate that the backoff timer value 424 applies to the requested network slice 404, and the second value may indicate that the backoff timer value applies to the authorized network slice 414. Table 1 shows certain illustrative aspects of the first example:

[0120] Table 1

[0121]

[0122] In the second example, the second bit has a first value indicating that the backoff timer value 424 is not applicable to the requested network slice 404 or a second value indicating that the backoff timer value is applicable to the requested network slice 404. In the second example, the third bit (e.g., bit 3) in the plurality of bits 603 has a first value indicating that the backoff timer value 424 is not applicable to the authorized network slice 414 or a second value indicating that the backoff timer value 424 is applicable to the authorized network slice 414. For further explanation, Table 2 shows certain illustrative aspects of the second example:

[0123] Table 2

[0124]

[0125] In a third example, the plurality of bits 603 have a first set of values ​​indicating that the backoff timer value 424 is applicable to the requested network slice 404, a second set of values ​​indicating that the backoff timer value 424 is applicable to the authorized network slice 414, or a third set of values ​​indicating that the backoff timer value 424 is applicable to both the requested network slice 404 and the authorized network slice 414. For further explanation, Table 3A shows certain illustrative aspects of the third example:

[0126] Table 3A

[0127]

[0128] In an alternative implementation of the third example, the plurality of bits 603 has a set of values ​​selected from Table 3B:

[0129] Table 3B

[0130]

[0131] In the example of Table 3B, the first value set may indicate an implementation-specific association of the back-off timer 454. For example, "no information" may indicate that the UE 115 is allowed to associate the operation of the back-off timer 454 with a certain network slice selected (e.g., "preferred") by the UE 115.

[0132] In some examples, an implementation according to Table 3B is used in conjunction with a wireless communication protocol having multiple versions. A first version (e.g., a less recent version) of the wireless communication protocol may specify that the second bit and the third bit are to be set to zero, and a second version (e.g., a more recent version) may indicate that the second bit and the third bit may both be set to zero or one. As a result, in some examples, an implementation according to Table 3B may be compatible with a device that operates based on the first version and expects to receive zero values ​​for the second bit and the third bit (and may not "understand" a value for the second bit and the third bit).

[0133] Figure 7 Another illustrative example of a congestion notification message 700 is depicted. In one example, the congestion notification message 700 corresponds to a 5GSM congestion retry IE. The base station 105 may be configured to send the congestion notification message 600 to the UE 115. For example, in some implementations, the base station 105 is configured to include the congestion notification message 600 in the data session release command 422, in the data session modification reject message 426, or in both. Figure 7 One or more aspects of the congestion notification message 700 may correspond to Figure 6 Congestion notification message 600.

[0134] exist Figure 7 In the example of , one or more bits of the plurality of bits 603 indicate a DNN indication message 710. According to some aspects of the present disclosure, the DNN indication message 710 indicates one or more DNNs associated (or not associated) with the operation of the backoff timer 454, such as one or both of the requested DNN 504 or the authorized DNN 508.

[0135] To illustrate, in a first example, a second bit (e.g., bit 2) in the plurality of bits 603 has a first value or a second value. The first value may indicate that the backoff timer value 424 applies to the requesting DNN 504, and the second value may indicate that the backoff timer value applies to the granting DNN 508. Table 4 shows certain illustrative aspects of the first example:

[0136] Table 4

[0137]

[0138] In the second example, the second bit has a first value indicating that the backoff timer value 424 is not applicable to the requested DNN 504 or a second value indicating that the backoff timer value is applicable to the requested DNN 504. In the second example, a third bit (e.g., bit 3) in the plurality of bits 603 has a first value indicating that the backoff timer value 424 is not applicable to the authorized DNN 508 or a second value indicating that the backoff timer value 424 is applicable to the authorized DNN 508. For further explanation, Table 5 shows certain illustrative aspects of the second example:

[0139] Table 5

[0140]

[0141] In a third example, the plurality of bits 603 has a first set of values ​​indicating that the backoff timer value 424 is applicable to the requested DNN 504, a second set of values ​​indicating that the backoff timer value 424 is applicable to the authorized DNN 508, or a third set of values ​​indicating that the backoff timer value 424 is applicable to both the requested DNN 504 and the authorized DNN 508. For further explanation, Table 6 shows certain illustrative aspects of the third example:

[0142] Table 6

[0143]

[0144] In some implementations, a network entity (e.g., a base station 105 or other device) may dynamically select one or more techniques described herein based on one or more criteria. In some deployments, in conjunction with a first wireless communication protocol that does not allow a network slice (or DNN) to be changed during a data session, Figure 4 or Figure 5 In some other deployments, in combination with a second wireless communication protocol that allows changing network slices (or DNNs) during a data session, the network entity may select operation based on the first technology in response to detecting a threshold number of UEs 115 communicating using the first wireless communication protocol. Figure 6 or Figure 7 A second technique (eg, an "explicit" technique) may be more advantageous. In this case, the network entity may select the second technique in response to detecting a threshold number of UEs communicating using the second wireless communication protocol.

[0145] Alternatively or additionally, in some implementations, the network entity may select the first technique or the second technique based at least in part on the number of default session management functions (SMFs) of the network that handle requests that do not specify a network slice (or DNN). For example, in a situation where there is a larger number of SMFs in the network, blocking requests that do not specify a network slice (or DNN) may be unnecessary, which may in some cases make operation according to the second technique more advantageous than operation according to the first technique. As a result, the network entity may be configured to select operation according to the first technique in response to detecting that the number of default SMFs in the network fails to meet (e.g., is less than) a threshold, and to select operation according to the second technique in response to detecting that the number of default SMFs in the network meets (e.g., is greater than or equal to) a threshold.

[0146] By following Figure 4-7 One or more aspects of determining or indicating one or more network slices or DNNs can improve network resource allocation. For example, Figure 4-7 One or more aspects of can reduce or avoid situations in which UE 115 avoids sending a message (despite being eligible to send a message). As another example, Figure 4-7 One or more aspects of can reduce or avoid situations where a device sends messages associated with a network slice or DNN despite being ineligible to do so (e.g., before backoff timer 454 expires).

[0147] In addition, in some cases, Figure 4-7 In some aspects of the present invention, the UE 115 may determine or indicate one or more network slices or DNNs to improve the user experience. To illustrate, a user may initiate an operation that is subject to the backoff timer 454. In this case, in response to determining that the user-initiated operation is subject to the operation of the backoff timer 454, the UE 115 may present a notification alerting the user that the operation is subject to the operation of the backoff timer 454. In some cases, the notification may indicate the time until the operation can be completed (e.g., by indicating the value 456 of the backoff timer 454). As a result, the user may be alerted more quickly than certain conventional techniques of attempting to perform an operation and then waiting until the operation fails or "times out" (e.g., due to failure to receive a response to a message indicating a network slice that is subject to the backoff timer 454).

[0148] Reference Figure 8, an illustrative example of a method of operation of a UE is depicted and generally designated as 800. In some examples, method 800 is performed by UE 115 according to reference Figure 4 One or more aspects of the description may be performed.

[0149] The method 800 includes, at 802, sending, by a UE device, a data session establishment request to a network device to establish a data session with the network device using a wireless communication network. The data session establishment request has a first field that can be used to indicate a requested network slice for the data session. For example, the UE 115 can send a data session establishment request 402 to the base station 105 to establish a data session 418. The data session establishment request 402 has a first field that can be used to indicate a requested network slice 404.

[0150] The method 800 also includes receiving, at the UE device, from a network device, an indication of an authorized network slice for the data session, at 804. For example, the UE 115 may receive a data session establishment accept message 412 from the base station 105. In other examples, the UE 115 may receive another message to change the network slice for the data session 418.

[0151] The method 800 also includes receiving, at the UE apparatus, an indication of a backoff timer value from the network device, at 806. As illustrative examples, the UE 115 may receive the indication of the backoff timer value 424 via the data session release command 422 or via the data session modification reject message 426.

[0152] The method 800 also includes, at 808, during operation of the backoff timer based on the backoff timer value, refraining from sending a first message associated with the authorized network slice, and refraining from sending a second message having a second field corresponding to the first field of the data session establishment request. For example, the UE 115 may initialize a value 456 of the backoff timer 454 based on the backoff timer value 424 (e.g., by starting to count down from or to the backoff timer value 424 using the backoff timer 454). During operation of the backoff timer 454, the UE 115 may refrain from sending the first message 460 (e.g., in response to detecting that the first message 460 indicates the authorized network slice 414), and may refrain from sending the second message 462 (e.g., in response to detecting that the second field of the second message 462 matches the first field of the data session establishment request 402).

[0153] The method 800 may further include, at 810, in response to the backoff timer expiring, sending the first message and the second message by the UE device to the network device. For example, the UE 115 may send the first message 460 and the second message 462 to the base station 105 upon the backoff timer 454 expiring.

[0154] Reference Fig. 9 , an illustrative example of a method of operation of a UE is depicted and generally designated as 800. In some examples, method 900 is performed by UE 115 according to reference Figure 5 One or more aspects of the description may be performed.

[0155] The method 900 includes, at 902, sending, by the UE device, a data session establishment request to a network device to establish a data session with the network device using a wireless communication network. The data session establishment request has a first field that can be used to indicate a DNN of the request for the data session. For example, the UE 115 can send the data session establishment request 402 to the base station 105 to establish the data session 418. The data session establishment request 402 has a first field (e.g., the first DNN field 502) that can be used to indicate the requested DNN 504.

[0156] The method 900 also includes receiving, at the UE device, from the network device, an indication of an authorized DNN for the data session, at 904. For example, the UE 115 may receive a data session setup accept message 412 from the base station 105. In other examples, the UE 115 may receive another message to change the DNN for the data session 418.

[0157] The method 900 also includes receiving, at the UE device, an indication of a backoff timer value from the network equipment, at 906. As illustrative examples, the UE 115 may receive the indication of the backoff timer value 424 via the data session release command 422 or via the data session modification reject message 426.

[0158] The method 900 also includes, at 908, during operation of the backoff timer based on the backoff timer value, refraining from sending a first message associated with the authorized DNN and refraining from sending a second message having a second field corresponding to the first field of the data session establishment request. For example, the UE 115 may initialize a value 456 of the backoff timer 454 based on the backoff timer value 424 (e.g., by starting to count down from or to the backoff timer value 424 using the backoff timer 454). During operation of the backoff timer 454, the UE 115 may refrain from sending the first message 560 (e.g., in response to detecting that the first message 560 indicates the authorized DNN 508), and may refrain from sending the second message 562 (e.g., in response to detecting that the second field of the second message 562 matches the first field of the data session establishment request 402).

[0159] The method 900 may also include: at 910, in response to the backoff timer expiring, the UE device sends the first message and the second message to the network device. For example, the UE 115 may send the first message 560 or the second message 562 to the base station 105 when the backoff timer 454 expires.

[0160] Reference Fig.10 , an illustrative example of a method of operation of a UE is depicted and generally designated 1000. In some examples, method 1000 is performed by UE 115 according to reference Figure 6 One or more aspects described (such as any of the examples described with reference to Tables 1, 2, 3A, or 3B) may be performed.

[0161] The method 1000 includes, at 1002, sending a data session establishment request by the UE device to a network device to establish a data session with the network device using a wireless communication network. For example, the UE 115 may send the data session establishment request 402 to the base station 105 to establish the data session 418.

[0162] The method 1000 also includes receiving, at the UE device, from a network device, an indication of an authorized network slice for the data session, at 1004. For example, the UE 115 may receive a data session setup accept message 412 from the base station 105. In other examples, the UE 115 may receive another message to change the network slice for the data session 418.

[0163] The method 1000 also includes, at 1006, receiving, at the UE device, from the network device, a congestion notification message indicating one or more network slices associated with the backoff timer value. The one or more network slices indicate one or both of an authorized network slice or a requested network slice specified by the UE device. The congestion notification message may correspond to Figure 6 The congestion notification message 600 may indicate the requested network slice 404, the authorized network slice 414, or both. As illustrative examples, the UE 115 may receive an indication of the backoff timer value 424 via a data session release command 422 or via a data session modification reject message 426.

[0164] The method 1000 also includes initiating operation of a backoff timer of the UE device based on the backoff timer value, at 1008. For example, the UE 115 may initialize a value 456 of the backoff timer 454 based on the backoff timer value 424 (e.g., by starting to count down from or to the backoff timer value 424 using the backoff timer 454).

[0165] The method 1000 also includes, at 1010, in response to the expiration of the backoff timer, sending, by the UE device, a message associated with at least one of the one or more network slices to the network device. For example, the UE 115 may send the first message 460 or the second message 462 to the base station 105 when the backoff timer 454 expires.

[0166] Reference Fig.11 , an illustrative example of a method of operation of a UE is depicted and generally designated as 1100. In some examples, method 1100 is performed by UE 115 according to reference Figure 7 One or more aspects described (such as any of the examples described with reference to Tables 4, 5, or 6) may be performed.

[0167] The method 1100 includes, at 1102, sending a data session establishment request by the UE device to a network device to establish a data session with the network device using a wireless communication network. For example, the UE 115 may send a data session establishment request 402 to the base station 105 to establish a data session 418.

[0168] The method 1100 also includes receiving, at the UE device, from the network device, an indication of an authorized DNN for the data session, at 1104. For example, the UE 115 may receive a data session setup accept message 412 from the base station 105. In other examples, the UE 115 may receive another message to change the DNN for the data session 418.

[0169] The method 1100 also includes, at 1106, receiving, at the UE device, a congestion notification message from the network device indicating one or more DNNs associated with the backoff timer value. The one or more DNNs indicate one or both of an authorized DNN or a requested DNN specified by the UE device. The congestion notification message may correspond to Figure 7 The congestion notification message 700 may indicate the requested DNN 504, the authorized DNN 508, or both. As illustrative examples, the UE 115 may receive an indication of the backoff timer value 424 via the data session release command 422 or via the data session modification reject message 426.

[0170] The method 1100 also includes initiating operation of a backoff timer of the UE device based on the backoff timer value at 1108. For example, the UE 115 may initialize a value 456 of the backoff timer 454 based on the backoff timer value 424 (e.g., by starting to count down from or to the backoff timer value 424 using the backoff timer 454).

[0171] The method 1100 also includes, at 1110, in response to the expiration of the backoff timer, sending, by the UE device, a message associated with at least one of the one or more DNNs to the network device. For example, the UE 115 may send the first message 560 or the second message 562 to the base station 105 when the backoff timer 454 expires.

[0172] refer to Fig.12 , depicts an illustrative example of a method of operation of a network device, and is generally designated 1200. In some examples, the method 1200 is performed by the base station 105 according to the reference Figure 6 One or more aspects described (such as any of the examples described with reference to Tables 1, 2, 3A, or 3B) may be performed.

[0173] The method 1200 includes, at 1202, receiving, by the network device, a data session establishment request from a UE device to establish a data session with the network device using a wireless communication network. For example, the base station 105 may receive the data session establishment request 402 from the UE 115.

[0174] The method 1200 also includes sending an indication of an authorized network slice for the data session from the network device to the UE device at 1204. For example, the base station 105 may send a data session establishment accept message 412 to the UE 115. In other examples, the UE 115 may receive another message to change the network slice for the data session 418.

[0175] The method 1200 also includes, at 1206, sending a congestion notification message from the network device to the UE device indicating one or more network slices associated with the backoff timer value. The one or more network slices indicate one or both of an authorized network slice or a requested network slice specified by the UE device. The congestion notification message may correspond to Figure 6 The congestion notification message 600 may indicate the requested network slice 404, the authorized network slice 414, or both.

[0176] The method 1200 also includes receiving, at the network device, a message associated with at least one of the one or more network slices from the UE device in response to expiration of a backoff timer based on the backoff timer value, at 1208. For example, the base station 105 may receive the first message 460 or the second message 462 from the UE 115 upon expiration of the backoff timer 454. The backoff timer 454 expires based on the backoff timer value 424.

[0177] refer to Fig.13 , depicts an illustrative example of a method of operation of a network device and is generally identified as 1300. In some examples, the method 1300 is performed by the base station 105 according to the reference Figure 7One or more aspects described (such as any of the examples described with reference to Tables 4, 5, or 6) may be performed.

[0178] The method 1300 includes receiving, by the network device, a data session establishment request from a UE device to establish a data session with the network device using a wireless communication network, at 1302. For example, the base station 105 may receive the data session establishment request 402 from the UE 115.

[0179] The method 1300 also includes sending an indication of an authorized DNN for the data session from the network device to the UE apparatus at 1304. For example, the base station 105 may send a data session establishment accept message 412 to the UE 115. In other examples, the UE 115 may receive another message that changes the DNN for the data session 418.

[0180] The method 1300 also includes, at 1306, sending a congestion notification message from the network device to the UE device indicating one or more DNNs associated with the backoff timer value. The one or more DNNs indicate one or both of an authorized DNN or a requested DNN specified by the UE device. The congestion notification message may correspond to Figure 7 The congestion notification message 700 may indicate the requesting DNN 504, the authorized DNN 508, or both.

[0181] The method 1300 also includes receiving, at the network device, a message associated with at least one of the one or more DNNs from the UE device in response to the backoff timer expiring based on the backoff timer value, at 1308. For example, the base station 105 may receive the first message 560 or the second message 562 from the UE 115 upon expiration of the backoff timer 454. The backoff timer 454 expires based on the backoff timer value 424.

[0182] Fig.14 1 is a block diagram illustrating a UE 115 configured according to one aspect of the present disclosure. The UE 115 includes Figure 2 1. The UE 115 of the present invention may be a wireless communication device, such as a wireless communication device, a wireless communication device, or a wireless communication device. For example, the UE 115 may include a controller / processor 280 that operates to execute logic or computer instructions stored in a memory 282 and to control components of the UE 115 that provide the features and functions of the UE 115. Under the control of the controller / processor 280, the UE 115 transmits and receives signals via wireless radios 1401a-r and antennas 252a-r. The wireless radios 1401a-r include various components and hardware, such as Figure 2 As shown for UE 115, modulators / demodulators 254a-r, MIMO detector 256, receive processor 258, transmit processor 264, and TX MIMO processor 266 are included.

[0183] The memory 282 is configured to store instructions, data, or other information to implement wireless communications based on the backoff timer 454. For example, the memory 282 may store delay logic 1402, which may be executed by the controller / processor 280 to cause the controller / processor 280 to delay sending the message 458 until the backoff timer 454 expires. The memory 282 may further store comparison logic 1404, which may be executed by the controller / processor 280 to cause the controller / processor 280 to compare the value 456 to the backoff timer value 424 to detect the expiration of the backoff timer 454. The memory 282 may also store message transmission logic 1406, which may be executed by the controller / processor 280 to initiate the transmission of the message 458 to the base station 105. Alternatively or additionally, delay logic 1402 may be executed by the controller / processor 280 to cause the controller / processor 280 to delay sending the message 558 until the backoff timer 454 expires, and message sending logic 1406 may be executed by the controller / processor 280 to initiate sending the message 558 to the base station 105.

[0184] Fig.15 1 is a block diagram illustrating a base station 105 configured according to one aspect of the present disclosure. The base station 105 includes Figure 2 1. The base station 105 of FIG. 105 is a schematic diagram of the structure, hardware, and components of the base station 105 shown in FIG. 105. For example, the base station 105 includes a controller / processor 240 that operates to execute logic or computer instructions stored in a memory 242 and controls the components of the base station 105 that provide the features and functions of the base station 105. Under the control of the controller / processor 240, the base station 105 transmits and receives signals via wireless radios 1401a-t and antennas 234a-t. The wireless radios 1401a-t include various components and hardware, such as Figure 2 As shown for base station 105, modulators / demodulators 232a-t, MIMO detector 236, receive processor 238, transmit processor 220, and TX MIMO processor 230 are included.

[0185] The memory 242 is configured to store instructions, data, or other information that implement communications based on the backoff timer value 424. For example, the memory 242 may store network congestion logic 1502 that may be executed by the controller / processor 240 to determine whether or not a wireless communication system (such as a wireless communication system) is connected to the network. Figure 4 A wireless communication system 400 or Figure 5As another example, the memory 242 may store backoff timer value selection logic 1504 that may be executed by the controller / processor 240 to determine the backoff timer value 424 (e.g., based on the amount or type of network congestion). Additionally, in some examples, the memory 242 may store data or instructions representing one or more aspects of any of Tables 1-6.

[0186] To further illustrate certain aspects of the present disclosure, Table 7 depicts content that may be indicated by an example of an uplink (UL) non-access stratum (NAS) transport message. In some examples, the NAS transport message corresponds to or includes a data session establishment request 402. For illustration, the information element "Payload container" of Table 7 may correspond to the data session establishment request 402. In some examples, the information element identifier (IEI) 22 of Table 7 corresponds to the requested network slice 404. Alternatively or additionally, the IEI 25 of Table 7 may correspond to the requested DNN 504.

[0187] Table 7

[0188]

[0189]

[0190] Table 8 depicts content that may be indicated by an example of a PDU session setup accept message. In one example, the PDU session setup accept message corresponds to the data session setup accept message 412. In one example, IEI 22 of Table 8 may correspond to the authorized network slice 414. Alternatively or additionally, IEI 25 of Table 8 may correspond to the authorized DNN 508.

[0191] Table 8

[0192]

[0193]

[0194] Table 9 depicts some of the content that may be indicated by an example of a PDU session release command. In one example, the PDU session release command message corresponds to a data session release command 422. In Table 9, IEI 37 may correspond to a backoff timer value 424, and IE "5GSM cause" may correspond to a cause value 430.

[0195] Table 9

[0196]

[0197] Table 10 depicts some of the content that may be indicated by an example of a PDU session modification reject message. In one example, the PDU session modification reject message corresponds to the data session modification reject message 426. In Table 9, IEI 37 may correspond to the backoff timer value 424, and IE "5GSM cause" may correspond to the cause value 430.

[0198] Table 10

[0199]

[0200] In a first aspect, an apparatus for wireless communication includes a memory and a processor coupled to the memory. The processor is configured to send a data session establishment request to establish a data session with a network device using a wireless communication network. The data session establishment request has a first field indicating a requested network slice for the data session. The processor is also configured to receive an indication of an authorized network slice for the data session and receive an indication of a backoff timer value from the network device. The processor is also configured to send a first message associated with the authorized network slice after a backoff timer based on the backoff timer value expires, and send a second message having a second field corresponding to the first field of the data session establishment request after a backoff timer based on the backoff timer value expires.

[0201] In a second aspect alternatively or additionally to the first aspect, the processor is further configured to delay sending the first message and the second message during a time interval, the time interval starting upon initiation of operation of the backoff timer and ending upon expiration of the backoff timer.

[0202] In a third aspect, which is an alternative or supplement to one or more of the first to second aspects, the data session establishment request includes first single network slice selection assistance information (S-NSSAI) indicating a requested network slice, and the processor is also configured to receive a data session establishment acceptance message, wherein the data session establishment acceptance message includes a second S-NSSAI indicating an authorized network slice.

[0203] In a fourth aspect, which is an alternative or supplement to one or more of the first to third aspects, the memory is configured to store an indication of a requested network slice, and the processor is further configured to access the indication to determine that the operation of the backoff timer applies to the requested network slice.

[0204] In a fifth aspect which is an alternative or supplement to one or more of the first to fourth aspects, the data session establishment request does not indicate any requested network slice.

[0205] In a sixth aspect which is an alternative or supplement to one or more of the first to fifth aspects, the processor is further configured to send a data session modification request to the network device to request modification of the data session.

[0206] In the seventh aspect, which is a replacement or supplement for one or more of the first to sixth aspects, the processor is also configured to: detect that the backoff timer value is greater than zero, and in response to detecting that the backoff timer value is greater than zero, initiate the operation of the backoff timer.

[0207] In an eighth aspect which is an alternative or additional option to one or more of the first to seventh aspects, an indication of the backoff timer value is included in the data session release command.

[0208] In a ninth aspect which is an alternative or additional option to one or more of the first to eighth aspects, an indication of the backoff timer value is included in the data session modification reject message.

[0209] In a tenth aspect which is an alternative or supplement to one or more of the first to ninth aspects, the processor is further configured to receive a cause value indicating a first type of back-off timer value or a second type of back-off timer value.

[0210] In the eleventh aspect, which is a replacement or supplement for one or more of the first to tenth aspects, the first type indicates that the back-off timer value is associated with the network slice, and the second type indicates that the back-off timer value is associated with the network slice and the data network name (DNN).

[0211] In a twelfth aspect, which is an alternative or supplement to one or more of the first to eleventh aspects, the processor is further configured to: in response to detecting expiration of the backoff timer, terminate the operation of the backoff timer.

[0212] In the thirteenth aspect, which is a replacement or supplement for one or more of the first to twelfth aspects, a method of wireless communication includes: sending a data session establishment request by a user equipment (UE) device to establish a data session with a network device using a wireless communication network. The data session establishment request has a first field indicating a requested data network name (DNN) for the data session. The method also includes receiving an indication of an authorized DNN for the data session at the UE device, and receiving an indication of a backoff timer value from the network device at the UE device. The method also includes: after a backoff timer based on the backoff timer value expires, sending a first message associated with the authorized DNN, and sending a second message having a second field corresponding to the first field of the data session establishment request.

[0213] In a fourteenth aspect which is an alternative or supplement to one or more of the first to thirteenth aspects, the UE device delays sending the first message and the second message during a time interval which starts when operation of a backoff timer is initiated and ends when the backoff timer expires.

[0214] In a fifteenth aspect that is an alternative or supplement to one or more of the first to fourteenth aspects, a device for wireless communication includes a memory and a processor coupled to the memory. The processor is configured to receive a data session establishment request to establish a data session with a user equipment (UE) device using a wireless communication network, and send an indication of an authorized network slice for the data session. The processor is also configured to send a congestion notification message, which indicates one or more network slices associated with a backoff timer value. The one or more network slices indicate one or both of an authorized network slice or a requested network slice specified by the UE device. The processor is also configured to: in response to the expiration of a backoff timer based on the backoff timer value, receive a message associated with at least one of the one or more network slices.

[0215] In a sixteenth aspect which is an alternative or supplement to one or more of the first to fifteenth aspects, the congestion notification message corresponds to a fifth generation session management (5GSM) congestion retry information element (IE).

[0216] In the seventeenth aspect, which is a replacement or supplement for one or more of the first to sixteenth aspects, the congestion notification message includes a first bit having a first value indicating that the back-off timer value is applicable to a public land mobile network (PLMN) registered to the UE device or a second value indicating that the back-off timer value is applicable to multiple PLMNs.

[0217] In the eighteenth aspect, which is a replacement or supplement for one or more of the first to seventeenth aspects, the congestion notification message includes a second bit having a first value indicating that the backoff timer value is applicable to the requested network slice or a second value indicating that the backoff timer value is applicable to the authorized network slice.

[0218] In a nineteenth aspect that is an alternative or supplement to one or more of the first to eighteenth aspects, the congestion notification message includes a second bit and a third bit. The second bit has a first value indicating that the backoff timer value is not applicable to the requested network slice or a second value indicating that the backoff timer value is applicable to the requested network slice. The third bit has a first value indicating that the backoff timer value is not applicable to the authorized network slice or a second value indicating that the backoff timer value is applicable to the authorized network slice.

[0219] In the twentieth aspect, which is a replacement or supplement for one or more of the first to nineteenth aspects, the congestion notification message includes multiple bits, wherein the multiple bits have a first value set indicating that the backoff timer value is applicable to the requested network slice, a second value set indicating that the backoff timer value is applicable to the authorized network slice, or a third value set indicating that the backoff timer value is applicable to both the requested network slice and the authorized network slice.

[0220] In aspect 21, which is a replacement or supplement for one or more of aspects 1 to 20, the data session establishment request includes first single network slice selection assistance information (S-NSSAI) indicating a requested network slice, and the processor is also configured to send a data session establishment acceptance message, wherein the data session establishment acceptance message includes a second S-NSSAI indicating an authorized network slice.

[0221] In aspect 22, which is an alternative or supplement to one or more of aspects 1 to 21, the data session establishment request does not indicate any requested network slice.

[0222] In a twenty-third aspect, which is an alternative or additional aspect to one or more of the first to twenty-second aspects, the processor is further configured to receive a data session modification request from a UE device.

[0223] In a twenty-fourth aspect, which is an alternative or supplement to one or more of the first to twenty-third aspects, the processor is further configured to send a data session release command to the UE device.

[0224] In a twenty-fifth aspect, which is an alternative or additional option to one or more of the first to twenty-fourth aspects, the congestion notification message is included in a data session release command.

[0225] In a twenty-sixth aspect, which is an alternative or additional option to one or more of the first to twenty-fifth aspects, the congestion notification message is included in the data session modification reject message.

[0226] In the twenty-seventh aspect, which is an alternative or supplement to one or more of the first to twenty-sixth aspects, the processor is further configured to send a reason value indicating a first type of back-off timer value or a second type of back-off timer value. The first type indicates that the back-off timer value is associated with a network slice, and the second type indicates that the back-off timer value is associated with a network slice and a data network name (DNN).

[0227] In the twenty-eighth aspect, which is an alternative or additional aspect to one or more of the first to twenty-seventh aspects, the data session comprises a protocol data unit (PDU) data session.

[0228] In aspect 29, which is an alternative or supplement to one or more of aspects 1 to 28, a method of wireless communication includes: receiving a data session establishment request by a network device to establish a data session with a user equipment (UE) device using a wireless communication network. The method also includes sending an indication of an authorized data network name (DNN) for the data session by the network device, and sending a congestion notification message by the network device indicating one or more DNNs associated with a backoff timer value. The one or more DNNs indicate one or both of an authorized DNN or a requested DNN specified by the UE device. The method also includes: in response to the expiration of a backoff timer based on the backoff timer value, receiving a message associated with at least one of the one or more DNNs at the network device.

[0229] In a thirtieth aspect, as an alternative or supplement to one or more of the first to twenty-ninth aspects, the congestion notification message corresponds to a fifth generation session management (5GSM) congestion retry information element (IE).

[0230] Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0231] The functional blocks and modules described herein may include processors, electronic devices, hardware devices, electronic components, logic circuits, memories, software codes, firmware codes, etc., or any combination thereof. It will be further appreciated by those skilled in the art that the various illustrative logic blocks, modules, circuits, and operations described herein may be implemented as electronic hardware, computer software, or a combination of the two. For illustration, various illustrative components, blocks, modules, circuits, and operations have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and design of the entire system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as resulting in a departure from the scope of the present disclosure. It will also be readily appreciated by those skilled in the art that the order or combination of components, methods, or interactions described herein is merely an example, and the components, methods, or interactions of various aspects of the present disclosure may be combined or performed in a manner different from that shown and described herein.

[0232] The various illustrative logical blocks, modules, and circuits described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0233] The operation of the method or process described herein can be realized using hardware, utilizing a software module executed by a processor, or in a combination of the two. The software module can reside in a storage medium of any other form as known in the art, such as a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or a storage medium. The storage medium can be coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium can be integrated into the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In an alternative, the processor and the storage medium can reside in a user terminal as discrete components.

[0234] In some implementations, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Computer-readable storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. As an example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, disk storage, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code means in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. As used herein, disks and optical disks include compact disks (CDs), laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks typically reproduce data magnetically, and optical disks reproduce data optically with lasers. The above combination should also be included in the scope of computer-readable media.

[0235] As used herein, including the claims, when the term "and / or" is used in a list of two or more items, it means that any one of the listed items can be taken alone, or any combination of two or more of the listed items can be taken. For example, if a composition is described as comprising components A, B, and / or C, the composition can comprise A alone, B alone, C alone, a combination of A and B, a combination of A and C, a combination of B and C, or a combination of A, B, and C. In addition, as used herein, including the claims, "or" used in a list of items ending with "at least one of" indicates a disjunctive list, such that, for example, a list of "at least one of A, B, or C" means any of A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination thereof.

[0236] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Therefore, the disclosure is not intended to be limited to the examples and designs described herein, but to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A device for wireless communication, comprising: Memory; as well as A processor, coupled to a memory and configured to: send a data session establishment request to establish a data session with a network device using a wireless communication network, the data session establishment request having a first field indicating a requested network slice for the data session, receive an indication of an authorized network slice for the data session, receive an indication of a backoff timer value from the network device, and send a first message associated with the authorized network slice and a second message having a second field corresponding to the first field of the data session establishment request after a backoff timer based on the backoff timer value expires, wherein the authorized network slice is different from the requested network slice, and wherein the processor is further configured to delay sending the first message and the second message during a time interval, the time interval starting when the operation of the backoff timer is initiated and ending when the backoff timer expires.

2. The device according to claim 1, wherein: The data session establishment request includes first single network slice selection assistance information S-NSSAI indicating the requested network slice, and wherein the processor is further configured to receive a data session establishment acceptance message, the data session establishment acceptance message including a second S-NSSAI indicating the authorized network slice.

3. The device according to claim 1, wherein: The memory is configured to store an indication of a requested network slice, and wherein the processor is further configured to access the indication of the requested network slice to determine that operation of the backoff timer applies to the requested network slice.

4. The device according to claim 1, wherein: The processor is further configured to send a data session modification request to the network device to request modification of the data session.

5. The device according to claim 1, wherein: The processor is further configured to detect that the backoff timer value is greater than zero, and in response to detecting that the backoff timer value is greater than zero, initiate operation of the backoff timer.

6. The device according to claim 1, wherein: An indication of the back-off timer value is included in the data session release command.

7. The device of claim 1, wherein: An indication of the back-off timer value is included in the DATA SESSION MODIFY REJECT message.

8. The device of claim 1, wherein: The processor is further configured to receive a cause value indicating a first type of back-off timer value or a second type of back-off timer value.

9. The device of claim 8, wherein: The first type indicates that the backoff timer value is associated with a network slice, and wherein the second type indicates that the backoff timer value is associated with the network slice and a data network name DNN.

10. The device of claim 1, wherein: The processor is further configured to terminate operation of the back-off timer in response to detecting expiration of the back-off timer.

11. A method of wireless communication, comprising: sending a data session establishment request to establish a data session with a network device using a wireless communication network, the data session establishment request having a first field indicating a requested network slice for the data session; receiving an indication of an authorized network slice for a data session; receiving an indication of a backoff timer value from a network device; as well as sending a first message associated with the authorized network slice and a second message having a second field corresponding to the first field of the data session establishment request after expiration of a back-off timer based on the back-off timer value; wherein the authorized network slice is different from the requested network slice, and wherein sending of the first message and the second message is delayed during a time interval that starts when operation of the backoff timer is initiated and ends when the backoff timer expires.

12. A method of wireless communication, comprising: Sending, by a user equipment UE device, a data session establishment request to establish a data session with a network device using a wireless communication network, the data session establishment request having a first field indicating a requested data network name DNN for the data session; receiving, at a UE device, an indication of an authorized DNN for a data session; receiving, at a UE device, an indication of a back-off timer value; sending a first message associated with the authorized DNN after expiration of a backoff timer based on the backoff timer value; as well as After a backoff timer based on a backoff timer value expires, sending a second message having a second field corresponding to the first field of a data session establishment request, wherein the authorized DNN is different from the requested DNN, and wherein the UE device delays sending the first message and the second message during a time interval that starts when operation of the backoff timer is initiated and ends when the backoff timer expires.

13. An apparatus for wireless communication, comprising: Memory; as well as A processor, coupled to a memory and configured to: send a data session establishment request by a user equipment UE device to establish a data session with a network device using a wireless communication network, the data session establishment request having a first field indicating a requested data network name DNN for the data session, receive an indication of an authorized DNN for the data session at the UE device, receive an indication of a backoff timer value at the UE device, send a first message associated with the authorized DNN after a backoff timer based on the backoff timer value expires, and send a second message having a second field corresponding to the first field of the data session establishment request after a backoff timer based on the backoff timer value expires, wherein the authorized DNN is different from the requested DNN, and wherein the UE device delays sending the first message and the second message during a time interval, the time interval starting when the operation of the backoff timer is initiated and ending when the backoff timer expires.

14. A method of wireless communication, comprising: receiving a data session establishment request to establish a data session with a user equipment UE device using a wireless communication network; sending an indication of an authorized network slice for a data session; sending a congestion notification message indicating a plurality of network slices associated with a backoff timer value, the plurality of network slices indicating the authorized network slice and a requested network slice specified by the UE device, wherein the authorized network slice is different from the requested network slice; as well as In response to expiration of a backoff timer based on a backoff timer value, receiving a message associated with the multiple network slices.

15. An apparatus for wireless communication, comprising: Memory; as well as A processor, coupled to the memory and configured to: receive a data session establishment request to establish a data session with a user equipment UE device using a wireless communication network, send an indication of an authorized network slice for the data session, send a congestion notification message indicating multiple network slices associated with a backoff timer value, the multiple network slices indicating the authorized network slices and a requested network slice specified by the UE device, wherein the authorized network slice is different from the requested network slice, and receive a message associated with the multiple network slices in response to expiration of a backoff timer based on the backoff timer value.

16. The device of claim 15, wherein: The congestion notification message corresponds to the fifth generation session management 5GSM congestion retry information element IE.

17. The device of claim 15, wherein: The congestion notification message includes a first bit having a first value indicating that a back-off timer value is applicable to a public land mobile network PLMN registered with the UE device or a second value indicating that the back-off timer value is applicable to a plurality of PLMNs.

18. The device of claim 15, wherein: The congestion notification message includes: a second bit having a first value indicating that the back-off timer value is not applicable to the requested network slice or a second value indicating that the back-off timer value is applicable to the requested network slice; and The third bit has a first value indicating that the backoff timer value is not applicable to the authorized network slice or a second value indicating that the backoff timer value is applicable to the authorized network slice.

19. The device of claim 15, wherein: The congestion notification message includes multiple bits, and the multiple bits have a first set of values ​​indicating that the backoff timer value is applicable to the requested network slice, a second set of values ​​indicating that the backoff timer value is applicable to the authorized network slice, or a third set of values ​​indicating that the backoff timer value is applicable to both the requested network slice and the authorized network slice.

20. The device of claim 15, wherein: The data session establishment request includes first single network slice selection assistance information S-NSSAI indicating the requested network slice, and wherein the processor is further configured to send a data session establishment acceptance message, the data session establishment acceptance message including a second S-NSSAI indicating the authorized network slice.

21. The apparatus of claim 15, wherein: The processor is also configured to receive a data session modification request from a UE device.

22. The apparatus of claim 15, wherein: The processor is also configured to send a data session release command to the UE device.

23. The apparatus of claim 15, wherein: The congestion notification message is included in a data session release command.

24. The apparatus of claim 15, wherein: The congestion notification message is included in a data session modification reject message.

25. The apparatus of claim 15, wherein: The processor is also configured to send a reason value indicating a first type of back-off timer value or a second type of back-off timer value, wherein the first type indicates that the back-off timer value is associated with a network slice, and wherein the second type indicates that the back-off timer value is associated with a network slice and a data network name DNN.

26. The apparatus of claim 15, wherein: The data session includes a protocol data unit (PDU) data session.

27. A method of wireless communication, comprising: Receiving, by the network device, a data session establishment request to establish a data session with a user equipment UE device using a wireless communication network; sending, by the network device, an indication of an authorized data network name DNN for the data session; sending, by a network device, a congestion notification message indicating a plurality of DNNs associated with a backoff timer value, the plurality of DNNs indicating the authorized DNN and a requested DNN specified by a UE device, wherein the authorized DNN is different from the requested DNN; as well as In response to expiration of a backoff timer based on the backoff timer value, a message associated with the plurality of DNNs is received by the network device.

28. The method of claim 27, wherein: The congestion notification message corresponds to the fifth generation session management 5GSM congestion retry information element IE.

29. An apparatus for wireless communication, comprising: Memory; as well as A processor is coupled to a memory and is configured to: receive, by a network device, a data session establishment request to establish a data session with a user equipment UE device using a wireless communication network, send, by the network device, an indication of an authorized data network name DNN for the data session, send, by the network device, a congestion notification message indicating a plurality of DNNs associated with a backoff timer value, the plurality of DNNs indicating the authorized DNN and a requested DNN specified by the UE device, wherein the authorized DNN is different from the requested DNN, and receive, by the network device, a message associated with the plurality of DNNs in response to expiration of a backoff timer based on the backoff timer value.

30. An apparatus for wireless communication, comprising: means for sending a data session establishment request to establish a data session with a network device using a wireless communication network, the data session establishment request having a first field indicating a requested network slice for the data session; means for receiving an indication of an authorized network slice for a data session; means for receiving an indication of a backoff timer value from a network device; as well as means for sending, after expiration of a back-off timer based on a back-off timer value, a first message associated with the authorized network slice and a second message having a second field corresponding to the first field of the data session establishment request; wherein the authorized network slice is different from the requested network slice, and wherein sending of the first message and the second message is delayed during a time interval that starts when operation of the backoff timer is initiated and ends when the backoff timer expires.

31. An apparatus for wireless communication, comprising: means for sending, by a user equipment UE device, a data session establishment request to establish a data session with a network device using a wireless communication network, the data session establishment request having a first field indicating a requested data network name DNN for the data session; means for receiving, at a UE device, an indication of an authorized DNN for a data session; means for receiving, at a UE device, an indication of a back-off timer value; means for sending a first message associated with the authorized DNN after expiration of a backoff timer based on a backoff timer value; as well as means for sending a second message having a second field corresponding to the first field of the data session establishment request after expiration of a backoff timer based on the backoff timer value; wherein the authorized DNN is different from the requested DNN, and wherein the UE device delays sending the first message and the second message during a time interval that begins when operation of the backoff timer is initiated and ends when the backoff timer expires.

32. An apparatus for wireless communication, comprising: means for receiving a data session establishment request to establish a data session with a user equipment UE device using a wireless communication network; means for sending an indication of an authorized network slice for a data session; means for sending a congestion notification message indicating a plurality of network slices associated with a backoff timer value, the plurality of network slices indicating the authorized network slice and a requested network slice specified by the UE device, wherein the authorized network slice is different from the requested network slice; as well as A component for receiving a message associated with the plurality of network slices in response to expiration of a backoff timer based on a backoff timer value.

33. An apparatus for wireless communication, comprising: means for receiving, by a network device, a data session establishment request to establish a data session with a user equipment UE device using a wireless communication network; means for sending, by the network device, an indication of an authorized data network name DNN for a data session; means for sending, by the network device, a congestion notification message indicating a plurality of DNNs associated with a backoff timer value, the plurality of DNNs indicating the authorized DNN and a requested DNN specified by the UE device, wherein the authorized DNN is different from the requested DNN; as well as Means for receiving, by the network device, a message associated with the plurality of DNNs in response to expiration of a backoff timer based on a backoff timer value.

34. A non-transitory computer readable medium storing code for wireless communication, the code comprising instructions executable by a processor to: sending a data session establishment request to establish a data session with a network device using a wireless communication network, the data session establishment request having a first field indicating a requested network slice for the data session; receiving an indication of an authorized network slice for a data session; receiving an indication of a backoff timer value from a network device; as well as sending a first message associated with the authorized network slice and a second message having a second field corresponding to the first field of the data session establishment request after expiration of a back-off timer based on the back-off timer value; wherein the authorized network slice is different from the requested network slice, and wherein the processor is further configured to delay sending the first message and the second message during a time interval that starts when operation of the backoff timer is initiated and ends when the backoff timer expires.

35. A non-transitory computer readable medium storing code for wireless communication, the code comprising instructions executable by a processor to: Sending, by a user equipment UE device, a data session establishment request to establish a data session with a network device using a wireless communication network, the data session establishment request having a first field indicating a requested data network name DNN for the data session; receiving, at a UE device, an indication of an authorized DNN for a data session; receiving, at a UE device, an indication of a back-off timer value; sending a first message associated with the authorized DNN after expiration of a backoff timer based on the backoff timer value; as well as sending a second message having a second field corresponding to the first field of the data session establishment request after expiration of a backoff timer based on the backoff timer value; wherein the authorized DNN is different from the requested DNN, and wherein the UE device delays sending the first message and the second message during a time interval that begins when operation of the backoff timer is initiated and ends when the backoff timer expires.

36. A non-transitory computer readable medium storing code for wireless communication, the code comprising instructions executable by a processor to: receiving a data session establishment request to establish a data session with a user equipment UE device using a wireless communication network; sending an indication of an authorized network slice for a data session; sending a congestion notification message indicating a plurality of network slices associated with a backoff timer value, the plurality of network slices indicating the authorized network slice and a requested network slice specified by the UE device, wherein: The authorized network slice is different from the requested network slice; as well as In response to expiration of a backoff timer based on a backoff timer value, receiving a message associated with the multiple network slices.

37. A non-transitory computer readable medium storing code for wireless communication, the code comprising instructions executable by a processor to: Receiving, by the network device, a data session establishment request to establish a data session with a user equipment UE device using a wireless communication network; sending, by the network device, an indication of an authorized data network name DNN for the data session; sending, by a network device, a congestion notification message indicating a plurality of DNNs associated with a backoff timer value, the plurality of DNNs indicating the authorized DNN and a requested DNN specified by a UE device, wherein the authorized DNN is different from the requested DNN; as well as In response to expiration of a backoff timer based on the backoff timer value, a message associated with the plurality of DNNs is received by the network device.

Images