Systems and methods for a connection release procedure between user equipment and a base station

A base station may cause a user equipment (UE) to be connected to a network, wherein an attach request message, that is used to connect the UE to the network, includes one or more eligibility parameters for a connection release service. The base station may determine, based on the one or more eligibility parameters, that the UE is to receive the connection release service. The base station may provide, to the UE, a connection release message that is provided based on determining that the UE is to receive the connection release service. The base station may receive, from the UE, a connection release acknowledgement message that indicates that the connection release message has been received by the UE. The base station may perform one or more actions associated with changing a state of the UE based on receiving the connection release acknowledgement message.

BACKGROUND

A radio resource control (RRC) connection release procedure may be used to change a state that a user equipment (UE) has while connected to a network. For example, if the UE becomes inactive for a threshold time period, a base station may provide, to the UE, an RRC connection release message that has been encapsulated using a data-link-layer header. The RRC connection release message may notify the UE that a state of the UE has changed from a connected state to a different state (e.g., an idle state, a disconnected state, and/or the like).

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

A user equipment (UE) that is connected to a network may be in a state that indicates whether the UE has a connection with the network, a state that indicates a type of connection that the UE has with the network, and/or the like. For example, a UE that is connected to a network may be in a connected state while using one or more services that are available via the network, may be in an idle state while the UE remains connected to the network but is not presently using the one or more services, may be in a disconnected state that indicates that the UE is no longer connected to the network, and/or the like.

In some cases, while the UE is connected to the network, a base station may notify the UE that a state of the UE has changed (or is to be changed). For example, the base station may provide the UE with a connection release message, such as a radio resource control (RRC) connection release message, to notify the UE that the state has changed from a connected state to a new state, such as an idle state, a disconnected state, and/or the like.

However, in some cases, the UE may not receive the connection release message and therefore may not be notified of the state change. For example, poor network performance (e.g., poor radio frequency (RF) coverage, low bandwidth and/or throughput, and/or the like) may prevent the UE from receiving the connection release message. As another example, the UE may be prevented from receiving the connection release message and/or from being able to properly decode the connection release message if the UE has an overlap between a measurement gap period and a period for reception of system information (e.g., for reception of system information blocks (SIBs)). To provide a specific example, if there is an overlap between a measurement gap period and a period for reception of SIBs, the UE may be unable to decode a downlink message, which may prevent the UE from being able to understand the connection release message.

Furthermore, there is no mechanism available that will allow the UE to notify the base station that the connection release message has been received (or not received). Consequently, the base station may reassign resources that had been assigned to the UE, regardless of whether the UE has received an indication that the state has changed. The UE may then waste resources (e.g., processing resources, network resources, and/or the like) to attempt to use a service via an old connection to the network. Additionally, resources of the UE, the base station, and/or other core network devices may be wasted in reconnecting the UE to the network. For example, resources of the base station may be wasted because the base station has to assign new resources to the UE, despite the fact that the UE would otherwise have already been connected to the network.

According to some implementations described herein, a base station may use a connection release service to notify a UE that a state that the UE has with a network has changed (or is to be changed). In some implementations, the base station may provide the UE with a connection release message that has been encapsulated with a network-layer-header. In some implementations, the connection release service may cause the base station to be provided with a connection release acknowledge message that indicates that the UE has received notice that the state has changed (or is to be changed). In some implementations, the base station may be configured with one or more conditions that must be satisfied for the UE to be eligible to receive the connection release service (and/or for the UE to actually receive the connection release service). The connection release service may allow the UE to be notified that the state of the UE has changed (or is to be changed) to a new state (e.g., from a connected state to an idle state, to a disconnected state, and/or the like).

In this way, the connection release service ensures that the UE is notified when the state of the UE changes and/or ensures that the base station is provided with an acknowledgement that the UE has been notified. By using the connection release message to notify the UE of the state change, resources of the UE are conserved relative to an inferior technique where the UE is not notified of the state change, and therefore may waste resources attempting to use a service via the network with an old connection (e.g., despite no longer being in a connected state and thus lacking an appropriate network connection), may waste resources (e.g., processing resources, network resources, memory resources, and/or the like) reconnecting to the network, and/or the like.

Additionally, the base station may, based on receiving the connection release acknowledgement message from the UE, cause resources that are reserved for the UE to be made available to one or more other UEs. Without acknowledgement from the UE, processing resources of the base station might be wasted in unassigning resources from the UE and/or reassigning those resources to one or more other UEs, processing resources of the base station, the UE, and/or one or more other network devices might be wasted in assisting the UE in reconnecting to the network, and/or the like.

