EP4154672A1

EP4154672A1 - Ue-requested cp-pur configuration change

Info

Publication number: EP4154672A1
Application number: EP21729010.5A
Authority: EP
Inventors: Tuomas TIRRONEN; Emre YAVUZ; Mattias BERGSTRÖM
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2020-05-21
Filing date: 2021-05-21
Publication date: 2023-03-29
Also published as: WO2021234666A1

Abstract

According to some embodiments, a method performed by a wireless device includes receiving a control plane preconfigured uplink resource (CP-PUR) configuration. The CP-PUR configuration includes time/frequency resources for PUR uplink occasions. The method further includes determining to transition to connected mode, transmitting a connection request to a network node using the PUR time/frequency resources, and transitioning to connected state.

Description

UE-REQUESTED CP-PUR CONFIGURATION CHANGE

TECHNICAL FIELD

Embodiments of the present disclosure are directed to wireless communications and, more particularly, user equipment (UE) requested control plane preconfigured uplink resource (CP-PUR) configuration change.

BACKGROUND

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

Third Generation Partnership Project (3GPP) specifications includes technologies such as Machine-to-Machine (M2M) and/or Internet of Things (IoT). Recent 3GPP work includes enhancements to support Machine-Type Communications (MTC) with new user equipment (UE) categories (Cat-Mi, Cat- M2), supporting reduced bandwidth of up to 6 and 24 physical resource blocks (PRBs), and Narrowband IoT (NB-IoT) UEs providing a new radio interface (and UE categories Cat-NBl and Cat-NB2).

Long term evolution (LTE) enhancements for MTC may be referred to as “eMTC” or “LTE-M,” including (not limiting) support for bandwidth limited UEs, Cat-Mi, and support for coverage enhancements. This is to separate discussions from NB-IoT, although the supported features are similar on a general level.

Both eMTC and NB-IoT include ‘CIoT EPS UP optimization’ and ‘CIoT EPS CP optimization’ signaling reductions. The former, here referred to as user plane (UP)-solution, enables a UE to resume a previously stored radio resource control (RRC) connection (thus also known as RRC Suspend/Resume). The latter, here referred to as control plane (CP)-solution, enables the transmission of user-plane data over the non-access stratum (NAS) (also referred to as data over NAS (DoNAS)).

There are multiple differences between legacy LTE and the procedures and channels defined for eMTC and for NB-IoT. Some differences include a new physical channel, such as the physical downlink control channels, called MMTC physical downlink control channel (PDCCH) in eMTC and NB-IoT physical downlink control channel (NPDCCH) in NB-IoT, and a new physical random access channel, NPRACH, for NB-IoT.

Another important difference is the coverage level (also known as coverage enhancement level) that these technologies can support. By applying repetitions to the transmitted signals and channels, both eMTC and NB-IoT enable UE operation down to much lower SNR level compared to LTE, i.e. Es/Iot>-15 dB being the lowest operating point for eMTC and NB-IoT which can be compared to - 6 dB Es/IoT for “legacy” LTE.

Some improvements for LTE-M and NB-IoT focus on improving the uplink transmission efficiency and/or UE power consumption by means of transmission in preconfigured resources. For example, improvements in uplink transmission efficiency and/or UE power consumptions include transmission in preconfigured resources in idle and/or connected mode based on SC-FDMA waveform for UEs with a valid timing advance. Preconfigured resources may include both shared and dedicated resources. The improvements may be limited to orthogonal (multi) access schemes.

Regarding preconfigured uplink resource (PUR), 3 GPP Rel-16 may include dedicated PUR (D-PUR) in which a UE is provided with a PUR configuration during an initial radio resource control (RRC) connection and provided with periodic radio resources and parameters to apply when later transmitting with PUR in Idle mode. The restriction on UEs having a valid timing advance described above means that, in practice, UEs need to be stationary to use PUR (or close to). Further, a PUR UE can omit transmitting in up to a number m of its PUR resources before its PUR configuration is implicitly released. Network triggered release of the PUR configuration is also supported in general, if PUR is to be released for other reasons.

PUR can be used with the UP-solution (see above), which is referred to as UP-PUR or with CP-solution (see above), which is referred to as CP-PUR. PUR uplink transmission happens in RRC_IDLE mode. The eNB has an opportunity to move the UE to RRC_CONNECTED mode after receiving the transmission from the UE and replying back with RRC message moving the UE to connected. PUR transmissions do not use random access procedure, i.e., the UE does not send random access preamble and/or receive random access response prior to the PUR uplink transmission, but the uplink transmission is done according to the previously configured time and frequency resources. This configuration is done by RRC protocol and the PUR feature and procedures is mainly controlled by RRC and medium access control (MAC) protocols/layers.

A UE can request PUR configuration when it is in RRC_CONNECTED mode. A UE can request, e.g., change of PUR periodicity or starting time, or request to cancel or release the PUR configuration in UE and eNB using the same message.

For PUR configuration, the eNB configures the dedicated preconfigured uplink resources via RRC dedicated signaling. A UE may perform a D-PUR request/information, if D-PUR is indicated as enabled in the cell. The network makes the decision on the D-PUR configuration. A request/information can include requested transport block size (TBS), requested periodicity, and/or other information.

The eNB can (re)configure and release D-PUR by dedicated RRC signaling. D-PUR configuration is released when the eNB does not detect “m” consecutive UE transmissions. The UE releases the D-PUR when it does a random access (RA) procedure on a new cell. D- PUR configuration can be set up without a pre-defined end (infinite).

