# Renovated XTEA Encoder Architecture-Based Lightweight Mutual Authentication Protocol for RFID and Green Wireless Sensor Network Applications

Authors: Manikandan Nagarajan; Muthaiah Rajappa; Yuvaraja Teekaraman; Ramya Kuppusamy; Amruth Ramesh Thelkar
Journal: Wireless Communications and Mobile Computing
 (2022)

---

## Abstract

Wireless sensor networks find applications everywhere in day to day activities right from attendance entry systems to healthcare monitoring systems. The evolution of the Internet of Things (IoT) as the Internet of Everything (IoET) makes the wireless sensor network omnipresent and increases the use of Radio Frequency Identification (RFID) for the proper identification of devices and sensor nodes which are mostly battery operated. As technology evolves, security threats also increase rapidly. This mandates a strong and energy-efficient green solution. This work attempted to address these issues by effectively deploying the lightweight encryption scheme called Extended Tiny Encryption Algorithm (XTEA). Though the XTEA is lightweight and famous, it is commonly known for various attacks. Our work patches the security threats in the XTEA by applying domain-specific customization, random number utilization, and undisclosed key renewal techniques. Two custom Renovated XTEA Mutual Authentication Protocol (RXMAP) encoder architectures, namely, RXMAP-1 and RXMAP-2, are proposed based on the replacement of accurate computational blocks with approximate blocks. The proposed RXMAP protocol is evaluated for its computational and storage overhead and verified against various security threats using BAN logic formal verification and informal verification. The proposed encoder architectures are simulated for functional verification, and ASIC implementation is done with a 132 nm process node. ASIC implementation results show that the proposed designs RXMAP-1 and RXMAP-2 occupy 53.11% and 53.31% lesser area compared to XTEA I and 52.97% and 53.18% lesser area compared to XTEA II implementation. The total power consumed by the proposed encoder architectures RXMAP-1 and RXMAP-2 is 68.76% and 71.64% lesser than XTEA II implementation, respectively, while maintaining the equal throughput.


---

## Body

## 1. Introduction

Advancement in technology facilitates people to enjoy wireless devices with smart sensors. Wireless sensor networks (WSN) are finding applications in various places, viz, health monitoring, IoT (Internet of Things), logistics, and warehouses [1]. As the application areas are getting wider, the privacy and security issues are also getting complex. So, securing information exchanged in the networks is the need of the hour. There are many algorithms available in the literature for securing the communication among the sensors and systems. Most of the secured algorithms are complex and computation intensive in nature [2]. Wireless sensor networks are composed of Radio Frequency Identification (RFID) tags and low power-consuming sensors [3]. Deploying complex security algorithms is not a feasible solution for the WSN components. This leads to the lightweight cryptography domain. Lightweight encryption schemes utilize fundamental operations like addition, rotation, and xor (ARX) operations [4]. The ARX operations are alone not sufficient for securing the data and communication. There is a chance of attack, and some complex encryption schemes are essential to protect the sensors and systems. The encryption scheme deployed for WSN is the tradeoff between the complexity and the performance [5, 6].There are plenty of research works which satisfy the requirements of the WSN in the literature, namely, PRESENT [7], PRINCE [8], TEA [9], XTEA [10], XXTEA [11], LEA [12], HIGHT [13], and AES [14]. Each encryption scheme features and fits best for the unique applications based on the requirements and the nature. In the WSN, mutual authentication is the key part in the node registration and communication phase. In IoT applications, also, authentication is pivotal in the perception layer to address the devices and send the collected data from edge to server for processing [15]. Mutual authentication uses symmetric key encryption schemes [16, 17]. The edge sensors and RFID tags are the components of the perception layer. A separate subfield in cryptography is prevailing to establish mutual authentication between the nodes and the servers. Standard block encryption schemes need to be customized to make it fit in the RFID or sensor nodes. [18–24] implements the lightweight encoding schemes for mutual authentication.Mutual authentication protocols (MAP) are slightly unique from conventional encryption schemes. Nondisclosure of the key is vital in the MAP which does not exactly require the conventional encryption algorithms. This work is attempted to explore the domain-specific requirements and deploy the appropriate things to ensure the security of authentication. Domain-specific architectures (DSA) are customized architectures based on the need of the specific domains and their application. DSA is a next disruptive technology alternate to the parallelism and pipelining to attain the performance [25]. In this work, we targeted the Extended Tiny Encryption Algorithm (XTEA) which is cracked by attacks such as related key attacks [26] and meet-in-the-middle attack [27].All the encryption algorithms do have its security breaking point. This work proposes a renovated XTEA (RXTEA) which patches the reported security problems in the XTEA and optimizes the area of implementation and power requirements [6]. The requirements of the passive RFID EPC class 1 generation 2 tags [28] are that the design should have less than 10000 gate equivalent which includes security and functional handling chip components and circuit should be operated with low power which the tag receives from the reader as a trigger. This work RXTEA addresses the above mentioned issues without compromising any of the requirements of RFID EPC class 1 generation 2 tags, and it is a suitable candidate for the mutual authentication in passive tags and green wireless sensor network applications.The proposed protocol architecture is implemented in ASIC (Application Specific Integrated Circuit) design flow with the technology process (130 nm).


### 1.1. The Significant Contribution of the Proposed Work

The following are the significant contributions of the proposed work:(1)
Domain-specific architecture customization for XTEA is done to make it fit for low power applications(2)
Add the features to produce delta in a random fashion which makes XTEA to withstand for various attacks(3)
Key is not shared in any form in the information used for the mutual authentication process(4)
Communication messages used in the authentication process are much lesser in size than in key size, so it is impossible to guess the key and robust against adversaries(5)
Key and identity are updated after each successful session thereby fortifying against desynchronization attack models


### 1.2. Organization

The remainder of the manuscript is consolidated with related works in Section2, protocol design in Section 3, and security analysis in Section 4. Evaluation of the protocol is done in Section 5, and the ASIC implementation of the proposed protocol architecture is briefed in Section 6. Section 7 consolidates the contribution and concludes this paper.


## 1.1. The Significant Contribution of the Proposed Work

The following are the significant contributions of the proposed work:(1)
Domain-specific architecture customization for XTEA is done to make it fit for low power applications(2)
Add the features to produce delta in a random fashion which makes XTEA to withstand for various attacks(3)
Key is not shared in any form in the information used for the mutual authentication process(4)
Communication messages used in the authentication process are much lesser in size than in key size, so it is impossible to guess the key and robust against adversaries(5)
Key and identity are updated after each successful session thereby fortifying against desynchronization attack models


## 1.2. Organization

The remainder of the manuscript is consolidated with related works in Section2, protocol design in Section 3, and security analysis in Section 4. Evaluation of the protocol is done in Section 5, and the ASIC implementation of the proposed protocol architecture is briefed in Section 6. Section 7 consolidates the contribution and concludes this paper.


## 2. Related Works

TEA family algorithms attract the interest of the researchers, and it has been evolved from the year of its invention. Few of the works modified the TEA computation to strengthen the security, and many works in the literature are focused on the performance improvement of it to get better throughput. Some of the closely related recent works which targeted RFID and IOT applications are presented below.Mishra and Acharya [4] proposed the high throughput architectures of TEA family for high speed IoT and RFID applications. Pipelined implementation of TEA, XTEA, and XXTEA is done to improve the throughput of computation of the encryption process. By parallelizing the computation process, significant throughput improvement is attained at the expense of the more resource utilization. The authors also implemented a hybrid method by combining the TEA architecture. The designed encoders are implemented in Field Programmable Gate Array (FPGA) and Application Specific Integrated Circuit (ASIC) platform.Kella et al. [29] attempted to modify the XXTEA architecture to make it fit for RFID tags. A serial architecture for XXTEA-192 block cipher can perform ARX operations in each clock. This works on variable length ciphers with the minimum block size of 32-bits and its multiple so that it is extended for a higher length. The design is implemented on FPGA to calculate throughput parameters.Ragab et al. [30] claimed higher throughput while maintaining the security by adding S-box to the computation process. To add an additional strength key generation is done with the chaotic computation method. The designed M-XXTEA is compared with AES, and it is producing 57% better efficiency than AES.Yeo et al. [31] created the IP core for the corrected block TEA to integrate and reuse the design in various IoT applications. The developed block TEA is able to encrypt the data width from 64 bits to 256 bits in multiple of 32 bits. The IP core is developed in verilog-HDL and implemented in Vertex 4 FPGA. The design has exhibited good throughput performance.Anusha et al. [32] drafted a pipelined architecture to implement an XTEA and TEA for the parallel computation while keeping the resources minimum to make them fit in the RFID authentication process. The developed architecture implemented in the artix-7 FPGA and computation performance is evaluated.Khan and Zhu [33] presented a secure symmetric key-based mutual authentication protocol for the RFID authentication. In this, they used XTEA for encrypting the communication messages. An effective key updating mechanism is adopted to make the protocol stand against replay, eavesdropping, and man-in-the middle attack while keeping the computing cost minimum.Khan et al. [34] deployed a NIOS II processor to implement the XTEA encryption process for the RFID mutual authentication purpose. The subkey of the RFID tag is updated in a random way that makes the developed protocol stable against various attacks.


