Integrity protection method and communication device

By using RRC signaling configuration and PDCP PDU indicator bits and other technologies in the new wireless communication system, only some data packets are DRB IP and encryption, which solves the problem of high performance requirements for network equipment at full data level DRB integrity protection. Efficient integrity protection and security are achieved.

CN114930890BActive Publication Date: 2024-11-19GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080092652.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-03-30
Publication Date
2024-11-19
Estimated Expiration
2040-03-30

AI Technical Summary

Technical Problem

DRB integrity protection at full data level has high performance requirements for network equipment, making it difficult to achieve efficient integrity protection while taking into account performance and security.

Method used

An integrity protection method is proposed. By selecting the data to perform integrity protection and encryption on the sending end, using RRC signaling configuration rules, only some data packets are DRB IP and encryption, combining the indicator bits of the PDCP PDU and MAC-I Verification to achieve partial integrity protection and encryption of data packets.

Benefits of technology

While providing integrity protection, it reduces the requirements for network equipment performance, improves the execution efficiency and application range of DRB IP, and enables the effective use of DRB IP.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114930890B_ABST
    Figure CN114930890B_ABST
Patent Text Reader

Abstract

This application proposes an integrity protection method and a communication device. The method includes: a transmitting device selecting first data for integrity protection and / or encryption; performing integrity protection and / or encryption on the selected first data; and transmitting data containing the integrity-protected and / or encrypted first data. This application can reduce the performance requirements of network devices while providing integrity protection.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communications, and more particularly, to an integrity protection method and a communication device. Background Art

[0002] In New Radio (NR), encryption and integrity protection of the user plane are activated at the granularity of Data Radio Bearer (DRB), that is, each DRB is individually configured whether to activate the encryption function and / or whether to activate the integrity protection (IP) function.

[0003] However, full data rate DRB integrity protection (DRB IP) places high demands on the implementation and performance of network devices. Summary of the invention

[0004] The embodiments of the present application provide an integrity protection method and a network device, which can reduce the performance requirements for the network device while providing integrity protection.

[0005] The present application embodiment provides an integrity protection method, including:

[0006] The sending end device selects first data to be integrity protected and / or encrypted;

[0007] Performing integrity protection and / or encryption on the selected first data;

[0008] Data including the integrity protected and / or encrypted first data is sent.

[0009] The present application embodiment provides an integrity protection method, including:

[0010] The receiving device receives data, wherein the data includes first data that has been integrity protected and / or encrypted;

[0011] The first data is decrypted and / or integrity protected and verified.

[0012] The present application embodiment provides an integrity protection method, including:

[0013] The network device receives a security policy for a PDU session and information about a quality of service (QoS) flow in the PDU session that needs to be integrity protected and / or encrypted;

[0014] Mapping the QoS flow requiring integrity protection and / or encryption to the first DRB data;

[0015] The first DRB data is integrity protected and / or encrypted.

[0016] The present application embodiment provides an integrity protection method, including:

[0017] The network device sends the security policy of the PDU session and the information of the quality of service QoS flow that needs to be integrity protected and / or encrypted in the PDU session.

[0018] The present application provides a communication device, including:

[0019] A selection module, configured to select first data to be integrity protected and / or encrypted;

[0020] A first integrity protection module, configured to perform integrity protection and / or encryption on the selected first data;

[0021] The data sending module is used to send data including integrity protected and / or encrypted first data.

[0022] The present application provides a communication device, including:

[0023] A data receiving module, used for receiving data, wherein the data includes first data which has been integrity protected and / or encrypted;

[0024] An integrity protection verification module is used to decrypt and / or perform integrity protection verification on the first data.

[0025] The present application embodiment provides a network device, including:

[0026] A security policy receiving module, configured to receive a security policy for a PDU session and information about a QoS flow in the PDU session that needs to be integrity protected and / or encrypted;

[0027] A mapping module, configured to map the QoS flow requiring integrity protection and / or encryption to first DRB data;

[0028] The second integrity protection module is used to perform integrity protection and / or encryption on the first DRB data.

[0029] The present application embodiment provides a network device, including:

[0030] The security policy sending module is used to send the security policy of the PDU session and the information of the quality of service QoS flow that needs to be integrity protected and / or encrypted in the PDU session.

[0031] An embodiment of the present application proposes a communication device, including: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute any one of the above methods.

[0032] An embodiment of the present application proposes a network device, including: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of the above methods.

[0033] An embodiment of the present application proposes a chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes any one of the above methods.

[0034] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, wherein the computer program enables a computer to execute any one of the above methods.

[0035] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute any one of the above methods.

[0036] An embodiment of the present application provides a computer program, which enables a computer to execute any one of the above methods.

[0037] The embodiment of the present application selects a portion of the first data that needs to be integrity protected and / or encrypted for integrity protection and / or encryption, which can reduce the requirements on the performance of the network device while providing integrity protection. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application.

[0039] Figure 2 It is a flowchart of an implementation of an integrity protection method 200 according to an embodiment of the present application.

[0040] Figure 3 This is a schematic diagram of the structure of PDCP PDU.

[0041] Figure 4 A schematic diagram of an implementation method of sending the first information during the PDU session establishment process in an embodiment of the present application.

[0042] Figure 5 It is a flowchart of an integrity protection method 400 according to an embodiment of the present application.

[0043] Figure 6 It is a flowchart of an integrity protection method 500 according to an embodiment of the present application.

[0044] Figure 7 It is a flowchart of an integrity protection method 600 according to an embodiment of the present application.

[0045] Figure 8 It is a structural diagram of a communication device 700 according to an embodiment of the present application.

[0046] Fig. 9 It is a structural diagram of a communication device 800 according to an embodiment of the present application.

[0047] Fig.10 It is a structural diagram of a communication device 900 according to an embodiment of the present application.

[0048] Fig.11 It is a structural diagram of a communication device 1000 according to an embodiment of the present application.

[0049] Fig.12 It is a structural diagram of a network device 1100 according to an embodiment of the present application.

[0050] Fig.13 It is a structural diagram of a network device 1200 according to an embodiment of the present application.

[0051] Fig.14 It is a structural diagram of a network device 1300 according to an embodiment of the present application.

[0052] Fig.15 is a schematic structural diagram of a communication device 1400 according to an embodiment of the present application;

[0053] Fig.16 is a schematic structural diagram of a chip 1500 according to an embodiment of the present application. DETAILED DESCRIPTION

[0054] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0055] It should be noted that the terms "first", "second", etc. in the description and claims of the embodiments of the present application and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. The objects described by the "first" and "second" described at the same time may be the same or different.

[0056] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th-Generation (5G) system or other communication systems.

[0057] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), and vehicle to vehicle (Vehicle to Vehicle, V2V) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0058] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0059] The embodiments of the present application do not limit the spectrum to which they are applied. For example, the embodiments of the present application can be applied to licensed spectrum or unlicensed spectrum.

[0060] The embodiments of the present application describe various embodiments in combination with network devices and terminal devices, wherein: the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc. The terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, and a next-generation communication system, for example, a terminal device in an NR network or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0061] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0062] The network device can be a device used to communicate with a mobile device. The network device can be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, etc.

[0063] In an embodiment of the present application, a network device provides services for a cell, and a terminal device communicates with the network device through transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell may be a cell corresponding to a network device (e.g., a base station). The cell may belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: a metro cell, a micro cell, a picocell, a femtocell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0064] Figure 1 The wireless communication system 100 applied in the embodiment of the present application is exemplarily shown, and the communication system includes a terminal device 110, a master node (MN, Master Node) 120 and a secondary node (SN, Secondary Node) 130. Optionally, the wireless communication system 100 may include multiple MNs 120 or multiple SNs 130, and each MN 120 or SN 130 may include other number of terminal devices 110 within its coverage area, which is not limited in the embodiment of the present application.

