Methods and nodes on signaling behavior for terminating a device from current occasion for the purpose of re-access

Abstract

There is provided a method performed by a wireless device. The method comprises: receiving a paging message, from a network node, the paging message triggering an access procedure with the network node; initiating the access procedure with the network node; receiving a message from the network node, the message comprising an indication to terminate an ongoing access procedure with the network node; and terminating the access procedure with the network node, wherein terminating the access procedure is considered as a failed procedure.

Description

Pl 12880 W02Methods and Nodes On Signaling Behavior for Terminating a Device from Current Occasion for the purpose of Re-accessRELATED APPLICATIONS

[0001] This application claims the benefits of priority of PCTPCT / CN2025 / 076111, entitled “On Signaling Behavior for Terminating a Device from Current Occasion for the purpose of Re-access” and filed at the CNIPA on February 7, 2025, which is hereby incorporated by reference in its entirety.TECHNICAL FIELD

[0002] This application relates to communication networks and particularly to methods and nodes for signaling a device about terminating its current occasion for the purpose of a reaccess procedure.BACKGROUND

[0003] Zero-Energy (ZE) Internet of Things (loT) & Ambient-IoT (A-IoT)

[0004] Wireless loT devices are often battery powered and both the need to change battery and the battery lifetime may be concerns for many potential applications such as asset tracking or environmental / industrial sensors. For this reason, the wireless communications industry has been interested in so-called zero-energy (ZE) devices. ZE devices refer to wireless loT devices that do not require battery replacement, and often harvest energy from the environment. In some use cases, such as monitoring the temperature of foodstuffs, the ZE devices may have small batteries that are disposable (e.g., organic, compostable batteries), rechargeable or have very limited capacity.

[0005] These ZE-IoT devices can in addition be of very small form factor and could even be printable and they target ultra-low power consumption to enable operation based on either energy-harvesting from an ambient sources or back-scattering communication (cf. Radio Frequency Identification (RFID)). That is, instead of relying on energy for communication being provided by a battery it is instead harvested from an ambient source, such as vibrations, solar power, radio frequency (RF), etc. (harvesting), or a charge carrier wave is provided to the device which is modulated and reflected back to a reader (in the back-scattering communication case). This enables energy autonomous operation during the lifetime of the devices without need for either manual replacement or charging of the batteries. Compared to existing radio access technologies this puts new requirements on the radio interface and the protocols.

[0006] Connectivity topologiesPl 12880 W02

[0007] The following connectivity topologies for A-IoT networks and devices are defined for the purposes of the study. In all these topologies, the A— loT device may be provided with a carrier wave from other node(s) either inside or outside the topology. The links in each topology may be bidirectional or unidirectional.

[0008] Base Station (BS), User Equipment (UE), assisting node, or intermediate node could be multiple BSs or UEs, respectively. The mixture of indoor and outdoor placement of such nodes is regarded as a network implementation choice. Account would need to be taken of potential impact on device or node complexity. In the connectivity topologies, this does not imply the existence of multi-hop assisting or intermediate nodes. Different topologies are illustrated in Fig. 1 to Fig. 5 respectively.

[0009] Topology I : BS A-IoT device

[0010] In Topology 1, the A-IoT device directly and bidirectionally communicates with a base station. The communication between the BS and the A-IoT device includes A- loT data and / or signalling. This topology includes the possibility that the BS transmitting to the A-IoT device is a different from the BS receiving from the A-IoT device. This is illustrated in Fig. 1.

[0011] Topology 2: BS intermediate node A-IoT device

[0012] In Topology 2, the A-IoT device communicates bidirectionally with an intermediate node between the device and BS. In this topology, the intermediate node can be a relay, IAB node, UE, repeater, etc. which is capable of A-IoT. The intermediate node transfers A-IoT data and / or signalling between BS and the A- loT device. This is illustrated in Fig. 2.

[0013] Topology 3: BS «-> assisting node A-IoT device BS

[0014] In Topology 3, the A- loT device transmits data / signalling to a base station, and receives data / signalling from the assisting node; or the A-IoT device receives data / signalling from a base station and transmits data / signalling to the assisting node. In this topology, the assisting node can be a relay, IAB, UE, repeater, etc. which is capable of A- loT. This is illustrated in Figs. 3 and 4 respectively.

[0015] Topology 4: UE A- loT device

[0016] In Topology 4, the A- loT device communicates bidirectionally with a UE. The communication between UE and the A-IoT device includes A- loT data and / or signalling. This is illustrated in Fig. 5.

[0017] Functional and protocol simplifications for A / ZE loT

[0018] For A-IoT, 3GPP will target an loT segment well below the existing Cellular (C) loT technologies rather than replacement of existing 3GPP PLWA technologies. It is expected that together with simplifications in physical layer design, the higher layer (L2 / L3) design willPl 12880 W02also be much more lightweighted than the existing higher layer design in 3GPP, i.e., a minimal set of functionalities (both at access stratum (AS) and non-access stratum (NAS) levels), which is even more simplified compared to that adopted for the existing CIoT technologies, should be used to operate A-IoT devices. One way of such simplifications is to design a communication protocol shifted from fully connection oriented with both NAS and Radio Resource Control (RRC) connections between device and network to connectionless type of communication without RRC connections or even also no NAS connections between device and network so that the protocol and signaling overhead associated with the handshaking between device and network is minimized. This means that A-IoT devices do not setup and maintain an RRC connection with the network, also A-IoT devices do not setup and maintain AS context including (dedicated) radio bearer, logical channel, etc.

