Support for transmission in preconfigured UL resources

Abstract

Uplink transmission efficiency and / or user equipment (UE) power consumption is improved by means of transmission in preconfigured resources. This may involve specifying support for transmission in preconfigured resources in idle and / or connected mode. Both shared resources and dedicated resources may be used. An example method performed by a wireless device includes: receiving (110) signaling indicating configuration of preconfigured resources on a first link; and receiving (120) information indicating whether the wireless device is allowed or not allowed to use the preconfigured resources. The method also includes: using or not using (130) the preconfigured resources based on the received information.

Description

Technical Field

[0001] The present disclosure relates generally to the use of preconfigured resources on a radio link, and more particularly to techniques for indicating whether a wireless device is allowed to use such preconfigured resources. Background Art

[0002] There has been a lot of work in 3GPP on specifying technologies to cover machine-to-machine (M2M) and / or Internet of Things (IoT) related use cases. This work in 3GPP Releases 13, 14, and 15 includes enhancements to support machine type communications (MTC) with new UE categories (Cat-M1, Cat-M2), support for reduced bandwidths of up to 6 and 24 physical resource blocks (PRBs), and narrowband IoT (NB-IoT) UEs (and UE categories Cat-NB1 and Cat-NB2) providing a new radio interface.

[0003] Here, the LTE enhancements for MTC introduced in 3GPP Releases 13, 14, and 15 will be referred to as "eMTC" or "LTE-M", including (but not limited to) support for bandwidth-limited UEs, Cat-M1, and support for coverage enhancement. This is to separate the discussion from NB-IoT (the notation here is used for any release), although the supported features are similar at a general level.

[0004] For both eMTC and NB-IoT, 'CIoT EPS UP optimization' and 'CIoT EPS CP optimization' signaling reductions are also introduced in Release 13 (Rel-13). The former, referred to herein as the UP solution, allows the UE to resume a previously stored RRC connection (hence also referred to as RRC suspend / resume). The latter, referred to herein as the CP solution, allows user plane data to be transmitted over the network access layer (NAS) (which may also be referred to as DoNAS).

[0005] There are multiple differences between "legacy" LTE and the procedures and channels defined for eMTC and NB-IoT. Some important differences include new physical channels, such as the Physical Downlink Control Channel, called MPDCCH in eMTC and NPDCCH in NB-IoT, and a new Physical Random Access Channel NPRACH for NB-IoT. Another important difference is the coverage level (also called coverage enhancement level) that these technologies can support. By applying repetition to the transmitted signals and channels, both eMTC and NB-IoT allow UE operation down to much lower SNR levels compared to LTE, i.e., Es / IoT ≥ -15 dB is the lowest operating point for eMTC and NB-IoT, which can be compared to the -6 dB Es / IoT of "legacy" LTE. Summary of the invention

[0006] The purpose is to improve uplink transmission efficiency and / or UE power consumption by means of transmission in pre-configured resources.

[0007] Embodiments described herein may improve uplink transmission efficiency and / or UE power consumption. This may involve specifying support for transmission in pre-configured resources in idle and / or connected mode based on SC-FDMA waveforms for UEs with effective timing advance. Shared resources and dedicated resources may be used. In some embodiments, this is limited to orthogonal (multi) access schemes.

[0008] One potential problem with preconfigured uplink resources (PUR) is that radio resources are reserved very long in advance. Machine type communication (MTC) traffic usually has little or no payload. For example, a UE may transmit a small measurement report once a day. Therefore, it may be difficult for the radio access network to guarantee that the radio resources will be available at a later point, since more important usage may be identified later. If the eNB decides to use the previously configured radio resources for some more urgent ordinary dynamically scheduled transmissions from some UEs, and a PUR-UE happens to wake up and transmit in the same (previously configured) radio resources, the resulting collisions between transmissions from different UEs will lead to interference and performance degradation.

[0009] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these or other challenges. Various embodiments may introduce mechanisms that allow the network to revoke PUR radio resources, or more precisely, to communicate to the UE that the PUR resources have been revoked, or the network may actively control the UE's use of its pre-allocated PUR radio resources.

[0010] In one embodiment, PUR specific access barring is introduced. That is, when a UE wakes up to transmit in its PUR resources, it must first check the system information broadcast to ensure that PUR access is currently allowed in the cell.

[0011] According to some embodiments, a method performed by a wireless device may include receiving signaling indicating configuration of preconfigured resources on a link, and receiving information indicating whether the wireless device is allowed or not allowed to use the preconfigured resources. The method also includes using or not using the preconfigured resources based on the received information.

[0012] According to some embodiments, a method performed by a network node includes transmitting information indicating whether a wireless device is allowed or not allowed to use preconfigured resources on a link. This may be preceded by a determination of whether to allow the wireless device to use the preconfigured resources - this may be based on, for example, a load on the preconfigured resources, a priority of the wireless device, or a priority of a transmission or type of transmission to be performed by the wireless device.

[0013] The embodiments also include corresponding apparatus, wireless apparatus, radio network node, computer program and carrier (eg computer readable medium).

[0014] One advantage of an embodiment is that PUR resources or configurations may be revoked, allowing radio resources to be reused for better purposes. Certain embodiments may provide the following benefits: enabling the wireless network to better manage overall resources even when PUR resources are pre-allocated to some UEs when more important transmissions are needed. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a process flow diagram illustrating an example method implemented by a wireless device.

[0016] Figure 2 is a process flow diagram illustrating an example method implemented by a network node.

[0017] Figure 3 and Figure 4 An example wireless device is shown in accordance with some embodiments.

[0018] Figure 5 and Figure 6 An example network node is shown in accordance with some embodiments.

[0019] Figure 7 is a block diagram illustrating components of an example wireless network.

[0020] Figure 8 An embodiment of a UE in accordance with various aspects described herein is shown.

[0021] Fig. 9 is a schematic block diagram illustrating a virtualization environment in which functionality implemented by some embodiments may be virtualized.

[0022] Fig.10 A telecommunications network is shown connected to a host computer via an intermediary network in accordance with some embodiments.

[0023] Fig.11 A host computer is illustrated communicating with a user device via a base station over a partially wireless connection in accordance with some embodiments.

[0024] Fig.12 is a flow chart illustrating a method implemented in a communication system.

[0025] Fig.13 is a flow chart illustrating a method implemented in a communication system.

[0026] Fig.14 is a flow chart illustrating another method implemented in a communication system.

[0027] Fig.15 is a flow chart illustrating yet another method implemented in a communication system.

[0028] Fig.16 An example of contention-based PUR transmission is shown.

[0029] Fig.17 An example of a contention-free PUR transmission is shown.

[0030] Fig.18 A two-step scheme for PUR transmission in idle mode is shown.

[0031] Fig.19 The time difference of arrival reception of reference signals transmitted from two base stations is shown.

[0032] Fig. 20 is an example of a signaling diagram for a PUR configuration. DETAILED DESCRIPTION

[0033] Figure 1 A method implemented by a wireless device according to certain embodiments is depicted. The method includes receiving signaling indicating configuration of preconfigured resources on a link (block 100). The method may also include receiving information indicating whether the wireless device is allowed or not allowed to use the preconfigured resources (block 110). In some embodiments, the method further includes using or not using the preconfigured resources based on the received information (block 120).

[0034] The information may include, for example, access barring information indicating: whether access to the link using preconfigured resources is prohibited; whether access to the link using one or more next occurrences of preconfigured resources is prohibited; whether access to the link using any occurrence of preconfigured resources is prohibited; whether access to the link using preconfigured resources is prohibited by a group of wireless devices or at a specific coverage level; and / or whether access to the link using any preconfigured resources is prohibited. In some cases, use or non-use of preconfigured resources may occur depending on whether a wireless device is included in a wireless device group or has a specific coverage level and whether access to the link using preconfigured resources is prohibited.

[0035] In some embodiments, the information comprises access barring information indicating whether access to the link using any preconfigured resources is barred.The access barring information may be specific to the preconfigured resources.

[0036] In some embodiments, the information may be system information broadcast on the link. The information may be included in system information block 2 (SIB2) or system information block 14 (SIB14). The system information may be included in system information block 1 (SIB1) or master information block (MIB).

[0037] The information may indicate: whether a group of wireless devices are allowed to use the preconfigured resources; whether the use of the preconfigured resource group is allowed; the reason why the use of the preconfigured resources is not allowed; whether the preconfigured resources are overloaded or the link is overloaded; an alternative way for the wireless device to access the wireless communication network; and / or whether the wireless device is authorized to use the preconfigured resources. The signaling may indicate a time interval for which the configuration of the preconfigured resources is valid. The preconfigured resources may be preconfigured uplink resources (PUR).

[0038] Figure 2 A method performed by a network node according to other specific embodiments is depicted. The method includes: transmitting information indicating whether a wireless device is allowed or not allowed to use preconfigured resources on a link (block 210). In some embodiments, prior to the transmitting, the network node may determine whether to allow the wireless device to use the preconfigured resources on the link based on one or more of: a load on the preconfigured resources or a total load on a cell or carrier; a priority of the wireless device; and / or a priority or transmission type of a transmission to be performed by the wireless device (block 200).

[0039] In some embodiments, the information may indicate whether the wireless device is authorized or unauthorized to use the preconfigured resources. The method may also include determining whether the wireless device is authorized or unauthorized to use the preconfigured resources based on one or more of: previous misuse of the preconfigured resources by the wireless device; previous non-use of the preconfigured resources by the wireless device; inactivity of the wireless device; detachment or handover of the wireless device; and radio link failure experienced by the wireless device. The method may also include determining whether the wireless device is authorized to use the preconfigured resources based on subscription information of the wireless device or context of the wireless device.

[0040] As used herein, the term "preconfigured resources" (e.g., preconfigured radio resources) refers to resources (e.g., one or more time-frequency resources, code resources, or any combination of time, frequency, or code resources) that a wireless device can transmit without receiving a dynamic (and / or explicit) scheduling grant from a radio network node (e.g., on a downlink control channel). In some embodiments, preconfigured resources can be distinguished from semi-static scheduling (SPS) resources, for example, based on the fact that preconfigured resources do not recur or do not recur with a longer period than SPS resources. Preconfigured resources can be resources on which a wireless device can transmit even in idle mode or inactive mode. In the uplink, preconfigured resources are referred to herein as preconfigured uplink resources PUR.

[0041] Note that the above-mentioned devices can perform the methods and any other processing herein by implementing any functional components, modules, units or circuits. For example, in one embodiment, the device includes a corresponding circuit or circuit system configured to perform the steps shown in the method diagram. In this regard, the circuit or circuit system may include a circuit and / or one or more microprocessors combined with a memory dedicated to performing certain functional processing. For example, the circuit may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute a program code stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory, a cache memory, a flash memory device, an optical storage device, etc. In several embodiments, the program code stored in the memory may include program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more techniques described herein. In an embodiment using a memory, the memory stores program code, which executes the techniques described herein when executed by one or more processors.

[0042] For example, Figure 3 A wireless device 300 implemented according to one or more embodiments is shown. As shown, the wireless device 300 includes a processing circuit 310 and a communication circuit 320. The communication circuit 320 (e.g., a radio circuit) is configured to transmit and / or receive information to and / or from one or more other nodes, for example, via any communication technology. Such communication may occur via one or more antennas inside or outside the wireless device 300. The processing circuit 310 is configured to perform the above-mentioned processing, such as by executing instructions stored in a memory 330. In this regard, the processing circuit 310 may implement certain functional components, units, or modules.