## 3. Proposed Renovated XTEA Mutual Authentication Protocol Architecture

In this section, we propose a renovated XTEA (RXTEA) encoder architecture and a secure RXTEA-based mutual authentication protocol (RXMAP). The following changes are made in the XTEA architecture to reduce the computation and to make it robust against related key attack [26] and meet-in-the-middle attack [27]:
(1)
Domain-specific customization is done to the XTEA architecture. For encryption purpose, accurate adders are not necessary, so it is replaced with approximate adders(2)
Constant delta value may lead to the guess of internal computations. It is replaced with the delta computation block which computes fresh delta for every successful authentication with the random numbers(3)
Only one-half of the ciphered text is used as a message to authenticate the server and tag. This makes it almost impossible to guess the key value(4)
Key value is updated at both server and tag side with the values internally computed. It is highly impossible to guess the new key


### 3.1. Renovated XTEA Encoder Architecture

The proposed RXMAP encoder architecture is presented in Figure1. The notations used in the proposed architecture and protocol are listed in Table 1. Inputs for the RXMAP encoder architecture are 128-bit key, 64-bit IDS, 32-bit RS, and RT. With the received inputs and the computed delta value, both tag and server start to compute the cover-coded password, i.e., cipher text of two 32-bit data as in equation (1). In the cover-coded password computation, ARX process is involved. In that instead of accurate adder, approximate adders are used. Based on the approximate adders used, two proposed configurations, namely, RXMAP-1 and RXMAP-2, are constructed. Protocol governing control block produces CTRL signal to have control over the trigger generation and new IDS, key update process.
(1)Delta=RT31:16RS15:0RS31:16RT15:0.Figure 1
Proposed RXMAP encoder architecture for both the tag and reader.Table 1
Nomenclature and symbols used in the proposed protocol.
NotionsExplanationsReqReader’s request to the tagIDIdentity number of the RFID tagIDSThe pseudonym of the IDRTTag’s random numberRSReader’s random numberCPWDMTMSB 32 bits of cover-coded password generated through the proposed XTEA on the tag sideCPWDLTLSB 32 bits of cover-coded password generated through the proposed XTEA on the tag sideCPWDMRMSB 32 bits of cover-coded password generated through the proposed XTEA on the reader sideCPWDLRLSB 32 bits of cover-coded password generated through the proposed XTEA on the reader side| |Concatenation operation&AND operation^XOR operation<<Left rotationCTRLControl signal generated by the protocol governing control moduleIRCIntermediate result in the multiple round encryptions of cover-coded passwordIRC5Intermediate result of cover-coded password at the end of the 5th roundIRC10Intermediate result of cover-coded password at the end of the 10th round


#### 3.1.1. Approximate Adders for RXMAP Encoder

Adders in the XTEA architecture are used to repeatedly sum up the translated plaintext with the key. Here, the concept behind the addition process is to change the plaintext value to some other value. Hence, an accurate adder is necessary to do the translation process, because they are computation intensive process in the repeated rounds. As approximate adders are noncommutative, the same logic would not work for the different domains where decryption is also mandatory. In the case of mutual authentication process, decryption is not essential and that is specified as domain-specific customization in our work.Two 32-bit adders are proposed in this work as follows:(1)
OR only adder (OOA)—two 32-bit data are added with two inputs OR gate bit by bit(2)
XOR only adder (XOA)—two 32-bit data are added with two inputs XOR gate bit by bitThese adders are inspired from the lower part OR adder (LOA) [35]. LOA is an area and computation-efficient implementation of the adder among the various approximate adders in the literature ever found. Still, the research is progressed in the same approach for striving better accuracy [36–39]. Our work is unique in this; we hardly bother about accuracy since in this encryption domain adder is used for translation purpose.The encoder architecture uses XOA and OOA with its addition processes called RXMAP-1 and RXMAP-2, respectively.


### 3.2. Renovated XTEA-Based Mutual Authentication Protocol

Our proposed Renovated XTEA Mutual Authentication Protocol is shown in Figure2. The proposed protocol architecture is formulated for encrypting a block of 64-bit plaintext with the 128-bit key. Mutual authentication is performed by considering random numbers RT and RS. The random numbers and the key are manipulated by the proposed RXMAP encoder to produce cover-coded passwords, and it proceeds as per the protocol flow described below,Figure 2
The proposed lightweight Renovated XTEA Mutual Authentication Protocol (RXMAP).There is a certain initial set of assumptions to start the proposed protocol, and it is listed as follows:(1)
Both the tag and server knows the pseudonym IDS of the tag and the key used for authentication(2)
The tag and reader have the ability to produce the random numbersThe step by step elucidation of the proposed RXMAP protocol is as follows:(Step 1)
The reader commences the protocol by sending a Req message.(Step 2)
Tag on getting Req notification generates random number RT and sends generated RT by concatenating it with its pseudonym IDS as a response to the reader Req.(Step 3)
Upon receiving IDS||RT, the reader forwards it to the server.(Step 4)
With the received IDS, the server starts searching the database for the matches. If it is found, the corresponding key will be extracted and reader side random number (RS) will be generated to use it in further steps.With the received RT, generated RS, and extracted Key, the server computes cover-coded passwords/keys named CPWDLR and CPWDMR by using RXMAP encoder. The server sends the concatenated values RS||CPWDLR to the reader.If the received IDS is not matched with the old or new entries in the database, then, it considers the tag as an invalid one and terminates the communication. If it matches with the new entry, then, the server deletes old entry in the database and proceeds further. Otherwise, it will check the match with the old entry; if it matches, then it senses the attack in between during the preceding communication and deletes the new entry in the database and continues the authentication process as a fresh one with the old entry. This ensures the tag’s synchronization with the server all the time and also optimizes the server’s storage space.(Step 5)
The reader redirects the received RS||CPWDLR to the tag.(Step 6)
With the received RS, generated RT, and the Key, the tag also computes cover-coded passwords/keys named CPWDLT and CPWDMT using RXMAP encoder.Upon completion of the CPWDLT computation, the tag verifies CPWDLR with CPWDLT; if it is matched, then, the tag authenticates the server, and as an acknowledgement to the server authentication, the tag sends the cover-coded CPWDLT to the reader.(Step 7)
The reader redirects the received CPWDLT to the server.(Step 8)
The server verifies the received CPWDLT with CPWDLR for similarity by XNOR process; if it is equal, then the server authenticates the tag and computes the trigger value internally as per(2)Trigger=RS31:16RT15:0&RT31:16RS15:0.Once the server authenticated the tag, the server sends the trigger as an acknowledgement of authentication to the tag through the reader to initiate the IDS and key replacement at the tag side. During that process, the server computes new IDS and key as per equations (3) and (4) and inserts it in its database for the corresponding tag while keeping the IDS and key used in the present session as old IDS and key. If authentication failed, the server terminates the communication without updating its database for new IDS and key.The computation of tag’s new pseudonym IDS and the corresponding key value for further processing is as follows:(3)NewKey=IRC1031:16IRC515:0IRC1015:0IRC531:16,(4)NewIDS=CPWDMRT31:16RS31:16RT15:0CPWDMRT15:0.(Step 9)
The reader redirects the received trigger to the tag.After receiving the trigger value, the tag computes the trigger value internally as per equation (2) and compares it with the received trigger value. If it matches, then, the tag replaces its IDS and key value as in equations (3) and (4) and establishes the connection. Else, it terminates the communication without altering its IDS and key values.


## 3.1. Renovated XTEA Encoder Architecture