[0019] One way to implement connectionless communication is to employ message-based or self-contained transmission where context / control information associated with the signaling / data traffic is transmitted together with or right after the signaling / data traffic where in the latter case (i.e., the right after case) there is no other transmission between the context / control information and the associated signaling / data traffic carrying information that is needed for reception of the signaling / data traffic. One such example is that in DL the signaling / data traffic is transmitted within or right after the paging message.SUMMARY

[0020] There currently exist certain challenge(s). In a work item, the below objectives are defined in RAN2 scope:

[0021] - Specify the necessary functions and procedures for an Ambient loT compact protocol stack and lightweight signalling procedure to enable DO-DTT and DT data transmission:a. A-IoT Paging, including subsequent paging for the same service.Support the options that a paging message contains one identifier, and that a paging message contains no identifier. Temporary identifier is not supported, unless required by SA WGs.b. Note: RAN2 aims to design a paging message format such that multiple identifiers can be contained in one paging message, for forward compatibility purposes.c. A-IoT Random access, including re-access for failure handling.Contention-based and contention-free cases are supported. For the contention-based random access, only Solution 1 (3-step only) isPl 12880 W02included (unless RAN2 decides to use Solution 3 (unified solution) by RAN2#129).d. A-IoT data transmission, including data (re-)transmission for failure handling. Segmentation is supported at least in D2R.e. Only MAC layer is included

[0022] Among the above objectives, both re-access and data (re)transmission are considered as options for failure handling (e.g., data transmission failure). However, below issues are expected to be addressed during the WI phase.

[0023] Issue 1: the conditions under which either or both mechanisms are triggered / performed.

[0024] Issue 2: how to perform both mechanisms in an integrated manner.

[0025] For a 3 step (or 4 step) Contention-Based Random Access (CBRA) procedure, it has been agreed that Msg4, feedback to Msg3 (transmission from the device in uplink (UL)) in an occasion of inventory / access round is optional. It is expected that the reader can indicate whether the reader will provide a feedback message during subsequent access occasions / rounds in an initial trigger message / paging message upon initiating the subsequent access round.

[0026] During an inventory procedure, if a device is constantly failing to transmit successfully, e.g., with Msg3 transmission attempts based on the reader’s feedback (e.g., via any variety of implicit / explicit N / ACK), then the reader may prefer to schedule no further resources in the current access round or it can postpone its access procedure. The reason can be, e.g., coverage issues, poor allocation parameters, etc. In such scenarios, a mechanism is needed where a device currently engaged in an inventory procedure associated with a given service request / transaction can be altered or modified, such that the device can be offloaded, e.g., through a new access round / procedure, etc. As one example, the CBRA with 4-step RA type for a UE and a gNB is illustrated in Fig. 6 as given by 3GPP TS 38.300 v.18.4.0. Fig. 6 can be used with an A-IoT device as well.

[0027] In addition, in cases where a 2-step Random Access (RA) procedure is used by the device, absence of a (repeated) Msg2 / MsgB upon Msgl / MsgA transmission does not lead to the device autonomously retransmitting or re-accessing the network. As the transmission of Msg2 is up to reader implementation, the cases for which Msgl is received by the reader but no corresponding Msg2 is transmitted vs. Msgl is transmitted but not received by the reader or Msg2 is not received by the device are not distinguishable. In the context of transmissions and transmission failures by devices, a Msgl transmission and transmission failure can be considered equivalent to that of Msg3. As one example, the CBRA with 2-step RA type for aPl 12880 W02UE and a gNB is illustrated in Fig. 7 as given by 3GPP TS 38.300 v.18.4.0. 6. Fig. 7 can be used with an A-IoT device as well.

[0028] If a transmission failure is an issue for the inventory procedure for some devices, it may not necessarily need to be resolved in that inventory round or if some devices have a different assumption with respect to the reader regarding whether they have responded to the reader successfully. One can assume that it is up to the network to follow up on those devices.

[0029] However, if too many devices have failed with their Msg3 transmissions in an inventory / access round or assumed differently with respect to the network whether they have responded successfully, e.g., due to implicit ACK, then, transmission failure becomes an issue and a solution is required.

[0030] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.

[0031] There is provided a method where a device which is engaged in paging or access round, i.e., accessing an occasion provided by paging (triggered by a core network (CN) / AF or RAN), can be provided with a re-access opportunity if it’s failing or failed to have a transmission success during this paging / access round. The re-access related message can be provided by a reader to one or more devices allowing devices to access or wait for access for a new paging / access, and at the same time terminate or suspend the existing paging / access round. This allows devices to terminate the current occasion / round and prepare for re-accessing in a new occasion as per re-access policies.

[0032] For example, a reader provides broadcast or groupcast type signaling to failed or failing devices which are accessing an existing paging / access round, the signaling comprising indications allowing them to re-access the network in a new paging / access round associated with the same service / transaction ID and terminate the devices’ access from the current paging / access round.

[0033] There is provided a method in an A-IoT device / wireless device. The method comprises: receiving a paging message, from a network node, the paging message triggering an access procedure with the network node; initiating the access procedure with the network node; receiving a message from the network node, the message comprising an indication to terminate an ongoing access procedure with the network node; and terminating the access procedure with the network node, wherein terminating the access procedure is considered as a failed procedure. A wireless device is also provided for implementing this method.

[0034] There is provided a method in a network node. The method comprises: sending a paging message, to the wireless device, the paging message triggering an access procedure withPl 12880 W02the wireless device; performing the access procedure with the wireless device; sending a message to the wireless device, the message comprising an indication to terminate an ongoing access procedure with the wireless device; and terminating the access procedure with the wireless device, wherein terminating the access procedure is considered as a failed procedure. A network node for implementing this method is also provided.

[0035] There is provided a computer-readable medium comprising instructions which, when executed by at least one processor, cause the at least one processor to carry out the above methods.

[0036] Certain embodiments may provide one or more of the following technical advantage(s):

[0037] - Faster and efficient re-access: the network has the possibility to allow re-access to the network node even when the existing paging / access round is utilized.

[0038] This saves resources as the network does not engage persistently in failing devices, by offloading the devices in a new access round, for example.

[0039] This saves energy as the devices which are failing will be terminated from the current round and will have opportunity in a new access round which could be in a different frequency domain or later in a time domain which may subdue the impact of time or frequency dependent losses or fades.BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Exemplary embodiments will be described in more detail with reference to the following figures, in which:

[0041] Fig. 1 illustrates an example of Topology 1 in TR 38.848 V 1.0.0.

[0042] Fig. 2 illustrates an example of Topology 2 in TR 38.848 V 1.0.0.

[0043] Fig. 3 illustrates an example of Topology 3 with downlink assistance in TR 38.848 V 1.0.0.

[0044] Fig. 4 illustrates an example of Topology 3 with uplink assistance in TR 38.848 V 1.0.0.

[0045] Fig. 5 illustrates an example of Topology 4 in TR 38.848 V 1.0.0.

[0046] Fig. 6 illustrates an example of a CBRA with 4-step RA type.

[0047] Fig. 7 illustrates an example of a CBRA with 2-step RA type.

[0048] Fig. 8 illustrates an example of a signal diagram for an access procedure and reaccess procedure, according to an embodiment.

[0049] Fig. 9 illustrates a method in a wireless device, according to an embodiment.

[0050] Fig. 10 illustrates a method in a network node, according to an embodiment.Pl 12880 W02

[0051] Fig. 11 shows an example of a communication system, according to an embodiment.

[0052] Fig. 12 shows another example of a communication system, according to an embodiment.

[0053] Fig. 13 shows a schematic diagram of a UE / wireless device, according to an embodiment.

[0054] Fig. 14 shows a schematic diagram of a network node, according to an embodiment.

[0055] Fig. 15 illustrates a block diagram illustrating a virtualization environment.DETAILED DESCRIPTION

[0056] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0057] Terminology and disclaimer