[0043] Figure 4 A schematic block diagram of a wireless device 400 in a wireless network according to other embodiments is shown (eg, Figure 7 34 and / or software codes. For example, these functional components, units or modules for implementing the methods herein include, for example: a configuration receiving unit 410, which is configured to receive signaling indicating the configuration of pre-configured resources on a link; and an information receiving unit 420, which is configured to: receive information indicating whether the wireless device is allowed to use the pre-configured resources. The functional implementation may also use a radio resource use unit 430, which is configured to use or not use the pre-configured resources according to the received information.

[0044] Figure 5 A network node 500 implemented according to one or more embodiments is shown. As shown, the network node 500 includes a processing circuit 510 and a communication circuit 520. The communication circuit 520 is configured to transmit information to one or more other nodes and / or receive information from one or more other nodes, for example, via any communication technology. The processing circuit 510 is configured to perform the above-mentioned processing, for example, by executing instructions stored in a memory 530. In this regard, the processing circuit 510 can implement certain functional components, units or modules.

[0045] Figure 6 According to other embodiments (for example, Figure 7 Schematic block diagram of a network node 600 in a wireless network of FIG. 1 . As shown in the figure, the network node 600 is, for example, connected via Figure 5 The processing circuit 510 in the embodiment and / or the software code implement various functional components, units or modules. For example, these functional components, units or modules for implementing one or more methods in this document include, for example: a determination unit 610, configured to determine whether the wireless device is allowed to use the preconfigured resources on the link based on one or more of the following: the load on the preconfigured resources; the priority of the wireless device; the transmission priority or transmission type to be performed by the wireless device; an information transmission unit 620, used to transmit information indicating whether the wireless device is allowed to use the preconfigured resources on the link.

[0046] Those skilled in the art will also appreciate that the embodiments herein also include corresponding computer programs.

[0047] The computer program includes instructions, which, when executed on at least one processor of a device, cause the device to perform any corresponding processing described above. In this regard, the computer program may include one or more code modules corresponding to the above components or units.

[0048] The embodiment also includes a carrier embodying such a computer program. The carrier may include one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium.

[0049] In this regard, embodiments herein also include a computer program product stored on a non-transitory computer-readable (storage or recording) medium and including instructions that, when executed by a processor of a device, cause the device to perform as described above.

[0050] The embodiment also includes a computer program product, which includes a program code portion, and when the computer program product is executed by a computing device, the program code portion is used to perform the steps of any embodiment of the present invention. The computer program product can be stored on a computer readable recording medium.

[0051] Additional embodiments will now be described.For purposes of illustration, at least some of these embodiments may be described as applicable to certain contexts and / or wireless network types, but the embodiments are similarly applicable to other contexts and / or wireless network types not explicitly described.

[0052] MTC traffic is typically very infrequent, and the idea of ​​PUR is to pre-configure radio resources that the UE can use immediately for uplink transmissions, in order to reduce the signaling overhead for the transmissions, and therefore reduce UE power consumption (and improve transmission efficiency due to the use of less radio resources). The PUR resources will be of (N) PUSCH class in the sense that the UE can wake up and transmit user plane payload immediately (if the UE has a valid timing advance). However, MTC traffic is typically very infrequent, but in some cases, for example when many new UEs move into the cell, the traffic situation may have changed dramatically when the UE with the PUR resources wakes up to transmit. The radio network may, for example, have started prioritizing transmissions from another UE, or the PUR load may be so high that the PUR performance is actually less favorable than conventional transmissions (in the case of common PUR resources). The embodiments disclosed herein may include various methods for revoking PUR resources, either for one occasion or for deconfiguring them completely.

[0053] Barring-based access control

[0054] In one set of embodiments, the UE first checks whether the network allows the use of the PUR (eg, due to a temporary overload of the PUR), even if the resources have been pre-configured by the network.

[0055] In one embodiment of the invention, PUR specific access barring is introduced so that a PUR-UE waking up to transmit must first check the system information broadcast to see if PUR access is currently allowed in the cell. An example of this is given below, where PUR access barring is added to the EAB parameters in SIB14.

[0056] SystemInformationBlockType14

[0057] IE SystemInformationBlockType14 contains EAB parameters:

[0058] ----------SystemInformationBlockType14 information element----------

[0059]

[0060] ------------End SystemInformationBlockType14 Information Element---------

[0061] EAB Inspection

[0062] UE will:

[0063] 1> If SystemInformationBlockType14 exists and includes pur-barring:

[0064] 2 > If pur-barring is set to true and the UE is transmitting access PUR resources:

[0065] 3 > It is considered that the access to the cell using PUR resources is prohibited;

[0066] 1> If SystemInformationBlockType14 exists and includes eab-Param:

[0067] 2 > If eab_Common is included in eab_ Param:

[0068] 3 > if the UE belongs to the UE category as indicated in eab-Category contained in eab-Common; and

[0069] 3 > If for the UE's access class, as stored on the USIM and the value is in the range 0..9, the corresponding bit in the eab-BarringBitmap contained in the eab-Common is set to one:

[0070] 4 > It is considered that access to the cell is prohibited;

[0071] 3 > Otherwise:

[0072] 4 > It is considered that access to the cell is not prohibited due to EAB;

[0073] 2> Otherwise (eab-PerPLMN-List is included in eab-Param):

[0074] <text omitted>

[0075] Since LTE-M UEs are affected by both Access Class Barring (ACB) in SIB2 and Extended Access Barring (EAB) in SIB14, the PUR specific supplement may also be added to SIB2. Alternatively, it may be added to a new SIB.

[0076] The implementation of NB-IoT can alternatively be done in NB-IoT mode, but otherwise is very similar.

[0077] This inhibition may have the interpretation that PUR access is temporarily not allowed, ie in the current PUR resources, or it may mean that any PUR configuration should be cancelled and further use of the PUR is not allowed for the UE until a later reconfiguration.

[0078] In one embodiment, an indication of whether PUR access is allowed (or not allowed) is given in system information other than system information considering cell barring (i.e., other than SIB2, SIB14). For example, the indication may be in MasterInformationBlock (MIB or MIB-NB) or SystemInformationBlock1 (SIB1 or SIB1-NB). The indication may be a flag (e.g., a Boolean value) indicating whether the network allows PUR access. Compared to other embodiments in this section, the difference in this embodiment is that the indication will not be considered as a barring, but an indication that the PUR allocation should not be used by a UE previously configured with a PUR.

[0079] Access control may also be configured according to coverage levels together with different UE groups.

[0080] Preemptive access control

[0081] In one embodiment, the eNB may group UEs in different groups. The grouping may be random in nature, for example based on UE identifiers (such as C-RNTI, resumeID, S-TMSI, etc.), or more structured and for example based on CE level, or a combination of both. Each group may be further divided into UE subgroups.

[0082] In some embodiments, each group may be associated with a PUR, which is divided into subsets. In one example, the PUR is defined by a set of time-frequency resources that are divided into orthogonal PUR subsets. Each UE subgroup may then be associated with one or more orthogonal PUR time-frequency resource subsets. In another example, the PUR is defined by a PUR subset of time, frequency, and code resources. Each UE subgroup may then be associated with one or more orthogonal PUR time-frequency code subsets. The coding dimension may be defined, for example, by a codeword pool for scrambling time-frequency resources or a precoder pool for shaping the eNB receiver antenna direction.

[0083] In some embodiments, the network indicates which UE group or UE subgroup is allowed to access the system using its PUR resources. Alternatively, the network may indicate which set or subset of PUR resources are available for access. UEs belonging to the group or subgroup associated with the available PUR resources may then access the cell.

[0084] Admission control via partial dynamic PUR configuration

[0085] In one set of embodiments, the PUR configuration is partly semi-static and partly dynamic.

[0086] In one embodiment, for a UE belonging to a group or PUR that is not allowed to use its PUR resources, the UE may need to further check whether the network indicates that it can use other alternative ways to access the system in the meantime, such as a contention-based random access procedure, or that it needs to wait until a later opportunity to access the system. This is driven by the fact that the network can indicate whether the PUR resources are overloaded or the entire cell is overloaded.

[0087] If there are available resources other than the PUR resources, the network can instruct the UE to use other alternative ways to access the system. If the entire cell is overloaded, the network can temporarily prohibit the UE and let the UE return at a later time.

[0088] In some cases, if the PUR resources allocated to the group UE are occupied, the network can indicate to the UE a second set of PUR resources with a one-to-one mapping to the previous PUR resources allocated to the UE. For example, the network can indicate to the UE to use another carrier (NB-IoT) or narrowband (LTE-M), but keep other parameters the same. This can help the network balance the load between different carriers without reconfiguring each of the individual UEs.

[0089] Access control may also be configured according to coverage levels together with different UE groups.

[0090] Other aspects

[0091] In some cases, when a PUR is allocated to a UE, the network may indicate how long the PUR is valid, such as 12 hours or 24 hours. After the indicated period, the UE should not assume that it still has valid PUR resources, but needs to use the method indicated by the NW (e.g., traditional random access procedure, early data transmission procedure, etc.). Note that the PUR resource verification duration may be different from the TA value verification duration. That is, if the UE has valid PUR resources, but the TA value expires, it needs to verify the TA value first and then use the PUR resources.

[0092] Authorization and Revoke

[0093] The PUR resources may be of PUSCH type in the sense that the UE may wake up and transmit user plane payload immediately (if the UE has a valid timing advance, which is required according to the WI target). However, MTC traffic is typically very infrequent, and by the time the UE wakes up to transmit, the situation may have changed drastically. For example, the wireless network may have started prioritizing transmissions from another UE, or the PUR load may be so high that the PUR performance is actually less favorable than conventional transmissions (in the case of common PUR resources). The embodiments described herein may include various methods for revoking PUR resources, either for one occasion or for deconfiguring them completely.

[0094] In one embodiment, the UE is authorized to use the PUR feature. The authorization can be performed, for example, by RRC or NAS signaling and stored as part of the UE context or subscription information. The authorization can be completed based on UE subscription information, UE category, UE capability, subscription-based UE differentiation information, coverage enhancement level, QoS or QCI, etc. Any UE misuse of the PUR may cause the network to remove the UE's authorization to use the PUR. That is, if the UE, for example, does not transmit in the configured PUR resources, it can be reconfigured with less frequent PUR resources in the first step, and if these are not utilized, it can remove its PUR authorization in the second step. That is, the UE may behave incorrectly by requesting PUR resources but not using them, resulting in insufficient utilization of radio resources. Thereafter, the UE may be blacklisted as being unable to use the PUR with a time limit, and any other eNB based on the PUR authorization information does not configure the UE with a PUR. That is, the network will reject any further PUR requests from the UE (in the list for a period of time).

[0095] In another embodiment, the PUR resources may be revoked for UEs that will not be using them. In one example, it may be identified in the target eNB that a UE configured with a PUR has entered the cell, and the target eNB will then inform the source eNB of this. The source eNB will then revoke all resources for that UE in the cell. The signaling may be over X2 or via S1, i.e. the signaling in the PUR parameters used for configuration may be stored in the cell in which the PUR is configured (e.g. as part of the UE context). The target eNB sees this message when retrieving the UE context, and therefore will know the identity of the source eNB, and inform it that this particular PUR UE has left the cell.

[0096] In one embodiment, a UE that has been configured with PUR resources in a first cell / under a first eNB, upon appearing in a different / second cell and / or under a different / second eNB, provides information indicating active / current PUR resources to a second eNB. The information indicating active / current PUR resources may include information identifying the resources and / or such identification information may be provided upon request from the eNB. The identification information may include, for example, an eNB identifier, a cell identifier, a UE identifier, time / timing, frequency, code, and / or a resource index.

[0097] In one embodiment, the first eNB that has configured / allocated PUR resources for / to the UE indicates to the MME a desire / request to receive whether / when / the UE has been present in a different cell and / or under another / second eNB. The MME, upon receiving the indication and / or determining that the UE has been present in a different cell and / or under a different / second eNB, provides an indication to the first eNB that the UE has been present in a different cell and / or under a second eNB. The first eNB, upon receiving the indication, may release and / or reuse the PUR resources configured / allocated to the UE.

[0098] There may also be conditions for revoking PUR resources; underutilization of radio resources (see previous paragraph), inactivity (e.g. controlled by a timer), detachment from the network, inter-RAT handover, handover in RRC_CONNECTED, RRC re-establishment, radio link failure, etc.

[0099] accomplish

[0100] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks such as Figure 7 For simplicity, Figure 7 The wireless network of FIG. 706 is only depicted as network 706, network nodes 760 and 760b, and wireless devices (WD) 710, 710b, and 710c. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or final device. In the illustrated components, network node 760 and WD 710 are described with additional details. The wireless network can provide communication and other types of services to one or more wireless devices, so that the wireless device can access and / or use the services provided by or via the wireless network.

[0101] A wireless network may include, and / or interface with, any type of communication, telecommunication, data, cellular and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Narrowband Internet of Things (NB-IoT), and / or other suitable 2G, 3G, 4G, or 5G standards; Wireless Local Area Network (WLAN) standards such as IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, and / or ZigBee standards.

[0102] Network 706 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.

[0103] The network node 760 and WD 710 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in data and / or signal communications via wired or wireless connections.

[0104] As used herein, a network node refers to a device that is capable of, configured to, arranged to, and / or operable to communicate directly or indirectly to a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to a wireless device and / or perform other functions (e.g., management) in a wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, node Bs, evolved node Bs (eNBs), and NR NodeBs (gNBs)). Base stations can be classified based on the amount of coverage they provide (or, in other words, their transmit power levels), and then may also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit 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). Still other examples of network nodes include multi-standard radio (MSR) equipment (such as an MSR BS), a network controller (such as a radio network controller (RNC) or a base station controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node, as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured to, arranged to, and / or operable to enable and / or provide a wireless device with access to a wireless network or to provide a certain service to a wireless device that has access to a wireless network.

[0105] exist Figure 7 In the embodiment, the network node 760 includes a processing circuit 770, a device readable medium 780, an interface 790, an auxiliary device 784, a power supply 786, a power circuit 787, and an antenna 762. Figure 7The network node 760 illustrated in the example wireless network of can represent a device including the illustrated combination of hardware components, but other embodiments can include network nodes with different combinations of components. It is to be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Moreover, although the components of the network node 760 are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the network node can include multiple different physical components that make up the single illustrated component (for example, the device readable medium 780 can include multiple separate hard drives and multiple RAM modules).

[0106] Similarly, the network node 760 may be composed of multiple physically separated components (e.g., NodeB components and RNC components or BTS components and BSC components, etc.), each of which may have its own corresponding components. In certain scenarios where the network node 760 includes multiple individual components (e.g., BTS and BSC components), one or more of the individual components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may be considered a single individual network node in some instances. In some embodiments, the network node 760 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be replicated (e.g., separate device readable storage media 780 for different RATs), and some components may be reused (e.g., RATs may share the same antenna 762). The network node 760 may also include multiple groups of various components shown for different wireless technologies (such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into the network node 760. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 760 .

[0107] The processing circuit 770 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being provided by the network node. These operations performed by the processing circuit 770 may include processing information obtained by the processing circuit 770, such as by converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information and making a determination as a result of the processing.

[0108] The processing circuit 770 may include a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or a combination of hardware, software, and / or encoded logic operable to provide network node 760 functionality, either alone or in conjunction with other network node 760 components (such as device readable medium 780). For example, the processing circuit 770 may execute instructions stored in the device readable medium 780 or in a memory within the processing circuit 770. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit 770 may include a system on a chip (SOC).

[0109] In some embodiments, processing circuit 770 may include one or more of radio frequency (RF) transceiver circuit QQ172 and baseband processing circuit 774. In some embodiments, radio frequency (RF) transceiver circuit 772 and baseband processing circuit 774 may be on separate chips (or chipsets), boards, or units (such as a radio unit and a digital unit). In alternative embodiments, part or all of RF transceiver circuit 772 and baseband processing circuit 774 may be on the same chip or chipset, board, or unit.

[0110] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by a processing circuit 770 executing instructions stored in a memory or device-readable medium 780 within the processing circuit 770. In alternative embodiments, some or all of the functionality may be provided by the processing circuit 770 without the need to execute instructions stored on a separate or discrete device-readable medium, such as in a hardwired manner. In any of those embodiments, the processing circuit 770 can be configured to perform the described functionality, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuit 770 alone or other components of the network node 760, but are enjoyed by the network node 760 as a whole, and / or generally by end users and wireless networks.

[0111] The device-readable medium 780 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD), or digital video disk (DVD)), and / or computer-executable memory devices that store information, data, and / or instructions that can be used by the processing circuit 770. The device-readable medium 780 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions that can be executed by the processing circuit 770 and utilized by the network node 760. The device-readable medium 780 may be used to store any calculations performed by the processing circuit 770 and / or any data received via the interface 790. In some embodiments, the processing circuit 770 and the device-readable medium 780 may be considered integrated.