FIGS. 1A-1Care diagrams of one or more example implementations100described herein. For example, example implementation(s)100may include a UE102, a base station104, and a core network106.

As shown inFIGS. 1A-1C, base station104may use a connection release service to notify UE102that a state of UE102has changed (or is to be changed). For example, UE102may have a state that represents a status that UE102has with core network106. The state may be a connected state that indicates that UE102is in a connected mode (e.g., and connected to core network106), an idle state that indicates that UE102is in an idle mode, an airplane state that indicates that UE102is in an airplane mode, a disconnected state that indicates that UE102is not connected to core network106, and/or the like. In some cases, the state of UE102may be a radio resource control (RRC) state, such as a dedicated channel connected state (e.g., a CELL_DCH state), a reduced resources state (e.g., a CELL_FACH state, a CELL_PCH state, a URA_PCH state, an idle state, and/or the like), and/or the like.

The connection release service may be a service that allows base station104to provide UE102with a connection release message that indicates that a state of UE102has changed (or is to be changed). The connection release message may, for example, be an RRC connection release message and/or a similar type of message. Additionally, the connection release service may cause UE102to provide base station104with a connection release acknowledgement message that indicates that UE102has received the connection release message. The connection release acknowledgement message may, for example, be an RRC connection release acknowledgement message and/or a similar type of message. Additional details are provided herein.

As shown inFIG. 1A, UE102may establish a connection with core network106(e.g., to utilize one or more services that are available via core network106). Some implementations described herein involve communications between UE102, base station104, and/or core network106. In these implementations, the communications may be supported via a communication interface, such as an air interface, an application programming interface (API), and/or another type of communication interface. In some implementations, the communications may be supported by one or more protocols, such as an RRC protocol and/or another type of protocol that may be used to support data communications over core network106. Core network106may be a third generation (3G) network, a fourth generation (4G) network (e.g., a 4G long-term evolution (LTE) network), a fifth generation (5G) network, a next generation network, and/or the like.

To establish the connection with core network106, and as shown by reference number108, UE102may provide an attach request message to base station104. The attach request message may include one or more eligibility parameters that indicate whether UE102is eligible for the connection release service, that specify when UE102is to receive the connection release service, and/or the like. For example, the one or more eligibility parameters may include a value that indicates whether UE102is eligible for the connection release service, a device type identifier that identifies a device type of UE102, a device type category identifier that identifies a category of the device type of UE102, a threshold network performance indicator (NPI) value, and/or the like.

To provide an example, the one or more eligibility parameters may include the value that indicates whether UE102is eligible for the connection release service. In this example, base station104may be configured to provide the connection release services if the one or more eligibility parameters include the value that indicates that UE102is eligible for the connection release service.

To provide another example, the one or more eligibility parameters may include the device type identifier. In this example, base station104may be configured to provide the connection release service to specific types of devices. The device type identifier may, for example, identify UE102as a mobile device (e.g., a smartphone), as an internet of things (IoT) device, as a machine-to-machine (M2M) device, as a 4G device, as a 5G device, and/or the like. By including the device type identifier in the attach request message, base station104will be able to determine whether to provide UE102with the connection release service, as will be described further herein.

To provide another example, the one or more eligibility parameters may include the device type category identifier. In this example, base station104may be configured to provide the connection release service to specific categories of devices (e.g., a category may serve as a subset of a particular type of device). The device type category identifier may, for example, identify UE102as being a category one (CAT-1) device, a narrowband (NB) category device (e.g., a CAT-NB1 device, a CAT-NB2 device, and/or the like), a category M device (e.g., a CAT-M1 device), a device that is defined by a 5G device type category, and/or the like. By including the device type category identifier in the attach request message, base station104will be able to determine whether to provide UE102with the connection release service, as will be described further herein.

To provide another example, the one or more eligibility parameters may include the threshold NPI value, such as a signal-to-interference-plus-noise ratio (SINR) value, a reference signal received power (RSRP) value, a reference signal received quality (RSRQ) value, a quality of service (QoS) value, a bandwidth value, a latency value, a throughput value, and/or the like. In this example, while UE102is connected to core network106, UE102may periodically report NPI values associated with the connection that UE102has with core network106. Additionally, base station104may have access to one or more corresponding threshold NPI values, and may be configured to provide the connection release service if a particular reported NPI value satisfies a corresponding threshold NPI value. Additional details and examples are provided further herein.

As shown by reference number110, base station104may determine that UE102is eligible to receive the connection release service. For example, base station104may identify the one or more eligibility parameters in the attach request message to determine that UE102is eligible to receive the connection release service. In some implementations, even if UE102is eligible to receive the connection release service, base station104may make a real-time determination as to whether to provide UE102with the connection release service at a given time period, as will be described further herein.

