Sending a message, and determining whether a message has a plurality of message segments

Abstract

A method performed by a first wireless communication device is disclosed The method is for determining whether a message comprises a plurality of message segments. The method comprises receiving a first message from the second wireless communication device, and if the first message includes an indication, determining, based on the indication in the first message, whether a second message from the second wireless communication device comprises a plurality of message segments.

Description

[0001] SENDING A MESSAGE, AND DETERMINING WHETHER

[0002] A MESSAGE HAS A PLURALITY OF MESSAGE SEGMENTS Technical Field

[0003] Examples of this disclosure relate to sending a message, and determining whether a message has a plurality of message segments. The message may be sent by an ambientinternet of things (A-loT) device to a reader, for example.

[0004] Background

[0005] Zero-Energy loT & Ambient-loT

[0006] 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.

[0007] These ZE-loT 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. 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, RF, etc.

[0008] (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.

[0009] Recently work on this new category of loT devices has started in 3GPP, then referred to as ‘Ambient-loT’. The study was started in SA1 working group in Rel-18. TR 22.840 and TS22.369 (by SA1) are specified to capture potential use cases, traffic scenarios, device constraints of Ambient loT (A-loT) and identify new potential service requirements as well as new KPIs. RAN plenary conducted a Rel-18 study on A-loT (RP-222685) for discussionsabout deployment scenarios, connectivity topologies, and RAN design targets. The Rel-18 RAN study was captured in TR38.848.

[0010] Rel-19 WG-level studies were carried out study and study outcomes are being captured in TR38.769 (by RAN1-4 WGs), TR23.700-13 (by SA2), and TR33.713 (by SA3).

[0011] Rel-19 Ambient-loT Wl phase

[0012] Solutions for Rel-19 A-loT are being specified during work item phase in multiple WGs.

[0013] Revised RAN WID for Rel-19 A-loT approved in RP-250796, with following objectives:

[0014] WGs begin their discussions from the decisions already made in TR 38.769, with the following refinements for the scope:

[0015] The following objectives are set, within the General Scope:

[0016] • RAN1 scope:

[0017] o PRDCH and PDRCH, which are the only physical channels in R2D and D2R, respectively.

[0018] o R2D and D2R signal(s)

[0019] o Multiplexing / multiple access in R2D is by only TDMA, and in D2R is by only TDMA and FDMA.

[0020] o R2D supports only OOK-4 modulation, one solution for CP handling. D2R backscattering supports only OOK and BPSK modulations.

[0021] o R2D transmission supports only the Manchester line code in TR 38.769 o D2R transmission supports:

[0022] ■ Either the Manchester line code in TR 38.769 or no line code (one to be down-selected); and

[0023] ■ A corresponding small frequency shift method according to the options in TR 38.769.

[0024] o R2D does not support FEC. D2R supports only convolutional code with generator polynomials as per TS 36.212. Applying or not applying the FEC to D2R is specified by ensuring it is under the reader control and applies to all devices targeted by the reader.

[0025] o PRDCH and PDRCH both support transmission without CRC, and with CRC as per the generator polynomials in TS 38.212 for 6-bit CRC and 16-bit CRC. Cases to use which length of CRC, or no CRC, to be decided in RAN1.o D2R supports physical layer repetition transmission. R2D does not support physical-layer repetition transmission.

[0026] • RAN2 scope:

[0027] o 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:

[0028] ■ A-loT 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.

[0029] Note: RAN2 aims to design a paging message format such that multiple identifiers can be contained in one paging message, for forward compatibility purposes.

[0030] ■ A-loT Random access, including re-access for failure handling. Contentionbased and contention-free cases are supported. For the contention-based random access, only Solution 1 (3-step only) is included.

[0031] ■ A-loT data transmission, including data (re-)transmission for failure handling. Segmentation is supported at least in D2R.

[0032] ■ Only MAC layer is included

[0033] • RAN3 scope:

[0034] o Specify necessary architectural aspects, and signaling and procedures between A-loT RAN and A-loT CN to support the A-loT functions, assuming an architecture of aggregated gNB, including:

[0035] ■ Inventory and command operations

[0036] ■ Device location reporting at reader ID granularity

[0037] Note: The above A-loT functions are supported over the existing NG interface, based on architecture(s) defined by RAN3 / SA2.

[0038] • RAN4 scope:

[0039] o Specify RF requirements for Ambient-loT BS, device 1 , and CW

[0040] ■ RF requirements for Type 1-C Ambient-loT BS

[0041] ■ RF requirements for device 1

[0042] ■ RF requirements for CW

[0043] o Specify RRM core requirements for device 1 , if necessary

[0044] o Study and develop OTA test methodology for A-loT device 1

[0045] ■ Consider test methods specified in TR 38.870 as starting point. Take test system reuse, test system complexity and test time into account, when developing test methods suitable for Ambient loT.■ Develop the preliminary Measurement Uncertainty (MU) assessment for the test system

[0046] o Use band n8 as an example band

[0047] Note 1 : Coordination with SA2 and SA3 is expected. Updates to the WID objectives should be considered if needed.

[0048] Note 2: This Wl shall target for an loT segment well below the existing 3GPP loT technologies, e.g. NB-loT, eMTC, RedCap, etc. The Wl shall not aim to replace existing 3GPP LPWA technologies.

[0049] SA3 WID for Rel-19 A-loT approved in SP-250359, with following objectives:

[0050] Specifically, the work item objectives are:

[0051] 1. Network Layer Authentication between AloT device and 5G core

[0052] a. AloTF is the endpoint in the 5G core

[0053] b. Credentials are securely stored in the ADM on the network side

[0054] NOTE 1 : The credentials are assumed to be stored in a secure environment in the ADM. How this is realized is left to implementation. The requirements will reflect this.

[0055] c. Secure storage and processing of credentials in the AloT device

[0056] NOTE 2: For SNPN deployment the storage of the credentials of non-AKA based methods is out of scope as described in TS 33.501 Annex I 2.2.

[0057] d. Security aspects of the storage of the credentials at the ADM

[0058] 2. Confidentiality, anti-replay and integrity protection of information during AloT service communication

[0059] 3. Privacy of AloT device identifiers using the AloT Temp ID as concluded in TR 33.713. 4. Security to protect the permanent disabling RF transmission capabilities of AloT device(s) as concluded in TR 33.713.

[0060] SA2 WID for Rel-19 A-loT approved in SP-250377, with following objectives:

[0061] Specifically, the work item objectives are:

[0062] • WT#1 Architecture to support Ambient loT:

[0063] o Architecture to Support Device 1 in Topology 1 (Direct interface option and Indirect interface option).

[0064] • WT#2 Ambient loT Device management:

[0065] o Identifier of Ambient loT Device (i.e. permanent device ID, temporary device ID).o AloT Device Data Profile Management

[0066] • WT#3 Ambient loT Service enabler for Inventory and Command:

[0067] o Exposure for AIOT services to AF.

[0068] o Data transfer between AloT Device / RAN reader and AIOTF.

[0069] NOTE: Alignment with SA3 on security aspects is expected.

[0070] One segmentation for A-loT

[0071] RAN2 has discussed the support of segmentation for A-loT and agreed that the Rel-19 solution considers only segmentation of the uplink message (i.e., device to reader D2R direction), for example the D2R message carrying device ID (Msg3 in the contention based random access procedure) or the D2R message carrying the command response (Msg5). The list of agreements from RAN2-125bi to RAN2-129 meetings are as below.

[0072]

[0073]

[0074]

[0075]

[0076] In addition, it has been agreed from recent discussion in RAN1 that the A-loT reader provides the payload size (grant size) for the D2R message in the preceding R2D message. For example, Msg2 that schedules Msg3 (with device ID) indicates Msg3 size.

[0077] Agreement from RAN1-120

[0078] The payload size (i.e. TBS-like) for PDRCH transmission with variable size is explicitly indicated in the corresponding R2D control information.

[0079] There currently exist certain challenge(s). For example, as identified in RAN2 discussion, A- loT reader may or may not have information about the expected size of a device to reader (D2R) message in response to an ambient-internet of Things (A-loT) paging. In case such information is not available (e.g., not provided by core network, CN), there needs a mechanism to support the reader to determine radio resources to allocate for D2R messages in an efficient manner. This includes the allocation for the first D2R message with variable size (i.e., Msg3 in contention based random access procedure) and the subsequent D2R segments, if applicable. Note that the 1 -bit indication from A-loT device, as recently agreed in RAN2-129 meeting, might not be sufficient for the reader to know size of remaining uplink data (D2R segments).

[0080] Summary

[0081] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, examples of this disclosure provide solutions to enable an A-loT reader to efficiently allocate resources for D2R transmission with segmentation support. Examples may include one or more of the following features:• Indication from A-loT device inside the D2R message with variable size

[0082] o D2R message (D2R segment) contains information / indication about the size of remaining payload rather than the size of current segment (MAC PDU).

[0083] ■ This information can be in a form of MAC header field, for example, length field.

[0084] ■ This information allows the reader to decide resources for the next segment(s), if needed.

[0085] o Alternatively (to remaining payload size), D2R message (D2R segment) contains the information / indication about the size of whole payload.

[0086] ■ The reader can infer the remaining size based on the received segment(s) to determine the resource allocation for next segment. ■ Device does not need to compute the remaining size.

[0087] ■ Whole payload size may cover the size of NAS PDU and control information at MAC, e.g., MAC header fields.

[0088] ■ Alternatively, in case header elements and other information in the transmitted payload is either static or determinable, the payload size indication covers only the size or number of bits of the total upper layer data unit.

[0089] o Alternatively, the payload size indication refers to the total payload size to be transmitted whenever the payload is a segment, or otherwise indicates the included payload size in the currently transmitted data unit when the included payload is either a complete unsegmented data unit, or is the last segment of a segmented data unit.

[0090] ■ As in the above present as a length field or in combination with a header element or other control information

[0091] • Indication in association with Msg1

[0092] o In case the information about expected D2R message is not available at reader (not provided by CN), payload size for the first D2R can be determined based on an indication from / associated with transmission of Msg1 during the contention based random access procedure (i.e., L1 or L2 control information) ■ Msg1 contains an indication about the device identifier format. For instance, one-bit indication tells reader if long device ID format or not. In case devices indicates the longer device ID format, reader expects segmentation for Msg3 and thus allocates the grant size for first D2R segment (after Msg2) with maximum allowable size.

[0093] Implicit indication from the range of RN16 picked by the device. For instance, a value of RN16 in the range from 0 to 2A15means that ashort / normal size of Msg3 (short / normal device ID format), whereas RN16 value greater than 2A15means that segmentation is needed for Msg3.

[0094] ■ Reader indicates in A-loT paging if such indication in / associated with Msg1 is needed or not (availability of expected D2R size from CN). ■ Based on transmission in a specific (set of) TDMA / FDMA occasion(s) for Msg1

[0095] • Assistant information before A-loT paging

[0096] o In case the information about expected D2R message is not available at CN to provide to reader (e.g., not provided by AF), CN provides reader in advance possible sizes of device identifier, e.g., permanent device ID has either the size of X bits (default / typical format) or Y bits (long format). This helps reader determine default size of Msg3, e.g., based on the typical device ID format (for example, 96-bit EPC identifier requires a grant size of 144 bits). o CN provides to the reader also other NAS level control information in Msg3, for example, the security related information used for authentication steps.

[0097] The above mechanisms can be used independently or in combination.

[0098] Certain embodiments may provide one or more of the following technical advantage(s). For example, one or both of the following may apply for examples of this disclosure:

[0099] • Network / reader can allocate resources for D2R in an efficient manner, even without assistant information from CN about expected D2R message size.

[0100] • Segmentation support for D2R transmission can be achieved with simple design. A first example aspect of this disclosure provides there is provided a method performed by a first wireless communication device for determining whether a message comprises a plurality of message segments. The method comprises receiving a first message from the second wireless communication device, and if the first message includes an indication, determining, based on the indication in the first message, whether a second message from the second wireless communication device comprises a plurality of message segments.

[0101] Another example aspect of this disclosure provides a method performed by a second wireless communication device for sending an indication in a message. The method comprises sending, to a first wireless communication device, a first message. If the second communication device should include an indication in the first message to the first wirelesscommunication device that a second message from the second wireless communication device comprises a plurality of message segments, the first message includes the indication.

[0102] A further example aspect of this disclosure provides a method performed by a first wireless communication device for receiving a message. The method comprises receiving a first message from a second communication device. The first message includes an indication of one or more of:

[0103] - whether the first message is a segment of a second message;

[0104] - whether the first message is a last segment of the second message;

[0105] - whether a further message to be sent by the second communication device to the first communication device is a segment of the second message;

[0106] - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.

[0107] An additional example aspect of this disclosure provides a method performed by a second wireless communication device for sending a message. The method comprises sending a first message to a first communication device. The first message includes an indication of one or more of:

[0108] - whether the first message is a segment of a second message;

[0109] - whether the first message is a last segment of the second message;

[0110] - whether a further message to be sent by the second communication device to the first communication device is a segment of the second message;

[0111] - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.

[0112] A further example aspect of this disclosure provides a tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations in a first wireless communication device for determining whether a message comprises a plurality of message segments. The operations comprise receiving a first message from the second wireless communication device, and if the first message includes an indication, determining, based on the indication in the first message, whether a second message from the second wireless communication device comprises a plurality of message segments.An additional example aspect of this disclosure provides a tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations in a second wireless communication device for sending an indication in a message. The operations comprise sending, to a first wireless communication device, a first message. If the second communication device should include an indication in the first message to the first wireless communication device that a second message from the second wireless communication device comprises a plurality of message segments, the first message includes the indication.

[0113] Another example aspect of this disclosure provides a tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations in a first wireless communication device for receiving a message. The operations comprise receiving a first message from a second communication device. The first message includes an indication of one or more of:

[0114] - whether the first message is a segment of a second message;

[0115] - whether the first message is a last segment of the second message;

[0116] - whether a further message to be sent by the second communication device to the first communication device is a segment of the second message;

[0117] - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.

[0118] A further example aspect of this disclosure provides a tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations in a second wireless communication device for sending a message. The operations comprise sending a first message to a first communication device. The first message includes an indication of one or more of:

[0119] - whether the first message is a segment of a second message;

[0120] - whether the first message is a last segment of the second message;

[0121] - whether a further message to be sent by the second communication device to the first communication device is a segment of the second message;

[0122] - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.

[0123] A still further example aspect of this disclosure provides apparatus in a first wireless communication device for determining whether a message comprises a plurality of messagesegments, the apparatus comprising processing circuitry and a memory. The apparatus is configured to receive a first message from the second wireless communication device, and if the first message includes an indication, determine, based on the indication in the first message, whether a second message from the second wireless communication device comprises a plurality of message segments.

[0124] An additional example aspect of this disclosure provides apparatus in a second wireless communication device for sending an indication in a message, the apparatus comprising processing circuitry and a memory. The apparatus is configured to send, to a first wireless communication device, a first message. If the second communication device should include an indication in the first message to the first wireless communication device that a second message from the second wireless communication device comprises a plurality of message segments, the first message includes the indication.

[0125] Another example aspect of this disclosure provides apparatus in a first wireless communication device for receiving a message, the apparatus comprising processing circuitry and a memory. The apparatus is configured to receive a first message from a second communication device. The first message includes an indication of one or more of:

[0126] - whether the first message is a segment of a second message;

[0127] - whether the first message is a last segment of the second message;

[0128] - whether a further message to be sent by the second communication device to the first communication device is a segment of the second message;

[0129] - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.

[0130] Another example aspect of this disclosure provides apparatus in a second wireless communication device for sending a message, the apparatus comprising processing circuitry and a memory. The apparatus is configured to send a first message to a first communication device. The first message includes an indication of one or more of:

[0131] - whether the first message is a segment of a second message;

[0132] - whether the first message is a last segment of the second message;

[0133] - whether a further message to be sent by the second communication device to the first communication device is a segment of the second message;

[0134] - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.Brief Description of the Drawings

[0135] For a better understanding of the embodiments of the present disclosure, and to show how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which:

[0136] Figure 1 depicts a method in accordance with particular embodiments;

[0137] Figure 2 depicts a method in accordance with particular embodiments;

[0138] Figure 3 depicts a method in accordance with particular embodiments;

[0139] Figure 4 depicts a method in accordance with particular embodiments;

[0140] Figure 5 shows an example signaling flow according to examples of this disclosure; Figure 6 shows an example of a communication system in accordance with some embodiments;

[0141] Figure 7 shows an example of another communication system in accordance with some embodiments;

[0142] Figure 8 shows a wireless device in accordance with some embodiments;

[0143] Figure 9 shows a network node in accordance with some embodiments; and Figure 10 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

[0144] Detailed Description

[0145] 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.

[0146] Figure 1 depicts a method 100 in accordance with particular embodiments, for example a method performed by a first wireless communication device for determining whether a message comprises a plurality of message segments. The method 100 may be performed by a wireless device (e.g. UE QQ112, station QQ212 or wireless device QQ300 as described later with reference to Figures 6, 7 and 8 respectively) or a network node (e.g. network node QQ110, access point QQ210 or network node QQ400 as described later with reference to Figures 6, 7 and 9 respectively. In particular, the method 100 may be performed by a wireless communication device such as a reader device (e.g. A-loT reader). The method 100 begins at step 102, comprising receiving a first message from the second wireless communication device. Step 104 comprises, if the first message includes an indication, determining, based on the indication in the first message, whether a secondmessage from the second wireless communication device comprises a plurality of message segments.

[0147] Figure 2 depicts a method 200 in accordance with particular embodiments, such as for example a method performed by a second wireless communication device for sending an indication in a message. The method 200 may be performed by a wireless device (e.g. UE QQ112, station QQ212 or wireless device QQ300 as described later with reference to Figures 6, 7 and 8 respectively) ora network node (e.g. network node QQ110, access point QQ210 or network node QQ400 as described later with reference to Figures 6, 7 and 9 respectively. In particular, the method 200 may be performed by a wireless communication device such as an A-loT device.

[0148] The method 200 begins at step 202, comprising sending, to a first wireless communication device, a first message, wherein, if the second communication device should include an indication in the first message to the first wireless communication device that a second message from the second wireless communication device comprises a plurality of message segments, the first message includes the indication.

[0149] Figure 3 depicts a method 300 in accordance with particular embodiments, for example a method performed by a first wireless communication device for receiving a message. The method 300 may be performed by a wireless device (e.g. UE QQ112, station QQ212 or wireless device QQ300 as described later with reference to Figures 6, 7 and 8 respectively) or a network node (e.g. network node QQ110, access point QQ210 or network node QQ400 as described later with reference to Figures 6, 7 and 9 respectively. In particular, the method 300 may be performed by a wireless communication device such as a reader device (e.g. A-loT reader).

[0150] The method 300 begins at step 302, comprising receiving a first message from a second communication device. The first message includes an indication of one or more of:

[0151] - whether the first message is a segment of a second message;

[0152] - whether the first message is a last segment of the second message;

[0153] - whether a further message to be sent by the second communication device to the first communication device is a segment of the second message;

[0154] - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.Figure 4 depicts a method 400 in accordance with particular embodiments, such as for example a method performed by a second wireless communication device for sending a message. The method 400 may be performed by a wireless device (e.g. UE QQ112, station QQ212 or wireless device QQ300 as described later with reference to Figures 6, 7 and 8 respectively) or a network node (e.g. network node QQ110, access point QQ210 or network node QQ400 as described later with reference to Figures 6, 7 and 9 respectively. In particular, the method 400 may be performed by a wireless communication device such as an A-loT device.

[0155] The method 400 begins at step 402, comprising receiving a sending message to a first communication device. The first message includes an indication of one or more of:

[0156] - whether the first message is a segment of a second message;

[0157] - whether the first message is a last segment of the second message;

[0158] - whether a further message to be sent by the second communication device to the first communication device is a segment of the second message;

[0159] - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.

[0160] In examples of this disclosure, a first wireless communication device may be for example a reader, and a second wireless communication device may be for example a device such as an A-loT device.

[0161] Particular example embodiments will now be described for illustrative purposes.

[0162] Figure 5 shows an example signaling flow according to examples of this disclosure, for the inventory only procedure with device to reader (D2R) segmentation support covering the solutions presented in following embodiments. Note that the proposed mechanisms can be combined or employed separately. The same / similar solutions are also applicable to other procedures (e.g., inventory plus command).

[0163] In the main embodiment, for the A-loT network system with buffer-less operation, the A-loT device contains information / indication about the size of whole payload inside the D2R message (D2R segment) (steps 7, 10 in the figure).

[0164] • This can be realized by means of a length field in the MAC PDU header.

[0165] • In this case, the reader can infer the remaining size based on the value of the length field and the received segment(s) to determine the resource allocation for next segment(s).o i.e., the reader deduces the size of the remaining payload by using the size of whole payload minus the summarized sizes of the received segment(s). • Device does not need to compute the remaining size.

[0166] • The device may only need to provide such information once, e.g., Msg3 (where the device responds with an identifier) or Msg5 (where the device responds to a “read” or “write” command for the first time), which would then apply for the rest of the data transmission until the procedure is completed. Note that the length field may not necessarily be transmitted every time, i.e., a bit that precedes may indicate whether it will be present or absent.

[0167] o In an example, the bit with the value ‘1 ’ indicates presence of the length field, while the bit with the value ‘0’ indicates absence of the length field.

[0168] o In an example, the bit with the value ‘0’ indicates presence of the length field, while the bit with the value ‘1’ indicates absence of the length field.

[0169] In an alternative embodiment (alternative to remaining D2R payload size), A-loT device contains

[0170] • information / indication about the remaining payload size of the subsequent D2R segment(s), and / or

[0171] • length information, e.g., in header; this enables network to parse data from the MAC PDU according to the length field indicated in header inside the current D2R segment / message. This can be indirectly utilized in indicate the remaining payload.

[0172] • This can be realized by means of a length field in the MAC PDU for current D2R message. For example, 7-bit length field can be used to indicate number of bytes of remaining segment(s). Note that, instead of indicating the size related the current MAC PDU (e.g., NAS PDU element), the length indicates the size of the remaining payload, that may need zero, one or more D2R segments. In addition, the payload size covers not only the NAS PDU but also header information at MAC, i.e., MAC header fields.

[0173] o As a note, the header information at MAC for remaining segment(s) is estimated by the device in advance. The estimated size may be different from the actual size when the MAC PDUs of the remaining segments are built. The estimated size may depend on the estimated number segments / MAC PDUs to be built. The device can make such estimation given an assumption that the size of each upcoming grant for the remaining payload is the same or similar as the grant size of previous grants.• This information together with the size of the D2R message allocated by the reader in the preceding R2D message assists the reader to decide resources for the next segment(s) as well as parsing the received D2R(i.e., when the padding starts, if there is).

[0174] • The device needs to maintain the remaining payload size, e.g., in a register, local variable during the current access procedure.

[0175] • In case of no segmentation, value for this field is set to zero.

[0176] In another embodiment, the reader determines grant size (payload size) for the first D2R carrying A-loT NAS information (i.e., with variable size) based on an indication from / associated with transmission of Msg1 during the contention based random access procedure (i.e., L1 or L2 control information). See also steps 2, 3 in the figure.

[0177] • This is particularly beneficial in case the information about expected D2R message size in response to A-loT paging is not available, e.g., CN cannot get this from AF.

[0178] • As an example, in addition to RN16, Msg1 in contention based random access procedure contains an indication about the device identifier format. For instance, one-bit indication tells reader if long device ID format or short device ID format is used. In case the device indicates the longer device ID format, reader expects segmentation for Msg3 and thus may allocate a large grant size for first D2R segment, e.g., with maximum allowable size.

[0179] • As another example, the indication to the reader can be implicit from the range of RN16 value picked by the device. For instance, a value of RN16 in the range from 0 to 2A15means that a short / normal size of Msg3 (short / normal device ID format), whereas RN16 value greater than 2A15means that segmentation is needed for Msg3. The indication associated with Msg1 transmission can be optional and controlled by the reader. In a sub-embodiment, the reader indicates in the A-loT paging if device(s) need to provide the indication via Msg1 , e.g., via RN16 value range or explicit indication in Msg1. For example, such an indication is not needed if the reader is provided with the size of expected D2R message from CN.

[0180] In another alternative, paging contains a set of reserved TDMA occasions or FDMA occasions or both where the devices which intend to transmit a certain device ID type (long or short) in Msg3 can contend for. As an example, if the paging reserves X={1,2} TDMA time occasions and F={1,2,3,4} FDMA occasions, there can be a pre-defined rule or a configuration in paging that mandates that devices which intend to transmit short device IDsto choose one of the resource configurations from within X=1, F={1,2,3,4}; and the devices which intend to transmit longer ID to choose from within X=2,F={1 ,2,3,4} occasions for transmitting their Msgls. These combinations can be configured by the reader in one of the Messages prior to Msg1- for eg- paging, an explicit signalling or control information. The reader categorizes the devices based on where it transmitted its Msg1 in and allocates D2R resources for Msg3 accordingly.

[0181] In another embodiment, CN (AIOTF) provides the reader information related to possible sizes of D2R message in response to A-loT paging (including device identifier).

[0182] • This is particularly beneficial in case the information about expected D2R message size in response to A-loT paging is not available, e.g., CN cannot get this from AF.

[0183] • This information can be predefined or dynamically provided to the reader, e.g., as part of assistant information in the service request for inventory or inventory + command procedure (i.e., step 1 in the figure).

[0184] • The information can be about potential size of device ID to be reported in the Msg3.

[0185] o In one example, permanent device ID has either the size of X bits (default / typical format) or Y bits (long format). This helps reader determine default size of Msg3, e.g., based on the typical device ID format (for example, 96-bit EPC identifier requires a grant size of 144 bits).

[0186] o As another example, when the device ID information contains the permanent device ID with mask information which targets to a group of devices, the device may report only its truncated device ID (the bits which are not masked). In this case, based on the mask information in the device ID information (in the service request), the CN may determine the size if a short / long form of device ID is to be reported in Msg3.

[0187] o Yet in another example, the device ID information (in the service request) contains only a partial of the permanent device ID (call it partial ID) and its size, the device may report the remaining bits of the permanent device ID if its permanent device ID matches the partial ID. In this case, the CN may determine potential device ID to be reported in Msg3 to indicate to the RAN / reader.

[0188] • CN provides to the reader also other NAS level control information in Msg3, for example, the security related information used for authentication steps.

[0189] In another embodiment, the device provides the length field as part of the D2R message, only if the remaining data becomes less than the maximum possible transport block size. The benefit of such indication with respect to providing the size of the remaining data in anearly segment of the D2R message (ideally the first segment of the D2R message with the data) is that it would require lower number of bits to represent the length field, i.e., maximum possible size is equal to the maximum possible value of the transport block size.

[0190] In some examples, the header is configured to include following non-limiting features in any combinations:

[0191] • 1 -bit indication as agreed

[0192] o Aligns with existing agreement if length field is added

[0193] o Can be indicated in MAC subheader, MAC CE payload, MAC PDU payload o Purpose: We define two options indicating how 1 -bit indication can be utilized ■ Option A: Is it a last segment or not

[0194] ■ Option B: If there is more data or not; or if there is remaining payload which cannot be included in current D2R transmission

[0195] • Length field

[0196] o This can be indicated in MAC subheader.

[0197] • Payload indication for subsequent D2R messages or remaining payload

[0198] o Indicated in D2R MAC PDU payload or in MAC CE payload

[0199] In some examples, if a payload is divided into N segment transmissions, then on indicating length information related to data in PDU, we define following behaviors, e.g., during transmissions of:

[0200] • First N-1 segments, except the last segment, device can indicate following information in length field

[0201] o No length information (length field contains dummy bits)

[0202] ■ This is implicit behavior, if no value indicated in length field of header o Full length information

[0203] ■ This means, the length field indicates information pertinent to whole payload in PDU used for data

[0204] Above means (no length info or full length info), the whole PDU / resource is utilized for data

[0205] • N-th segment (last segment), device can indicate length (in length field in header) of PDU or sub-PDU which contains data and remaining padding bits.

[0206] In some examples, if a field indicating remaining payload is included (means some value is included), then the length field is not necessary to be indicated. The reason is that if a device has still remaining data or payload to be included in future segments, then the currentsegments (PDU) must be filled to max without any paddings. In other words, if device has no more remaining payload indicated in D2R message, then the length field must be indicated with value as there are chances that data in current PDU may not filled to max. In one option we can define an algorithm, where all 3 fields interact (1 -bit indication, remaining payload, and length field). In current D2R message containing header and its associated payload,

[0207] • the headerSH contains

[0208] o 1 -bit indication and

[0209] ■ The 1 -bit indication tells if there is remaining payload, and if it is, the size of remaining payload can be included as form of control information payload#P

[0210] o length field, and

[0211] ■ This indicates size of data in payload#P

[0212] • the payload#P contains

[0213] o data plus

[0214] o control information related remaining payload

[0215] ■ This is equivalent to MAC CE

[0216] ■ The reader does not need to send such control informato to CN

[0217] In some examples, the reader informs the device in a R2D transmission, e.g., Msg2 or Msg4, whether 1 bit indication is sufficient or more info about D2R MAC PDU / payload size is needed, where the D2R transmission is triggered by the R2D transmission. The reader may indicate 1 bit indication is sufficient in a D2R transmission in case CN provides an estimated expected D2R message size (where the D2R message is included in the D2R transmission triggered by the R2D transmission). The device only sends 1 bit indication in the triggered D2R transmission if it is informed 1 bit indication is sufficient, otherwise it may (also) indicates D2R MAC PDU / payload size.

[0218] In some examples, if the 1-bit indication indicates:

[0219] • There is no remaining payload, then length field is utilized to indicate size of data in payload (as part of payload including padding)

[0220] o Given there is no more remaining data, so current D2R transmission PDU may not contain data to max in PDU container.

[0221] • There is remaining payload, then length field is utilized to indicate remaining payload o The whole payload is used for data without paddingPerforming segmentation implies the MAC PDU cannot accommodate all the data / signalling to be transmitted. In some examples, in case segmentation is applied to D2R transmission, the device performs the following:

[0222] • In case the current MAC PDU cannot accommodate all the (remained) higher layer data (after encryption if needed), the device first reserves space for MAC CE(s) (if any) in the MAC PDU, and then determines the size of the (remained) higher layer data segment (after encryption if needed) that can be included in the MAC PDU based on the remaining available MAC PDU space. This is because in this case anyway (further) segmentation needs to be performed no matter MAC CE is transmitted or not so it may be good to prioritize MAC CE transmission by which the reader can take more appropriate actions for subsequent R2D / D2R transmissions.

[0223] • Otherwise, the device first reserves space for all the (remained) higher layer data (after encryption if needed) in the MAC PDU and then determines which MAC CE(s) (if any) can be included in the MAC PDU based on the remaining available MAC PDU space. By this (further) segmentation can be avoided which saves device energy.

[0224] Figure 6 shows an example of a communication system QQ100 in accordance with some embodiments.

[0225] In the example, the communication system QQ100 includes a telecommunications network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes or base stations of various types, access network nodes QQ110A and QQ110B are depicted (which may be collectively referred to as network nodes QQ110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network QQ104 may include more than one access network technology. The network nodes QQ110 of access network QQ104 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs QQ112A, QQ112B, QQ112C, and QQ112D (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections. 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 QQ102includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network QQ102 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 QQ102, including one or more access network nodes QQ110 and / or core network nodes QQ108.

[0226] 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 control application (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 A1, F1, W1, E1, 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 O-RAN Alliance or comparable technologies.

[0227] The network nodes QQ110 facilitate direct or indirect connection of one or more UEs QQ112 to the core network QQ106 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 QQ100 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 QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0228] The UEs QQ112 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 QQ110 and other communication devices. Similarly, the network nodes QQ108,QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network QQ102) with the UEs QQ112 and / or with other network nodes or equipment in the telecommunications network QQ102 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 QQ102. More specifically, UEs QQ112 may send messages, data, and / or other signals to network nodes QQ108, QQ110 or other elements of the telecommunications network QQ102 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 intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes QQ108, QQ110 may send messages, data, and other signals to UEs QQ1122, other network nodes QQ108, QQ110, and other devices in telecommunications network QQ102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE QQ 112 by transmitting the message to an access network node QQ110 that will then transmit the message to the intended UE QQ112. Similarly, a core network node 108 may receive a particular message from a UE QQ112 by receiving the message from an access network node QQ110 that itself received the message from the UE QQ112.

[0229] In the depicted example, the core network QQ106 connects elements of the access network QQ104 (e.g., one or more of the network nodes QQ110) to one or more host computing systems, such as host QQ116. 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 QQ106 includes one or more core network nodes (e.g., core network node QQ108) of various types, one or more of which may be generally referred to as network nodes QQ108. Network nodes QQ108 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 QQ108. 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).The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunications network QQ102. The host QQ116 may be operated by the service provider or on behalf of the service provider. The host QQ116 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.

[0230] As a whole, the communication system QQ100 of Figure 6 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system QQ100 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 QQ100 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 QQ100 supporting different standards, protocols, or rule sets.

[0231] As one example, in certain embodiments, access network QQ104 may contain some access network nodes QQ110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes QQ110 support (or the same access network nodes QQ110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network QQ102 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.Telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network QQ102. For example, the telecommunications network QQ102 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)ZMassive loT services to yet further UEs.

[0232] In some examples, one or more of the UEs QQ112 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 QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0233] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112C and / or QQ112D) and network nodes (e.g., network node QQ110B). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 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 QQ110, or by executable code, script, process, or other instructions in the hub QQ114.

[0234] As another example, the hub QQ114 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 QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110B. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112C and / or QQ112D), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 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 QQ110B. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0235] Figure 7 is another example of a communication system QQ200 according to some embodiments. As used herein, the communication system QQ200 includes multiple access points (APs) QQ210 (with four exemplary APs QQ210A, QQ210B, QQ210C, and QQ210D being depicted) and multiple wireless devices, referred to in the context of communication system QQ200 as stations (ST As) QQ212 (referred to individually as STA QQ212A, STA QQ212B, STAQQ212C, STA QQ212D, and STA QQ212E). STA QQ212A is served byAP QQ210A in a first basic service set (BSS) QQ220A. STA QQ210B and STA QQ210C are served byAP QQ210B in a second BSS, BSS QQ220B. STAQQ212D is served byAP QQ210C in a third BSS, BSS QQ220C. STA QQ212E is served by AP QQ210D in a fourth BSS, BSS QQ220D. Stations QQ212 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 QQ212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0236] Each of STAs QQ212 may connect through a radio link to one of APs QQ210. For example, depending on location or channel conditions experienced by a given STA QQ212, 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 afrequency 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.

