Second network node, device and methods therein in a communications network

Abstract

A method performed by a second network node is provided The method is for handling an identifier of a device in a communications network. The second network node receives (301) a first request message from a first network node, for the device. The second network node identifies (302) a device identifier, ID, type assigned to the device based on the first request message. The second network node then attaches the device ID type into a second request message. The second network node sends (303) the second request message and the identified device ID type to a third network node, to be delivered in a paging message towards the device. Thereby the device is enabled to use the device ID type as a basis for determining which action to proceed with.

Description

[0001] SECOND NETWORK NODE, DEVICE AND METHODS THEREIN IN A COMMUNICATIONS NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a second network node, a device and methods therein. Furthermore, a computer program and a carrier therefore, are also provided herein. In some aspects, they relate to handling an identifier of a device in a communications network.

[0004] BACKGROUND

[0005] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0006] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5G Core (5GC) is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5GC.

[0007] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0008] I RAN Technical Report

[0009] 3GPP TR 38.769 v2.0.0: “Study on solutions for Ambient (loT) in 3GPP NR Release 19” was agreed in RAN. Clause 6.3.3 specifies the identifiers to be used in A-IoT paging message.

[0010] 2.1.1.1 6.3.3 A-IoT paging

[0011] In A-IoT AS layer, the A-IoT paging functionality is to use A-IoT paging message to indicate device(s) that need to respond.

[0012] As to the A-IoT paging message, the identifier may be required to identify the device / group of devices in this trigger message (e.g., for the case of reaching a single or a group of devices). Following cases are studied:

[0013] - The A-IoT paging message containing an identifier of a single A-IoT device.

[0014] - The A-IoT paging message containing a group ID that maps to multiple A-IoT devices. - The A-IoT paging message that does not contain any identifier, i.e., indicating all A-IoT devices that can receive the A-IoT paging message need to respond.

[0015] - The A-IoT paging message containing multiple identifiers of A-IoT devices. The need for this use case is still to be confirmed / dependent according to the conclusion in 3GPP TR 23.700-13: "Study on Architecture support of Ambient power-enabled Internet of Things". From RAN2 perspective, it is feasible to support paging multiple identifiers of A-IoT devices, pending on TB size and multiplexing design of A-IoT paging message.

[0016] NOTE 1 : The details of the above identifier and group ID and also the use case / scenario are studied in 3GPP TR 23.700-13: "Study on Architecture support of Ambient power-enabled Internet of Things".As to the A-IoT paging message, it can additionally indicate the information from which the device(s) can determine the resource(s) to be used for D2R response message(s). It can be further considered on more details for the discussion in clause 6.1.

[0017] For A-IoT device paging functionality, it is understood that the legacy paging message, legacy paging occasion and legacy DRX from NR are not supported (See TS 38.300

[0153] for references for any legacy NR functionality). From RAN2 perspective, it is assumed that the A-IoT device can receive as long as there is enough.

[0018] It is supported that the reader can send multiple (subsequent) A-IoT paging messages that are associated with the same service request from the CN. A reader when used herein e.g. means a node performing A-IoT communication with A-IoT device(s). The duplicated response from devices for the same service request should be avoided. The A-IoT paging message may include information to avoid this duplicated response from the device to a reader. It needs to be further discussed on how to design this information in A-IoT paging message (e.g., including stage-3 details and considering the related aspects from other WGs). Then, based on this information, the device determines whether to skip sending the response to A-IoT paging message or not (if the device had successfully responded to the same service before). This information should be short and simple. This information is one ID, while it needs to be further discussed whether the ID is generated by the reader or by the core network. It needs to be further discussed on the size of this information.

[0019] It needs to be further discussed for the scenario that different readers may send A-IoT paging messages, which are associated with the same service request from the CN, to the same device for response. If this scenario is in the scope, it needs to be further discussed, by considering the progress from all the WGs.

[0020] It needs to be further discussed on whether other information is included in A-IoT paging message to indicate service type / command type or to indicate whether there will be subsequent messages.

[0021] 2.1.2 SA3 Reply LS

[0022] S2-2501384: “Reply LS on security Aspect of Ambient loT” was received in 3GPP SA2 167. In the reply LS, it was mentioned that SA3 has agreed the conclusion of KI#3 as in S3-251048.

[0023] SA WG2 Meeting S2-167 S2-2501384

[0024] 17 - 21 February, 2025, Athens, Greece3GPP TSG-SA3 Meeting #120 S3-251055

[0025] Athens, Greece, 17 -21 February 2025

[0026] Title: Reply LS on security aspects of Ambient loT

[0027] Response to: LS S2-2411049 on security aspects of Ambient loT from SA2 Release: Release 19

[0028] Work Item: FS AmbientloT

[0029] Source: SA3

[0030] To: SA2

[0031] Cc: RAN2

[0032] Contact person: Lihui Xiong

[0033] xionglihui@oppo.com

[0034] Send any reply LS to: 3 GPP Liaisons Coordinator, mailto : 3 GPPLiai son@etsi . org

[0035] Attachments: (Attach S3-251048)

[0036] Overall description

[0037] SA3 would like to thank SA2 for the LS on security aspects of Ambient loT (AIoT).

[0038] SA3 has drawn a set of preliminary conclusions regarding protection of AIoT device identifier as attached.

[0039] SA3 will keep SA2 informed about further progress.

[0040] 2 Actions

[0041] To SA2

[0042] ACTION:

[0043] SA3 kindly asks SA2 to take the above information into consideration.

[0044] 3 Dates of next TSG SA WG 3 meetings

[0045] SA3#121 07 - 11 April 2025 Goteborg, Sweden SA3#122 19 - 23 May 2025 Fukuoka, Japan

[0046] 2.1.3 SA3 KI#3 Conclusion

[0047] In S3 -251058: “Conclusion on KI#3”, it specified that the protection of Ambient device ID on the usage of temporary ID shall be supported.7.3 Conclusion on KI#3

[0048] The following aspects and principles are agreed for the conclusion on KI#3

[0049] - A mechanism to protect AIoT device ID based on the use of temporary ID shall be supported.

[0050] - Mechanism shall allow unambiguous identification of the AIoT device

[0051] - A mechanism to re-synchronize de-synchronized temporary IDs shall be supported.

[0052] Editor’s Note: Additional conclusions on solution are For Further Study (FFS).

[0053] 2.1.4 SA2 Draft Technical Specification

[0054] 3GPP TS 23.xyz v0.2.0: “Architecture support for Ambient power-enabled Internet of Things; Stage 2 (Release 19)” was agreed in 3GPP SA2 167.

[0055] Within the draft TS, the inventory procedure was agreed and included.

[0056] Inventory Procedure

[0057] Figures la and b describe the inventory procedure.

[0058] 1. The Application Function (AF) invokes Nnef AIoT Inventory (AF ID, [Target area information], [AIoT Device ID identification information], [Approximate number of AIoT Devices]) service operation request to the Network Exposure Function (NEF).