[0112] Interface 790 is used in wired or wireless communication of signaling and / or data between network node 760, network 706 and / or WD 710. As shown, interface 790 includes (one or more) ports / (one or more) terminals 794, for example, to send data to network 706 and receive data from the network through a wired connection. Interface 790 also includes radio front-end circuit 792, which can be coupled to antenna 762, or is part of the antenna in some embodiments. Radio front-end circuit 792 includes filter 798 and amplifier 796. Radio front-end circuit 792 can be connected to antenna 762 and processing circuit 770. Radio front-end circuit can be configured to adjust the signal transmitted between antenna 762 and processing circuit 770. Radio front-end circuit 792 can receive digital data to be sent to other network nodes or WD via wireless connection. Radio front-end circuit 792 can use a combination of filter 798 and / or amplifier 796 to convert digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via antenna 762. Similarly, when data is received, antenna 762 may collect radio signals, which are then converted into digital data by radio front end circuitry 792. The digital data may be passed to processing circuitry 770. In other embodiments, the interface may include different components and / or different combinations of components.

[0113] In some alternative embodiments, the network node 760 may not include a separate radio front end circuit 792, and instead the processing circuit 770 may include the radio front end circuit and may be connected to the antenna 762 without the separate radio front end circuit 792. Similarly, in some embodiments, all or some of the RF transceiver circuit 772 may be considered part of the interface 790. In still other embodiments, the interface 790 may include one or more ports or terminals 794, the radio front end circuit 792, and the RF transceiver circuit 772 as part of a radio unit (not shown), and the interface 790 may communicate with a baseband processing circuit 774 that is part of a digital unit (not shown).

[0114] Antenna 762 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 762 may be coupled to radio front-end circuit 790 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 762 may include one or more omnidirectional, sector or flat panel antennas operable to transmit / receive, for example, radio signals between 2 GHz and 66 GHz. Omnidirectional antennas may be used to transmit / receive radio signals in any direction, sector antennas may be used to transmit / receive radio signals from devices within a specific area, and flat panel antennas may be line of sight antennas for transmitting / receiving radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 762 may be separate from network node 760 and may be connected to network node 760 via an interface or port.

[0115] Antenna 762, interface 790 and / or processing circuit 770 can be configured to perform any receiving operation and / or certain obtaining operation described herein as being performed by a network node. Any information, data and / or signal can be received from a wireless device, another network node and / or any other network equipment. Similarly, antenna 762, interface 790 and / or processing circuit 770 can be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data and / or signal can be transmitted to a wireless device, another network node and / or any other network equipment.

[0116] The power circuit 787 may include or be coupled to a power management circuit, and is configured to supply power for performing the functionality described herein to the components of the network node 760. The power circuit 787 may receive power from a power supply 786. The power supply 786 and / or the power circuit 787 may be configured to provide power to the various components of the network node 760 in a form suitable for the respective components (e.g., with the voltage and current levels required for each respective component). The power supply 786 may be included in the power circuit 787 and / or the network node 760, or outside it. For example, the network node 760 may be connected to an external power source (e.g., an electrical socket) via an input circuit or interface (such as a cable), whereby the external power source supplies power to the power circuit 787. As another example, the power supply 786 may include a power source in the form of a battery or a battery pack, which is connected to or integrated in the power circuit 787. If the external power supply fails, the battery may provide a backup power source. Other types of power sources, such as photovoltaic devices, may also be used.

[0117] Alternative embodiments of network node 760 may include, in addition to Figure 7 , which may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 760 may include a user interface device to allow information to be input into the network node 760 and to allow information to be output from the network node 760. This may allow a user to perform diagnostics, maintenance, repair, and other management functions on the network node 760.

[0118] As used herein, a wireless device (WD) refers to a device capable of, configured to, arranged to, and / or operable to wirelessly communicate with a network node and / or other wireless device. Unless otherwise noted, the term WD may be used interchangeably with a user equipment (UE) herein. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information through the air to transmit and / or receive wireless signals. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to a network on a predetermined schedule when triggered by an internal or external event, or in response to a request from the network. Examples of WD include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, rechargeable devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded devices (LEEs), laptop mounted equipment (LMEs), smart devices, wireless customer premises equipment (CPEs), wireless terminal devices installed in vehicles, etc. WDs can support device-to-device (D2D) communications, such as by implementing the (3GPP) standards for sidelink communications, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case can be referred to as D2D communication devices. As another specific example, in an Internet of Things (IoT) scenario, a WD can represent a machine or other device that performs monitoring and / or measurement, and transmits the results of such monitoring and / or measurement to another WD and / or network node. In this case, the WD may be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context. As a specific example, the WD may be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, the WD may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation. The WD as described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. In addition, the WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0119] As shown, wireless device 710 includes antenna 711, interface 714, processing circuit 720, device readable medium 730, user interface device 732, auxiliary device 734, power supply 736 and power circuit 737. WD 710 can include multiple groups of one or more illustrated components for different wireless technologies supported by WD 710, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMax or Bluetooth wireless technology, just to mention a few. These wireless technologies can be integrated into chips or chipsets that are the same or different from other components in WD 710.

[0120] Antenna 711 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 714. In some alternative embodiments, antenna 711 can be separated from WD 710 and can be connected to WD 710 through an interface or port. Antenna 711, interface 714 and / or processing circuit 720 can be configured to perform any receiving or transmitting operation described herein as being performed by WD. Any information, data and / or signal can be received from a network node and / or another WD. In some embodiments, radio front-end circuit and / or antenna 711 can be considered as an interface.

[0121] As shown, the interface 714 includes a radio front-end circuit 712 and an antenna 711. The radio front-end circuit 712 includes one or more filters 718 and an amplifier 716. The radio front-end circuit 714 is connected to the antenna 711 and the processing circuit 720, and is configured to adjust the signal transmitted between the antenna 711 and the processing circuit 720. The radio front-end circuit 712 can be coupled to the antenna 711, or as a part thereof. In some embodiments, the WD 710 may not include a separate radio front-end circuit 712; on the contrary, the processing circuit 720 may include a radio front-end circuit and may be connected to the antenna 711. Similarly, in some embodiments, some or all of the RF transceiver circuit 722 may be considered as part of the interface 714. The radio front-end circuit 712 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 712 may use a combination of filters 718 and / or amplifiers 716 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via the antenna 711. Similarly, when data is received, antenna 711 may collect radio signals, which are then converted into digital data by radio front end circuit 712. The digital data may be passed to processing circuit 720. In other embodiments, the interface may include different components and / or different combinations of components.

[0122] The processing circuit 720 may include a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or a combination of hardware, software, and / or encoded logic operable to provide WD710 functionality, either alone or in combination with other WD710 components (such as device readable medium 730). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 720 may execute instructions stored in the device readable medium 730 or in a memory within the processing circuit 720 to provide the functionality disclosed herein.

[0123] As shown, the processing circuit 720 includes one or more of the RF transceiver circuit 722, the baseband processing circuit 724, and the application processing circuit 726. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 720 of the WD 710 may include a SOC. In some embodiments, the RF transceiver circuit 722, the baseband processing circuit 724, and the application processing circuit 726 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit 724 and the application processing circuit 726 may be combined into one chip or chipset, and the RF transceiver circuit 722 may be on a separate chip or chipset. In some alternative embodiments, part or all of the RF transceiver circuit 722 and the baseband processing circuit 724 may be on the same chip or chipset, and the application processing circuit 726 may be on a separate chip or chipset. In some alternative embodiments, part or all of the RF transceiver circuit 722, the baseband processing circuit 724, and the application processing circuit 726 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuit 722 may be part of interface 714. RF transceiver circuit 722 may condition RF signals for processing circuit 720.

[0124] In some embodiments, some or all of the functionality described herein as being performed by the WD may be provided by a processing circuit 720 executing instructions stored on a device-readable medium 730, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuit 720 without the need to execute instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those specific embodiments, the processing circuit 720 can be configured to perform the described functionality, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuit 720 alone or other components of the WD 710, but are enjoyed by the WD 710 as a whole, and / or are generally enjoyed by end users and wireless networks.

[0125] The processing circuit 720 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by the WD. These operations performed by the processing circuit 720 may include processing information obtained by the processing circuit 720, such as by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by the WD 710, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of the processing. The device readable medium 730 is operable to store computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions that can be executed by the processing circuit 720. The device readable medium 730 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable memory device that stores information, data, and / or instructions that can be used by the processing circuit 720. In some embodiments, the processing circuit 720 and the device readable medium 730 may be considered integrated.

[0126] The user interface device 732 can provide a component that allows a human user to interact with the WD 710. Such interaction can be in a variety of forms, such as visual, auditory, tactile, etc. The user interface device 732 can operate to generate output to the user and allow the user to provide input to the WD 710. The type of interaction can vary according to the type of user interface device 732 installed in the WD 710. For example, if the WD 710 is a smart phone, the interaction can be carried out via a touch screen; if the WD 710 is a smart meter, the interaction can be carried out through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 732 can include input interfaces, devices and circuits, as well as output interfaces, devices and circuits. The user interface device 732 is configured to allow information to be input into the WD 710, and is connected to the processing circuit 720 to allow the processing circuit 720 to process the input information. The user interface device 732 may include, for example, a microphone, a proximity sensor or other sensor, a key / button, a touch display, one or more cameras, a USB port or other input circuits. The user interface device 732 is further configured to allow information to be output from the WD 710 and to allow the processing circuit 720 to output information from the WD 710. The user interface device 732 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuits. Using one or more input and output interfaces, devices, and circuits of the user interface device 732, the WD 710 can communicate with an end user and / or a wireless network and allow them to benefit from the functionality described herein.

[0127] Auxiliary device 734 is operable to provide more specific functionality not typically performed by a WD. This may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communications such as wired communications, etc. The inclusion and types of components of auxiliary device 734 may vary depending on the embodiment and / or scenario.

[0128] In some embodiments, the power supply 736 may be in the form of a battery or battery pack. Other types of power supplies may also be used, such as an external power supply (e.g., an electrical socket), a photovoltaic device, or a power battery. The WD 710 may further include a power circuit 737 for delivering power from the power supply 736 to various parts of the WD 710, which need to be powered from the power supply 736 to implement any functionality described or indicated herein. In some embodiments, the power circuit 737 may include a power management circuit. The power circuit 737 may additionally or alternatively be operable to receive power from an external power supply; in this case, the WD 710 may be connected to an external power supply (such as an electrical socket) via an input circuit or interface (such as a power cable). In some embodiments, the power circuit 737 may also be operable to deliver power from an external power supply to the power supply 736. For example, this may be used for charging the power supply 736. The power circuit 737 may perform any formatting, conversion, or other modifications to the power from the power supply 736 so that the power is suitable for the corresponding components of the WD 710 to which the power is supplied.

[0129] Figure 8 An embodiment of a UE in accordance with various aspects described herein is illustrated. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Rather, a UE may represent a device that is intended to be sold to or operated by a human user, but that may not be associated with, or that may not initially be associated with, a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but that may be associated with or operated for the benefit of a user (e.g., a smart meter). UE 800 may be any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Figure 8 The UE 800 illustrated in FIG. 8 is an example of a WD configured to communicate in accordance with one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Thus, although Figure 8 It is a UE, but the components discussed in this article are also applicable to WD, and vice versa.

[0130] exist Figure 8In the embodiment, UE 800 includes a processing circuit 801, which is operably coupled to an input / output interface 805, a radio frequency (RF) interface 809, a network connection interface 811, a memory 815 including a random access memory (RAM) 817, a read-only memory (ROM) 819 and a storage medium 821, a communication subsystem 831, a power supply 833 and / or any other components or any combination thereof. The storage medium 821 includes an operating system 823, an application 825 and data 827. In other embodiments, the storage medium 821 may include other similar types of information. Some UEs may utilize Figure 8 All components shown in the UE may be used, or only a subset of the components may be utilized. The level of integration between components may vary from one UE to another. In addition, some UEs may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0131] exist Figure 8 , processing circuitry 801 may be configured to process computer instructions and data. Processing circuitry 801 may be configured to implement any sequential state machine that operates to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as microprocessors or digital signal processors (DSPs), together with appropriate software; or any combination of the above. For example, processing circuitry 801 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0132] In the depicted embodiment, the input / output interface 805 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 800 may be configured to use an output device via the input / output interface 805. The output device may use an interface port of the same type as the input device. For example, a USB port may be used to provide input to the UE 800 and output from the UE. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 800 may be configured to use an input device via the input / output interface 805 to allow a user to capture information into the UE 800. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0133] exist Figure 8 In the embodiment of the present invention, the RF interface 809 can be configured to provide a communication interface to the RF components (such as transmitters, receivers and antennas). The network connection interface 811 can be configured to provide a communication interface to the network 843a. The network 843a can include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network or any combination thereof. For example, the network 843a can include a Wi-Fi network. The network connection interface 811 can be configured to include a receiver and a transmitter interface for communicating with one or more other devices through a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface 811 can implement receiver and transmitter functionality suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.

[0134] RAM 817 can be configured to interface with processing circuit 801 via bus 802 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications and device drivers. ROM 819 can be configured to provide computer instructions or data to processing circuit 801. For example, ROM 819 can be configured to store unchanged low-level system code or data of basic system functions stored in non-volatile memory, such as basic input and output (I / O), startup or receiving keystrokes from a keyboard. Storage medium 821 can be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable cassette or flash drive. In one example, storage medium 821 can be configured to include operating system 823, application 825 (such as a web browser application, widget or gadget engine or another application) and data file 827. The storage medium 821 may store any of various operating systems or combinations of operating systems for use by the UE 800 .

