WO2024241179A1 - Methods for threshold modification for multiple prach transmissions - Google Patents

Abstract

In an embodiment of the present disclosure, a method performed by a User Equipment device (UE) is provided for modifying a procedure for multiple physical random access channel (PRACH) transmissions. The method includes obtaining a first parameter from a network wherein the first parameter is related to modifying a multiple PRACH transmission procedure, wherein the first parameter specifies a number of failed attempts that are allowed before modifying the multiple PRACH transmission procedure. The method also includes attempting a plurality of PRACH transmissions, wherein each of the plurality of PRACH transmissions failed and upon determining that a number of failed PRACH transmissions exceeds the first parameter, modifying the multiple PRACH transmission procedure.

Description

METHODS FOR THRESHOLD MODIFICATION FOR MULTIPLE PRACH TRANSMISSIONS

Related Applications

[0001] This application claims the benefit of provisional patent application serial number 63/467,762, filed May 19, 2023, the disclosure of which is hereby incorporated herein by reference in its entirety.

Technical Field

[0002] The present disclosure relates to methods for modifying a procedure for multiple Physical Random Access Channel (PRACH) transmissions performed by a User Equipment device (UE) and a network node and a UE and network node configured to perform the same.

Background

Coverage Enhancements in standardization

[0003] Coverage Enhancements have been introduced to Third Generation Partnership Program (3GPP) New Radio (NR) Rel-17 and 18 in several enhancements. One of these is repetitions of UL channels over several occasions, to enhance the chance of successful reception in the gNB. One of the identified bottlenecks is the Random Access Channel (RACH) procedure, with the messages transmitted from the UE as the main problems, see Figure 1. Figure 1 illustrates a 4-step Contention Based Random Access (CBRA) procedure that is taken from European Telecommunications Standards Institute (ETSI) 3GPP TS 38.300 V17.4.0 Section 9.2.6-1 A, with 4 messages sent between a UE and a gNB (e.g., a network node).

[0004] 3GPP Release 17 introduced repetitions of msg3 of the 4-step CBRA procedure, and Rel-18 aims to introduce repetitions for msgl. These repetitions are known as Multiple Physical RACH (PRACH) Transmissions (MuPT). According to agreements in RANI who leads the work item, the following has been decided: “For multiple PRACH transmissions with same Transmit (Tx) beam, at least Synchronization Signal (SS) Physical Broadcast Channel (PBCH) (SSB) Reference Signal Received Power (RSRP) threshold(s) are used to determine the number of PRACH transmissions at least for the first RACH attempt. Note: whether to support multiple numbers of PRACH transmissions is separately discussed.”

[0005] It has also been agreed in Radio Access Network 1 (RANI) that the number of transmissions will be 2, 4 or 8 (known as repetition factor). In particular it has been agreed that Support {2, 4, 8} for the number of multiple PRACH transmissions with same Tx beams. With this in mind, it is likely that for RSRP, all UEs in the SSB will use the same threshold values for MuPT repetition factor decision, distributed through System Information.

[0006] If the Random Access (RA) procedure is not successful (i.e. no msg2 received), there are now discussions whether or not the UE can increase the repetition factor, however no agreements in this case have been made in 3GPP. Two main views exist here; either the UE increases the repetition factor, or the UE modifies the RSRP measurements received.

Coverage Enhancements use cases

[0007] The use cases for coverage enhancements spans many different scenarios, all covering poor radio conditions. One of these use cases is believed to be Internet Of Things (loT) Devices reporting measurement data at sporadic times. These devices are often electricity meters, water reporting devices or other equipment placed in basements, or in close proximity of other devices that can cause high interference.

Summary

[0008] In an embodiment of the present disclosure, a method performed by a User Equipment device (UE) is provided for modifying a procedure for multiple physical random access channel (PRACH) transmissions. The method includes obtaining a first parameter from a network wherein the first parameter is related to modifying a multiple PRACH transmission procedure, wherein the first parameter specifies a number of failed attempts that are allowed before modifying the multiple PRACH transmission procedure. The method also includes attempting a plurality of PRACH transmissions, wherein each of the plurality of PRACH transmissions failed and upon determining that a number of failed PRACH transmissions exceeds the first parameter, modifying the multiple PRACH transmission procedure.

[0009] In an embodiment, the method further includes obtaining a second parameter from the network, and a second parameter that specifies a penalty to be applied should the number of failed attempts exceed the first parameter.

[0010] In an embodiment, the modifying the multiple PRACH transmission procedure comprises applying the penalty based on the second parameter.