[0059] Editor's note: The parameters for the inventory service operation need further definition. 2. The NEF selects the AIoT Function (AIOTF) to handle the request.

[0060] Editor's note: How the NEF selects the AIOTF needs further definition.

[0061] 3. The NEF invokes the Naiotf_AIoT_Inventory(AF ID, [Target area information], [AIoT Device ID identification information], [Approximate number of AIoT Devices]) service operation towards to the selected AIOTF.

[0062] 4. The AIOTF receives the AIoT service operation request and checks the parameters included in the request. If the AIoT service operation request cannot be processed, the AIOTF rejects the AIoT service operation request with an appropriate cause code, and step 7 onwards are skipped.

[0063] The AIOTF generates a correlation ID corresponding to this AF service operation request, as well as the AIoT Device Identification information to be included in the paging message sent by AIoT RAN.

[0064] AIOTF performs Reader Selection, see clause 5.3.The AIOTF may also use the last serving Reader to assist with determining which Readers to use for an AFs request targeting for a specific AIoT Device.

[0065] The AIOTF determines assistance information as described in clause 5.4.

[0066] Editor's note: The authorisation split between the NEF and AIOTF needs alignment with the other clauses in this TS.

[0067] 5. AIOTF sends the AIoT Inventory Service Response to the NEF containing the accept or reject result for the AIoT Inventory service operation request based on step 4.

[0068] 6. NEF sends the AIoT service operation response to the AF, containing the accept or reject result for the AIoT Inventory service operation request as specified in clause 8.3.

[0069] 7. The AIOTF sends the Inventory Request message including the correlation ID, the AIoT Device Identification information to be included in the paging message, and assistance information to the selected AIoT RAN.

[0070] Editor's note: AIoT Device Identification information needs further definition.

[0071] Editor's note: Whether the Inventory Request sent to AIoT RAN includes indication about whether there will be a follow up command or not needs to be determined.

[0072] 8. The AIoT RAN sends an Inventory Response to the AIOTF with the correlation ID indicating that the Inventory Request is received successfully and will perform the service operation accordingly.

[0073] 9. Upon reception of the Inventory Request message from the AIOTF, the AIoT Reader(s) will execute the inventory operation.

[0074] If an AIoT device matches the AIoT Device Identification information in the paging message, the AIoT Device responds to the paging message and sends an AIOT Non-Access Stratum (NAS) message that includes its AIoT Device ID.

[0075] Editor's note: Whether and how the Device ID is concealed or encrypted will be determined and aligned with SA WG3.

[0076] 10. AIoT RAN sends one or more Inventory Report messages to the AIOTF including the correlation ID, Reader ID and the AIOT NAS message(s) from the AIoT Device(s).

[0077] 11. The AIOTF validates the results, using local stored device information or device profile data retrieved from the Application Data Management (ADM). The AIOTF may aggregate the results.

[0078] 12. The AIOTF reports the progress of the AIoT inventory request to the NEF by sending the AIoT Notify message including a list of AIoT Device ID(s).

[0079] Editor's note: Whether only one, or more than one report is generated by the AIOTF to send to the AF needs clarification.13. The NEF informs the AF of the outcome of the AIoT Inventory request by sending the AIoT Notify message including the AIoT Device ID(s).

[0080] SUMMARY

[0081] An object of embodiments herein is e.g. to improve the way of handling the type of the device identifier in a wireless communications network.

[0082] According to an aspect of embodiments herein, the object is achieved by a method performed by a second network node. The method is for handling an identifier of a device in a communications network. The second network node receives a first request message from a first network node, for the device. The second network node identifies a device identifier, ID, type assigned to the device based on the first request message. _The device ID type may be anyone out of a temporary device ID, a permanent device ID, a group ID. The second network node then attaches the device ID type into a second request message. The second network node sends the second request message and the identified device ID type to a network node, to be delivered in a paging message towards the device. Thereby the device is enabled to use the device ID type as a basis for determining which action to proceed with.

[0083] According to another aspect of embodiments herein, the object is achieved by a method performed by a device. The method is for handling an identifier of the device in a communications network. The device receives a paging message and a device identifier, ID, type assigned to the device from a network node. The device determines whether the device ID type assigned to itself is a temporary device ID, a permanent device ID, or a group ID. Based on the determined device ID type, the device then determines which action to proceed with.

[0084] According to another aspect of embodiments herein, the object is achieved by a second network node configured to handle an identifier of a device in a communications network. The second network node is further configured further configured to perform any one or more out of:

[0085] - Receive a first request message from a first network node, for the device,

[0086] - Identify a device identifier, ID, type assigned to the device based on the first request message and attach the device ID type into a second request message,

[0087] - Send to a third network node the second request message and the identified device ID type, to be delivered in a paging message towards the device, thereby enabling the device to use the device ID type as a basis for determining which action to proceed with.

[0088] According to another aspect of embodiments herein, the object is achieved by a device configured to handle an identifier of a device in a communications network. The device is further configured to perform any one or more out of:- Receive a paging message and a device identifier, ID, type assigned to the device from a third network node.

[0089] - Determine whether the device ID type assigned to the device is a temporary device ID, a permanent device ID, or a group ID,

[0090] -Based on the determined device ID type, determine which action to proceed with.

[0091] Embodiments herein may provide one or more of the following advantages:

[0092] This solution enables the Ambient loT devices to understand the type of the identifier for inventory, so that it is enabled check its identifiers stored in Non-Volatile Memory (NVM) directly, without blindly try one by one. It reduces unnecessary energy waste in the device.

[0093] BRIEF DESCRIPTION OF THE DRAWINGS

[0094] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0095] Figures la and b are sequence diagrams illustrating prior art.

[0096] Figure 2 is a schematic block diagram illustrating embodiments of a communications network.

[0097] Figure 3 is a flowchart depicting an embodiment of a method in a second network node.

[0098] Figure 4 is a flowchart depicting an embodiment of a method in a device.

[0099] Figures 5 a and b are sequence diagrams depicting an example embodiment of a method herein.

[0100] Figure 6 a and b are sequence diagrams depicting an example embodiment of a method herein.

[0101] Figure 7 is a schematic block diagram of embodiments of a second network node.

[0102] Figure 8 is a schematic block diagram of embodiments of a device.

[0103] Figure 9 schematically illustrates embodiments of a communication system.

[0104] Figure 10 is a generalized block diagram of embodiments of a UE.

[0105] Figure 11 is a generalized block diagram of embodiments of a network node.

[0106] Figure 12 is a generalized block diagram of embodiments of a virtualization environment.

[0107] DETAILED DESCRIPTION

[0108] As part of developing embodiments herein, the inventors identified some problems that first will be described.

[0109] According to 3GPP RAN’s TR (TR 38.769), the identifier in A-IoT paging can be an identifier of a single A-IoT device, a group ID that maps to multiple A-IoT devices, multiple identifiers, or no identifier.