[0135] The storage medium 821 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM) synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (such as a subscriber identity module or a removable user identity (SIM / RUIM) module), other memory or any combination thereof. The storage medium 821 may allow the UE 800 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article such as utilizing a communication system may be tangibly embodied in the storage medium 821, which may include a device-readable medium.

[0136] exist Figure 8In the embodiment, the processing circuit 801 can be configured to communicate with the network 843b using the communication subsystem 831. The network 843a and the network 843b can be the same one or more networks or different one or more networks. The communication subsystem 831 can be configured to include one or more transceivers for communicating with the network 843b. For example, the communication subsystem 831 can be configured to include one or more transceivers for communicating with the network 843b according to one or more communication protocols (such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.) and one or more remote transceivers of another device (such as another WD, UE or base station of a radio access network (RAN)) capable of wireless communication. Each transceiver can include a transmitter 833 and / or a receiver 835 to respectively implement the transmitter or receiver functionality (e.g., frequency allocation, etc.) applicable to the RAN link. In addition, the transmitter 833 and the receiver 835 of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.

[0137] In the illustrated embodiment, the communication functions of the communication subsystem 831 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a global positioning system (GPS) to determine the location, another similar communication function or any combination thereof. For example, the communication subsystem 831 may include cellular communication, Wi-Fi communication, Bluetooth communication and GPS communication. The network 843b may include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network or any combination thereof. For example, the network 843b may be a cellular network, a Wi-Fi network and / or a near-field network. The power supply 813 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 800. The features, benefits and / or functions described herein may be implemented in one of the components of the UE 800, or may be divided among multiple components of the UE 800. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 831 can be configured to include any of the components described herein. In addition, the processing circuit 801 can be configured to communicate with any such components via the bus 802. In another example, any such component can be represented by program instructions stored in a memory, which, when executed by the processing circuit 801, perform the corresponding functions described herein. In another example, the functionality of any such component can be divided between the processing circuit 801 and the communication subsystem 831. In another example, the non-computationally intensive functions of any such component can be implemented in software or firmware, and the computationally intensive functions can be implemented in hardware.

[0138] Fig. 9 900 is a schematic block diagram of a virtualized environment, wherein the functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and relates to an implementation in which at least some functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0139] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 900 hosted by one or more of the hardware nodes 930. Additionally, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0140] These functions may be implemented by one or more applications 920 (alternatively they may be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) that operate to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications 920 run in a virtualized environment 900 that provides hardware 930 including processing circuitry 960 and memory 990. The memory 990 includes instructions 995 executable by the processing circuitry 960, whereby the applications 920 may operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0141] The virtualized environment 900 includes a general or special purpose network hardware device 930, which includes a collection of one or more processors or processing circuits 960, which may be commercial off-the-shelf (COTS) processors, specialized application-specific integrated circuits (ASICs), or any other type of processing circuit, including digital or analog hardware components or special purpose processors. Each hardware device may include a memory 990-1, which may be a non-permanent memory for temporarily storing software or instructions 995 executed by the processing circuit 960. Each hardware device may include one or more network interface controllers (NICs) 970, also known as network interface cards, which include physical network interfaces 980. Each hardware device may also include a non-transitory, permanent machine-readable storage medium 990-2 in which instructions and / or software 995 executable by the processing circuit 960 are stored. The software 995 may include any type of software, including software for instantiating one or more virtualization layers 950 (also known as hypervisors), software for executing virtual machines 940, and software that allows them to perform the functions, features, and / or benefits described in conjunction with some of the embodiments described herein.

[0142] The virtual machine 940 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be run by a corresponding virtualization layer 950 or hypervisor. Different embodiments of the instance of the virtual appliance 920 can be implemented on one or more of the virtual machines 940, and the implementation can be performed in different ways.

[0143] During operation, processing circuitry 960 executes software 995 to instantiate a hypervisor or virtualization layer 950, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 950 may present to virtual machines 940 a virtual operating platform that appears to be networked hardware.

[0144] like Fig. 9 As shown, hardware 930 can be an independent network node with common or specific components. Hardware 930 can include antenna 9225, and some functions can be implemented via virtualization. Alternatively, hardware 930 can be part of a larger hardware cluster (e.g., such as in a data center or customer premise equipment (CPE)), where many hardware nodes work together and are managed via management and orchestration (MANO) 9100, which also oversees the life cycle management of application 920, among other things.

[0145] Virtualization of hardware is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage devices, which can be located in data centers and customer premises equipment.

[0146] In the context of NFV, a virtual machine 940 may be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each virtual machine 940 and the portion of the hardware 930 on which it executes, whether it is hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines 940, form a separate virtual network element (VNE).

[0147] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines 940 atop the hardware networking infrastructure 930 and corresponds to Fig. 9 Application 920.

[0148] In some embodiments, one or more radio units 9200, each including one or more transmitters 9220 and one or more receivers 9210, may be coupled to one or more antennas 9225. The radio units 9200 may communicate directly with the hardware nodes 930 via one or more appropriate network interfaces, and may be used in combination with virtual components to provide radio capabilities to virtual nodes, such as radio access nodes or base stations.

[0149] In some embodiments, some signaling may be accomplished using a control system 9230 , which may alternatively be used for communications between the hardware node 930 and the radio unit 9200 .

[0150] Fig.10 A telecommunications network connected to a host computer via an intermediate network according to an embodiment is shown. In particular, reference is made to Fig.10According to one embodiment, the communication system includes a telecommunication network 1010, such as a 3GPP type cellular network, which includes an access network 1011 (such as a radio access network) and a core network 1014. The access network 1011 includes a plurality of base stations 1012a, 1012b, 1012c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1013a, 1013b, 1013c. Each base station 1012a, 1012b, 1012c may be connected to the core network 1014 via a wired or wireless connection 1015. A first UE 1091 located in the coverage area 1013c is configured to be wirelessly connected to or paged by the corresponding base station 1012c. A second UE 1092 in the coverage area 1013a may be wirelessly connected to the corresponding base station 1012a. Although multiple UEs 1091, 1092 are illustrated in this example, the disclosed embodiments are equally applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 1012. The telecommunications network 1010 itself is connected to a host computer 1030, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server cluster. The host computer 1030 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. The connections 1021 and 1022 between the telecommunications network 1010 and the host computer 1030 may extend directly from the core network 1014 to the host computer 1030, or may be via an optional intermediate network 1020. The intermediate network 1020 may be a combination of one or more of a public, private, or managed network; the intermediate network 1020 (if any) may be a backbone network or the Internet; in particular, the intermediate network 1020 may include two or more subnets (not shown).

[0151] Fig.10The communication system as a whole enables connectivity between the connected UEs 1091, 1092 and the host computer 1030. The connectivity can be described as an over-the-top (OTT) connection 1050. The host computer 1030 and the connected UEs 1091, 1092 are configured to use the access network 1011, the core network 1014, any intermediate networks 1020, and possible additional infrastructure (not shown) as intermediaries to pass data and / or signaling via the OTT connection 1050. The OTT connection 1050 can be transparent in the sense that the participating communication devices through which the OTT connection 1050 passes are unaware of the routing of uplink and downlink communications. For example, the base station 1012 may not be informed or need not be informed of the past routing of incoming downlink communications, which have data originating from the host computer 1030 to be forwarded (e.g., switched) to the connected UE 1091. Similarly, base station 1012 need not be aware of the future routing of outgoing uplink communications originating from UE 1091 toward host computer 1030 .

[0152] According to the embodiment, reference will now be made to Fig.11 Example implementations of the UE, base station, and host computer discussed in the previous paragraphs are described. Fig.11 A host computer that communicates with a user device via a base station through a partial wireless connection according to an embodiment is shown. In the communication system 1100, the host computer 1110 includes hardware 1115, which includes a communication interface 1116, which is configured to establish and maintain a wired or wireless connection of an interface with different communication devices of the communication system 1100. The host computer 1110 further includes a processing circuit 1118, which may have storage and / or processing capabilities. In particular, the processing circuit 1118 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The host computer 1110 further includes software 1111, which is stored in or accessible to the host computer 1010 and can be executed by the processing circuit 1118. Software 1111 includes a host application 1112. The host application 1112 is operable to provide services to remote users, such as UE 1130 connected via an OTT connection 1150 terminated at UE 1130 and the host computer 1110. When providing services to remote users, the host application 1112 can provide user data transmitted using the OTT connection 1150.

[0153] The communication system 1100 further includes a base station 1120, which is provided in the telecommunication system and includes hardware 1125, enabling it to communicate with the host computer 1110 and the UE 1130. The hardware 1125 may include a communication interface 1126 for establishing and maintaining a wired or wireless connection with different communication devices of the communication system 1100, and for establishing and maintaining a connection with the base station 1120 in the coverage area ( Fig.11 1100). The communication interface 1126 may be configured to facilitate a connection 1160 to the host computer 1110. The connection 1160 may be direct, or it may be through a core network (eg, a wireless network) of the telecommunications system. Fig.11 1120) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 1125 of the base station 1120 further includes processing circuitry 1128, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The base station 1120 further has software 1121 stored internally or accessible via an external connection.

[0154] The communication system 1100 further includes the UE 1130 already mentioned. Its hardware 1135 may include a radio interface 1137, which is configured to establish and maintain a wireless connection 1170 with a base station serving the coverage area where the UE 1130 is currently located. The hardware 1135 of the UE 1130 further includes a processing circuit 1138, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The UE 1130 further includes software 1131, which is stored in the UE 1130 or can be accessed by it and can be executed by the processing circuit 1138. The software 1131 includes a client application 1132. The client application 1132 is operable to provide services to human or non-human users via the UE 1130 with the support of the host computer 1110. In the host computer 1110, the executing host application 1112 can communicate with the executing client application 1132 via the OTT connection 1150 terminated at the UE 1130 and the host computer 1110. When providing services to users, the client application 1132 can receive request data from the host application 1112 and provide user data in response to the request data. The OTT connection 1150 can transfer both request data and user data. The client application 1132 can interact with the user to generate the user data it provides.

[0155] Notice, Fig.11The host computer 1110, base station 1120 and UE 1130 shown may be similar to or identical to Fig.10 The host computer 1030, one of the base stations 1012a, 1012b, 1012c and one of the UEs 1091, 1092. That is, the internal workings of these entities can be as follows Fig.11 shown, and independently, the surrounding network topology can be Fig.10 network topology.

[0156] exist Fig.11 11, OTT connection 1150 has been abstractly drawn to illustrate communications between host computer 1110 and UE 1130 via base station 1120, without explicit reference to any intermediary devices and the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from UE 1130, or hidden from the service provider operating host computer 1110, or hidden from both. When OTT connection 1150 is active, the network infrastructure can further make decisions by which it dynamically changes the routing (e.g., based on network reconfiguration or load balancing considerations).

[0157] The wireless connection 1170 between the UE 1130 and the base station 1120 is in accordance with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments improves the performance of the OTT service provided to the UE 1130 using the OTT connection 1150, wherein the wireless connection 1170 forms the last segment. More precisely, the teachings of these embodiments can improve uplink transmission efficiency and / or UE power consumption, and thereby provide benefits such as reduced usage latency, better responsiveness, and extended battery life.

[0158] For the purpose of monitoring data rate, latency, and other factors improved by one or more embodiments, a measurement process may be provided. There may further be optional network functionality for reconfiguring the OTT connection 1150 between the host computer 1110 and the UE 1130 in response to changes in the measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 1150 may be implemented in the software 1111 and hardware 1115 of the host computer 1110 or in the software 1131 and hardware 1135 of the UE 1130, or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 1150 passes; the sensor may participate in the measurement process by providing the values ​​of the monitored quantities exemplified above or providing the values ​​of other physical quantities from which the software 1111, 1131 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1150 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the base station 1120 and may be unknown or imperceptible to the base station 1120. Such processes and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling, facilitating host computer 1110 to measure throughput, propagation time, latency, etc. The measurements may be implemented as follows: Software 1011 and 1031 causes messages (particularly empty messages or "dummy" messages) to be transmitted using OTT connection 1150 while it monitors propagation time, errors, etc.

[0159] Fig.12 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.10 and 11 To simplify this disclosure, only the Fig.12 . In step 1210, the host computer provides user data. In sub-step 1211 of step 1210 (which may be optional), the host computer provides the user data by executing a host application. In step 1220, the host computer initiates a transmission carrying the user data to the UE. In step 1230 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In step 1240 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0160] Fig.13 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.10 and 11To simplify this disclosure, only the Fig.13 In step 1310 of the method, a host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 1320, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be delivered via a base station. In step 1330 (which may be optional), the UE receives the user data carried in the transmission.

[0161] Fig.14 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.10 and 11 To simplify this disclosure, only the Fig.14 . In step 1410 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1420, the UE provides user data. In sub-step 1421 of step 1420 (which may be optional), the UE provides user data by executing a client application. In sub-step 1411 of step 1410 (which may be optional), the UE executes a client application that provides user data in response to received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner of providing user data, in sub-step 1430 (which may be optional), the UE initiates transmission of user data to the host computer. In step 1440 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data transmitted from the UE.

[0162] Fig.15 is a flow chart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.10 and 11 To simplify this disclosure, only the Fig.15 In step 1510 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station receives user data from the UE. In step 1520 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 1530 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0163] Any suitable steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include several of these functional units. These functional units may be implemented via processing circuits and other digital hardware, and the processing circuits may include one or more microprocessors or microcontrollers, and the digital hardware may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory device, optical storage device, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for implementing one or more technologies described herein. In some implementations, according to one or more embodiments of the present disclosure, the processing circuit may be used to cause the corresponding functional unit to perform the corresponding function.

[0164] Generally, all terms used herein, unless clearly given and / or different meanings are implied from the context in which it is used, will be interpreted according to their common meanings in the relevant technical field. Unless otherwise clearly stated, all references to one / an / the element, equipment, assembly, parts, step, etc. will be openly interpreted as referring to at least one instance of the element, equipment, assembly, parts, step, etc. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless the steps are clearly described as after or before another step and / or the implicit step must be after or before another step. In any appropriate case, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. From the following description, other purposes, features and advantages of the attached embodiments will be apparent.