[0011] In an embodiment, the penalty results in a reduction to a derived reference signal received power, RSRP, value associated with a reference signal from the network.

[0012] In an embodiment, the first and second parameters comprise a plurality of first and second parameters wherein a first repetition factor has a different first and/or second parameter compared to a second repetition factor. [0013] In an embodiment, the method includes obtaining a third parameter that specifies an additional configuration for PRACH attempts made after the penalty is applied.

[0014] In an embodiment, the first parameter comprises a series of parameters each associated with a respective repetition factor, each parameter of the series of parameters indicating a number of failed attempts on each repetition factor before modifying the multiple PRACH transmission procedure.

[0015] In an embodiment, the method includes upon successfully performing a PRACH transmission, transmitting a report to a network node, the report specifying information related to the plurality of failed PRACH transmissions.

[0016] In an embodiment, a UE is provided that is configured to modify a procedure for multiple PRACH transmissions, where the UE comprises a processor that causes the UE to obtain a first parameter from a network wherein the first parameter is related to modifying a multiple PRACH transmission procedure, wherein the first parameter specifies a number of failed attempts that are allowed before modifying the multiple PRACH transmission procedure, attempt a plurality of PRACH transmissions, wherein each of the plurality of PRACH transmissions failed and upon determining that a number of failed PRACH transmissions exceeds the first parameter, modify the multiple PRACH transmission procedure.

[0017] In an embodiment, a method performed by a network node for modifying the threshold for multiple PRACH transmission is provided where the method includes providing a UE with a first parameter, wherein the first parameter is related to modifying a multiple PRACH transmission procedure, wherein the first parameter specifies a number of failed attempts that are allowed before modifying the multiple PRACH transmission procedure.

[0018] In an embodiment, the method includes providing the UE with a second parameter, wherein the second parameter specifies a penalty to be applied should the number of failed attempts exceed the first parameter.

[0019] In an embodiment, the first and second parameters comprise a plurality of first and second parameters wherein a first repetition factor has a different first and/or second parameter compared to a second repetition factor.

[0020] In an embodiment, the penalty results in a reduction to a derived reference signal received power, RSRP, value associated with a reference signal from the network node.

[0021] In an embodiment, the method includes providing a third parameter that specifies an additional configuration for PRACH attempts made after the penalty is applied.

[0022] In an embodiment, the first parameter comprises a series of parameters each associated with a respective repetition factor, each parameter of the series of parameters indicating a number of failed attempts on each repetition factor before modifying the multiple PRACH transmission procedure.

[0023] In an embodiment, the method includes receiving from the UE a report, the report specifying information related to the plurality of failed PRACH transmissions.

[0024] In an embodiment, a network node is provided that is configured to modify a procedure for multiple PRACH transmissions. The network includes a processor that causes the network node to provide a UE with a first parameter, wherein the first parameter is related to modifying a multiple PRACH transmission procedure, wherein the first parameter specifies a number of failed attempts that are allowed before modifying the multiple PRACH transmission procedure.

[0025] Certain embodiments may provide one or more of the following technical advantage(s). For example, by applying penalties to the RSRP threshold based on failed attempts, the behavior of the UE will be predictable and also possible to steer from the network level, while still reusing the benefits of thresholds.

Brief Description of the Drawings

[0026] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0027] Figure 1 illustrates a four step Contention-Based Random Access (CBRA) procedure according to one or more embodiments of the present disclosure;

[0028] Figure 2 illustrates example of how different repetitions are used for signals from a network node with varying Reference Signal Received Power (RSRP) according to one or more embodiments of the present disclosure;

[0029] Figure 3 illustrates a flowchart of a method for modifying a procedure for multiple physical random access channel (PRACH) transmissions according to one or more embodiments of the present disclosure;

[0030] Figure 4 shows an example of a communication system in accordance with some embodiments;

[0031] Figure 5 shows a UE in accordance with some embodiments;

[0032] Figure 6 shows a network node in accordance with some embodiments;

[0033] Figure 7 is a block diagram of a host in accordance with some embodiments; [0034] Figure 8 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized in accordance with some embodiments; and

[0035] Figure 9 shows a communication diagram of a host in accordance with some embodiments.

Detailed Description

[0036] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0037] There currently exist certain challenge(s). In particular, the Reference Signal Received Power (RSRP) just corresponds to the transmitted signal strength from the gNB, reduced by the attenuation towards the User Equipment device (UE). When the UE transmits back to the gNB, there might be interference which is not then included in the selection of a repetition factor. For this reason, the gNB might not be able to decode the random access from the UE, even though repetitions have been used. It is reasonable to believe that after a number of failed attempts, the UE could try with more repetitions, to see if the gNB can detect the random access. The question is how this ramping of the repetitions should be done.