[0237] Each AP QQ210 may provide data connectivity to ST As QQ212 connected to a particular AP QQ210. As illustrated, APs QQ210 may be connected to a data network QQ230. In this way, APs QQ210 may also provide data connectivity between STAs QQ212 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 QQ212 and its serving AP QQ210 may be used for providing various kinds of services to STA QQ212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA QQ212 and / or on a device linked to STA QQ212. By way of example, Figure 7 illustrates an application service platform QQ232 provided in data network QQ230. The application(s) executed on STA QQ212 and / or on one or more other devices linked to STA QQ212 may use the radio link for data communication with one or more other STA QQ212 and / or the application service platform QQ232, thereby enabling utilization of the corresponding service(s) at STA QQ212.

[0238] Figure 8 shows a wireless device QQ300, which may be configured to operate in communication system QQ100 of Figure 6 or in communication system QQ200 of Figure 7. The wireless device QQ300 may be alternatively referred to as a UE QQ300, like a UE QQ112 within the context of communication system QQ100, or as a station (STA) QQ300 or as a non-access-point station (non-AP STA) QQ300, like a STA QQ212 within the context of the communication system QQ200, 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), laptop-mounted 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 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.A wireless device QQ300 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), orvehicle-to-everything (V2X). In other examples, wireless device QQ300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device QQ300 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device QQ300 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0239] In particular embodiments, wireless device QQ300 includes processing circuitry QQ302 that is operatively coupled via a bus QQ304 to an input / output interface QQ306, a power source QQ308, a memory QQ310, a communication interface QQ312, and / or any other component, or any combination thereof. Certain embodiments of wireless device QQ300 may include all or a subset of the components shown in Figure 8. The level of integration between the components may vary from some examples of wireless device QQ300 to another. In general, in a particular embodiment of wireless device QQ300, processing circuitry QQ302, input / output interface QQ306, power source QQ308, memory QQ310, and communication interface QQ312 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 QQ300. Further, certain embodiments of wireless devices QQ300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0240] The processing circuitry QQ302 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 QQ310. The processing circuitry QQ302 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 QQ302 may include multiple central processing units (CPUs). The processing circuitry QQ302 may be configured to cause the wireless device QQ300 to perform the methods as described with reference to Figure 1, 2, 3 and / or 4.In the example, the input / output interface QQ306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device QQ300. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0241] In some embodiments, the power source QQ308 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 QQ308 may further include power circuitry for delivering power from the power source QQ308 itself, and / or an external power source, to the various parts of wireless device QQ300 via input circuitry or an interface such as an electrical power cable. Power source QQ308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device QQ300 to which power is supplied.

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

