KR20210133017A - Electronic device performing integrity verification and method for operating thereof - Google Patents

Abstract

According to various embodiments, an electronic device includes at least one processor. The at least one processor can be configured to receive a first message from a network, perform deciphering on a first part of the first message, perform a first integrity check on a second part for confirming the integrity of the deciphered first part, and determine, based on a result of the first integrity check, whether there is a mismatch between a hyper frame number (HFN) of the electronic device and an HFN of the network. Other embodiments are also possible.

Description

Electronic device for performing integrity check and method of operation thereof

Various embodiments relate to an electronic device that performs an integrity check and a method of operating the same.

As the use of portable terminals having various functions has become common due to the recent development of mobile communication technology, efforts are being made to develop a 5G communication system to meet the increasing demand for wireless data traffic. In addition to the frequency bands used by 3G and LTE (e.g., bands below 6 GHz), the 5G communication system provides a higher frequency band (e.g., implementations in bands above 6 GHz) are also being considered.

A user equipment (UE) may transmit and receive packets to and from a network. A packet based on a packet data convergence protocol (PDCP) protocol data unit (PDU) may be transmitted and received between the user equipment and the network. For uplink (UL) and downlink (DL), a hyper frame number (HFN) value is set in the PDCP PDU. A count (COUNT) is set based on the HFN value and a sequence number (SN) included in the header of the PDCP PDU. The user equipment and/or the network may use the count to perform an operation for in-order delivery of the PDCP PDU. The user device and/or the network may use the count to perform integrity verification and/or ciphering/deciphering.

When the user equipment and the network perform communication, there may be a case where the HFN managed by the transmitter and the HFN managed by the receiver are different. If the HFNs are different, deciphering and/or integrity verification may fail. Since the count may be set by the HFN, a difference between the HFN of the transmitting entity and the HFN of the receiving entity may cause a difference between the count of the transmitting entity and the count of the receiving entity. In particular, even if an error does not occur in the SN in the PDU, a difference in count may be caused. Depending on the difference in counts, when deciphering and/or integrity verification fails, a transmitted/received packet may be discarded.

The electronic device and the method of operating the same according to various embodiments of the present disclosure may perform an operation for resolving the inconsistency by checking that HFNs corresponding to each of the transmitting and receiving subjects do not match.

According to various embodiments, an electronic device includes at least one processor, wherein the at least one processor receives a first message from a network, performs deciphering on a first portion of the first message, and A first integrity check is performed on a second part for confirming the integrity of the deciphered first part, and based on the result of the first integrity check, a hyper frame number (HFN) of the electronic device and an HFN of the network It can be set to determine whether there is a discrepancy between them. Various other embodiments are possible.

According to various embodiments, a method of operating an electronic device includes receiving a first message from a network, performing deciphering on a first part of the first message, and checking the integrity of the deciphered first part. performing a first integrity check on the second part for may include.

According to various embodiments, an electronic device capable of performing an operation for resolving inconsistency by checking that HFNs corresponding to a transmitting entity and a receiving entity do not match may be provided, and an operating method thereof. Accordingly, packet discard due to HFN mismatch may be reduced.

1 is a block diagram of an electronic device in a network environment, according to various embodiments of the present disclosure;
2A is a block diagram of an electronic device for supporting network communication and 5G network communication, according to various embodiments of the present disclosure;
3 illustrates a protocol structure according to various embodiments.
4 is a diagram for explaining an operation of a PDCP layer according to various embodiments.
5A is a view for explaining a ciphering and deciphering process according to various embodiments.
5B illustrates a format of a count in accordance with various embodiments.
5C is a diagram for explaining an integrity verification process according to various embodiments.
6A is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
6B illustrates a PDCP control PDU (PDCP control PDU) format for a PDCP status report according to various embodiments.
7 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
8A is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
8B illustrates a format of a PDCP data PDU according to various embodiments.
9 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
10A is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
10B is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
11 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
12A is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
12B is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
13 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
14A is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
14B is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
15 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
16A and 16B are examples of received PDUs and counts according to various embodiments.
17 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
18 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;
19 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

1 is a block diagram of an electronic device 101 in a network environment 100 according to various embodiments. Referring to FIG. 1 , in a network environment 100 , an electronic device 101 communicates with an electronic device 102 through a first network 198 (eg, a short-range wireless communication network) or a second network 199 . It may communicate with the electronic device 104 or the server 108 through (eg, a long-distance wireless communication network). According to an embodiment, the electronic device 101 may communicate with the electronic device 104 through the server 108 . According to an embodiment, the electronic device 101 includes a processor 120 , a memory 130 , an input device 150 , a sound output device 155 , a display device 160 , an audio module 170 , and a sensor module ( 176 , interface 177 , haptic module 179 , camera module 180 , power management module 188 , battery 189 , communication module 190 , subscriber identification module 196 , or antenna module 197 . ) may be included. In some embodiments, at least one of these components (eg, the display device 160 or the camera module 180 ) may be omitted or one or more other components may be added to the electronic device 101 . In some embodiments, some of these components may be implemented as one integrated circuit. For example, the sensor module 176 (eg, a fingerprint sensor, an iris sensor, or an illuminance sensor) may be implemented while being embedded in the display device 160 (eg, a display).

The processor 120, for example, executes software (eg, the program 140) to execute at least one other component (eg, a hardware or software component) of the electronic device 101 connected to the processor 120 . It can control and perform various data processing or operations. According to one embodiment, as at least part of data processing or operation, the processor 120 converts commands or data received from other components (eg, the sensor module 176 or the communication module 190 ) to the volatile memory 132 . may be loaded into the volatile memory 132 , process commands or data stored in the volatile memory 132 , and store the resulting data in the non-volatile memory 134 . According to an embodiment, the processor 120 includes a main processor 121 (eg, a central processing unit or an application processor), and a secondary processor 123 (eg, a graphics processing unit, an image signal processor) that can be operated independently or in conjunction with the main processor 121 . , a sensor hub processor, or a communication processor). Additionally or alternatively, the auxiliary processor 123 may be configured to use less power than the main processor 121 or to be specialized for a designated function. The auxiliary processor 123 may be implemented separately from or as a part of the main processor 121 .

The auxiliary processor 123 may be, for example, on behalf of the main processor 121 while the main processor 121 is in an inactive (eg, sleep) state, or when the main processor 121 is active (eg, executing an application). ), together with the main processor 121, at least one of the components of the electronic device 101 (eg, the display device 160, the sensor module 176, or the communication module 190) It is possible to control at least some of the related functions or states. According to an embodiment, the coprocessor 123 (eg, an image signal processor or a communication processor) may be implemented as part of another functionally related component (eg, the camera module 180 or the communication module 190). have.

The memory 130 may store various data used by at least one component of the electronic device 101 (eg, the processor 120 or the sensor module 176 ). The data may include, for example, input data or output data for software (eg, the program 140 ) and instructions related thereto. The memory 130 may include a volatile memory 132 or a non-volatile memory 134 .

The program 140 may be stored as software in the memory 130 , and may include, for example, an operating system 142 , middleware 144 , or an application 146 .

The input device 150 may receive a command or data to be used by a component (eg, the processor 120 ) of the electronic device 101 from the outside (eg, a user) of the electronic device 101 . The input device 150 may include, for example, a microphone, a mouse, a keyboard, or a digital pen (eg, a stylus pen).

The sound output device 155 may output a sound signal to the outside of the electronic device 101 . The sound output device 155 may include, for example, a speaker or a receiver. The speaker can be used for general purposes such as multimedia playback or recording playback, and the receiver can be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from or as part of the speaker.

The display device 160 may visually provide information to the outside (eg, a user) of the electronic device 101 . The display device 160 may include, for example, a display, a hologram device, or a projector and a control circuit for controlling the corresponding device. According to an embodiment, the display device 160 may include a touch circuitry configured to sense a touch or a sensor circuit (eg, a pressure sensor) configured to measure the intensity of a force generated by the touch. .

The audio module 170 may convert a sound into an electric signal or, conversely, convert an electric signal into a sound. According to an embodiment, the audio module 170 acquires a sound through the input device 150 , or an external electronic device (eg, a sound output device 155 ) connected directly or wirelessly with the electronic device 101 . The sound may be output through the electronic device 102 (eg, a speaker or a headphone).

The sensor module 176 detects an operating state (eg, power or temperature) of the electronic device 101 or an external environmental state (eg, user state), and generates an electrical signal or data value corresponding to the sensed state. can do. According to an embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, a humidity sensor, or an illuminance sensor.

The interface 177 may support one or more specified protocols that may be used by the electronic device 101 to directly or wirelessly connect with an external electronic device (eg, the electronic device 102 ). According to an embodiment, the interface 177 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

The connection terminal 178 may include a connector through which the electronic device 101 can be physically connected to an external electronic device (eg, the electronic device 102 ). According to an embodiment, the connection terminal 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