[0165] The term "unit" has a conventional meaning in the field of electronics, electrical devices and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc., such as those described herein.

[0166] Some embodiments contemplated herein are more fully described with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as being limited to the embodiments described herein; the present invention is not limited to the disclosed embodiments. Instead, these embodiments are provided merely as examples to convey the scope of the subject matter to those skilled in the art.

[0167] Example Embodiments

[0168] Group A Embodiment

[0169] A1. A method performed by a wireless device, the method comprising:

[0170] receiving signaling indicating configuration of one or more preconfigured resources on a link; and

[0171] Information is received indicating whether the wireless device is allowed or not allowed to use the preconfigured resources.

[0172] A2. The method according to embodiment A1 further includes: using or not using the preconfigured resources according to the received information.

[0173] A3. The method according to any one of embodiments A1-A2, wherein the information includes access prohibition information, and the access prohibition information indicates whether access to the link using the preconfigured resources is prohibited.

[0174] A4. The method of any one of embodiments A1-A3, wherein the information comprises access barring information indicating whether to prohibit access to the link using one or more next occurrences of the preconfigured resources.

[0175] A5. The method of any one of embodiments A1-A3, wherein the information includes access barring information indicating whether accessing the link using any occurrence of the preconfigured resources is prohibited.

[0176] A6. The method of any one of embodiments A1-A5, wherein the information includes access barring information indicating whether a group of wireless devices or a specific coverage level are barred from accessing the link using the preconfigured resources.

[0177] A7. The method according to embodiment A6, further comprising using or not using preconfigured resources according to the following:

[0178] whether the wireless device is included in the group of wireless devices or has a particular coverage level; and

[0179] The use of the preconfigured resources to access the link is prohibited.

[0180] A8. The method according to any one of embodiments A1-A7, wherein the information includes access prohibition information, and the access prohibition information indicates whether access to the link using any pre-configured resources is prohibited.

[0181] A9. The method of any one of embodiments A3-A8, wherein the access barring information is specific to preconfigured resources.

[0182] A10. The method of any one of embodiments A1-A9, wherein the information is system information broadcast on a link.

[0183] A11. The method of any one of embodiments A1-A7, wherein the information is included in a system information block 2 SIB2 or in a system information block 14 SIB14.

[0184] A12. The method of any one of embodiments A1-A10, wherein the system information is included in a system information block 1 SIB1 or a master information block MIB.

[0185] A13. The method of any one of embodiments A1-A12, wherein the information indicates whether a group of wireless devices are allowed or not allowed to use the preconfigured resources.

[0186] A14. The method of any one of embodiments A1-A13, wherein the information indicates whether a group of wireless devices are allowed or not allowed to use a set of preconfigured resources.

[0187] A15. The method of any one of embodiments A1-A14, wherein the information indicates a reason why the use of the preconfigured resources is not allowed.

[0188] A16. The method according to any one of embodiments A1-A15, wherein the information indicates whether the preconfigured resources are overloaded or whether the link is overloaded.

[0189] A17. The method of any one of embodiments A1-A16, wherein the information further indicates an alternative way for the wireless device to access the wireless communication network.

[0190] A18. A method according to any one of embodiments A1-A17, wherein the signaling indicates a time interval during which the configuration of the pre-configured resources is valid.

[0191] A19. The method according to any one of embodiments A1-A18, wherein the pre-configured resources are pre-configured uplink resources PUR.

[0192] A20. The method of any one of embodiments A1-A19, wherein the information indicates whether the wireless device is authorized or unauthorized to use the preconfigured resources.

[0193] A21. The method of embodiment A20, wherein the information indicates whether the wireless device is authorized or unauthorized to use the preconfigured resource by indicating whether the wireless device is blacklisted from using the preconfigured resource.

[0194] A22. The method of any one of embodiments A1-A21, wherein the information is received via radio resource control, RRC, or non-access stratum, NAS, signaling and / or stored as part of a context or subscription of the wireless device.

[0195] A23. The method of any one of embodiments A1-A22, wherein the information denies the wireless device's request for the preconfigured resources or a request for use of the preconfigured resources.

[0196] A24. The method according to any one of embodiments A1-A23 further includes: after a mobility process of changing the wireless device from the link to a target link or as part of the mobility process, transmitting control signaling indicating any pre-configured resources configured on the link, wherein the control signaling is transmitted to a radio network node serving the target link or a network node configured to perform mobility management.

[0197] A25. The method of embodiment A24, wherein the control signaling indicates an identifier of the link and an identifier of each preconfigured resource configured on the link.

[0198] AA. The method according to any one of the preceding embodiments, further comprising:

[0199] Provide user data; and

[0200] User data is forwarded to a host computer via communications to a base station.

[0201] AB. The method according to any of the preceding embodiments, wherein the pre-configured resources are pre-configured radio resources.

[0202] AC. The method as in any of the preceding embodiments, wherein the link is a cell, a beam, a sector, a radio network node.

[0203] Group B Example

[0204] B1. A method performed by a network node, the method comprising:

[0205] Information is transmitted indicating whether the wireless device is allowed or not allowed to use the preconfigured resources on the link.

[0206] B2. The method according to embodiment B1 further comprises: determining whether the wireless device is allowed or not allowed to use the preconfigured resources on the first link based on one or more of the following:

[0207] the load on the preconfigured resources;

[0208] The priority of the wireless device; and

[0209] The type of transmission to be performed by the wireless device or the priority of the transmission.

[0210] B3. The method according to any one of embodiments B1-B2, wherein the information includes access prohibition information, and the access prohibition information indicates whether to prohibit the use of the preconfigured resources to access the link.

[0211] B4. The method of any one of embodiments B1-B3, wherein the information includes access barring information indicating whether to prohibit access to the link using one or more next occurrences of preconfigured resources.

[0212] B5. The method of any one of embodiments B1-B3, wherein the information includes access barring information indicating whether accessing the link using any occurrence of preconfigured resources is prohibited.

[0213] B6. The method of any one of embodiments B1-B5, wherein the information includes access barring information indicating whether a group of wireless devices are barred from accessing the link using the preconfigured resources or at a specific coverage level.

[0214] B7. A method according to any one of embodiments B1-B6, wherein the information includes access prohibition information indicating whether to prohibit the use of any pre-configured resources to access the link.

[0215] B8. A method according to any one of embodiments B3-B7, wherein the access barring information is specific to preconfigured resources.

[0216] B9. The method according to any one of embodiments B1-B8, wherein the information is system information broadcast on the link.

[0217] B10. The method of any one of embodiments B1-B9, wherein the information is included in a system information block 2 SIB2 or in a system information block 14 SIB14.

[0218] B11. The method of any one of embodiments B1-B9, wherein the system information is included in a system information block 1 SIB1 or a master information block MIB.

[0219] B12. The method of any one of embodiments B1-B11, wherein the information indicates whether a group of wireless devices are allowed or not allowed to use the preconfigured resources.

[0220] B13. The method of any one of embodiments B1-B12, wherein the information indicates whether use of a set of preconfigured resources is allowed or not allowed.

[0221] B14. A method according to any one of embodiments B1-B13, wherein the information indicates a reason why the use of the pre-configured resources is not allowed.

[0222] B15. The method according to any one of embodiments B1-B14, wherein the information indicates whether the pre-configured resources are overloaded or whether the link is overloaded.

[0223] B16. The method of any one of embodiments B1-B15, wherein the information further indicates an alternative way for the wireless device to access the wireless communication network.

[0224] B17. The method according to any one of embodiments B1-B16, wherein the pre-configured resource is a pre-configured uplink resource PUR.

[0225] B18. The method of any one of embodiments B1-B17, wherein the information indicates whether the wireless device is authorized or unauthorized to use the preconfigured resources.

[0226] B19. The method according to embodiment 18 further includes: determining whether the wireless device is authorized or unauthorized to use the preconfigured resource based on one or more of the following:

[0227] prior misuse of preconfigured resources by the wireless device;

[0228] The wireless device has not previously used the preconfigured resources;

[0229] inactivity of said wireless device;

[0230] separation or switching of the wireless device; and

[0231] A radio link failure experienced by the wireless device.

[0232] B20. The method according to embodiment 18 also includes: determining whether the wireless device is authorized or unauthorized to use the preconfigured resources based on: subscription information of the wireless device, the context of the wireless device, the category or capability of the wireless device, subscription-based differentiation information of the wireless device, the coverage enhancement level of the wireless device, the quality of service of the wireless device, or the quality of service classification identifier of the wireless device.

[0233] B21. The method of any one of embodiments B18-B20, wherein the information indicates whether the wireless device is authorized or unauthorized to use the preconfigured resource by indicating whether the wireless device is blacklisted from using the preconfigured resource.

[0234] B22. The method according to any one of embodiments B18-B21, further comprising:

[0235] receiving signaling from a radio network node serving a second link or a network node configured to perform mobility management, the signaling indicating that the wireless device has changed to the second link and / or that the wireless device has left the first link; and

[0236] Based on the received signaling, it is determined that the wireless device is no longer authorized to use the preconfigured resources on the first link.

[0237] B23. The method of embodiment B22, wherein the signaling includes a context of the wireless device, and the context indicates that the wireless device has changed to the second link and / or the wireless device has left the first link.

[0238] B24. The method of any one of embodiments B1-B23, wherein the information is transmitted via radio resource control (RRC) or non-access stratum (NAS) signaling and / or retrieved from or based on a context or subscription of the wireless device.

[0239] B25. The method of any one of embodiments B1-B24, wherein the information denies the wireless device's request for the preconfigured resources or a request for use of the preconfigured resources.

[0240] B26. The method according to any one of embodiments B1-B25 further includes: after a mobility process of changing the wireless device from a source link to a link serving as a target link or as part of the mobility process, receiving control signaling indicating any pre-configured resources configured for the wireless device on the source link.

[0241] B27. The method according to any one of embodiments B1-B25 also includes: after or as part of a mobility procedure of changing the wireless device from a source link to a target link, transmitting control signaling indicating any pre-configured resources configured for the wireless device on the source link.

[0242] B28. The method of any one of embodiments B26-B27, wherein the control signaling indicates an identifier of a source link and an identifier of each preconfigured resource configured for the wireless device on the source link.

[0243] BA. The method of any preceding embodiment, wherein the preconfigured resources are preconfigured radio resources.

[0244] BB. The method according to any of the preceding embodiments, further comprising:

[0245] obtain user data; and

[0246] Forwards user data to a host computer or wireless device.

[0247] BC. The method of any preceding embodiment, wherein the link is a cell, a beam, a sector, or a radio network node.

[0248] BD. The method of any preceding embodiment, wherein the network node is a radio network node serving the link.

[0249] BE. The method of any of the preceding embodiments, comprising transmitting the information to a wireless device.

[0250] BF. The method according to any of the preceding embodiments, comprising transmitting the information to another network node.

[0251] Group C Example

[0252] C1. A wireless device configured to perform any of the steps of any of the embodiments in Group A.

[0253] C2A. A wireless device comprising:

[0254] Processing circuitry configured to perform any of the steps of any of the embodiments in Group A; and

[0255] A power supply circuit configured to supply power to the wireless device.

[0256] C2B. A wireless device comprising:

[0257] communications circuits; and

[0258] A processing circuit configured to perform any of the steps of any of the embodiments in Group A.

[0259] C3. A wireless device comprising:

[0260] A processing circuit and a memory containing instructions executable by the processing circuit, whereby the wireless device is configured to perform any of the steps of any of the embodiments of Group A.

[0261] C4. A user equipment (UE), comprising:

[0262] an antenna configured to send and receive wireless signals;

[0263] a radio front end circuit coupled to the antenna and the processing circuit and configured to condition signals passed between the antenna and the processing circuit;

[0264] The processing circuit is configured to perform any of the steps of any of the embodiments in Group A;

[0265] an input interface connected to the processing circuitry and configured to allow information to be input into the UE for processing by the processing circuitry;

[0266] an output interface connected to the processing circuit and configured to output, from the UE, information that has been processed by the processing circuit; and

[0267] A battery connected to the processing circuit and configured to supply power to the UE.

[0268] C5. A computer program comprising instructions that, when executed on at least one processor of a wireless device, perform any of the steps of any of the embodiments of Group A.

[0269] C6. A carrier comprising the computer program of embodiment C5, wherein the carrier is one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium.

[0270] C7. A network node configured to perform any of the steps of any of the embodiments of Group B.

[0271] C8A. A network node, comprising:

[0272] Processing circuitry configured to perform any of the steps of any of the embodiments of Group B;

[0273] A power supply circuit configured to supply power to a network node.

[0274] C8B. A network node, comprising:

[0275] communications circuits; and

[0276] Processing circuitry configured to perform any of the steps of any of the embodiments in Group B.

[0277] C9. A network node, comprising:

[0278] A processing circuit and a memory containing instructions executable by the processing circuit, whereby the network node is configured to perform any of the steps of any of the embodiments of Group B.

[0279] C10. A computer program comprising instructions which, when executed by at least one processor of a network node, cause the network node to perform any of the steps of any of the embodiments of Group B.

[0280] C11. A carrier comprising the computer program of embodiment C10, wherein the carrier is one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium.

[0281] Group D Examples

[0282] D1. A communication system comprising a host computer, the host computer comprising:

[0283] processing circuitry configured to provide user data; and

[0284] a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),

[0285] The cellular network comprises a network node having a radio interface and a processing circuit, the processing circuit of the network node being configured to perform any of the steps of any of the embodiments of Group B.

[0286] D2. The communication system of the aforementioned embodiment further includes a network node.

[0287] D3. The communication system of the above two embodiments further includes a UE, wherein the UE is configured to communicate with a network node.

[0288] D4. The communication system of the above three embodiments, wherein:

[0289] The processing circuitry of the host computer is configured to execute a host application, thereby providing user data; and

[0290] The UE includes processing circuitry configured to execute a client application associated with a host application.