The UE may use the D-PUR resource to send RRCConnectionRequest or RRCConnectionResumeRequest to establish or resume RRC connection. The UE may send part of the data using the padding.

For the CP solution, the uplink data are encapsulated as a NAS protocol data unit (PDU) in an uplink RRC message transmitted in the common control channel (CCCH). For the UP solution, the uplink data are transmitted in the dedicated traffic channel (DTCH).

After reception of a D-PUR transmission, the eNB can move the UE to RRC connected by RRCConnectionSetup message or RRCConnectionResume message.

Regarding the D-PUR Request, (re)configuration and release mechanism, a D-PUR request can be sent by a bandwidth limited (BL) UE, a UE in coverage enhancement (CE) or NB-IoT UE, and the UE is capable of D-PUR. A D-PUR request can be sent when the UE is in RRC_CONNECTED. A D-PUR request includes a number of PUR grant occasions requested with possibility to request infinite. A UE can request D-PUR release.

A new RRC message may be used for transmission of PUR request when UE is in RRC_CONNECTED (i.e., not for the cases of sending PUR request during early data transmission (EDT) and during PUR). A UE-specific PUR (re)configuration can be provided while the UE is in RRC_CONNECTED. PUR (re)configuration can be included in RRC Connection Release.

At least the following information can be included in PUR (re)configurations: “m” consecutive missed allocations before release, time alignment timer for idle mode, and reference signal receive power (RSRP) change threshold for serving cell. PUR (re)configuration can be provided in a downlink RRC response message of the D-PUR procedure. PUR can be released explicitly by RRCConnectionRelease message and downlink RRC response message of the D-PUR procedure. A UE is not restricted from initiating RRC Connection for the purpose of sending PUR request (i.e., does not impact legacy RRC Connection Establishment/Resume procedures).

Regarding CP and UP solutions, for PUR transmission and associated response, no new RRC messages are introduced and the existing RRC messages are re-used (S-TMSI and establishment cause for CP, and Resume ID and establishment cause for UP, are mandatory IEs). Existing establishment causes are reused.

A PUR update request is performed only in RRC_CONNECTED (i.e., not included with PUR transmission). This replaces the previous policy for UP regarding piggyback of PUR request with the PUR transmission.

If PUR (re)configuration is provided in RRC Connection release, no additional explicit success/failure indication is used, i.e., existing methods are sufficient. No further UE behavior is specified when successful PUR reconfiguration is not confirmed using the existing methods (i.e., the PUR configuration that the UE considers valid depends on whether UE received the reconfiguration). It is up to the network implementation how to handle this scenario.

The network releases PUR only upon successful confirmation that UE received the release message using the existing methods. A PUR request includes an optional indication that LI ACK is sufficient. The network has the final decision whether to use LI ACK or not.

No new RRC message for PUR release request is used (i.e. PUR configuration request is used for requesting PUR release). “UE is stationary /quasi- stationary” is not a precondition before sending PUR configuration request. “UL data size is limited to maximum supported TBS based on the UE category /capability” is a precondition before sending PUR configuration request.

A UE cannot be configured with more than one PUR configuration. Therefore, PUR config identity /index is not needed in PUR configuration. Information on TBS size is provided in PUR configuration.

For CP, similar to EDT, “the size of the resulting MAC PDU including the total uplink data is expected to be smaller than or equal to the TBS configured for PUR” is a precondition before initiating uplink transmission using PUR. Sending RRC Connection request without the CP data is not excluded due to this.

For UP, refer to PUR messages as “RRCConnectionResumeRequest for PUR” and “RRCConnectionResumeRequest for EDT or PUR” etc. in the specifications.

PUR timing advance (TA) timer is configurable up to hour(s) level, disabled/infinity is possible.

The configuration may include a configurable value of m. If not configured, then release by “m” skip mechanism is disabled a UE may increase ‘m’ when (1) PUR occasion is not used while UE is in RRC_IDLE and (2) PUR occasion is used in RRC_IDLE but no ACK is received. The network may increase ‘m’ when no ACK is sent by the network. The value ‘m’ is not increased (neither by UE nor eNB) while UE is in a dedicated RRC connection. The value of ‘m’ is reset to zero after successful communication between UE and eNB (both in RRC_IDLE or RRC_CONNECTED). The value ‘m’ is not increased (neither by UE nor eNB) while barring timer is running.

A UE may increase ‘m’ when (1) PUR occasion is not used while UE is in RRC_IDLE and (2) PUR occasion is used in RRC_IDLE but no response (none of explicit HARQ ACK/NACK, LI ACK or L2/L3 response) is received. The network may increase ‘m’ when no response corresponding to a PUR occasion (none of explicit HARQ ACK/NACK, LI ACK or L2/L3 response) is sent by the network. The value ‘m’ is not increased (neither by UE nor eNB) while UE is in RRC_CONNECTED. Counter ‘m’ is reset to zero after successful communication between UE and eNB using PUR. Counter ‘m’ is not reset to zero after successful communication between UE (with a valid PUR configuration) and eNB in RRC_CONNECTED. Configurable value of m = {2, 4, 8, spare}.