The haptic module 179 may convert an electrical signal into a mechanical stimulus (eg, vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic sense. According to an embodiment, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

The camera module 180 may capture still images and moving images. According to an embodiment, the camera module 180 may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module 188 may manage power supplied to the electronic device 101 . According to an embodiment, the power management module 188 may be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

The battery 189 may supply power to at least one component of the electronic device 101 . According to one embodiment, battery 189 may include, for example, a non-rechargeable primary cell, a rechargeable secondary cell, or a fuel cell.

The communication module 190 is a direct (eg, wired) communication channel or a wireless communication channel between the electronic device 101 and an external electronic device (eg, the electronic device 102, the electronic device 104, or the server 108). It can support establishment and communication through the established communication channel. The communication module 190 may include one or more communication processors that operate independently of the processor 120 (eg, an application processor) and support direct (eg, wired) communication or wireless communication. According to one embodiment, the communication module 190 is a wireless communication module 192 (eg, a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 194 (eg, : It may include a local area network (LAN) communication module, or a power line communication module). A corresponding communication module among these communication modules is a first network 198 (eg, a short-range communication network such as Bluetooth, Wi-Fi direct, or infrared data association (IrDA)) or a second network 199 (eg, a cellular network, the Internet). , or through a computer network (eg, a telecommunication network such as a LAN or WAN) to communicate with an external electronic device. These various types of communication modules may be integrated into one component (eg, a single chip) or may be implemented as a plurality of components (eg, multiple chips) separate from each other. The wireless communication module 192 uses the subscriber information (eg, International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 196 within a communication network such as the first network 198 or the second network 199 . The electronic device 101 may be identified and authenticated.

The antenna module 197 may transmit or receive a signal or power to the outside (eg, an external electronic device). According to an embodiment, the antenna module 197 may include one antenna including a conductor formed on a substrate (eg, a PCB) or a radiator formed of a conductive pattern. According to one embodiment, the antenna module 197 may include one or more antennas. In this case, at least one antenna suitable for a communication scheme used in a communication network such as the first network 198 or the second network 199 is connected from the one or more antennas by, for example, the communication module 190 . can be selected. A signal or power may be transmitted or received between the communication module 190 and an external electronic device through the selected at least one antenna. According to some embodiments, other components (eg, RFIC) other than the radiator may be additionally formed as a part of the antenna module 197 .

At least some of the components are connected to each other through a communication method between peripheral devices (eg, a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)) and a signal ( eg commands or data) can be exchanged with each other.

According to an embodiment, the command or data may be transmitted or received between the electronic device 101 and the external electronic device 104 through the server 108 connected to the second network 199 . Each of the external electronic devices 102 and 104 may be the same as or different from the electronic device 101 . According to an embodiment, all or a part of operations executed in the electronic device 101 may be executed in one or more of the external electronic devices 102 , 104 , or 108 . For example, when the electronic device 101 needs to perform a function or service automatically or in response to a request from a user or other device, the electronic device 101 may perform the function or service itself instead of executing the function or service itself. Alternatively or additionally, one or more external electronic devices may be requested to perform at least a part of the function or the service. The one or more external electronic devices that have received the request may execute at least a part of the requested function or service, or an additional function or service related to the request, and transmit a result of the execution to the electronic device 101 . The electronic device 101 may process the result as it is or additionally and provide it as at least a part of a response to the request. For this purpose, for example, cloud computing, distributed computing, or client-server computing technology may be used.

2A is a block diagram 200 of an electronic device 101 for supporting network communication and 5G network communication, according to various embodiments. Referring to FIG. 2A , the electronic device 101 includes a first communication processor 212 , a second communication processor 214 , a first radio frequency integrated circuit (RFIC) 222 , a second RFIC 224 , and a third RFIC 226 , a fourth RFIC 228 , a first radio frequency front end (RFFE) 232 , a second RFFE 234 , a first antenna module 242 , a second antenna module 244 , and an antenna (248). The electronic device 101 may further include a processor 120 and a memory 130 . The network 199 may include a first network 292 and a second network 294 . According to another embodiment, the electronic device 101 may further include at least one component among the components illustrated in FIG. 1 , and the network 199 may further include at least one other network. According to one embodiment, a first communication processor 212 , a second communication processor 214 , a first RFIC 222 , a second RFIC 224 , a fourth RFIC 228 , a first RFFE 232 , and the second RFFE 234 may form at least a part of the wireless communication module 192 . According to another embodiment, the fourth RFIC 228 may be omitted or may be included as a part of the third RFIC 226 .

The first communication processor 212 may support establishment of a communication channel of a band to be used for wireless communication with the first network 292 and legacy network communication through the established communication channel. According to various embodiments, the first network may be a legacy network including a second generation (2G), 3G, 4G, or long term evolution (LTE) network. The second communication processor 214 establishes a communication channel corresponding to a designated band (eg, about 6 GHz to about 60 GHz) among bands to be used for wireless communication with the second network 294 , and 5G network communication through the established communication channel can support According to various embodiments, the second network 294 may be a 5G network defined by 3GPP. Additionally, according to an embodiment, the first communication processor 212 or the second communication processor 214 is configured to correspond to another designated band (eg, about 6 GHz or less) among bands to be used for wireless communication with the second network 294 . It is possible to support establishment of a communication channel, and 5G network communication through the established communication channel.

The first communication processor 212 may transmit/receive data to and from the second communication processor 214 . For example, data that was classified to be transmitted over the second cellular network 294 may be changed to be transmitted over the first cellular network 292 . In this case, the first communication processor 212 may receive transmission data from the second communication processor 214 .

For example, the first communication processor 212 may transmit/receive data through the interface 213 between the second communication processor 214 and the processor. The interprocessor interface 213 may be implemented as, for example, a universal asynchronous receiver/transmitter (UART) (eg, high speed-UART (HS-UART) or peripheral component interconnect bus express (PCIe)) interface, but the There is no restriction on the type. Alternatively, the first communication processor 212 and the second communication processor 214 may exchange control information and packet data information using, for example, a shared memory. The first communication processor 212 may transmit/receive various information to and from the second communication processor 214 , such as sensing information, information on output strength, and resource block (RB) allocation information.

Depending on the implementation, the first communication processor 212 may not be directly connected to the second communication processor 214 . In this case, the first communication processor 212 may transmit and receive data through the second communication processor 214 and the processor 120 (eg, an application processor). For example, the first communication processor 212 and the second communication processor 214 may transmit and receive data with the processor 120 (eg, an application processor) through the HS-UART interface or the PCIe interface, but There is no restriction on the type. Alternatively, the first communication processor 212 and the second communication processor 214 may exchange control information and packet data information using a shared memory with the processor 120 (eg, an application processor). .

According to one embodiment, the first communication processor 212 and the second communication processor 214 may be implemented in a single chip or a single package. According to various embodiments, the first communication processor 212 or the second communication processor 214 may be formed in a single chip or a single package with the processor 120 , the coprocessor 123 , or the communication module 190 . have. For example, as shown in FIG. 2B , the unified communication processor 260 may support both functions for communication with the first cellular network and the second cellular network.

The first RFIC 222, when transmitting, transmits a baseband signal generated by the first communication processor 212 to about 700 MHz to about 3 GHz used in the first network 292 (eg, a legacy network). can be converted to a radio frequency (RF) signal of Upon reception, an RF signal is obtained from a first network 292 (eg, a legacy network) via an antenna (eg, a first antenna module 242 ), and via an RFFE (eg, a first RFFE 232 ). It can be preprocessed. The first RFIC 222 may convert the preprocessed RF signal into a baseband signal to be processed by the first communication processor 212 .

The second RFIC 224, when transmitting, transmits the baseband signal generated by the first communication processor 212 or the second communication processor 214 to the second network 294 (eg, a 5G network). It can be converted into an RF signal (hereinafter, 5G Sub6 RF signal) of the Sub6 band (eg, about 6 GHz or less). Upon reception, a 5G Sub6 RF signal is obtained from a second network 294 (eg, 5G network) via an antenna (eg, second antenna module 244 ), and RFFE (eg, second RFFE 234 ) can be pre-processed. The second RFIC 224 may convert the preprocessed 5G Sub6 RF signal into a baseband signal to be processed by a corresponding one of the first communication processor 212 or the second communication processor 214 .

The third RFIC 226 transmits the baseband signal generated by the second communication processor 214 to the RF of the 5G Above6 band (eg, about 6 GHz to about 60 GHz) to be used in the second network 294 (eg, 5G network). It can be converted into a signal (hereinafter referred to as 5G Above6 RF signal). Upon reception, a 5G Above6 RF signal may be obtained from the second network 294 (eg, 5G network) via an antenna (eg, antenna 248 ) and pre-processed via a third RFFE 236 . The third RFIC 226 may convert the preprocessed 5G Above6 RF signal into a baseband signal to be processed by the second communication processor 214 . According to one embodiment, the third RFFE 236 may be formed as part of the third RFIC 226 .

According to an embodiment, the electronic device 101 may include the fourth RFIC 228 separately from or as at least a part of the third RFIC 226 . In this case, the fourth RFIC 228 converts the baseband signal generated by the second communication processor 214 into an RF signal (hereinafter, IF signal) of an intermediate frequency band (eg, about 9 GHz to about 11 GHz). After conversion, the IF signal may be transmitted to the third RFIC 226 . The third RFIC 226 may convert the IF signal into a 5G Above6 RF signal. Upon reception, a 5G Above6 RF signal may be received from the second network 294 (eg, 5G network) via an antenna (eg, antenna 248 ) and converted into an IF signal by a third RFIC 226 . . The fourth RFIC 228 may convert the IF signal into a baseband signal for processing by the second communication processor 214 .

According to an embodiment, the first RFIC 222 and the second RFIC 224 may be implemented as at least a part of a single chip or a single package. According to an embodiment, the first RFFE 232 and the second RFFE 234 may be implemented as at least a part of a single chip or a single package. According to an embodiment, at least one antenna module of the first antenna module 242 or the second antenna module 244 may be omitted or may be combined with another antenna module to process RF signals of a plurality of corresponding bands.

According to an embodiment, the third RFIC 226 and the antenna 248 may be disposed on the same substrate to form the third antenna module 246 . For example, the wireless communication module 192 or the processor 120 may be disposed on the first substrate (eg, main PCB). In this case, the third RFIC 226 is located in a partial area (eg, the bottom surface) of the second substrate (eg, sub PCB) that is separate from the first substrate, and the antenna 248 is located in another partial region (eg, the top surface). is disposed, the third antenna module 246 may be formed. By disposing the third RFIC 226 and the antenna 248 on the same substrate, it is possible to reduce the length of the transmission line therebetween. This, for example, can reduce loss (eg, attenuation) of a signal in a high-frequency band (eg, about 6 GHz to about 60 GHz) used for 5G network communication by a transmission line. Accordingly, the electronic device 101 may improve the quality or speed of communication with the second network 294 (eg, a 5G network).

According to an embodiment, the antenna 248 may be formed as an antenna array including a plurality of antenna elements that can be used for beamforming. In this case, the third RFIC 226 may include, for example, as a part of the third RFFE 236 , a plurality of phase shifters 238 corresponding to a plurality of antenna elements. During transmission, each of the plurality of phase shifters 238 may transform the phase of a 5G Above6 RF signal to be transmitted to the outside of the electronic device 101 (eg, a base station of a 5G network) through a corresponding antenna element. . Upon reception, each of the plurality of phase shifters 238 may convert the phase of the 5G Above6 RF signal received from the outside through a corresponding antenna element into the same or substantially the same phase. This enables transmission or reception through beamforming between the electronic device 101 and the outside.

The second network 294 (eg, 5G network) may be operated independently (eg, Stand-Alone (SA)) or connected to the first network 292 (eg, legacy network) (eg: Non-Stand Alone (NSA)). For example, the 5G network may have only an access network (eg, 5G radio access network (RAN) or next generation RAN (NG RAN)) and no core network (eg, next generation core (NGC)). In this case, after accessing the access network of the 5G network, the electronic device 101 may access an external network (eg, the Internet) under the control of a core network (eg, evolved packed core (EPC)) of the legacy network. Protocol information for communication with a legacy network (eg, LTE protocol information) or protocol information for communication with a 5G network (eg, New Radio (NR) protocol information) is stored in the memory 130 , and other components (eg, processor 120 , the first communication processor 212 , or the second communication processor 214 ).

2A and 2B , the processor 120 is shown as separate from the first communication processor 212 , the second communication processor 214 , or the unified communication processor 260 , but this is merely exemplary. In various embodiments, the electronic device 101 provides a function of the processor 120 , a function for a first network communication of the first communication processor 212 , and a function for a second network communication of the second communication processor 214 . It may include an integrated system on chip (SoC) that supports both. It will be understood by those skilled in the art that operations of the processor 120 , the first communication processor 212 , or the second communication processor 214 in this document may be performed by an integrated SoC.

Alternatively, although not shown, an embodiment of the disclosure may also be applied to the electronic device 101 supporting only LTE communication. In this case, the electronic device 101 includes a processor 120 and/or a first communication processor 212 , a first RFIC 222 , a first RFFE 232 , and a first antenna module 242 . and 5G communication-related components (eg, the second RFIC 224 , the second RFFE 234 , the second antenna module 244 , the second communication processor 214 , the fourth RFIC 238 , the third At least one of the antenna modules 246) may be implemented not to include.

3 illustrates a protocol structure according to various embodiments.

According to various embodiments, a protocol structure corresponding to the electronic device 101 (eg, UE) may include a PDCP layer 301 , a radio link control (RLC) layer 302 , a MAC layer 303 , and a PHY layer ( 304) can be configured. A protocol structure corresponding to a network (eg, a base station) may include a PDCP layer 311 , an RLC layer 312 , a MAC layer 313 , and a PHY layer 314 .

The PDCP layers 301 and 311 may be in charge of operations such as IP header compression/restore. The main functions of the PDCP layers 301 and 311 can be summarized as follows.

- Header compression and decompression (ROHC only)

- User data transfer function (transfer of user data)

- In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM)

- Order reordering function (for split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

- Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

- Retransmission function (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

- Encryption and decryption function (ciphering and deciphering)

- Timer-based SDU discard function (timer-based SDU discard in uplink.)

The RLC layers 302 and 312 may perform an operation such as an ARQ function by reconfiguring a PDCP packet data unit (PDU) to an appropriate size. The main functions of the RLC layers 302 and 312 can be summarized as follows.

- Data transfer function (transfer of upper layer PDUs)

- ARQ function (error correction through ARQ (only for AM data transfer))

- Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer)

- Re-segmentation of RLC data PDUs (only for AM data transfer)

- Reordering of RLC data PDUs (only for UM and AM data transfer)

- Duplicate detection (only for UM and AM data transfer)

- Protocol error detection (only for AM data transfer)

- RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))