[0065] Optionally, the wireless communication system 100 may also include other network entities such as a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF), etc., which is not limited in the embodiments of the present application.

[0066] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone.

[0067] An embodiment of the present application proposes an integrity protection method, which can be applied to communication equipment, such as terminal equipment or network equipment. Figure 2 2 is a flowchart of an integrity protection method 200 according to an embodiment of the present application, comprising the following steps:

[0068] S210: The transmitting end device selects first data to be integrity protected and / or encrypted;

[0069] S220: Perform integrity protection and / or encryption on the selected first data;

[0070] S230: Send data including integrity-protected and / or encrypted first data.

[0071] In some implementations, the first data is a Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) or a Service Data Adaptation Protocol (SDAP) SDU.

[0072] In some implementations, the first data includes a portion of data in a PDCP SDU or a portion of data in a SDAP SDU.

[0073] Optionally, the data containing the first data sent in step S230 is DRB data.

[0074] By adopting the above method, the embodiment of the present application can select a certain number of data packets in a DRB to execute DRB IP, and other data packets do not execute DRB IP; or, select a part of the data in a data packet to execute DRB IP.

[0075] In some implementations, the method further includes: adding indication information of whether integrity protection and / or encryption is performed on the first data in the PDCP SDU or the PDCP PDU corresponding to the SDAP SDU.

[0076] Specifically, indication information on whether integrity protection and / or encryption is performed on the first data may be added to a reserved field (such as an R field) of a PDCP protocol data unit (PDU) corresponding to the PDCP SDU or SDAP SDU.

[0077] Optionally, the above-mentioned method of selecting the first data may include at least one of the following:

[0078] Random selection;

[0079] Select based on data transmission rate and processing capability of the receiving device;

[0080] Select based on preconfigured rules;

[0081] A selection is made according to the first information.

[0082] The above-mentioned pre-configuration rules may be configured through dedicated signaling of Radio Resource Control (RRC), or may be specified in a protocol.

[0083] Regarding the manner of configuring the pre-configuration rule through RRC dedicated signaling, in some implementations, the above method further includes: receiving a first RRC signaling, where the first RRC signaling carries the pre-configuration rule.

[0084] Optionally, the first RRC signaling is received during an RRC connection reconfiguration process.

[0085] In some implementations, when the first data is a PDCP SDU or a SDAP SDU, the preconfigured rule includes:

[0086] When PDCP SN mod N=K, integrity protection and / or ciphering are performed on the PDCP SDU or SDAP SDU;

[0087] In the case where PDCP SN mod N≠K, integrity protection and / or encryption are not performed on the PDCP SDU or SDAP SDU; wherein the PDCP SN is the sequence number of the PDCP PDU corresponding to the PDCP SDU or SDAP SDU;

[0088] mod is the remainder function;

[0089] N and K are preset parameters.

[0090] In some implementations, when the first data includes a portion of data in a PDCP SDU or a portion of data in an SDAP SDU, the preconfigured rule includes at least one of the following:

[0091] whether the first data includes a header of a PDCP SDU or the SDAP SDU;

[0092] The data volume of the first data;

[0093] The position of the first data in the PDCP SDU or the SDAP SDU.

[0094] Optionally, when the above-mentioned sending end device is a terminal device, the terminal device receives the above-mentioned first RRC signaling sent by a master node (MN, MasterNode) and / or a secondary node (SN, Secondary Node).

[0095] When the above-mentioned sending end device is MN, it also includes: generating the above-mentioned pre-configuration rules, and sending the pre-configuration rules to SN and / or terminal equipment.

[0096] When the above-mentioned sending end device is a SN, it also includes: receiving or generating the above-mentioned pre-configuration rules, and sending the pre-configuration rules to the terminal device.

[0097] In some implementations, the above preconfigured rules are set for different PDU sessions; and / or,

[0098] Set up for different DRBs; and / or,

[0099] Configure settings for different terminal devices.

[0100] In some implementations, the method further includes: receiving a second RRC signaling, where the second RRC signaling carries a setting method for the preconfiguration rule.

[0101] In some implementations, the first information includes at least one of the following:

[0102] a total rate of the first data corresponding to a PDU session or each QoS flow;

[0103] a selection ratio of the first data;

[0104] The selection rule of the first data.

[0105] Optionally, when the transmitting end device is a base station, it further includes:

[0106] receiving the first information; or,

[0107] A security policy is received, where the security policy includes the first information.

[0108] In some implementations, the first information or the security policy is received during a PDU session establishment and / or a PDU session modification process.

[0109] Optionally, when the above-mentioned sending end device is a terminal device, it also includes: receiving a non-access stratum (NAS, Non-Access-Stratum) message, and the NAS information includes the first information.

[0110] In some implementations, the NAS message is received during a PDU session establishment and / or a PDU session modification process.

[0111] In some implementations, the preconfiguration rules are the same or different for uplink transmission and downlink transmission. For example, for uplink transmission and downlink transmission, the same preconfiguration rule may be used to select the first data, or different preconfiguration rules may be used to select the first data.

[0112] In some implementations, the first information is the same or different for uplink transmission and downlink transmission. For example, for uplink transmission and downlink transmission, the same first information may be used to select the first data, or different first information may be used to select the first data.

[0113] The present application is introduced below with reference to the accompanying drawings by giving specific implementation methods.

[0114] Embodiment 1:

[0115] In this embodiment, DRB IP is performed on a certain number of data packets (such as PDCP SDU or SDAP SDU) in a DRB, and DRB IP is not performed on other data packets.

[0116] For example, in the case where DRB IP is executed on some PDCP SDUs or SDAP SDUs in the DRB, at least the following two methods can be used to select the PDCP SDUs or SDAP SDUs on which DRB IP is executed.

[0117] Method 1:

[0118] The transmitting device selects the PDCP SDU or SDAP SDU of the DRB IP to be performed.

[0119] In some embodiments, the transmitting end device only adds MAC-I in the PDCP SDU or SDAP SDU that requires integrity protection (abbreviated as integrity protection) for integrity protection verification, and / or adds an indication bit to the packet header of the PDCP PDU corresponding to each PDCP SDU or SDAP SDU that chooses to perform integrity protection and / or encryption, to indicate whether the PDCP SDU or SDAP SDU performs DRB IP and / or encryption. For example, when the value of the indication bit is 1, it means that DRB IP is executed; when the value of the indication bit is 0, it means that DRB IP is not executed. For example, the indication bit can use an existing reserved bit (bit), that is, Rbit. In addition, the embodiment of the present application can also use one of the Rbits to indicate whether the current data packet has been encrypted.

[0120] Figure 3 It is a schematic diagram of the structure of PDCP PDU, such as Figure 3 As shown, the PDCP PDU includes 3 R bits, which can be used to carry the corresponding PDCP SDU or SDAP SDU whether to perform integrity protection and / or encryption. If integrity protection is performed, the last 32 bits are used for integrity verification MAC-I; if integrity protection is not performed, the last 32 bits are data.

[0121] The sending end device can randomly select the data packets that need to be protected, or can select them according to a certain rule, such as performing protection on the 1st, 3rd, 5th, 7th, 9th... (odd number) data packets.

[0122] In addition, the number of data packets selected by the transmitting device for complete protection can refer to the complete protection processing capability of the receiving device (such as the complete protection processing rate) and / or the current data transmission volume (such as the transmission rate). For example, if the complete protection processing capability of the receiving end is 100MB / s, and the current data transmission rate is 500MB / s, the transmitting device can select 1 / 5 of the transmitted data packets for complete protection operation (such as selecting 1 out of every 5 data packets for complete protection); or, select a smaller proportion of data packets than 1 / 5 for complete protection operation.

[0123] Method 2:

[0124] The network side configures a DRB to execute DRB IP and / or encryption rules through RRC signaling, and the sending device selects the data that needs to be integrity protected and / or encrypted according to the rules; the receiving device decrypts and / or integrity protects the data that has been integrity protected and / or encrypted according to the rules.

[0125] The above rules can be set according to actual conditions. For example, the above rules are:

[0126] When PDCP SN mod N=K, integrity protection and / or ciphering are performed on the PDCP SDU or SDAP SDU;

[0127] In the case of PDCP SN mod N≠K, integrity protection and / or encryption is not performed on the PDCP SDU or SDAP SDU; wherein,

[0128] The PDCP SN is the sequence number of the PDCP PDU corresponding to the PDCP SDU or SDAP SDU;

[0129] mod is the remainder function;

[0130] N and K are preset parameters.

[0131] like Figure 3 As shown, PDCP SN is a field in PDCP PDU, indicating the sequence number of PDCP PDU.

[0132] In order to reduce the complexity of implementation, the above rules do not change during the existence of the RRC connection, or the changes to the above rules can only be changed through synchronous RRC connection reconfiguration.

[0133] In the Multi-RAT Dual Connectivity (MR-DC) scenario, if a PDU session is split between the MN and the SN, the MN may be responsible for generating the above rules and configuring the rules to the SN via the Xn interface, and the SN configures the rules configured by the MN to the UE via the SN RRC.

[0134] Alternatively, the MN may also configure the above rules to the UE through RRC signaling.

[0135] Alternatively, the SN may generate the required rules, and the MN and the SN may respectively configure the relevant rules to the UE through the RRC.

[0136] The above rules may be configured with DRB as the granularity, for example, each rule is associated with a DRB identifier (DRB ID). Alternatively, the above rules may also be configured with PDU session as the granularity, for example, each rule is associated with a DRB identifier list (DRB ID list). Alternatively, the above rules may also be configured with UE as the granularity. Optionally, the network side may configure the granularity of the rule in RRC dedicated signaling, that is, with DRB as the granularity, or with PDU session as the granularity, or with UE as the granularity.

[0137] In some implementations, the transmitting device only adds MAC-I in the PDCP SDU or SDAP SDU that requires integrity protection (abbreviated as integrity protection) for integrity verification. Furthermore, the same scheme as the above-mentioned method 1 can be adopted to add an indication bit to the packet header of the PDCP PDU corresponding to each PDCP SDU or SDAP SDU that performs integrity protection and / or encryption, to indicate whether the PDCP SDU or SDAP SDU executes DRB IP. Alternatively, since the receiving device is also configured with the above-mentioned rules, the embodiment of the present application may not set the indication bit of whether DRB IP is executed; after receiving the data, the receiving device determines the PDCP SDU or SDAP SDU that executes integrity protection and / or encryption according to the above-mentioned rules.

[0138] Embodiment 2:

[0139] Integrity protection is performed first and then encryption at the PDCP layer. In order to improve the efficiency of DRB IP, integrity protection can be performed on a portion of the data packet, such as a portion of the payload data portion in the PDCP SDU or SDAP SDU, or a portion of the header portion in the PDCP SDU or SDAP SDU.

[0140] For example, n bits (or n bytes) including the header are selected to perform integrity protection and / or encryption, or n bits (or n bytes) excluding the header are selected to perform integrity protection and / or encryption.

[0141] Whether to include a header can be specified in the data packet header or configured through RRC dedicated signaling. The size of n can be fixed in the protocol or configured by the network side through RRC signaling. The n bits (or n bytes) selected for integrity protection and / or encryption can be the n bits (or n bytes) in the header of the data packet, or the n bits (or n bytes) at the end of the data packet, or the kth n bits (or n bytes) in the data packet (k is a natural number), etc. The selection rule of n bits (or n bytes) can also be specified in the data packet header or configured through RRC dedicated signaling. In addition, the data packet header or RRC dedicated signaling configuration can also indicate the position of the data portion that is integrity protected and / or encrypted, such as the position from the nth byte to the mth byte is integrity protected and / or encrypted.

[0142] The specific method of integrity protection can be the same as that of embodiment 1, which will not be repeated here.

[0143] For the MR-DC scenario, the MN can decide whether to use partial data to perform DRB IP and / or encryption, and the above selection rules can also be configured by the MN to the SN; the SN executes DRB IP and / or encryption according to the above rules configured by the MN, and configures the above rules to the UE through the SN RRC.

[0144] Alternatively, the MN may also configure the above rules to the UE through RRC signaling.

[0145] Alternatively, the SN may generate the required rules, and the MN and the SN may respectively configure the relevant rules to the UE through the RRC.

[0146] The above rules may be configured with DRB as the granularity, for example, each rule is associated with a DRB identifier (DRB ID). Alternatively, the above rules may also be configured with PDU session as the granularity, for example, each rule is associated with a DRB identifier list (DRB ID list). Alternatively, the above rules may also be configured with UE as the granularity. Optionally, the network side may configure the granularity of the rule in RRC dedicated signaling, that is, with DRB as the granularity, or with PDU session as the granularity, or with UE as the granularity.

[0147] Based on the above embodiment, further, the base station and / or the terminal may perform integrity protection and / or encryption configuration according to the first information sent by the core network element, where the first information includes at least one of the following:

[0148] 1) The total rate of integrity protection and / or encryption for the entire PDU session or each QoS flow;

[0149] 2) The ratio of integrity protection and / or encryption (e.g., 20% of the packets need to be intact);

[0150] 3) The regularity of integrity protection and / or encryption of packets (e.g., integrity protection is performed on packets with an odd number of PDCP SNs, or integrity protection is performed on one packet out of every five packets);

[0151] The first information can be sent to the base station as part of the security policy, or can be sent to the base station as a separate parameter. The first information can also be sent to the terminal via a NAS message, and the terminal then performs data integrity protection and / or encryption based on the first information.

[0152] If the first information is only sent to the base station, the base station decides which specific data packets need to be integrity protected and / or encrypted based on the first information, and can inform the terminal through air interface signaling (such as RRC signaling) or user plane data packet header indication (such as PDCP packet header).

[0153] If the base station does not instruct the terminal which data packets need to be integrity protected and / or encrypted, or the terminal receives a NAS message containing the first information, the terminal determines which data packets need to be integrity protected and / or encrypted according to the first information.

[0154] In some implementations, the first information may be sent to the base station and / or the terminal through a PDU session establishment or a PDU session modification process. Figure 4 Schematic diagram of an implementation method of sending the first information during the PDU session establishment process in the embodiment of the present application. Figure 4 As shown, during the PDU session establishment process, the SMF determines the first information based on the contract information, policy control and charging (PCC) policy or local configuration, and sends the first information to the base station and / or the terminal.

[0155] This application embodiment proposes an integrity protection method. Figure 5 4 is a flowchart of an integrity protection method 400 according to an embodiment of the present application, comprising the following steps:

[0156] S410: The receiving end device receives data, where the data includes first data that has been integrity protected and / or encrypted;

[0157] S420: Decrypt and / or perform integrity protection verification on the first data.

[0158] The above-mentioned receiving end device may be a communication device, such as a network device or a terminal device.

[0159] In some implementations, the first data is a PDCP SDU or a SDAP SDU.

[0160] In some implementations, the first data includes a portion of data in a PDCP SDU or a portion of data in a SDAP SDU.

[0161] Optionally, the above method also includes: determining whether the first data is integrity protected and / or encrypted according to the indication information in the PDCP PDU corresponding to the PDCP SDU or SDAP SDU, or determining the first data that is integrity protected and / or encrypted.

[0162] Optionally, whether the first data is integrity protected and / or encrypted, or the first data is integrity protected and / or encrypted, is determined according to the indication information in the reserved field of the PDCP PDU corresponding to the PDCP SDU or SDAP SDU.