[0243] The memory QQ310 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 (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ310 may allow wireless device QQ300 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 QQ310, which may be or comprise a device-readable storage medium.

[0244] The processing circuitry QQ302 may be configured to communicate with an access network or other network via or using the communication interface QQ312. The communication interface QQ312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ322. The communication interface QQ312 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 QQ318 and / or a receiver QQ320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ318 and receiver QQ320 may be coupled to one or more antennas (e.g., antenna QQ322) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0245] In the illustrated embodiment, communication functions of the communication interface QQ312 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, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol(TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0246] In particular embodiments, wireless device QQ300 may provide an output of data captured via a sensor, through its communication interface QQ312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device QQ300 can be communicated through a wireless connection to a network node via another wireless device QQ300. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

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

[0248] Wireless device QQ300, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device QQ300 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 QQ300 shown in Figure 8.As yet another specific example, in an loT scenario, wireless device QQ300 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 QQ300 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 QQ300 may implement the 3GPP NB-loT standard. In other scenarios, wireless device QQ300 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.

[0249] In practice, any number of wireless devices QQ300 may be used together with respect to a single use case. For example, a first wireless device QQ300 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 QQ300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device QQ300 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device QQ300 can also include more than one of the functionalities described above. For example, wireless device QQ300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0250] Figure 9 shows a network node QQ400 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 QQ400 may be configured to operate in communication system QQ100 of Figure 6, like network nodes QQ108 or QQ110, or in communication system QQ200 of Figure 7, like an AP QQ210 or a station QQ212. 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)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0251] Network nodes QQ400 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 QQ400 may be a relay node or a relay donor node controlling a relay. Network nodes QQ400 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., inan 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).