[0058] In the embodiments below, use cases with ultra-low power devices, zero-energy or A-IoT devices are considered or assumed.

[0059] The term RAN node is used which can be a network node or a user equipment (UE). Examples of network nodes are NodeB (NB), BS, multi-standard radio (MSR) radio node such as MSR BS, eNB, gNB, MeNB, SeNB, location measurement unit (LMU), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, IAB, repeater, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, transmission reception point (TRP), RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MCS, MME etc.), O&M, OSS, SON, positioning node (e.g. E-SMLC), etc. In particular, in A-IoT scenario the RAN nodes comprise intermediate node / UE (e.g., relay UE, IAB, repeater etc.) and assisting node / UE (e.g., relay UE, IAB, repeater etc.).

[0060] In particular, in A-IoT scenario, the RAN nodes comprise intermediate node / UE (e.g., relay UE, IAB, repeater etc.) and assisting node / UE (e.g., relay UE, IAB, repeater etc.).

[0061] In this disclosure, the terms ‘polling’, ‘poll’ and ‘paging’, ‘page’, ‘inventory’, ‘query’, ‘interrogate’ are used to represent one or more signals transmitted by a network node broadcast wise or specially to a dedicated UE. The purpose of the signal is to facilitate / serve / manage / command one or more UEs to synchronize with the network nodePl 12880 W02(DL / UL synchronize with a reference time / frame / symbol or synchronize with one or more signals which the UE receives from the network node, or synchronize based on a pre-defined rule), receive DL data, response and transmit UL data correctly in intended resources. The content of such signal may be a particular reference signal or a signal carrying control information and / or data. Such a signal may be transmitted periodically or aperiodically configured by the network node.

[0062] In this disclosure, the terms ‘ A-IoT UE’, ‘ A-IoT device’, ‘device’, or ‘UE’ are used interchangeably without losing the meaning.

[0063] In this disclosure, the terms ‘intermediate node’, ‘intermediate UE’, ‘UE’ are applied interchangeably without losing the meaning.

[0064] The term “re-access” and “re-access procedure” are used interchangeably in this disclosure.

[0065] During a contention-based access procedure / round, an access occasion for a device starts from the time when the device receives a first DL (or reader to device (R2D)) signaling indicating the start of the access occasion until the time when the device receives a second DL (or R2D) signaling indicating the end of the access occasion or the start of the next access occasion.

[0066] The device performs a re-access procedure in case of contention resolution failure. The device performs re-access or retransmission in case of data transmission failure. Re-access means that the device accesses and transmits in a different access occasion from the access occasion where the device has experienced failures. Retransmission means that the device uses the same or different resources to retransmit the data on the same access occasion in the time domain.

[0067] It should be noted that the inventory procedure can be considered as a broad term which can include the access procedures (at RAN side) and non-access procedures (at CN / AF side). Thus, from the RAN behavior, the inventory procedure and the access procedure can be used interchangeably.