[0110] According to SA3’s reply LS and KI#3 conclusion, the temporary identifier of Ambient loT device shall be supported for security and privacy reason. This would affect the A-IoT procedures, e.g., inventory / paging procedure.It means, to identify an individual A-IoT device, the identifier can be a temporary identifier of the device or the permanent ID of the device.

[0111] When receiving an A-IoT paging for inventory, the A-IoT device needs to monitor its identifier over the A-IoT air interface. Depending on different identifier type, it may need to take different actions:

[0112] - When a temporary identifier is used, it needs to check whether the received temporary identifier in the paging message matches the temporary identifier stored in the Non-Volatile Memory (NVM) (e.g., the memory bank designed for temporary identifier and other parameters). Usually, the temporary identifier does not need to be encrypted (it can be encrypted as well).

[0113] - When (part or whole) permanent device identifier is used, it needs to first check if it can decrypt the received identifier and possibly check whether the decrypted identifier matches (the specified part or whole) permanent device identifier stored in the NVM (e.g., the memory bank stored the permanent device ID)

[0114] Ambient loT devices are characterized as devices with low complexity, low data rate, small size, energy harvesting, low capabilities and low power consumption. Without knowing the type of the identifier, the device can only blindly try one by one, which is not efficient for the device. It will waste the energy in the device unnecessarily as well.

[0115] Therefore, it is necessary to develop the solutions on how to signal the device ID type to the devices. In addition, it maybe also beneficial to let the reader to know the ID type. It is necessary to develop the solutions on how to signal the ID type to the reader.

[0116] An object of embodiments herein is e.g. to improve the way of handling the type of the device identifier in a wireless communications network.

[0117] Embodiments herein provide a number of options, such as e.g. two options, to indicate a device identifier (ID) type on whether the device ID is a temporary device ID or a permanent device ID or a group ID. E.g. a permanent device ID with mask bits which target a group of devices.

[0118] - Option 1: The device ID type is introduced in NAS layer by a second network node, e.g. an Ambient Internet Of Things Function (AIOTF), in a communications network such as e.g. a Core Network. It may be an explicit indicator (i.e., an additional parameter) or an implicit indicator (e.g., depending on the presence of the encryption parameter or the length field).

[0119] - Option 2: The device ID type is indicated in AS layer by a reader in a network node, e.g., a reader in an A-IoT capable NG-RAN (AIoT RAN). It may be realized in form of a field in A-loT paging message e.g., identifier type or identifier length or as part of message header, preamble, flags or control / Ll / L2 information in or associated with paging message. In this option, thenetwork node, such as the AIoT RAN, obtains explicitly device ID type from the communications network, such as the CN, e.g., directly from the AIOTF over Next Generation Application Protocol (NGAP) or indirectly via the Access and Mobility Management Function (AMF), or the network node such as the AIoT RAN, determines ID type based on the device ID information received from CN (e.g., device identifier length, whether the mask is included, whether (part or whole) permanent device ID is used with or without encryption, etc.).

[0120] When the presence of an encryption parameter is used as an implicit indicator, if the encryption parameter is present, assuming the device ID is not a temporary identifier. Otherwise, assuming the device identifier is a temporary identifier. It assumes that the temporary identifier will never be encrypted while all other identifiers will always be encrypted, which may be a limitation of this option.

[0121] When the length field is used as the implicit indicator, it assumes that temporary identifier will be a fixed length, while other identifiers should try to avoid being encoded with such length, which also brings some limitation.

[0122] In explicit indicator case, there’s no such limitation. The ID type is not coupled with the encryption of the identifier or the length of the identifier.

[0123] Embodiments herein describe a method for network node, e.g. gNB based readers (i.e., topology 1). However, it applies to intermediate-UE based methods (i.e., topology 2) as well. For an intermediate-UE based method, (in this case the network node is a UE) the network node, e.g., AIOTF, delivers the device ID type towards UE readers via the NAS signals, or user-plane packets, or via gNB Radio Resource Control (RRC) signals (in this option, the AIOTF delivers the device identifier type towards gNB directly over NGAP or via the AMF indirectly). The UE readers may deliver the device identifier type towards the AIoT devices. For option 1, the UE reader transparently delivers the NAS content towards the device. For option 2, the UE reader performs the same operations as the readers in the network node, e.g., the gNB.

[0124] In examples of embodiments herein, for an inventory request, also referred to as a first request message, introduce an ID type indicator from a second network function such as the AIoTF (e.g. in CN) or reader (in NG-RAN / AIoT RAN) towards the Ambient loT devices. The device may then take proper action based on the indicator:

[0125] - If the identifier is a temporary identifier, the device check with the NVM where stores the temporary identifier directly.

[0126] - If the identifier is a permanent device ID or a group ID (can be represented by device ID with MASK bits), the device check with the NVM where stores the permanent device ID.This method enables the device, such as the Ambient loT devices to understand the type of the ID for inventory, so that it can check its identifiers stored in NVM directly, without blindly try one by one. It reduces unnecessary energy waste in the device.