[0291] D5. A method implemented in a communication system including a host computer, a network node and a user equipment (UE), the method comprising:

[0292] providing user data at a host computer; and

[0293] At a host computer, a transmission is initiated to carry user data to a UE via a cellular network including a network node, wherein the network node performs any of the steps of any of the embodiments of Group B.

[0294] D6. The method of the aforementioned embodiment further includes: transmitting user data at a network node.

[0295] D7. The method of the above two embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising: executing, at the UE, a client application associated with the host application.

[0296] D8. A user equipment (UE) configured to communicate with a network node, the UE comprising a radio interface and a processing circuit configured to perform any one of the above three embodiments.

[0297] D9. A communication system comprising a host computer, the host computer comprising:

[0298] processing circuitry configured to provide user data; and

[0299] a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),

[0300] Wherein the UE comprises a radio interface and a processing circuit, the components of the UE are configured to perform any of the steps of any of the embodiments in Group A.

[0301] D10. The communication system of the aforementioned embodiment, wherein the cellular network further comprises a network node configured to communicate with the UE.

[0302] D11. The communication system of the above two embodiments, wherein:

[0303] The processing circuitry of the host computer is configured to execute a host application, thereby providing user data; and

[0304] The processing circuitry of the UE is configured to execute a client application associated with a host application.

[0305] D12. A method implemented in a communication system including a host computer, a network node and a user equipment (UE), the method comprising:

[0306] providing user data at a host computer; and

[0307] At a host computer, a transmission is initiated to carry user data to a UE via a cellular network including a network node, wherein the UE performs any of the steps of any of the embodiments of Group A.

[0308] D13. The method described in the above embodiment further includes: at the UE, receiving user data from a network node.

[0309] D14. A communication system comprising a host computer, the host computer comprising:

[0310] a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a network node,

[0311] The UE comprises a radio interface and a processing circuit, and the processing circuit of the UE is configured to perform any of the steps of any of the embodiments in Group A.

[0312] D15. The communication system described in the above embodiment also includes UE.

[0313] D16. The communication system described in the above two embodiments further comprises a network node, wherein the network node comprises a radio interface configured to communicate with the UE and a communication interface configured to forward user data carried by transmissions from the UE to the network node to a host computer.

[0314] D17. The communication system of the above three embodiments, wherein:

[0315] The processing circuitry of the host computer is configured to execute a host application; and

[0316] The processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0317] D18. The communication system of the above four embodiments, wherein:

[0318] The processing circuitry of the host computer is configured to execute the host application, thereby providing the requested data; and

[0319] The processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing user data in response to the request data.

[0320] D19. A method implemented in a communication system including a host computer, a network node and a user equipment (UE), the method comprising:

[0321] At a host computer, user data transmitted from a UE to a network node is received, wherein the UE performs any of the steps of any of the embodiments in Group A.

[0322] D20. The method described in the above embodiment further includes: providing user data to the network node at the UE.

[0323] D21. The method of the above two embodiments further includes:

[0324] At the UE, executing a client application thereby providing user data to be transmitted; and

[0325] At the host computer, a host application associated with the client application is executed.

[0326] D22. The method of the above three embodiments further includes:

[0327] At the UE, executing a client application; and

[0328] At the UE, receiving input data to the client application, providing the input data at the host computer by executing a host application associated with the client application,

[0329] The user data to be transmitted is provided by the client application in response to the input data.

[0330] D23. A communication system comprising a host computer, the host computer comprising: a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a network node; wherein the network node comprises a radio interface and a processing circuit, the processing circuit of the network node being configured to perform any of the steps of any of the embodiments in Group B.

[0331] D24. The communication system of the aforementioned embodiment further includes a network node.

[0332] D25. The communication system of the above two embodiments further includes a UE, wherein the UE is configured to communicate with a network node.

[0333] D26. The communication system of the above three embodiments, wherein:

[0334] The processing circuitry of the host computer is configured to execute a host application;

[0335] The UE is configured to execute a client application associated with a host application, thereby providing user data to be received by the host computer.

[0336] D27. A method implemented in a communication system including a host computer, a network node and a user equipment (UE), the method comprising:

[0337] At a host computer, user data is received from a network node that originates from a transmission that the network node has received from a UE, wherein the UE performs any of the steps of any of the embodiments in Group A.

[0338] D28. The method described in the above embodiment further includes: receiving user data from the UE at the network node.

[0339] D29. The method described in the above two embodiments further includes: at the network node, initiating transmission of the received user data to the host computer.

[0340] D30. Wherein the network node in any of the above embodiments is a radio network node.

[0341] Appendix A

[0342] Title: Support for transmission in preconfigured UL resources

[0343] An objective is to specify the following improvements for machine type communications for BL / CE UEs:

[0344]

[0345]

[0346] This annex evaluates support for transmissions in preconfigured UL resources while remaining compliant with the protocol and keeping specification impact and implementation complexity to a minimum.

[0347] Transmission on Preconfigured UL Resources (PUR) in Idle Mode:

[0348] "Pre-configured UL resources based on idle mode are supported for UEs with valid TA", which includes two actions for further study "FFS: verification mechanism of TA" and "FFS: how to obtain pre-configured UL resources". The following subsections provide a possible framework for transmission on pre-configured UL resources in idle mode, which keeps the implementation and specification impact of RAN1 and other working groups to a minimum while meeting the WI objectives.

[0349] Two-step PUR transfer in IDLE mode:

[0350] In order to be able to transmit on preconfigured UL resources in idle mode, the UE must have acquired an initial timing advance (TA) and ensure that it is still valid when transmission on the preconfigured UL is intended to be performed. The initial timing advance command (which indicates the total distance between the UE and the cell) is signaled in the random access response. Thereafter, once the UE enters connected mode, the TA can be adjusted by advancing or delaying the uplink transmission timing.

[0351] The above indicates that the first step for a UE intending to transmit in preconfigured UL resources is to acquire an initial TA, which can be obtained by following a conventional connection establishment. As a second step, and for a later opportunity in IDLE mode, if the network has authorized the UE to transmit on preconfigured UL resources and the TA it maintains is still considered valid, the UE may benefit from transmitting on preconfigured UL resources. Furthermore, in order to give an answer to the question "FFS: How to acquire preconfigured UL resources", it is necessary to determine the type of traffic it is intended to evaluate by transmission on PUR. Accordingly, PUR uplink resources may be acquired, for example, periodically or on an on-demand basis.

[0352] Fig.18 An example of a two-step PUR transmission in IDLE mode is provided, which consists of the conventional sequence for initial access, followed by PUR configuration in connected mode, plus the actual PUR transmission in idle mode.

[0353] Step-1: Initial TA acquisition and pre-configuration of UL resources.

[0354] • Reuse the legacy connection establishment. From Msg2, the initial TA is stored for possible subsequent transmissions on the preconfigured UL resources.

[0355] In an RRC connection, the UE obtains a PUR configuration similar to an idle SPS via dedicated RRC signaling, which may include two configurable options depending on the type of service to be served:

[0356] o Recurring resources: This option is used when dealing with deterministic traffic, as the pre-configured UL resources will be available periodically.

[0357] DCI is used for activation / deactivation.

[0358] A timer may be used to indicate how long the resources are retained, in order to avoid potential waste of resources (e.g. in the event that the UE abandons the cell).

[0359] o Request per data transmission: This other option will be used when handling non-regular traffic, in which case pre-configured UL resources will become available on a per-request basis.

[0360] NOTE: When in connected mode, the TA may be adjusted, in which case the TA may be re-stored by the UE.

[0361] Step-2: PUR verification and transmission on pre-configured UL resources

[0362] When in idle mode, a UE that has previously gone through step-1 may directly transmit data in Msg3 (i.e., skip Msg1 and Msg2) if:

[0363] - A UE in idle mode has been authorized to transmit data in pre-configured UL resources.

[0364] - After testing the TA currently held by the UE by using any one of the TA validity mechanisms to be adopted by RAN1, it is considered valid.

[0365] - The PUR timer has not expired, which is the case in the reproducing resource method.

[0366] Otherwise, the conventional sequence for initial access restarts.

[0367] UE transmits PUR related data in "Msg3".

[0368] o Re-use resource: For subsequent transmissions on the PUR, the same UL grant is reused cyclically.

[0369] o Request for each data transmission: For subsequent transmissions on the PUR, the UE requests an UL grant (e.g. including the PUR interval and PUR-TBS)

[0370] The eNB receives "Msg3" and moves the UE to RRC_IDLE, or in case of further data, to RRC_CONNECTED via "Msg4".

[0371] o Re-appearance of resources: The timer used to maintain the UL resources for the PUR is extended and there is also the possibility to deactivate the re-appearance of resources from this message.

[0372] o Request for each data transmission: the eNodeB provides a UL grant via DCI.

[0373] The advantage of following the two-step approach for transmitting in pre-configured uplink resources is that the legacy connection establishment will be reused, while the actual PUR transmission will benefit from the signaling load reduction, power savings and reduced latency by transmitting directly on the "Msg3" of the EDT class frame, which will help to minimize the impact in RAN1 and other working groups (e.g. EDT security aspects can be inherited).

[0374] As an overview, these two steps can be performed as follows:

[0375] In a first step, the conventional connection establishment is reused to acquire the initial TA and obtain a pre-configuration of UL resources that may be used by the UE in future idle mode transmissions.

[0376] In the second step, after evaluating and satisfying some criteria (including TA validity), the UE may perform IDLE mode transmission on pre-configured UL resources directly on Msg3 (ie, skipping Msg1 and Msg2) by using a periodic or on-demand method.

[0377] Performing PUR transmission directly on Msg3 (i.e. skipping Msg1 and Msg2) will provide signaling load reduction, power savings and latency reduction, while using EDT-like frame operation to achieve this will help minimize the impact in RAN1 and other working groups.

[0378] The two-step PUR transmission scheme for idle mode can serve dedicated or shared uplink transmission. For example, the UL grant design for transmission on PUR can reuse sub-PRB allocation to increase spectrum efficiency, in which case up to four UEs can share the same PRB. In addition, HARQ retransmissions can also be supported by reusing the corresponding fields in the DCI used by the sub-PRB (e.g., HARQ process number, new data indicator).

[0379] TA validity mechanism:

[0380] Support of transmissions on pre-configured UL resources in idle mode relies on the condition of having a valid TA. Therefore, once an initial TA has been acquired and thereafter retained by a UE having stayed in or moved back to idle mode, a mechanism is needed that can be used to determine the validity of such a TA when idle mode transmissions on pre-configured UL resources are to be performed.

[0381] TA validity mechanism based on RSRP / RSRQ:

[0382] For stationary or low mobility devices, limited changes in idle mode service and neighbor cell signal strength can be expected. Therefore, a possible way to determine the validity of the retained TA configuration can be based on identifying large changes in idle mode service and neighbor cell signal strength (RSRP) and quality measurements (RSRQ).

[0383] For example, when the UE acquires the initial TA at time T0, it measures the downlink signal strength RSRP (T0) and compares it with the configured threshold RSRPTH. If RSRP (T0) > RSRPTH, the device considers this as an indication that it is near a base station. At a second time instance T1, higher layers in the device trigger idle mode data transmission, and the device again measures the absolute signal strength RSRP (T1) of the serving cell to compare it with the threshold RSRPTH. If RSRP (T1) > RSRP TH , the device interprets this as an indication that it is still in the vicinity of the base station and assumes that the stored TA (T0) value is still valid.

[0384] Another possibility could be that the device calculates the change in signal strength RSRP (T1) - RSRP (T0) in the serving cell before transmitting idle mode data. The change in this value would be considered an indication of mobility. If RSRP (T1) - RSRP (T0) is below a configured threshold, the device may assume that its TA (T0) value stored at time T0 is still valid and can be used to perform idle mode data transmission.

[0385] TA validity mechanism based on TDOA:

[0386] A stationary or low-mobility device may be expected to experience limited changes in the time difference of arrival (TDOA) of two or more reference signals received from two or more base stations.

[0387] Fig.19 A UE is shown receiving reference signals (RS) A and B transmitted from base stations eNB A and B. Based on the time of arrival (TOA) of each of these reference signals, the UE can calculate the TDOA between the two reference signals. Since each TOA corresponds to the distance between the base station and the UE, TDOA can be used as a strong indicator of mobility. Time-varying TDOA indicates mobility, while time-invariant TDOA indicates low or no mobility.

[0388] TA effectiveness mechanism based on cell radius:

[0389] The timing error tolerance provided by the cyclic prefix, together with the known serving cell radius, can be used to determine the effectiveness of the TA. Recall that step 1 T A Equal to 16T s = 0.52us, which is converted to meters as ((16Ts) (300000000)) / 2 = about 78m.

[0390] For example, in the case of small cell deployment, when a normal cyclic prefix (i.e., CP length 4.7 us) has been configured and the cell radius happens to be Y = 700 meters, the TA value currently maintained by the UE can be considered valid if it is less than a threshold value X = 8, which corresponds to ~624m (the calculation of the threshold can be summarized as floor (Y / ((16Ts c) / 2)) for any cell radius).

[0391] The above prevents UEs located in dotted coverage areas near the cell edge from transmitting with outdated / incorrect TA values ​​in the uplink.

[0392] TA validity mechanism based on TA history:

[0393] TA validity may be determined based on previously allocated TAs. For example, the eNodeB and / or the UE may keep track of previous TA values ​​allocated to a particular UE, and based on the frequency of updating the TA value, the eNodeB may understand whether the UE is a stationary or semi-stationary device. This information may then be used to determine whether the UE is allowed to directly apply some TA value the next time it intends to send UL data in idle mode, without having to obtain a new TA value.

[0394] More specifically, if the TA value estimated by the eNB and assigned to the UE does not change within a predetermined time (e.g., which may be tens of minutes, hours, or even days), the eNB and / or the network may identify the UE as a (semi-)stationary UE (in time) and may assign a TA value with a long-term validity time to it.

[0395] Timer-based TA validity mechanism:

[0396] Once the UE acquires a TA, the eNodeB provides a configurable timer (Time Alignment Timer), which can be UE-specific or cell-specific, which is used to control how long the UE is considered to be uplink time aligned. Similarly, a Time Alignment Timer for idle mode may be introduced, for example in conjunction with some other TA validity mechanism aimed at providing periodic TA refresh.

[0397] Appendix B

[0398] Title: Support for transmission in preconfigured UL resources

[0399] The appendix relates to improving uplink transmission efficiency and / or UE power consumption by transmission in preconfigured resources:

[0400] Improved UL transmission efficiency and / or UE power consumption:

[0401] For UEs with valid timing advance, transmission in pre-configured resources in idle and / or connected mode based on SC-FDMA waveform is specifically supported [RAN1, RAN2, RAN4]

[0402] o Shared and dedicated resources can be discussed

[0403] oNote: This is limited to orthogonal (multi) access schemes

[0404]

[0405] Due to the large-scale MTC nature of small amounts of infrequent data, we believe that Preconfigured Uplink Resources (PUR) are most relevant and beneficial in RRC_IDLE. Therefore, unless otherwise stated, we continue to discuss Idle-PUR. Connected PUR is discussed at the end of Section 2.4. In addition, the use case of uplink reporting is considered in the following discussion.

[0406] The UE is allowed to use a PUR "with valid timing advance". In conventional operation, in Msg2, the UE obtains a timing advance (TA) to apply to uplink transmissions to be received synchronously (timing advance command in RAR, see TS 36.321). The eNB configures a timer for the UE during which it should consider the timing advance valid (timeAlignmentTimer in MAC-MainConfig in TS 36.331), and after the expiration of this timer, the UE must perform random access again to obtain a new timing advance. Since it is specified that the UE must have a valid TA for the Rel-16 PUR, there are two options: 1) the UE is stationary enough to reuse its previous TA, i.e., moves within the length of the cyclic prefix, or 2) the UE moves but constantly updates the TA to keep it valid. For option 2), signaling is required in order to work. For example, random access is triggered every time the UE moves beyond the distance that the cyclic prefix can cover. In any case, uplink transmission is required, which has a negative impact on the two KPIs that the WI goal attempts to improve: UL transmission efficiency and UE power consumption.

[0407] It is not feasible to maintain a valid timing advance for a mobile UE in RRC_IDLE.

[0408] Transmissions in preconfigured uplink resources in RRC_IDLE are restricted to UEs that can reuse their timing advance relative to previous transmissions.

[0409] For legacy operation, the eNB may base the length of the timeAlignmentTimer on UE speed, cell size, etc. In addition, a low mobility UE will not move very far during the relatively short time in RRC_CONNECTED. However, for a PUR, the UE may be in RRC_IDLE for several hours and then return to transmit. A timer-based solution is not sufficient because the eNB has no way to estimate whether the UE's TA will be valid when it returns. Therefore, since the UE will be in RRC_IDLE, requirements for the UE will be needed. That is, the UE should meet certain conditions to check that the TA is valid before PUR access.

[0410] The UE must meet certain requirements to ensure that its timing advance is valid before accessing the pre-configured uplink resources.

[0411] Furthermore, again based on conventional operation, the UE must transmit at least once in the UL in order to be assigned a TA. That is, in practice the PUR will not be applicable to the initial transmission in a cell.

[0412] Since the UE has to obtain timing advance, for initial transmission in a cell, transmission in the pre-configured uplink resources is not possible.

[0413] Therefore, the initial data transmission requires conventional transmission, and the most straightforward solution is to configure the PUR via dedicated RRC signaling.

[0414] Transmission in the pre-configured uplink resources is configured by dedicated RRC signaling.

[0415] For the actual data transport, there are potentially many RAN2 open issues. If RAN1 agrees generally to some new physical channel for PUR transport (potentially only supporting a smaller TBS), RAN2 needs to ensure there is a solution for working data addressing / routing, working retransmissions, potential contention resolution, security, etc. This may require a lot of RAN2 work and will have to look at all protocol layers; MAC, RLC, PDCP, etc.

[0416] Transmission in preconfigured uplink resources may potentially have many RAN2 impacts.

[0417] However, data transmission can reuse the extensive work of Rel-15 EDT, where all these issues have been addressed. That is, for both solutions considered below, the data transmission part can be done similarly to the EDT data transmission in Msg3. RAN2 can also potentially consider reusing the EDT Msg3 and Msg4 RRC messages or using them as a baseline for the new PUR RRC messages. This will address all the open issues mentioned above.

[0418] Rel-15 EDT Msg3 / Msg4 data transmission is used as a baseline for transmission in pre-configured uplink resources.

[0419] Contention-free or contention-based data transmission:

[0420] For RAN2, it does not matter whether the PUR resources that the UE is configured with are dedicated or shared radio resources. For example, a UE-specific code for CDMA may be allocated to the UE in the shared resources. However, it is important whether the PUR data transmission is contention-based or contention-free.

[0421] Contention-based PUR:

[0422] For contention-based PUR. Fig.16As shown, the UE will be given a common PUR configuration and TA in the initial access. These common PURs can be selected by any UE, and sending data there will be at risk of collision. The configuration may be most motivated as a periodic resource, much like how PRACH is configured. In a similar way, different CE levels will have to be supported, and in addition several TBSs must be supported, which may make this solution very resource intensive.

[0423] When data arrives, the UE will select the subsequent periodic PUR to transmit its data. There is no need to know the traffic predicted by the UE. However, the transmission will be performed at the risk of collision, and if no improvements are made at the PHY layer, the risk of collision is x64 or x48 compared to the legacy of LTE-M and NB-IoT, respectively, due to the lack of preamble selection. If it cannot be ensured that the risk of collision is lower than the legacy process (i.e., compared to EDT), the public PUR may perform worse than the legacy process. If so, it will be difficult to start a contention-based PUR. In addition, according to the legacy process, HARQ retransmissions will not be possible in this case because the eNB cannot perform soft combining. That is, it is impossible to schedule retransmissions, or if subsequent public PUR resources are used, it is impossible to know whether it is a retransmission.

[0424] Since the resources will be used by any UE, it is not possible to take advantage of higher UE capabilities unless the PUR feature is limited to those UEs. Due to this fact, contention-based PUR may be best suited for use cases with sparse traffic, where most often nothing is transmitted, such as alarms, etc. Even then, the uplink efficiency gain is highly questionable, but the UE will have slightly reduced power consumption because Msg1 and Msg2 can be omitted. Is this reduction significant when most often no transmissions are still visible?

[0425] Therefore, contention-based transmission in preconfigured uplink resources can be justified by use cases with sparse and rare transmissions, such as alarms, etc.

[0426] For non-contention PUR, such as Fig.17 As shown, dedicated PUR resources and TA will be given to the UE in the initial access. PUR resources can be configured to be customized for UE service profile, capability and CE level. In addition, PUR transmission will be guaranteed to be conflict-free. Therefore, as long as the configured resources are used, the gain of uplink transmission efficiency and UE power consumption will be ensured.

[0427] A potential problem is to configure dedicated radio resources for UEs in RRC_IDLE mode. That is, the eNB does not usually track UEs in RRC_IDLE mode, and reserving radio resources for UEs that may no longer be in the cell will reduce UL transmission efficiency rather than improve it, because resources will be wasted. However, there is no reason why periodic resources must be reserved. At this time, dedicated PUR resources can be reserved for one PUR transmission. That is, only one PUR resource is allocated, and after that, the transmission resources are reserved for the next PUR transmission, and so on. This will greatly limit the potential waste of resources and make this feature useful for more use cases with periodic services. Alternatively, resource reservation can be timer-based. For dedicated pre-configured uplink resources, the following advantages can be achieved: less resource waste, resources are allocated only when needed; adapted to UE, no additional resource waste from multiple CE levels, TBS, etc.; conflict-free guarantees gains in UE power consumption and ULTx efficiency; UE-specific higher data rates are possible (i.e., obtained from capabilities such as multi-tone, Cat-M2 / Cat-NB2, etc.); HARQ retransmission.

[0428] Therefore, contention-free PUR can be considered a good solution due to less system overhead and guaranteed gain according to the WI target.

[0429] Therefore, transmission in preconfigured uplink resources is supported in RRC_IDLE in dedicated resources.

[0430] For dedicated PUR, some UE-specific parameters will have to be configured by dedicated RRC signaling. These can be, for example, the PUR interval (i.e., resource time offset), the PUR TBS, any allocation information of the PUR resource, etc. As mentioned above, allocating only one PUR resource at a time has great potential benefits, and the same principles as the Rel-12 power saving mode (PSM) can be applied. That is, for each uplink transmission, the UE will request the PUR interval and PUR-TBS, and the network will respond with the configuration parameters that the UE should apply. This automatically reduces resource waste because if the UE leaves the cell or does not transmit in the PUR resource for other reasons, at most one transmission opportunity is wasted. In addition, if the TBS or interval should change, it is more adaptive. Of course, if the interval and TBS are always the same for some UEs, the disadvantage is the signaling overhead. However, this can be easily solved by declaring a flag that the same interval and TBS as the last time should be applied.

[0431] Therefore, the dedicated transmission in the pre-configured uplink resources is configured for one transmission opportunity at this time.

[0432] As shown, the UE will be configured during an RRC connection (or EDT transmission). Both the eNB and the UE will need to have a common understanding of when subsequent transmissions will occur.

[0433] Therefore, the interval (time resource offset) and TBS are used as configuration parameters for dedicated transmission in pre-configured uplink resources.

[0434] The network will need to store these parameters when the UE moves to RRC_IDLE. For the CIoT UP solution (RRC Suspend / Resume), this will mean adding the PUR parameters to the stored UE context. For the CIoT CP solution (DoNAS), this will mean adding the PUR parameters to the UE context stored in the MME. In addition, it must be ensured that the scheduler is aware of all these PUR opportunities.

[0435] Therefore, configuration parameters for pre-configuring uplink resources are added to the UE context.

[0436] Above, PURs in RRC_IDLE have been discussed, but the WI target potentially also includes PURs in RRC_CONNECTED. First, consider the public PUR in a connection. The UE has gone through the random access procedure to obtain a connection and dedicated radio resources for transmission. Then, sending data in public resources with the risk of collision and retransmission is less efficient than triggering a scheduling request.

[0437] On the other hand, a dedicated PUR in a connection will be very similar to SPS. Note that LTE-M already supports SPS, while for NB-IoT, no strong need is seen in Rel-15, and SPS support in Rel-15 is only introduced in BSR. However, since a large number of MTC services are not completely periodic at the subframe level, like VoIP, where SPS was originally introduced, some PUR modifications for SPS will still be needed. For example, as discussed above for idle mode, a PUR resource is configured at this time.

[0438] Transmissions in preconfigured uplink resources in RRC_CONNECTED are considered in dedicated resources (contention-free) but not in common resources (contention-based).

[0439] exist Fig. 20 An example of a signaling diagram for a PUR configuration is given in FIG. Note that this is a conventional connection establishment procedure assuming initial access in a cell.

[0440] Abbreviations

[0441] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between abbreviations, the above usage should take precedence. If listed multiple times below, the first listing should take precedence over the subsequent (one or more) listings.

[0442] 3GPP Third Generation Partnership Project

[0443] ACB access level restriction

[0444] BI back-off instructions

[0445] BSR Buffer Status Report

[0446] Cat-M1 Category M1

[0447] Cat-M2 Category M2

[0448] CE coverage enhancement

[0449] DL Downlink

[0450] EAB extended access prohibition

[0451] eMTC Enhanced Machine Type Communication

[0452] eNB Evolved NodeB

[0453] EDT Early Data Transfer

[0454] IoT

[0455] LTE Long Term Evolution

[0456] LTE-M Long Term Evolution Machine Type Communications

[0457] LTE-MTC Long Term Evolution Machine Type Communications

[0458] MAC Media Access Control

[0459] NAS non-access layer

[0460] NB-IoT Narrowband Internet of Things

[0461] M2M Machine to Machine

[0462] MCS modulation and coding scheme

[0463] MTC Machine Type Communication

[0464] PDU protocol data unit

[0465] PUR pre-configured uplink resources

[0466] (N)PRACH (narrowband) physical random access channel

[0467] PRB Physical Resource Block

[0468] PUR pre-configured uplink resources

[0469] RA Random Access

[0470] RAPID Random Access Preamble Identifier

[0471] RAR Random Access Response

[0472] RNTI Radio Network Temporary Identifier

[0473] RRC Radio Resource Control (protocol)

[0474] TBS transport block size

[0475] UE User Equipment

[0476] UL Uplink

[0477] WI Work Project

[0478] 1x RTT CDMA2000 1x Radio Transmission Technology

[0479] 3GPP Third Generation Partnership Project

[0480] 5G fifth generation

[0481] ABS Almost Blank Subframe

[0482] ARQ Automatic Repeat Request

[0483] AWGN Additive White Gaussian Noise

[0484] BCCH Broadcast Control Channel

[0485] BCH Broadcast Channel

[0486] CA Carrier Aggregation

[0487] CC carrier component

[0488] CCCH SDU Common Control Channel SDU

[0489] CDMA Code Division Multiple Access

[0490] CGI Cell Global Identifier

[0491] CIR channel impulse response

[0492] CP cyclic prefix

[0493] CPICH Common Pilot Channel

[0494] CPICH Ec / No The energy received by each CPICH chip divided by the power density in the frequency band

[0495] CQI channel quality information

[0496] C-RNTI Cell RNTI

[0497] CSI Channel State Information

[0498] DCCH dedicated control channel

[0499] DL Downlink

[0500] DM Demodulation

[0501] DMRS demodulation reference signal

[0502] DRX Discontinuous Reception

[0503] DTX Discontinuous Transmission

[0504] DTCH Dedicated Traffic Channel

[0505] DUT Device Under Test

[0506] E-CID Enhanced Cell-ID (positioning method)

[0507] E-SMLC Evolved Service Mobile Location Center

[0508] ECGI Evolved CGI