[0038] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, with certain embodiments the UE would read cell specific information in the system information, including a number of parameters on how to handle failed attempts for the use of multiple Physical Random Access Channel (PRACH) transmissions (msgl repetitions). The information could include (but is not limited to): a threshold penalty which the UE would apply as a penalty to the detected threshold of the gNB ; or a parameter indicating how many failed attempts the UE can make before applying the penalty. With certain embodiments, the UE reads information from the network on how to handle failed Random Access (RA) attempts for multiple PRACH Transmissions. The UE may then make at least one failed attempt for random access with multiple PRACH transmissions. The UE may apply the configuration, modifying the input to the RSRP value it has derived. The number of repetitions eventually changing based on the penalty applied. [0039] Certain embodiments may provide one or more of the following technical advantage(s). For example, by applying penalties to the RSRP threshold based on failed attempts, the behavior of the UE will be predictable and also possible to steer from the network level, while still reusing the benefits of thresholds.

[0040] In some embodiments, the network/gNB configures multiple parameters that that the UE can use with respect to PRACH transmissions. One parameter is the number of failed attempts (N) before applying a penalty. The second parameter is the actual penalty (P). This means, for example, that after N failed attempts, the UE will apply the penalty P to the RSRP it has derived. An example of this would be after 2 failed attempts, apply -2 dB to the received signal strength (RSRP). In some embodiments, separate values of N and P may be used for each repetition factor (K) that is used in the cell.

[0041] In some embodiments, the network may also configure a parameter indicating how failed attempts after applying the penalty should be treated. This would enable the UE to do quicker application of the penalty/ramping of repetitions if they are not detected at the gNB side after the penalty has been applied. In particular embodiments, the number of failed attempts may be a series of N values, corresponding to each repetition factor. This would mean that Ni, N2, N4 would be sent and indicate how many failed attempts that are required on each K before the penalty is applied.

[0042] In some embodiments, the UE reads the configuration information and, after N failed RA attempts, applies the penalty P to the derived RSRP value. This means it might, or might not, reach another RSRP threshold. This means the UE might increase the repetitions (if it has reached a new threshold) or stay on the same repetition factor. After N new failed attempts (or fewer as depending on the embodiment) the penalty will once again be added, thus moving further towards a new threshold value.

[0043] In some embodiments, after a successful RA procedure, the UE may transmit information indicating the applied penalties to the network. This may allow the UE to make the network aware of the number of attempts performed. In some embodiments the network may also apply individual RSRP thresholds to the UE. In some embodiments, the network may configure individual N and P values based on previous successful attempts from the random access procedure.

[0044] Figure 2 depicts an example of how different repetitions are used for signals from a network node with varying RSRP. For example, there can be no repetitions if a RSRP (measured in dB, where a higher dB is a weaker signal) is below a first threshold, 2 repetitions for an RSRP between the first and a second threshold, 4 repetitions for an RSRP between a second threshold and a third threshold, and 8 repetitions above the third threshold. For a detected RSRP, if a penalty is applied, it can increase the detected rsrp, resulting in possible an increased number of repetitions.

[0045] Figure 3 depicts a method in accordance with particular embodiments. For purposes of simplifying the discussion, the steps performed by a user equipment (noted with a “(UE)” following the reference number) and a network node (noted with a “(NN)” following the reference number) have been combined in the above flow chart. Thus, neither a user equipment nor a network node will perform all the steps of Figure 3. As depicted, the method begins at step 310 where the network node provides the UE with at least first and second parameters. The first parameter may relate to the number of failed PRACH attempts the UE is allowed to have before applying a penalty. The second parameter may relate to the penalty the UE is to apply after experiencing the first parameter number of failed attempts. In some embodiments, the UE may obtain multiple instances of the first and/or the second parameters. This may allow for different parameters to be applied to different repetition factors. In some embodiments, the network noOde may provide a third parameter that specifies additional configuration for PRACH attempts made after the second parameter has been applied (i.e., after the penalty has been applied).

[0046] At step 315 the UE obtains at least the first and second parameters from the network node. Although in this example, the network node is providing the parameters to the UE, in other embodiments or scenarios the UE may have the parameters pre-coded (e.g., they may be specified by the applicable standard) or the UE may determine the parameters from lookup table or determine them based on some set of factors.