[0068] In one exemplary embodiment as illustrated in Fig. 8, if a device is accessing an access round for inventory reporting (step 115) triggered by a paging message with a given transact on / service ID (step 110), the device will continue to monitor the paging / DL / R2D messages (e g., referred to as ROUND MODIFICATION or MODIFICATION signaling / message in the examples below) associated with the same transaction or service ID during the ongoing access round for the purpose of re-accessing from one or more devices (step 120).Pl 12880 W02

[0069] The MODIFICATION message (or DL signaling / paging / any other DL terminology) message may indicate, e.g.:

[0070] - Terminate a device to access in the current access round or current paging round; and / or

[0071] - Offload or allocate the device or group of devices to new occasions (the devices must go through contention again) of a new / later access round; and / or

[0072] - Modify the allocation (of resources) associated with the current access / paging round.

[0073] More specifically, in an example, during an ongoing inventory (paging per access round), which is triggered by a paging message (step 110) or an access trigger message (e.g., may be referred to as a MsgO), the device implements one of the following behaviors:

[0074] - It does not decode the paging / access trigger / MsgO message (the device could know whether it is a paging / access trigger / MsgO message or other R2D message from the preamble preceding the message).

[0075] - It does not execute the service request included in paging / access trigger / MsgO if there is an ongoing round (meaning the round is not completed or terminated) unless the MODIFICATION message indicates the ongoing round is terminated and re-access is not barriered (for the device).

[0076] - It monitors the MODIFICATION (DL / paging message in alternative terminology) signaling / message which can provide / signal information related to one or more of: termination of the occasion / inventory round, and additional re-access information for accessing new occasions in the same / new round.

[0077] For example, the signaling / message can be L1 / L2 based. If a termination is indicated for the round in the message, then there can be two options:

[0078] - Termination of the ongoing inventory round;

[0079] - Termination of the ongoing inventory round with an implicit or explicit re-access instruction. This can be specified with or without a back-off time.

[0080] Some examples of the additional re-access information may comprise the following indications, if the re-access is limited to the same round:

[0081] - Changes in the ongoing inventory round,

[0082] - Adjustment of resources and access occasion in the ongoing inventory round;

[0083] - Changes in the feedback behavior (for example indication for switching from enabled to disabled (or vice-versa) Msg2 transmissions or switching between implicit or explicit ACK / NACK or vice-versa);Pl 12880 W02

[0084] - Increase or decrease in occasions of the ongoing inventory round;

[0085] - Barring of devices with certain RN16s or Collision resolution IDs to re-access in the new round associated with the same service request / transaction ID.

[0086] In the above, combinations of example indications are possible.

[0087] In one example, the MODIFICATION message / command is designed with various / multiple formats. This could be similar to the multiple formats of Downlink Control Information (DCI). Each format may be associated with some particular information. For example, the different formats can indicate:

[0088] - Format 1: Increase the existing inventory round size from N occasions to N + X occasion; this format needs a bit field to indicate X.

[0089] - Format 2 or extension of Format 1: Decrease the existing inventory round size from N occasions to N - X occasions; this format needs a bit field to indicate X. If built on Format 1, a 1 bit bitfield is needed to indicate addition or subtraction of X occasions from the existing size.

[0090] - Format 2 or extension of Format 1 or 2: The format explicitly carries the access occasion number or resources.

[0091] - Format 3: Terminate the current inventory round.

[0092] - Format 4: Terminate the current inventory round and re-initiate the inventory round again.

[0093] In one example, regarding format 4, a procedure that describes how re-paging of re-initiating of the inventory works is explained as follows, with reference to Fig. 8:

[0094] - A reader sends a MODIFICATION Format 4 command / message to devices which are participating in the ongoing round (step 120);

[0095] - All devices will monitor and decode the command irrespective of if the device has transmitted or not in the previous occasions in the same ongoing inventory round;

[0096] - After termination of the current round (step 125), the reader sends paging / access message / trigger of the new round corresponding to the same service / transaction request associated with the terminated round (step 130);

[0097] - All the devices associated with the previous terminated round will perform the access again in the new inventory round (step 135); when the new inventory is initiated, the reader can use the introduced changes / updated parameters via the MODIFICATION message, either through the format previously sent for termination or in a (re) Paging message corresponding to the new inventory round. For example, the changes can be changes inPl 12880 W02Modulation and Coding Scheme (MCS), changes in the feedback behavior (enabling / disabling Msg4 or Msg2), changes in FDRA or frequency allocation changes to the new access occasion.

[0098] - The reader could bar specific devices to access the new round (e.g., the devices that have already successfully transmitted (decoded by the reader) in the previous terminated round). The indication of barred devices can be sent in the MODIFICATION message of step 120 (previously sent for termination) or in the (re) Paging message of step 130.

[0099] In one option, the reader can indicate barred device IDs. The IDs can be core network (CN) allocated or in control or used by the CN. The IDs may or may not be encrypted.

[0100] In case the gNB cannot decode or has no knowledge of an ID associated with a device (due to protection), then the gNB can indicate barred device IDs based on the RN16 IDs that the devices use if the devices have been successfully transmitted in the terminated inventory round (e.g. step 115) through Msgl transmission, for example.