[0252] Other examples of network nodes QQ400 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).

[0253] In particular embodiments, network node QQ400 includes a processing circuitry QQ402, a memory QQ404, a communication interface QQ406, and a power source QQ408. In general, in a particular embodiment of network node QQ400, processing circuitry QQ402, memory QQ404, communication interface QQ406, and power source QQ408 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 QQ400.

[0254] The network node QQ400 may be composed of multiple distinct network entities (e.g., a NodeB 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 QQ400 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 QQ400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories QQ404 or portions of memory QQ404 for different RATs) and some components may be reused (e.g., a same antenna QQ410 may be shared by different RATs). The network node QQ400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ400, 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 QQ400.The processing circuitry QQ402 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 QQ404, to provide network node QQ400 functionality. For example, the processing circuitry QQ402 may be configured to cause the network node QQ400 to perform the methods as described with reference to Figure 1, 2, 3 and / or 4.

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

[0256] The memory QQ404 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ402. The memory QQ404 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 QQ402 and utilized by the network node QQ400. The memory QQ404 may be used to store any calculations made by the processing circuitry QQ402 and / or any data received via the communication interface QQ406. In some embodiments, the processing circuitry QQ402 and memory QQ404 is integrated.

[0257] The communication interface QQ406 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 QQ406 comprises port(s) / terminal(s) QQ416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node QQ300 may be capable of wirelesscommunication and communication interface QQ406 may also include radio front-end circuitry QQ418 that may be coupled to, or in certain embodiments a part of, an antenna QQ410. Particular embodiments of radio front-end circuitry QQ418 include filter(s) QQ420 and amplifier(s) QQ422. The radio front-end circuitry QQ418 may be connected to an antenna QQ410 and processing circuitry QQ402. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ410 and processing circuitry QQ402. The radio front-end circuitry QQ418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters QQ420 and / or amplifiers QQ422. The radio signal(s) may then be transmitted via the antenna QQ410. Similarly, when receiving data, the antenna QQ410 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ418. The digital data may be passed to the processing circuitry QQ402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0258] In certain alternative embodiments, network node QQ400 may be capable of wireless communication but does not include separate radio front-end circuitry QQ418, instead, the processing circuitry QQ402 includes radio front-end circuitry and is connected to the antenna QQ410. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ412 is part of the communication interface QQ406. In still other embodiments, the communication interface QQ406 includes one or more ports or terminals QQ416, the radio front-end circuitry QQ418, and the RF transceiver circuitry QQ412, as part of a radio unit (not shown), and the communication interface QQ406 communicates with the baseband processing circuitry QQ414, which is part of a digital unit (not shown).

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