[0509] eNB E-UTRAN Node B

[0510] ePDCCH Enhanced Physical Downlink Control Channel

[0511] E-SMLC Evolved Service Mobile Location Center

[0512] E-UTRA Evolved UTRA

[0513] E-UTRAN Evolved UTRAN

[0514] FDD Frequency Division Duplex

[0515] FFS needs further study

[0516] GERAN GSM EDGE Radio Access Network

[0517] Base stations in gNB NR

[0518] GNSS Global Navigation Satellite System

[0519] GSM Global System for Mobile Communications

[0520] HARQ Hybrid Automatic Repeat Request

[0521] HO Handover

[0522] HSPA High Speed ​​Packet Access

[0523] HRPD High Rate Packet Data

[0524] LOS Line of Sight

[0525] LPP LTE Positioning Protocol

[0526] LTE Long Term Evolution

[0527] MAC Media Access Control

[0528] MBMS Multimedia Broadcast Multicast Service

[0529] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0530] MBSFN ABS MBSFN Almost Blank Subframe

[0531] MDT Minimization of Drive Test

[0532] MIB Master Information Block

[0533] MME mobility management entity

[0534] MSC Mobile Switching Center

[0535] NPDCCH narrowband physical downlink control channel

[0536] NR New Radio

[0537] OCNG OFDMA Channel Noise Generator

[0538] OFDM Orthogonal Frequency Division Multiplexing

[0539] OFDMA Orthogonal Frequency Division Multiple Access

[0540] OSS Operation Support System

[0541] OTDOA Observation Time Difference

[0542] O&M Operation and Maintenance

[0543] PBCH Physical Broadcast Channel

[0544] P-CCPCH Primary Common Control Physical Channel

[0545] PCell Primary Cell

[0546] PCFICH Physical Control Format Indicator Channel

[0547] PDCCH Physical Downlink Control Channel

[0548] PDP Power Delay Profile

[0549] PDSCH Physical Downlink Shared Channel

[0550] PGW Packet Gateway

[0551] PHICH Physical Hybrid ARQ Indicator Channel

[0552] PLMN Public Land Mobile Network

[0553] PMI precoder matrix indicator

[0554] PRACH Physical Random Access Channel

[0555] PRS Positioning Reference Signal

[0556] PSS primary synchronization signal

[0557] PUCCH Physical uplink control channel

[0558] PUSCH Physical uplink shared channel

[0559] RACH Random Access Channel

[0560] QAM Quadrature Amplitude Modulation

[0561] RAN Radio Access Network

[0562] RAT Radio Access Technology

[0563] RLM Radio Link Management

[0564] RNC Radio Network Controller

[0565] RNTI Radio Network Temporary Identifier

[0566] RRC Radio Resource Control

[0567] RRM Radio Resource Management

[0568] RS reference signal

[0569] RSCP received signal code power

[0570] RSRP reference symbol received power or

[0571] Reference signal received power

[0572] RSRQ Reference Signal Received Quality or

[0573] Reference symbol reception quality

[0574] RSSI Received Signal Strength Indicator

[0575] RSTD Reference Signal Time Difference

[0576] SCH synchronization channel

[0577] SCell secondary cell

[0578] SDU Service Data Unit

[0579] SFN system frame number

[0580] SGW Service Gateway

[0581] SI system information

[0582] SIB System Information Block

[0583] SNR signal-to-noise ratio

[0584] SON Self-Optimizing Network

[0585] SS sync signal

[0586] SSS secondary synchronization signal

[0587] TDD Time Division Duplex

[0588] TDOA Time Difference of Arrival

[0589] TOA Arrival Time

[0590] TSS three-level synchronization signal

[0591] TTI transmission time interval

[0592] UE User Equipment

[0593] UL Uplink

[0594] UMTS Universal Mobile Telecommunications System

[0595] USIM Universal Subscriber Identity Module

[0596] UTDOA uplink time difference of arrival

[0597] UTRA Universal Terrestrial Radio Access

[0598] UTRAN Universal Terrestrial Radio Access Network

[0599] WCDMA Wide CDMA

[0600] WLAN

Claims

1. A method performed by a wireless device, the method comprising: receiving (100) signaling indicating configuration of one or more preconfigured resources on a first link; receiving (110) information indicating whether the wireless device is allowed or not allowed to use one of the preconfigured resources; as well as The preconfigured resources are used or not used (120) depending on the received information.

2. The method according to claim 1, wherein: The information includes access prohibition information, where the access prohibition information indicates whether access to the first link using the pre-configured resources is prohibited.

3. The method according to any one of claims 1 to 2, wherein: The information includes access barring information indicating whether access to the first link using one or more next occurrences of the preconfigured resources is prohibited.

4. The method according to any one of claims 1 to 2, wherein: The information includes access barring information indicating whether a group of wireless devices or a group of wireless devices within a specific coverage area is prohibited from accessing the first link using the preconfigured resources.

5. The method according to any one of claims 1 to 2, wherein: The information includes access barring information indicating whether access to the first link using any preconfigured resources is prohibited.

6. The method according to claim 2, wherein: The access barring information is specific to the pre-configured resources.

7. The method according to any one of claims 1 to 2 and 6, wherein: The information is system information broadcast on the first link.

8. The method according to any one of claims 1 to 2 and 6, wherein: The information is included in system information block 2 SIB2, or in system information block 14 SIB14.

9. The method according to claim 7, wherein: The system information is included in a system information block 1 SIB1 or a master information block MIB.

10. The method according to any one of claims 1 to 2 and 6, wherein: The information indicates whether a group of wireless devices are allowed or not allowed to use the preconfigured resources.

11. The method according to any one of claims 1 to 2 and 6, wherein: The one or more preconfigured resources include a plurality of groups of preconfigured resources, and wherein the information indicates whether use of one of the plurality of groups of preconfigured resources is allowed or not allowed.

12. The method according to any one of claims 1 to 2 and 6, wherein: The information indicates the reason why the use of the preconfigured resource is not allowed.

13. The method according to any one of claims 1 to 2 and 6, wherein: The information also indicates an alternative way for the wireless device to access a wireless communication network.

14. The method according to any one of claims 1 to 2 and 6, wherein: The signaling indicates a time interval during which the configuration of the pre-configured resource is valid.

15. The method according to any one of claims 1 to 2 and 6, wherein: The pre-configured resource is a pre-configured uplink resource PUR.

16. The method according to any one of claims 1-2 and 6, wherein: The information indicates whether the wireless device is authorized or unauthorized to use the preconfigured resources.

17. The method according to claim 16, wherein: The information indicates whether the wireless device is authorized or unauthorized to use the preconfigured resource by indicating whether the wireless device is blacklisted from using the preconfigured resource.

18. The method according to any one of claims 1 to 2 and 6, wherein: The information is received via Radio Resource Control (RRC) or Non-Access Stratum (NAS) signaling and / or stored as part of a context or subscription of the wireless device.

19. The method according to any one of claims 1 to 2 and 6, wherein: The information denies the wireless device's request for the preconfigured resources or a request for use of the preconfigured resources.

20. The method according to any one of claims 1-2 and 6, further comprising: After or as part of a mobility procedure to change the wireless device from the first link to a second link, control signaling indicating any pre-configured resources configured on the first link is transmitted, wherein the control signaling is transmitted to a radio network node serving the second link or a network node configured to perform mobility management.

21. The method according to claim 20, wherein: The control signaling indicates an identifier of the first link and an identifier of each preconfigured resource configured on the first link.

22. A method performed by a network node, the method comprising: determining (200) whether the wireless device is allowed or not allowed to use preconfigured resources on the first link; as well as Information is transmitted (210) indicating whether the wireless device is allowed or not allowed to use the preconfigured resources on the first link.

23. The method according to claim 22, wherein: Determining whether the wireless device is allowed to use the preconfigured resources on the link is based on one or more of the following: the load on the preconfigured resources; The priority of the wireless device; and The type of transmission to be performed by the wireless device or the priority of the transmission.

24. The method according to any one of claims 22-23, wherein: The information includes access barring information indicating whether access to the first link using the preconfigured resources is prohibited.

25. The method according to any one of claims 22-23, wherein: The information includes access barring information indicating whether access to the first link using one or more next occurrences of preconfigured resources is prohibited.

26. The method according to any one of claims 22-23, wherein: The information includes access barring information indicating whether a group of wireless devices are barred from accessing the first link using the preconfigured resources at a specific coverage level.

27. The method according to any one of claims 22-23, wherein: The information includes access barring information, the access barring information being specific to the preconfigured resources.

28. The method according to any one of claims 22-23, wherein: The information is system information broadcast on the first link.

29. The method according to any one of claims 22-23, wherein: The information is included in system information block 2 SIB2, or in system information block 14 SIB14.

30. The method of claim 28, wherein: The system information is included in a system information block 1 SIB1 or a master information block MIB.

31. The method according to any one of claims 22-23, wherein: The preconfigured resources include a plurality of groups of preconfigured resources, and wherein the information indicates whether use of one of the plurality of groups of preconfigured resources is permitted or not permitted.

32. The method according to any one of claims 22-23, wherein: The information indicates the reason why the use of the preconfigured resource is not allowed.

33. The method according to any one of claims 22-23, wherein: The information also indicates an alternative way for the wireless device to access a wireless communication network.

34. The method according to any one of claims 22-23, wherein: The pre-configured resource is a pre-configured uplink resource PUR.

35. The method according to any one of claims 22-23, wherein: The information indicates whether the wireless device is authorized or unauthorized to use the preconfigured resources.

36. The method of claim 35, further comprising: Determining whether the wireless device is authorized or unauthorized to use the preconfigured resources based on one or more of: prior misuse of preconfigured resources by the wireless device; The wireless device has not previously used the preconfigured resources; inactivity of said wireless device; separation or switching of the wireless device; as well as A radio link failure experienced by the wireless device.

37. The method of claim 35, further comprising: Whether the wireless device is authorized or unauthorized to use the preconfigured resources is determined based on: subscription information of the wireless device, a context of the wireless device, a class or capability of the wireless device, subscription-based differentiation information of the wireless device, a coverage enhancement level of the wireless device, a quality of service of the wireless device, or a quality of service classification identifier of the wireless device.

38. The method of claim 35, wherein: The information indicates whether the wireless device is authorized or unauthorized to use the preconfigured resource by indicating whether the wireless device is blacklisted from using the preconfigured resource.

39. The method of claim 35, further comprising: receiving signaling from a radio network node serving a second link or a network node configured to perform mobility management, the signaling indicating that the wireless device has changed to the second link and / or that the wireless device has left the first link; as well as Based on the received signaling, it is determined that the wireless device is no longer authorized to use the preconfigured resources on the first link.

40. The method of claim 39, wherein: The signaling includes a context of the wireless device, and the context indicates that the wireless device has changed to the second link and / or that the wireless device has left the first link.

41. The method according to any one of claims 22-23, wherein: The information is transmitted via Radio Resource Control (RRC) or Non-Access Stratum (NAS) signaling and / or retrieved from or based on the context or subscription of the wireless device.

42. The method according to any one of claims 22-23, wherein: The information denies the wireless device's request for the preconfigured resources or a request for use of the preconfigured resources.

43. The method according to any one of claims 22-23, further comprising: After or as part of a mobility procedure that changes the wireless device from a source link to the first link, control signaling is received that indicates any pre-configured resources configured for the wireless device on the source link.

44. The method according to any one of claims 22-23, further comprising: After or as part of a mobility procedure that changes the wireless device from the first link to a second link, control signaling is transmitted that indicates any pre-configured resources configured for the wireless device on the first link.

45. A wireless device (300), the wireless device (300) comprising: a communication circuit (320) configured to communicate with a network; A processing circuit (310) operably coupled to the communication circuit (320) and configured to: receiving signaling indicating configuration of preconfigured resources on a first link; receiving information indicating whether the wireless device is allowed or not allowed to use the preconfigured resources; as well as The preconfigured resources are used or not used according to the received information.

46. ​​The wireless device (300) of claim 45, wherein: The processing circuit (310) is configured to perform the method according to any one of claims 2 to 21.

47. A network node (500), the network node (500) comprising: a communication circuit (520) configured to communicate with a network; A processing circuit (510) operably coupled to the communication circuit (510) and configured to: determining whether to allow the wireless device to use preconfigured resources on the first link; as well as Information is transmitted indicating whether the wireless device is allowed or not allowed to use the preconfigured resources on the first link.

48. The network node (500) of claim 47, wherein: The processing circuit (510) is configured to perform the method according to any of claims 23-44.

49. A wireless device (400), comprising: A configuration receiving unit (410) configured to receive signaling indicating configuration of pre-configured resources on a first link; An information receiving unit (420) is configured to receive information indicating whether the wireless device is allowed or not allowed to use the preconfigured resources; and The radio resource using unit (430) is configured to use or not use the pre-configured resources according to the received information.

50. The wireless device (400) of claim 49, wherein: The wireless device (400) is configured to perform the method according to any one of claims 2 to 21.

51. A network node (600), comprising: A determination unit (610) configured to determine whether to allow the wireless device to use the preconfigured resources on the first link; as well as An information transmission unit (620) is configured to transmit information indicating whether the wireless device is allowed or not allowed to use the preconfigured resources on the first link.

52. The network node (600) of claim 51, wherein: The network node is configured to perform the method according to any of claims 23-44.

53. A computer program product comprising computer program instructions stored thereon for execution by a processor in a wireless device (300), the computer program instructions being configured to cause the wireless device (300) to perform a method according to any one of claims 1-21.

54. A computer program product comprising computer program instructions stored thereon for execution by a processor in a network node (500), the computer program instructions being configured to cause the network node (500) to perform a method according to any of claims 22-44.

55. A computer readable medium having computer program instructions stored thereon for execution by a processor in a wireless device, the computer program instructions being configured to cause the wireless device to perform the method according to any one of claims 1-21.

56. A computer readable medium having computer program instructions stored thereon for execution by a processor in a network node, the computer program instructions being configured to cause the network node to perform a method according to any one of claims 22-44.

Images