- RLC re-establishment function (RLC re-establishment)

The MAC layers 303 and 313 are connected to several RLC layer devices configured in one terminal, and may perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of the MAC layers 303 and 313 can be summarized as follows.

- Mapping function (mapping between logical channels and transport channels)

- Multiplexing and demultiplexing function (multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels)

- Scheduling information reporting function (scheduling information reporting)

- HARQ function (error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification

- Transport format selection

- Padding function

Physical (PHY) layers 304 and 314 channel-code and modulate upper layer data, make OFDM symbols and transmit them over a wireless channel, or demodulate OFDM symbols received through a wireless channel, decode channels, and deliver to the upper layers. can be done

4 is a diagram for explaining an operation of a PDCP layer according to various embodiments.

According to various embodiments, the transmitting PDCP entity 410 may receive the SDU 431 and output the PDU 432 . The receiving PDCP entity 420 may receive the PDU 432 and output the SDU 431 . The PDCP entities 410 and 420 may be located in the PDCP layer. In FIG. 4 , the PDU 432 is shown as being transmitted directly from the transmitting PDCP entity 410 to the receiving PDCP entity 420 via a radio interface (UU) 434 , but this is not described For the convenience of , those skilled in the art will understand that the PDU 432 is transmitted through the RLC layer, the MAC layer, and the physical layer.

According to various embodiments, the transmitting-side PDCP entity 410 may perform sequence numbering on the SDU 431 in a transmission buffer in operation 411 . For example, the transmitting PDCP entity 410 may assign an SN to the SDU 431 . The transmitting-side PDCP entity 410 may perform header compression on the SDU 431 in operation 412 . The transmitting-side PDCP entity 410 may perform an integrity protection procedure in operation 413 when a packet to be transmitted is associated with a PDCP SDU (Packets associated to a PDCP SDU). The transmitting-side PDCP entity 410 may perform ciphering on a data block generated as a result of performing the integrity protection procedure in operation 414 . The transmitting-side PDCP entity 410 may perform add PDCP header in operation 415 . When the packet is not associated with a PDCP SDU (Packets not associated to a PDCP SDU), the transmitting-side PDCP entity 410 may directly add a PDCP header without performing integrity protection and ciphering. The transmitting-side PDCP entity 410 may perform routing/duplication of the PDU 432 in operation 416 .

According to various embodiments, the receiving-side PDCP entity 420 may remove a PDCP header 421 from the received PDU 432 in operation 421 . The receiving-side PDCP entity 420 may perform deciphering in operation 422 and integrity verification in operation 423 . The receiving-side PDCP entity 420, in operation 424, performs at least one of reordering, duplicating, or discarding a data block for which integrity verification has been completed in a reception buffer. , can be transmitted to a higher layer. The receiving-side PDCP entity 420 may perform header decompression in operation 425 . If the packet is not related to the PDCP SDU, the receiving-side PDCP entity 420 may perform header decompression after removing the PDCP header. The receiving-side PDCP entity 420 may transmit the header decompressed SDU 433 to a higher layer.

5A is a view for explaining a ciphering and deciphering process according to various embodiments.

According to various embodiments, the transmitting-side PDCP entity 410 may perform ciphering as in operation 414 of FIG. 4 . Referring to FIG. 5A , the transmitting-side PDCP entity (eg, the transmitting-side PDCP entity 410 of FIG. 4 ) includes a cipher key (KEY) (eg, 128 bits), a count (COUNT) (eg, 32). bit), bearer identity (BEARER) (eg 5 bits), DIRECTION (eg 1 bit), length of keystream required (LENGTH), NEA (NR encryption algorithm). As for the transmission direction (DIRECTION), UL may be 0 and DL may be 1. The transmitting-side PDCP entity 410 may check a key stream block (KEYSTREAM BLOCK) as an output value of the NEA. Among the values input to the NEA, the count COUNT may vary for each packet. For example, FIG. 5B illustrates the format of a count in accordance with various embodiments. The count may be composed of, for example, a hyper frame number (HFN) and a PDCP sequence number (PDCP sequence number). The HFN may be maintained by the transmitting PDCP entity and the receiving PDCP entity, and the SN may be included in the PDU. The count may have, for example, a length of 32 bits, and the length of the HFN may be a value obtained by subtracting the PDCP SN length from 32. The PDCP SN may be incremented by one every time a PDU is transmitted one by one. In addition, when the PDCP SN reaches the maximum value, the PDCP SN may later return to the starting value, and HFN may increase by 1. Accordingly, the count COUNT may be set differently for each packet, and keystream blocks that are NEA result values may also be set differently for each packet. The transmitting-side PDCP entity 410 may provide a ciphertext block (CIPHERTEXT BLOCK) based on a plaintext block (PLAINTEXT BLOCK) and a key stream block (KEYSTREAM BLOCK). For example, the transmitting-side PDCP entity 410 may provide a ciphertext block (CIPHERTEXT BLOCK) by performing an operation (eg, binary addition) of a plaintext block (PLAINTEXT BLOCK) and a key stream block (KEYSTREAM BLOCK). , there is no limitation on the type of operation.