[0260] The antenna QQ410, communication interface QQ406, and / or the processing circuitry QQ402 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 QQ400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ410, the communication interfaceQQ406, and / or the processing circuitry QQ402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node QQ400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0261] The power source QQ408 provides power to the various components of network node QQ400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ400 with power for performing the functionality described herein. For example, the network node QQ400 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 QQ408. As a further example, the power source QQ408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

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

[0263] Figure 10 is a block diagram illustrating a virtualization environment QQ500 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 QQ500 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 entirelyvirtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0264] Applications QQ502 (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.

[0265] Hardware QQ504 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 QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM QQ508A and VM QQ508B (which may be collectively referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs QQ508. The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, 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.

[0266] In the context of NFV, each of the VMs QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 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 QQ508 on top of the hardware QQ504 and corresponds to an application QQ502. Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization.Alternatively, hardware QQ504 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 QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 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 QQ512 which may alternatively be used for communication between hardware nodes and radio units.

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

[0268] 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 maybe 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. This disclosure includes the following enumerated example embodiments.

[0269] Group A Embodiments

[0270] 1. A method performed by a first wireless communication device for determining, based on the indication in the second message, whether a message from the second wireless communication device comprises a plurality of message segments, the method comprising:

[0271] receiving a first message from the second wireless communication device; and if the first message includes an indication, determining, based on the indication in the first message, whether a second message from the second wireless communication device comprises a plurality of message segments.

[0272] 2. The method of embodiment 1 , comprising, before receiving the first message from the second wireless communication device, sending a paging message to the second wireless communication device, wherein the paging message indicates whether the second communication device should include the indication in the second message to the first wireless communication device.

[0273] 3. The method of embodiment 2, wherein:

[0274] the first message includes the indication if the paging message indicates that the second communication device should include the indication in the first message to the first wireless communication device; and / or

[0275] the first message does not include the indication if the paging message indicates that the second communication device should not include the indication in the first message to the first wireless communication device.

[0276] 4. The method of embodiment 2 or 3, wherein:

[0277] the paging message indicates that the second communication device should include the indication in the first message to the first wireless communication device if an expectedsize of the second message is not available at the first wireless communication device; and / or

[0278] the paging message indicates that the second communication device should not include the indication in the first message to the first wireless communication device if the expected size of the second message is available at the first wireless communication device.

[0279] 5. The method of embodiment 4, comprising receiving the expected message size from a network node, such that the expected size of the second message is available at the first wireless communication device.

[0280] 6. The method of embodiment 4, comprising determining the expected message size from one or more of the following information received from the network node:

[0281] one or more expected message sizes from the network node;

[0282] one or more sizes of device identifiers;

[0283] a size, of a truncated device identifier, determined from mask information for the device identifier;

[0284] a size, of a remaining identifier, determined from a partial identifier for the device.

[0285] 7. The method of embodiment 5 or 6, wherein the network node comprises a core network node, an application function (AF), or an Ambient loT Function (AIOTF).

[0286] 8. The method of any of embodiments 1 to 7, wherein the indication in the first message indicates whether the second message from the second wireless communication device comprises a plurality of message segments.

[0287] 9. The method of any of embodiments 1 to 8, wherein:

[0288] the indication in the first message indicates that the second message from the second wireless communication device comprises a plurality of message segments if the second message includes a long device identifier format; and / or

[0289] the indication in the first message indicates that the second message from the second wireless communication device does not comprise a plurality of message segments if the second message includes a short device identifier format.

[0290] 10. The method of any of embodiments 1 to 9, comprising determining, based on whether the second message from the second wireless communication device comprises a plurality of message segments, a size of resources allocated for the second message, or one or more remaining segments of the second message.11. The method of any of embodiments 1 to 10, wherein the indication in the first message comprises one or more bits.

[0291] 12. The method of any of embodiments 1 to 11 , wherein the indication in the first message comprises a random number.

[0292] 13. The method of embodiment 12, wherein:

[0293] the random number indicates that the second message from the second wireless communication device comprises a plurality of message segments if the random number has one of a first plurality of values; and

[0294] the random number indicates that the second message from the second wireless communication device does not comprise a plurality of message segments if the random number has one of a second plurality of values.

[0295] 14. The method of embodiment 13, wherein the first plurality of values comprises a first range of values, and the second plurality of values comprises a second range of values.

[0296] 15. The method of embodiment 13 or 14, wherein the random number comprises a random access preamble or random identifier.

[0297] 16. The method of any of embodiments 1 to 15, wherein:

[0298] the first message comprises a random access preamble, a random identifier, or a Msg1; and / or

[0299] the second message comprises a Msg3 in a random access procedure, a Msg5 or other message.

[0300] 17. The method of any of embodiments 1 to 16, wherein:

[0301] the first wireless communication device comprises a reader or ambient-internet of things (A-loT) reader; and / or

[0302] the second wireless communication device comprises an ultra low power device, zero energy device or A-loT device.

[0303] 18. A method performed by a second wireless communication device for sending an indication in a message, the method comprising:

[0304] sending, to a first wireless communication device, a first message;wherein, if the second communication device should include an indication in the first message to the first wireless communication device that a second message from the second wireless communication device comprises a plurality of message segments, the first message includes the indication.

[0305] 19. The method of embodiment 18, comprising, before sending the first message to the first wireless communication device, receiving a paging message from the first wireless communication device, wherein the paging message indicates whether the second communication device should include the indication in the second message to the first wireless communication device.

[0306] 20. The method of embodiment 19, wherein:

[0307] the first message includes the indication if the paging message indicates that the second communication device should include the indication in the first message to the first wireless communication device; and / or

[0308] the first message does not include the indication if the paging message indicates that the second communication device should not include the indication in the first message to the first wireless communication device.

[0309] 21. The method of embodiment 19 or 20, wherein:

[0310] the paging message indicates that the second communication device should include the indication in the first message to the first wireless communication device if an expected size of the second message is not available at the first wireless communication device; and / or

[0311] the paging message indicates that the second communication device should not include the indication in the first message to the first wireless communication device if the expected size of the second message is available at the first wireless communication device.

[0312] 22. The method of any of embodiments 18 to 21 , wherein the indication in the first message indicates whether the second message from the second wireless communication device comprises a plurality of message segments.

[0313] 23. The method of any of embodiments 18 to 22, wherein:

[0314] the indication in the first message indicates that the second message from the second wireless communication device comprises a plurality of message segments if the second message includes a long device identifier format; and / orthe indication in the first message indicates that the second message from the second wireless communication device does not comprise a plurality of message segments if the second message includes a short device identifier format.

[0315] 24. The method of any of embodiments 18 to 23, comprising receiving, from the first wireless communication device, an indication of resources allocated for the second message, wherein a size of the resources is based on whether the second message from the second wireless communication device comprises a plurality of message segments.

[0316] 25. The method of any of embodiments 18 to 24, wherein the indication in the first message comprises one or more bits.

[0317] 26. The method of any of embodiments 18 to 25, wherein the indication in the first message comprises a random number.

[0318] 27. The method of embodiment 26, wherein:

[0319] the random number indicates that the second message from the second wireless communication device comprises a plurality of message segments if the random number has one of a first plurality of values; and

[0320] the random number indicates that the second message from the second wireless communication device does not comprise a plurality of message segments if the random number has one of a second plurality of values.

[0321] 28. The method of embodiment 27, wherein the first plurality of values comprises a first range of values, and the second plurality of values comprises a second range of values.

[0322] 29. The method of embodiment 27 or 28, wherein the random number comprises a random access preamble or random identifier.

[0323] 30. The method of any of embodiments 18 to 29, wherein:

[0324] the first message comprises a random access preamble, a random identifier, or a Msg1; and / or

[0325] the second message comprises a Msg3 in a random access procedure, a Msg5 or other message.

[0326] 31. The method of any of embodiments 18 to 30, wherein:the first wireless communication device comprises a reader or ambient-internet of things (A-loT) reader; and / or

[0327] the second wireless communication device comprises an ultra low power device, zero energy device or A-loT device.

[0328] 32. A method performed by a first wireless communication device for receiving a message, the method comprising:

[0329] receiving a first message from a second communication device,

[0330] wherein the first message includes an indication of one or more of:

[0331] - whether the first message is a segment of a second message;

[0332] - whether the first message is a last segment of the second message;

[0333] - whether a further message to be sent by the second communication device to the first communication device is a segment of the second message;

[0334] - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.

[0335] 33. The method of embodiment 32, wherein the remaining size is a size of a part of the second message or of the payload remaining to be sent to the first communication device by the second communication device.

[0336] 34. The method of embodiment 32 or 33, wherein the first message includes an indication of the total size of the second message or of the payload of the second message if the first message comprises a segment of the second message that is not the last segment of the second message.

[0337] 35. The method of embodiment 34, wherein the first message includes the indication of the total size of the second message or of the payload of the second message instead of an indication of a size of the first message or of a payload of the first message if the first message comprises a segment of the second message that is not the last segment of the second message.

[0338] 36. The method of embodiment 35, wherein the indication of the total size of the second message is comprised in a field of the first message that, when the first message is the last segment of the second message, is not a segment of the second message, or is not a segmented message, is used for the indication of the size of the first message or of the payload of the first message.37. The method of any of embodiments 32 to 36, wherein the first message comprises a first segment of the second message, and the method further comprises receiving one or more additional messages from the second wireless communication device, wherein each of the one or more additional messages comprises a segment of the second message, and each of the one or more additional messages does not include the indication of the total size of the second message or of the payload of the second message.

[0339] 38. The method of any of embodiments 32 to 37, wherein the first message includes an indication of the remaining size of the second message or of the payload of the second message if the first message comprises a segment of the second message that is not the last segment of the second message.

[0340] 39. The method of any of embodiments 32 to 38, wherein the first message includes an indication of the size of the first message or of the payload of the first message if the first message comprises a segment of the second message that is the last segment of the second message, or does not comprise a segment of the second message, or is not a segmented message.

[0341] 40. The method of any of embodiments 32 to 39, wherein, when the first message does not comprise a segment of the second message or is not a segmented message, the first message does not include the indication or includes an indication that the first message is not a segment of a second message or is not a segmented message.

[0342] 41. The method of any of embodiments 32 to 40, wherein:

[0343] the first message includes the indication of whether the first message is a segment of the second message if an expected size of the second message is available at the first wireless communication device; and / or

[0344] the first message includes the indication of the total size of the second message or of the payload of the second message and / or the remaining size of the second message or of the payload of the second message if the expected size of the second message is not available at the first wireless communication device.

[0345] 42. The method of embodiment 41 , comprising sending, to the second wireless communication device, information including one or more of:

[0346] an indication of whether the expected size of the second message is available at the first wireless communication device;if the expected size of the second message is available at the first wireless communication device, an indication that the first message should include the indication of whether the first message is a segment of the second message;

[0347] if the expected size of the second message is not available at the first wireless communication device, an indication that the first message should include the indication of the total size of the second message or of the payload of the second message and / or the remaining size of the second message or of the payload of the second message.

[0348] 43. The method of embodiment 42, comprising sending the information to the second wireless communication device in a configuration and / or in a paging message to the second wireless communication device.

[0349] 44. The method of any of embodiments 41 to 43, comprising receiving the expected message size from a network node, such that the expected size of the second message is available at the first wireless communication device.

[0350] 45. The method of embodiment 44, wherein the network node comprises a core network node, an application function (AF), or an Ambient loT Function (AIOTF).

[0351] 46. The method of any of embodiments 32 to 45, wherein:

[0352] the first message comprises a Msg3 or Msg5, or a segment of a Msg3 or of a Msg5; and / or

[0353] the second message comprises a Msg3 or Msg5.

[0354] 47. The method of any of embodiments 32 to 46, wherein the payload comprises a Protocol Data Unit (PDU), a Medium Access Control (MAC) PDU, and / or user data.

[0355] 48. The method of any of embodiments 32 to 47, wherein the indication comprises or is included in one or more of:

[0356] one or more bits in the first message;

[0357] a field in a header of the first message;

[0358] a length field in a header of the first message;

[0359] a field in a Medium Access Control (MAC) header of the first message.

[0360] 49. The method of any of embodiments 32 to 48, wherein:

[0361] the first wireless communication device comprises a reader or ambient-internet of things (A-loT) reader; and / orthe second wireless communication device comprises an ultra low power device, zero energy device or A-loT device.

[0362] 50. A method performed by a second wireless communication device for sending a message, the method comprising:

[0363] sending a first message to a first communication device,

[0364] wherein the first message includes an indication of one or more of:

[0365] - whether the first message is a segment of a second message;

[0366] - whether the first message is a last segment of the second message;

[0367] - whether a further message to be sent by the second communication device to the first communication device is a segment of the second message;

[0368] - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.

[0369] 51. The method of embodiment 50, wherein the remaining size is a size of a part of the second message or of the payload remaining to be sent to the first communication device by the second communication device.

[0370] 52. The method of embodiment 50 or 51 , wherein the first message includes an indication of the total size of the second message or of the payload of the second message if the first message comprises a segment of the second message that is not the last segment of the second message.

[0371] 53. The method of embodiment 52, wherein the first message includes the indication of the total size of the second message or of the payload of the second message instead of an indication of a size of the first message or of a payload of the first message if the first message comprises a segment of the second message that is not the last segment of the second message.

[0372] 54. The method of embodiment 53, wherein the indication of the total size of the second message is comprised in a field of the first message that, when the first message is the last segment of the second message, is not a segment of the second message, or is not a segmented message, is used for the indication of the size of the first message or of the payload of the first message.55. The method of any of embodiments 50 to 54, wherein the first message comprises a first segment of the second message, and the method further comprises receiving one or more additional messages from the second wireless communication device, wherein each of the one or more additional messages comprises a segment of the second message, and each of the one or more additional messages does not include the indication of the total size of the second message or of the payload of the second message.

[0373] 56. The method of any of embodiments 50 to 55, wherein the first message includes an indication of the remaining size of the second message or of the payload of the second message if the first message comprises a segment of the second message that is not the last segment of the second message.

[0374] 57. The method of any of embodiments 50 to 56, wherein the first message includes an indication of the size of the first message or of the payload of the first message if the first message comprises a segment of the second message that is the last segment of the second message, or does not comprise a segment of the second message or is not a segmented message.

[0375] 58. The method of any of embodiments 50 to 57, wherein, when the first message does not comprise a segment of the second message or is not a segmented message, the first message does not include the indication or includes an indication that the first message is now a segment of a second message.

[0376] 59. The method of any of embodiments 50 to 58, comprising receiving, from the first wireless communication device, information including one or more of:

[0377] an indication of whether the expected size of the second message is available at the first wireless communication device;

[0378] an indication that the first message should include the indication of whether the first message is a segment of the second message;

[0379] an indication that the first message should include the indication of the total size of the second message or of the payload of the second message and / or the remaining size of the second message or of the payload of the second message.

[0380] 60. The method of embodiment 59, wherein:

[0381] the first message includes the indication of whether the first message is a segment of the second message if an expected size of the second message is available at the first wireless communication device or if the indication that the first message should include theindication of whether the first message is a segment of the second message is received from the first network node; and / or

[0382] the first message includes the indication of the total size of the second message or of the payload of the second message and / or the remaining size of the second message or of the payload of the second message if the expected size of the second message is not available at the first wireless communication device or the indication that the first message should include the indication of the total size of the second message or of the payload of the second message and / or the remaining size of the second message or of the payload of the second message is received from the first network node.

[0383] 61. The method of embodiment 59 or 60, comprising sending the information to the second wireless communication device in a configuration and / or in a paging message to the second wireless communication device.

[0384] 62. The method of any of embodiments 50 to 61 , wherein:

[0385] the first message comprises a Msg3 or Msg5, or a segment of a Msg3 or of a Msg5; and / or

[0386] the second message comprises a Msg3 or Msg5.

[0387] 63. The method of any of embodiments 50 to 62, wherein the payload comprises a Protocol Data Unit (PDU), a Medium Access Control (MAC) PDU, and / or user data.

[0388] 64. The method of any of embodiments 50 to 63, wherein the indication comprises or is included in one or more of:

[0389] one or more bits in the first message;

[0390] a field in a header of the first message;

[0391] a length field in a header of the first message;

[0392] a field in a Medium Access Control (MAC) header of the first message.

[0393] 65. The method of any of embodiments 50 to 64, wherein:

[0394] the first wireless communication device comprises a reader or ambient-internet of things (A-loT) reader; and / or

[0395] the second wireless communication device comprises an ultra low power device, zero energy device or A-loT device.

[0396] Group C Embodiments

[0397] 66. A wireless device (QQ112, QQ212, QQ300) comprising:processing circuitry (QQ302) configured to cause the wireless device to perform any of the operations of any of the Group A embodiments; and

[0398] a power source (QQ308) configured to supply power to the processing circuitry (QQ302).

[0399] 67. A wireless device comprising:

[0400] one or more antennas;

[0401] communication interface connected to the one or more antennas and to processing circuitry;

[0402] the processing circuitry being configured to cause the wireless device to perform any of the operations of any of the Group A embodiments;

[0403] an input interface connected to the processing circuitry and configured to allow input of information into the wireless device to be processed by the processing circuitry;

[0404] an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and

[0405] a power source connected to the processing circuitry and configured to supply power to the wireless device.

[0406] 68. A computer program product comprising a non-transitory computer-readable medium having computer-readable code embodied therein, the computer-readable code being configured such that, on execution by a suitable computer or processing circuitry, the computer or processing circuitry is caused to perform the method of any of the Group A embodiments.

[0407] 69. A wireless device (QQ112, QQ212, QQ300) configured to perform the method of any of the Group A embodiments.

[0408] 70. A wireless device (QQ112, QQ212, QQ300) comprising processing circuitry (QQ302) and a memory (QQ310), said memory containing instructions executable by said processing circuitry whereby said wireless device is operative to perform the method of any of the Group A embodiments.

[0409] 71. A tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations in a first wireless communication device for determining whether a message comprises a plurality of message segments, the operations comprising:receiving (102) a first message from the second wireless communication device; and if the first message includes an indication, determining (104), based on the indication in the first message, whether a second message from the second wireless communication device comprises a plurality of message segments.

[0410] 72. The computer-readable medium of embodiment 71 , comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform the method (100) of any of embodiments 2 to 17.

[0411] 73. A tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations in a second wireless communication device for sending an indication in a message, the operations comprising:

[0412] sending (202), to a first wireless communication device, a first message; wherein, if the second communication device should include an indication in the first message to the first wireless communication device that a second message from the second wireless communication device comprises a plurality of message segments, the first message includes the indication.

[0413] 74. The computer-readable medium of embodiment 73, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform the method (200) of any of embodiments 19 to 31.

[0414] 75. A tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations in a first wireless communication device for receiving a message, the operations comprising:

[0415] receiving (302) a first message from a second communication device,

[0416] wherein the first message includes an indication of one or more of:

[0417] whether the first message is a segment of a second message;

[0418] whether the first message is a last segment of the second message;

[0419] whether a further message to be sent by the second communication device to the first communication device is a segment of the second message;

[0420] a total size of the second message or of a payload of the second message;

[0421] a remaining size of the second message or of the payload of the second message.76. The computer-readable medium of embodiment 75, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform the method (300) of any of embodiments 33 to 49.

[0422] 77. A tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations in a second wireless communication device for sending a message, the operations comprising:

[0423] sending (402) a first message to a first communication device,

[0424] wherein the first message includes an indication of one or more of:

[0425] whether the first message is a segment of a second message;

[0426] whether the first message is a last segment of the second message;

[0427] whether a further message to be sent by the second communication device to the first communication device is a segment of the second message;

[0428] a total size of the second message or of a payload of the second message;

[0429] a remaining size of the second message or of the payload of the second message.

[0430] 78. The computer-readable medium of embodiment 77, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform the method (400) of any of embodiments 51 to 65.

[0431] 79. A computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method (100, 200, 300, 400) according to any of embodiments 1 to 65.

[0432] 80. A computer program, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method (100, 200, 300, 400) according to any of embodiments 1 to 65.

[0433] 81. A carrier containing the computer program of embodiment 80, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer-readable medium.

[0434] ABBREVIATIONS

[0435] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).3GPP 3rd Generation Partnership Project

[0436] 5G 5th Generation

[0437] 6G 6th Generation

[0438] ABS Almost Blank Subframe

[0439] ARQ Automatic Repeat Request

[0440] AWGN Additive White Gaussian Noise

[0441] BCCH Broadcast Control Channel

[0442] BCH Broadcast Channel

[0443] CA Carrier Aggregation

[0444] CC Carrier Component

[0445] CCCH SDU Common Control Channel SDU

[0446] CDMA Code Division Multiplex Access

[0447] CGI Cell Global Identity

[0448] CIR Channel Impulse Response

[0449] CP Cyclic Prefix

[0450] CPICH Common Pilot Channel

[0451] CQI Channel Quality Information

[0452] C-RNTI Cell RNTI

[0453] CSI Channel State Information

[0454] DCCH Dedicated Control Channel

[0455] DL Downlink

[0456] DM Demodulation

[0457] DMRS Demodulation Reference Signal

[0458] DRX Discontinuous Reception

[0459] DTX Discontinuous Transmission

[0460] DTCH Dedicated Traffic Channel

[0461] DUT Device Under Test

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

[0463] Ec / No Received energy per chip divided by the power density in the band eMBMS Evolved Multimedia Broadcast Multicast Services

[0464] ECGI Evolved CGI

[0465] eNB E-UTRAN NodeB

[0466] ePDCCH Enhanced Physical Downlink Control Channel

[0467] E-SMLC Evolved Serving Mobile Location Center

[0468] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0469] FDD Frequency Division Duplex