In some implementations, base station104may use a data structure to store the one or more eligibility parameters. For example, base station104may use a data structure to store the one or more eligibility parameters in association with an identifier of UE102, in association with a session identifier for a session that UE102is using for a service, and/or the like. This may allow base station104to reference the one or more eligibility parameters when determining whether to provide UE102with the connection release service. As a specific example, if the one or more eligibility parameters include a threshold NPI value, base station104may use the data structure to store the threshold NPI value, such that base station104may receive an NPI value from UE and may compare the NPI value with the threshold NPI value to determine whether to provide UE102with the connection release service, as described further herein.

As shown by reference number112, base station104may provide the attach request message to core network106. For example, base station104may provide the attach request message to one or more devices of core network106, such as a mobility management entity (MME), a serving gateway (SGW), a packet data network (PDN) gateway (PGW), and/or the like. This may allow the PGW (or another device within core network106) to generate an attachment response message and may, as shown by reference number114, cause the attachment response message to be provided to base station104. The attachment response message may indicate that UE102is connected to core network106. For example, the attachment response message may include a state value that indicates that UE102is in a connected state.

In some implementations, base station104may connect UE102to a 5G network. In this case, the attach request may be provided to one or more elements of the 5G network, such as a network slice selection function (NSSF), a network exposure function (NEF), an authentication server function (AUSF), a unified data management (UDM) component, a policy control function (PCF), an application function (AF), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), and/or the like.

In some implementations, base station104may update the data structure (or another data structure) with state data that identifies the state of UE102. For example, base station104may update the data structure with the state data to allow base station104to keep a record of a current state of UE102and/or any other UEs102that are using base station104to connect to core network106, to allow base station104to update the record of the current state of UE102and/or any other UEs102that are using base station104to connect to core network106, and/or the like.

As shown by reference number116, base station104may provide the attachment response message to UE102. This may notify UE102that the connection to core network106has been established. In some implementations (not shown), UE102may provide (e.g., using base station104as an intermediary) core network106with an acknowledgement message indicating that UE102has received the attachment response message.

In this way, UE102connects to core network106in a manner that uses the one or more eligibility parameters to notify base station104that UE102is eligible for the connection release service.

As shown inFIG. 1B, and by reference number118, base station104may determine to provide UE102with the connection release service. For example, base station104may determine to provide UE102with the connection release service based on one or more conditions being satisfied. In this case, base station104may be configured with one or more conditions that, if satisfied, cause base station104to provide UE102with the connection release service. The one or more conditions may include a first condition that is satisfied if UE102stops communicating with core network106for a threshold time period, a second condition that is satisfied if resource usage of UE102satisfies a threshold resource usage, a third condition that is satisfied if an NPI value reported by UE102satisfies a corresponding threshold NPI value, and/or the like, as further described below.

In some implementations, base station104may determine to provide UE102with the connection release service based on the first condition being satisfied. For example, a user may stop using UE102to access a service that is provided via core network106, and base station104may monitor a quantity of time that has passed since UE102has used network resources for the service. If the quantity of time that has passed since UE102has used network resources satisfies a threshold quantity of time, base station104may determine to provide UE102with the connection release service.

Additionally, or alternatively, base station104may determine to provide UE102with the connection release service based on the second condition being satisfied. For example, base station104may periodically compare data identifying a quantity of resources being used by UE102with a corresponding resource usage threshold value, and may determine to provide UE102with the connection release service based on the quantity of resources satisfying the corresponding resource usage threshold value.

Additionally, or alternatively, base station104may determine to provide UE102with the connection release service based on the third condition being satisfied. For example, UE102may periodically provide base station104with NPI values, such as an SINR value, an RSRP value, an RSRQ value, a QoS value, and/or the like. This may allow base station104to compare the NPI value with a corresponding threshold NPI value and to determine to provide UE102with the connection release service if the NPI value satisfies the corresponding threshold NPI value.

As shown by reference number120, base station104may encapsulate a connection release message with a network-layer header. For example, to provide UE102with the connection release service, base station104may identify or generate a connection release message, and may encapsulate the connection release message using one or more headers that include a network-layer header. The network-layer header may include data that allows the connection release message to be delivered to a proper destination (e.g., via one or more intermediate devices).

To provide a specific example, base station104may first encapsulate the connection release message with a data-link-layer header (and/or footer), such as an RRC header, a media access control (MAC) header, a radio link control (RLC) header, and/or the like. Next, base station104may encapsulate the connection release message (e.g., which has already been encapsulated with the data link-layer-header) with a network-layer header, such as an internet protocol (IP) header, an internet packet exchange (IPX) header, an address resolution protocol (ARP) header, a virtual location area network (VLAN) header, and/or the like.