[0127] Figure 2 is a schematic overview depicting a communications network 100 wherein embodiments herein may be implemented. The communications network 100 comprises one or more RANs, and one or more CNs. The communications network 100 may use 5G NR but may further use a number of other different technologies, such as, 6G, Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSMZEDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0128] Network nodes such as a third network node 110 operate in the RAN the communications network 100. The third network node 110 provides one or more cells such as a first cell 11. The third network node 110 may be a transmission and reception point e.g. a radio access network node such as a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), an NR Node B (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, or any other network unit capable of communicating with UEs, such as a UE 121, within the first cell 11, served by the third network node 110. The third network node 110 may be referred to as a serving radio network node and communicates with the UE 121 with Downlink (DL) transmissions to the UE 121 and Uplink (UL) transmissions from the UE 121. The third network node 110 may in some embodiments be a UE, e.g. an intermediate-UE. The third network node 110 may e.g. be an AIoT RAN. It should be noted that in embodiments herein, ‘third network node 110, ‘ AIoT RAN’, ‘ AIoT RAN’ reader, and ‘third network node reader are used interchangeably without losing the meaning.

[0129] Network nodes, such as a first network node 131, and a second network node 132 operate in the communications network 100. The first network node 131 may e.g. comprise an AF. It should be noted that in embodiments herein, ‘first network node 131, and ‘AF network node’ are used interchangeably without losing the meaning. The second network node 132, may e.g. comprise an AIOTF. It should be noted that in embodiments herein, ‘second network node 132, and ‘AIOTF’ are used interchangeably without losing the meaning.

[0130] One or more devices operate in the communication network 100, such as e.g. the device 120.

[0131] The device 120 may be an AIoT device. The device 120 may e.g. be a remote UE, a wirelessdevice, an NR device, a mobile station, a wireless terminal, an NB-IoT device, an MTC device, an eMTC device, a CAT-M device, a WiFi device, an LTE device and an a non-access point (non-AP) STA, a STA, that communicates via a base station such as e.g. a network node 110, one or more Access Networks (AN), e.g. a RAN, to one or more core network (CN) nodes, in one or more CNs, one or more IMS network nodes. The device 120 may communicate with one or more CN nodes, and / or IMS network nodes, such as the network node 130. It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, client, mobile client, IMS client, wireless communication terminal, user equipment, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a car or any small base station communicating within a cell.

[0132] Methods according to embodiments herein are performed in the second network node 132 and / or the device 120. These nodes may be, e.g. partly, Distributed Nodes (DN)s and functionality, e.g. comprised in a cloud 170 as shown in Figure 2.

[0133] A number of embodiments will now be described, some of which may be seen as alternatives, while some may be used in combination.

[0134] A method according to embodiments will first be described as seen from the view of the second network node 132 together with Figure 3, and then as seen from the view of the device 120 together with Figure 4.

[0135] Figure 3 shows example embodiments of a method performed by the second network node 132, e.g. an AIOTF. The method is for handling an identifier of the device 120, e.g. an AIoT device, in the communications network 100. The method comprises the following actions, which actions may be taken in any suitable order.

[0136] Action 301: The second network node 132 receives a first request message from the first network node 131. The first request message is for the device 120 and may e.g. be a the AIoT service operation request.

[0137] Action 302: The second network node 132 identifies a device ID type assigned to the device 120 based on the first request message. The device ID type may be anyone out of a temporary device ID, a permanent device ID, a group ID. The second network node 132 attaches the device ID type, such as e.g. a parameter or indication of the device ID type, e.g., explicit or implicit, into a second request message.

[0138] Action 303: The second network node 132 sends the second request message and the identified device ID type to the third network node 110, also referred to as an A-IoT RAN node, which e.g. may be an A-IoT reader or in charge of A-IoT reader(s). The identified device ID type is to be delivered in a paging message, e.g., by the A-IoT reader, towards the device 120. Thedevice ID type, also referred to as ID type info, may e.g., be either comprised in or outside of the request message. The device ID type enables the device 120 to use the device ID type as a basis for determining which action to proceed with.

[0139] Figure 4 shows example embodiments of a method performed by the device 120, e.g., an AIoT device. The method is for handling an ID of the device 120, in the communications network 100. The method comprises the following actions, which actions may be taken in any suitable order.

[0140] Action 401: The device 120 receives a paging message and a device ID type assigned to the device from a network node 110, such as e.g., an AIoT RAN reader. The paging message comprises the device ID type. The device ID type may e.g. be represented by a parameter or indication of the device ID type. It may e.g. be e.g., explicit or implicit indicated.

[0141] Action 402: The device 120 determines whether the device ID type assigned to itself is a temporary device ID, a permanent device ID, or a group ID.

[0142] Action 403: Based on the determined device ID type, the device 120 determines which action to proceed with.

[0143] In some embodiments, the determining which action to proceed with further comprises: - when the device ID type is, e.g. indicates, a temporary ID, checking whether the temporary ID in the paging message matches a temporary ID stored in a memory such as e.g., a Non-Volatile Memory, NVM.

[0144] - when the device ID type is, e.g. indicates, a permanent ID, checking whether the permanent ID in the paging message matches a permanent ID stored in a memory such as e.g., an NVM.

[0145] - when the device ID type is, e.g. indicates, a group ID, e.g., a device ID with MASK information included, checking whether the device ID with applied MASK information matches, or at least partly matches, corresponding part of a permanent device ID of the device 120 stored in a memory, such as e.g., an NVM.

[0146] In below embodiments, it has been considered or assumed that the device 120 in example use cases is represented by an ultra-low power device, and zero-energy or A-IoT device.

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

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

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

[0150] In embodiments herein, ‘A-IoT UE’, ‘A-IoT device’, ‘device’, or ‘UE’ are used interchangeably without losing the meaning.

[0151] In embodiments herein, ‘intermediate node’, ‘intermediate UE’, ‘UE reader’ are applied interchangeably without losing the meaning.

[0152] In embodiments herein, a reader may be gNB based (i.e. reader inside gNB), or intermediate-UE based (i.e. UE reader).

[0153] NAS Option.

[0154] Figures 5 a and b show an example of the NAS Option according to some embodiments herein. The underlined text relates to examples of the NAS option actions according to embodiments herein. In the examples of Figures 5 a and b, the device 120 is represented by an AIoT device, the third network node 110 is represented by an AIoT RAN (readers), the second network node 132 is represented by a AIOTF, and the first network node 131 is represented by an AF.

[0155] 1. The AF invokes Nnef AIoT Inventory (AF ID, [Target area information], [AIoT Device ID identification information], [Approximate number of AIoT Devices]) service operation request to the NEF.

[0156] 2. The NEF selects the AIOTF to handle the request.3. The NEF invokes the Naiotf_AIoT_Inventory(AF ID, [Target area information], [AIoT Device ID identification information], [Approximate number of AIoT Devices]) service operation towards to the selected AIOTF, also referred to as the second network node 132.

[0157] 4. The AIOTF e.g. the second network node 132, receives the AIoT service operation request, also referred to as in the first request message. This relates and may be combined with Action 301 described above. The AIOTF e.g. the second network node 132, identifies, e.g. checks, the parameters included in the request. This relates and may be combined with to Action 302 described above. If the AIoT service operation request cannot be processed, the AIOTF rejects the AIoT service operation request with an appropriate cause code, and step 7 onwards are skipped.

[0158] The AIOTF generates a correlation ID corresponding to this AF service operation request, as well as the AIoT Device Identification information to be included in the paging message sent by AIoT RAN.

[0159] AIOTF performs Reader Selection, see above.

[0160] The AIOTF may also use the last serving Reader to assist with determining which Readers to use for an AFs request targeting for a specific AIoT Device.

[0161] The AIOTF determines assistance information as described above.

[0162] 5. AIOTF sends the AIoT Inventory Service Response to the NEF containing the accept or reject result for the AIoT Inventory service operation request based on step 4.

[0163] 6. NEF sends the AIoT service operation response to the AF, containing the accept or reject result for the AIoT Inventory service operation request.

[0164] 7. This relates to and may be combined with Actions 302303 and 401 described above. The AIOTF checks, e.g. identitfies, and includes, e.g. attaches, the device ID type in the second request message, e.g. in the AIoT Device ID identity information, which is going to be delivered to the device 120 in A-IoT paging:

[0165] - If the AIoT Device ID identification information contains one or several individual AIoT permanent Device IDs, the AIOTF checks whether the temporary identifiers have been allocated for those devices. For those devices with temporary identifiers, their temporary identifiers will be used as device IDs in A-IoT paging, and device identifier type for those IDs should be set to the type value indicating temporary ID is used. Otherwise, permanent device IDs will be used as device IDs, and device identifier type for those IDs should be set to the type value indicating permanent Ids are used.

[0166] - If the AIoT Device ID identification information contains a group identifier (e.g., device ID with MASK information included), the device identifier type should be set to the type value indicating group ID is used.The AIOTF may encrypt the content of the whole AIoT Device ID identification information including the device identifier type parameters, or encrypt the content of each AIoT Device IDs individually including or not including the device identifier type, or only encrypt the AIoT Device IDs which are not temporary identifiers including or not including the device identifier type. This relates to and may be combined with Actions 402 and 403 described above.

[0167] * Encryption of permanent device ID may be performed using device specific security key (pre-shared key) with or without a freshness parameter. If the freshness parameter is used, CN may also include this parameter in the A-IoT paging.

[0168] As an alternative option, the device ID type parameter may not be present explicitly. In this case, it will be coupled with the security information / encryption parameters to be delivered from the AIOTF to the device. If the security information / encryption parameters are included, the device identifier type is not temporary identifier, i.e., permanent ID or group ID if group identifier applies encryption. Otherwise, it is temporary identifier.

[0169] It may also be coupled with the length field indicating the length of the device identifier. If the length of the device identifier matches the temporary identifier length, it is a temporary identifier. Otherwise, it may be a permanent device identifier or group identifier.

[0170] 8. The AIOTF e.g. the second network node 132, sends the Inventory Request message, also referred to as the second request message, including the correlation ID, the AIoT Device Identification information to be included in the paging message, and assistance information to the selected the third network node 110, e.g., the AIoT RAN (NG-RAN with AIoT capabilities). The device ID type, e.g. the device ID type parameter, is included within the second request message, e.g., in the AIoT Device Identification information. This relates and may be combined with to Action 303 described above.

[0171] 9. The AIoT RAN sends an Inventory Response to the AIOTF with the correlation ID indicating that the Inventory Request is received successfully and will perform the service operation accordingly.

[0172] 10. This relates to and may be combined with Action 401 described above. Upon reception of the Inventory Request message from the AIOTF, the AIoT Reader(s) will execute the inventory operation. The reader performs AIoT paging with the AIoT Device Identification information.

[0173] Within the AIoT Device Identification information, the device identifier type parameter is included.

[0174] 11. This relates to and may be combined with Action 402 described above. The device 120, e.g., the AIoT device, may need to perform decryption if the device IDs are encrypted by the AIOTF. The device 120, determined whether the device ID type assigned to the device 120 is atemporary device ID, a permanent device ID, or a group ID. E.g., the AIoT device, checks the device ID type, e.g., the device ID type parameter, to determine whether its device ID matches:

[0175] - If the device identifier type indicating temporary ID, it checks whether the ID in A-IoT paging matches the temporary ID stored in NVM.

[0176] - If the device identifier type indicating permanent ID, it checks whether the ID in A-IoT paging matches the permanent ID stored in NVM,

[0177] -If the device identifier type indicating group ID, it checks whether the device ID with MASK information matches the permanent ID stored in NVM, In this case, it does not require a full match. Once the masked bits match, it will be regarded as matched.

[0178] In the alternative option, if the device 120 may need to decrypt the device ID, it checks whether the decrypted ID type matches its permanent device ID stored in NVM, Otherwise, it checks whether the decrypted ID type matches the temporary identifier stored in NVM, The device 120 may also determine based on the length of the device identifier. If the length matches the temporary identifier length, it further checks whether it matches the temporary identifier stored in NVM, Otherwise, it checks the permanent device ID stored in the NVM,

[0179] If an AIoT device matches the AIoT Device Identification information in the paging message, the AIoT Device responds to the paging message and sends an AIOT NAS message that includes its AIoT Device ID.

[0180] 12. AIoT RAN sends one or more Inventory Report messages to the AIOTF including the correlation ID, Reader ID and the AIOT NAS message(s) from the AIoT Device(s).

[0181] 13. The AIOTF validates the results, using local stored device information or device profile data retrieved from the ADM. The AIOTF may aggregate the results.

[0182] 14. The AIOTF reports the progress of the AIoT inventory request to the NEF by sending the AIoT Notify message including a list of AIoT Device ID(s).

[0183] 15. The NEF informs the AF of the outcome of the AIoT Inventory request by sending the AIoT Notify message including the AIoT Device ID(s).

[0184] In step 8, the AIOTF, e.g. the second network node 132, may need to communicate with the AIoT RAN via the AMF. In this case, the AIOTF sends Namf AIoT MessageDelivery (AIoT RAN ID, Inventory Request (correlation identifier, AIoT Device Identification information)) to the AMF. And the AMF sends the Inventory Request to the AIoT RAN. Within AIoT Device Identification information, the field of device ID type is included.

[0185] It may also be applied to command procedure, as the AIOTF triggers inventory firstly and then deliver the command towards those responded / identified devices. Within the inventory request towards AIoT RAN and A-IoT paging, the field of device identifier type may be included in the AIoT Device Identification information.AS Option

[0186] Figures 6a and b show an example of the AS Option. The underlined text relates to examples of the AS option actions according to embodiments herein. In the examples of Figures 6 a and b, the device 120 is represented by an AIoT device, the third network node 110 is represented by an AIoT RAN (readers), the second network node 132 is represented by a AIOTF, and the first network node 131 is represented by an AF.

[0187] 1. The AF invokes Nnef_AIoT_Inventory(AF ID, [Target area information], [AIoT Device ID identification information], [Approximate number of AIoT Devices]) service operation request to the NEF.

[0188] 2. The NEF selects the AIOTF to handle the request.

[0189] 3. The NEF invokes the Naiotf AIoT Inventory (AF ID, [Target area information], [AIoT Device ID identification information], [Approximate number of AIoT Devices]) service operation towards to the selected AIOTF.

[0190] 4. The AIOTF receives the AIoT service operation request and checks the parameters included in the request. If the AIoT service operation request cannot be processed, the AIOTF rejects the AIoT service operation request with an appropriate cause code, and step 7 onwards are skipped.

[0191] The AIOTF generates a correlation ID corresponding to this AF service operation request, as well as the AIoT Device Identification information to be included in the paging message sent by AIoT RAN.

[0192] AIOTF performs Reader Selection, see text above.

[0193] The AIOTF may also use the last serving Reader to assist with determining which Readers to use for an AFs request targeting for a specific AIoT Device.

[0194] The AIOTF determines assistance information as described in clause 5.4.

[0195] 5. AIOTF sends the AIoT Inventory Service Response to the NEF containing the accept or reject result for the AIoT Inventory service operation request based on step 4.

[0196] 6. NEF sends the AIoT service operation response to the AF, containing the accept or reject result for the AIoT Inventory service operation request.

[0197] 7. This relates to and may be combined with Actions 302, and 302 described above. The AIOTF such as the second network node 132, checks and include the device ID type into the second request message, e.g. in the AIoT Device ID identity information, which is going to be delivered in A-IoT paging:

[0198] - If the second request message, e.g. the AIoT Device ID identification information contains one or several individual AIoT permanent Device IDs, the AIOTF check whether the temporary identifiers have been allocated for those devices. For those devices with temporary identifiers.their temporary identifiers will be used as device IDs in A-IoT paging, and device identifier type for those IDs should be set to the type value indicating temporary Ids are used. Otherwise, permanent device IDs will be used as device IDs, and device identifier type for those IDs should be set to the type value indicating permanent Ids are used.

[0199] - If the AIoT Device ID identification information contains a group identifier (e.g., device ID with MASK information included), the device identifier type should be set to the type value indicating group ID is used.

[0200] The AIOTF such as the second network node 132 may encrypt the content of the whole AIoT Device ID identification information, or encrypt the content of each AIoT Device IDs individually, or only encrypt the AIoT Device IDs which are not temporary identifiers.

[0201] 8. This relates to and may be combined with Action 303 described above The AIOTF such as the second network node 132, sends the second request message, e.g. the Inventory Request message including the correlation ID, the device identifier type, the AIoT Device Identification information to be included in the paging message, and assistance information to the selected AIoT RAN (NG-RAN with AIoT capabilities).

[0202] a. The AIOTF such as the second network node 132, may send the length of device ID and / or the device identifier type to the AIoT RAN. This is because the device ID field in A-IoT paging may be variable (mask / filter and encrypted part of permanent device ID are dynamic), i.e., RAN / reader needs to indicate the device(s) the length of the identifier. In addition, the size of device identifier may be different for the considered cases. For example, temporary ID may have a constant size (e.g., 64 bits), whereas the permanent device ID size may be variable (e.g., at least 96 bits), and the mask / filter may include memory address information, e.g., starting address in memory, mask length, mask value.

[0203] b. In one example, the AIOTF such as the second network node 132, sends only the information of the length of device identifier (i.e., without type information) to the RAN / reader and RAN may then generate an A-IoT paging message so that targeted device(s) may implicitly know what type of device ID to proceed, e.g., by means of a length field in the paging message. In this case, the indication is implicit from the format of the paging message.

[0204] 9. The AIoT RAN sends an Inventory Response to the AIOTF with the correlation ID indicating that the Inventory Request is received successfully and will perform the service operation accordingly.

[0205] 10. Upon reception of the Inventory Request message from the AIOTF, the AIoT Reader(s) will execute the inventory operation. The reader performs AIoT paging with the AIoT Device Identification information. Besides the AIoT Device Identification information in the paging message, the third network node 110 such as its reader may explicitly include a device identifiertype field and / or the length field in the A-IoT paging. In addition, if the AS ID of the device is available, the RAN / reader may use device AS ID in the A-IoT paging. Note that the length of AS ID is typical shorter than that of upper layer identifier.

[0206] 11. This relates to and may be combined with Actions 401, 402 and 403 described above.

[0207] The device 120, e.g., the AIoT device, may need to perform decryption if the device IDs are encrypted by the AIOTF. The AIoT device checks the device identifier type and / or length field in the received A-IoT paging message to determine how to proceed:

[0208] - If the device identifier type and / or length indicating temporary ID, the device checks whether the ID in A-IoT paging matches its temporary identifier stored in NVM.

[0209] - If the device identifier type and / or length indicating permanent ID, the device checks whether the ID in A-IoT paging (after decryption if needed) matches its corresponding (part or whole) permanent device ID stored in NVM,

[0210] - If the device identifier type and / or length indicating group ID, the device checks whether the device ID with applied MASK information matches corresponding part of its permanent device ID stored in NVM, In this case, the check does not have to be a full match. Once the masked bits match, it will be regarded as matched.

[0211] If an AIoT device matches the AIoT Device Identification information in the paging message, the AIoT Device responds to the paging message and sends an AIOT NAS message that includes its AIoT Device ID.

[0212] 12. AIoT RAN sends one or more Inventory Report messages to the AIOTF including the correlation ID, Reader ID and the AIOT NAS message(s) from the AIoT Device(s).

[0213] 13. The AIOTF validates the results, using local stored device information or device profile data retrieved from the ADM. The AIOTF may aggregate the results.

[0214] 14. The AIOTF reports the progress of the AIoT inventory request to the NEF by sending the AIoT Notify message including a list of AIoT Device ID(s).

[0215] 15. The NEF informs the AF of the outcome of the AIoT Inventory request by sending the AIoT Notify message including the AIoT Device ID(s).

[0216] In step 8, the AIOTF such as the second network node 132,_may need to communicate with the third network node 110, e.g., the AIoT RAN via the AMF. In this case, the AIOTF sends Namf AIoT MessageDelivery (AIoT RAN ID, Inventory Request (correlation identifier, AIoT Device Identification information)) to the AMF. And the AMF sends the Inventory Request to the AIoT RAN. Within Inventory Request message, the parameter of device identifier type is included.

[0217] It may also be applied to a command procedure, as the AIOTF such as the second network node 132, triggers inventory firstly and then deliver the command towards those responded devices, such as the device 120, e.g., the AIoT device. Within the inventory request towards AIoTRAN and A-IoT paging, the parameter of device identifier type is included in the AIoT Device Identification information.

[0218] In step 8, after the RAN node (e.g., the network node 110, such as the gNB operating as a reader) receives the device ID type and the corresponding ID for a device 120from the CN, the RAN node may use the information for one of the below use case / purposes.

[0219] 1) The RAN node maintains a mapping between device IDs (permanent ID or temporary ID) and AS IDs.