A PUR configuration request may contain a time offset request, i.e., requested time of the first PUR transmission. A PUR configuration may contain a time offset, i.e., time of the first PUR transmission. For CP solution, eNB stores part of the PUR configuration needed to receive the PUR transmission. Some part of configuration may be in the mobility management entity (MME).

PUR (re-)configuration can be provided to the UE for the CP solution without AS security enabled.

There currently exist certain challenges. For example, it is unknown for CP-PUR how the eNB links the UE and the UE's PUR configuration. One way is to link the UE with the configured time/frequency resources for PUR, i.e., when UE uses its configured time/frequency (t/f) resources, the eNB knows the UEs PUR configuration.

However, in the above case, when a UE initiates RRC_CONNECTION using some other time/frequency resources, e.g., when initiating a normal RRC connection setup procedure or early data transmission, the eNB is not able to link the UE to its PUR configuration. This means that eNB cannot count the 'm' value of skipped PUR occasions while the UE is in RRC_CONNECTED. Also, if the UE sends a RRC message to request change or release of the PUR configuration, the eNB will not know how to map the UE to the correct configuration.

The above is a problem for CP-PUR because there is no explicit identifier that can be used to identify the PUR configuration. For UP-PUR there is no issue because the UE sends resumelD over RRC signaling which the eNB uses to find the UEs radio configuration, i.e., also including PUR configuration.

SUMMARY

Based on the description above, certain challenges currently exist with user equipment (UE) requested control plane preconfigured uplink resource (CP-PUR) configuration change. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments solve the problem with CP-PUR and lack of identifier and ability to map UE to its PUR configuration by requiring the UE to send the message to establish or resume the RRC connection using the time and frequency resource configured for PUR (i.e., using the PUR occasion), rather than some other resources. This way the eNB can link UE and its PUR configuration, thus 'm' counting and PUR configuration request and release procedures will work. However, if the UE is not interested in changing the PUR configuration, the UE may use other resources to send the message for establishing or resuming the RRC connection.

According to some embodiments, a method performed by a wireless device comprises receiving a CP-PUR configuration. The CP-PUR configuration includes time/frequency resources for PUR uplink occasions. The method further comprises determining to transition to connected mode, transmitting a connection request to a network node using the PUR time/frequency resources, and transitioning to connected state.

In particular embodiments, the method further comprises determining to request a PUR configuration change or release and transmitting a PUR request to the network node requesting PUR configuration change or requesting release of its PUR configuration. Determining to request a PUR configuration release may be based on a number of remaining PUR occasions.

In particular embodiments, the method further comprises determining a PUR occasion is not used for PUR transmission and refraining from incrementing a counter for skipped PUR occasions.

According to some embodiments, a method performed by a wireless device comprises receiving a CP-PUR configuration. The CP-PUR configuration includes time/frequency resources for PUR uplink occasions. The method further comprises determining to transition to connected mode, transmitting a connection request to a network node using time/frequency resources other than the PUR time/frequency resources, and transitioning to connected state.

In particular embodiments, the method further comprises determining a PUR occasion is not used for PUR transmission and incrementing a counter for skipped PUR occasions.

According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above. Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless devices described above.

According to some embodiments, a method performed by a network node comprises associating a wireless device with a CP-PUR configuration. The CP-PUR configuration includes time/frequency resources for PUR uplink occasions. The method further comprises receiving a connection request from the wireless device using the PUR time/frequency resources, receiving a request for a PUR configuration change or release from the wireless device, and based on the association between the wireless device and the CP-PUR configuration, changing or releasing the CP-PUR configuration.

According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above.

Certain embodiments may provide one or more of the following technical advantages. For example, some embodiments facilitate properly counting 'm' skipped PUR occasions and/or enable the UE to request, change or release its PUR configuration when the UE is configured with CP PUR, without using a new identifier with CP-PUR procedures and configuration.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which: FIGURE 1 is a flow diagram illustrating an example UE requesting PUR configuration, configuration change or release of PUR configuration;

FIGURE 2 is a flow diagram illustrating an example UE configured with CP-PUR requesting RRC connection setup only using the time and frequency resources configured for PUR transmission;

FIGURE 3 is a flow diagram illustrating an example UE counting 'm' depending on whether the connection request is sent using resources configured for PUR or other resources;

FIGURE 4 is a block diagram illustrating an example wireless network;

FIGURE 5 illustrates an example user equipment, according to certain embodiments;

FIGURES 6A and 6B are flowcharts illustrating example methods in a wireless device, according to certain embodiments;

FIGURE 7 is flowchart illustrating an example method in a network node, according to certain embodiments;

FIGURE 8 illustrates a schematic block diagram of a wireless device and a network node in a wireless network, according to certain embodiments;

FIGURE 9 illustrates an example virtualization environment, according to certain embodiments;

FIGURE 10 illustrates an example telecommunication network connected via an intermediate network to a host computer, according to certain embodiments;

FIGURE 11 illustrates an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments;

FIGURE 12 is a flowchart illustrating a method implemented, according to certain embodiments;

FIGURE 13 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments;

FIGURE 14 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments; and

FIGURE 15 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments. DETAILED DESCRIPTION

As described above, certain challenges currently exist with user equipment (UE) requested control plane preconfigured uplink resource (CP-PUR) configuration change. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments solve the problem with CP-PUR and lack of identifier and ability to map UE to its PUR configuration by requiring the UE to send the message to establish or resume the RRC connection using the time and frequency resource configured for PUR (i.e., using the PUR occasion), rather than some other resources. This way the eNB can link UE and its PUR configuration, thus 'm' counting and PUR configuration request and release procedures will work. However, if the UE is not interested in changing the PUR configuration, the UE may use other resources to send the message for establishing or resuming the RRC connection.