In some implementations, a payload of the connection release message may include state data that includes a value that identifies the state of UE102, a value that identifies the state of UE102and/or a prior-assigned state of UE102, a value that indicates that the state of UE102is to be changed (e.g., base station104may be configured to wait until receipt of a connection release acknowledgement message to change the state), and/or the like. In some implementations, the state data may be included in the network-layer-header.

As shown by reference number122, base station104may provide UE102with the connection release message that includes the network-layer header. This may notify UE102that the state of UE102has changed (or is to be changed). In some implementations, UE102may not receive the connection release message. A description of these implementations is provided in connection withFIGS. 2A-2C.

In this way, base station104provides UE102with the connection release message that includes the network-layer header.

As shown inFIG. 1C, and by reference number124, UE102may encapsulate a connection release acknowledgement message with another network-layer header. For example, UE102may be configured to generate and/or identify a connection release acknowledgement message based on receiving the connection release message, and may encapsulate the connection release acknowledgement message using another network-layer header.

As shown by reference number126, UE102may provide the connection release acknowledgement message that includes the other network-layer header to base station104. This may notify base station104that UE102has received the connection release message.

As shown by reference number128, base station104may perform one or more actions based on receiving the connection release acknowledgement message. For example, base station104may update the state data that identifies the state of UE102, may modify a configuration of available resources, and/or the like, as each described below.

In some implementations, base station104may update the state data that identifies the state of UE102. For example, base station104may have been configured to wait to update the state data until after receiving the connection release acknowledgement message from UE102and may, based on receipt of that message, update the state data (e.g., that is stored via the data structure).

Additionally, or alternatively, base station104may modify a configuration of available resources. The configuration may include a reference signal configuration, such as a demodulation reference signal (DMRS) configuration and/or another type of signal configuration. As an example, base station104may have reserved, for UE102, a set of resource blocks of a channel that is used for communications with core network106. In this example, base station104may, based on receiving the connection release acknowledgement message, modify the set of resource blocks that are assigned to UE102(e.g., by unassigning the set of resource blocks from UE102, by unassigning a subset of the set of resource blocks from UE102, and/or the like).

In this way, the connection release service ensures that UE102is notified when the state of the UE changes and/or ensures that base station104is provided with an acknowledgement that UE102has been notified.

As indicated above,FIGS. 1A-1Care provided as one or more examples. Other examples may differ from what is described with regard toFIGS. 1A-1C. For example, there may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown inFIGS. 1A-1C. Furthermore, two or more devices shown inFIGS. 1A-1Cmay be implemented within a single device, or a single device shown inFIGS. 1A-1Cmay be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) of example implementation100may perform one or more functions described as being performed by another set of devices of example implementation100. For example, one or more implementations described as being performed by base station104may, in other implementations, be performed by UE102. Additionally, one or more implementations described as being performed by UE102may, in other implementations, be performed by base station104.

FIGS. 2A-2Care diagrams of one or more example implementations200described herein. For example, example implementation(s)200may include a UE202, a base station204, and a core network206.FIGS. 2A-2Cdescribe how base station204handles situations where UE202does not receive a connection release message (e.g., which may be part of a connection release service). One or more implementations described below may include terminology and/or examples that have already been described in connection withFIGS. 1A-1C.

As shown inFIG. 2A, UE202may establish a connection with core network206(e.g., to utilize one or more services that are available via core network206). For example, as shown by reference number208, UE202may provide, to base station204, an attach request message that includes one or more eligibility parameters.

As shown by reference number210, base station204may determine that UE202is eligible to receive the connection release service. In some implementations, even if UE202is eligible to receive the connection release service, base station204may make a real-time determination as to whether to provide UE202with the connection release service at a given time period, as further described elsewhere herein. In some implementations, base station204may update a data structure with the one or more eligibility parameters.

As shown by reference number212, base station204may provide the attach request message to core network206. As shown by reference number214, base station204may receive an attachment response message from core network206. The attachment response message may indicate that UE202is connected to core network206. In some implementations, base station204may update the data structure (or another data structure) with state data that identifies the state of UE202.

As shown by reference number216, base station204may provide the attachment response message to UE202. This may notify UE202that the connection to core network206has been established. In some implementations (not shown), UE202may provide (e.g., using base station204as an intermediary) core network206with an acknowledgement message indicating that UE202has received the attachment response message.

In this way, UE202connects to core network206in a manner that uses the one or more eligibility parameters to notify base station204that UE202is eligible for the connection release service.