[0220] The mapping information may be triggered to update concerning a device when one of the below conditions is met

[0221] * AS ID is newly assigned to the device.

[0222] * AS ID is inactivated or expired for the device.

[0223] * AS ID is updated for the device.

[0224] * Temporary ID is newly assigned to the device.

[0225] * Temporary ID is inactivated or expired for the device.

[0226] * Temporary ID is updated for the device

[0227] 2) The RAN node may determine whether to apply a filter / mask towards a device or devices according to the ID type.

[0228] a. In an example, the RAN node may determine to apply a filter / mask towards permanent device IDs.

[0229] b. In an example, the RAN node may determine to not apply a filter / mask towards temporary device IDs.

[0230] The filter and / or mask may be determined by the third network node 110 such as the RAN node. In one option, the Inventory Request message sent by AIOTF includes multiple AIoT Device identification information fields where each field includes AIoT Device identification information of a specific device identifier type, the field is empty if there is no corresponding AIoT Device identification information. Based on the received AIoT Device identification information, the RAN node puts the AIoT Device Identifiers and adds the device identifier type parameters in AIoT paging message. The RAN node determines the device identifier type for an AIoT Device Identifier based on in which AIoT Device identification information field the AIoT Device identifier is included.

[0231] In some embodiments, the RAN node could determine the device identifier type for an AIoT Device Identifier received from AIOTF based on whether there is Mask info and the Identifier size. If there is no Mask info (or AIOTF explicitly indicates it is individual AIoT Device Identifier), the RAN node determines whether the AIoT Device Identifier is temporary ID or permanent device ID based on the Identifier size (as the two IDs have different lengths). In thiscase, the RAN node needs to be aware of the ID length, which may be preconfigured or configured to the RAN node (e.g., by the CN entity, for instance, by AIOTF or AMF). The RAN node then includes the determined device identifier type parameter in AIoT paging message.