The proposed RXMAP encoder architecture is presented in Figure1. The notations used in the proposed architecture and protocol are listed in Table 1. Inputs for the RXMAP encoder architecture are 128-bit key, 64-bit IDS, 32-bit RS, and RT. With the received inputs and the computed delta value, both tag and server start to compute the cover-coded password, i.e., cipher text of two 32-bit data as in equation (1). In the cover-coded password computation, ARX process is involved. In that instead of accurate adder, approximate adders are used. Based on the approximate adders used, two proposed configurations, namely, RXMAP-1 and RXMAP-2, are constructed. Protocol governing control block produces CTRL signal to have control over the trigger generation and new IDS, key update process.
(1)Delta=RT31:16RS15:0RS31:16RT15:0.Figure 1
Proposed RXMAP encoder architecture for both the tag and reader.Table 1
Nomenclature and symbols used in the proposed protocol.
NotionsExplanationsReqReader’s request to the tagIDIdentity number of the RFID tagIDSThe pseudonym of the IDRTTag’s random numberRSReader’s random numberCPWDMTMSB 32 bits of cover-coded password generated through the proposed XTEA on the tag sideCPWDLTLSB 32 bits of cover-coded password generated through the proposed XTEA on the tag sideCPWDMRMSB 32 bits of cover-coded password generated through the proposed XTEA on the reader sideCPWDLRLSB 32 bits of cover-coded password generated through the proposed XTEA on the reader side| |Concatenation operation&AND operation^XOR operation<<Left rotationCTRLControl signal generated by the protocol governing control moduleIRCIntermediate result in the multiple round encryptions of cover-coded passwordIRC5Intermediate result of cover-coded password at the end of the 5th roundIRC10Intermediate result of cover-coded password at the end of the 10th round


### 3.1.1. Approximate Adders for RXMAP Encoder

Adders in the XTEA architecture are used to repeatedly sum up the translated plaintext with the key. Here, the concept behind the addition process is to change the plaintext value to some other value. Hence, an accurate adder is necessary to do the translation process, because they are computation intensive process in the repeated rounds. As approximate adders are noncommutative, the same logic would not work for the different domains where decryption is also mandatory. In the case of mutual authentication process, decryption is not essential and that is specified as domain-specific customization in our work.Two 32-bit adders are proposed in this work as follows:(1)
OR only adder (OOA)—two 32-bit data are added with two inputs OR gate bit by bit(2)
XOR only adder (XOA)—two 32-bit data are added with two inputs XOR gate bit by bitThese adders are inspired from the lower part OR adder (LOA) [35]. LOA is an area and computation-efficient implementation of the adder among the various approximate adders in the literature ever found. Still, the research is progressed in the same approach for striving better accuracy [36–39]. Our work is unique in this; we hardly bother about accuracy since in this encryption domain adder is used for translation purpose.The encoder architecture uses XOA and OOA with its addition processes called RXMAP-1 and RXMAP-2, respectively.


## 3.1.1. Approximate Adders for RXMAP Encoder

Adders in the XTEA architecture are used to repeatedly sum up the translated plaintext with the key. Here, the concept behind the addition process is to change the plaintext value to some other value. Hence, an accurate adder is necessary to do the translation process, because they are computation intensive process in the repeated rounds. As approximate adders are noncommutative, the same logic would not work for the different domains where decryption is also mandatory. In the case of mutual authentication process, decryption is not essential and that is specified as domain-specific customization in our work.Two 32-bit adders are proposed in this work as follows:(1)
OR only adder (OOA)—two 32-bit data are added with two inputs OR gate bit by bit(2)
XOR only adder (XOA)—two 32-bit data are added with two inputs XOR gate bit by bitThese adders are inspired from the lower part OR adder (LOA) [35]. LOA is an area and computation-efficient implementation of the adder among the various approximate adders in the literature ever found. Still, the research is progressed in the same approach for striving better accuracy [36–39]. Our work is unique in this; we hardly bother about accuracy since in this encryption domain adder is used for translation purpose.The encoder architecture uses XOA and OOA with its addition processes called RXMAP-1 and RXMAP-2, respectively.


## 3.2. Renovated XTEA-Based Mutual Authentication Protocol

Our proposed Renovated XTEA Mutual Authentication Protocol is shown in Figure2. The proposed protocol architecture is formulated for encrypting a block of 64-bit plaintext with the 128-bit key. Mutual authentication is performed by considering random numbers RT and RS. The random numbers and the key are manipulated by the proposed RXMAP encoder to produce cover-coded passwords, and it proceeds as per the protocol flow described below,Figure 2
The proposed lightweight Renovated XTEA Mutual Authentication Protocol (RXMAP).There is a certain initial set of assumptions to start the proposed protocol, and it is listed as follows:(1)
Both the tag and server knows the pseudonym IDS of the tag and the key used for authentication(2)
The tag and reader have the ability to produce the random numbersThe step by step elucidation of the proposed RXMAP protocol is as follows:(Step 1)
The reader commences the protocol by sending a Req message.(Step 2)
Tag on getting Req notification generates random number RT and sends generated RT by concatenating it with its pseudonym IDS as a response to the reader Req.(Step 3)
Upon receiving IDS||RT, the reader forwards it to the server.(Step 4)
With the received IDS, the server starts searching the database for the matches. If it is found, the corresponding key will be extracted and reader side random number (RS) will be generated to use it in further steps.With the received RT, generated RS, and extracted Key, the server computes cover-coded passwords/keys named CPWDLR and CPWDMR by using RXMAP encoder. The server sends the concatenated values RS||CPWDLR to the reader.If the received IDS is not matched with the old or new entries in the database, then, it considers the tag as an invalid one and terminates the communication. If it matches with the new entry, then, the server deletes old entry in the database and proceeds further. Otherwise, it will check the match with the old entry; if it matches, then it senses the attack in between during the preceding communication and deletes the new entry in the database and continues the authentication process as a fresh one with the old entry. This ensures the tag’s synchronization with the server all the time and also optimizes the server’s storage space.(Step 5)
The reader redirects the received RS||CPWDLR to the tag.(Step 6)
With the received RS, generated RT, and the Key, the tag also computes cover-coded passwords/keys named CPWDLT and CPWDMT using RXMAP encoder.Upon completion of the CPWDLT computation, the tag verifies CPWDLR with CPWDLT; if it is matched, then, the tag authenticates the server, and as an acknowledgement to the server authentication, the tag sends the cover-coded CPWDLT to the reader.(Step 7)
The reader redirects the received CPWDLT to the server.(Step 8)
The server verifies the received CPWDLT with CPWDLR for similarity by XNOR process; if it is equal, then the server authenticates the tag and computes the trigger value internally as per(2)Trigger=RS31:16RT15:0&RT31:16RS15:0.Once the server authenticated the tag, the server sends the trigger as an acknowledgement of authentication to the tag through the reader to initiate the IDS and key replacement at the tag side. During that process, the server computes new IDS and key as per equations (3) and (4) and inserts it in its database for the corresponding tag while keeping the IDS and key used in the present session as old IDS and key. If authentication failed, the server terminates the communication without updating its database for new IDS and key.The computation of tag’s new pseudonym IDS and the corresponding key value for further processing is as follows:(3)NewKey=IRC1031:16IRC515:0IRC1015:0IRC531:16,(4)NewIDS=CPWDMRT31:16RS31:16RT15:0CPWDMRT15:0.(Step 9)
The reader redirects the received trigger to the tag.After receiving the trigger value, the tag computes the trigger value internally as per equation (2) and compares it with the received trigger value. If it matches, then, the tag replaces its IDS and key value as in equations (3) and (4) and establishes the connection. Else, it terminates the communication without altering its IDS and key values.


## 4. Security Analysis

In this clause, the presented RXMAP protocol is investigated for security analysis. The proposed RXMAP protocol is examined for formal and informal analyses. For formal analysis, Burrows-Abadi-Needham (BAN) logic is formulated. The informal analysis is performed on the following facets: security requirements, security threats, and cryptanalysis models.


### 4.1. Formal Analysis

Formal analysis is the art of analyzing a deficiency in the designed protocols that are not directly apparent through cryptanalysis. A five-step procedure was suggested for applying the formal verification functions in the RFID designs [40]. Formal analysis works under the principle of belief analysis, and based on that request/response communication between the tag and the reader is evaluated. This function examines the plain message formation and succession of communication between the transaction groups to assess the protocol’s potential on epitomized level efficiently. The BAN logic is deployed for verifying our RXMAP protocol.


#### 4.1.1. BAN Logic Analysis