[0101] To ensure this behavior, the devices need to store the RN16 ID used in the inventory round for which a termination has been indicated for use in a subsequent inventory round. The RN16 can be considered as a local ID or as an AS ID or handle, which may have a temporary validity. For instance, if an inventory round is terminated before completion, this can be considered equivalent to an inventory round failure. As such, the devices must store the used RN16, because the reader may use this information to target devices in case a CN ID cannot be used.

[0102] In one example, when the current access round is completed / terminated (step 125), the device starts a timer (denoted suspension timer) and does not decode the paging / access trigger / MsgO (received in step 130) or execute the service request included in the paging / access trigger / MsgO if the suspension timer is still running. Alternatively, the device only respects the information obtained from the last received MODIFICATION (or non-round modification command, e.g., paging command) command if the suspension timer is still running, i.e., when the timer expires, the device will decode the paging / access trigger / MsgO and execute the included service request even if the information obtained from the last received MODIFICATION (or non-round modification command, e.g., paging command) command indicates this is not allowed / needed. In one variant, when the timer expires, the device releases the stored information obtained from the last received MODIFICATION (or non-round modification command, e.g., paging command) command and decodes (or always decodes) the paging / access trigger / MsgO and executes the included service request.

[0103] In one example, the MODIFICATION command itself may be transmitted in the paging / access trigger / MsgO, the paging / access trigger / MsgO may indicate (e.g., in the MACPl 12880 W02layer or using a different preamble) whether there is a MODIFICATION command included. In this case, the device performs the following:

[0104] The device decodes the paging / access trigger / MsgO if any of the following conditions are met:

[0105] - the device has no valid stored MODIFICATION information;

[0106] - the stored MODIFICATION information indicates that the decoding is allowed / needed;

[0107] - the paging / access trigger / MsgO to be decoded indicates it includes a MODIFICATION command.

[0108] In case the device decodes the paging / access trigger / MsgO (if any of the above conditions are met), if the paging / access trigger / MsgO does not include the MODIFICATION command, then the device executes the included service request. Otherwise, it behaves / performs the actions according to the information / indication included in the MODIFICATION command.

[0109] In one other example, the device considers that no (further) retransmissions are needed if the device has received a message indicating that the current access occasion (in time) has ended, and / or a new access occasion has started. Even though the device may be required to monitor on a continuous basis, it considers it unsuccessful for that access occasion and releases the random ID it has randomly selected to transmit Msgl in that access occasion.

[0110] Furthermore, the device can receive a DL (or R2D) signaling indicating one or more of the following:

[0111] 1) the device shall stop further retransmissions on the current access occasion;

[0112] 2) the initial transmission and its retransmissions initiated by the device on the current access occasion have failed;

[0113] 3) the device can perform re-access to handle the transmission failure. The device may be provisioned on how to proceed with the re-access in that case, e.g., a Q number, a dedicated paging / DL message round for devices which perform the re-access, etc.

[0114] Now turning to Fig. 9, an example of a flow chart of a method 200, in a wireless device or an A-IoT device such as 1300 or 1112, for accessing or re-accessing a network, will be described. Method 200 comprises:

[0115] Step 210: receiving a paging message, from a network node, the paging message triggering an access procedure with the network node;

[0116] Step 220: initiating the access procedure with the network node;Pl 12880 W02

[0117] Step 230: receiving a message from the network node, the message comprising an indication to terminate an ongoing access procedure with the network node; and

[0118] Step 240: terminating the access procedure with the network node, wherein terminating the access procedure is considered as a failed procedure.

[0119] In some examples, the paging message further comprises a transaction ID. In some examples, the wireless device monitors for the message while still performing the access procedure. In some examples, the message further comprises an indication of a re-access procedure. In some examples, the message further comprises information related to the reaccess procedure. In some examples, the information related to the re-access procedure comprises one or more of changes in an ongoing inventory round, adjustment of resources, access occasion in an ongoing access procedure and changes in a feedback behavior and barring of devices with certain IDs. In some examples, the indication of a re-access procedure comprises information for accessing one or more new occasions in a new round. In some examples, the access procedure comprises retransmissions. In some examples, the wireless device performs a re-access procedure using the same transition ID. In some examples, the wireless device stores an Access Stratum (AS) identity (ID) of the device. In some examples, the message has different formats. In some examples, the wireless device starts a timer after terminating the access procedure.

[0120] Fig. 10 illustrates an example of a flow chart for a method 300, in a network node, such as 1110 or 1400, for indicating a re-access procedure to a wireless device (e.g. A-IoT device). Method 300 comprises:

[0121] Step 310: sending a paging message, to the wireless device, the paging message triggering an access procedure with the wireless device;

[0122] Step 320: performing the access procedure with the wireless device;

[0123] Step 330: sending a message to the wireless device, the message comprising an indication to terminate an ongoing access procedure with the wireless device; and

[0124] Ste 340: terminating the access procedure with the wireless device, wherein terminating the access procedure is considered as a failed procedure.

[0125] In some examples, the network node stops monitoring the A-IoT device for ongoing transmissions. In some examples, the paging message further comprises a transaction ID. In some examples, the message comprises an indication of a re-access procedure. In some examples, the message further comprises information related to the re-access procedure. In some examples, the information related to the re-access procedure comprises one of more of changes in the ongoing inventory round, adjustment of resources, access occasion in anPl 12880 W02ongoing access procedure and changes in a feedback behavior and barring of devices with certain IDs. In some examples, the indication of a re-access procedure comprises information for accessing one or more new occasions in a new round. In some examples the access procedure comprises retransmissions.