[0163] In some embodiments, the above method further comprises:

[0164] According to a preconfigured rule or the first information, it is determined whether the first data is integrity protected and / or encrypted, or the first data is integrity protected and / or encrypted.

[0165] Optionally, the above method also includes: receiving a third RRC signaling, where the third RRC signaling carries the pre-configured rule.

[0166] In some implementations, the third RRC signaling is received during an RRC connection reconfiguration procedure.

[0167] In some implementations, when the first data is a PDCP SDU or a SDAP SDU, the preconfigured rule includes:

[0168] When PDCP SN mod N=K, integrity protection and / or ciphering are performed on the PDCP SDU or SDAP SDU;

[0169] In the case where PDCP SN mod N≠K, integrity protection and / or encryption are not performed on the PDCP SDU or SDAP SDU; wherein the PDCP SN is the sequence number of the PDCP PDU corresponding to the PDCP SDU or SDAP SDU;

[0170] mod is the remainder function;

[0171] N and K are preset parameters.

[0172] In some implementations, when the first data includes a portion of data in a PDCP SDU or a portion of data in an SDAP SDU, the preconfigured rule includes at least one of the following:

[0173] whether the first data includes a header of the PDCP SDU or the SDAP SDU;

[0174] The data volume of the first data;

[0175] The position of the first data in the PDCP SDU or the SDAP SDU.

[0176] In some implementations, when the above-mentioned receiving end device is a terminal device, the terminal device receives the above-mentioned third RRC signaling sent by the MN and / or the SN.

[0177] Optionally, when the receiving device is a MN, the method further comprises: generating the pre-configuration rule, and sending the pre-configuration rule to the SN and / or the terminal device.

[0178] Optionally, when the receiving device is a SN, the method further includes: receiving or generating the pre-configuration rule, and sending the pre-configuration rule to the terminal device.

[0179] In some implementations, the above preconfigured rules are set for different PDU sessions; and / or,

[0180] Setting for different DRB data; and / or,

[0181] Configure settings for different terminal devices.

[0182] In some implementations, the above method further includes: receiving a fourth RRC signaling, wherein the fourth RRC signaling carries a setting method of the preconfiguration rule.

[0183] In some embodiments, the first information includes at least one of the following:

[0184] a total rate of the first data corresponding to a PDU session or each QoS flow;

[0185] a selection ratio of the first data;

[0186] The selection rule of the first data.

[0187] Optionally, when the receiving end device is a base station, it further includes:

[0188] receiving the first information; or,

[0189] A security policy is received, where the security policy includes the first information.

[0190] In some implementations, the first information or the security policy is received during a PDU session establishment and / or a PDU session modification process.

[0191] Optionally, when the receiving device is a terminal device, it also includes: receiving a NAS message, wherein the NAS message includes the first information.

[0192] In some implementations, the NAS message is received during a PDU session establishment and / or a PDU session modification process.

[0193] In some implementations, the preconfigured rules are the same or different for uplink transmission and downlink transmission.

[0194] In some implementations, the first information is the same or different for uplink transmission and downlink transmission.

[0195] The embodiment of the present application also proposes an integrity protection method, which can be applied to a network device, such as a MN or a SN. Figure 65 is a flowchart of an integrity protection method 500 according to an embodiment of the present application, comprising the following steps:

[0196] S510: The network device receives a security policy of a PDU session and information of a Quality of Service (QoS) flow that needs to be integrity protected and / or encrypted in the PDU session;

[0197] S520: Map the QoS flow that needs to perform integrity protection and / or encryption to the first DRB data;

[0198] S530: Perform integrity protection and / or encryption on the first DRB data.

[0199] In some embodiments, in the above step S520, QoS flows that need to perform integrity protection and / or encryption and whose QoS differences are not greater than a preset threshold are mapped to the same first DRB data.

[0200] Optionally, the information of the quality of service QoS flow that needs to be integrity protected and / or encrypted includes:

[0201] an identified list of QoS flows for which integrity protection and / or encryption is required; or,

[0202] An identified list of QoS flows for which integrity protection and / or encryption need not be performed.

[0203] In some implementations, when the network device is a MN, the method further includes: sending the security policy of the PDU session and information about the data stream that needs to be integrity protected and / or encrypted in the PDU session to the SN.

[0204] Specific embodiments are given below. Figure 6 The integrity protection method 500 shown is described in detail.

[0205] Embodiment three:

[0206] In the prior art, the security policy from the Session Management Function (SMF) is based on the PDU session granularity. In order to better control the effectiveness of DRB IP execution, the embodiment of the present application provides the SMF with a list of QoS flows that need to execute DRB IP and / or encryption in the PDU session (Qos flow idlist); or, the SMF provides the Qos flow idlist that does not need to execute DRB IP and / or encryption in the PDU session. Specifically, it includes:

[0207] Step 1: When SMF sends a security policy based on PDU session granularity to the base station, SMF also provides a Qosflow id list, indicating that the Qos flows in the list need to execute DRB IP and / or encryption, or indicating that the Qos flows in the list do not need to execute DRB IP.

[0208] Step 2: After receiving the security policy, the base station maps the QoS flows with the same or similar QoS parameters in the QoS flows that must execute DRB IP and / or encryption under the PDU session to the same DRB. Alternatively, when executing the binding of DRB and QoS flow, consider whether the QoS flow needs to execute DRB IP and / or encryption, and do not bind the QoS flows that need to execute and do not need to execute DRB IP and / or encryption to the same DRB (even if the QoS parameters corresponding to the two QoS flows are the same or similar).

[0209] In addition, in the MR-DC scenario, when the above network device is MN, MN can further forward the security policy of the PDU session to SN, including the QoS flow id list that needs to execute DRB IP and / or encryption, or the QoS flow id list that does not need to execute DRB IP and / or encryption. SN can perform the mapping of QoS flow to DRB based on the received information.

[0210] The embodiment of the present application also proposes an integrity protection method, which can be applied to network devices, such as SMF. Figure 7 6 is a flowchart of an integrity protection method 600 according to an embodiment of the present application, comprising the following steps:

[0211] S610: The network device sends a security policy for a PDU session and information about a QoS flow that needs to be integrity protected and / or encrypted in the PDU session;

[0212] Optionally, the information of the QoS flow that needs to be integrity protected and / or encrypted includes:

[0213] an identified list of QoS flows for which integrity protection and / or encryption is required; or,

[0214] An identified list of QoS flows for which integrity protection and / or encryption need not be performed.

[0215] It can be seen that the integrity protection method proposed in the embodiment of the present application can improve the execution efficiency of DRB IP, while increasing the application scope of DRB IP, so that DRB IP can be used effectively.

[0216] An embodiment of the present application provides a communication device, which may be a network device or a terminal device. Figure 8 7 is a schematic diagram of a communication device 700 according to an embodiment of the present application, including:

[0217] A selection module 710, configured to select first data to be integrity protected and / or encrypted;

[0218] A first integrity protection module 720, configured to perform integrity protection and / or encryption on the selected first data;

[0219] The data sending module 730 is used to send data including integrity protected and / or encrypted first data.

[0220] In some implementations, the first data is a PDCP SDU or a SDAP SDU.

[0221] In some implementations, the first data includes a portion of data in a PDCP SDU or a portion of data in a SDAP SDU.

[0222] In some embodiments, Fig. 9 As shown, the above-mentioned communication device also includes: an indication module 840, which is used to add indication information of whether the first data performs the integrity protection and / or encryption in the PDCP PDU corresponding to the PDCP SDU or SDAP SDU.

[0223] Optionally, the indication module 840 adds indication information of whether the first data performs the integrity protection and / or encryption in a reserved field of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU.