This logic was formulated by Burrows et al. [41]. This logic was used to rationale authentication protocols among contenders in a distributed processing system. The precepts used in BAN logic analysis [42] are explained below with equations. The notions and corresponding descriptions of the notions that are used for BAN logic analysis [43] are tabulated in Table 2.Table 2
Notions and descriptions used for BAN logic analysis.
NotionsExplanationsP or QPandQ are the principal that refers to a sender or receiver. For instance, the tag or the readerP∣≡XP believes the statement XP⊲XP sees the statement X#XThe formulaX is freshP∣~XP once said the statement XX,YEither formulaX or Y is one section of formula X,YP∣⇒XP has control over statement XXYX is integrated with formula YP↔KQShared keyK is used for communication between P and Q. K will be known only to these two entitiesNKEYThis denotes the new key generated for further updating and processingThe BAN logic rules have been applied for the proposed RXMAP protocol for the abstract level evaluation. These rules are tabulated in Table3.Table 3
The BAN model rules applied for the proposed RXMAP protocol.
BAN logic rulesRules applied for the proposed RXMAP protocolMessage-meaning rule (M)Case (1)T∣≡R↔RST,T⊲CPWDLRRM/T≡R~CPWDLRCase (2) R∣≡T↔RTR,R⊲CPWDLTRT/R∣≡T∣~CPWDLTNonce-verification rule (NV)Case (1)T∣≡#CPWDLR,T∣≡R∣~CPWDLR/T≡R≡CPWDLRCase (2) R∣≡#CPWDLT,R∣≡T∣~CPWDLT/R∣≡T∣≡CPWDLTJurisdiction rule (J)Case (1)T∣≡R⟹CPWDLR,T∣≡R∣≡CPWDLR/T∣≡CPWDLRCase (2) R∣≡T⟹CPWDLT,R∣≡T∣≡CPWDLT/R∣≡CPWDLTFreshness rule (F)Case (1)T∣≡#RT/T∣≡#CPWDLT,RTCase (2) R∣≡#RS/R∣≡#CPWDLR,RSOther inference rules (I)Case (1)T⊲CPWDLR,RS/T⊲CPWDLRCase (2) R⊲CPWDLT,RT/R⊲CPWDLTFrom [42], goals for achieving mutual authentication for a protocol are derived. In the proposed protocol, the mutual authentication phase takes place only after the translated cover-coded password exchange between the tag and the reader. A successful translated cover-coded password exchange indicates a successful protocol run for one session. Therefore, if mutual authentication is verified through BAN logic, then, the protocol run is also verified simultaneously. Hence, these goals are targeted to achieve the protocol evaluation. Mutual authentication is accomplished between two principles A and B if K is existing such that
(5)A∣≡A↔KB,B∣≡A↔KB,A≡B≡A↔KB,B≡A≡A↔KB.The first two are believed to be essential for any protocol to be mutually authenticated. Assumptions, according to the proposed protocol in order to acquire the above goals, are formulated as mentioned below. Besides, it is assumed that the tag hasRS,RT,andPWD (KEY) and the reader has RS,RT,andPWD (KEY). The server is considered a secure channel and hence not included in the analysis. PWD is retrieved with pseudonym IDS which is updated after each session. T principle denotes the tag, and R principle denotes the reader.
(6)A1:T⇒RT,A2:T≡#RT,A3:R⇒RS,A4:R≡#RS,A5:T≡T↔PWDR,A6:R≡T↔PWDR.Messages that are communicated betwixt the tag and the reader in the RXMAP run are as follows:Message 1:R⟶T:CPWDLRPWD,RT,TriggerRT.Message 2:T⟶R:IDS,CPWDLTPWD,RSFrom the reader to tag,CPWDLR is an encrypted message transmitted. This CPWDLR is encrypted using PWD, RT, and RS. Trigger is sent from the reader to tag to initiate the key update process. Trigger is interleaved and translated version of RT and RS. Similarly, from the tag to reader CPWDLT is the encrypted message that is encrypted using PWD, RT, and RS.As mentioned earlier, the RXMAP protocol should satisfy the following goals for mutual authentication analysis:G1: R≡T≡T↔NKEYRG2:T∣≡R∣≡T↔NKEYRBased on the above assumptions and rules, it is witnessed that the RXMAP protocol attains the goals for mutual authentication and they are provided with multiple steps below.S1:AccordingtoMessage1andruleI1,T⊲CPWDLRPWD,RT,RSBy assumption A1 and A2 and ruleF (2),S2:T∣≡#CPWDLRPWD,RT,RSFrom assumptions A1 and A2 and statement S1 and ruleM (1), T∣≡R∣~CPWDLRPWD,RT,RSS3:T∣≡R⇒CPWDLRPWD,RT,RSBy statement S2, statement S3, and rule NV (1),S4:T≡R≡CPWDLRPWD,RT,RSAccording to statement S3, statement S4, and ruleJ (1), T∣≡CPWDLRPWD,RT,RS.Therefore, from statement S4 and statement S5, it can be stated asS6:T≡R≡T↔NKEYRS7: According to the proposed protocol,NKEYIRC10,IRC5Hence, from statement S1 to statement S7, it is evident thatT∣≡R∣≡↔NKEYR⟶ (G2 i.e. goal 2 satisfied)From Message 2 and rule I (2), it can be stated thatS8:R⊲CPWDLTPWD,RT,RSFrom the assumptions A3 and A4, and from rule F (2), it can be stated thatS9:R∣≡#CPWDLTPWD,RT,RSBy the assumptions A3 and A6 and from the statement S8 and rule M (2), it can be stated thatS10:R≡T~CPWDLTPWD,RT,RSR≡T⇒CPWDLTPWD,RT,RSFrom statements S9 and S10 and from rule NV (2), the following statement can be obtained:S11:R∣≡T∣≡CPWDLTPWD,RT,RSFrom statements S10 and S11 and from ruleJ (2), it can be stated thatS12:R∣≡CPWDLTPWD,RT,RSTherefore, from statements S11 and S12, it is obvious that statement S13 can be formulated asS13:R≡T≡T↔NKEYRS14: According to the RXMAP protocol,NKEYIRC10,IRC5Hence, from statement S8 to statement S14, it is apparent thatR∣≡T∣≡T↔NKEYR⟶(G1 i.e. goal 1 satisfied)Hence, from goals G1 and G2, formal analysis with BAN logic for the RXMAP protocol has been done.


### 4.2. Informal Analysis

In this section, the proposed RXMAP protocol is verified against variant possible security requirements, threats, and attacks.


#### 4.2.1. Security against the Tag’s Identity Reveal

In the message communication of the proposed protocol, tag’s ID is not revealed in any mean. The pseudonym IDS combined with RT {IDS||RT} is only used for the transaction, and it is renewed for each process. So it is impossible to get the ID of the tag. Hence, RXMAP is secured against the tag’s identity reveal.


#### 4.2.2. Resistance to Known Session-Specific Temporary Information Attack

This attack happens when the adversary happened to get intermediate session specific information and tried to retrace the useful information of the protocol scheme. In our work, the communication messages {RS||CPWDLR}, CPWDLT, and Trigger are generated from the temporary random numbers. Moreover, messages are of different sizes that are 64 bits and 32 bits. This is not at all sufficient for tracing the tag or server information, so it is resistant to known session-specific temporary information attacks.


#### 4.2.3. Mutual Authentication

Mutual authentication is essential for communication and data transfer to happen between tags and readers. A step by step verification of authentication of tags and server is presented in Section3.2. It also narrates the termination of invalid tag and invalid servers at various stages. Our protocol offers mutual authentication among the valid devices in the network.


#### 4.2.4. Forward and Backward Security

The communication messages {RS||CPWDLR}, CPWDLT, and Trigger are of sizes 64 bits, 32 bits, and 32 bits, respectively. The actual key size used in the encryption process is of 128-bit size. In addition with that, intermediate messages are generated through the session-specific random numbers. There is no possibility of finding trace of the previous or next session key. It is highly impossible to guess the 128-bit value from the 32-bit value.


#### 4.2.5. Resistance to Replay Attack

This attack can happen when the intruder eavesdrops on any of the intermediate information to take the communication further in later point of time. This is a risky thing in many applications. In our protocol, each message at a specific time depends on the random numbers generated at that specific session. Since previous session’s messages are not useful to perform replay, it is resilient to replay attack.


#### 4.2.6. Resistance against Impersonation Attack

In order to impersonate the reader/tag adversary, we need to know the structure of the encoder in either side. Moreover, the intermediate messages are generated based on RS, RT, IDS, and key. None of the details needed for the computation and the domain-specific architecture of the encoder are available with the intruder to impersonate in between. Thus, the proposed protocol is tolerant against impersonation attack from either side.


#### 4.2.7. Security against Man-In-The-Middle Attack

This attack may be performed by the privileged mediator trying to extract the tag or readers’ identity so that the entire system becomes under the control of the intruder. This attack was there with the XTEA architecture. In our domain-specific customized RXMAP architecture, we introduced the dynamically changing “delta” value, “IDS” values, and “key” values based on the random numbers at each session. So, it is unpredictable in nature and information that the privileged mediator is subject to change for every session. Hence, the proposed architecture and protocol inherit the resistance against the man-in-the-middle attack.


#### 4.2.8. Resistance to Masquerade Attack

An attacker may able to make the communication protocol to reveal the tag secret key by repeatedly sending the messages to the reader. This kind of repeated action will not be able to get the unique tag ID, because pseudonym was only used in each transaction also generated from the random numbers as follows:IDS=CPWDMR/T31:16‖RS31:16‖RT15:0‖CPWDMR/T15:0. Thus, no information can be cracked. The intruder cannot do replay attack, also due the IDS’s freshness. Hence, the proposed scheme is resistant to masquerade attack and denial of service (DoS).