According to various embodiments, the receiving-side PDCP entity (eg, the receiving-side PDCP entity 420 of FIG. 4 ) may perform deciphering as in operation 422 of FIG. 4 . The receiving-side PDCP entity 420 includes a cipher key (KEY) (eg, 128 bits), a count (COUNT) (eg, 32 bits), a bearer identity (BEARER) (eg, 5 bits). ), transmission direction (eg, 1 bit), length of keystream required (LENGTH), and NEA (NR encryption algorithm) can be input. The receiving-side PDCP entity 420 may identify a key stream block (KEYSTREAM BLOCK) as an output value of the NEA. The receiving-side PDCP entity 420 may check the plaintext block PLAINTEXT BLOCK based on the operation of the key stream block KEYSTREAM BLOCK and the received ciphertext block CIPHERTEXT BLOCK. The receiving-side PDCP entity 420 may, for example, be the reverse of the operation in the transmitting-side PDCP entity 410, and there is no limitation. If the counts (COUNT) checked by the transmitting-side PDCP entity 410 and the receiving-side PDCP entity 420 are different, the receiving-side PDCP entity 420 may fail deciphering.

5C is a diagram for describing an integrity protection operation and verification according to various embodiments.

According to various embodiments, the transmitting-side PDCP entity 410 may perform an integrity protection operation as in operation 413 of FIG. 4 . Referring to FIG. 5C , the transmitting-side PDCP entity 410 includes an integrity key (KEY) (eg, 128 bits), a count (COUNT) (eg, 32 bits), a bearer identity (BEARER). ) (eg, 5 bits), transmission direction (eg, 1 bit), and message (MESSAGE) can be input as NIA (NR integrity algorithm). The bit length of the message (MESSAGE) may be LENGTH. As for the transmission direction (DIRECTION), UL may be 0 and DL may be 1. The transmitting-side PDCP entity 410 may identify MAC-I/NAS-MAC as an output value of NIA. Among the values inputted to the NIA, a count (COUNT) may be different for each packet, and MAC-I/NAS-MAC, which is a result value of the NIA, may also be set differently for each packet. MAC-I/NAS-MAC may be a 32-bit message identification code. MAC-I/NAS-MAC may be appended to the message at the time of transmission.

According to various embodiments, the receiving-side PDCP entity 420 may perform integrity verification as in operation 424 of FIG. 4 . The receiving-side PDCP entity 420 includes an integrity key (KEY) (eg, 128 bits), a count (COUNT) (eg, 32 bits), a bearer identity (BEARER) (eg, 5 bits). ), transmission direction (eg, 1 bit), and message (MESSAGE) can be entered as NIA. The receiving-side PDCP entity 420 may identify the XMAC-I/XNAS-MAC as an output value of the NIA. XMAC-I/XNAS-MAC may be an expected message authentication code. The receiving-side PDCP entity 420 checks that integrity verification is successful if the MAC-I/NAS-MAC received from the transmitting-side PDCP entity 410 and the calculated XMAC-I/XNAS-MAC are the same. It can be confirmed that the integrity verification has failed. If the counts (COUNT) checked by the transmitting-side PDCP entity 410 and the receiving-side PDCP entity 420 are different, the receiving-side PDCP entity 420 may fail integrity verification.

6A is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure; The embodiment of FIG. 6A will be described with reference to FIG. 6B. 6B illustrates a PDCP control PDU (PDCP control PDU) format for a PDCP status report according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , in operation 601 , a first message indicating a PDCP state may be received from the network. The electronic device 101 may receive, for example, a PDCP control PDU for a PDCP status report from the network. For example, the electronic device 101 may receive a PDCP control PDU for PDCP status report upon handover, but there is no limitation on the reception time. For example, the electronic device 101 may receive a PDCP control PDU having the format shown in FIG. 6B . Referring to FIG. 6B , the PDCP control PDU may consist of one or more octets (8 bits). The first octet Oct1 may include a data/control (D/C) field 621 , a PDU type field 622 , and a reserved field 623 . The value of the D/C field 621 may indicate whether the corresponding PDU is a data PDU or a control PDU. A value of the PDU type field 622 may indicate a PDU type, for example, a value of 000 may indicate a PDCP status report type. A first missing count (FMC) field 624 may be included in the second octet (Oct2) to the fifth octet (Oct4), that is, 40 bits, and the value in the FMC field 624 is determined by the receiving PDCP entity in the reordering window. It may indicate the count of PDUs not initially received. A bitmap field 625 may be included in the sixth octet (Oct 6) to the fifth +N octet (Oct 5_N). The length of the bitmap field 625 may be variable and may indicate whether a PDU corresponding to a subsequent count value is received/not received from the FMC, but there is no limitation.

According to various embodiments, in operation 603 , the electronic device 101 may check an initial non-reception count of the network. For example, the electronic device 101 may check the initial non-receipt count based on the value of the FMC field 624 of the PDCP control PDU of FIG. 6B .

According to various embodiments, in operation 605 , the electronic device 101 may compare a count of a message scheduled to be transmitted and an initial not-received count. The electronic device 101, for example, the transmitting PDCP entity, may maintain the following state variables.

a)TX_NEXT: This state variable may indicate the count value of the next PDCP SDU to be transmitted, and the initial value may be set to 0.

For example, the electronic device 101 may compare the state variable of TX_NEXT with the initial non-receipt count. In operation 607 , the electronic device 101 may adjust the count of messages scheduled to be transmitted based on the comparison result. For example, when the initial non-received count (eg, FMC) of the network is greater than the count of messages scheduled to be transmitted (eg, TX_NEXT), the electronic device 101 may be set to adjust the message count scheduled to be transmitted. . This may be due to an error occurring in the electronic device 101 or at least one of the network as the network expects a larger count than the count of the message to be transmitted. Or, for example, when the count (eg, TX_NEXT) of the message to be transmitted is greater than the initial non-received count (eg, FMC) of the network, for example, when TX_NEXT is greater than the sum of the FMC and the specified value, the electronic device 101 can be set to adjust the message count to be sent. In general, the count of messages scheduled to be transmitted may be greater than the initial unreceived count. However, when the count of messages scheduled to be transmitted is greater than the initial non-received count, for example, greater than a specified value, this may be due to an error occurring in at least one of the electronic device 101 or the network. Hereinafter, an adjustment process for each of the above-described embodiments will be described.

7 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , in operation 701 , a first message indicating a PDCP state may be received from the network. For example, the electronic device 101 may receive a PDCP control PDU having the format shown in FIG. 6B . In operation 703 , the electronic device 101 may check the initial non-receipt count of the network. For example, the electronic device 101 may check the initial non-receipt count based on the value of the FMC field 624 of the PDCP control PDU having the format shown in FIG. 6B .

According to various embodiments, in operation 705 , the electronic device 101 may determine that the count of the message scheduled to be transmitted is less than (or less than) the initial non-received count. For example, the electronic device 101 may check that the FMC in which the TX_NEXT is received is smaller (or less than) during management. In operation 707 , the electronic device 101 may adjust the count of the message scheduled to be transmitted to the initial non-received count. The electronic device 101 may adjust, for example, TX_NEXT to the received FMC.

8A is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure; The embodiment of FIG. 8A will be described with reference to FIG. 8B. 8B illustrates a format of a PDCP data PDU according to various embodiments.