[0126] In some examples, the network node performs a re-access procedure using the same transition ID. In some examples the message has different formats.

[0127] Fig. 11 shows an example of a communication system 1100 in accordance with some embodiments.

[0128] In the example, the communication system 1100 includes a telecommunications network 1102 that includes an access network 1104, such as a radio access network (RAN), and a core network 1106, which includes one or more core network nodes 1108. The access network 1104 includes one or more access network nodes or base stations of various types, access network nodes 1110A and 1110B are depicted (which may be collectively referred to as network nodes 1110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 1104 may include more than one access network technology. The network nodes 1110 of access network 1104 facilitate direct or indirect connection of wireless devices, also referred to as UEs, such as by connecting UEs 1112A, 1112B, 1112C, and 1112D (one or more of which may be generally referred to as UEs 1112) to the core network 1106 over one or more wireless connections.

[0129] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 1102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 1102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 1102, including one or more access network nodes 1110 and / or core network nodes 1108.

[0130] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time controlPl 12880 W02application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.

[0131] The network nodes 1110 facilitate direct or indirect connection of one or more UEs 1112 to the core network 1106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0132] The UEs 1112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1110 and other communication devices. Similarly, the network nodes 1108, 1110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 1102) with the UEs 1112 and / or with other network nodes or equipment in the telecommunications network 1102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 1102. More specifically, UEs 1112 may send messages, data, and / or other signals to network nodes 1108, 1110 or other elements of the telecommunications network 1102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple interveningPl 12880 W02devices) that then transmit the signal to the relevant device. Similarly, network nodes 1108, 1110 may send messages, data, and other signals to UEs 11122, other network nodes 1108, 1110, and other devices in telecommunications network 1102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 1112 by transmitting the message to an access network node 1110 that will then transmit the message to the intended UE 1112. Similarly, a core network node 108 may receive a particular message from aUE 1112 by receiving the message from an access network node 1110 that itself received the message from the UE 1112.

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

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

[0135] As a whole, the communication system 1100 of Fig. 11 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 1100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 1100 supporting different standards, protocols, or rule sets.

[0136] As one example, in certain embodiments, access network 1104 may contain some access network nodes 1110 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 1110 support (or the same access network nodes 1110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 1102 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0137] Telecommunications network 1102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 1102. For example, the telecommunications network 1102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0138] In some examples, one or more of the UEs 1112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1104.Pl 12880 W02Additionally, a UE may be configured for operating in single- or multi-RAT or multi -standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) NR - Dual Connectivity (EN-DC).

[0139] In the example, the hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE 1112C and / or 1112D) and network nodes (e.g., network node 1110B). In some examples, the hub 1114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1114 may be a broadband router enabling access to the core network 1106 for the UEs. As another example, the hub 1114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1110, or by executable code, script, process, or other instructions in the hub 1114.

[0140] As another example, the hub 1114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0141] The hub 1114 may have a constant / persi stent or intermittent connection to the network node 1110B. The hub 1114 may also allow for a different communication scheme and / or schedule between the hub 1114 and UEs (e.g., UE 1112C and / or 1112D), and between the hub 1114 and the core network 1106. In other examples, the hub 1114 is connected to the core network 1106 and / or one or more UEs via a wired connection. Moreover, the hub 1114 may be configured to connect to an M2M service provider over the access network 1104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1110 while still connected via the hub 1114 via a wired or wireless connection. In some embodiments, the hub 1114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1110B. In other embodiments, the hub 1114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and networkPl 12880 W02node 1110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0142] Fig. 12 is another example of a communication system 1200 according to some embodiments. As used herein, the communication system 1200 includes multiple access points (APs) 1210 (with four exemplary APs 1210A, 1210B, 1210C, and 1210D being depicted) and multiple wireless devices, referred to in the context of communication system 1200 as stations (STAs) 1212 (referred to individually as STA 1212A, STA 1212B, STA 1212C, STA 1212D, and STA 1212E). STA 1212Ais served by AP 1210Ain a first basic service set(BSS) 1220A. STA 1210B and STA 1210C are served by AP 1210B in a second BSS, BSS 1220B. STA 1212D is served by AP 1210C in a third BSS, BSS 1220C. STA 1212E is served by AP 1210D in a fourth BSS, BSS 1220D. Stations 1212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 1212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0143] Each of STAs 1212 may connect through a radio link to one of APs 1210. For example, depending on location or channel conditions experienced by a given STA 1212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0144] Each AP 1210 may provide data connectivity to STAs 1212 connected to a particular AP 1210. As illustrated, APs 1210 may be connected to a data network 1230. In this way, APs 1210 may also provide data connectivity between STAs 1212 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 1212 and its serving AP 1210 may be used for providing various kinds of services to STA 1212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 1212 and / or on a device linked to STA 1212. By way of example, Fig. 12 illustrates an application service platform 1232 provided in data network 1230. The application(s) executed on STA 1212 and / or on one or more other devices linked to STA 1212 may use the radio link for data communication with one or more other STA 1212 and / or thePl 12880 W02application service platform 1232, thereby enabling utilization of the corresponding service(s) at STA 1212.

[0145] Fig. 13 shows a wireless device 1300, which may be configured to operate in communication system 1100 of Figure 11 or in communication system 1200 of Fig. 120. The wireless device 1300 may be alternatively referred to as a UE 1300, like a UE 1112 within the context of communication system 1100, or as a station (STA) 1300 or as a non-access-point station (non-AP STA) 1300, like a STA 1212 within the context of the communication system 1200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptopmounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3GPP, including a narrow band NB-IoT UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE, or an A-IoT device.