#### 4.2.9. Resistance to Desynchronization Attack

Desynchronization attack focuses on disassociating the tag from the communication thereby leading to DoS. This is effectively handled in the proposed protocol by means of storing old and new IDs and key of the specific tag in the server and maintaining the freshness in the communication messages and values involved in by generating new random numbers RS and RT for each session. The proposed protocol uses verification message and acknowledges message to update the key and IDS values in either side. CPWDLR was used for verifying the server at the tag side, and CPWDLT was sent by the tag in response to act like an acknowledgement for the server and uses it for tag authentication. Key update will happen at the tag side upon receiving trigger acknowledge signal from the server.Here, desynchronization attack may be applied at step 9 to disassociate the tag from the server. But in the proposed RXMAP, we stored old and new details of the tag in the server. So once the attack happens, the tag will never get permanently disassociated from the server; rather, it will start the communication fresh with its old IDS and key. Therefore, the proposed scheme is versatile against the desynchronization attack.


#### 4.2.10. Anonymity and Untraceability

In the proposed protocol, IDS is not separately sent. Rather, it is sent along with the random number RT as IDS||RT. It is difficult to differentiate the random number RT and the IDS since both are random and regenerated for every session. Hence, it is anonyms to the attacker if he wants to get the identity of the tag, and it is untraceable.


#### 4.2.11. Related Key Attack

This is one of the weaknesses of the XTEA. The related key attack may be tried with the partial known part of the key in the transaction. The proposed RXMAP encoder architecture patched this weakness by randomizing the delta which involved in the calculation of sum and ciphered text. Another fact is that the key is rejuvenated in a highly random fashion since it is generated by intermediate results of cipher text processing and with unique delta value at each session.(7)Newkey=IRC1031:16IRC515:0IRC1015:0IRC531:16.Therefore, related key attack is overcome by the proposed architecture.


## 4.1. Formal Analysis

Formal analysis is the art of analyzing a deficiency in the designed protocols that are not directly apparent through cryptanalysis. A five-step procedure was suggested for applying the formal verification functions in the RFID designs [40]. Formal analysis works under the principle of belief analysis, and based on that request/response communication between the tag and the reader is evaluated. This function examines the plain message formation and succession of communication between the transaction groups to assess the protocol’s potential on epitomized level efficiently. The BAN logic is deployed for verifying our RXMAP protocol.


### 4.1.1. BAN Logic Analysis

This logic was formulated by Burrows et al. [41]. This logic was used to rationale authentication protocols among contenders in a distributed processing system. The precepts used in BAN logic analysis [42] are explained below with equations. The notions and corresponding descriptions of the notions that are used for BAN logic analysis [43] are tabulated in Table 2.Table 2
Notions and descriptions used for BAN logic analysis.
NotionsExplanationsP or QPandQ are the principal that refers to a sender or receiver. For instance, the tag or the readerP∣≡XP believes the statement XP⊲XP sees the statement X#XThe formulaX is freshP∣~XP once said the statement XX,YEither formulaX or Y is one section of formula X,YP∣⇒XP has control over statement XXYX is integrated with formula YP↔KQShared keyK is used for communication between P and Q. K will be known only to these two entitiesNKEYThis denotes the new key generated for further updating and processingThe BAN logic rules have been applied for the proposed RXMAP protocol for the abstract level evaluation. These rules are tabulated in Table3.Table 3
The BAN model rules applied for the proposed RXMAP protocol.
BAN logic rulesRules applied for the proposed RXMAP protocolMessage-meaning rule (M)Case (1)T∣≡R↔RST,T⊲CPWDLRRM/T≡R~CPWDLRCase (2) R∣≡T↔RTR,R⊲CPWDLTRT/R∣≡T∣~CPWDLTNonce-verification rule (NV)Case (1)T∣≡#CPWDLR,T∣≡R∣~CPWDLR/T≡R≡CPWDLRCase (2) R∣≡#CPWDLT,R∣≡T∣~CPWDLT/R∣≡T∣≡CPWDLTJurisdiction rule (J)Case (1)T∣≡R⟹CPWDLR,T∣≡R∣≡CPWDLR/T∣≡CPWDLRCase (2) R∣≡T⟹CPWDLT,R∣≡T∣≡CPWDLT/R∣≡CPWDLTFreshness rule (F)Case (1)T∣≡#RT/T∣≡#CPWDLT,RTCase (2) R∣≡#RS/R∣≡#CPWDLR,RSOther inference rules (I)Case (1)T⊲CPWDLR,RS/T⊲CPWDLRCase (2) R⊲CPWDLT,RT/R⊲CPWDLTFrom [42], goals for achieving mutual authentication for a protocol are derived. In the proposed protocol, the mutual authentication phase takes place only after the translated cover-coded password exchange between the tag and the reader. A successful translated cover-coded password exchange indicates a successful protocol run for one session. Therefore, if mutual authentication is verified through BAN logic, then, the protocol run is also verified simultaneously. Hence, these goals are targeted to achieve the protocol evaluation. Mutual authentication is accomplished between two principles A and B if K is existing such that
(5)A∣≡A↔KB,B∣≡A↔KB,A≡B≡A↔KB,B≡A≡A↔KB.The first two are believed to be essential for any protocol to be mutually authenticated. Assumptions, according to the proposed protocol in order to acquire the above goals, are formulated as mentioned below. Besides, it is assumed that the tag hasRS,RT,andPWD (KEY) and the reader has RS,RT,andPWD (KEY). The server is considered a secure channel and hence not included in the analysis. PWD is retrieved with pseudonym IDS which is updated after each session. T principle denotes the tag, and R principle denotes the reader.
(6)A1:T⇒RT,A2:T≡#RT,A3:R⇒RS,A4:R≡#RS,A5:T≡T↔PWDR,A6:R≡T↔PWDR.Messages that are communicated betwixt the tag and the reader in the RXMAP run are as follows:Message 1:R⟶T:CPWDLRPWD,RT,TriggerRT.Message 2:T⟶R:IDS,CPWDLTPWD,RSFrom the reader to tag,CPWDLR is an encrypted message transmitted. This CPWDLR is encrypted using PWD, RT, and RS. Trigger is sent from the reader to tag to initiate the key update process. Trigger is interleaved and translated version of RT and RS. Similarly, from the tag to reader CPWDLT is the encrypted message that is encrypted using PWD, RT, and RS.As mentioned earlier, the RXMAP protocol should satisfy the following goals for mutual authentication analysis:G1: R≡T≡T↔NKEYRG2:T∣≡R∣≡T↔NKEYRBased on the above assumptions and rules, it is witnessed that the RXMAP protocol attains the goals for mutual authentication and they are provided with multiple steps below.S1:AccordingtoMessage1andruleI1,T⊲CPWDLRPWD,RT,RSBy assumption A1 and A2 and ruleF (2),S2:T∣≡#CPWDLRPWD,RT,RSFrom assumptions A1 and A2 and statement S1 and ruleM (1), T∣≡R∣~CPWDLRPWD,RT,RSS3:T∣≡R⇒CPWDLRPWD,RT,RSBy statement S2, statement S3, and rule NV (1),S4:T≡R≡CPWDLRPWD,RT,RSAccording to statement S3, statement S4, and ruleJ (1), T∣≡CPWDLRPWD,RT,RS.Therefore, from statement S4 and statement S5, it can be stated asS6:T≡R≡T↔NKEYRS7: According to the proposed protocol,NKEYIRC10,IRC5Hence, from statement S1 to statement S7, it is evident thatT∣≡R∣≡↔NKEYR⟶ (G2 i.e. goal 2 satisfied)From Message 2 and rule I (2), it can be stated thatS8:R⊲CPWDLTPWD,RT,RSFrom the assumptions A3 and A4, and from rule F (2), it can be stated thatS9:R∣≡#CPWDLTPWD,RT,RSBy the assumptions A3 and A6 and from the statement S8 and rule M (2), it can be stated thatS10:R≡T~CPWDLTPWD,RT,RSR≡T⇒CPWDLTPWD,RT,RSFrom statements S9 and S10 and from rule NV (2), the following statement can be obtained:S11:R∣≡T∣≡CPWDLTPWD,RT,RSFrom statements S10 and S11 and from ruleJ (2), it can be stated thatS12:R∣≡CPWDLTPWD,RT,RSTherefore, from statements S11 and S12, it is obvious that statement S13 can be formulated asS13:R≡T≡T↔NKEYRS14: According to the RXMAP protocol,NKEYIRC10,IRC5Hence, from statement S8 to statement S14, it is apparent thatR∣≡T∣≡T↔NKEYR⟶(G1 i.e. goal 1 satisfied)Hence, from goals G1 and G2, formal analysis with BAN logic for the RXMAP protocol has been done.