[0470] FFS For Further StudygNB Base station in NR

[0471] GNSS Global Navigation Satellite System

[0472] HARQ Hybrid Automatic Repeat Request

[0473] HO Handover

[0474] HSPA High Speed Packet Access

[0475] HRPD High Rate Packet Data

[0476] LOS Line of Sight

[0477] LPP LTE Positioning Protocol

[0478] LTE Long-Term Evolution

[0479] MAC Medium Access Control

[0480] MAC Message Authentication Code

[0481] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe

[0482] MDT Minimization of Drive Tests

[0483] MIB Master Information Block

[0484] MME Mobility Management Entity

[0485] MSC Mobile Switching Center

[0486] NPDCCH Narrowband Physical Downlink Control Channel

[0487] NR New Radio

[0488] OCNG OFDMA Channel Noise Generator

[0489] OFDM Orthogonal Frequency Division Multiplexing

[0490] OFDMA Orthogonal Frequency Division Multiple Access

[0491] OSS Operations Support System

[0492] OTDOA Observed Time Difference of Arrival

[0493] O&M Operation and Maintenance

[0494] PBCH Physical Broadcast Channel

[0495] P-CCPCH Primary Common Control Physical Channel

[0496] PCell Primary Cell

[0497] PCFICH Physical Control Format Indicator Channel