[0232] In some embodiments, in case the AIoT paging message only provides one contention free random access (CFRA) resource, the device could determine that the AIoT paging message only includes one AIoT Device Identifier which is either temporary ID or permanent device ID, then based on size of the MAC SDU including the AIoT Device Identifier the device could determine whether it is temporary ID or permanent device ID and take action accordingly as described above. Alternatively, the lower layer of the device forwards the MAC SDU to the upper layer, the upper layer may decode the ID, and inform the ID type to the lower layer, alternatively, the device bases on the CFRA resource (allocated for subsequent D2R transmission), and may derive the transport block size, which may indicate the ID type, it is worth noting that the device needs to be aware the ID size beforehand. Such information may be preconfigured (e.g., prestored in the device memory) or configured to the device (e.g., by the reader or the CN).

[0233] As an additional embodiment, the paging message may provide multiple CFRA resources targeting multiple devices. The above embodiment is equally applicable wherein each device applies the procedure as described in the above embodiment.

[0234] In some embodiments, if in a received AIoT paging message a device is addressed by a specific type of AIoT Device Identifier, then in a subsequent AIoT paging message with the same transaction id, the device only checks the same type of AIoT Device Identifier as that included in the previously received AIoT paging message. For instance, if a device is addressed by temporary ID / permanent device ID in a received AIoT paging message, in the subsequent AIoT paging message with the same transaction id, the device only checks if it is addressed by one of the temporary ID(s) / permanent device ID(s) w / o further checking the permanent device ID(s) / temporary ID(s) (if present). The device ignores the subsequent AIoT paging message if it does not include temporary ID(s) / permanent device ID(s) or there is no matching temporary ID(s) / permanent device ID(s).