## 4.1.1. BAN Logic Analysis

This logic was formulated by Burrows et al. [41]. This logic was used to rationale authentication protocols among contenders in a distributed processing system. The precepts used in BAN logic analysis [42] are explained below with equations. The notions and corresponding descriptions of the notions that are used for BAN logic analysis [43] are tabulated in Table 2.Table 2
Notions and descriptions used for BAN logic analysis.
NotionsExplanationsP or QPandQ are the principal that refers to a sender or receiver. For instance, the tag or the readerP∣≡XP believes the statement XP⊲XP sees the statement X#XThe formulaX is freshP∣~XP once said the statement XX,YEither formulaX or Y is one section of formula X,YP∣⇒XP has control over statement XXYX is integrated with formula YP↔KQShared keyK is used for communication between P and Q. K will be known only to these two entitiesNKEYThis denotes the new key generated for further updating and processingThe BAN logic rules have been applied for the proposed RXMAP protocol for the abstract level evaluation. These rules are tabulated in Table3.Table 3
The BAN model rules applied for the proposed RXMAP protocol.
BAN logic rulesRules applied for the proposed RXMAP protocolMessage-meaning rule (M)Case (1)T∣≡R↔RST,T⊲CPWDLRRM/T≡R~CPWDLRCase (2) R∣≡T↔RTR,R⊲CPWDLTRT/R∣≡T∣~CPWDLTNonce-verification rule (NV)Case (1)T∣≡#CPWDLR,T∣≡R∣~CPWDLR/T≡R≡CPWDLRCase (2) R∣≡#CPWDLT,R∣≡T∣~CPWDLT/R∣≡T∣≡CPWDLTJurisdiction rule (J)Case (1)T∣≡R⟹CPWDLR,T∣≡R∣≡CPWDLR/T∣≡CPWDLRCase (2) R∣≡T⟹CPWDLT,R∣≡T∣≡CPWDLT/R∣≡CPWDLTFreshness rule (F)Case (1)T∣≡#RT/T∣≡#CPWDLT,RTCase (2) R∣≡#RS/R∣≡#CPWDLR,RSOther inference rules (I)Case (1)T⊲CPWDLR,RS/T⊲CPWDLRCase (2) R⊲CPWDLT,RT/R⊲CPWDLTFrom [42], goals for achieving mutual authentication for a protocol are derived. In the proposed protocol, the mutual authentication phase takes place only after the translated cover-coded password exchange between the tag and the reader. A successful translated cover-coded password exchange indicates a successful protocol run for one session. Therefore, if mutual authentication is verified through BAN logic, then, the protocol run is also verified simultaneously. Hence, these goals are targeted to achieve the protocol evaluation. Mutual authentication is accomplished between two principles A and B if K is existing such that
(5)A∣≡A↔KB,B∣≡A↔KB,A≡B≡A↔KB,B≡A≡A↔KB.The first two are believed to be essential for any protocol to be mutually authenticated. Assumptions, according to the proposed protocol in order to acquire the above goals, are formulated as mentioned below. Besides, it is assumed that the tag hasRS,RT,andPWD (KEY) and the reader has RS,RT,andPWD (KEY). The server is considered a secure channel and hence not included in the analysis. PWD is retrieved with pseudonym IDS which is updated after each session. T principle denotes the tag, and R principle denotes the reader.
(6)A1:T⇒RT,A2:T≡#RT,A3:R⇒RS,A4:R≡#RS,A5:T≡T↔PWDR,A6:R≡T↔PWDR.Messages that are communicated betwixt the tag and the reader in the RXMAP run are as follows:Message 1:R⟶T:CPWDLRPWD,RT,TriggerRT.Message 2:T⟶R:IDS,CPWDLTPWD,RSFrom the reader to tag,CPWDLR is an encrypted message transmitted. This CPWDLR is encrypted using PWD, RT, and RS. Trigger is sent from the reader to tag to initiate the key update process. Trigger is interleaved and translated version of RT and RS. Similarly, from the tag to reader CPWDLT is the encrypted message that is encrypted using PWD, RT, and RS.As mentioned earlier, the RXMAP protocol should satisfy the following goals for mutual authentication analysis:G1: R≡T≡T↔NKEYRG2:T∣≡R∣≡T↔NKEYRBased on the above assumptions and rules, it is witnessed that the RXMAP protocol attains the goals for mutual authentication and they are provided with multiple steps below.S1:AccordingtoMessage1andruleI1,T⊲CPWDLRPWD,RT,RSBy assumption A1 and A2 and ruleF (2),S2:T∣≡#CPWDLRPWD,RT,RSFrom assumptions A1 and A2 and statement S1 and ruleM (1), T∣≡R∣~CPWDLRPWD,RT,RSS3:T∣≡R⇒CPWDLRPWD,RT,RSBy statement S2, statement S3, and rule NV (1),S4:T≡R≡CPWDLRPWD,RT,RSAccording to statement S3, statement S4, and ruleJ (1), T∣≡CPWDLRPWD,RT,RS.Therefore, from statement S4 and statement S5, it can be stated asS6:T≡R≡T↔NKEYRS7: According to the proposed protocol,NKEYIRC10,IRC5Hence, from statement S1 to statement S7, it is evident thatT∣≡R∣≡↔NKEYR⟶ (G2 i.e. goal 2 satisfied)From Message 2 and rule I (2), it can be stated thatS8:R⊲CPWDLTPWD,RT,RSFrom the assumptions A3 and A4, and from rule F (2), it can be stated thatS9:R∣≡#CPWDLTPWD,RT,RSBy the assumptions A3 and A6 and from the statement S8 and rule M (2), it can be stated thatS10:R≡T~CPWDLTPWD,RT,RSR≡T⇒CPWDLTPWD,RT,RSFrom statements S9 and S10 and from rule NV (2), the following statement can be obtained:S11:R∣≡T∣≡CPWDLTPWD,RT,RSFrom statements S10 and S11 and from ruleJ (2), it can be stated thatS12:R∣≡CPWDLTPWD,RT,RSTherefore, from statements S11 and S12, it is obvious that statement S13 can be formulated asS13:R≡T≡T↔NKEYRS14: According to the RXMAP protocol,NKEYIRC10,IRC5Hence, from statement S8 to statement S14, it is apparent thatR∣≡T∣≡T↔NKEYR⟶(G1 i.e. goal 1 satisfied)Hence, from goals G1 and G2, formal analysis with BAN logic for the RXMAP protocol has been done.


## 4.2. Informal Analysis

In this section, the proposed RXMAP protocol is verified against variant possible security requirements, threats, and attacks.


### 4.2.1. Security against the Tag’s Identity Reveal

In the message communication of the proposed protocol, tag’s ID is not revealed in any mean. The pseudonym IDS combined with RT {IDS||RT} is only used for the transaction, and it is renewed for each process. So it is impossible to get the ID of the tag. Hence, RXMAP is secured against the tag’s identity reveal.


### 4.2.2. Resistance to Known Session-Specific Temporary Information Attack

This attack happens when the adversary happened to get intermediate session specific information and tried to retrace the useful information of the protocol scheme. In our work, the communication messages {RS||CPWDLR}, CPWDLT, and Trigger are generated from the temporary random numbers. Moreover, messages are of different sizes that are 64 bits and 32 bits. This is not at all sufficient for tracing the tag or server information, so it is resistant to known session-specific temporary information attacks.


### 4.2.3. Mutual Authentication

Mutual authentication is essential for communication and data transfer to happen between tags and readers. A step by step verification of authentication of tags and server is presented in Section3.2. It also narrates the termination of invalid tag and invalid servers at various stages. Our protocol offers mutual authentication among the valid devices in the network.


### 4.2.4. Forward and Backward Security

The communication messages {RS||CPWDLR}, CPWDLT, and Trigger are of sizes 64 bits, 32 bits, and 32 bits, respectively. The actual key size used in the encryption process is of 128-bit size. In addition with that, intermediate messages are generated through the session-specific random numbers. There is no possibility of finding trace of the previous or next session key. It is highly impossible to guess the 128-bit value from the 32-bit value.


### 4.2.5. Resistance to Replay Attack

This attack can happen when the intruder eavesdrops on any of the intermediate information to take the communication further in later point of time. This is a risky thing in many applications. In our protocol, each message at a specific time depends on the random numbers generated at that specific session. Since previous session’s messages are not useful to perform replay, it is resilient to replay attack.


### 4.2.6. Resistance against Impersonation Attack