As shown inFIG. 2B, and by reference number218, base station204may determine to provide UE202with the connection release service. For example, base station204may determine to provide UE202with the connection release service based on one or more conditions being satisfied. In this case, base station204may be configured with one or more conditions that, if satisfied, cause base station204to provide UE202with the connection release service.

As shown by reference number220, base station204may encapsulate a connection release message with a network-layer header. For example, to provide UE202with the connection release service, base station204may identify or generate a connection release message and may encapsulate the connection release message using one or more headers that include a network-layer header.

As shown by reference number222, base station204may attempt to provide UE202with the connection release message but UE202may not receive the message. The connection release message may not reach UE202if poor network performance (e.g., poor radio frequency coverage, and/or the like) prevents the connection release message from being received by UE202, if UE202is unable to properly decode the connection release message based on an overlap between a measurement gap period and a period for reception of system information (e.g., for reception of system information blocks), and/or the like.

In this way, UE202is unable to receive and/or decode the connection release message that is provided by base station204.

As shown inFIG. 2C, and by reference numbers224,226,228, and230, base station104may successfully retransmit the connection release message to UE202to cause UE202to provide base station204with a connection release acknowledgement message. For example, and as shown by reference number224, base station204may retransmit the connection release message to UE202.

In some implementations, base station204may retransmit the connection release message based on a retransmission condition being satisfied. For example, base station204may be configured with a retransmission condition that allows base station204to retransmit the connection release message after a threshold amount of time passes (e.g., relative to a time at which a previous attempt to transmit or retransmit the connection release message was made). Additionally, or alternatively, base station204may retransmit the connection release message based on one or more other retransmission conditions. For example, base station204may compare an NPI value (e.g., a most recent NPI value received from UE202) with a corresponding threshold NPI value, and may retransmit the connection release message based on determining that the NPI value satisfies the corresponding threshold NPI value.

As shown by reference number226, UE202may encapsulate a connection release acknowledgement message with another network-layer header. As shown by reference number228, base station204may receive, from UE202, the connection release acknowledgement message that includes the network-layer header. As shown by reference number230, base station204may perform one or more actions (e.g., as described elsewhere herein) based on receiving the connection release acknowledgement message.

In this way, base station204retransmits the connection release message to ensure that UE202receives an indication that the state of UE202has changed (or is to be changed).

As shown by reference numbers232,234,236, and238, the connection release message may fail to reach UE202, and base station204may still modify a state that UE202is in with core network206. For example, base station204may retransmit the connection release message that includes the network layer header to UE202. However, UE202may not receive the retransmission (e.g., for one or more reasons described above).

As shown by reference number234, base station204may retransmit the connection release message to UE202(e.g., over a given time period). For example, base station204may periodically retransmit the connection release message to UE202, may retransmit the connection release message to UE202a threshold number of times, and/or the like. As shown by reference number236, base station204may determine that a state of UE202is to be changed, despite the fact that UE202did not receive the connection release message. For example, base station204may determine that the state is to be changed based on the retransmission condition being satisfied a threshold number of times (e.g., within a given time period).

As an example, base station204may periodically continue to retransmit the connection release message to UE202until a number of transmissions (or retransmissions) satisfy a threshold number of transmissions (or retransmissions). If the threshold is satisfied, base station204may stop attempting to retransmit the connection release message and may, based on the threshold being satisfied, determine that the state of UE202is to be changed (e.g., despite the fact that UE202has not provided the connection release acknowledgement message).

As shown by reference number238, base station204may perform one or more actions. For example, base station204may update the state data corresponding to UE202with new state data that identifies a new state of UE202, may cause resources allocated to UE202to be made available to one or more other UEs202, and/or the like.

In this way, the connection release service ensures that UE202is notified when the state of UE202changes (or is to be changed), ensures that base station204is provided with an acknowledgement that UE202has been notified, ensures that a mechanism is in place to attempt to retransmit the connection release message in situations where UE202does not receive the message, and/or ensures that the state of UE202is changed after making multiple attempts to retransmit the message to UE202.

As indicated above,FIGS. 2A-2Care provided as one or more examples. Other examples may differ from what is described with regard toFIGS. 2A-2C. For example, there may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown inFIGS. 2A-2C. Furthermore, two or more devices shown inFIGS. 2A-2Cmay be implemented within a single device, or a single device shown inFIGS. 2A-2Cmay be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) of example implementation200may perform one or more functions described as being performed by another set of devices of example implementation200. For example, one or more implementations described as being performed by base station204may, in other implementations, be performed by UE202. Additionally, one or more implementations described as being performed by UE202may, in other implementations, be performed by base station204.