Particular embodiments are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

In particular embodiments, a UE initiates a connection to the network on different types of resources; resources associated with a PUR configuration or other resources, dependent on if the UE wants to change or release a PUR configuration. Multiple candidate messages may be used for initiating a connection with the network. One of those candidates is the RRC resume request message, but for radio access types (RATs) other than long term evolution (LTE) other types of messages may be used. The description of embodiments herein uses terminology for LTE/EPS networks but can be applicable to new radio (NR) and fifth generation system (5GS) as well.

In some embodiments, a UE considers the purpose of connection establishment to select resources used to establish the connection. In particular embodiments, when the UE is configured with CP-PUR, i.e., eNB has provided the UE with a PUR configuration and the UE has an upcoming PUR occasion (time and frequency resources, necessary configuration parameters) configured, and the UE wants to request a change to the PUR configuration, the UE uses its next or a later (see below) PUR occasion to transmit a RRC message which moves the UE into RRC_CONNECTED mode. In RRC connected mode, the UE sends RRC message for requesting PUR configuration.

However, if the UE does not want to perform any change for the PUR configuration, the UE may transmit an RRC message which moves the UE into RRC_CONNECTED mode using other resources than the resources associated with the PUR occasion.

In some embodiments, when the UE is configured with CP-PUR, i.e., eNB has provided it with PUR configuration and the UE has an upcoming PUR occasion (time and frequency resources, necessary configuration parameters) configured, and the UE wants to request a release of the PUR configuration, the UE uses its next or later (see below) PUR occasion to transmit a RRC message which moves the UE into RRC_CONNECTED mode. In RRC connected mode, the UE sends RRC message which indicates the UE wants to release the PUR configuration.

In some embodiments, the UE determines the number of remaining PUR occasions and based on this determines if the UE should request a release of the PUR configuration. If the number of PUR occasions are few (e.g., lower than a threshold) the UE may decide not to send an explicit release of the PUR configuration. This is beneficial because if there is only a few, for example 1, PUR occasion remaining before the PUR configuration will become obsolete/invalid/etc. the UE can instead just refrain from performing a transmission on these (few) remaining PUR occasions and the release will be triggered after them. However, if the number of remaining PUR occasions is greater than a threshold, the UE may explicitly request a release of the PUR configuration. As indicated, this may be determined based on a threshold. The threshold may be configured for the UE by the network. Another approach is that the threshold is determined by the UE itself, e.g., based on implementation.

In both above cases, the eNB is able to connect the UE and its PUR configuration, assuming the eNB has stored a correspondence between UE and its PUR configuration.

As described above, in some embodiments the UE uses the "next or later" PUR occasion if the UE wants to request a change or release of PUR configurations. When the UE determines to request a change or release of the PUR configuration, and the "next" PUR occasion is close in time, the UE may not have time to prepare for and/or initiate transmission of a PUR configuration change/release indication. There is usually a non-negligible processing time for RRC procedures in the UE, e.g., in the order of 10's of milliseconds, and if the UE determines that it wants to change/release a PUR configuration shortly before the next PUR occasion (e.g. less than 10's of milliseconds) the UE may instead send the request for PUR reconfiguration/release in a later (e.g. second-next) PUR occasion. The UE may even wait more than one PUR occasion to send the request for change/release of the PUR configuration based on implementation.

In particular embodiments, the RRC message used to request the PUR configuration is the same message used to request a change in PUR configuration or release of the PUR configuration, e.g. PURConfigurationRequest or PURConfigurationRequest-NB.

Some embodiments include conditional counting of m-counter. As described above, a UE configured with PUR maintains a counter m which counts the number of PUR occasions which the UE has not used to transmit on. If the counter reaches a certain value, the UE considers the PUR configuration no longer applicable/valid. The network can do similar counting in the sense that if the network has not detected any transmission from the UE in a certain number of consecutive PUR occasions, the network may also determine that the PUR configuration is not applicable/valid for the UE. The associated resources may then not be considered allocated for that UE. Further, conventionally the UE does not apply the above type of counting if the UE is in CONNECTED-mode.

In particular embodiments, if the UE initiated a connection to the network using the resources associated with the PUR-configuration, the UE does not count the counter m. However, if the UE has initiated the connection to the network using other resources than those connected to the PUR-configuration, the UE counts the counter m.

If the UE has established a connection to the network on the resources associated with a PUR-configuration, the network can know that the UE is the UE which has been given the PUR configuration. The network can then ensure that it performs the above counting of the counter m for this UE. However, if the UE connects using resources which are not connected to the PUR configuration, the network may not know that this UE is connected to the PUR configuration. Instead the network may believe that the UE which is connected to the PUR resources is outside of CONNECTED mode and therefore the UE would be performing counting of counter m.

The above embodiment therefore ensures that the network and UE counts the counter m in a synchronized manner and thus there will be no misalignment between the counter value the UE and the network maintains.

In some embodiments, a UE considers only PUR resources valid resources for connection. In particular embodiments, a UE configured with CP-PUR is only allowed to go to RRC_CONNECTED mode using the configured PUR occasion and it is not allowed for the UE to request RRC_CONNECTION setup using any other time and frequency resources. This leads to correct counting of 'm' skipped PUR occasions. Additionally, as described above, the UE is able to request PUR configuration change/release only after using the time/frequency resources configured for PUR for requesting RRC connection setup.