[0047] At step 320 the UE attempts a PRACH transmission that fails. If the UE has not attempted the first parameter number of times, the UE will try again. However, at step 325 UE, if the UE has attempted the first parameter number of times, then the UE applies the second parameter. The second parameter may be a penalty related to the RSRP.

[0048] If the UE is successful in a PRACH transmission after having multiple failed attempts, the UE may, at step 303 transmit a report to the network node that specifies information related to the plurality of failed PRACH transmissions. This report is received by the network node at step 335.

[0049] At step 340, the UE provides user data (e.g., a request for data based on user input). At step 345 the UE forwards the user data to a host computer via the network node. At step 350 the network node obtains the user data. At step 355 the network node then forwards the user data to the host computer. User data can also flow in the opposite direction in which the network node obtains user data and then forwards the data to the UE. [0050] Figure 4 shows an example of a communication system 400 in accordance with some embodiments.

[0051] In the example, the communication system 400 includes a telecommunication network 402 that includes an access network 404, such as a radio access network (RAN), and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes, such as network nodes 410a and 410b (one or more of which may be generally referred to as network nodes 410), or any other similar 3^rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 412a, 412b, 412c, and 412d (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections. The network node 410 and one or more of the UEs 412 can be configured to perform the embodiments of the method described in Figure 3.

[0052] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 400 may include any number of wired or wireless networks, network nodes, UEs, 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. The communication system 400 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

[0053] The UEs 412 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 410 and other communication devices. Similarly, the network nodes 410 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 412 and/or with other network nodes or equipment in the telecommunication network 402 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 402.

[0054] In the depicted example, the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 406 includes one more core network nodes (e.g., core network node 408) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 408. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

[0055] The host 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and/or the telecommunication network 402 and may be operated by the service provider or on behalf of the service provider. The host 416 may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0056] As a whole, the communication system 400 of Figure 4 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Fong Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0057] In some examples, the telecommunication network 402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunications network 402 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs. [0058] In some examples, the UEs 412 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0059] In the example, the hub 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE 412c and/or 412d) and network nodes (e.g., network node 410b). In some examples, the hub 414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 414 may be a broadband router enabling access to the core network 406 for the UEs. As another example, the hub 414 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 410, or by executable code, script, process, or other instructions in the hub 414. As another example, the hub 414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 414 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 414 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0060] The hub 414 may have a constant/persistent or intermittent connection to the network node 410b. The hub 414 may also allow for a different communication scheme and/or schedule between the hub 414 and UEs (e.g., UE 412c and/or 412d), and between the hub 414 and the core network 406. In other examples, the hub 414 is connected to the core network 406 and/or one or more UEs via a wired connection. Moreover, the hub 414 may be configured to connect to an M2M service provider over the access network 404 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 410 while still connected via the hub 414 via a wired or wireless connection. In some embodiments, the hub 414 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 410b. In other embodiments, the hub 414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 410b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

[0061] Figure 5 shows a UE 500 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

[0062] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a 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).

[0063] The UE 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input/output interface 506, a power source 508, a memory 510, a communication interface 512, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 5. 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.

[0064] The processing circuitry 502 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 510. The processing circuitry 502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, 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 502 may include multiple central processing units (CPUs).

[0065] In the example, the input/output interface 506 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include 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. An input device may allow a user to capture information into the UE 500. Examples of an input device 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, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. [0066] In some embodiments, the power source 508 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 508 may further include power circuitry for delivering power from the power source 508 itself, and/or an external power source, to the various parts of the UE 500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 508.

Power circuitry may perform any formatting, converting, or other modification to the power from the power source 508 to make the power suitable for the respective components of the UE 500 to which power is supplied.

[0067] The memory 510 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 510 includes one or more application programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516. The memory 510 may store, for use by the UE 500, any of a variety of various operating systems or combinations of operating systems.

[0068] The memory 510 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), 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 tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 510 may allow the UE 500 to access instructions, application programs and 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 as or in the memory 510, which may be or comprise a device -readable storage medium.

[0069] The processing circuitry 502 may be configured to communicate with an access network or other network using the communication interface 512. The communication interface 512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 522. The communication interface 512 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 518 and/or a receiver 520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., antenna 522) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0070] In the illustrated embodiment, communication functions of the communication interface 512 may include cellular communication, Wi-Fi communication, LPWAN communication, 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. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. [0071] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 512, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0072] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0073] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 500 shown in Figure 5.

[0074] As yet another specific example, in an loT scenario, a UE 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 UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

[0075] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0076] Figure 6 shows a network node 600 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication 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)).

[0077] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may 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). [0078] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, 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), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