[0224] In some implementations, the selection module 710 selects the first data in at least one of the following ways:

[0225] Random selection;

[0226] Select based on data transmission rate and processing capability of the receiving device;

[0227] Select based on preconfigured rules;

[0228] A selection is made according to the first information.

[0229] In some implementations, the method further includes: a first rule receiving module 850, configured to receive a first radio resource control RRC signaling, wherein the first RRC signaling carries the preconfigured rule.

[0230] Optionally, the first rule receiving module 850 receives the first RRC signaling during an RRC connection reconfiguration process.

[0231] In some implementations, when the first data is a PDCP SDU or a SDAP SDU, the preconfigured rule includes:

[0232] When PDCP SN mod N=K, integrity protection and / or ciphering are performed on the PDCP SDU or SDAP SDU;

[0233] In the case of PDCP SN mod N≠K, integrity protection and / or encryption is not performed on the PDCP SDU or SDAP SDU; wherein,

[0234] The PDCP SN is a sequence number of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU;

[0235] The mod is a remainder function;

[0236] The N and K are preset parameters.

[0237] In some implementations, when the first data includes a portion of data in a PDCP SDU or a portion of data in an SDAPSDU, the preconfigured rule includes at least one of the following:

[0238] whether the first data includes a header of the PDCP SDU or the SDAP SDU;

[0239] The data volume of the first data;

[0240] The position of the first data in the PDCP SDU or the SDAP SDU.

[0241] In some implementations, when the above-mentioned communication device is a terminal device, the first rule receiving module 850 receives the first RRC signaling sent by the MN and / or the SN.

[0242] In some implementations, when the sending end device is a MN, it further includes: a first rule sending module 860, which is used to generate the pre-configured rule and send the pre-configured rule to the SN and / or the terminal device.

[0243] Optionally, when the sending end device is a SN, it further includes: a second rule sending module 870, which is used to receive or generate the pre-configuration rule and send the pre-configuration rule to the terminal device.

[0244] In some implementations, the above preconfigured rules are set for different PDU sessions; and / or,

[0245] Setting for different data radio bearers DRB; and / or,

[0246] Configure settings for different terminal devices.

[0247] In some implementations, the method further includes: a second rule receiving module 880, configured to receive a second RRC signaling, wherein the second RRC signaling carries a setting method of the preconfigured rule.

[0248] In some embodiments, the first information includes at least one of the following:

[0249] a total rate of the first data corresponding to a PDU session or each QoS flow;

[0250] a selection ratio of the first data;

[0251] The selection rule of the first data.

[0252] It should be understood that the above and other operations and / or functions of the modules in the communication device according to the embodiment of the present application are to achieve Figure 2 The corresponding process of the communication device in the method 200 is not repeated here for the sake of brevity.

[0253] The embodiment of the present application also proposes a communication device, which may be a network device or a terminal device. Fig.10 9 is a schematic diagram of a communication device 900 according to an embodiment of the present application, including:

[0254] A data receiving module 910 is used to receive data, wherein the data includes integrity protected and / or encrypted first data;

[0255] The integrity protection verification module 920 is used to decrypt and / or perform integrity protection verification on the first data.

[0256] In some implementations, the first data is a PDCP SDU or a SDAP SDU.

[0257] In some implementations, the first data includes a portion of data in a PDCP SDU or a portion of data in a SDAP SDU.

[0258] In some embodiments, Fig.11 As shown, it also includes: a first determination module 1030, which is used to determine whether the first data is integrity protected and / or encrypted, or determine the first data that is integrity protected and / or encrypted according to the indication information in the PDCP PDU corresponding to the PDCP SDU or SDAP SDU.

[0259] Optionally, the first determination module 1030 determines whether the first data is integrity protected and / or encrypted, or determines the first data that is integrity protected and / or encrypted, based on the indication information in the reserved field of the PDCP PDU corresponding to the PDCP SDU or SDAP SDU.

[0260] In some embodiments, it further comprises:

[0261] The second determination module 1040 is used to determine whether the first data is integrity protected and / or encrypted, or to determine the first data that is integrity protected and / or encrypted, according to a preconfigured rule or the first information.

[0262] In some implementations, the method further includes: a third rule receiving module 1050, configured to receive a third RRC signaling, wherein the third RRC signaling carries the preconfigured rule.

[0263] Optionally, the third rule receiving module 1050 receives the third RRC signaling during an RRC connection reconfiguration process.

[0264] In some implementations, when the first data is a PDCP SDU or a SDAP SDU, the preconfigured rule includes:

[0265] When PDCP SN mod N=K, integrity protection and / or ciphering are performed on the PDCP SDU or SDAP SDU;

[0266] In the case of PDCP SN mod N≠K, integrity protection and / or encryption is not performed on the PDCP SDU or SDAP SDU; wherein,

[0267] The PDCP SN is a sequence number of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU;

[0268] The mod is a remainder function;

[0269] The N and K are preset parameters.

[0270] In some implementations, when the first data includes a portion of data in a PDCP SDU or a portion of data in an SDAP SDU, the preconfigured rule includes at least one of the following:

[0271] whether the first data includes a header of the PDCP SDU or the SDAP SDU;

[0272] The data volume of the first data;

[0273] The position of the first data in the PDCP SDU or the SDAP SDU.

[0274] Optionally, when the communication device is a terminal device, the third rule receiving module 1050 receives the third RRC signaling sent by the master node MN and / or the secondary node SN.

[0275] In some implementations, when the above-mentioned communication device is a MN, it further includes: a third rule sending module 1060, which is used to generate the pre-configuration rule and send the pre-configuration rule to the SN and / or the terminal device.

[0276] In some implementations, when the above-mentioned communication device is a SN, it further includes: a fourth rule sending module 1070, which is used to receive or generate the pre-configuration rule and send the pre-configuration rule to the terminal device.

[0277] In some implementations, the preconfigured rules are set for different PDU sessions; and / or,

[0278] Setting for different DRB data; and / or,

[0279] Configure settings for different terminal devices.

[0280] In some implementations, the method further includes: a fourth rule receiving module 1080, configured to receive a fourth RRC signaling, wherein the fourth RRC signaling carries a setting method of the preconfigured rule.

[0281] In some embodiments, the first information includes at least one of the following:

[0282] a total rate of the first data corresponding to a PDU session or each QoS flow;

[0283] a selection ratio of the first data;

[0284] The selection rule of the first data.

[0285] It should be understood that the above and other operations and / or functions of the modules in the communication device according to the embodiment of the present application are respectively to implement Figure 5 The corresponding process of the communication device in the method 400 is not repeated here for the sake of brevity.

[0286] An embodiment of the present application provides a network device, which may be a MN or a SN. Fig.12 1 is a schematic diagram of a network device 1100 according to an embodiment of the present application, including:

[0287] A security policy receiving module 1110 is configured to receive a security policy for a PDU session and information about a quality of service (QoS) flow that needs to be integrity protected and / or encrypted in the PDU session;

[0288] A mapping module 1120, configured to map the QoS flow requiring integrity protection and / or encryption to first DRB data;

[0289] The second integrity protection module 1130 is used to perform integrity protection and / or encryption on the first DRB data.

[0290] In some embodiments, the mapping module 1120 maps QoS flows that require integrity protection and / or encryption and whose QoS differences are no greater than a preset threshold to the same first DRB data.

[0291] In some implementations, the information of the quality of service (QoS) flow requiring integrity protection and / or encryption includes:

[0292] an identified list of QoS flows for which integrity protection and / or encryption is required; or,

[0293] An identified list of QoS flows for which integrity protection and / or encryption need not be performed.

[0294] In some embodiments, Fig.13 As shown, when the above-mentioned network device is MN, it also includes: a security policy sending module 1240, which is used to send the security policy of the PDU session and the information of the data flow that needs to be integrity protected and / or encrypted in the PDU session to the SN.