[0146] A wireless device 1300 may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X).

[0147] In particular embodiments, wireless device 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input / output interface 1306, a power source 1308, a memory 1310, a communication interface 1312, and / or any other component, or any combination thereof. Certain embodiments of wireless device 1300 may include all or a subset of the components shown in Figure 13. The level of integration between the components may vary from one embodiment of wireless device 1300 to another. In general, in a particular embodiment of wireless device 1300, processing circuitry 1302, input / output interface 1306, power source 1308, memory 1310, and communication interface 1312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 1300. Further, certain embodiments of wireless devices 1300 mayPl 12880 W02contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0148] The processing circuitry 1302 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1310. The processing circuitry 1302 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1302 may include multiple central processing units (CPUs). The processing circuitry 1302 may be configured to perform any steps of method 200 of Fig.9. It should be noted that an A-IoT device has simpler hardware than the hardware as described for the UE.

[0149] In the example, the input / output interface 1306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 1300. Examples of an input device include a touch-sensitive or presencesensitive display, a camera, a microphone, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0150] In some embodiments, the power source 1308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 1308 may further include power circuitry for delivering power from the power source 1308 itself, and / or an external power source, to the various parts of wireless device 1300 via input circuitry or an interface such as an electrical power cable. Power source 1308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 1300 to which power is supplied.Pl 12880 W02

[0151] The memory 1310 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM) and other kinds of ROMs, magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1310 includes one or more programs 1314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1316. The memory 1310 may store, for use by wireless device 1300, any of a variety of various operating systems or combinations of operating systems.

[0152] The memory 1310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1310 may allow wireless device 1300 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1310, which may be or comprise a device-readable storage medium.

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

[0154] In the illustrated embodiment, communication functions of the communication interface 1312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Hypertext Transfer Protocol (HTTP), and so forth.

[0155] In particular embodiments, wireless device 1300 may provide an output of data captured via a sensor, through its communication interface 1312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 1300 can be communicated through a wireless connection to a network node via another wireless device 1300.

[0156] Wireless device 1300, when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot, etc. In particular embodiments, wireless device 1300 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 1300 shown in Fig. 13.

[0157] As yet another specific example, in an loT scenario, wireless device 1300 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 1300 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 1300 may implement the 3 GPP NB-IoT standard. In other scenarios, wireless device 1300 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.Pl 12880 W02

[0158] In practice, any number of wireless devices 1300 may be used together with respect to a single use case. For example, a first wireless device 1300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 1300 that is a remote controller operating the drone.

[0159] Fig. 14 shows a network node 1400 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 1400 may be configured to operate in communication system 1100 of Figure 11, like network nodes 1108 or 1110, or in communication system 1200 of Figure 12, like an AP 1210 or a station 1212. 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)), 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, 0-DU, O-CU).

[0160] Network nodes 1400 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 1400 may be a relay node or a relay donor node controlling a relay. Network nodes 1400 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0161] Other examples of network nodes 1400 include multiple transmission point (multi-TRP) 5G access nodes, multi -standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0162] In particular embodiments, network node 1400 includes a processing circuitry 1402, a memory 1404, a communication interface 1406, and a power source 1408. In general, in a particular embodiment of network node 1400, processing circuitry 1402, memory 1404,Pl 12880 W02communication interface 1406, and power source 1408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1400.

[0163] The network node 1400 may be composed of multiple distinct network entities (e.g., a NodeB (NB) entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 1400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1404 or portions of memory 1404 for different RATs) and some components may be reused (e.g., a same antenna 1410 may be shared by different RATs). The network node 1400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1400.

[0164] The processing circuitry 1402 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 1404, to provide network node 1400 functionality.

[0165] In some embodiments, the processing circuitry 1402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1402 includes one or more of radio frequency (RF) transceiver circuitry 1412 and baseband processing circuitry 1414. In some embodiments, the RF transceiver circuitry 1412 and the baseband processing circuitry 1414 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1412 and baseband processing circuitry 1414 may be on the same chip or set of chips, boards, or units.Pl 12880 W02Furthermore, the processing circuitry 1402 can be configured to perform any steps of the method 300 of Fig. 10.

[0166] The memory 1404 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1402. The memory 1404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1402 and utilized by the network node 1400. The memory 1404 may be used to store any calculations made by the processing circuitry 1402 and / or any data received via the communication interface 1406. In some embodiments, the processing circuitry 1402 and memory 1404 is integrated.

[0167] The communication interface 1406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 1406 comprises port(s) / terminal(s) 1416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 1300 may be capable of wireless communication and communication interface 1406 may also include radio front-end circuitry 1418 that may be coupled to, or in certain embodiments a part of, an antenna 1410. Particular embodiments of radio front-end circuitry 1418 include filter(s) 1420 and amplifier(s) 1422. The radio front-end circuitry 1418 may be connected to an antenna 1410 and processing circuitry 1402. The radio front-end circuitry may be configured to condition signals communicated between antenna 1410 and processing circuitry 1402. The radio front-end circuitry 1418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio frontend circuitry 1418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 1420 and / or amplifiers 1422. The radio signal(s) may then be transmitted via the antenna 1410. Similarly, when receiving data, the antenna 1410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1418. The digital data may be passed to the processing circuitry 1402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.Pl 12880 W02