FIGURE 1 is a flow diagram illustrating an example UE requesting PUR configuration, configuration change or release of PUR configuration. In particular embodiments, one or more steps of FIGURE 1 may be performed by wireless device 110 described with respect to FIGURE 4.

The method begins at step 103, where the UE (e.g., wireless device 110) is configured with CP-PUR. At step 105, the UE determines that it wants to request a PUR configuration change.

At step 107, when the UE has its opportunity to transmit using PUR, the UE sends an RRC Connection Request to ask for transition to connected mode. When in RRC_CONNECTED, at step 109, the UE sends a PUR request message to eNB/ng-eNB (e.g., network node 160) to ask for PUR configuration change or release. The eNB knows the PUR configuration associated with the UE because the UE used its PUR resources to send the RRC Connection Request.

FIGURE 2 is a flow diagram illustrating an example UE configured with CP-PUR requesting RRC connection setup only using the time and frequency resources configured for PUR transmission. In particular embodiments, one or more steps of FIGURE 2 may be performed by wireless device 110 described with respect to FIGURE 4.

The method begins at step 203, where the UE (e.g., wireless device 110) is configured with CP-PUR. At step 205, the UE determines that it wants to transition to RRC_CONNECTED mode.

At step 207, the UE sends an RRC Connection Request to ask for transition to connected mode only using its configured PUR occasion or resources. At step 209, the UE transitions to RRC_CONNECTED according to received RRC signaling.

FIGURE 3 is a flow diagram illustrating an example UE counting 'm' depending on whether the connection request is sent using resources configured for PUR or other resources. In particular embodiments, one or more steps of FIGURE 3 may be performed by wireless device 110 described with respect to FIGURE 4.

The method begins at step 303, where the UE (e.g., wireless device 110) is configured with CP-PUR. At step 305, the UE determines that it wants to transition to RRC_CONNECTED mode. The UE has the options of sending the connected request using PUR resources or not using PUR resources.

If the UE does not use PUR resources, then the method continues to step 307. At step 307 the UE determines that a current PUR occasion is configured but not used. Because the UE did not use PUR resources to initiate the connection, the UE continues to step 309 where the UE increases the count for skipped PUR occasions.

If at step 305 the UE did use PUR resources to send the connection request then the method continues to step 311. At step 311 the UE determines that a current PUR occasion is configured but not used. Because the UE used PUR resources to initiate the connection, the UE continues to step 313 where the UE does not increase the count for skipped PUR occasions.

FIGURE 4 illustrates an example wireless network, according to certain embodiments. The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 160 and WD 110 comprise various components described in more detail below. These components work together to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.

Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.

A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.

As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In FIGURE 4, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 illustrated in the example wireless network of FIGURE 4 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components.

It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.

Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality.

For example, processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC).

In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160 but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.

Device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170. Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160. Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 may be considered to be integrated.

Interface 190 is used in the wired or wireless communication of signaling and/or data between network node 160, network 106, and/or WDs 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162.

Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 may be considered a part of interface 190. In still other embodiments, interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 192 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.

Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160.

For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further example, power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node 160 may include additional components beyond those shown in FIGURE 4 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.

In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.

Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastmcture (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.

As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).

In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137. WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 110.

Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from WD 110 and be connectable to WD 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface.

As illustrated, interface 114 comprises radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116. Radio front end circuitry 112 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 may be coupled to or a part of antenna 111. In some embodiments, WD 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered a part of interface 114.

Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 110 components, such as device readable medium 130, WD 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 120 of WD 110 may comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips.

In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 122 may be a part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard- wired manner.

In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of WD 110, but are enjoyed by WD 110, and/or by end users and the wireless network generally.

Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120. Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120. In some embodiments, processing circuitry 120 and device readable medium 130 may be integrated.

User interface equipment 132 may provide components that allow for a human user to interact with WD 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to WD 110. The type of interaction may vary depending on the type ofuser interface equipment 132 installed in WD 110. For example, if WD 110 is a smart phone, the interaction may be via a touch screen; if WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).

User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into WD 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from WD 110, and to allow processing circuitry 120 to output information from WD 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, WD 110 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.

Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario. Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 110 which need power from power source 136 to carry out any functionality described or indicated herein. Power circuitry 137 may in certain embodiments comprise power management circuitry.

Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of WD 110 to which power is supplied.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIGURE 4. For simplicity, the wireless network of FIGURE 4 only depicts network 106, network nodes 160 and 160b, and WDs 110, 110b, and 110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 160 and wireless device (WD) 110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

FIGURE 5 illustrates an example user equipment, according to certain embodiments. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 200 may be any UE identified by the 3^rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 200, as illustrated in FIGURE 5, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although FIGURE 5 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In FIGURE 5, UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 213, and/or any other component, or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may use all the components shown in FIGURE 5, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In FIGURE 5, processing circuitry 201 may be configured to process computer instructions and data. Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 200 may be configured to use an output device via input/output interface 205.

An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.

UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200. The input device may include a touch-sensitive or presence- sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence- sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In FIGURE 5, RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 211 may be configured to provide a communication interface to network 243a. Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243a may comprise a Wi-Fi network. Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.

Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.

Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium. In FIGURE 5, processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231. Network 243a and network 243b may be the same network or networks or different network or networks. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near- field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243b may be a cellular network, a Wi-Fi network, and/or a near- field network. Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 200 or partitioned across multiple components of UE 200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Further, processing circuitry 201 may be configured to communicate with any of such components over bus 202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIGURE 6A is a flowchart illustrating an example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 6 A may be performed by wireless device 110 described with respect to FIGURE 4.

The method may begin at step 612, where the wireless device (e.g., wireless device 110) receives a CP-PUR configuration. The CP-PUR configuration includes time/frequency resources for PUR uplink occasions. When in idle mode, the wireless device may use the CP- PUR time/frequency resources for uplink transmission without first performing a random access procedure.

At step 614, the wireless device may determine to request a PUR configuration change or release. For example, the wireless device may have missed a threshold number of PUR occasions, not received acknowledgments for a threshold number of uplink transmissions, or detected a change in signal strength, etc., and determine that a new configuration is needed or to release the configuration.

In some embodiments, even if the wireless device determines to release configuration, the wireless device may decide not to release the configuration based on the number of remaining PUR occasions. For example, if few PUR occasions are remaining, it may be more efficient to let the occasions pass. If many PUR occasions are remaining, the wireless device may determine to release the configuration.

The wireless device cannot request the change or release from idle mode. Accordingly, at step 616 the wireless device determines to transition to connected mode, and at step 618 the wireless device transmits a connection request to a network node using the PUR time/frequency resources. The wireless device uses the PUR time/frequency resources so that the network node can associate the correct CP-PUR configuration with the wireless device.

At step 620, the wireless device transitions to connected state. In the connected state, the wireless device may transmit a PUR request (e.g., RRC request) to the network node requesting PUR configuration change or requesting release of its PUR configuration at step 622.

While in connected mode, at step 624 the wireless device may determine a PUR occasion is not used for PUR transmission. Because the wireless device used the PUR time/frequency resources to connect to the network, at step 626 the network node refrains from incrementing a counter (e.g., m counter) for skipped PUR occasions.

Modifications, additions, or omissions may be made to method 600 of FIGURE 6A. Additionally, one or more steps in the method of FIGURE 6A may be performed in parallel or in any suitable order.

FIGURE 6B is a flowchart illustrating another example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 6B may be performed by wireless device 110 described with respect to FIGURE 4.

The method may begin at step 652, where the wireless device (e.g., wireless device 110) receives a CP-PUR configuration. The CP-PUR configuration includes time/frequency resources for PUR uplink occasions. When in idle mode, the wireless device may use the CP- PUR time/frequency resources for uplink transmission without first performing a random access procedure.

At step 654, the wireless device determines to transition to connected mode. If the wireless device does not intend to request modification of its CP-PUR configuration, then it does not need to use the CP-PUR time/frequency resources. Accordingly, at step 656 the wireless device transmits a connection request to a network node using time/frequency resources other than the PUR time/frequency resources. At step 658, the wireless device transitions to the connected state.

While in connected mode, at step 660 the wireless device may determine a PUR occasion is not used for PUR transmission. Because the wireless device did not use the PUR time/frequency resources to connect to the network, at step 662 the network node increments a counter (e.g., m counter) for skipped PUR occasions.

Modifications, additions, or omissions may be made to method 650 of FIGURE 6B. Additionally, one or more steps in the method of FIGURE 6B may be performed in parallel or in any suitable order.

FIGURE 7 is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 7 may be performed by network node 160 described with respect to FIGURE 4.

The method may begin at step 712, where the network node (e.g., network node 160) associates a wireless device with a CP-PUR configuration. The CP-PUR configuration includes time/frequency resources for PUR uplink occasions.

At step 714, the network node receives a connection request from the wireless device using the PUR time/frequency resources, and at step 716 the network node receives a request for a PUR configuration change or release from the wireless device.

Based on the association between the wireless device and the CP-PUR configuration, at step 718, the network node is able to change or release the CP-PUR configuration.

While the wireless device is in connected mode, the network node may determine, at step 720, that a PUR occasion is not used for PUR transmission. Because the wireless device connected to the network using the PUR time/frequency resources, at step 722 the network node refrains from incrementing a counter for skipped PUR occasions.

Modifications, additions, or omissions may be made to method 700 of FIGURE 7. Additionally, one or more steps in the method of FIGURE 7 may be performed in parallel or in any suitable order.

FIGURE 8 illustrates a schematic block diagram of two apparatuses in a wireless network (for example, the wireless network illustrated in FIGURE 4). The apparatuses include a wireless device and a network node (e.g., wireless device 110 and network node 160 illustrated in FIGURE 4). Apparatuses 1600 and 1700 are operable to carry out the example methods described with reference to FIGURES 6A and 6B and FIGURE 7, respectively, and possibly any other processes or methods disclosed herein. It is also to be understood that the methods of FIGURES 6 A and 6B and FIGURE 7 are not necessarily carried out solely by apparatuses 1600 and/or 1700. At least some operations of the methods can be performed by one or more other entities.

Virtual apparatuses 1600 and 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.