In FIG. 8A , operations of transmitting an uplink message of the electronic device 101 to the network 800 are illustrated.

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , 801, the SN portion of TX_NEXT may be set (or maintained) to A1-1. A-1, A1, and A2 described in FIG. 8A may be SNs, for example, a value corresponding to a natural number and may follow the format set in the PDCP SN field 833 of FIG. 8B. In operation 803 , the electronic device 101 may transmit the first PDU (PDU #1) to the network 800 . The SN of the first PDU (PDU #1) may be A1-1. For example, the electronic device 101 may transmit a PDCP data PDU having the format shown in FIG. 8B to the network 800 . A PDCP data PDU may be configured to have N octets, for example. The first octet (Oct1) may include a part of a data/control (D/C) field 831 , a reserved field 832 , and a PDCP SN field 833 , and the second octet (Oct2) and the second octet (Oct2) The remainder of the PDCP SN field 833 may be included in 3 octets (Oct3). The value of the D/C field 831 may indicate whether the corresponding PDU is a data PDU or a control PDU. A data field 834 may be included in the fourth octet (Oct 4) to the N-4 th octet. A MAC-I field 835 may optionally be included in the N-3 th octet (Oct N-3) to the N th octet (Oct 4). For example, in operation 803 , the electronic device 101 may transmit a first PDU (PDU #1) including a bit indicating A1-1 in the PDCP SN field 833 to the network 800 .

According to various embodiments, after transmitting the first PDU (PDU #1), the electronic device 101 may update TX_NEXT in operation 805 . For example, the electronic device 101 may increase the SN portion of TX_NEXT to A1 by 1 compared to the existing one. For example, the example of FIG. 8A assumes that the HFN remains unchanged. According to various embodiments, the electronic device 101 may receive a control PDU of the PDCP status report from the network 800 in operation 807 . For example, the electronic device 101 may receive a control PDU in which the SN portion of the FMC field 624 of FIG. 6B is A2. It is assumed that the FMC of the Control PDU is greater than (or greater than) TX_NEXT.

According to various embodiments, the electronic device 101 may update TX_NEXT to the received FMC based on that the FMC of the Control PDU is greater than (or greater than) TX_NEXT in operation 807 . Accordingly, the SN of the updated TX_NEXT may be A2. The electronic device 101 may then transmit the second PDU (PDU #2) to the network 800 in operation 811 . The SN of the second PDU (PDU #2) may be set to A2 instead of A1. The network 800 may accordingly not discard packets until a PDU of the expected SN has been received.

9 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure; In FIG. 9 , operations of transmitting an uplink message of the electronic device 101 to the network 800 are illustrated.

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) is , in operation 901 , a first message indicating a PDCP state may be received from the network 800 . For example, the electronic device 101 may receive a PDCP control PDU having the format shown in FIG. 6B . In operation 903 , the electronic device 101 may check the initial non-receipt count of the network. For example, the electronic device 101 may check the initial non-receipt count based on the value of the FMC field 624 of the PDCP control PDU having the format shown in FIG. 6B .

According to various embodiments, in operation 905 , the electronic device 101 may confirm that the count of the message scheduled to be transmitted and the initial non-received count satisfy at least one of at least one specified condition. For example, the electronic device 101 determines whether the first condition among the at least one condition is satisfied, and determines whether the count of the message scheduled to be transmitted is less than (or less than) the initial non-received count. can be checked Alternatively, the electronic device 101 may determine whether the count of messages scheduled to be transmitted is greater than the initial non-received count by a specified value or more as an operation of determining whether a second condition among at least one condition is satisfied. For example, the electronic device 101 may determine whether Equation 1 is satisfied as whether the second condition is satisfied.

TX_NEXT in Equation 1 may be TX_NEXT managed by the electronic device 101 , and the FMC may be an FMC received by the electronic device 101 . Whether the value of TX_NEXT - X in Equation 1 is greater than FMC may be changed depending on whether the value of TX_NEXT - X is greater than FMC. X in Equation 1, in one example, may be set based on the number of PDUs that may be delivered during a reordering timer. X may be set, for example, based on Equation (2).

Max throughput in Equation 2 is maximum throughput, MTU size is the size of a maximum transmission unit (MTU), and the reordering timer may be the time of the reordering timer. For example, if Max throughput is 100Mbps, MTU size is 1500Byte, and reordering timer is 100ms, X may be 100,000,000 / (1500Bytes*8bit) * 0.1 = 833. If the reordering timer is 0, the electronic device 101 may identify X by applying a specified value (eg, 1 ms) of the reordering timer to Equation 2 .

According to various embodiments, X may be set according to bandwidth information of a cell in which a packet is being serviced, for example, as shown in Table 1.

Bandwidth 5 10 15 20 25 30 40 X 800 1600 2400 3200 4000 4800 6400 Bandwidth 50 60 80 90 100 200 400 X 8000 9600 12800 14400 16000 32000 64000

According to various embodiments, X may be set according to Max throughput, for example, as shown in Table 2.

Max Throughput(X) 100 200 300 400 500 600 800 X 800 1600 2400 3200 4000 4800 6400 Max Throughput(X) 1000 1200 1600 1800 2000 4000 8000 X 8000 9600 12800 14400 16000 32000 64000

In various embodiments, X may be a designated constant.

According to various embodiments, the electronic device 101 checks that at least one condition (eg, the first condition and/or the second condition described above) is satisfied, and based on this, in operation 907 , a radio (RLF) link failure) procedure to adjust the count of messages scheduled to be transmitted. The electronic device 101 may prevent data stall through connection reconnection and may resolve counter mismatch.

10A is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) is , 1001 , it may be confirmed that the count of the message scheduled to be transmitted and the initial non-received count satisfy at least one of at least one specified condition. For example, as described with reference to FIG. 9 , the electronic device 101 may confirm that TX_NEXT and FMC satisfy Equation 1 or Equation 2, for example.

According to various embodiments, the electronic device 101 may declare the RLF in operation 1003 . For example, the electronic device 101 may perform at least one operation set in response to the RLF. When a problem occurs in an unacknowledged mode (UM) bearer, the electronic device 101 may perform an RRC reestablishment procedure. For example, the electronic device 101 may perform cell selection in operation 1005 . The electronic device 101 may perform cell selection on the basis that a measurement result of the network 800 (eg, a cell) satisfies a cell selection condition. The electronic device 101 may camp on, for example, a suitable cell. In operation 1007 , the electronic device 101 may transmit a random access preamble to the camped-on cell. In operation 1009 , the electronic device 101 may receive a random access response from the camped-on cell. In operation 1011 , the electronic device 101 may transmit an RRC reestablishment request. In operation 1013 , the network 800 may transmit an RRC reestablishment to the electronic device 101 . In operation 1015 , the electronic device 101 may transmit an RRC reestablishment complete to the network 800 . The network 800 may transmit an RRC reconfiguration to the electronic device 101 in operation 1017 . The electronic device 101 may transmit an RRC reconfiguration complete to the network 800 in operation 1019 . In the case of a UM bearer, since TX_NEXT is initialized during PDCP re-establishment, a count mismatch between the electronic device 101 and the network 800 may be resolved.

10B is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , 1021 , it may be confirmed that the count of the message scheduled to be transmitted and the initial non-received count satisfy at least one of at least one specified condition. For example, as described with reference to FIG. 9 , the electronic device 101 may confirm that TX_NEXT and FMC satisfy Equation 1 or Equation 2, for example.

According to various embodiments, the electronic device 101 may declare the RLF in operation 1023 . For example, the electronic device 101 may perform at least one operation set in response to the RLF. When a problem occurs in the acknowledged mode (AM) bearer, the electronic device 101 may transition to the RRC_IDLE state and reconnect the RRC connection with respect to data generated thereafter through a SERVICE REQEUST procedure. For example, in operation 1025 , the electronic device 101 may perform cell selection in an idle state (eg, an RRC_IDLE state). In operation 1027 , the electronic device 101 may transmit a random access preamble to the network 800 (eg, a suitable cell) camped on as a result of the cell selection. In operation 1029 , the network 800 may transmit a random access response to the electronic device 101 .

According to various embodiments, in operation 1031 , the electronic device 101 may transmit an RRC connection request including a SERVICE REQUEST to the network 800 . The network 800 may transmit an RRC setup to the electronic device 101 in operation 1033 . In operation 1035 , the electronic device 101 may transmit an RRC setup complete to the network 800 . In operation 1037 , the network 800 may transmit an RRC reconfiguration to the electronic device 101 . In operation 1039 , the electronic device 101 may transmit an RRC connection complete to the network 800 . In the AM bearer, since TX_NEXT is not initialized during PDCP re-establishment, the count mismatch between the electronic device 101 and the network 800 may be resolved through the above-described method.

11 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , in operation 1101 , a first message indicating a PDCP status may be received from the network 800 . In operation 1103 , the electronic device 101 may check the initial non-receipt count of the network 800 . For example, the electronic device 101 may receive a PDCP control PDU having the format shown in FIG. 6B . In operation 1103 , the electronic device 101 may check the initial non-receipt count of the network. For example, the electronic device 101 may check the initial non-receipt count based on the value of the FMC field 624 of the PDCP control PDU having the format shown in FIG. 6B . In operation 1105 , the electronic device 101 may confirm that the count of the message scheduled to be transmitted and the initial non-received count satisfy at least one of at least one specified condition. For example, as described with reference to FIG. 9 , the electronic device 101 may confirm that TX_NEXT and FMC satisfy Equation 1 or Equation 2, for example.

According to various embodiments, the electronic device 101 may transmit a PDU requesting recovery to the network 800 in operation 1107 . For example, the electronic device 101 may transmit a control PDU having the format shown in FIG. 6B to the network 800 . The electronic device 101 may transmit a control PDU including a recovery request value (eg, 010) to the network 800 in the PDU type field 622 of the format shown in FIG. 6B . “010” indicates, for example, PDCP recovery required, and may be shared by the electronic device 101 and the network 800 . Accordingly, the network 800 may check whether the electronic device 101 requests recovery according to the count mismatch. When the recovery request is confirmed, the network 800 may perform recovery by re-establishing the PDCP through RRC reconfiguration.

12A is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , 1201 , it may be confirmed that the count of the message scheduled to be transmitted and the initial non-received count satisfy at least one of at least one specified condition. For example, as described with reference to FIG. 9 , the electronic device 101 may confirm that TX_NEXT and FMC satisfy, for example, Equation 1 or Equation 2

According to various embodiments, the electronic device 101 may transmit a recovery request PDU (eg, PDCP Control PDU with PDU type Bit 010, PDCP Recovery required) to the network 800 in operation 1203 . For example, when a problem in the UM bearer is detected, the electronic device 101 transmits a control PDU including a recovery request value (eg, 010) in the PDU type field 622 of the format shown in FIG. 6B to the network. (800). In operation 1205 , the network 800 may transmit an RRC reconfiguration message (eg, RRC reconfiguration with reestablishPDCP for the UM bearer) to the electronic device 101 . In operation 1207 , the electronic device 101 may transmit an RRC reconfiguration complete message to the network 800 . Accordingly, the electronic device 101 and the network 800 may reset the count through PDCP reformation, and the count mismatch may be resolved.