In order to impersonate the reader/tag adversary, we need to know the structure of the encoder in either side. Moreover, the intermediate messages are generated based on RS, RT, IDS, and key. None of the details needed for the computation and the domain-specific architecture of the encoder are available with the intruder to impersonate in between. Thus, the proposed protocol is tolerant against impersonation attack from either side.


### 4.2.7. Security against Man-In-The-Middle Attack

This attack may be performed by the privileged mediator trying to extract the tag or readers’ identity so that the entire system becomes under the control of the intruder. This attack was there with the XTEA architecture. In our domain-specific customized RXMAP architecture, we introduced the dynamically changing “delta” value, “IDS” values, and “key” values based on the random numbers at each session. So, it is unpredictable in nature and information that the privileged mediator is subject to change for every session. Hence, the proposed architecture and protocol inherit the resistance against the man-in-the-middle attack.


### 4.2.8. Resistance to Masquerade Attack

An attacker may able to make the communication protocol to reveal the tag secret key by repeatedly sending the messages to the reader. This kind of repeated action will not be able to get the unique tag ID, because pseudonym was only used in each transaction also generated from the random numbers as follows:IDS=CPWDMR/T31:16‖RS31:16‖RT15:0‖CPWDMR/T15:0. Thus, no information can be cracked. The intruder cannot do replay attack, also due the IDS’s freshness. Hence, the proposed scheme is resistant to masquerade attack and denial of service (DoS).


### 4.2.9. Resistance to Desynchronization Attack

Desynchronization attack focuses on disassociating the tag from the communication thereby leading to DoS. This is effectively handled in the proposed protocol by means of storing old and new IDs and key of the specific tag in the server and maintaining the freshness in the communication messages and values involved in by generating new random numbers RS and RT for each session. The proposed protocol uses verification message and acknowledges message to update the key and IDS values in either side. CPWDLR was used for verifying the server at the tag side, and CPWDLT was sent by the tag in response to act like an acknowledgement for the server and uses it for tag authentication. Key update will happen at the tag side upon receiving trigger acknowledge signal from the server.Here, desynchronization attack may be applied at step 9 to disassociate the tag from the server. But in the proposed RXMAP, we stored old and new details of the tag in the server. So once the attack happens, the tag will never get permanently disassociated from the server; rather, it will start the communication fresh with its old IDS and key. Therefore, the proposed scheme is versatile against the desynchronization attack.


### 4.2.10. Anonymity and Untraceability

In the proposed protocol, IDS is not separately sent. Rather, it is sent along with the random number RT as IDS||RT. It is difficult to differentiate the random number RT and the IDS since both are random and regenerated for every session. Hence, it is anonyms to the attacker if he wants to get the identity of the tag, and it is untraceable.


### 4.2.11. Related Key Attack

This is one of the weaknesses of the XTEA. The related key attack may be tried with the partial known part of the key in the transaction. The proposed RXMAP encoder architecture patched this weakness by randomizing the delta which involved in the calculation of sum and ciphered text. Another fact is that the key is rejuvenated in a highly random fashion since it is generated by intermediate results of cipher text processing and with unique delta value at each session.(7)Newkey=IRC1031:16IRC515:0IRC1015:0IRC531:16.Therefore, related key attack is overcome by the proposed architecture.


## 4.2.1. Security against the Tag’s Identity Reveal

In the message communication of the proposed protocol, tag’s ID is not revealed in any mean. The pseudonym IDS combined with RT {IDS||RT} is only used for the transaction, and it is renewed for each process. So it is impossible to get the ID of the tag. Hence, RXMAP is secured against the tag’s identity reveal.


## 4.2.2. Resistance to Known Session-Specific Temporary Information Attack

This attack happens when the adversary happened to get intermediate session specific information and tried to retrace the useful information of the protocol scheme. In our work, the communication messages {RS||CPWDLR}, CPWDLT, and Trigger are generated from the temporary random numbers. Moreover, messages are of different sizes that are 64 bits and 32 bits. This is not at all sufficient for tracing the tag or server information, so it is resistant to known session-specific temporary information attacks.


## 4.2.3. Mutual Authentication

Mutual authentication is essential for communication and data transfer to happen between tags and readers. A step by step verification of authentication of tags and server is presented in Section3.2. It also narrates the termination of invalid tag and invalid servers at various stages. Our protocol offers mutual authentication among the valid devices in the network.


## 4.2.4. Forward and Backward Security

The communication messages {RS||CPWDLR}, CPWDLT, and Trigger are of sizes 64 bits, 32 bits, and 32 bits, respectively. The actual key size used in the encryption process is of 128-bit size. In addition with that, intermediate messages are generated through the session-specific random numbers. There is no possibility of finding trace of the previous or next session key. It is highly impossible to guess the 128-bit value from the 32-bit value.


## 4.2.5. Resistance to Replay Attack

This attack can happen when the intruder eavesdrops on any of the intermediate information to take the communication further in later point of time. This is a risky thing in many applications. In our protocol, each message at a specific time depends on the random numbers generated at that specific session. Since previous session’s messages are not useful to perform replay, it is resilient to replay attack.


## 4.2.6. Resistance against Impersonation Attack

In order to impersonate the reader/tag adversary, we need to know the structure of the encoder in either side. Moreover, the intermediate messages are generated based on RS, RT, IDS, and key. None of the details needed for the computation and the domain-specific architecture of the encoder are available with the intruder to impersonate in between. Thus, the proposed protocol is tolerant against impersonation attack from either side.


## 4.2.7. Security against Man-In-The-Middle Attack

This attack may be performed by the privileged mediator trying to extract the tag or readers’ identity so that the entire system becomes under the control of the intruder. This attack was there with the XTEA architecture. In our domain-specific customized RXMAP architecture, we introduced the dynamically changing “delta” value, “IDS” values, and “key” values based on the random numbers at each session. So, it is unpredictable in nature and information that the privileged mediator is subject to change for every session. Hence, the proposed architecture and protocol inherit the resistance against the man-in-the-middle attack.


## 4.2.8. Resistance to Masquerade Attack

An attacker may able to make the communication protocol to reveal the tag secret key by repeatedly sending the messages to the reader. This kind of repeated action will not be able to get the unique tag ID, because pseudonym was only used in each transaction also generated from the random numbers as follows:IDS=CPWDMR/T31:16‖RS31:16‖RT15:0‖CPWDMR/T15:0. Thus, no information can be cracked. The intruder cannot do replay attack, also due the IDS’s freshness. Hence, the proposed scheme is resistant to masquerade attack and denial of service (DoS).


## 4.2.9. Resistance to Desynchronization Attack

Desynchronization attack focuses on disassociating the tag from the communication thereby leading to DoS. This is effectively handled in the proposed protocol by means of storing old and new IDs and key of the specific tag in the server and maintaining the freshness in the communication messages and values involved in by generating new random numbers RS and RT for each session. The proposed protocol uses verification message and acknowledges message to update the key and IDS values in either side. CPWDLR was used for verifying the server at the tag side, and CPWDLT was sent by the tag in response to act like an acknowledgement for the server and uses it for tag authentication. Key update will happen at the tag side upon receiving trigger acknowledge signal from the server.Here, desynchronization attack may be applied at step 9 to disassociate the tag from the server. But in the proposed RXMAP, we stored old and new details of the tag in the server. So once the attack happens, the tag will never get permanently disassociated from the server; rather, it will start the communication fresh with its old IDS and key. Therefore, the proposed scheme is versatile against the desynchronization attack.


## 4.2.10. Anonymity and Untraceability

In the proposed protocol, IDS is not separately sent. Rather, it is sent along with the random number RT as IDS||RT. It is difficult to differentiate the random number RT and the IDS since both are random and regenerated for every session. Hence, it is anonyms to the attacker if he wants to get the identity of the tag, and it is untraceable.


## 4.2.11. Related Key Attack

This is one of the weaknesses of the XTEA. The related key attack may be tried with the partial known part of the key in the transaction. The proposed RXMAP encoder architecture patched this weakness by randomizing the delta which involved in the calculation of sum and ciphered text. Another fact is that the key is rejuvenated in a highly random fashion since it is generated by intermediate results of cipher text processing and with unique delta value at each session.(7)Newkey=IRC1031:16IRC515:0IRC1015:0IRC531:16.Therefore, related key attack is overcome by the proposed architecture.


## 5. Evaluation of the RXMAP Protocol

The evaluation of the propounded RXMAP protocol is done on the basis of security requirements, computation overhead, and storage requirements to ensure its strength and lightweight to deploy it in the green energy devices.


### 5.1. Security Requirements