In some implementations, the processing circuitry may be used to cause receiving module 1602, determining module 1604, transmitting module 1606, and any other suitable units of apparatus 1600 to perform corresponding functions according one or more embodiments of the present disclosure. Similarly, the processing circuitry described above may be used to cause receiving module 1702, determining module 1704, transmitting module 1706, and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in FIGURE 8, apparatus 1600 includes receiving module 1602 configured to receive CP-PUR configuration according to any of the embodiments and examples described herein. Determining module 1604 is configured to determine whether to transition to connected mode, whether to request a change or release of CP-PUR configuration, which time/frequency resources to use for the transition, and whether to increment a counter for skipped PUR occasions, according to any of the embodiments and examples described herein. Transmitting module 1606 is configured to transmit connection requests, CP-PUR change or release requests, according to any of the embodiments and examples described herein.

As illustrated in FIGURE 8, apparatus 1700 includes receiving module 1702 configured to receive connection requests from a wireless device according to any of the embodiments and examples described herein. Determining module 1704 is configured to CP-PUR configuration associated with a wireless device and whether to increment a counter for skipped PUR occasions according to any of the embodiments and examples described herein. Transmitting module 1706 is configured to transmit control and/or data, such as a CP-PUR configuration to a wireless device, according to any of the embodiments and examples described herein.

FIGURE 9 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 300, comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360. Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.

During operation, processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.

As shown in FIGURE 9, hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high- volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 340 on top of hardware networking infrastructure 330 and corresponds to application 320 in Figure 18.

In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225. Radio units 3200 may communicate directly with hardware nodes 330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signaling can be effected with the use of control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.

With reference to FIGURE 10, in accordance with an embodiment, a communication system includes telecommunication network 410, such as a 3GPP-type cellular network, which comprises access network 411, such as a radio access network, and core network 414. Access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c. A second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 412. Telecommunication network 410 is itself connected to host computer 430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 430 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider. Connections 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420. Intermediate network 420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 420, if any, may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).

The communication system of FIGURE 10 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430. The connectivity may be described as an over-the-top (OTT) connection 450. Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signaling via OTT connection 450, using access network 411, core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries. OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of uplink and downlink communications. For example, base station 412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, base station 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.

FIGURE 11 illustrates an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments. Example implementations, in accordance with an embodiment of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIGURE 11. In communication system 500, host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500. Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities. In particular, processing circuitry 518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518. Software 511 includes host application 512. Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 may provide user data which is transmitted using OTT connection 550.

Communication system 500 further includes base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530. Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in FIGURE 11) served by base station 520. Communication interface 526 may be configured to facilitate connection 560 to host computer 510. Connection 560 may be direct, or it may pass through a core network (not shown in FIGURE 11) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 525 of base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 520 further has software 521 stored internally or accessible via an external connection.

Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a base station serving a coverage area in which UE 530 is currently located. Hardware 535 of UE 530 further includes processing circuitry 538, which may comprise one or more programmable processors, application- specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538. Software 531 includes client application 532. Client application 532 may be operable to provide a service to a human or non-human user via UE 530, with the support of host computer 510. In host computer 510, an executing host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the user, client application 532 may receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 may transfer both the request data and the user data. Client application 532 may interact with the user to generate the user data that it provides.

It is noted that host computer 510, base station 520 and UE 530 illustrated in FIGURE 11 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 9, respectively. This is to say, the inner workings of these entities may be as shown in FIGURE 11 and independently, the surrounding network topology may be that of FIGURE 9.

In FIGURE 11, OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via base station 520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., based on load balancing consideration or reconfiguration of the network).

Wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve the signaling overhead and reduce latency, which may provide faster internet access for users. A measurement procedure may be provided for monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 550 between host computer 510 and UE 530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or supplying values of other physical quantities from which software 511, 531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 520, and it may be unknown or imperceptible to base station 520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 550 while it monitors propagation times, errors etc.

FIGURE 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 10 and 11. For simplicity of the present disclosure, only drawing references to FIGURE 12 will be included in this section.

In step 610, the host computer provides user data. In substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIGURE 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 10 and 11. For simplicity of the present disclosure, only drawing references to FIGURE 13 will be included in this section.

In step 710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

FIGURE 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 10 and 11. For simplicity of the present disclosure, only drawing references to FIGURE 14 will be included in this section.

In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally, or alternatively, in step 820, the UE provides user data. In substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application. In substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 830 (which may be optional), transmission of the user data to the host computer. In step 840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure. FIGURE 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 10 and 11. For simplicity of the present disclosure, only drawing references to FIGURE 15 will be included in this section.

In step 910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Modifications, additions, or omissions may be made to the systems and apparatuses disclosed herein without departing from the scope of the invention. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document, “each” refers to each member of a set or each member of a subset of a set.

Modifications, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the invention. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation .

References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s). lx RTT CDMA2000 lx Radio Transmission Technology

3 GPP 3rd Generation Partnership Project

5G 5th Generation

ACK/NACK Ackno wledgment/N on- acknowledgment

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CBRA Contention-Based Random Access

CC Carrier Component

CDMA Code Division Multiplexing Access

CFRA Contention-Free Random Access CG Configured Grant

CGI Cell Global Identifier

CP Cyclic Prefix

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DCI Downlink Control Information

DFTS-OFDM Discrete Fourier Transform Spread OFDM

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

E-CID Enhanced Cell-ID (positioning method)

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH enhanced Physical Downlink Control Channel

E-SMLC evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

FDD Frequency Division Duplex

GERAN GSM EDGE Radio Access Network gNB Base station in NR

GNSS Global Navigation Satellite System

GSM Global System for Mobile communication