12B is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , 1211 , it may be confirmed that the count of the message scheduled to be transmitted and the initial non-received count satisfy at least one of at least one specified condition. For example, as described with reference to FIG. 9 , the electronic device 101 may confirm that TX_NEXT and FMC satisfy, for example, Equation 1 or Equation 2

According to various embodiments, the electronic device 101 may transmit a recovery request PDU (eg, PDCP Control PDU with PDU type Bit 010, PDCP Recovery required) to the network 800 in operation 1213 . For example, when a problem in the AM bearer is detected, the electronic device 101 transmits a control PDU including a recovery request value (eg, 010) in the PDU type field 622 of the format shown in FIG. 6B to the network. (800). In operation 1215 , the network 800 may transmit an RRC reconfiguration message (eg: RRC Reconfiguration with fullconfig and DRB setup) to the electronic device 101 . In operation 1217 , the electronic device 101 may transmit an RRC reconfiguration complete message to the network 800 . Accordingly, the electronic device 101 and the network 800 may reset the count through full config and DRB setup, and the count mismatch may be resolved.

13 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , in operation 1301 , a first message may be received from the network 800 . For example, the electronic device 101 may receive, as a DL, a data PDU having the format shown in FIG. 8B from the network 800 . The first message may include an SN, for example, the SN may be included in the PDCP SN field 833 of FIG. 8B .

According to various embodiments, in operation 1303 , the electronic device 101 may compare the count of the first message with at least one count set in the electronic device. The electronic device 101 may check the count of the first message based on the SN included in the first message and the managed HFN. Meanwhile, the receiving-side PDCP entity may manage (or maintain) the following state variables.

a)RX_NEXT: This state variable indicates the count value of the next PDCP SDU expected to be received, and the initial value may be 0.

b) RX_DELIV: This state variable may indicate the count value of the first PDCP SDU that is not transferred to upper layers and is still waiting.

c) RX_REORD: This state variable may indicate a count value following the count value associated with the PDCP data PDU that triggered t-Reordering.

The RX_DELIV of b) may be reported as FMC when reported to the transmitting PDCP entity.

The electronic device 101 may compare at least one of the state variables maintained in the aforementioned receiving-side PDCP entity with the count of the first message. In operation 1305 , the electronic device 101 may adjust at least one count set in the electronic device 101 , for example, at least one of state variables, based on the comparison result. In one example, when the count of the received message is less than RX_DELIV, for example, when the sum of the count of the received message and the specified value is less than RX_DELIV, the electronic device 101 adjusts It can be judged that the conditions for Alternatively, when the count of the received message is greater than RX_NEXT, for example, when the count of the received message is greater than the sum of RX_NEXT and the specified value, the electronic device 101 performs the adjustment It can be judged that the condition is satisfied. The specified value may be determined, for example, as in the example described in Equation 1 (eg, 833), but this is illustrative and not limited. A method of setting the designated value will be described with reference to FIG. 14 . The specified values associated with FIG. 13 and the specified values associated with FIG. 6A and Equation 1 may be different, but may be set to be the same. Specified values for solving the count mismatch problem due to HARQ and RLC retransmission may be set according to DL channel conditions, which will be described later.

14A is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , in operation 1401 , a first message may be received. In operation 1403 , the electronic device 101 may check the count and RX_DELIV of the first message. The electronic device 101 may, for example, check the count of the first message based on the SN and the HFN maintained in the PDCP SN field 833 of FIG. 8B . The electronic device 101 may check the maintained RX_DELIV.

According to various embodiments, in operation 1405 , the electronic device 101 may determine that the count of the first message and RX_DELIV satisfy a specified condition. For example, the electronic device 101 may confirm that the count and RX_DELIV of the first message satisfy Equation (3).

RCVD_COUNT in Equation 3 is a count of a received message, and Y may be a specified value. Whether the value of RCVD_COUNT in Equation 3 is less than RX_DELIV - Y may be changed depending on whether the value of RCVD_COUNT is less than or equal to RX_DELIV - Y. Y may be set, for example, based on at least some of the above-described methods for setting X. Alternatively, since Y is a value corresponding to a case in which reordering is already completed and the SN for the PDU to which the RLC ACK is transmitted is received again, Y may be set to a designated constant (eg, 10). When it is confirmed that the specified condition is satisfied (eg, Equation 3 is satisfied), the electronic device 101 performs at least one count (eg, RX_NEXT, RX_NEXT, at least one of RX_DELIV and RX_REORD) can be adjusted.

14B is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , in operation 1411 , a first message may be received. In operation 1413 , the electronic device 101 may check the count and RX_NEXT of the first message. The electronic device 101 may, for example, check the count of the first message based on the SN and the HFN maintained in the PDCP SN field 833 of FIG. 8B . The electronic device 101 may check the maintained RX_NEXT.

According to various embodiments, in operation 1415 , the electronic device 101 may confirm that the count of the first message and RX_NEXT satisfy a specified condition. For example, the electronic device 101 may confirm that the count and RX_NEXT of the first message satisfy Equation (4).

RCVD_COUNT in Equation 4 is a count of a received message, and Z may be a specified value. Whether the value of RCVD_COUNT in Equation 3 is greater than RX_NEXT + Z may be changed depending on whether the value of RCVD_COUNT is greater than RX_NEXT + Z. Z may be set, for example, based on at least some of the above-described methods for setting X. At least some of X, Y, and Z in Equation 1, Equation 3, and Equation 4 may be the same as each other, or all may be different. When it is confirmed that the specified condition is satisfied (eg, Equation 4 is satisfied), the electronic device 101 performs at least one count (eg, RX_NEXT, RX_NEXT, at least one of RX_DELIV and RX_REORD) can be adjusted.

15 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure; The embodiment of FIG. 15 will be described with reference to FIGS. 16A and 16B. 16A and 16B are examples of received PDUs and counts according to various embodiments.

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , in operation 1501 , a first message may be received. In operation 1503 , the electronic device 101 may compare the count of the first message and at least one count set in the electronic device, for example, at least one of RX_NEXT, RX_DELIV, or RX_REORD. In operation 1505 , the electronic device 101 may determine that at least one count adjustment set in the electronic device 101 is required based on the comparison result. For example, the electronic device 101 may confirm that Equation 3 or Equation 4 is satisfied.

According to various embodiments, the electronic device 101 may identify an adjustment rule in operation 1507 . The electronic device 101 may select any one adjustment rule from among a plurality of adjustment rules. For example, Equation 5 may be a condition for selecting an adjustment rule.

In Equation 5, A is the count of the PDU causing the count mismatch, B is the RX_NEXT value immediately before receiving the PDU, and C is the count of the PDU received after receiving the PDU. For example, if it is confirmed that Equation 5 is satisfied, the electronic device 101 may select the first adjustment rule, and if it is confirmed that Equation 5 is not satisfied, the electronic device 101 selects the second adjustment rule can

According to various embodiments, if the first adjustment rule is selected, in operation 1509 , the electronic device 101 may adjust at least one count set in the electronic device based on the first adjustment rule. For example, referring to FIG. 16A , the electronic device 101 may receive the first PDU 1601 from the network 800 at a first time point. The count of the first PDU 1601 may be B-1. The electronic device 101 may manage RX_NEXT as B. The electronic device 101 may receive the second PDU 1602 from the network 800 at a second time point. The count of the second PDU 1602 may be A. The electronic device 101 may check the count mismatch based on the second PDU 1602 . For example, the electronic device 101 may confirm that Equation 4, A > B + Z, is satisfied. The electronic device 101 may identify the second PDU 1602 as a PDU causing a count mismatch.

Thereafter, the electronic device 101 may receive the third PDU 1603 from the network 800 at a third time point. The count of the second PDU 1602 may be C. The electronic device 101 is, for example, |A - C| It can be confirmed that =< |B - C| is satisfied, and accordingly, the first adjustment rule can be selected. |A - C| When =< |B - C| is satisfied, it may mean that the SN transmitted from the network 800 has high accuracy, and the first adjustment rule is based on the received SN other than the B maintained by the electronic device 101 . It may be based on A. For example, as shown in FIG. 16A , when A is greater than C, the electronic device 101 may update RX_NEXT to A+1. When C is greater than A, the electronic device 101 may update RX_NEXT to C+1. In this case, the electronic device 101 may not discard the second PDU 1602 .

According to various embodiments, if the second adjustment rule is selected, in operation 1511 , the electronic device 101 may adjust at least one count set in the electronic device based on the second adjustment rule. The electronic device 101 is, for example, |A - C| It can be checked that =< |B - C| is not satisfied, and accordingly, the second adjustment rule can be selected. |A - C| =< |B - C| is not satisfied, it may mean that the SN transmitted from the network 800 has low accuracy, and the second adjustment rule is determined in the electronic device 101 other than A according to the received SN. It may be based on B being maintained. If the state variable is updated based on A, all PDUs with a count smaller than A are discarded. Therefore, the second adjustment rule may be based on B maintained in the electronic device 101 . For example, as shown in FIG. 16B , when C is greater than B, the electronic device 101 may update RX_NEXT to C+1. When B is greater than C, the electronic device 101 may update RX_NEXT to B+1.