[0235] In some embodiments, the device ID type is indicated as AS information as part of header, preamble, flags or control / Ll / L2 information prior to paging message which contains device ID (temporary device ID or permanent device ID). This AS information may be encoded with paging message or paging message payload in a mutual inclusive or exclusive manner. See below options depicting encoding mechanisms.

[0236] In one option, the paging message remains same irrespective of ID type. Given these two IDs may have distinct sizes, hence ID container in paging message is designed or set according to largest of these two ID types. In case, the paging message contains ID which does no occupy allthe bits in the ID container then the leftover space is filled with reserved bits. Based on header or flag or AS information pertinent to ID type, the device may interpret which bits in ID container is related to device ID and which bits correspond to padding bits.

[0237] In another option, the paging message size is made dynamic. It means the ID container in paging is set dynamic, i.e., depending on ID type, the ID container size is adjusted accordingly. The device does not need to apply any blind decode in order to decode paging message if there is header, or flag or AS information indicates ID type before the paging payload. It is assumed that the header and payload will be encoded in mutual exclusive manner, i.e., the header may be decoded independently, which enables device to retrieve information related to ID types which correspond the size of entailed paging message payload or TB.

[0238] In above, the ID type may be indicated using a specific selection of preamble included before paging message. Say premable#Pl is used before paging message if it contains temporary device ID, and preamble#P2 id paging message contains permanent ID.

[0239] To perform the method actions above, the second network node 132 is configured to handle an identifier of a device in a communications network 100.

[0240] The second network node 132 may comprise an arrangement depicted in Figure 7. The second network node 132 may comprise an input and output interface 700 configured to communicate in the communications network 100, e.g., with the device 120 The input and output interface 700 may comprise a wireless receiver not shown, and a wireless transmitter not shown.

[0241] The second network node 132 is further configured to receive a first request message from a first network node 131 for the device 120.

[0242] The second network node 132 is further configured to identify a device identifier, ID, type assigned to the device 120 based on the first request message and attach the device ID type into a second request message. The device ID type may be adapted to be anyone out of a temporary device ID, a permanent device ID, a group ID.

[0243] The second network node 132 is further configured to send to a network node 110, the second request message and the identified device ID type, to be delivered in a paging message towards the device 120, thereby enabling the device 120 to use the device ID type as a basis for determining what action to proceed with.

[0244] To perform the method actions above, the device 120 is configured to handle an identifier of the device in a communications network 100.

[0245] The device 120 may comprise an arrangement depicted in Figure 8. The device 120 may comprise an input and output interface 800 configured to communicate in the communicationsnetwork 100, e.g., with the device 120. The input and output interface 800 may comprise a wireless receiver not shown, and a wireless transmitter not shown.

[0246] The device 120 is further configured to receive a paging message and a device identifier, ID, type assigned to the device 120, from a network node 110.

[0247] The device 120 is further configured to determine whether the device ID type assigned to the device 120 is a temporary device ID, a permanent device ID, or a group ID.

[0248] The device 120 is further configured to determine, based on the determined device ID type, which action to proceed with.

[0249] The device 120 is furthermore configured to determine what action to proceed with by: - when the device ID type is adapted to be, a temporary ID, check whether the temporary ID in the paging message matches a temporary ID stored in a memory.

[0250] - when the device ID type is adapted to be a permanent ID, check whether the permanent ID in the paging message matches a permanent ID stored in a memory.

[0251] - when the device ID type is adapted to be a group ID, check whether the device ID with applied MASK information matches, or at least partly matches, corresponding part of a permanent device ID of the device 120 stored in a memory.

[0252] Embodiments herein may be implemented through a respective processor or one or more processors, such as the respective processor 710 of a processing circuitry in the second network node 132 depicted in Figure 7, and processor 810 of a processing circuitry in the device 120 depicted in Figure 8 together with respective computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the respective second network node 132 and device 120. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the respective second network node 132 and device 120.

[0253] The second network node 132 and device 120 may further comprise a respective memory 720 and memory 820 comprising one or more memory units. The respective memory 720 and memory 820 comprises instructions executable by the processor in the respective second network node 132 and device 120. The respective memory 720 and memory 820 are arranged to be used to store e.g., media functions, indications, tags, information, data, configurations, communication data, and applications to perform the methods herein when being executed in the respective second network node 132 and device 120.In some embodiments, a respective computer program 730 and computer program 830 comprises instructions, which when executed by the respective at least one processor 710 and processor 810, cause the at least one processor of respective second network node 132 and device 120 to perform the actions above.