[0498] PDCCH Physical Downlink Control Channel

[0499] PDCP Packet Data Convergence Protocol

[0500] PDP Power Delay Profile

[0501] PDSCH Physical Downlink Shared Channel

[0502] PG W Packet Gateway

[0503] PHICH Physical Hybrid-ARQ Indicator Channel

[0504] PLMN Public Land Mobile Network

[0505] PMI Precoding Matrix IndicatorPRACH Physical Random Access Channel PRS Positioning Reference Signal

[0506] PSS Primary Synchronization Signal

[0507] PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel RACH Random Access Channel

[0508] QAM Quadrature Amplitude Modulation

[0509] RAN Radio Access Network

[0510] RAT Radio Access Technology

[0511] RLC Radio Link Control

[0512] RLM Radio Link Monitoring

[0513] RNC Radio Network Controller

[0514] RNTI Radio Network Temporary Identifier

[0515] RRC Radio Resource Control

[0516] RRM Radio Resource Management

[0517] RS Reference Signal

[0518] RSCP Received Signal Code Power

[0519] RSRP Reference Symbol Received Power OR Reference Signal Received Power

[0520] RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality

[0521] RSSI Received Signal Strength Indicator

[0522] RSTD Reference Signal Time Difference SCH Synchronization Channel

[0523] SCell Secondary Cell

[0524] SDAP Service Data Adaptation Protocol SDU Service Data Unit

[0525] SFN System Frame Number

[0526] SGW Serving Gateway

[0527] SI System Information

[0528] SIB System Information Block

[0529] SNR Signal to Noise Ratio

[0530] SON Self-Organizing Network

[0531] SS Synchronization Signal

[0532] SSS Secondary Synchronization Signal

[0533] TDD Time Division Duplex

[0534] TDOA Time Difference of ArrivalTOA Time of Arrival

[0535] TSS Tertiary Synchronization Signal

[0536] TTI Transmission Time Interval

[0537] UE User Equipment

[0538] UL Uplink

[0539] UMTS Universal Mobile Telecommunications System USIM Universal Subscriber Identity Module

[0540] UTDOA Uplink Time Difference of Arrival WCDMA Wideband CDMA

[0541] WLAN Wireless Local Area Network

Claims

Claims1. A method (100) performed by a first wireless communication device for determining whether a message comprises a plurality of message segments, the method comprising: receiving (102) a first message from the second wireless communication device; and if the first message includes an indication, determining (104), based on the indication in the first message, whether a second message from the second wireless communication device comprises a plurality of message segments.

2. The method of claim 1, comprising, before receiving (12) the first message from the second wireless communication device, sending a paging message to the second wireless communication device, wherein the paging message indicates whether the second communication device should include the indication in the second message to the first wireless communication device.

3. The method of claim 2, wherein:the first message includes the indication if the paging message indicates that the second communication device should include the indication in the first message to the first wireless communication device; and / orthe first message does not include the indication if the paging message indicates that the second communication device should not include the indication in the first message to the first wireless communication device.

4. The method of claim 2 or 3, wherein:the paging message indicates that the second communication device should include the indication in the first message to the first wireless communication device if an expected size of the second message is not available at the first wireless communication device; and / orthe paging message indicates that the second communication device should not include the indication in the first message to the first wireless communication device if the expected size of the second message is available at the first wireless communication device.

5. The method of claim 4, comprising receiving the expected message size from a network node, such that the expected size of the second message is available at the first wireless communication device, or determining the expected message size from one or more of the following information received from the network node:one or more expected message sizes from the network node;one or more sizes of device identifiers;a size, of a truncated device identifier, determined from mask information for the device identifier;a size, of a remaining identifier, determined from a partial identifier for the device.

6. The method of claim 5, wherein the network node comprises a core network node, an application function (AF), or an Ambient loT Function (AIOTF).

7. The method of any of claims 1 to 6, wherein:the indication in the first message indicates whether the second message from the second wireless communication device comprises a plurality of message segments; and / or the indication in the first message indicates that the second message from the second wireless communication device comprises a plurality of message segments if the second message includes a long device identifier format; and / orthe indication in the first message indicates that the second message from the second wireless communication device does not comprise a plurality of message segments if the second message includes a short device identifier format.

8. The method of any of claims 1 to 7, comprising determining, based on whether the second message from the second wireless communication device comprises a plurality of message segments, a size of resources allocated for the second message, or one or more remaining segments of the second message.

9. The method of any of claims 1 to 8, wherein the indication in the first message comprises one or more bits, and / or comprises a random number.

10. The method of claim 9, wherein:the random number indicates that the second message from the second wireless communication device comprises a plurality of message segments if the random number has one of a first plurality of values; andthe random number indicates that the second message from the second wireless communication device does not comprise a plurality of message segments if the random number has one of a second plurality of values.

11. The method of claim 10, wherein the random number comprises a random access preamble or random identifier.

12. The method of any of claims 1 to 11 , wherein:the first message comprises a random access preamble, a random identifier, or a Msg1; and / orthe second message comprises a Msg3 in a random access procedure, a Msg5 or other message.

13. The method of any of claims 1 to 12, wherein:the first wireless communication device comprises a reader or ambient-internet of things (A-loT) reader; and / orthe second wireless communication device comprises an ultra low power device, zero energy device or A-loT device.

14. A method (200) performed by a second wireless communication device for sending an indication in a message, the method comprising:sending (202), to a first wireless communication device, a first message; wherein, if the second communication device should include an indication in the first message to the first wireless communication device that a second message from the second wireless communication device comprises a plurality of message segments, the first message includes the indication.

15. The method of claim 14, comprising, before sending (202) the first message to the first wireless communication device, receiving a paging message from the first wireless communication device, wherein the paging message indicates whether the second communication device should include the indication in the second message to the first wireless communication device.

16. The method of claim 15, wherein:the first message includes the indication if the paging message indicates that the second communication device should include the indication in the first message to the first wireless communication device; and / orthe first message does not include the indication if the paging message indicates that the second communication device should not include the indication in the first message to the first wireless communication device.

17. The method of claim 15 or 16, wherein:the paging message indicates that the second communication device should include the indication in the first message to the first wireless communication device if an expectedsize of the second message is not available at the first wireless communication device; and / orthe paging message indicates that the second communication device should not include the indication in the first message to the first wireless communication device if the expected size of the second message is available at the first wireless communication device.

18. The method of any of claims 14 to 18, wherein:the indication in the first message indicates whether the second message from the second wireless communication device comprises a plurality of message segments; and / or the indication in the first message indicates that the second message from the second wireless communication device comprises a plurality of message segments if the second message includes a long device identifier format; and / orthe indication in the first message indicates that the second message from the second wireless communication device does not comprise a plurality of message segments if the second message includes a short device identifier format.

19. The method of any of claims 14 to 18, comprising receiving, from the first wireless communication device, an indication of resources allocated for the second message, wherein a size of the resources is based on whether the second message from the second wireless communication device comprises a plurality of message segments.