Meanwhile, the aforementioned adjustment of RX_NEXT is merely exemplary, and the electronic device 101 according to various embodiments may also adjust RX_DELIV and/or RX_REORD in addition to RX_NEXT.

According to various embodiments, the electronic device 101 may perform the adjustment through the RLF described with reference to FIGS. 9, 10A, and 10B in addition to the first and second adjustment rules described above. Alternatively, the electronic device 101 may perform the adjustment by transmitting the control PDU requesting the recovery described with reference to FIGS. 11, 12A, and 12B to the network 800 .

17 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , in operation 1701 , a PDU may be received from the network 800 . For example, the electronic device 101 may receive a PDCP data PDU having the format shown in FIG. 8B .

According to various embodiments, the electronic device 101 may identify an integrity verification failure in operation 1703 . For example, the electronic device 101 may identify the received MAC-I based on a value included in the MAC-I field 835 . As described with reference to FIG. 5C , the electronic device 101 may identify XMAC-I. The electronic device 101 may perform integrity verification based on the comparison of XMAC-I and MAC-I. If XMAC-I and MAC-I are the same, the electronic device 101 may determine that integrity verification is successful. If XMAC-I and MAC-I are not the same, the electronic device 101 may determine that integrity verification has failed. If it is determined that the integrity verification has failed, the electronic device 101 may determine that there is a difference between the HFN managed by the electronic device 101 and the HFN managed by the network 800 .

The electronic device 101 according to various embodiments may adjust the HFN in operation 1705 based on the integrity verification failure. Although the adjustment rule of the HFN will be described later, there is no limitation. In operation 1707 , the electronic device 101 may check again whether the integrity verification is successful based on the adjusted HFN. As the HFN is adjusted, the count (COUNT) input from the receiving PDCP entity to the NIA in FIG. 5C may also be adjusted.

According to various embodiments, if integrity verification is successful (1707-Yes), the electronic device 101 may update the HFN, for example, determine the HFN adjusted in operation 1705 . If the integrity verification fails again (1707 - NO), the electronic device 101 may adjust the HFN again in operation 1705 . The electronic device 101 may adjust the HFN until integrity verification succeeds, or if integrity verification failure is confirmed for a specified number of times, the electronic device 101 may adjust the HFN to an initial value.

According to various embodiments, the electronic device 101 may determine whether the HFN does not match, for example, after adjusting the state variable managed (or maintained) by the electronic device 101 , but at the time of determination no limits. Upon receiving the PDU, the electronic device 101 may be configured to determine whether the HFN does not match at a determination time or without limitation.

Meanwhile, although FIG. 17 has been described as an operation of the electronic device 101, the operations of FIG. 17 and FIGS. 18 and 19 to be described later may be performed by the receiving PDCP entity, and in the case of UL, by the network 800 It will be understood by those skilled in the art that this may also be performed.

For reference, in LTE (eg, 3GPP TS 36.323), there is a condition that the MAC-I field is restricted, and the use of the MAC-I field is restricted for a DRB used by a terminal device such as a smart phone. For example, according to NR (eg, 3GPP TS 38.323), unlike conventional LTE, the MAC-I field is optionally available in the DRB, and there is no restriction on the use of the MAC-I field. Accordingly, the NR-based electronic device 101 may perform integrity verification based on a value in the MAC-I field regardless of the type of DRB.

18 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , in operation 1801 , a PDU may be received from the network 800 . For example, the electronic device 101 may receive a PDCP data PDU having the format shown in FIG. 8B .

According to various embodiments, the electronic device 101 may perform deciphering on the first part of the received PDU in operation 1803 . For example, the electronic device 101 may perform deciphering on the data field 834 and the MAC-I field 835 of FIG. 8B . For example, the electronic device 101 may perform the deciphering operation as described with reference to FIG. 5A . In operation 1805 , the electronic device 101 may perform integrity verification on the second portion for verifying the integrity of the deciphered first portion. The electronic device 101 may perform integrity verification by comparing the value in the MAC-I field 835, which is the deciphered second part, with the XMAC-I generated as described with reference to FIG. 5C . In operation 1807 , the electronic device 101 may determine whether there is a discrepancy between the HFN of the electronic device 101 and the HFN of the network 800 based on the integrity verification result. Whether to correct the HFN managed by the electronic device 101 may be checked according to whether the HFN does not match.

19 is a flowchart illustrating a method of operating an electronic device according to various embodiments of the present disclosure;

According to various embodiments, the electronic device 101 (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , in operation 1901 , a PDU may be received from the network 800 . For example, the electronic device 101 may receive a PDCP data PDU having the format shown in FIG. 8B . In operation 1903 , the electronic device 101 may identify integrity verification failure. In operation 1905 , the electronic device 101 may update the HFN by adding 1 to the current value. For example, if the current HFN managed (or maintained) by the electronic device 101 is “D”, the HFN may be updated to “D+1” in operation 1905 . In operation 1907 , the electronic device 101 may determine whether the integrity verification is successful. For example, the electronic device 101 may check the count COUNT based on the HFN of "D+1", and may perform deciphering and integrity verification again based on the checked count.

If it is determined that the integrity verification is successful (1907 - Yes), according to various embodiments, the electronic device 101 may confirm the update of the HFN in operation 1909 . The electronic device 101 may determine, for example, “D+1” as the HFN. If it is determined that the integrity verification has failed (1907 - NO), the electronic device 101 may update the HFN by subtracting 1 from the current value in operation 1911 . For example, the electronic device 101 may update the HFN to “D-1” in operation. In operation 1913 , the electronic device 101 may determine whether the integrity verification is successful. For example, the electronic device 101 may check the count COUNT based on the HFN of "D-1", and may perform deciphering and integrity verification again based on the checked count. If it is determined that the integrity verification is successful (1913 - Yes), the electronic device 101 may confirm the update of the HFN in operation 1915 . The electronic device 101 may determine, for example, “D-1” as the HFN. If it is determined that the integrity verification has failed (1913 - NO), the electronic device 101 may update HFN and HFN to 0 in operation 1917 . In operation 1919 , the electronic device 101 may determine whether the integrity verification is successful. For example, the electronic device 101 may check a count COUNT based on an HFN of “0”, and may perform deciphering and integrity verification again based on the checked count. If it is determined that the integrity verification is successful (1919 - Yes), the electronic device 101 may confirm the update of the HFN in operation 1921 . The electronic device 101 may determine, for example, “0” as the HFN. If it is determined that the integrity verification has failed (1919 - NO), the electronic device 101 may determine the integrity verification failure in operation 1923 and discard the PDU.

According to various embodiments, “+1”, “-1”, and “set to zero” of operation 1905, operation 1911, and operation 1917 are merely exemplary, the order is not limited, and the numerical value may be changed have.

According to various embodiments, the electronic device 101 may include at least one processor (eg, the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated communication processor 260 ). at least one SoC), wherein the at least one processor (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) One) receives a first message from a network, performs deciphering on a first part of the first message, and performs a first integrity check on a second part for verifying the integrity of the deciphered first part and determine whether there is a mismatch between a hyper frame number (HFN) of the electronic device 101 and the HFN of the network based on a result of the first integrity check.