[0254] In some embodiments, a respective carrier 740 and carrier 840 comprises the respective computer program 730 and computer program 830, wherein the respective carrier 740 and carrier 840 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0255] Those skilled in the art will appreciate that units in the respective second network node 132 and device 120 described above may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, e.g. stored in the respective second network node 132 and device 120, that when executed by the respective one or more processors such as the processors described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry ASIC, or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

[0256] Fig- 9 shows an example of a communication system QQ100 in accordance with some embodiments.

[0257] In the example, the communication system QQ100 includes a telecommunication 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, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, 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 telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication 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 nodes to implement one or more functionalities of any nodein the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0258] 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). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), 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.

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

[0260] 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 QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication 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 telecommunication network QQ102.In the depicted example, the core network QQ106 connects 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 more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0261] 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 telecommunication network QQ102. 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.

[0262] As a whole, the communication system QQ100 of Figure 15 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); 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 (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0263] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102may support network slicing to provide different logical networks to different devices that are connected to the telecommunication 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) / Massive loT services to yet further UEs.

[0264] In some examples, 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).

[0265] 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. 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 device, 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.

[0266] The hub QQ114 may have a constant / persi stent or intermittent connection to the network node QQllOb. 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 QQ114may 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 QQllOb. 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.

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

[0268] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0269] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 10. The level of integrationbetween the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0270] The processing circuitry QQ202 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 QQ210. The processing circuitry QQ202 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 QQ202 may include multiple central processing units (CPUs).

[0271] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. 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.

[0272] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.The memory QQ210 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 QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

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

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

[0275] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication,data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0276] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

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

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

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

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

[0281] Fig. 11 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, 0-DU, O-CU).

[0282] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an 0-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).Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0283] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

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

[0285] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio unitsand digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0286] The memory QQ304 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 QQ302. The memory QQ304 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 QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0287] The communication interface QQ306 is used in wired or wireless communication of signalling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio frontend circuitry QQ318 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 QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0288] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some ofthe RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

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

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

[0291] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 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 QQ308. As a further example, the power source QQ308 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.

[0292] Embodiments of the network node QQ300 may include additional components beyond those shown in Fig. 11 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 QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic,maintenance, repair, and other administrative functions for the network node QQ300. In some embodiments providing a core network node, such as core network node 108 of Fig. 9, some components, such as the radio front-end circuitry QQ318 and the RF transceiver circuitry QQ312 may be omitted.

[0293] Fig. 12 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 a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. 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. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

[0294] 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 Q500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0295] 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 VMs QQ508a and QQ508b (one or more of which may be generally 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 the VMs QQ508.

[0296] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding 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.

[0297] In the context of NFV, a VM 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 VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0298] 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 signalling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0299] Although the computing devices described herein (e.g., UEs, network nodes) 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, whilecomponents 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.

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

[0301] In some embodiments a more general term “network node” is used and it can correspond to any type of radio network node or any network node, which communicates with a wireless device and / or with another network node. Examples of network nodes are NodeB, Master eNB, Secondary eNB, a network node belonging to Master cell group (MCG) or Secondary Cell Group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node e.g. Mobility Switching Centre (MSC), Mobile Management Entity (MME) etc., Operation and Maintenance (O&M), Operation Support System (OSS), Self-Organizing Network (SON), positioning node e.g. Evolved Serving Mobile Location Centre (E-SMLC), Minimizing Drive Test (MDT), etc.

[0302] In some embodiments, the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device-to-device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UEcapable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.

[0303] The embodiments are described for 5G. However the embodiments are applicable to any RAT or multi-RAT systems, where the UE receives and / or transmit signals (e.g. data) e.g. LTE, LTE FDD / TDD, WCDMA / HSPA, GSM / GERAN, Wi Fi, WLAN, CDMA2000 etc.As will be readily understood by those familiar with communications design, functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.

[0304] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0305] It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

[0306] When using the word "comprise" or “comprising” it shall be interpreted as non- limiting, i.e. meaning "consist at least of'.

[0307] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

Claims

CLAIMS1. A method performed by a second network node (132) for handling an identifier of a device (120) in a communications network (100), the method comprising:receiving (301) a first request message from a first network node (131) for the device (120),identifying (302) a device identifier, ID, type assigned to the device (120) based on the first request message, which device ID type is anyone out of a temporary device ID, a permanent device ID, and a group ID, and attaching the device ID type into a second request message,sending (303) to a third network node (110), the second request message and the identified device ID type to be delivered in a paging message towards the device (120), enabling the device (120) to use the device ID type as a basis for determining which action to proceed with.

2. A method performed by a device (120), for handling an identifier of the device (120), in a communications network (100), the method comprising:receiving (401) a paging message comprising a device Identifier, ID, type assigned to the device (120),determining (402) whether the device ID type assigned to the device (120) is a temporary device ID, a permanent device ID, or a group ID, andbased on the determined device ID type, determining (403) which action to proceed with.

3. The method performed according to claim 2, wherein the determining (403) which action to proceed with comprises:- when the device ID type indicates a temporary ID, checking whether the temporary ID in the paging message matches a temporary ID stored in a memory,- when the device ID type indicates a permanent ID, checking whether the permanent ID in the paging message matches a permanent ID stored in a memory- when the device ID type, indicates a group ID checking whether the device ID with applied MASK information matches, or at least partly matches, a corresponding part of a permanent device ID of the device (120) stored in a memory.

4. A computer program (730, 830) comprising instructions, which when executed by a processor (710, 810), causes the processor (710, 810) to perform actions according to any of the claims 1-3.

5. A carrier (740, 840) comprising the computer program (730, 830) of claim 4, wherein the carrier (740, 840) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer- readable storage medium.

6. A second network node (132) configured to handle an identifier of a device (120) in a communications network (100), wherein the second network node (132) is further configured to:receive a first request message from a first network node (131) for the device (120), identify a device identifier, ID, type assigned to the device (120) based on the first request message, which device ID type is adapted to be anyone out of a temporary device ID, a permanent device ID, and a group ID, and attach the device ID type into a second request message,send to a third network node (110), the second request message and the identified device ID type, to be delivered in a paging message towards the device (120), enabling the device (120) to use the device ID type as a basis for determining which action to proceed with.

7. A device (120) configured to handle an identifier of the device (120) in a communications network (100), wherein the device (120) is further configured to:receive a paging message comprising a device identifier, ID, type assigned to the device (120),determine whether the device ID type assigned to the device (120) is a temporary device ID, a permanent device ID, or a group ID,based on the determined device ID type determine which action to proceed with.

8. The device (120) according to claim 7, further being configured to determine which action to proceed with by:- when the device ID type is adapted to indicate a temporary ID, check whether the temporary ID in the paging message matches a temporary ID stored in a memory- when the device ID type is adapted to indicate a permanent ID, check whether the permanent ID in the paging message matches a permanent ID stored in a memory- when the device ID type is adapted to indicate a group ID check whether the device ID with applied MASK information matches, or at least partly matches, corresponding part of a permanent device ID of the device (120) stored in a memory.

Images