In this section, the evaluation of the RXMAP protocol for its resistance against security issues is presented. From the analysis at Section4, it is inferred that the proposed protocol withstands various security threats and cryptanalysis models. Table 4 formed below provides the evaluation of our proposed RXMAP protocol against various security requirements, threats, and cryptanalysis models in comparison with the existing protocols.Table 4
Performance evaluation of the RXMAP against the security requirements, threats, and cryptanalysis models.
ProtocolSR1SR2SR3SR4SR5SR6SR7SR8SR9SR10SR11Liu et al. [24]YNAYYYNANANAYYNAAssidi et al. [20]YNAYYYNANANAYNANAFan et al. [23]YNAYYYNANANAYYNAAyebie and Souidi [21]NANAYYYNANANAYYNAIzza et al. [22]YYYYYYYYYYNAProposed RXMAP protocolYYYYYYYYYYYSR1: security against the tag’s identity reveal; SR2: resistance to known session-specific temporary information attack; SR3: mutual authentication; SR4: forward and backward security; SR5: resistance to replay attack; SR6: resistance against impersonation attack; SR7: security against man-in-the-middle attack; SR8: resistance to masquerade attack; SR9: resistance to desynchronization attack; SR10: anonymity and untraceability; SR11: related key attack.From Table4, it is clear that our proposed RXMAP outperforms other existing protocols with a simple architecture. Works listed for comparison in Table 4 are used complex algorithms to ensure the security, but the proposed work uses the approximate computing blocks to address the issues without adding any additional complex functions, so the architecture of the proposed RXMAP is simple.


### 5.2. Computation Overhead

Computation over the head of the RXMAP in the tag side is given in Table5, respectively.Table 5
Comparison of computation overhead of the tag with some lightweight protocols.
ParameterLiu et al. [24]Assidi et al. [20]Fan et al. `[23]Ayebie and Souidi [21]Izza et al. [22]Proposed RXMAP protocolTypes of computationQC-MDPC encoderAGS-based encoder⊕, rot, per symmetric key encryption algorithmHash, rank metric coderHash, elliptic curveXTEA approximate addersCommunication messages (in bytes)18322740192105224816From Table5, it is certain that the computational complexity of the proposed protocol in the tag side is much less and a number of bytes transacted are also a few and it is 100 times lesser than other protocols.


### 5.3. Storage Requirement

The storage requirement of the tag is one of the pivotal deciding factors of the cost and size of the tag. Table6 represents the comparison of storage requirement of the proposed protocol with the recent lightweight protocols in the literature.Table 6
Comparison of storage requirement of the tag with some lightweight protocols.
ParameterLiu et al. [24]Assidi et al. [20]Fan et al. [23]Ayebie and Souidi [21]Izza et al. [22]Proposed RXMAP protocolStorage requirement (in bytes)6161735635112444The proposed protocol needs 92%, 74%,21.43%, 87.5%, and 64.5% lesser storage compared to Liu, Assidi, Fan, Ayebie, and Izza et al.’s protocols, respectively.


## 5.1. Security Requirements

In this section, the evaluation of the RXMAP protocol for its resistance against security issues is presented. From the analysis at Section4, it is inferred that the proposed protocol withstands various security threats and cryptanalysis models. Table 4 formed below provides the evaluation of our proposed RXMAP protocol against various security requirements, threats, and cryptanalysis models in comparison with the existing protocols.Table 4
Performance evaluation of the RXMAP against the security requirements, threats, and cryptanalysis models.
ProtocolSR1SR2SR3SR4SR5SR6SR7SR8SR9SR10SR11Liu et al. [24]YNAYYYNANANAYYNAAssidi et al. [20]YNAYYYNANANAYNANAFan et al. [23]YNAYYYNANANAYYNAAyebie and Souidi [21]NANAYYYNANANAYYNAIzza et al. [22]YYYYYYYYYYNAProposed RXMAP protocolYYYYYYYYYYYSR1: security against the tag’s identity reveal; SR2: resistance to known session-specific temporary information attack; SR3: mutual authentication; SR4: forward and backward security; SR5: resistance to replay attack; SR6: resistance against impersonation attack; SR7: security against man-in-the-middle attack; SR8: resistance to masquerade attack; SR9: resistance to desynchronization attack; SR10: anonymity and untraceability; SR11: related key attack.From Table4, it is clear that our proposed RXMAP outperforms other existing protocols with a simple architecture. Works listed for comparison in Table 4 are used complex algorithms to ensure the security, but the proposed work uses the approximate computing blocks to address the issues without adding any additional complex functions, so the architecture of the proposed RXMAP is simple.


## 5.2. Computation Overhead

Computation over the head of the RXMAP in the tag side is given in Table5, respectively.Table 5
Comparison of computation overhead of the tag with some lightweight protocols.
ParameterLiu et al. [24]Assidi et al. [20]Fan et al. `[23]Ayebie and Souidi [21]Izza et al. [22]Proposed RXMAP protocolTypes of computationQC-MDPC encoderAGS-based encoder⊕, rot, per symmetric key encryption algorithmHash, rank metric coderHash, elliptic curveXTEA approximate addersCommunication messages (in bytes)18322740192105224816From Table5, it is certain that the computational complexity of the proposed protocol in the tag side is much less and a number of bytes transacted are also a few and it is 100 times lesser than other protocols.


## 5.3. Storage Requirement

The storage requirement of the tag is one of the pivotal deciding factors of the cost and size of the tag. Table6 represents the comparison of storage requirement of the proposed protocol with the recent lightweight protocols in the literature.Table 6
Comparison of storage requirement of the tag with some lightweight protocols.
ParameterLiu et al. [24]Assidi et al. [20]Fan et al. [23]Ayebie and Souidi [21]Izza et al. [22]Proposed RXMAP protocolStorage requirement (in bytes)6161735635112444The proposed protocol needs 92%, 74%,21.43%, 87.5%, and 64.5% lesser storage compared to Liu, Assidi, Fan, Ayebie, and Izza et al.’s protocols, respectively.


## 6. ASIC Implementation of the RXMAP Encoder Architecture

The proposed RXMAP protocol is simulated with ModelSim 10.5b edition, and ASIC implementation is done in an OpenLane silicon-proven tool with the 130 nm logic process. The layout diagram of the proposed RXMAP-1 and RXMAP-2 is presented in Figure3. ASIC implemented parameters are listed in Table 7.Figure 3
The layout diagrams of the proposed RXMAP encoder architectures: (a) proposed RXMAP-1 encoder and (b) proposed RXMAP-2 encoder.
(a)(b)Table 7
Comparison of ASIC implemented proposed RXMAP architecture with the standard XTEA.
AlgorithmBlock sizeLogic processGECycles/blockThroughput @ 100 kHzThroughput/areaPower (μW)XTEA I [19]64130 nm350024026.70.00818.8XTEA II [19]64130 nm349011257.10.01619.5RXMAP-164130 nm164124026.70.0166.09RXMAP-264130 nm163424026.70.0165.53Table7 represents the through put and area in terms of gate equivalents (GE). In comparison, it is proved that the proposed designs RXMAP I and RXMAP II occupy 53.11% and 53.31% lesser area compared to XTEA I and 52.97% and 53.18% lesser area compared to XTEA II implementation.From the parameter throughput at 100 kHz, it is clear that XTEA II overcomes other implementations, but the throughput per area of the fast implementation XTEA II and the proposed architectures RXMAP-1 and RXMAP-2 are equal while consuming 68.76% and 71.64% less power than XTEA II implementation, respectively. The proposed architectures show much improved power and throughput per area performance compared to XTEA I implementation. From this comparison, it is evident that the proposed RXMAP encoder architectures are the best fit for the portable low-energy applications.


## 7. Conclusion

The use of wireless sensor network applications in a day to day life is inevitable right from sophisticated systems to life-saving systems such as health care monitoring. Security and energy consumption problems are essentially addressed in this field. Our article suggested the solution for the power and security requirements of the RFID and wireless sensor network applications. The proposed RXMAP encoder architecture patches the security issues in one of the most commonly used the lightweight XTEA algorithm and secured it from the related key attack and man-in-the-middle attack. The proposed domain-specific approximate adders OOA and XOA further made the modified XTEA architecture lighter in terms of computation and area. The proposed protocol is validated against various security threats through both formal and informal verifications. ASIC implementation results prove that the proposed designs RXMAP I and RXMAP II occupy 53.11% and 53.31% lesser area compared to XTEA I and 52.97% and 53.18% lesser area compared to XTEA II implementation. The total power consumed by the proposed encoder architectures RXMAP-1 and RXMAP-2 is 68.76% and 71.64% lesser than XTEA II implementation, respectively, while maintaining the equal throughput. These results ensure that the proposed RXMAP encoder architecture and protocol are the best fit for RFID and green wireless sensor network applications. The proposed domain-specific customization of the architectures could be extended further for other lightweight protocols to reduce the computational and storage complexity.



---

*Source: 8876096-2022-03-10.xml*