[0079] The network node 600 includes a processing circuitry 602, a memory 604, a communication interface 606, and a power source 608. The network node 600 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 the network node 600 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 NodeBs. In such a scenario, each unique NodeB and RNC pair may in some instances be considered a single separate network node. In some embodiments, the network node 600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 604 for different RATs) and some components may be reused (e.g., a same antenna 610 may be shared by different RATs). The network node 600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) 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 600.

[0080] The processing circuitry 602 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 600 components, such as the memory 604, to provide network node 600 functionality.

[0081] In some embodiments, the processing circuitry 602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 602 includes one or more of radio frequency (RF) transceiver circuitry 612 and baseband processing circuitry 614. In some embodiments, the radio frequency (RF) transceiver circuitry 612 and the baseband processing circuitry 614 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 612 and baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units.

[0082] The memory 604 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 the processing circuitry 602. The memory 604 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 602 and utilized by the network node 600. The memory 604 may be used to store any calculations made by the processing circuitry 602 and/or any data received via the communication interface 606. In some embodiments, the processing circuitry 602 and memory 604 is integrated.

[0083] The communication interface 606 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 606 comprises port(s)/terminal(s) 616 to send and receive data, for example to and from a network over a wired connection. The communication interface 606 also includes radio front-end circuitry 618 that may be coupled to, or in certain embodiments a part of, the antenna 610. Radio front-end circuitry 618 comprises filters 620 and amplifiers 622. The radio front-end circuitry 618 may be connected to an antenna 610 and processing circuitry 602. The radio front-end circuitry may be configured to condition signals communicated between antenna 610 and processing circuitry 602. The radio front-end circuitry 618 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 620 and/or amplifiers 622. The radio signal may then be transmitted via the antenna 610. Similarly, when receiving data, the antenna 610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 618. The digital data may be passed to the processing circuitry 602. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0084] In certain alternative embodiments, the network node 600 does not include separate radio front-end circuitry 618, instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612, as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown).

[0085] The antenna 610 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 610 may be coupled to the radio front-end circuitry 618 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 610 is separate from the network node 600 and connectable to the network node 600 through an interface or port.

[0086] The antenna 610, communication interface 606, and/or the processing circuitry 602 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 610, the communication interface 606, and/or the processing circuitry 602 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

[0087] The power source 608 provides power to the various components of network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein. For example, the network node 600 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 608. As a further example, the power source 608 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0088] Embodiments of the network node 600 may include additional components beyond those shown in Figure 6 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, the network node 600 may include user interface equipment to allow input of information into the network node 600 and to allow output of information from the network node 600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 600.

[0089] Figure 7 is a block diagram of a host 700, which may be an embodiment of the host 416 of Figure 4, in accordance with various aspects described herein. As used herein, the host 700 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 700 may provide one or more services to one or more UEs.

[0090] The host 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input/output interface 706, a network interface 708, a power source 710, and a memory 712. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 5 and 6, such that the descriptions thereof are generally applicable to the corresponding components of host 700.

[0091] The memory 712 may include one or more computer programs including one or more host application programs 714 and data 716, which may include user data, e.g., data generated by a UE for the host 700 or data generated by the host 700 for a UE. Embodiments of the host 700 may utilize only a subset or all of the components shown. The host application programs 714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 714 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 700 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 714 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. [0092] Figure 8 is a block diagram illustrating a virtualization environment 800 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 any device described herein, 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. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0093] Applications 802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

[0094] Hardware 804 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 808a and 808b (one or more of which may be generally referred to as VMs 808), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 806 may present a virtual operating platform that appears like networking hardware to the VMs 808.

[0095] The VMs 808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 806. Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of VMs 808, and the implementations may be made in different ways. 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. [0096] In the context of NFV, a VM 808 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 the VMs 808, and that part of hardware 804 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 808 on top of the hardware 804 and corresponds to the application 802.

[0097] Hardware 804 may be implemented in a standalone network node with generic or specific components. Hardware 804 may implement some functions via virtualization.

Alternatively, hardware 804 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 810, which, among others, oversees lifecycle management of applications 802. In some embodiments, hardware 804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes 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 provided with the use of a control system 812 which may alternatively be used for communication between hardware nodes and radio units.

[0098] Figure 9 shows a communication diagram of a host 902 communicating via a network node 904 with a UE 906 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 412a of Figure 4 and/or UE 500 of Figure 5), network node (such as network node 410a of Figure 4 and/or network node 600 of Figure 6), and host (such as host 416 of Figure 4 and/or host 700 of Figure 7) discussed in the preceding paragraphs will now be described with reference to Figure 9.