[0168] In certain alternative embodiments, network node 1400 may be capable of wireless communication but does not include separate radio front-end circuitry 1418, instead, the processing circuitry 1402 includes radio front-end circuitry and is connected to the antenna 1410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1412 is part of the communication interface 1406. In still other embodiments, the communication interface 1406 includes one or more ports or terminals 1416, the radio front-end circuitry 1418, and the RF transceiver circuitry 1412, as part of a radio unit (not shown), and the communication interface 1406 communicates with the baseband processing circuitry 1414, which is part of a digital unit (not shown).

[0169] The antenna 1410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1410 may be coupled to the radio frontend circuitry 1418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1410 is separate from the network node 1400 and connectable to the network node 1400 through one or more interfaces or ports.

[0170] The antenna 1410, communication interface 1406, and / or the processing circuitry 1402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 1400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1410, the communication interface 1406, and / or the processing circuitry 1402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

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

[0172] Embodiments of the network node 1400 may include additional components beyond those shown in Fig. 14 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1400 may include user interface equipment to allow input of information into the network node 1400 and to allow output of information from the network node 1400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1400.

[0173] Fig. 15 is a block diagram illustrating a virtualization environment 1500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

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

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

[0176] The VMs 1508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 1506. Different embodiments of the instance of a virtual appliance 1502 may be implemented on one or more of VMs 1508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0177] In the context of NFV, each of the VMs 1508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine. Each of the VMs 1508, and that part of hardware 1504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 1508 on top of the hardware 1504 and corresponds to an application 1502.

[0178] Hardware 1504 may be implemented in a standalone network node with generic or specific components. Hardware 1504 may implement some functions via virtualization. Alternatively, hardware 1504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1510, which, among others, oversees lifecycle management of applications 1502. In some embodiments, hardware 1504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1512 which may alternatively be used for communication between hardware nodes and radio units.

[0179] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understoodPl 12880 W02that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0180] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0181] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.

Claims

Pl 12880 W02CLAIMS1. A method (200) performed by a wireless device (1112, 1300), the method comprising:- receiving (210) a paging message, from a network node, the paging message triggering an access procedure with the network node;- initiating (220) the access procedure with the network node;- receiving (230) a message from the network node, the message comprising an indication to terminate an ongoing access procedure with the network node; and- terminating (240) the access procedure with the network node, wherein terminating the access procedure is considered as a failed procedure.

2. The method of claim 1, wherein the paging message further comprises a transaction ID.

3. The method of any one of claims 1 to 2, further comprising monitoring for the message while still performing the access procedure.

4. The method of any one of claims 1 to 3, wherein the message further comprises an indication of a re-access procedure.

5. The method of claim 4, wherein the message further comprises information related to the re-access procedure.

6. The method of claim 5, wherein the information related to the re-access procedure comprises one or more of changes in an ongoing inventory round, adjustment of resources, access occasion in an ongoing access procedure and changes in a feedback behavior and barring of devices with certain IDs.

7. The method of any one of claims 4 to 6, wherein the indication of a re-access procedure comprises information for accessing one or more new occasions in a new round.

8. The method of any one of claims 1 to 7, wherein the access procedure comprises retransmissions.

9. The method of any one of claims 4 to 8, further comprising performing a re-access procedure using the same transition ID.

10. The method of any one of claims 1 to 9, further comprising storing an Access Stratum (AS) identity (ID) of the device.

11. The method of any one of claims 1 to 10, wherein the message has different formats.

12. The method of any one of claims 1 to 11, further comprising starting a timer after terminating the access procedure.

13. A method (300) performed by a network node (1110, 1400) in communication with a wireless device, the method comprising:- sending (310) a paging message, to the wireless device, the paging message triggeringPl 12880 W02an access procedure with the wireless device;- performing (320) the access procedure with the wireless device;- sending (330) a message to the wireless device, the message comprising an indication to terminate an ongoing access procedure with the wireless device; and- terminating (340) the access procedure with the wireless device, wherein terminating the access procedure is considered as a failed procedure.

14. The method of claim 13, further comprising stopping monitoring the wireless device for ongoing transmissions.

15. The method of claim 13 or 14, wherein the paging message further comprises a transaction ID.

16. The method of any one of claims 13 to 15, wherein the message comprises an indication of a re-access procedure.

17. The method of claim 16, wherein the message further comprises information related to the re-access procedure.

18. The method of claim 17, wherein the information related to the re-access procedure comprises one of more of changes in the ongoing inventory round, adjustment of resources, access occasion in an ongoing access procedure and changes in a feedback behavior and barring of devices with certain IDs.

19. The method of any one of claims 17 to 18, wherein the indication of a re-access procedure comprises information for accessing one or more new occasions in a new round.

20. The method of any one of claims 13 to 19, wherein the access procedure comprises retransmissions.

21. The method of any one of claims 15 to 20, further comprising performing a re-access procedure using the same transition ID.

22. The method of any one of claims 13 to 19, wherein the message has different formats.

23. A wireless device (1112, 1300) comprising a network interface (1312) and processing circuitry (1302) connected thereto, the processing circuitry (1302) configured to perform the method of any one of claims 1 to 12.

24. A network node (1110, 1400), the network node comprising a network interface (1406) and processing circuitry (1402) connected thereto, the processing circuitry (1402) configured to perform the method of any one of claims 13 to 22.

Images