[0295] It should be understood that the above and other operations and / or functions of the modules in the network device according to the embodiment of the present application are respectively to implement Figure 6 The corresponding process of the network device in the method 500 is not repeated here for the sake of brevity.

[0296] An embodiment of the present application also proposes a network device, which communication device can be SMF. Fig.14 1 is a schematic diagram of a network device 1300 according to an embodiment of the present application, including:

[0297] A security policy sending module 1310 is used to send a security policy for a PDU session and information about a quality of service (QoS) flow that needs to be integrity protected and / or encrypted in the PDU session;

[0298] In some implementations, the information of the QoS flow requiring integrity protection and / or encryption includes:

[0299] an identified list of QoS flows for which integrity protection and / or encryption is required; or,

[0300] An identified list of QoS flows for which integrity protection and / or encryption need not be performed.

[0301] It should be understood that the above and other operations and / or functions of the modules in the network device according to the embodiment of the present application are respectively to implement Figure 7 The corresponding process of the network device in the method 600 is not repeated here for the sake of brevity.

[0302] Fig.15 It is a schematic structural diagram of a communication device 1400 according to an embodiment of the present application. Fig.15 The communication device 1400 shown includes a processor 1410, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0303] Alternatively, if Fig.15 As shown, the communication device 1400 may further include a memory 1420. The processor 1410 may call and run a computer program from the memory 1420 to implement the method in the embodiment of the present application.

[0304] The memory 1420 may be a separate device independent of the processor 1410 , or may be integrated into the processor 1410 .

[0305] Alternatively, if Fig.15 As shown, the communication device 1400 may further include a transceiver 1430, and the processor 1410 may control the transceiver 1430 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0306] The transceiver 1430 may include a transmitter and a receiver. The transceiver 1430 may further include an antenna, and the number of the antennas may be one or more.

[0307] Optionally, the communication device 1400 may be the communication device of an embodiment of the present application, and the communication device 1400 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0308] Fig.16 is a schematic structural diagram of a chip 1500 according to an embodiment of the present application. Fig.16 The chip 1500 shown includes a processor 1510, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0309] Alternatively, if Fig.16 As shown, the chip 1500 may further include a memory 1520. The processor 1510 may call and run a computer program from the memory 1520 to implement the method in the embodiment of the present application.

[0310] The memory 1520 may be a separate device independent of the processor 1510 , or may be integrated into the processor 1510 .

[0311] Optionally, the chip 1500 may further include an input interface 1530. The processor 1510 may control the input interface 1530 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0312] Optionally, the chip 1500 may further include an output interface 1540. The processor 1510 may control the output interface 1540 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0313] Optionally, the chip can be applied to the communication device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the communication device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0314] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0315] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0316] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM) or a flash memory. The volatile memory may be a random access memory (RAM).

[0317] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0318] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instruction can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instruction can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0319] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0320] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0321] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. An integrity protection method, comprising: The sending end device selects first data to be integrity protected and / or encrypted; Performing integrity protection and / or encryption on the selected first data; sending data including integrity protected and / or encrypted first data; Wherein, the method further comprises: Adding indication information of whether the integrity protection and / or encryption is performed on the first data in a PDCP protocol data unit PDU corresponding to a PDCP SDU or a SDAP SDU; wherein the indication information is added in a reserved field of a PDCP PDU corresponding to the PDCP SDU or the SDAP SDU; The selection method includes: selecting according to pre-configured rules; The first data is a packet data convergence protocol PDCP service data unit SDU or a service data adaptation protocol SDAPSDU, wherein when the first data is a PDCP SDU or a SDAP SDU, the preconfigured rule includes: When PDCP SN mod N = K, integrity protection and / or ciphering is performed on the PDCP SDU or SDAP SDU; In PDCP SN mod N In the case of K, the PDCP SDU or SDAP SDU does not perform integrity protection and / or encryption; wherein, The PDCP SN is a sequence number of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU; The mod is a remainder function; The N and K are preset parameters.

2. The method according to claim 1, wherein: The first data includes a portion of data in a PDCP SDU or a portion of data in a SDAP SDU.

3. The method according to claim 1, wherein: The selection method also includes at least one of the following: Random selection; Select based on data transmission rate and processing capability of the receiving device; A selection is made according to the first information.

4. The method according to claim 1, further comprising: A first radio resource control RRC signaling is received, where the first RRC signaling carries the preconfigured rule.

5. The method according to claim 4, wherein: The first RRC signaling is received during the RRC connection reconfiguration process.

6. The method according to claim 1, wherein: When the first data includes a portion of data in a PDCP SDU or a portion of data in an SDAP SDU, the preconfigured rule further includes at least one of the following: whether the first data includes a header of the PDCP SDU or the SDAP SDU; The data volume of the first data; The position of the first data in the PDCP SDU or the SDAP SDU.

7. According to the method of claim 4, when the sending end device is a terminal device, the terminal device receives the first RRC signaling sent by the master node MN and / or the secondary node SN.

8. The method according to claim 1, when the transmitting end device is a MN, further comprising: Generate the pre-configuration rules, and send the pre-configuration rules to the SN and / or the terminal device.

9. The method according to claim 1, when the transmitting end device is a SN, further comprising: The pre-configuration rule is received or generated, and the pre-configuration rule is sent to the terminal device.

10. The method according to any one of claims 1 to 9, wherein: The preconfigured rules are set for different PDU sessions; and / or, The pre-configuration rules are set for different data radio bearers (DRBs); and / or, The preconfiguration rules are set for different terminal devices.

11. The method according to claim 10, further comprising: A second RRC signaling is received, where the second RRC signaling carries a setting method of the preconfigured rule.

12. The method according to claim 3, wherein the first information comprises at least one of the following: a total rate of the first data corresponding to a PDU session or each QoS flow; a selection ratio of the first data; The selection rule of the first data.

13. The method according to claim 3 or 12, when the transmitting end device is a base station, further comprising: receiving the first information; or, A security policy is received, where the security policy includes the first information.

14. The method according to claim 13, wherein: The first information or the security policy is received during a PDU session establishment and / or a PDU session modification process.

15. The method according to claim 3 or 12, when the transmitting end device is a terminal device, further comprising: A non-access layer NAS message is received, where the NAS message includes the first information.

16. The method according to claim 15, wherein: The NAS message is received during a PDU session establishment and / or a PDU session modification process.

17. The method according to any one of claims 1 to 9, wherein: The preconfigured rules are the same or different for uplink transmission and downlink transmission.

18. The method according to claim 3, wherein: The first information is the same or different for uplink transmission and downlink transmission.

19. An integrity protection method, comprising: The receiving device receives data, wherein the data includes first data that has been integrity protected and / or encrypted; Decrypting and / or verifying the integrity of the first data; Wherein, the method further comprises: Determine whether the first data is integrity protected and / or encrypted, or determine the first data that is integrity protected and / or encrypted, according to indication information in the PDCP PDU corresponding to the PDCP SDU or the SDAP SDU; wherein the indication information is added to a reserved field of the PDCP PDU corresponding to the PDCP SDU or the SDAP SDU; Wherein, the method further comprises: Determine, according to a preconfigured rule, whether the first data is integrity protected and / or encrypted, or determine the first data that is integrity protected and / or encrypted; The first data is PDCP SDU or SDAPSDU, and when the first data is PDCP SDU or SDAP SDU, the preconfigured rule includes: When PDCP SN mod N = K, integrity protection and / or ciphering is performed on the PDCP SDU or SDAP SDU; In PDCP SN mod N In the case of K, the PDCP SDU or SDAP SDU does not perform integrity protection and / or encryption; wherein, The PDCP SN is a sequence number of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU; The mod is a remainder function; The N and K are preset parameters.