[0099] Eike host 700, embodiments of host 902 include hardware, such as a communication interface, processing circuitry, and memory. The host 902 also includes software, which is stored in or accessible by the host 902 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 906 connecting via an over-the-top (OTT) connection 950 extending between the UE 906 and host 902. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 950. [0100] The network node 904 includes hardware enabling it to communicate with the host 902 and UE 906. The connection 960 may be direct or pass through a core network (like core network 406 of Figure 4) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0101] The UE 906 includes hardware and software, which is stored in or accessible by UE 906 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 906 with the support of the host 902. In the host 902, an executing host application may communicate with the executing client application via the OTT connection 950 terminating at the UE 906 and host 902. In providing the service to the user, the UE’s client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 950 may transfer both the request data and the user data. The UE’s client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 950.

[0102] The OTT connection 950 may extend via a connection 960 between the host 902 and the network node 904 and via a wireless connection 970 between the network node 904 and the UE 906 to provide the connection between the host 902 and the UE 906. The connection 960 and wireless connection 970, over which the OTT connection 950 may be provided, have been drawn abstractly to illustrate the communication between the host 902 and the UE 906 via the network node 904, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0103] As an example of transmitting data via the OTT connection 950, in step 908, the host 902 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 906. In other embodiments, the user data is associated with a UE 906 that shares data with the host 902 without explicit human interaction. In step 910, the host 902 initiates a transmission carrying the user data towards the UE 906. The host 902 may initiate the transmission responsive to a request transmitted by the UE 906. The request may be caused by human interaction with the UE 906 or by operation of the client application executing on the UE 906. The transmission may pass via the network node 904, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 912, the network node 904 transmits to the UE 906 the user data that was carried in the transmission that the host 902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 914, the UE 906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 906 associated with the host application executed by the host 902.

[0104] In some examples, the UE 906 executes a client application which provides user data to the host 902. The user data may be provided in reaction or response to the data received from the host 902. Accordingly, in step 916, the UE 906 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 906. Regardless of the specific manner in which the user data was provided, the UE 906 initiates, in step 918, transmission of the user data towards the host 902 via the network node 904. In step 920, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 904 receives user data from the UE 906 and initiates transmission of the received user data towards the host 902. In step 922, the host 902 receives the user data carried in the transmission initiated by the UE 906.

[0105] One or more of the various embodiments improve the performance of OTT services provided to the UE 906 using the OTT connection 950, in which the wireless connection 970 forms the last segment. More precisely, the teachings of these embodiments may improve the predictability with which devices connect to network and thereby provide benefits such as better resource planning by the network.

[0106] In an example scenario, factory status information may be collected and analyzed by the host 902. As another example, the host 902 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 902 may store surveillance video uploaded by a UE. As another example, the host 902 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 902 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

[0107] In some examples, a measurement procedure may be provided for the purpose of 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 the OTT connection 950 between the host 902 and UE 906, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 902 and/or UE 906. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 950 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 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 904. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 902. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 950 while monitoring propagation times, errors, etc.

[0108] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information 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. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. [0109] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

[0110] Some of the embodiments of the present disclosure include the following.

[0111] Embodiment 1 : A method performed by a user equipment for modifying the threshold for multiple physical random access channel (PRACH) transmissions, the method comprising: obtaining at least two parameters related to modifying multiple PRACH transmission, wherein a first parameter specifies a number of failed attempts that are allowed and a second parameter that specifies a penalty to be applied should the number of failed attempts exceed the first parameter; attempting a plurality of PRACH transmissions; wherein each of the plurality of PRACH transmissions failed; upon determining that a number of failed PRACH transmissions exceeds the first parameter, applying the second parameter.

[0112] Embodiment 2: The method of 1 wherein the first and second parameters comprise a plurality of first and second parameters wherein a first repetition factor has a different first and/or second parameter compared to a second repetition factor.

[0113] Embodiment 3: The method of any of 1-2 further comprising obtaining a third parameter that specifies additional configuration for PRACH attempts made after the second parameter has been applied.

[0114] Embodiment 4: The method of any of 1-3 wherein second parameter comprises a penalty to a derived received signal strength (RSRP) value.

[0115] Embodiment 5: The method of any of 1-4 further comprising upon successfully performing a PRACH transmission, transmitting a report to a network node, the report specifying information related to the plurality of failed PRACH transmissions.