HO Handover

HSPA High Speed Packet Access

HRPD High Rate Packet Data

IAB Integrated Access and Backhaul LOS Line of Sight

LTE Long-Term Evolution

MAC Medium Access Control

MCS Modulation and Coding Scheme

MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity

MSC Mobile Switching Center

NPDCCH Narrowband Physical Downlink Control Channel

NR New Radio

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OSS Operations Support System

OTDOA Observed Time Difference of Arrival

O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PDCCH Physical Downlink Control Channel

PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PLMN Public Land Mobile Network

PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUR Preconfigured Uplink Resources

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RA Random Access RAN Radio Access Network

RAT Radio Access Technology

RLF Radio Link Failure

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR Reference Signal Received Power

RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality

RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information

SIB System Information Block

SNR Signal to Noise Ratio

SON Self Optimized Network

SPS Semi-Persistent Scheduling

SUL Supplemental Uplink ss Synchronization Signal

SSB Synchronization Signal Block sss Secondary Synchronization Signal

TA Timing Advance

TDD Time Division Duplex TDOA Time Difference of Arrival

TO Transmission Occasion

TOA Time of Arrival

TSS Tertiary Synchronization Signal TTI Transmission Time Interval

UE User Equipment UL Uplink

URLLC Ultra-Reliable and Low-Latency Communications UMTS Universal Mobile Telecommunication System USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network WCDMA Wide CDMA WLAN Wide Local Area Network

Claims

CLAIMS:

1. A method performed by a wireless device, the method comprising: receiving (612) a control plane preconfigured uplink resource (CP-PUR) configuration, the CP-PUR configuration including time/frequency resources for PUR uplink occasions; determining (616) to transition to connected mode; transmitting (618) a connection request to a network node using the PUR time/frequency resources; and transitioning (620) to connected state.

2. The method of claim 1, further comprising: determining (614) to request a PUR configuration change or release; and transmitting (622) a PUR request to the network node requesting PUR configuration change or requesting release of its PUR configuration.

3. The method of claim 2, wherein determining to request a PUR configuration release is based on a number of remaining PUR occasions.

4. The method of any one of claims 1-3, further comprising: determining (624) a PUR occasion is not used for PUR transmission; and refraining (626) from incrementing a counter for skipped PUR occasions.

5. A wireless device (110) comprising processing circuitry (120) operable to: receive a control plane preconfigured uplink resource (CP-PUR) configuration, the CP-

PUR configuration including time/frequency resources for PUR uplink occasions; determine to transition to connected mode; transmit a connection request to a network node (160) using the PUR time/frequency resources; and transition to connected state.

6. The wireless device of claim 5, the processing circuitry further operable to: determine to request a PUR configuration change or release; and transmit a PUR request to the network node requesting PUR configuration change or requesting release of its PUR configuration.

7. The wireless device of claim 6, wherein the processing circuitry is operable to determine to request a PUR configuration release based on a number of remaining PUR occasions.

8. The wireless device of any one of claims 5-7, the processing circuitry further operable to: determine a PUR occasion is not used for PUR transmission; and refrain from incrementing a counter for skipped PUR occasions.

9. A method performed by a wireless device, the method comprising: receiving (652) a control plane preconfigured uplink resource (CP-PUR) configuration, the CP-PUR configuration including time/frequency resources for PUR uplink occasions; determining (654) to transition to connected mode; transmitting (656) a connection request to a network node using time/frequency resources other than the PUR time/frequency resources; and transitioning (658) to connected state.

10. The method of claim 9, further comprising: determining (660) a PUR occasion is not used for PUR transmission; and incrementing (662) a counter for skipped PUR occasions.

11. A wireless device (110) comprising processing circuitry (120) operable to: receive a control plane preconfigured uplink resource (CP-PUR) configuration, the CP-

PUR configuration including time/frequency resources for PUR uplink occasions; determine to transition to connected mode; transmitting a connection request to a network node using time/frequency resources other than the PUR time/frequency resources; and transition to connected state.

12. The wireless device of claim 11, the processing circuitry further operable to: determine a PUR occasion is not used for PUR transmission; and increment a counter for skipped PUR occasions.

13. A method performed by a network node, the method comprising: associating (712) a wireless device with a control plane preconfigured uplink resource

(CP-PUR) configuration, the CP-PUR configuration including time/frequency resources for PUR uplink occasions; receiving (714) a connection request from the wireless device using the PUR time/frequency resources; receiving (716) a request for a PUR configuration change or release from the wireless device; and based on the association between the wireless device and the CP-PUR configuration, changing or releasing (718) the CP-PUR configuration.

14. The method of claim 13, further comprising: determining (720) a PUR occasion is not used for PUR transmission; and refraining (722) from incrementing a counter for skipped PUR occasions.

15. A network node (160) comprising processing circuitry ( 170) operable to: associate a wireless device with a control plane preconfigured uplink resource (CP-

PUR) configuration, the CP-PUR configuration including time/frequency resources for PUR uplink occasions; receive a connection request from the wireless device using the PUR time/frequency resources; receive a request for a PUR configuration change or release from the wireless device; and based on the association between the wireless device and the CP-PUR configuration, change or release (718) the CP-PUR configuration.

16. The network node of claim 15, the processing circuitry further operable to: determine a PUR occasion is not used for PUR transmission; and refrain from incrementing a counter for skipped PUR occasions.