FIG. 3is a diagram of an example environment300in which systems and/or methods described herein may be implemented. As shown inFIG. 3, environment300may include a user equipment (UE)310, a base station320, a mobility management entity (MME)330, a serving gateway (SGW)340, a packet data network (PDN) gateway (PGW)350, a home subscriber server (HSS)360, an authentication, authorization, and/or accounting (AAA) server370, and/or a network380. Devices of environment300may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.

Some implementations are described herein as being performed within a long term evolution (LTE) network for explanatory purposes. Some implementations may be performed within a network that is not an LTE network, such as a third generation (3G) network, a fifth generation (5G) network, and/or the like.

Environment200may include an evolved packet system (EPS) that includes an LTE network and/or an evolved packet core (EPC) that operate based on a third generation partnership project (3GPP) wireless communication standard. The LTE network may include a radio access network (RAN) that includes one or more base stations320that take the form of evolved Node Bs (eNBs) via which UE310communicates with the EPC. The EPC may include MME330, SGW340, and/or PGW350that enable UE310to communicate with network380and/or an Internet protocol (IP) multimedia subsystem (IMS) core. The IMS core may include HSS360and/or AAA server370, and may manage device registration and authentication, session initiation, etc., associated with UE310. HSS360and/or AAA server370may reside in the EPC and/or the IMS core.

UE310includes one or more devices capable of communicating with base station320and/or a network (e.g., network380). For example, UE310may include a wireless communication device, a radiotelephone, a personal communications system (PCS) terminal (e.g., that may combine a cellular radiotelephone with data processing and data communications capabilities), a smart phone, a laptop computer, a tablet computer, a personal gaming system, and/or a similar device. UE310may send traffic to and/or receive traffic from network380(e.g., via base station320, SGW340, and/or PGW350).

In some implementations, UE310may be configured to utilize a connection release service. In some implementations, UE310may provide base station320with an attach request message (e.g., to connect to network380) that includes one or more eligibility parameters. In some implementations, UE310may receive an attachment response message indicating that a connection with network380has been established. In some implementations, UE310may receive a connection release message with a network-layer-header (e.g., a radio resource control (RRC) connection release message) from base station320. In some implementations, UE310may provide a connection release acknowledgement message (e.g., an RRC connection release message) to base station320. In some implementations, UE310may perform one or more tasks, features, and/or functions that are described herein as being performed by base station320.

Base station320includes one or more devices capable of transferring traffic, such as audio, video, text, and/or other traffic, destined for and/or received from UE310. In some implementations, base station320may include an eNodeB associated with an LTE network that receives traffic from and/or sends traffic to network380via SGW340and/or PGW350. Additionally, or alternatively, one or more base stations320may be associated with a radio access network (RAN) that is not associated with the LTE network. Base station320may send traffic to and/or receive traffic from UE310via an air interface. In some implementations, base station320may include a small cell base station, such as a base station of a microcell, a picocell, and/or a femtocell. In some implementations, base station320may alter (e.g., periodically) a base station identifier (e.g., a PCI) of base station320, as described elsewhere herein.

In some implementations, base station320may be configured to provide UE310with a connection release service. For example, base station320may be configured with data that identifies one or more conditions that, if satisfied, allow base station320to determine that UE310is eligible to receive the connection release service and/or that allow base station320to determine to provide UE310with the connection release service.

In some implementations, base station320may encapsulate a connection release message with a network-layer header and/or may provide the connection release message to UE310. In some implementations, base station320may receive a connection release acknowledgement message from UE310. In some implementations, base station320may be configured with one or more retransmission conditions that dictate when base station320retransmits the connection release message to UE310. In some implementations, base station320may update a data structure that is used to store state data that identifies a state of UE310. In some implementations, base station320may perform one or more other actions described herein.

MME330includes one or more devices, such as one or more server devices, capable of managing authentication, activation, deactivation, and/or mobility functions associated with UE310. In some implementations, MME330may perform operations relating to authentication of UE310. Additionally, or alternatively, MME330may facilitate the selection of a particular SGW340and/or a particular PGW350to serve traffic to and/or from UE310. MME330may perform operations associated with handing off UE310from a first base station320to a second base station320when UE310is transitioning from a first cell associated with the first base station320to a second cell associated with the second base station320. Additionally, or alternatively, MME330may select another MME (not pictured), to which UE310should be handed off (e.g., when UE310moves out of range of MME330).