[0116] Embodiment 6: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node. [0117] Embodiment 7 : A method performed by a network node for modifying the threshold for multiple physical random access channel (PRACH) transmissions, the method comprising: providing a UE with at least two parameters related to modifying multiple PRACH transmission, wherein a first parameter specifies a number of failed attempts that are allowed and a second parameter that specifies a penalty to be applied should the number of failed attempts exceed the first parameter.

[0118] Embodiment 8: The method of 7 wherein the first and second parameters comprise a plurality of first and second parameters wherein a first repetition factor has a different first and/or second parameter compared to a second repetition factor.

[0119] Embodiment 9: The method of any of 7-8 further comprising providing a third parameter that specifies additional configuration for PRACH attempts made after the second parameter has been applied.

[0120] Embodiment 10: The method of any of 7-9 wherein second parameter comprises a penalty to a derived received signal strength (RSRP) value.

[0121] Embodiment 11 : The method of any of 7-10 further comprising receiving from the UE a report, the report specifying information related to a plurality of failed PRACH transmissions.

[0122] Embodiment 12: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0123] Embodiment 13: A user equipment for modifying the threshold for multiple physical random access channel (PRACH) transmissions, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0124] Embodiment 14: A network node for modifying the threshold for multiple physical random access channel (PRACH) transmissions, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.

[0125] Embodiment 15: A user equipment (UE) for modifying the threshold for multiple physical random access channel (PRACH) transmissions, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

[0126] Embodiment 16: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host.

[0127] Embodiment 17: The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

[0128] Embodiment 18: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0129] Embodiment 19: A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.

[0130] Embodiment 20: The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0131] Embodiment 21: The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0132] Embodiment 22: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.

[0133] Embodiment 23: The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

[0134] Embodiment 24: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0135] Embodiment 25: A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.

[0136] Embodiment 26: The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0137] Embodiment 27: The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0138] Embodiment 28: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0139] Embodiment 29: The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0140] Embodiment 30: A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0141] Embodiment 31 : The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

[0142] Embodiment 32: The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

[0143] Embodiment 33: A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0144] Embodiment 34: The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment.

[0145] Embodiment 35: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.

[0146] Embodiment 36: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0147] Embodiment 37: The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

[0148] Embodiment 38: A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host. [0149] Embodiment 39: The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

[0150] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

Claims

1. A method performed by a User Equipment device, UE, (412) for modifying a procedure for multiple Physical Random Access Channel, PRACH, transmissions, the method comprising: obtaining (315) a first parameter from a network wherein the first parameter is related to modifying a multiple PRACH transmission procedure, wherein the first parameter specifies a number of failed attempts that are allowed before modifying the multiple PRACH transmission procedure; attempting (320) a plurality of PRACH transmissions, wherein each of the plurality of PRACH transmissions failed; and upon determining that a number of failed PRACH transmissions exceeds the first parameter, modifying (325) the multiple PRACH transmission procedure.

2. The method of claim 1, further comprising: obtaining (315) a second parameter from the network, and a second parameter that specifies a penalty to be applied should the number of failed attempts exceed the first parameter.

3. The method of claim 2, wherein the modifying the multiple PRACH transmission procedure comprises applying the penalty based on the second parameter.

4. The method of claim 2, wherein the penalty results in a reduction to a derived reference signal received power, RSRP, value associated with a reference signal from the network.

5. The method of any of claims 1 to 4, wherein the first and second parameters comprise a plurality of first and second parameters wherein a first repetition factor has a different first and/or second parameter compared to a second repetition factor.

6. The method of any of claims 2 to 5, further comprising obtaining (315) a third parameter that specifies an additional configuration for PRACH attempts made after the penalty is applied.

7. The method of any of claims 1 to 6, wherein the first parameter comprises a series of parameters each associated with a respective repetition factor, each parameter of the series of parameters indicating a number of failed attempts on each repetition factor before modifying the multiple PRACH transmission procedure.

8. The method of any of claims 1 to 6, further comprising: upon successfully performing a PRACH transmission, transmitting (330) a report to a network node (410), the report specifying information related to the plurality of failed PRACH transmissions.

9. A user equipment device, UE, (412) that is configured to modify a procedure for multiple Physical Random Access Channel, PRACH, transmissions, the UE (412) comprising a processor that causes the UE (412) to: obtain (315) a first parameter from a network wherein the first parameter is related to modifying a multiple PRACH transmission procedure, wherein the first parameter specifies a number of failed attempts that are allowed before modifying the multiple PRACH transmission procedure; attempt (320) a plurality of PRACH transmissions, wherein each of the plurality of PRACH transmissions failed; and upon determining that a number of failed PRACH transmissions exceeds the first parameter, modify (325) the multiple PRACH transmission procedure.