20. The method according to claim 19, wherein: The first data includes a portion of data in a PDCP SDU or a portion of data in a SDAP SDU.

21. The method of claim 19, further comprising: According to the first information, it is determined whether the first data is integrity protected and / or encrypted, or the first data is integrity protected and / or encrypted.

22. The method of claim 19, further comprising: A third RRC signaling is received, where the third RRC signaling carries the preconfigured rule.

23. The method according to claim 22, wherein: The third RRC signaling is received during the RRC connection reconfiguration process.

24. The method according to claim 19, wherein: When the first data includes a portion of data in a PDCP SDU or a portion of data in an SDAP SDU, the preconfigured rule further includes at least one of the following: whether the first data includes a header of the PDCP SDU or the SDAP SDU; The data volume of the first data; The position of the first data in the PDCP SDU or the SDAP SDU.

25. According to the method of claim 22, when the receiving device is a terminal device, the terminal device receives the third RRC signaling sent by the master node MN and / or the secondary node SN.

26. The method according to claim 19, when the receiving end device is a MN, further comprising: Generate the pre-configuration rules, and send the pre-configuration rules to the SN and / or the terminal device.

27. The method according to claim 19, when the receiving end device is a SN, further comprising: The pre-configuration rule is received or generated, and the pre-configuration rule is sent to the terminal device.

28. The method according to any one of claims 19 to 27, wherein: The preconfigured rules are set for different PDU sessions; and / or, The preconfigured rules are set for different DRB data; and / or, The preconfiguration rules are set for different terminal devices.

29. The method according to claim 28, further comprising: A fourth RRC signaling is received, where the fourth RRC signaling carries a setting method of the preconfiguration rule.

30. The method according to claim 21, wherein the first information comprises at least one of the following: a total rate of the first data corresponding to a PDU session or each QoS flow; a selection ratio of the first data; The selection rule of the first data.

31. The method according to claim 21 or 30, when the receiving end device is a base station, further comprising: receiving the first information; or, A security policy is received, where the security policy includes the first information.

32. The method according to claim 31, wherein: The first information or the security policy is received during a PDU session establishment and / or a PDU session modification process.

33. The method according to claim 21 or 30, when the receiving device is a terminal device, further comprising: A non-access layer NAS message is received, where the NAS message includes the first information.

34. The method of claim 33, wherein: The NAS message is received during a PDU session establishment and / or a PDU session modification process.

35. The method according to any one of claims 19 to 27, wherein: The preconfigured rules are the same or different for uplink transmission and downlink transmission.

36. The method of claim 21, wherein: The first information is the same or different for uplink transmission and downlink transmission.

37. An integrity protection method, comprising: The network device receives a security policy of a PDU session and information of a quality of service (QoS) flow that needs to be integrity protected and / or encrypted in the PDU session; Mapping the QoS flow requiring integrity protection and / or encryption to the first DRB data; Performing integrity protection and / or encryption on the first DRB data; Wherein, the method further comprises: Adding indication information in a reserved field of a PDCP PDU corresponding to a PDCP SDU or a SDAP SDU, wherein the indication information is used to indicate whether the first DRB data is integrity protected and / or encrypted, or to indicate the first DRB data that is integrity protected and / or encrypted; Whether the first DRB data is integrity protected and / or encrypted is determined according to a preconfigured rule, wherein when the first DRB data is a PDCP SDU or a SDAP SDU, the preconfigured rule includes: When PDCP SN mod N = K, integrity protection and / or ciphering is performed on the PDCP SDU or SDAP SDU; In PDCP SN mod N In the case of K, the PDCP SDU or SDAP SDU does not perform integrity protection and / or encryption; wherein, The PDCP SN is a sequence number of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU; The mod is a remainder function; The N and K are preset parameters.

38. The method of claim 37, wherein: QoS flows that require integrity protection and / or encryption and whose QoS differences are no greater than a preset threshold are mapped to the same first DRB data.

39. The method of claim 37, wherein: The information of the quality of service (QoS) flow that needs to be integrity protected and / or encrypted includes: an identified list of QoS flows for which integrity protection and / or encryption is required; or, An identified list of QoS flows for which integrity protection and / or encryption need not be performed.

40. The method according to any one of claims 37 to 39, when the network device is a MN, further comprising: The security policy of the PDU session and information about the data stream that needs to be integrity protected and / or encrypted in the PDU session are sent to the SN.

41. An integrity protection method, comprising: The network device sends a security policy for a PDU session and information about a quality of service (QoS) flow that needs to be integrity protected and / or encrypted in the PDU session; Wherein, the method further comprises: Adding indication information in a reserved field of a PDCP PDU corresponding to a PDCP SDU or a SDAP SDU, wherein the indication information is used to indicate whether the first DRB data is integrity protected and / or encrypted, or to indicate the first DRB data that is integrity protected and / or encrypted; Whether the first DRB data is integrity protected and / or encrypted is determined according to a preconfigured rule, wherein when the first DRB data is a PDCP SDU or a SDAP SDU, the preconfigured rule includes: When PDCP SN mod N = K, integrity protection and / or ciphering is performed on the PDCP SDU or SDAP SDU; In PDCP SN mod N In the case of K, the PDCP SDU or SDAP SDU does not perform integrity protection and / or encryption; wherein, The PDCP SN is a sequence number of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU; The mod is a remainder function; The N and K are preset parameters.

42. The method according to claim 41, wherein: The information of the QoS flow that needs to perform integrity protection and / or encryption includes: an identified list of QoS flows for which integrity protection and / or encryption is required; or, An identified list of QoS flows for which integrity protection and / or encryption need not be performed.

43. A communication device comprising: A selection module, configured to select first data to be integrity protected and / or encrypted; A first integrity protection module, configured to perform integrity protection and / or encryption on the selected first data; A data sending module, used for sending data including integrity protected and / or encrypted first data; as well as an indication module, configured to add indication information of whether the integrity protection and / or encryption is performed on the first data in a PDCP PDU corresponding to a PDCP SDU or an SDAP SDU; wherein the indication module adds indication information of whether the integrity protection and / or encryption is performed on the first data in a reserved field of the PDCP PDU corresponding to the PDCP SDU or the SDAPSDU; The manner in which the selection module selects the first data includes: selecting according to a preconfigured rule; The first data is a packet data convergence protocol PDCP service data unit SDU or a service data adaptation protocol SDAPSDU, wherein when the first data is a PDCP SDU or a SDAP SDU, the preconfigured rule includes: When PDCP SN mod N = K, integrity protection and / or ciphering is performed on the PDCP SDU or SDAP SDU; In PDCP SN mod N In the case of K, the PDCP SDU or SDAP SDU does not perform integrity protection and / or encryption; wherein, The PDCP SN is a sequence number of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU; The mod is a remainder function; The N and K are preset parameters.

44. The communication device according to claim 43, wherein: The first data includes a portion of data in a PDCP SDU or a portion of data in a SDAP SDU.

45. The communication device according to claim 43, wherein: The selection module further selects the first data in at least one of the following ways: Random selection; Select based on data transmission rate and processing capability of the receiving device; A selection is made according to the first information.

46. ​​The communication device of claim 43, further comprising: The first rule receiving module is used to receive a first radio resource control RRC signaling, where the first RRC signaling carries the pre-configured rule.

47. The communication device according to claim 46, wherein: The first rule receiving module receives the first RRC signaling during the RRC connection reconfiguration process.

48. The communication device of claim 43, wherein: When the first data includes a portion of data in a PDCP SDU or a portion of data in an SDAP SDU, the preconfigured rule further includes at least one of the following: whether the first data includes a header of the PDCP SDU or the SDAP SDU; The data volume of the first data; The position of the first data in the PDCP SDU or the SDAP SDU.