According to various embodiments, the at least one processor (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , when a discrepancy between the HFN of the electronic device 101 and the HFN of the network is identified, it may be further configured to adjust the HFN of the electronic device 101 .

According to various embodiments, the at least one processor (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , as at least a part of the operation of adjusting the HFN of the electronic device 101 , it may be configured to perform a first operation on the HFN of the electronic device 101 .

According to various embodiments, the at least one processor (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , deciphering the first part of the first message based on the HFN on which the first operation is performed, and checking the integrity of the deciphered first part based on the HFN on which the first operation is performed. It may be further configured to perform a second integrity check on the second part, and determine whether there is a discrepancy between the HFN of the electronic device 101 and the HFN of the network based on a result of the second integrity check.

According to various embodiments, the at least one processor (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , when it is confirmed that the second integrity check succeeds, it may be further configured to update the HFN on which the first operation has been performed to the HFN of the electronic device 101 .

According to various embodiments, the at least one processor (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , when it is determined that the second integrity check has failed, it may be further configured to perform a second operation on the HFN of the electronic device 101 .

According to various embodiments, the at least one processor (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , deciphering the first part of the first message based on the HFN on which the second operation is performed, and checking the integrity of the deciphered first part based on the HFN on which the second operation is performed. It may be further configured to perform a third integrity check on the second part and determine whether there is a discrepancy between the HFN of the electronic device 101 and the HFN of the network based on a result of the third integrity check.

According to various embodiments, the at least one processor (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , as at least part of the operation of adjusting the HFN of the electronic device 101 , it may be set to adjust the HFN of the electronic device 101 to a specified value.

According to various embodiments, the at least one processor (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , if it is confirmed that the integrity verification based on the adjusted HFN fails, it may be further configured to discard the first message.

According to various embodiments, the at least one processor (eg, at least one of the processor 120 , the first communication processor 212 , the second communication processor 214 , the unified communication processor 260 , or the integrated SoC) may include: , based on at least one state variable maintained by the electronic device 101 being adjusted as at least part of the operation of determining whether there is a mismatch between the HFN of the electronic device 101 and the HFN of the network, Based on the result of the first integrity check, it may be configured to determine whether there is a mismatch between the HFN of the electronic device 101 and the HFN of the network.

According to various embodiments, a method of operating the electronic device 101 includes receiving a first message from a network, performing deciphering on a first portion of the first message, and integrity of the deciphered first portion. performing a first integrity check on the second part to confirm It may include an operation of determining whether there is a discrepancy.

According to various embodiments, the operating method may further include adjusting the HFN of the electronic device 101 when a mismatch between the HFN of the electronic device 101 and the HFN of the network is identified.

According to various embodiments, the operation of adjusting the HFN of the electronic device 101 may perform a first operation on the HFN of the electronic device 101 .

According to various embodiments, the operating method includes an operation of performing deciphering on a first part of the first message based on the HFN on which the first operation is performed, and the deciphering based on the HFN on which the first operation is performed. performing a second integrity check on the second part for checking the integrity of the first part, and based on the result of the second integrity check, between the HFN of the electronic device 101 and the HFN of the network The method may further include an operation of determining whether .

According to various embodiments, the operation method may further include updating the HFN on which the first operation has been performed to the HFN of the electronic device 101 when it is confirmed that the second integrity check succeeds.

According to various embodiments, the operation method may further include performing a second operation on the HFN of the electronic device 101 when it is determined that the second integrity check has failed.

According to various embodiments, the operating method includes an operation of deciphering the first part of the first message based on the HFN on which the second operation is performed, and the deciphering based on the HFN on which the second operation is performed. performing a third integrity check on the second part for confirming the integrity of the first part, and based on the result of the third integrity check, between the HFN of the electronic device 101 and the HFN of the network The method may further include an operation of determining whether .

According to various embodiments, the operation of adjusting the HFN of the electronic device 101 may adjust the HFN of the electronic device 101 to a specified value.

According to various embodiments, the operating method may further include, if it is determined that the integrity verification based on the adjusted HFN fails, discarding the first message.

According to various embodiments, the operation of determining whether there is a discrepancy between the HFN of the electronic device 101 and the HFN of the network is that at least one state variable maintained by the electronic device 101 is adjusted. Based on the result of the first integrity check, it is possible to determine whether there is a discrepancy between the HFN of the electronic device 101 and the HFN of the network.

The electronic device according to various embodiments disclosed in this document may have various types of devices. The electronic device may include, for example, a computer device, a portable communication device (eg, a smart phone), a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance device. The electronic device according to the embodiment of the present document is not limited to the above-described devices.

It should be understood that the various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and include various modifications, equivalents, or substitutions of the embodiments. In connection with the description of the drawings, like reference numerals may be used for similar or related components. The singular form of the noun corresponding to the item may include one or more items, unless the relevant context clearly dictates otherwise. As used herein, “A or B”, “at least one of A and B”, “at least one of A or B,” “A, B or C,” “at least one of A, B and C,” and “A , B, or C" each may include any one of the items listed together in the corresponding one of the phrases, or all possible combinations thereof. Terms such as “first”, “second”, or “first” or “second” may simply be used to distinguish the component from other components in question, and may refer to components in other aspects (e.g., importance or order) is not limited. that one (eg first) component is “coupled” or “connected” to another (eg, second) component with or without the terms “functionally” or “communicatively” When referenced, it means that one component can be coupled to another component directly (eg, by wire), wirelessly, or through a third component.

As used herein, the term “module” may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as, for example, logic, logic block, component, or circuit. A module may be an integrally formed part or a minimum unit of a part or a part thereof that performs one or more functions. For example, according to an embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of the present document include software (eg, one or more instructions stored in a storage medium (eg, internal memory or external memory) readable by a machine (eg, a master device or a task performing device)) For example, it can be implemented as a program). For example, a processor of a device (eg, a master device or a task performing device) may call at least one of one or more instructions stored from a storage medium and execute it. This enables the device to be operated to perform at least one function according to at least one command called. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not contain a signal (eg, electromagnetic wave), and this term is used in cases where data is semi-permanently stored in the storage medium and It does not distinguish between temporary storage cases.

According to one embodiment, the method according to various embodiments disclosed in this document may be provided in a computer program product (computer program product). Computer program products may be traded between sellers and buyers as commodities. The computer program product is distributed in the form of a device-readable storage medium (eg compact disc read only memory (CD-ROM)), or through an application store (eg Play Store™) or on two user devices (eg, It can be distributed (eg downloaded or uploaded) directly, online between smartphones (eg: smartphones). In the case of online distribution, at least a part of the computer program product may be temporarily stored or temporarily created in a machine-readable storage medium such as a memory of a server of a manufacturer, a server of an application store, or a relay server.

According to various embodiments, each component (eg, a module or a program) of the described components may include a singular or a plurality of entities. According to various embodiments, one or more components or operations among the above-described corresponding components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (eg, a module or a program) may be integrated into one component. In this case, the integrated component may perform one or more functions of each component of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to integration. According to various embodiments, operations performed by a module, program, or other component are executed sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations are executed in a different order, omitted, or , or one or more other operations may be added.

Claims (20)

In an electronic device,
at least one processor;
The at least one processor comprises:
receive a first message from the network;
performing deciphering on a first part of the first message;
performing a first integrity check on the second part for confirming the integrity of the deciphered first part;
an electronic device configured to determine whether there is a discrepancy between a hyper frame number (HFN) of the electronic device and an HFN of the network, based on a result of the first integrity check. The method of claim 1,
the at least one processor,
The electronic device further configured to adjust the HFN of the electronic device when a mismatch between the HFN of the electronic device and the HFN of the network is identified. 3. The method of claim 2,
The at least one processor is configured to perform a first operation on the HFN of the electronic device as at least a part of the operation of adjusting the HFN of the electronic device. 4. The method of claim 3,
the at least one processor,
performing deciphering on the first part of the first message based on the HFN on which the first operation is performed;
Based on the HFN on which the first operation is performed, a second integrity check is performed on the second part for confirming the integrity of the deciphered first part,
The electronic device further configured to determine whether there is a discrepancy between the HFN of the electronic device and the HFN of the network based on a result of the second integrity check. 5. The method of claim 4,
The at least one processor is further configured to update the HFN on which the first operation has been performed to the HFN of the electronic device when it is confirmed that the second integrity check is successful. 5. The method of claim 4,
The at least one processor is further configured to perform a second operation on the HFN of the electronic device when it is determined that the second integrity check has failed. 7. The method of claim 6,
the at least one processor,
performing deciphering on the first part of the first message based on the HFN on which the second operation is performed;
Based on the HFN on which the second operation is performed, a third integrity check is performed on the second part for confirming the integrity of the deciphered first part,
The electronic device further configured to determine whether there is a discrepancy between the HFN of the electronic device and the HFN of the network based on a result of the third integrity check. 3. The method of claim 2,
The at least one processor is configured to adjust the HFN of the electronic device to a specified value as at least part of the operation of adjusting the HFN of the electronic device. 3. The method of claim 2,
the at least one processor,
The electronic device further configured to discard the first message when it is confirmed that the integrity verification based on the adjusted HFN fails. The method of claim 1,
The at least one processor, as at least part of the operation of determining whether there is a mismatch between the HFN of the electronic device and the HFN of the network,
configured to determine whether there is a discrepancy between the HFN of the electronic device and the HFN of the network based on a result of the first integrity check based on adjustment of at least one state variable maintained by the electronic device electronic device. A method of operating an electronic device, comprising:
receiving a first message from the network;
performing deciphering on a first portion of the first message;
performing a first integrity check on the second part to confirm the integrity of the deciphered first part; and
Determining whether there is a mismatch between a hyper frame number (HFN) of the electronic device and an HFN of the network based on a result of the first integrity check
A method of operating an electronic device comprising a. 12. The method of claim 11,
If mismatch between the HFN of the electronic device and the HFN of the network is identified, adjusting the HFN of the electronic device
The method of operating an electronic device further comprising a. 13. The method of claim 12,
The operation of adjusting the HFN of the electronic device includes performing a first operation on the HFN of the electronic device. 14. The method of claim 13,
performing deciphering on the first part of the first message based on the HFN on which the first operation is performed;
performing a second integrity check on the second part for checking the integrity of the deciphered first part based on the HFN on which the first operation has been performed, and
Determining whether there is a discrepancy between the HFN of the electronic device and the HFN of the network based on a result of the second integrity check
The method of operating an electronic device further comprising a. 15. The method of claim 14,
If it is confirmed that the second integrity check is successful, updating the HFN on which the first operation has been performed to the HFN of the electronic device
The method of operating an electronic device further comprising a. 15. The method of claim 14,
If it is determined that the second integrity check has failed, performing a second operation on the HFN of the electronic device
The method of operating an electronic device further comprising a. 17. The method of claim 16,
performing deciphering on the first part of the first message based on the HFN on which the second operation is performed;
performing a third integrity check on the second part for checking the integrity of the deciphered first part based on the HFN on which the second operation is performed, and
Determining whether there is a discrepancy between the HFN of the electronic device and the HFN of the network based on the result of the third integrity check
The method of operating an electronic device further comprising a. 13. The method of claim 12,
The operation of adjusting the HFN of the electronic device includes adjusting the HFN of the electronic device to a specified value. 13. The method of claim 12,
If it is confirmed that the integrity verification based on the adjusted HFN fails, discarding the first message
The method of operating an electronic device further comprising a. 12. The method of claim 11,
The operation of determining whether there is a discrepancy between the HFN of the electronic device and the HFN of the network is based on a result of the first integrity check based on adjustment of at least one state variable maintained by the electronic device to determine whether there is a discrepancy between the HFN of the electronic device and the HFN of the network.

Images