20. The method of any of claims 14 to 19, wherein the indication in the first message comprises one or more bits and / or comprises a random number.

21. The method of claim 20, wherein:the random number indicates that the second message from the second wireless communication device comprises a plurality of message segments if the random number has one of a first plurality of values; andthe random number indicates that the second message from the second wireless communication device does not comprise a plurality of message segments if the random number has one of a second plurality of values.

22. The method of claim 21 , wherein the random number comprises a random access preamble or random identifier.

23. The method of any of claims 14 to 22, wherein:the first message comprises a random access preamble, a random identifier, or a Msg1; and / orthe second message comprises a Msg3 in a random access procedure, a Msg5 or other message.

24. The method of any of claims 14 to 23, wherein:the first wireless communication device comprises a reader or ambient-internet of things (A-loT) reader; and / orthe second wireless communication device comprises an ultra low power device, zero energy device or A-loT device.

25. A method (300) performed by a first wireless communication device for receiving a message, the method comprising:receiving (302) a first message from a second communication device,wherein the first message includes an indication of one or more of:- whether the first message is a segment of a second message;- whether the first message is a last segment of the second message;- whether a further message to be sent by the second communication device to the first communication device is a segment of the second message; - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.

26. The method of claim 25, wherein the first message includes an indication of the total size of the second message or of the payload of the second message if the first message comprises a segment of the second message that is not the last segment of the second message.

27. The method of claim 26, wherein the first message includes the indication of the total size of the second message or of the payload of the second message instead of an indication of a size of the first message or of a payload of the first message if the first message comprises a segment of the second message that is not the last segment of the second message.

28. The method of claim 27, wherein the indication of the total size of the second message is comprised in a field of the first message that, when the first message is the last segment of the second message, is not a segment of the second message, or is not a segmentedmessage, is used for the indication of the size of the first message or of the payload of the first message.

29. The method of any of claims 25 to 28, wherein the first message comprises a first segment of the second message, and the method further comprises receiving one or more additional messages from the second wireless communication device, wherein each of the one or more additional messages comprises a segment of the second message, and each of the one or more additional messages does not include the indication of the total size of the second message or of the payload of the second message.

30. The method of any of claims 25 to 29, wherein the first message includes an indication of the remaining size of the second message or of the payload of the second message if the first message comprises a segment of the second message that is not the last segment of the second message.

31. The method of any of claims 25 to 30, wherein the first message includes an indication of the size of the first message or of the payload of the first message if the first message comprises a segment of the second message that is the last segment of the second message, or does not comprise a segment of the second message, or is not a segmented message.

32. The method of any of claims 25 to 31 , wherein, when the first message does not comprise a segment of the second message or is not a segmented message, the first message does not include the indication or includes an indication that the first message is not a segment of a second message or is not a segmented message.

33. The method of any of claims 25 to 32, wherein:the first message includes the indication of whether the first message is a segment of the second message if an expected size of the second message is available at the first wireless communication device; and / orthe first message includes the indication of the total size of the second message or of the payload of the second message and / or the remaining size of the second message or of the payload of the second message if the expected size of the second message is not available at the first wireless communication device.

34. The method of claim 33, comprising sending, to the second wireless communication device, information including one or more of:an indication of whether the expected size of the second message is available at the first wireless communication device;if the expected size of the second message is available at the first wireless communication device, an indication that the first message should include the indication of whether the first message is a segment of the second message;if the expected size of the second message is not available at the first wireless communication device, an indication that the first message should include the indication of the total size of the second message or of the payload of the second message and / or the remaining size of the second message or of the payload of the second message.

35. The method of claim 34, comprising sending the information to the second wireless communication device in a configuration and / or in a paging message to the second wireless communication device.

36. The method of any of claims 33 to 35, comprising receiving the expected message size from a network node, such that the expected size of the second message is available at the first wireless communication device.

37. The method of claim 36, wherein the network node comprises a core network node, an application function (AF), or an Ambient loT Function (AIOTF).

38. The method of any of claims 25 to 37, wherein:the first message comprises a Msg3 or Msg5, or a segment of a Msg3 or of a Msg5; and / orthe second message comprises a Msg3 or Msg5.

39. The method of any of claims 25 to 38, wherein the payload comprises a Protocol Data Unit (PDU), a Medium Access Control (MAC) PDU, and / or user data.

40. The method of any of claims 25 to 39, wherein the indication comprises or is included in one or more of:one or more bits in the first message;a field in a header of the first message;a length field in a header of the first message;a field in a Medium Access Control (MAC) header of the first message.

41. The method of any of claims 25 to 40, wherein:the first wireless communication device comprises a reader or ambient-internet of things (A-loT) reader; and / orthe second wireless communication device comprises an ultra low power device, zero energy device or A-loT device.

42. A method (400) performed by a second wireless communication device for sending a message, the method comprising:sending (402) a first message to a first communication device,wherein the first message includes an indication of one or more of:- whether the first message is a segment of a second message;- whether the first message is a last segment of the second message;- whether a further message to be sent by the second communication device to the first communication device is a segment of the second message; - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.

43. The method of claim 42, wherein the first message includes an indication of the total size of the second message or of the payload of the second message if the first message comprises a segment of the second message that is not the last segment of the second message.

44. The method of claim 43, wherein the first message includes the indication of the total size of the second message or of the payload of the second message instead of an indication of a size of the first message or of a payload of the first message if the first message comprises a segment of the second message that is not the last segment of the second message.

45. The method of claim 44, wherein the indication of the total size of the second message is comprised in a field of the first message that, when the first message is the last segment of the second message, is not a segment of the second message, or is not a segmented message, is used for the indication of the size of the first message or of the payload of the first message.

46. The method of any of claims 42 to 45, wherein the first message comprises a first segment of the second message, and the method further comprises receiving one or more additional messages from the second wireless communication device, wherein each of theone or more additional messages comprises a segment of the second message, and each of the one or more additional messages does not include the indication of the total size of the second message or of the payload of the second message.

47. The method of any of claims 42 to 46, wherein the first message includes an indication of the remaining size of the second message or of the payload of the second message if the first message comprises a segment of the second message that is not the last segment of the second message.

48. The method of any of claims 42 to 47, wherein the first message includes an indication of the size of the first message or of the payload of the first message if the first message comprises a segment of the second message that is the last segment of the second message, or does not comprise a segment of the second message or is not a segmented message.

49. The method of any of claims 42 to 48, wherein, when the first message does not comprise a segment of the second message or is not a segmented message, the first message does not include the indication or includes an indication that the first message is now a segment of a second message.

50. The method of any of claims 42 to 49, comprising receiving, from the first wireless communication device, information including one or more of:an indication of whether the expected size of the second message is available at the first wireless communication device;an indication that the first message should include the indication of whether the first message is a segment of the second message;an indication that the first message should include the indication of the total size of the second message or of the payload of the second message and / or the remaining size of the second message or of the payload of the second message.

51. The method of claim 50, wherein:the first message includes the indication of whether the first message is a segment of the second message if an expected size of the second message is available at the first wireless communication device or if the indication that the first message should include the indication of whether the first message is a segment of the second message is received from the first network node; and / orthe first message includes the indication of the total size of the second message or of the payload of the second message and / or the remaining size of the second message or of the payload of the second message if the expected size of the second message is not available at the first wireless communication device or the indication that the first message should include the indication of the total size of the second message or of the payload of the second message and / or the remaining size of the second message or of the payload of the second message is received from the first network node.

52. The method of claim 50 or 51 , comprising sending the information to the second wireless communication device in a configuration and / or in a paging message to the second wireless communication device.

53. The method of any of claims 42 to 52, wherein:the first message comprises a Msg3 or Msg5, or a segment of a Msg3 or of a Msg5; and / orthe second message comprises a Msg3 or Msg5.

54. The method of any of claims 42 to 53, wherein the payload comprises a Protocol Data Unit (PDU), a Medium Access Control (MAC) PDU, and / or user data.

55. The method of any of claims 42 to 54, wherein the indication comprises or is included in one or more of:one or more bits in the first message;a field in a header of the first message;a length field in a header of the first message;a field in a Medium Access Control (MAC) header of the first message.

56. The method of any of claims 42 to 55, wherein:the first wireless communication device comprises a reader or ambient-internet of things (A-loT) reader; and / orthe second wireless communication device comprises an ultra low power device, zero energy device or A-loT device.

57. Apparatus in a first wireless communication device for determining whether a message comprises a plurality of message segments, the apparatus comprising processing circuitry and a memory, the apparatus configured to:receive (102) a first message from the second wireless communication device; andif the first message includes an indication, determine (104), based on the indication in the first message, whether a second message from the second wireless communication device comprises a plurality of message segments.

58. The apparatus of claim 57, wherein the apparatus is configured to perform the method (100) of any of claims 2 to 13.

59. Apparatus in a second wireless communication device for sending an indication in a message, the apparatus comprising processing circuitry and a memory, the apparatus configured to:send (202), to a first wireless communication device, a first message;wherein, if the second communication device should include an indication in the first message to the first wireless communication device that a second message from the second wireless communication device comprises a plurality of message segments, the first message includes the indication.

60. The apparatus of claim 59, wherein the apparatus is configured to perform the method (200) of any of claims 15 to 24.

61. Apparatus in a first wireless communication device for receiving a message, the apparatus comprising processing circuitry and a memory, the apparatus configured to: receive (302) a first message from a second communication device,wherein the first message includes an indication of one or more of:- whether the first message is a segment of a second message;- whether the first message is a last segment of the second message;- whether a further message to be sent by the second communication device to the first communication device is a segment of the second message; - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.

62. The apparatus of claim 61 , wherein the apparatus is configured to perform the method (300) of any of claims 26 to 41.

63. Apparatus in a second wireless communication device for sending a message, the apparatus comprising processing circuitry and a memory, the apparatus configured to: send (402) a first message to a first communication device,wherein the first message includes an indication of one or more of:- whether the first message is a segment of a second message;- whether the first message is a last segment of the second message;- whether a further message to be sent by the second communication device to the first communication device is a segment of the second message; - a total size of the second message or of a payload of the second message; - a remaining size of the second message or of the payload of the second message.

64. The apparatus of claim 63, wherein the apparatus is configured to perform the method (400) of any of claims 43 to 56.

Images