49. According to the communication device according to claim 46, when the communication device is a terminal device, the first rule receiving module receives the first RRC signaling sent by the master node MN and / or the secondary node SN.

50. The communication device according to claim 43, when the communication device is a MN, further comprising: The first rule sending module is used to generate the pre-configuration rule and send the pre-configuration rule to the SN and / or the terminal device.

51. The communication device according to claim 43, when the communication device is a SN, further comprising: The second rule sending module is used to receive or generate the pre-configuration rule and send the pre-configuration rule to the terminal device.

52. The communication device according to any one of claims 43 to 51, wherein: The preconfigured rules are set for different PDU sessions; and / or, The pre-configuration rules are set for different data radio bearers (DRBs); and / or, The preconfiguration rules are set for different terminal devices.

53. The communication device according to claim 52, further comprising: The second rule receiving module is used to receive a second RRC signaling, where the second RRC signaling carries a setting method of the pre-configured rule.

54. The communication device according to claim 45, wherein the first information comprises at least one of the following: a total rate of the first data corresponding to a PDU session or each QoS flow; a selection ratio of the first data; The selection rule of the first data.

55. A communication device comprising: A data receiving module, used for receiving data, wherein the data includes first data which has been integrity protected and / or encrypted; an integrity protection verification module, configured to perform decryption and / or integrity protection verification on the first data; as well as a first determining module, configured to determine whether the first data is integrity protected and / or encrypted, or determine the first data that is integrity protected and / or encrypted, according to indication information in a PDCP PDU corresponding to the PDCP SDU or the SDAP SDU, wherein the first determining module determines whether the first data is integrity protected and / or encrypted, or determines the first data that is integrity protected and / or encrypted, according to indication information in a reserved field of the PDCP PDU corresponding to the PDCP SDU or the SDAP SDU; A second determination module, configured to determine whether the first data is integrity protected and / or encrypted, or to determine the first data is integrity protected and / or encrypted, according to a preconfigured rule; The first data is PDCP SDU or SDAPSDU; when the first data is PDCP SDU or SDAP SDU, the preconfigured rule includes: When PDCP SN mod N = K, integrity protection and / or ciphering is performed on the PDCP SDU or SDAP SDU; In PDCP SN mod N In the case of K, the PDCP SDU or SDAP SDU does not perform integrity protection and / or encryption; wherein, The PDCP SN is a sequence number of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU; The mod is a remainder function; The N and K are preset parameters.

56. The communication device according to claim 55, wherein: The first data includes a portion of data in a PDCP SDU or a portion of data in a SDAP SDU.

57. According to the communication device according to claim 55, the second determination module is also used to determine whether the first data is integrity protected and / or encrypted, or to determine the first data that is integrity protected and / or encrypted, based on the first information.

58. The communication device of claim 55, further comprising: The third rule receiving module is used to receive a third RRC signaling, where the third RRC signaling carries the pre-configured rule.

59. The communication device according to claim 58, wherein: The third rule receiving module receives the third RRC signaling during the RRC connection reconfiguration process.

60. The communication device of claim 55, wherein: When the first data includes a portion of data in a PDCP SDU or a portion of data in an SDAP SDU, the preconfigured rule further includes at least one of the following: whether the first data includes a header of the PDCP SDU or the SDAP SDU; The data volume of the first data; The position of the first data in the PDCP SDU or the SDAP SDU.

61. According to the communication device according to claim 58, when the communication device is a terminal device, the third rule receiving module receives the third RRC signaling sent by the master node MN and / or the secondary node SN.

62. The communication device according to claim 55, when the communication device is a MN, further comprising: The third rule sending module is used to generate the pre-configuration rule and send the pre-configuration rule to the SN and / or the terminal device.

63. The communication device according to claim 55, when the communication device is a SN, further comprising: The fourth rule sending module is used to receive or generate the pre-configured rule and send the pre-configured rule to the terminal device.

64. A communication device according to any one of claims 55 to 63, wherein: The preconfigured rules are set for different PDU sessions; and / or, The preconfigured rules are set for different DRB data; and / or, The preconfiguration rules are set for different terminal devices.

65. The communication device according to claim 64, further comprising: The fourth rule receiving module is used to receive a fourth RRC signaling, where the fourth RRC signaling carries a setting method of the pre-configured rule.

66. The communication device according to claim 57, wherein the first information comprises at least one of the following: a total rate of the first data corresponding to a PDU session or each QoS flow; a selection ratio of the first data; The selection rule of the first data.

67. A network device comprising: A security policy receiving module, configured to receive a security policy for a PDU session and information about a quality of service (QoS) flow in the PDU session that needs to be integrity protected and / or encrypted; A mapping module, configured to map the QoS flow requiring integrity protection and / or encryption to first DRB data; A second integrity protection module, configured to perform integrity protection and / or encryption on the first DRB data; The network device is further used to add indication information to a reserved field of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU, wherein the indication information is used to indicate whether the first DRB data is integrity protected and / or encrypted, or to indicate the first DRB data that is integrity protected and / or encrypted; Whether the first DRB data is integrity protected and / or encrypted is determined according to a preconfigured rule, wherein when the first DRB data is a PDCP SDU or a SDAP SDU, the preconfigured rule includes: When PDCP SN mod N = K, integrity protection and / or ciphering is performed on the PDCP SDU or SDAP SDU; In PDCP SN mod N In the case of K, the PDCP SDU or SDAP SDU does not perform integrity protection and / or encryption; wherein, The PDCP SN is a sequence number of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU; The mod is a remainder function; The N and K are preset parameters.

68. The network device according to claim 67, wherein: The mapping module maps the QoS flows that need to perform integrity protection and / or encryption and whose QoS differences are not greater than a preset threshold to the same first DRB data.

69. The network device according to claim 67, wherein: The information of the quality of service (QoS) flow that needs to be integrity protected and / or encrypted includes: an identified list of QoS flows for which integrity protection and / or encryption is required; or, An identified list of QoS flows for which integrity protection and / or encryption need not be performed.

70. The network device according to any one of claims 67 to 69, when the network device is a MN, further comprising: The security policy sending module is used to send the security policy of the PDU session and the information of the data flow that needs to be integrity protected and / or encrypted in the PDU session to the SN.

71. A network device comprising: A security policy sending module, used to send the security policy of the PDU session and information of the quality of service QoS flow that needs to be integrity protected and / or encrypted in the PDU session; The network device is further used to add indication information to a reserved field of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU, wherein the indication information is used to indicate whether the first DRB data is integrity protected and / or encrypted, or to indicate the first DRB data that is integrity protected and / or encrypted; Whether the first DRB data is integrity protected and / or encrypted is determined according to a preconfigured rule, wherein when the first DRB data is a PDCP SDU or a SDAP SDU, the preconfigured rule includes: When PDCP SN mod N = K, integrity protection and / or ciphering is performed on the PDCP SDU or SDAP SDU; In PDCP SN mod N In the case of K, the PDCP SDU or SDAP SDU does not perform integrity protection and / or encryption; wherein, The PDCP SN is a sequence number of a PDCP PDU corresponding to the PDCP SDU or SDAP SDU; The mod is a remainder function; The N and K are preset parameters.

72. The network device according to claim 71, wherein: The information of the QoS flow that needs to perform integrity protection and / or encryption includes: an identified list of QoS flows for which integrity protection and / or encryption is required; or, An identified list of QoS flows for which integrity protection and / or encryption need not be performed.

73. A communication device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 1 to 36.

74. A network device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 37 to 42.

75. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 36.

76. A chip, comprising: A processor, configured to call and run a computer program from a memory so that a device equipped with the chip executes a method as claimed in any one of claims 37 to 42.

77. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 36.

78. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 37 to 42.

79. A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 36.

80. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 37 to 42.