10. The UE (412) of claim 9, wherein the processor is further configured to cause the UE (412) to: obtain (315) a second parameter from the network, and a second parameter that specifies a penalty to be applied should the number of failed attempts exceed the first parameter.

11. The UE (412) of claim 10, wherein the modifying the multiple PRACH transmission procedure comprises applying the penalty based on the second parameter.

12. The UE (412) of claim 10, wherein the penalty results in a reduction to a derived Reference Signal Received Power, RSRP, value associated with a reference signal from the network.

13. The UE (412) of any of claims 9 to 12, wherein the first and second parameters comprise a plurality of first and second parameters wherein a first repetition factor has a different first and/or second parameter compared to a second repetition factor.

14. The UE (412) of any of claims 10 to 13, wherein the processor is further configured to cause the UE (412) to: obtain (315) a third parameter that specifies an additional configuration for PRACH attempts made after the penalty is applied.

15. The UE (412) of any of claims 9 to 14, wherein the first parameter comprises a series of parameters each associated with a respective repetition factor, each parameter of the series of parameters indicating a number of failed attempts on each repetition factor before modifying the multiple PRACH transmission procedure.

16. The UE (412) of any of claims 9 to 15, wherein the processor is further configured to cause the UE (412) to: upon successfully performing a PRACH transmission, transmit (330) a report to a network node (410), the report specifying information related to the plurality of failed PRACH transmissions.

17. A method performed by a network node (410) for modifying the threshold for multiple Physical Random Access Channel (PRACH) transmissions, the method comprising: providing (310) a User Equipment device, UE, (412) with a first parameter, wherein the first parameter is related to modifying a multiple PRACH transmission procedure, wherein the first parameter specifies a number of failed attempts that are allowed before modifying the multiple PRACH transmission procedure.

18. The method of claim 17, further comprising: providing (310) the UE (412) with a second parameter, wherein the second parameter specifies a penalty to be applied should the number of failed attempts exceed the first parameter.

19. The method of claim 18 wherein the first and second parameters comprise a plurality of first and second parameters wherein a first repetition factor has a different first and/or second parameter compared to a second repetition factor.

20. The method of any of claims 18 to 19, wherein the penalty results in a reduction to a derived Reference Signal Received Power, RSRP, value associated with a reference signal from the network node (410).

21. The method of any of claims 17 to 20, further comprising: providing (310) a third parameter that specifies an additional configuration for PRACH attempts made after the penalty is applied.

22. The method of any of claims 17 to 21, wherein the first parameter comprises a series of parameters each associated with a respective repetition factor, each parameter of the series of parameters indicating a number of failed attempts on each repetition factor before modifying the multiple PRACH transmission procedure.

23. The method of any of claims 17 to 22, further comprising: receiving (335) from the UE (412) a report, the report specifying information related to the plurality of failed PRACH transmissions.

24. A network node (410) that is configured to modify a procedure for multiple Physical Random Access Channel, PRACH, transmissions, the network node (410) comprising a processor that causes the network node (410) to: provide (310) a User Equipment device, UE, (412) with a first parameter, wherein the first parameter is related to modifying a multiple PRACH transmission procedure, wherein the first parameter specifies a number of failed attempts that are allowed before modifying the multiple PRACH transmission procedure.

25. The network node (410) of claim 24, wherein the processor is further configured to cause the network node (410) to: provide (310) the UE (412) with a second parameter, wherein the second parameter specifies a penalty to be applied should the number of failed attempts exceed the first parameter.

26. The network node (410) of claim 25 wherein the first and second parameters comprise a plurality of first and second parameters wherein a first repetition factor has a different first and/or second parameter compared to a second repetition factor.

27. The method of any of claims 25 to 26, wherein the penalty results in a reduction to a derived Reference Signal Received Power, RSRP, value associated with a reference signal from the network node (410).

28. The network node (410) of any of claims 24 to 27, wherein the processor is further configured to cause the network node (410) to: provide (310) a third parameter that specifies an additional configuration for PRACH attempts made after the penalty is applied.

29. The network node (410) of any of claims 24 to 28, wherein the first parameter comprises a series of parameters each associated with a respective repetition factor, each parameter of the series of parameters indicating a number of failed attempts on each repetition factor before modifying the multiple PRACH transmission procedure.

30. The network node (410) of any of claims 24 to 29, wherein the processor is further configured to cause the network node (410) to: receive (335) from the UE (412) a report, the report specifying information related to the plurality of failed PRACH transmissions.