SGW340includes one or more devices capable of routing packets. For example, SGW340may include a traffic transfer device, such as a gateway, a router, a modem, a switch, a firewall, a network interface card (MC), a hub, a bridge, a server device, an optical add/drop multiplexer (OADM), or any other type of device that processes and/or transfers traffic. In some implementations, SGW340may aggregate traffic received from one or more base stations210associated with the LTE network, and may send the aggregated traffic to network380(e.g., via PGW350) and/or other network devices associated with an evolved packet core (EPC) and/or an Internet Protocol Multimedia Subsystem (IMS) core. SGW340may also receive traffic from network380and/or other network devices, and may send the traffic to UE310via base station320. Additionally, or alternatively, SGW340may perform operations associated with handing off UE310to and/or from an LTE network.

PGW350includes one or more devices capable of providing connectivity for UE310to external packet data networks. For example, PGW350may include one or more data processing and/or traffic transfer devices, such as a gateway, a router, a modem, a switch, a firewall, a NIC, a hub, a bridge, a server device, an OADM, or any other type of device that processes and/or transfers traffic. In some implementations, PGW350may aggregate traffic received from one or more SGWs215and may send the aggregated traffic to network380. Additionally, or alternatively, PGW350may receive traffic from network380, and may send the traffic to UE310via SGW340and base station320. PGW350may record data usage information (e.g., byte usage).

HSS360may include one or more devices, such as one or more server devices, capable of managing (e.g., receiving, generating, storing, processing, and/or providing) information associated with UE310. For example, HSS360may manage subscription information associated with UE310, such as information that identifies a subscriber profile of a user associated with UE310, information that identifies services and/or applications that are accessible to UE310, location information associated with UE310, a network identifier (e.g., a network address) that identifies UE310, information that identifies a treatment of UE310(e.g., quality of service information, a quantity of minutes allowed per time period, a quantity of data consumption allowed per time period, etc.), and/or similar information. HSS360may provide this information to one or more other devices of environment300to support the operations performed by those devices.

AAA server370may include one or more devices, such as one or more server devices, that perform authentication, authorization, and/or accounting operations for communication sessions associated with UE310. For example, AAA server370may perform authentication operations for UE310and/or a user of UE310(e.g., using one or more credentials), may control access, by UE310, to a service and/or an application (e.g., based on one or more restrictions, such as time-of-day restrictions, location restrictions, single or multiple access restrictions, read/write restrictions, etc.), may track resources consumed by UE310(e.g., a quantity of voice minutes consumed, a quantity of data consumed, etc.), and/or may perform similar operations.

Network380includes one or more wired and/or wireless networks. For example, network380may include a cellular network (e.g., a 5G network, a 4G network, such as an LTE network, a 3G network, a code division multiple access (CDMA) network, etc.), a public land user network (PLMN), a wireless local area network (e.g., a Wi-Fi network), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, a cloud computing network, and/or a combination of these or other types of networks.

The number and arrangement of devices and networks shown inFIG. 3are provided as an example. In practice, there may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown inFIG. 3. Furthermore, two or more devices shown inFIG. 3may be implemented within a single device, or a single device shown inFIG. 3may be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) of environment300may perform one or more functions described as being performed by another set of devices of environment300.

FIG. 4is a diagram of example components of a device400. Device400may correspond to UE310, base station320, MME330, SGW340, PGW350, HSS360, and/or AAA server370. In some implementations, UE310, base station320, MME330, SGW340, PGW350, HSS360, and/or AAA server370may include one or more devices400and/or one or more components of device400. As shown inFIG. 4, device400may include a bus410, a processor420, a memory430, a storage component440, an input component450, an output component460, and a communication interface470.

Storage component440stores information and/or software related to the operation and use of device400. For example, storage component440may include a hard disk (e.g., a magnetic disk, an optical disk, and/or a magneto-optic disk), a solid state drive (SSD), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of non-transitory computer-readable medium, along with a corresponding drive.

Input component450includes a component that permits device400to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and/or a microphone). Additionally, or alternatively, input component450may include a component for determining location (e.g., a global positioning system (GPS) component) and/or a sensor (e.g., an accelerometer, a gyroscope, an actuator, another type of positional or environmental sensor, and/or the like). Output component460includes a component that provides output information from device400(via, e.g., a display, a speaker, a haptic feedback component, an audio or visual indicator, and/or the like).

Communication interface470includes a transceiver-like component (e.g., a transceiver, a separate receiver, a separate transmitter, and/or the like) that enables device400to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface470may permit device400to receive information from another device and/or provide information to another device. For example, communication interface470may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a wireless local area network interface, a cellular network interface, and/or the like.

Device400may perform one or more processes described herein. Device400may perform these processes based on processor420executing software instructions stored by a non-transitory computer-readable medium, such as memory430and/or storage component440. As used herein, the term “computer-readable medium” refers to a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

FIG. 5is a flowchart of an example process500for systems and methods for using a connection release service to notify a user equipment (UE) that a state that the UE has with a network has changed (or is to be changed). In some implementations, one or more process blocks ofFIG. 5may be performed by a base station (e.g., base station320). In some implementations, one or more process blocks ofFIG. 5may be performed by another device or a group of devices separate from or including the base station, such as a user equipment (UE) (e.g., UE310), a mobility management entity (MME) (e.g., MME330), a serving gateway (SGW) (e.g., SGW340), a packet data network (PDN) gateway (PGW) (e.g., PGW350), a home subscriber server (HSS) (e.g., HSS360), an authentication, authorization, and/or accounting (AAA) server (e.g., AAA server370), and/or the like.

As shown inFIG. 5, process500may include connecting the UE to a network (block510). For example, the base station (e.g., using processor420, memory430, storage component440, input component450, output component340, communication interface340, and/or the like) may connect the UE (e.g., UE310) to a network, as described above.

In some implementations, an attach request message, that is used to connect the UE to the network, may include one or more eligibility parameters for a connection release service. In some implementations, the one or more eligibility parameters may include a device type identifier that identifies a device type of the UE. In some implementations, the one or more eligibility parameters may include a device type category identifier that identifies a category of device type of the UE.

As further shown inFIG. 5, process500may include determining that the UE is to receive the connection release service (block520). For example, the base station (e.g., using processor420, memory430, storage component440, and/or the like) may determine that the UE is to receive the connection release service, as described above.

In some implementations, the base station may determine that the UE is to receive the connection release service based on the one or more eligibility parameters. In some implementations, the base station may determine that the UE is to receive the connection release service based on the one or more eligibility parameters including the device type identifier. In some implementations, the base station may determine that the UE is to receive the connection release service based on the one or more eligibility parameters including the device type category identifier.

In some implementations, while the UE is connected to the network, the base station may receive network performance indicator (NPI) data that identifies one or more NPIs associated with a connection that the UE has to the network. In this case, the base station may determine that the NPI data satisfies one or more threshold NPI values, and may determine that the UE is to receive the connection release service based on determining that the NPI data satisfies the one or more threshold NPI values. In some implementations, the NPI data may include at least one of: signal-to-interference-plus-noise ratio (SINR) data, reference signal received power (RSRP) data, or reference signal received quality (RSRQ) data.

As further shown inFIG. 5, process500may include providing, to the UE, a connection release message that is provided based on determining that the UE is to receive the connection release service (block530). For example, the base station (e.g., using processor420, memory430, storage component440, output component460, communication interface470, and/or the like) may provide, to the UE, a connection release message that is provided based on determining that the UE is to receive the connection release service, as described above. In some implementations, the connection release message may be a radio resource control (RRC) connection release message.

In some implementations (e.g., before providing the connection release message), the base station may associate the connection release message with a network-layer header. In this case, the base station may provide the connection release message, which has been associated with the network-layer header, to the UE.

In some implementations, the base station may retransmit the connection release message to the UE based on a retransmission condition being satisfied. In some implementations, the base station may determine that the retransmission condition has been satisfied a threshold number of times (e.g., based on a threshold number of unsuccessful attempts to transmit and/or retransmit the connection release message to the UE).

As further shown inFIG. 5, process500may include receiving, from the UE, a connection release acknowledgement message that indicates that the connection release message has been received by the UE (block540). For example, the base station (e.g., using processor420, memory430, storage component440, input component450, communication interface470, and/or the like) may receive, from the UE, a connection release acknowledgement message that indicates that the connection release message has been received by the UE, as described above.

In some implementations, the connection release acknowledgement message may be an RRC connection release acknowledgement message. In some implementations, the base station may receive an encapsulated connection release acknowledgement message that has been encapsulated with a network-layer header.

As further shown inFIG. 5, process500may include performing one or more actions associated with changing a state of the UE based on receiving the connection release acknowledgement message (block550). For example, the base station (e.g., using processor420, memory430, storage component440, input component450, output component340, communication interface340, and/or the like) may perform one or more actions associated with changing a state of the UE based on receiving the connection release acknowledgement message, as described above.

In some implementations, the base station may cause resources allocated to the UE to be made available for one or more other UEs (e.g., one or more other UEs310). In some implementations, the base station may update state data that identifies the state of the UE from a first value that identifies the state of the UE to a second value that identifies a new state of the UE. In some implementations, the base station may cause resources allocated to the UE to be made available for one or more other UEs. In some implementations, the base station may perform one or more actions based on determining that the retransmission condition has been satisfied the threshold number of times.