WO2020215323A1 - 用于完整性保护的方法或设备 - Google Patents

用于完整性保护的方法或设备 Download PDF

Info

Publication number
WO2020215323A1
WO2020215323A1 PCT/CN2019/084607 CN2019084607W WO2020215323A1 WO 2020215323 A1 WO2020215323 A1 WO 2020215323A1 CN 2019084607 W CN2019084607 W CN 2019084607W WO 2020215323 A1 WO2020215323 A1 WO 2020215323A1
Authority
WO
WIPO (PCT)
Prior art keywords
parameter value
bearer parameter
bearer
communication
lcid
Prior art date
Application number
PCT/CN2019/084607
Other languages
English (en)
French (fr)
Inventor
许阳
卢前溪
***
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to EP19926622.2A priority Critical patent/EP3846519B1/en
Priority to PCT/CN2019/084607 priority patent/WO2020215323A1/zh
Priority to AU2019442498A priority patent/AU2019442498A1/en
Priority to CN201980057442.0A priority patent/CN112655236A/zh
Priority to CN202110438087.0A priority patent/CN113194473B/zh
Publication of WO2020215323A1 publication Critical patent/WO2020215323A1/zh
Priority to US17/216,637 priority patent/US11979747B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/106—Packet or message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3242—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/80—Wireless
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the embodiments of the present application relate to the field of communication technology, and in particular to a method or device for integrity protection.
  • a secret key can be used for integrity protection at the Packet Data Convergence Protocol (PDCP) layer.
  • PDCP Packet Data Convergence Protocol
  • the embodiment of the present application provides a method or device for integrity protection of side link communication or Uu interface communication, which can realize the integrity protection of the PDCP layer, thereby improving the security of communication.
  • a method for integrity protection of side-link communication including: obtaining a first bearer BEARER parameter value based on at least one of the following: The logical channel identifier LCID corresponding to the data, the access communication standard adopted by the side-link communication, the BEARER parameter value allocated for the side-link communication, the preset BEARER parameter value, wherein the transmitted data corresponds to The bit length of the LCID is greater than the bit length of the first BEARER parameter value; based on the first BEARER parameter value, the integrity message authentication code MAC-I or expected integrity for the side link communication is calculated Message authentication code XMAC-I.
  • a method for integrity protection of Uu interface communication including: obtaining a first bearer BEARER parameter value based on at least one of the following: a logical channel identifier LCID for sidelink communication The bit length of, the BEARER parameter value allocated for the Uu interface communication, and the preset BEARER parameter value; based on the first BEARER parameter value, the integrity message authentication code MAC-I or expected for the Uu interface communication is calculated The integrity message authentication code XMAC-I.
  • a device for integrity protection of sidelink communication is provided, which is used to implement the method in the above-mentioned first aspect.
  • the device for integrity protection of side-link communication includes a functional module for executing the above-mentioned first aspect.
  • a device for integrity protection of Uu interface communication is provided, which is used to execute the method in the first aspect.
  • the device for integrity protection of Uu interface communication includes a functional module for executing the above-mentioned first aspect.
  • a device for integrity protection of side link communication 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 to execute the method in the above first aspect.
  • a device for integrity protection of Uu interface communication 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 to execute the method in the above first aspect.
  • a chip is provided for implementing the method in the first or second aspect.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the method in the first or second aspect.
  • a computer-readable storage medium for storing a computer program that enables a computer to execute the method in the first or second aspect.
  • a computer program product including computer program instructions that cause a computer to execute the method in the first or second aspect.
  • a computer program which when running on a computer, causes the computer to execute the method in the first or second aspect.
  • the first bearer BEARER parameter value is obtained based on at least one of the following: the logical channel identifier LCID corresponding to the data transmitted in the side link communication, and the access used in the side link communication Communication standard, the BEARER parameter value allocated for the sidelink communication, and the preset BEARER parameter value, wherein the bit length of the LCID corresponding to the transmitted data is greater than the bit length of the first BEARER parameter value;
  • the integrity message authentication code MAC-I or the expected integrity message authentication code XMAC-I for the side link communication is calculated, so that the PDCP layer based on the side link communication can be realized Integrity protection, which can improve the security of communication.
  • the first bearer parameter value based on at least one of the following: the bit length of the logical channel identifier LCID used for sidelink communication, the BEARER parameter value allocated for the Uu interface communication, and the preset BEARER parameter Value; based on the first BEARER parameter value, calculate the integrity message authentication code MAC-I or the expected integrity message authentication code XMAC-I for the Uu interface communication, so that the PDCP layer based on Uu interface communication can be realized Integrity protection, which can improve the security of communication.
  • Fig. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a method for integrity protection of side-link communication provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of calculating MAC-1 or XMAC-I according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a method for obtaining BEARER parameter values provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a method for integrity protection of Uu interface communication provided by an embodiment of the present application.
  • Fig. 6 is a schematic diagram of a device for integrity protection of sidelink communication provided by an embodiment of the present application.
  • Fig. 7 is a schematic diagram of a device for integrity protection of Uu interface communication provided by an embodiment of the present application.
  • Fig. 8 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System of Mobile Communication
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the network device mentioned in the embodiment of the present application may be a device that communicates with a terminal device (or called a communication terminal or terminal).
  • the network device can provide communication coverage for a specific geographic area, and can communicate with terminal devices located in the coverage area.
  • the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or a base station (gNB) in a new wireless system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device can be a mobile Switching centers, relay stations, access points, in-vehicle devices, wearable devices, hubs, switches, bridges, routers, network side devices in 5G networks, or future evolution of public land mobile networks (Public Land Mobile Network, PLMN) Network equipment
  • the terminal equipment mentioned in the embodiments of this application includes, but is not limited to, connection via a wired line, such as via a public switched telephone network (PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, and direct cable connection ; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and/or another terminal device that is set to receive/send communication signals; and/or Internet of Things (IoT) equipment.
  • a terminal device set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal” or a "mobile terminal".
  • Examples of mobile terminals include, but are not limited to, satellites or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio phone transceivers Electronic device.
  • Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in the future evolution of PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device 120 and the network device 110 may communicate with each other, specifically, the communication may be performed through a Uu interface, and/or the terminal device 120 and the terminal device 120 may communicate with each other.
  • the communication is carried out through the side link (Sidelink, SL).
  • the terminal device 120 communicates with the terminal device 120 through a side link, which can also be referred to as using a PC5 interface to communicate.
  • the side link communication in the embodiments of the present application can be used for communication of the following services: Vehicle to Anything (V2X), Network Controlled Interactive Services (NCIS), and Public Safety (Public Safty) services.
  • FIG. 2 is a schematic flowchart of a method 200 for integrity protection of sidelink communication.
  • the method 200 includes at least part of the following content.
  • the method 200 can be implemented by a terminal device.
  • the method 200 can be implemented by the sender of side link communication.
  • the terminal device as the sender can be used to calculate the integrity message authentication code (Message Authentication Code-Integrity, MAC-I); or,
  • the method can also be implemented by the receiving end of side link communication.
  • the terminal device as the receiving end can be used for computing (eXpected Message Authentication Code-Integrity, XMAC-I).
  • the bearer (BEARER) parameter value may be a parameter value used to obtain MAC-I or XMAC-I, and the bit length of the BEARER parameter value may be 5.
  • the BEARER parameter value may be a parameter value with a fixed length, and the fixed length may be preset on the terminal device, or may be configured by the network device for the terminal device.
  • the BEARER parameter value may also have other names, for example, logical channel identity (LCID) parameter value (for example, in the case where the parameter value is obtained based on LCID), input parameter value, etc., in this embodiment of the application There is no specific restriction on this.
  • LCID logical channel identity
  • the BEARER parameter value can be combined with other parameters to obtain MAC-I or XMAC-I.
  • the other parameters may include at least one of a PDCP count (COUNT) value, a direction of side link communication, an integrity protection key, an integrity protection key identifier, and data packet content.
  • COUNT PDCP count
  • the algorithm for calculating MAC-I or XMAC-I may be a network integrity algorithm (Network Integrity Algorithm, NIA) algorithm.
  • the PDCP COUNT value can include 32 bits. Bits 0-15 of the 32 bits are KD- sess ID, where KD- sess is the 16-bit generated by the root key of the terminal device at the granularity of each session.
  • the 31 bits are the Counter parameter value, where Counter is a counter, and the counter can be incremented by one each time a message is sent, and the K D-sess ID and Counter parameter values can be carried in the PDCP header.
  • the terminal device can set the K D-sess ID and Counter parameter values to 0.
  • the K D-sess ID and Counter parameter values can also be set to 0 in the PDCP message.
  • the integrity protection key may be a Proximity Service (ProSe) encryption key (ProSe Encryption Key, PEK), where the terminal device may have an algorithm identifier and a ProSe Group Key (PGK), and the PGK may be The corresponding secret key of the group to which the terminal device belongs.
  • the terminal can derive a ProSe Traffic Key (PTK) based on PGK.
  • the PTK can be exclusive to the terminal device and can be carried in the header of the user data message.
  • the terminal device can be derived based on PTK (ProSe Encryption Key, PEK), and PEK can be used to encrypt data.
  • the bit length of the integrity protection key can be 128 bits.
  • the direction of side link communication can be represented by 1 bit, and the direction of side link communication can include the direction from the terminal device that initiates side link communication to the direction of the terminal device that initiates side link communication (this direction
  • the corresponding bit value can be 1), and the direction from the terminal device that initiates sidelink communication to the terminal device that initiates sidelink communication (the bit value corresponding to this direction can be 0).
  • the terminal device obtains the first BEARER parameter value based on at least one of the following:
  • the bit length of the LCID corresponding to the transmitted data is greater than the bit length of the first BEARER parameter value.
  • the bit length of the LCID is 6, and the bit length of the first BEARER parameter value is 5.
  • the LCID mentioned in the embodiments of this application can be assigned by network equipment or terminal equipment (for example, the group head of the terminal equipment group to which the terminal equipment belongs in side-link communication, side-link communication
  • the sending end in the side link communication, the receiving end in the side link communication) or it can be negotiated between the sending end and the receiving end in the side link communication.
  • the LCID may be allocated or negotiated when the LC is established.
  • the bit length of the LCID corresponding to the transmitted data is greater than the first BEARER parameter value for description, but the embodiments of the present application are not limited to this, and the bit length of the LCID in the embodiments of the present application may also be Less than the value of the first BEARER parameter.
  • the terminal device may obtain the first BEARER parameter value based on one of them, or obtain the BEARER parameter value based on multiple of them. The following will give an example of how to obtain the BEARER parameter value.
  • the terminal device may obtain the first BEARER parameter value based on the LCID corresponding to the transmitted data.
  • the LCID When the bit length of the LCID is equal to the expected bit length of the BEARER parameter value, the LCID can be directly used as the BEARER parameter value. However, in some communication systems (for example, 5G communication systems), the bit length of the LCID may not be equal to the BEARER parameter value If the expected bit length does not solve the problem of the mismatch, the terminal device can process the LCID to obtain the first BEARER parameter value.
  • the processing performed on the LCID corresponding to the transmitted data may specifically include: intercepting a part of the bit value of the LCID corresponding to the transmitted data to generate the first BEARER parameter value.
  • the bit length of the LCID is greater than the bit length of the expected BEARER parameter value, if the first BEARER parameter value needs to be obtained based on the LCID, a part of the bit value of the LCID can be truncated as the first BEARER parameter value.
  • intercepting a part of the bit value of the LCID as the first BEARER parameter value means that the part of the bit value is used to generate the first BEARER parameter value, and other bit values are discarded.
  • the terminal device may intercept the lowest N bit value or the highest N bit value of the LCID corresponding to the transmitted data to generate the first BEARER parameter value. Wherein, the N may be equal to the bit length of the first BEARER parameter value.
  • the bit length of the LCID is 6, and the allowed bit length of the first BEARER parameter value is 5, then 5 bit values can be cut from the LCID as the first BEARER parameter value, for example, the highest value can be 5 One bit value (for example, (a) in FIG. 4) or the lowest 5 bit value (for example, (b) in FIG. 4) is used as the first BEARER parameter value.
  • the terminal device can intercept the lowest at least one bit and the highest at least one bit of the LCID, and combine the lowest at least one bit and the highest at least one bit to form the first BEARER parameter value.
  • the LCID may also have other processing.
  • the value corresponding to the LCID may be subtracted or divided by a certain value to obtain the first BEARER parameter value.
  • the terminal device may obtain the BEARER parameter value corresponding to the LCID corresponding to the transmitted data from the correspondence between at least one LCID and at least one BEARER parameter value, as the first BEARER Parameter value.
  • the LCID and the BEARER parameter value may have a corresponding relationship (for example, a one-to-one relationship, a one-to-many relationship, or a many-to-one relationship), where the corresponding relationship may be preset on the terminal device, or It can be configured by the network device or by the group header of the terminal device group to which the terminal device belongs, or it can be negotiated between the sender and the receiver.
  • the terminal device may also obtain the BEARER parameter value corresponding to the LCID corresponding to the transmitted data from the corresponding relationship as the first BEARER parameter value.
  • the terminal device may obtain the first BEARER parameter value based on the access communication standard adopted by the sidelink communication.
  • the terminal device obtains the BEARER parameter value corresponding to the access communication standard adopted by the sidelink communication from the correspondence between at least one access communication standard and at least one BEARER parameter value, as the first BEARER parameter value.
  • the access communication standard and the BEARER parameter value may have a corresponding relationship (for example, a one-to-one correspondence, a one-to-many relationship, or a many-to-one relationship), where the corresponding relationship may be preset on the terminal device It can also be configured by the network device or by the group header of the terminal device group to which the terminal device belongs, or it can be negotiated between the sender and the receiver.
  • the terminal device may also obtain the BEARER parameter value corresponding to the adopted access communication standard from the corresponding relationship as the first BEARER parameter value.
  • the access communication standard mentioned in the embodiment of the present application may be the NR communication standard or the E-UTRA communication standard.
  • the first BEARER parameter value can be a value.
  • the access communication standard adopted by the side link communication is the E-UTRA communication standard
  • the first The BEARER parameter value can be another value.
  • the terminal device may obtain the first BEARER parameter value based on the BEARER parameter value allocated for sidelink communication.
  • the BEARER parameter value allocated for the side link communication is allocated by the terminal device (for example, the terminal device that initiates the side link communication, the group head of the terminal device group to which the terminal device of the side link communication belongs); Or, the BEARER parameter value allocated for the sidelink communication is allocated by the network device.
  • the BEARER parameter value allocated for sidelink communication may be per logical channel, that is, the BEARER parameter value is allocated at the granularity of the logical channel.
  • the BEARER parameter value may be allocated in the LCID.
  • the BEARER parameter value allocated for sidelink communication may be per terminal device, that is, the BEARER parameter value is allocated at the granularity of the terminal device.
  • MAC-I or XMAC-I it may be The BEARER parameter value allocated by the end terminal is determined to be the first BEARER parameter value, or, alternatively, the BEARER parameter value allocated to the receiving end terminal may be determined as the first BEARER parameter value.
  • the terminal device may determine the first BEARER parameter value based on the preset BEARER parameter value.
  • the terminal device may determine the preset BEARER parameter value as the first BEARER parameter value.
  • the terminal device calculates MAC-I or XMAC-I for the side link communication.
  • the calculated MAC-I can be encapsulated into the PDCP header.
  • the receiver After the sender calculates the MAC-I, the calculated MAC-I can be encapsulated into the PDCP header.
  • the receiver After the receiver receives the message, it can calculate XMAC-I based on the received message, and combine XMAC-I with the PDCP header Compare the MAC-I in the MAC-I, if the two values are equal, it means that the integrity protection is successful, otherwise, it means that the message content has been changed.
  • the bit length of the first BEARER parameter value is equal to the bit length of the second BEARER parameter value
  • the second BEARER parameter value is used to calculate MAC-I or XMAC in Uu interface communication. -I.
  • multiple implementations are provided above to obtain the first BEARER parameter value, so that the bit length of the first BEARER parameter value may be equal to the bit length of the second BEARER parameter.
  • the bit length of the first BEARER parameter value and the bit length of the second BEARER parameter value may both be 5 bits, and the terminal device may determine the bit length of the first BEARER parameter value based on the bit length of the second BEARER parameter value, and Based on the determined bit length, the LCID corresponding to the transmitted data is processed, for example, a certain number of bit values are intercepted as the first BEARER parameter value.
  • the second BEARER parameter value is classified into BEARER parameter values used for non-access stratum (NAS) and access stratum (AS).
  • the second BEARER parameter value may be NAS Connection Identifier.
  • the value may be 0X01, and for non-3GPP, the value may be 0XX00;
  • the second BEARER parameter value can be the value of the SRB identifier or can be filled with a certain number of bit values before or after the SRB identifier (2 bits) (For example, 0), to generate the second BEARER parameter value;
  • the second BEARER parameter value may be DRB, or may be obtained by processing the DRB identifier, for example, the DRB identifier is taken The value is [1-32], so you can directly subtract one from the value of the DRB identifier to form a 5-bit binary value as the second BEARER parameter value.
  • the bit length used to calculate the BEARER parameter value of MAC-I or XMAC-I in sidelink communication is equal to the bit length used to calculate the BEARER parameter value of MAC-I or XMAC-I in Uu interface communication.
  • the bit length can avoid the problem of mismatch between MAC-I or XMAC-I calculations in the two communication modes, and only one set of MAC-I or XMAC-I calculation units can be needed, which reduces the complexity of terminal equipment implementation.
  • the first BEARER parameter value is obtained by the above-mentioned method, so that the bit length of the first BEARER parameter value can be equal to the bit length of the second BEARER parameter value, and it is not necessary to change the Uu interface communication to calculate the MAC-I or XMAC-I
  • the architecture can make full use of existing mechanisms and parameters, and make little changes to the existing ones.
  • the existing BEARER parameter value is 5 bits
  • the 5-bit BEARER parameter value is obtained by processing the LCID.
  • FIG. 5 is a schematic flowchart of a method 300 for integrity protection of Uu interface communication according to an embodiment of the present application.
  • the method 300 may be implemented by a terminal device or a network device. This method can be implemented by the receiving end of the communication or the sending end of the communication.
  • the method 300 can be implemented by a terminal device. At this time, the terminal device is used to calculate the MAC-I based on the first BEARER parameter value; or, when the Uu interface is used for uplink communication, The method 300 may be implemented by a network device. At this time, the network device may calculate XMAC-I based on the first BEARER parameter value.
  • the method 300 may be implemented by a terminal device. At this time, the terminal device is used to calculate XMAC-I based on the first BEARER parameter value; or, when the Uu interface is used for downlink communication, This method can be implemented by a network device. At this time, the network device can calculate the MAC-I based on the first BEARER parameter value.
  • the MAC-I or the XMAC-I is based on the first BEARER parameter value, and based on the PDCP COUNT value, the communication direction of the Uu interface communication, and the integrity protection key , At least one of the integrity protection key identifier and the content of the data packet is determined.
  • the bearer (BEARER) parameter value may be a parameter value used to obtain MAC-I or XMAC-I, and the bit length of the BEARER parameter value may be 5.
  • the BEARER parameter value may be a parameter value with a fixed length, and the fixed length may be preset on the terminal device, or may be configured by the network device for the terminal device.
  • the BEARER parameter value may also have other names, for example, logical channel identity (LCID) parameter value (for example, when the parameter value is obtained based on LCID), data radio bearer (DRB) ) Parameter value or signaling radio bearer (Signaling Radio Bearer, SRB) parameter value, or input parameter value, etc., which are not specifically limited in the embodiment of the present application.
  • LCID logical channel identity
  • DRB data radio bearer
  • SRB Signaling radio bearer
  • the BEARER parameter value can be combined with other parameters to obtain MAC-I or XMAC-I.
  • the other parameters may include the PDCP count (COUNT) value, the communication direction of the Uu interface, the integrity protection key, the integrity protection key identifier, and the content of the data packet (for example, Radio Resource Control (RRC) message) At least one of them.
  • the algorithm for calculating MAC-I or XMAC-I may be the NIA algorithm.
  • the PDCP COUNT value may include 32 bits.
  • the available bit length of the integrity protection key can be 128 bits, which can be derived from the original key (KgNB) key.
  • the communication direction of the Uu interface can be represented by 1 bit.
  • the uplink can be 0 and the downlink can be 1.
  • the communication device obtains the first BEARER parameter value based on at least one of the following:
  • the bit length of the LCID used for sidelink communication, the BEARER parameter value allocated for the Uu interface communication, and the preset BEARER parameter value is the bit length of the LCID used for sidelink communication, the BEARER parameter value allocated for the Uu interface communication, and the preset BEARER parameter value.
  • the communication device may obtain the first BEARER parameter value based on the bit length of the LCID used for sidelink communication.
  • the communication device may process the radio bearer identifier of the Uu interface communication based on the bit length of the LCID to obtain the first BEARER parameter value that is the same as the bit length of the LCID.
  • the processing of the identification of the radio bearer includes: adding at least one zero before the identification of the radio bearer, or adding at least one zero after the identification of the radio bearer.
  • a specific value can be added before or after the DRB identifier, so that the second BEARER parameter is equal to the bit length of the LCID of the sidelink communication.
  • the bit length of the LCID of the side link communication may be equal to the bit length of the BEARER parameter value of the MAC-I or XMAC-I in the side link communication.
  • the terminal device may obtain the first BEARER parameter value based on the bit length used to calculate the BEARER parameter value of the MAC-I or XMAC-I in the side link communication.
  • the bit length used to calculate the BEARER parameter of MAC-I or XMAC-I or the bit length of LCID used for side-link communication can be 6.
  • the communication device may obtain the first BEARER parameter value based on the BEARER parameter value allocated for Uu interface communication.
  • the BEARER parameter value allocated for Uu interface communication may be based on the terminal device as the granularity, or may be based on the radio bearer as the granularity.
  • the communication device may determine the BEARER parameter value corresponding to the radio bearer ID used in the Uu interface communication among the BEARER parameter values with the granularity of the radio bearer ID as the first BEARER parameter value.
  • the communication device will allocate a BEARER parameter value with a terminal device as the granularity for the Uu interface communication as the first BEARER parameter value.
  • the communication device may obtain the first BEARER parameter value based on the preset BEARER parameter value.
  • the communication device may determine the preset BEARER parameter value as the first BEARER parameter value.
  • the first BEARER parameter value can be divided into the BEARER parameter value of the AS layer and the NAS layer, and the BEARER parameter value of the AS layer and the NAS layer may be the same or different.
  • the method of obtaining the BEARER parameter value of the AS layer and the method of obtaining the BEARER parameter value of the NAS layer may be the same or different.
  • the communication device calculates MAC-I or XMAC-I used for the Uu interface communication.
  • the calculated MAC-I can be encapsulated into the PDCP header.
  • the receiver After the sender calculates the MAC-I, the calculated MAC-I can be encapsulated into the PDCP header.
  • the receiver After the receiver receives the message, it can calculate XMAC-I based on the received message, and combine XMAC-I with the PDCP header Compare the MAC-I in the MAC-I, if the two values are equal, it means that the integrity protection is successful, otherwise, it means that the message content has been changed.
  • the bit length of the first BEARER parameter value is equal to the bit length of the second BEARER parameter value
  • the second BEARER parameter value is used to calculate MAC-I in sidelink communication. Or XMAC-I.
  • the bit length used to calculate the BEARER parameter value of MAC-I or XMAC-I in sidelink communication is equal to the bit length used to calculate the BEARER parameter value of MAC-I or XMAC-I in Uu interface communication.
  • the bit length can avoid the problem of mismatch between MAC-I or XMAC-I calculations in the two communication modes, and only one set of MAC-I or XMAC-I calculation units can be needed, which reduces the complexity of terminal equipment implementation.
  • the above method 200 and method 300 can be used in combination.
  • the method used to calculate the BEARER parameters of MAC-I or XMAC-I in acquiring sidelink communication can adopt method 200.
  • the method 300 may be used to obtain the BEARER parameter value used to calculate the MAC-I or XMAC-I in the Uu interface communication.
  • FIG. 6 is a schematic block diagram of a device 400 for integrity protection of sidelink communication according to an embodiment of the present application.
  • the device 400 includes an acquisition unit 410 and a calculation unit 420.
  • the obtaining unit 410 is configured to obtain the first bearer BEARER parameter value based on at least one of the following: the logical channel identifier LCID corresponding to the data transmitted in the side link communication, and the interface used in the side link communication Incoming communication standard, the BEARER parameter value allocated for the side link communication, and the preset BEARER parameter value, wherein the bit length of the LCID corresponding to the transmitted data is greater than the bit length of the first BEARER parameter value;
  • the unit 420 is configured to calculate an integrity message authentication code MAC-I or a desired integrity message authentication code XMAC-I for the side link communication based on the first BEARER parameter value.
  • the bit length of the first BEARER parameter value is equal to the bit length of the second BEARER parameter value
  • the second BEARER parameter value is used to calculate MAC-I or XMAC in Uu interface communication. -I.
  • the obtaining unit 410 is further configured to:
  • the LCID corresponding to the transmitted data is processed to obtain the first BEARER parameter value.
  • the first BEARER parameter value is obtained in the following manner: intercepting a part of the bit value of the LCID corresponding to the transmitted data, and used to generate the first BEARER parameter value .
  • the first BEARER parameter value is obtained in the following manner: intercepting the lowest N bit value or the highest N bit value of the LCID corresponding to the transmitted data for Generate the first BEARER parameter value.
  • the N is equal to the number of bits of the first BEARER parameter value.
  • the obtaining unit 410 is further configured to:
  • the obtaining unit 410 is further configured to:
  • the BEARER parameter value allocated for the sidelink communication is allocated by the terminal device; or,
  • the BEARER parameter value allocated for the sidelink communication is allocated by the network device.
  • the obtaining unit 410 is further configured to:
  • the preset BEARER parameter value is determined as the first BEARER parameter value.
  • the MAC-I or the MAC-I is based on the first BEARER parameter value, and based on the PDCP COUNT value of the packet data convergence protocol, and the side link communication At least one of the direction, integrity protection key, integrity protection key identifier, and data packet content is calculated.
  • the device 400 can be used to implement the corresponding operations in the foregoing method 200, and for simplicity, details are not described herein again.
  • FIG. 7 is a schematic block diagram of a device 500 for integrity protection of Uu interface communication according to an embodiment of the present application.
  • the device 500 includes an acquisition unit 510 and a calculation unit 520.
  • the obtaining unit 510 is configured to obtain the first bearer parameter value based on at least one of the following: the bit length of the logical channel identifier LCID used for sidelink communication, the BEARER parameter value allocated for the Uu interface communication, The BEARER parameter value is preset; the calculation unit 520 is configured to calculate, based on the first BEARER parameter value, an integrity message authentication code MAC-I or an expected integrity message authentication code XMAC-I for the Uu interface communication.
  • the bit length of the first BEARER parameter value is equal to the bit length of the second BEARER parameter value
  • the second BEARER parameter value is used to calculate MAC-I in sidelink communication. Or XMAC-I.
  • the obtaining unit 510 is further configured to:
  • the radio bearer identifier of the Uu interface communication is processed to obtain the first BEARER parameter value that is the same as the bit length of the LCID.
  • the processing performed on the radio bearer identity includes: adding at least one zero before the radio bearer identity, or adding at least one zero after the radio bearer identity.
  • the obtaining unit 510 is further configured to:
  • the BEARER parameter value corresponding to the radio bearer identifier used for the Uu interface communication is determined as the first BEARER parameter value.
  • the obtaining unit 510 is further configured to:
  • the BEARER parameter value with the granularity of the terminal device allocated to the Uu interface communication is used as the first BEARER parameter value.
  • the obtaining unit 510 is further configured to:
  • the preset BEARER parameter value is determined as the first BEARER parameter value.
  • the MAC-I or the XMAC-I is based on the first BEARER parameter value, and based on the packet data convergence protocol count PDCP COUNT value, the communication direction of the Uu interface communication, At least one of the integrity protection key, the integrity protection key identifier, and the content of the data packet is calculated.
  • the device 500 may be used to implement the corresponding operations in the foregoing method 300, and for the sake of brevity, details are not repeated here.
  • FIG. 8 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application.
  • the communication device 600 shown in FIG. 8 includes a processor 610, and the processor 610 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the communication device 600 may further include a memory 620.
  • the processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
  • the memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.
  • the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 600 may specifically be a network device in an embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, details are not repeated here. .
  • the communication device 600 may specifically be a mobile terminal/terminal device of an embodiment of the application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the application.
  • I won’t repeat it here.
  • Fig. 9 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • the communication device 700 shown in FIG. 9 includes a processor 710, and the processor 710 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 700 may further include a memory 720.
  • the processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.
  • the memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.
  • the communication device 700 may further include an input interface 730.
  • the processor 710 can control the input interface 730 to communicate with other devices or communication devices, and specifically, can obtain information or data sent by other devices or communication devices.
  • the communication device 700 may further include an output interface 740.
  • the processor 710 may control the output interface 740 to communicate with other devices or communication devices, and specifically, may output information or data to other devices or communication devices.
  • the communication device may be applied to the network device in the embodiment of the present application, and the communication device may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the communication device may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the communication device can be applied to the mobile terminal/terminal device in the embodiment of this application, and the communication device can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of this application. For simplicity, I will not repeat them here.
  • the communication device mentioned in the embodiments of the present application may be a chip, and the chip may also be called a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • Synchlink DRAM SLDRAM
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment 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 connection 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 embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.
  • the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application ,
  • the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application ,
  • I will not repeat it here.
  • the embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For brevity, I won't repeat them here.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application.
  • the computer program runs on the computer, the computer executes each method in the embodiment of the present application. For the sake of brevity, the corresponding process will not be repeated here.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Power Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种用于侧行链路通信或Uu接口通信的完整性保护的方法（200）或设备，可以实现PDCP层的完整性保护，从而可以提高通信的安全性。该方法（200）包括：基于以下中的至少一种，获取第一承载BEARER参数值：所述侧行链路通信中传输的数据对应的逻辑信道标识LCID、所述侧行链路通信采用的接入通信制式、为所述侧行链路通信分配的BEARER参数值、预设BEARER参数值，其中，所述传输的数据对应的LCID的比特长度大于所述第一BEARER参数值的比特长度（210）；基于所述第一BEARER参数值，计算用于所述侧行链路通信的完整性消息认证码MAC-I或期望的完整性消息认证码XMAC-I（220）。

Description

用于完整性保护的方法或设备 技术领域
本申请实施例涉及通信技术领域，具体涉及一种用于完整性保护的方法或设备。
背景技术
在无线通信中，可以在分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层可以采用秘钥进行完整性保护。
如何具体实现PDCP层的完整性保护是一项亟待解决的问题。
发明内容
本申请实施例提供一种用于侧行链路通信或Uu接口通信的完整性保护的方法或设备，可以实现PDCP层的完整性保护，从而可以提高通信的安全性。
第一方面，提供了一种用于侧行链路通信的完整性保护的方法，包括：基于以下中的至少一种，获取第一承载BEARER参数值：所述侧行链路通信中传输的数据对应的逻辑信道标识LCID、所述侧行链路通信采用的接入通信制式、为所述侧行链路通信分配的BEARER参数值、预设BEARER参数值，其中，所述传输的数据对应的LCID的比特长度大于所述第一BEARER参数值的比特长度；基于所述第一BEARER参数值，计算用于所述侧行链路通信的完整性消息认证码MAC-I或期望的完整性消息认证码XMAC-I。
第二方面，提供了一种用于Uu接口通信的完整性保护的方法，包括：基于以下中的至少一种，获取第一承载BEARER参数值：用于侧行链路通信的逻辑信道标识LCID的比特长度、为所述Uu接口通信分配的BEARER参数值、预设BEARER参数值；基于所述第一BEARER参数值，计算用于所述Uu接口通信的完整性消息认证码MAC-I或期望的完整性消息认证码XMAC-I。
第三方面，提供了一种用于侧行链路通信的完整性保护的设备，用于执行上述第一方面中的方法。
具体地，该用于侧行链路通信的完整性保护的设备包括用于执行上述第一方面的功能模块。
第四方面，提供了一种用于Uu接口通信的完整性保护的设备，用于执行上述第一方面中的方法。
具体地，该用于Uu接口通信的完整性保护的设备包括用于执行上述第一方面的功能模块。
第五方面，提供了一种用于侧行链路通信的完整性保护的设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面中的方法。
第六方面，提供了一种用于Uu接口通信的完整性保护的设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面中的方法。
第七方面，提供了一种芯片，用于实现上述第一或第二方面中的方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行如上述第一或第二方面中的方法。
第八方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一或第二方面中的方法。
第九方面，提供了一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述第一或第二方面中的方法。
第十方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一或第二方面中的方法。
通过上述技术方案，基于以下中的至少一种，获取第一承载BEARER参数值：所述侧行链路通信中传输的数据对应的逻辑信道标识LCID、所述侧行链路通信采用的接入通信制式、为所述侧行链路通信分配的BEARER参数值、预设BEARER参数值，其中，所述传输的数据对应的LCID的比特长度大于所述第一BEARER参数值的比特长度；基于所述第一BEARER参数值，计算用于所述侧行链路通信的完整性消息认证码MAC-I或期望的完整性消息认证码XMAC-I，从而可以实现基于侧行链路通信的PDCP层的完整性保护，从而可以提高通信的安全性。
或者，基于以下中的至少一种，获取第一承载BEARER参数值：用于侧行链路通信的逻辑信道标识LCID的比特长度、为所述Uu接口通信分配的BEARER参数值、预设BEARER参数值；基于所述第一BEARER参数值，计算用于所述Uu接口通信的完整性消息认证码MAC-I或期望的完整性消息认证码XMAC-I，从而可以实现基于Uu接口通信的PDCP层的完整性保护，从而可以提高通信的安全性。
附图说明
图1是本申请实施例提供的一种通信***架构的示意性图。
图2是本申请实施例提供的一种用于侧行链路通信的完整性保护的方法的示意性图。
图3是本申请实施例提供的一种计算MAC-1或XMAC-I的示意性图。
图4是本申请实施例提供的一种获取BEARER参数值的方法的示意性图。
图5是本申请实施例提供的一种用于Uu接口通信的完整性保护的方法的示意性图。
图6是本申请实施例提供的一种用于侧行链路通信的完整性保护的设备的示意性图。
图7是本申请实施例提供的一种用于Uu接口通信的完整性保护的设备 的示意性图。
图8是本申请实施例提供的一种通信设备的示意性框图。
图9是本申请实施例提供的一种通信装置的示意性框图。
具体实施方式
本申请实施例的技术方案可以应用于各种通信***，例如：全球移动通讯(Global System of Mobile communication，GSM)***、码分多址(Code Division Multiple Access，CDMA)***、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)***、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)***、LTE频分双工(Frequency Division Duplex，FDD)***、LTE时分双工(Time Division Duplex，TDD)、通用移动通信***(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信***或5G***等。
本申请实施例提到的网络设备可以是与终端设备(或称为通信终端、终端)通信的设备。网络设备可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。可选地，该网络设备110可以是GSM***或CDMA***中的基站(Base Transceiver Station，BTS)，也可以是WCDMA***中的基站(NodeB，NB)，还可以是LTE***中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是新无线***中的基站(gNB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
本申请实施例提到的终端设备包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端设备的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的终端设备可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信***(Personal Communications System，PCS)终端；可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位***(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端设备可以指接入终端、用 户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
在本申请实施例中，如图1所示，终端设备120与网络设备110之间可以进行通信，具体地，可以通过Uu接口进行通信，和/或，终端设备120与终端设备120之间可以通过侧行链路(Sidelink，SL)进行通信。其中，终端设备120与终端设备120之间通过侧行链路进行通信，还可以称为利用PC5接口进行通信。本申请实施例中的侧行链路通信可以用于以下业务的通信：车联网(Vehicle to Anything，V2X)，网络控制交互服务(Network Controlled Interactive Services，NCIS)，公共安全(Public Safty)业务。
图2为用于侧行链路通信的完整性保护的方法200的示意性流程图。该方法200包括以下内容中的至少部分内容。该方法200可以由终端设备实现。
具体地，该方法200可以由侧行链路通信的发送端实现，此时，作为发送端的终端设备可以用于计算完整性消息认证码(Message Authentication Code–Integrity，MAC-I)；或者，该方法也可以由侧行链路通信的接收端实现，此时，作为接收端的终端设备可以用于计算(eXpected Message Authentication Code–Integrity，XMAC-I)。
在本申请实施例中，承载(BEARER)参数值可以为用于获取MAC-I或XMAC-I的参数值，BEARER参数值的比特长度可以为5。该BEARER参数值可以是具有固定长度的参数值，该固定长度可以是预设在终端设备上的，也可以是网络设备为终端设备配置的。该BEARER参数值还可以具有其他的名称，例如，逻辑信道标识(Logical Channel Identity，LCID)参数值(例如，在该参数值是基于LCID得到的情况下)，输入参数值等，本申请实施例对此不做具体限定。
该BEARER参数值可以结合其他的参数获取MAC-I或XMAC-I。
该其他的参数可以包括PDCP计数(COUNT)值、侧行链路通信的方向、完整性保护秘钥、完整性保护秘钥标识、数据包内容中的至少一种。本申请实施例中，计算MAC-I或XMAC-I的算法可以是网络完整算法(Network Integrity Algorithm，NIA)算法。
例如，如图3所示，可以在计算单元中，输入PDCP COUNT值、方向、完整性保护秘钥、BEARER参数值和完整性保护秘钥，得到MAC-I或XMAC-I。
其中，PDCP COUNT值可以包括32个比特位，32比特位中的0-15比特位为KD -sess ID，其中，KD -sess是终端设备的根密钥以每个会话为粒度生成的16-31比特位为Counter参数值，其中，Counter是计数器，每发送一次消 息计数器可以加一，K D-sess ID和Counter参数值可以承载于PDCP头中。对于用户面通信而言，如果不需要进行完整性保护，终端设备可以将K D-sess ID和Counter参数值设置为0。以及对于不要保护的信令消息而言，也可以在PDCP报文中，将K D-sess ID和Counter参数值设置为0。
完整性保护秘钥可以是临近服务(Proximity Service，ProSe)加密秘钥(ProSe Encryption Key，PEK)，其中，终端设备可以具有算法标识和ProSe组秘钥(ProSe Group Key，PGK)，PGK可以是终端设备所属的组的对应的秘钥，终端可以基于PGK推演得到ProSe业务秘钥(ProSe Traffic Key，PTK)，其中，PTK可以是专属于终端设备的，并且可以承载于用户数据报文的头中，终端设备可以基于PTK推演得到(ProSe Encryption Key，PEK)，PEK可以用于加密数据。完整性保护秘钥的比特长度可以为128比特。
侧行链路通信的方向可以通过1个比特来表示，侧行链路通信的方向可以包括从发起侧行链路通信的终端设备至被发起侧行链路通信的终端设备的方向(该方向对应的比特取值可以为1)，以及从被发起侧行链路通信的终端设备到发起侧行链路通信的终端设备的方向(该方向对应的比特取值可以为0)。
在210中，基于以下中的至少一种，终端设备获取第一BEARER参数值：
所述侧行链路通信中传输的数据对应的LCID、所述侧行链路通信采用的接入通信制式、为所述侧行链路通信分配的BEARER参数值、预设BEARER参数值，其中，所述传输的数据对应的LCID的比特长度大于所述第一BEARER参数值的比特长度。例如，LCID的比特长度为6，第一BEARER参数值的比特长度为5。
本申请实施例提到的LCID可以是由网络设备分配的，也可以是由终端设备分配的(例如，侧行链路通信中的终端设备所属的终端设备组的组头、侧行链路通信中的发送端、侧行链路通信中的接收端)，或者可以由侧行链路通信中的发送端和接收端协商得到的。可选地，在本申请实施例中，LCID可以是在LC建立时分配或协商得到的。
其中，本申请实施例多处以传输的数据对应的LCID的比特长度大于第一BEARER参数值为例进行描述，但是本申请实施例并不限于此，本申请实施例中的LCID的比特长度也可以小于第一BEARER参数值。
以上提到了获取第一BEARER参数值所需参考的因素，终端设备可以基于其中的一种来获取第一BEARER参数值，也可以基于其中的多种来获取BEARER参数值。以下将举例介绍获取BEARER参数值的实现方式。
在一种实现方式中，终端设备可以基于传输的数据对应的LCID，得到第一BEARER参数值。
在LCID的比特长度等于BEARER参数值期望的比特长度时，可以直接将LCID作为BEARER参数值，然而，在一些通信***(例如，5G通信***)中，LCID的比特比特长度可能不等于BEARER参数值期望的比特长度， 未解决该不匹配的问题，则终端设备可以对该LCID进行处理，以得到第一BEARER参数值。
对所述传输的数据对应的LCID进行的处理具体可以包括：截取所述传输的数据对应的LCID的一部分比特位数值，用于生成所述第一BEARER参数值。
具体地，由于LCID的比特长度大于期望的BEARER参数值的比特长度，如果需要基于LCID得到第一BEARER参数值，则可以截取(Truncate)该LCID的一部分比特位数值，作为第一BEARER参数值，其中，截取LCID的一部分比特位数值作为第一BEARER参数值是指将该一部分比特位数值用于生成第一BEARER参数值，其他比特位数值被丢弃。终端设备可以截取所述传输的数据对应的LCID最低N个比特位数值或最高N个比特位数值，用于生成所述第一BEARER参数值。其中，所述N可以等于所述第一BEARER参数值的比特长度。
例如，如图4所示，LCID的比特长度为6，第一BEARER参数值允许的比特长度为5，则可以从LCID中截取5个比特位数值作为第一BEARER参数值，例如可以将最高5个比特位数值(例如，如图4中的(a))或最低5个比特位数值(例如，如图4中的(b))作为第一BEARER参数值。
当然，终端设备可以截取该LCID的最低至少一个比特位以及最高至少一个比特位，将该最低最少一个比特位以及该最高至少一个比特位组合形成第一BEARER参数值。
应理解，对LCID的处理除了截取部分比特位数值之外，还可以具有其他的处理，例如，可以将该LCID对应的数值减去或除以一定的数值，以得到第一BEARER参数值。
或者，在本申请实施例中，终端设备可以从至少一个LCID与至少一个BEARER参数值的对应关系中，获取与所述传输的数据对应的LCID对应的BEARER参数值，以作为所述第一BEARER参数值。
具体地，LCID与BEARER参数值可以具有对应关系(例如，一一对应关系，一对多的关系，或多对一的关系)，其中，该对应关系可以是预设在终端设备上的，也可以是由网络设备或者由终端设备所属的终端设备组的组头配置的，也可以是发送端与接收端进行协商得到的。则终端设备也可以从该对应关系中，获取与传输的数据对应的LCID对应的BEARER参数值，作为第一BEARER参数值。
在另一种实现方式中，终端设备可以基于所述侧行链路通信采用的接入通信制式，获取第一BEARER参数值。
具体地，终端设备从至少一个接入通信制式与至少一个BEARER参数值的对应关系中，获取与所述侧行链路通信采用的接入通信制式对应的BEARER参数值，以作为所述第一BEARER参数值。
其中，接入通信制式与BEARER参数值可以具有对应关系(例如，一一对应关系，一对多的关系，或多对一的关系)，其中，该对应关系可以是 预设在终端设备上的，也可以是由网络设备或者由终端设备所属的终端设备组的组头配置的，也可以是发送端与接收端进行协商得到的。则终端设备也可以从该对应关系中，获取与采用的接入通信制式对应的BEARER参数值，作为第一BEARER参数值。
其中，本申请实施例中提到的接入通信制式可以为NR通信制式或E-UTRA通信制式。
在侧行链路通信采用的接入通信制式为NR通信制式时，第一BEARER参数值可以为一个值，在侧行链路通信采用的接入通信制式为E-UTRA通信制式时，第一BEARER参数值可以为另一值。
在另一种实现方式中，终端设备可以基于为侧行链路通信分配的BEARER参数值，获取第一BEARER参数值。
为所述侧行链路通信分配的BEARER参数值是由终端设备(例如，发起侧行链路通信的终端设备，侧行链路通信的终端设备所属的终端设备组的组头)分配的；或者，为所述侧行链路通信分配的BEARER参数值是由网络设备分配的。
其中，为侧行链路通信分配的BEARER参数值可以是per逻辑信道的，也即以逻辑信道为粒度分配BEARER参数值，具体可以在LCID时，分配BEARER参数值。或者，为侧行链路通信分配的BEARER参数值可以是per终端设备的，也即以终端设备为粒度分配BEARER参数值，其中，在计算MAC-I或XMAC-I时，可以是将为发送端终端分配的BEARER参数值，确定为第一BEARER参数值，或者，也可以是将为接收端终端分配的BEARER参数值，确定为第一BEARER参数值。
在另一种实现方式中，终端设备可以基于预设BEARER参数值，确定第一BEARER参数值。
具体地，终端设备可以将预设BEARER参数值，确定为第一BEARER参数值。
在220中，基于所述第一BEARER参数值，终端设备计算用于所述侧行链路通信的MAC-I或XMAC-I。
在发送端计算了MAC-I之后，可以将计算的MAC-I封装到PDCP包头中，接收端在接收到消息之后，可以基于接收到的消息计算XMAC-I，并将XMAC-I与PDCP包头中的MAC-I进行比较，如果两个值相等，则表示完整性保护成功，否则，则代表消息内容被更改。
可选地，在本申请实施例中，所述第一BEARER参数值的比特长度等于第二BEARER参数值的比特长度，所述第二BEARER参数值用于Uu接口通信中计算MAC-I或XMAC-I。在本申请实施例中，以上提供了多种实现方式来获取第一BEARER参数值，使得第一BEARER参数值的比特长度可以等于第二BEARER参数的比特长度。
其中，第一BEARER参数值的比特长度与第二BEARER参数值的比特长度可以均为5比特，其中，终端设备可以基于第二BEARER参数值的比 特长度确定第一BEARER参数值的比特长度，并基于确定的比特长度，对传输的数据对应的LCID进行处理，例如，截取一定数量的比特位数值作为第一BEARER参数值。
第二BEARER参数值区分为用于非接入层(Non-access stratum，NAS)和接入层(access stratum，AS)的BEARER参数值。
例如，对于NAS层而言，第二BEARER参数值可以为NAS连接标识符(NAS Connection Identifier)，对于3GPP而言，该值可以为0X01，对于非3GPP而言，该值可以为0XX00；
例如，对于AS层而言，对于控制面的完整性保护，第二BEARER参数值可以是SRB标识的值或者可以在SRB的标识(2个比特位)的前面或后面填充一定数量的比特位数值(例如0)，以生成第二BEARER参数值；对于用户面的完整性保护，第二BEARER参数值可以为DRB，或者也可以是对DRB的标识进行处理得到的，例如，DRB的标识的取值是[1-32]，因此可以直接将DRB的标识的取值减一，形成5比特的2进制值作为第二BEARER参数值。
因此，在本申请实施例中，用于侧行链路通信中计算MAC-I或XMAC-I的BEARER参数值的比特长度等于Uu接口通信中计算MAC-I或XMAC-I的BEARER参数值的比特长度，可以避免两种通信模式下进行MAC-I或XMAC-I计算不匹配的问题，可以只需要一套MAC-I或XMAC-I计算单元，降低终端设备实现的复杂度。
并且通过以上提到的方式获取第一BEARER参数值，使得第一BEARER参数值的比特长度可以等于第二BEARER参数值的比特长度，可以不需改动Uu接口通信计算MAC-I或XMAC-I的架构，以及可以实现充分利用已有机制和参数，对现有改动较小，例如，现有的BEARER参数值为5个比特位，通过对LCID进行处理得到5个比特位的BEARER参数值。
图5是根据本申请实施例的用于Uu接口通信的完整性保护的方法300的示意性流程图。该方法300可以由终端设备实现或网络设备实现。该方法可以由通信的接收端实现，也可以由通信的发送端实现。
例如，在Uu接口通信用于上行通信时，该方法300可以由终端设备实现，此时终端设备用于基于第一BEARER参数值，计算MAC-I；或者，在Uu接口用于上行通信时，该方法300可以由网络设备实现，此时，网络设备可以基于第一BEARER参数值，计算XMAC-I。
例如，在Uu接口通信用于下行通信时，该方法300可以由终端设备实现，此时终端设备用于基于第一BEARER参数值，计算XMAC-I；或者，在Uu接口用于下行通信时，该方法可以由网络设备实现，此时，网络设备可以基于第一BEARER参数值，计算MAC-I。
可选地，在本申请实施例中，所述MAC-I或所述XMAC-I是基于所述第一BEARER参数值，以及基于PDCP COUNT值、Uu接口通信的通信方向、完整性保护秘钥、完整性保护秘钥标识、数据包内容中的至少一种确定 的。
在本申请实施例中，承载(BEARER)参数值可以为用于获取MAC-I或XMAC-I的参数值，BEARER参数值的比特长度可以为5。该BEARER参数值可以是具有固定长度的参数值，该固定长度可以是预设在终端设备上的，也可以是网络设备为终端设备配置的。该BEARER参数值还可以具有其他的名称，例如，逻辑信道标识(Logical Channel Identity，LCID)参数值(例如，在该参数值是基于LCID得到的情况下)，数据无线承载(Data Radio Bearer，DRB)参数值或信令无线承载(Signaling Radio Bearer，SRB)参数值，或输入参数值等，本申请实施例对此不做具体限定。
该BEARER参数值可以结合其他的参数获取MAC-I或XMAC-I。
该其他的参数可以包括PDCP计数(COUNT)值、Uu接口通信的方向、完整性保护秘钥、完整性保护秘钥标识、数据包(例如，无线资源控制(Radio Resource Control，RRC)消息)内容中的至少一种。本申请实施例中，计算MAC-I或XMAC-I的算法可以是NIA算法。
例如，如图3所示，可以在计算单元中，输入PDCP COUNT值、方向、完整性保护秘钥、BEARER参数值和完整性保护秘钥，得到MAC-I或XMAC-I。
其中，PDCP COUNT值可以包括32个比特位。
完整性保护秘钥可的比特长度可以为128比特，可以是原始秘钥(KgNB)秘钥派生得到的。
Uu接口通信的方向可以通过1个比特来表示，例如，上行可以为0，下行可以为1。
在310中，基于以下中的至少一种，通信设备获取第一BEARER参数值：
用于侧行链路通信的LCID的比特长度、为所述Uu接口通信分配的BEARER参数值、预设BEARER参数值。
在一种实现方式中，通信设备可以基于用于侧行链路通信的LCID的比特长度，获取第一BEARER参数值。
具体地，通信设备可以基于所述LCID的比特长度，对所述Uu接口通信的无线承载标识进行处理，以得到与所述LCID的比特长度相同的所述第一BEARER参数值。
其中，对所述无线承载的标识进行的处理包括：在所述无线承载的标识之前补至少一个零，或在所述无线承载的标识之后补至少一个零。
例如，可以在DRB标识的前面或后面补特定数值，以使得第二BEARER参数等于侧行链路通信的LCID的比特长度。其中，侧行链路通信的LCID的比特长度可以等于侧行链路通信中用于计算MAC-I或XMAC-I的BEARER参数值的比特长度。
在本申请实施例中，终端设备可以基于侧行链路通信中用于计算MAC-I或XMAC-I的BEARER参数值的比特长度，获取第一BEARER参数值。
侧行链路通信中用于计算MAC-I或XMAC-I的BEARER参数的比特长度或用于侧行链路通信的LCID的比特长度可以为6。
在另一种实现方式中，通信设备可以基于为Uu接口通信分配的BEARER参数值，获取第一BEARER参数值。
其中，为Uu接口通信分配的BEARER参数值可以是以终端设备为粒度的，也可以是以无线承载为粒度的。
具体地，通信设备可以将为所述Uu接口通信分配的以无线承载ID为粒度的BEARER参数值中，与所述Uu接口通信采用的无线承载ID对应的BEARER参数值，确定为所述第一BEARER参数值。
或者，通信设备将为所述Uu接口通信分配的以终端设备为粒度的BEARER参数值，作为所述第一BEARER参数值。
在另一种实现方式中，通信设备可以基于预设BEARER参数值，获取第一BEARER参数值。
具体地，通信设备可以将所述预设BEARER参数值，确定为所述第一BEARER参数值。
方法300中，第一BEARER参数值可以区分为AS层和NAS层的BEARER参数值，AS层和NAS层的BEARER参数值可以相同，也可以不相同。获取AS层的BEARER参数值的方式与获取NAS层的BEARER参数值的方式可以相同，也可以不相同。
在320中，基于所述第一BEARER参数值，通信设备计算用于所述Uu接口通信的MAC-I或XMAC-I。
在发送端计算了MAC-I之后，可以将计算的MAC-I封装到PDCP包头中，接收端在接收到消息之后，可以基于接收到的消息计算XMAC-I，并将XMAC-I与PDCP包头中的MAC-I进行比较，如果两个值相等，则表示完整性保护成功，否则，则代表消息内容被更改。
可选地，在本申请实施例中，所述第一BEARER参数值的比特长度等于第二BEARER参数值的比特长度，所述第二BEARER参数值用于侧行链路通信中计算MAC-I或XMAC-I。
因此，在本申请实施例中，用于侧行链路通信中计算MAC-I或XMAC-I的BEARER参数值的比特长度等于Uu接口通信中计算MAC-I或XMAC-I的BEARER参数值的比特长度，可以避免两种通信模式下进行MAC-I或XMAC-I计算不匹配的问题，可以只需要一套MAC-I或XMAC-I计算单元，降低终端设备实现的复杂度。
应理解，以上方法200和方法300可以结合使用，例如，对于同一终端设备而言，在获取侧行链路通信中用于计算MAC-I或XMAC-I的BEARER参数的方式可以采用方法200，而获取Uu接口通信中用于计算MAC-I或XMAC-I的BEARER参数值的方式可以采用方法300。
图6是根据本申请实施例的一种用于侧行链路通信的完整性保护的设备400的示意性框图。该设备400包括获取单元410和计算单元420。
获取单元410，用于基于以下中的至少一种，获取第一承载BEARER参数值：所述侧行链路通信中传输的数据对应的逻辑信道标识LCID、所述侧行链路通信采用的接入通信制式、为所述侧行链路通信分配的BEARER参数值、预设BEARER参数值，其中，所述传输的数据对应的LCID的比特长度大于所述第一BEARER参数值的比特长度；计算单元420，用于基于所述第一BEARER参数值，计算用于所述侧行链路通信的完整性消息认证码MAC-I或期望的完整性消息认证码XMAC-I。
可选地，在本申请实施例中，所述第一BEARER参数值的比特长度等于第二BEARER参数值的比特长度，所述第二BEARER参数值用于Uu接口通信中计算MAC-I或XMAC-I。
可选地，在本申请实施例中，所述获取单元410进一步用于：
对所述传输的数据对应的LCID进行处理，得到所述第一BEARER参数值。
可选地，在本申请实施例中，所述第一BEARER参数值是通过以下方式获取的：截取所述传输的数据对应的LCID的一部分比特位数值，用于生成所述第一BEARER参数值。
可选地，在本申请实施例中，所述第一BEARER参数值是通过以下方式获取的：截取所述传输的数据对应的LCID最低N个比特位数值或最高N个比特位数值，用于生成所述第一BEARER参数值。
可选地，在本申请实施例中，所述N等于所述第一BEARER参数值的比特位的数量。
可选地，在本申请实施例中，所述获取单元410进一步用于：
从至少一个LCID与至少一个BEARER参数值的对应关系中，获取与所述传输的数据对应的LCID对应的BEARER参数值，以作为所述第一BEARER参数值。
可选地，在本申请实施例中，所述获取单元410进一步用于：
从至少一个接入通信制式与至少一个BEARER参数值的对应关系中，获取与所述侧行链路通信采用的接入通信制式对应的BEARER参数值，以作为所述第一BEARER参数值。
可选地，在本申请实施例中，为所述侧行链路通信分配的BEARER参数值是由终端设备分配的；或者，
为所述侧行链路通信分配的BEARER参数值是由网络设备分配的。
可选地，在本申请实施例中，所述获取单元410进一步用于：
将所述预设BEARER参数值，确定为所述第一BEARER参数值。
可选地，在本申请实施例中，所述MAC-I或所述MAC-I是基于所述第一BEARER参数值，以及基于分组数据汇聚协议计数PDCP COUNT值、所述侧行链路通信的方向、完整性保护秘钥、完整性保护秘钥标识、数据包内容中的至少一种计算的。
应理解，该设备400可以用于实现上述方法200中的相应操作，为了简 洁，在此不再赘述。
图7是根据本申请实施例的一种用于Uu接口通信的完整性保护的设备500的示意性框图。该设备500包括获取单元510和计算单元520。
获取单元510，用于基于以下中的至少一种，获取第一承载BEARER参数值：用于侧行链路通信的逻辑信道标识LCID的比特长度、为所述Uu接口通信分配的BEARER参数值、预设BEARER参数值；计算单元520，用于基于所述第一BEARER参数值，计算用于所述Uu接口通信的完整性消息认证码MAC-I或期望的完整性消息认证码XMAC-I。
可选地，在本申请实施例中，所述第一BEARER参数值的比特长度等于第二BEARER参数值的比特长度，所述第二BEARER参数值用于侧行链路通信中计算MAC-I或XMAC-I。
可选地，在本申请实施例中，所述获取单元510进一步用于：
基于所述LCID的比特长度，对所述Uu接口通信的无线承载标识进行处理，以得到与所述LCID的比特长度相同的所述第一BEARER参数值。
可选地，在本申请实施例中，对所述无线承载标识进行的处理包括：在所述无线承载标识之前补至少一个零，或在所述无线承载标识之后补至少一个零。
可选地，在本申请实施例中，所述获取单元510进一步用于：
将为所述Uu接口通信分配的以无线承载标识为粒度的BEARER参数值中，与所述Uu接口通信采用的无线承载标识对应的BEARER参数值，确定为所述第一BEARER参数值。
可选地，在本申请实施例中，所述获取单元510进一步用于：
将为所述Uu接口通信分配的以终端设备为粒度的BEARER参数值，作为所述第一BEARER参数值。
可选地，在本申请实施例中，所述获取单元510进一步用于：
将所述预设BEARER参数值，确定为所述第一BEARER参数值。
可选地，在本申请实施例中，所述MAC-I或所述XMAC-I是基于所述第一BEARER参数值，以及基于分组数据汇聚协议计数PDCP COUNT值、Uu接口通信的通信方向、完整性保护秘钥、完整性保护秘钥标识、数据包内容中的至少一种计算的。
应理解，该设备500可以用于实现上述方法300中的相应操作，为了简洁，在此不再赘述。
图8是本申请实施例提供的一种通信设备600示意性结构图。图8所示的通信设备600包括处理器610，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图8所示，通信设备600还可以包括存储器620。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以 集成在处理器610中。
可选地，如图8所示，通信设备600还可以包括收发器630，处理器610可以控制该收发器630与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备600具体可为本申请实施例的网络设备，并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备600具体可为本申请实施例的移动终端/终端设备，并且该通信设备600可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
图9是本申请实施例的通信装置的示意性结构图。图9所示的通信装置700包括处理器710，处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图9所示，通信装置700还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，该通信装置700还可以包括输入接口730。其中，处理器710可以控制该输入接口730与其他设备或通信装置进行通信，具体地，可以获取其他设备或通信装置发送的信息或数据。
可选地，该通信装置700还可以包括输出接口740。其中，处理器710可以控制该输出接口740与其他设备或通信装置进行通信，具体地，可以向其他设备或通信装置输出信息或数据。
可选地，该通信装置可应用于本申请实施例中的网络设备，并且该通信装置可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信装置可应用于本申请实施例中的移动终端/终端设备，并且该通信装置可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的通信装置可以为芯片，芯片还可以称为***级芯片，***芯片，芯片***或片上***芯片等。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field  Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的***和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/ 终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的移动终端/终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使 用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (43)

  1. 一种用于侧行链路通信的完整性保护的方法，其特征在于，包括：
    基于以下中的至少一种，获取第一承载BEARER参数值：
    所述侧行链路通信中传输的数据对应的逻辑信道标识LCID、所述侧行链路通信采用的接入通信制式、为所述侧行链路通信分配的BEARER参数值、预设BEARER参数值，其中，所述传输的数据对应的LCID的比特长度大于所述第一BEARER参数值的比特长度；
    基于所述第一BEARER参数值，计算用于所述侧行链路通信的完整性消息认证码MAC-I或期望的完整性消息认证码XMAC-I。
  2. 根据权利要求1所述的方法，其特征在于，所述第一BEARER参数值的比特长度等于第二BEARER参数值的比特长度，所述第二BEARER参数值用于Uu接口通信中计算MAC-I或XMAC-I。
  3. 根据权利要求1或2所述的方法，其特征在于，所述获取第一BEARER参数值，包括：
    对所述传输的数据对应的LCID进行处理，得到所述第一BEARER参数值。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第一BEARER参数值是通过以下方式获取的：获取所述传输的数据对应的LCID的一部分比特位数值，用于生成所述第一BEARER参数值。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一BEARER参数值是通过以下方式获取的：截取所述传输的数据对应的LCID最低N个比特位数值或最高N个比特位数值，用于生成所述第一BEARER参数值。
  6. 根据权利要求5所述的方法，其特征在于，所述N等于所述第一BEARER参数值的比特位的数量。
  7. 根据权利要求1或2所述的方法，其特征在于，所述获取第一BEARER参数值，包括：
    从至少一个LCID与至少一个BEARER参数值的对应关系中，获取与所述传输的数据对应的LCID对应的BEARER参数值，以作为所述第一BEARER参数值。
  8. 根据权利要求1或2所述的方法，其特征在于，所述获取第一BEARER参数值，包括：
    从至少一个接入通信制式与至少一个BEARER参数值的对应关系中，获取与所述侧行链路通信采用的接入通信制式对应的BEARER参数值，以作为所述第一BEARER参数值。
  9. 根据权利要求1或2所述的方法，其特征在于，为所述侧行链路通信分配的BEARER参数值是由终端设备分配的；或者，
    为所述侧行链路通信分配的BEARER参数值是由网络设备分配的。
  10. 根据权利要求1或2所述的方法，其特征在于，所述获取第一 BEARER参数值，包括：
    将所述预设BEARER参数值，确定为所述第一BEARER参数值。
  11. 根据权利要求1至10中任一项所述的方法，其特征在于，所述MAC-I或所述MAC-I是基于所述第一BEARER参数值，以及基于分组数据汇聚协议计数PDCP COUNT值、所述侧行链路通信的方向、完整性保护秘钥、完整性保护秘钥标识、数据包内容中的至少一种计算的。
  12. 一种用于Uu接口通信的完整性保护的方法，其特征在于，包括：
    基于以下中的至少一种，获取第一承载BEARER参数值：
    用于侧行链路通信的逻辑信道标识LCID的比特长度、为所述Uu接口通信分配的BEARER参数值、预设BEARER参数值；
    基于所述第一BEARER参数值，计算用于所述Uu接口通信的完整性消息认证码MAC-I或期望的完整性消息认证码XMAC-I。
  13. 根据权利要求12所述的方法，其特征在于，所述第一BEARER参数值的比特长度等于第二BEARER参数值的比特长度，所述第二BEARER参数值用于侧行链路通信中计算MAC-I或XMAC-I。
  14. 根据权利要求12或13所述的方法，其特征在于，所述获取第一BEARER参数值，包括：
    基于所述LCID的比特长度，对所述Uu接口通信的无线承载标识进行处理，以得到与所述LCID的比特长度相同的所述第一BEARER参数值。
  15. 根据权利要求14所述的方法，其特征在于，对所述无线承载标识进行的处理包括：在所述无线承载标识之前补至少一个零，或在所述无线承载标识之后补至少一个零。
  16. 根据权利要求12或13所述的方法，其特征在于，所述获取第一BEARER参数值，包括：
    将为所述Uu接口通信分配的以无线承载标识为粒度的BEARER参数值中，与所述Uu接口通信采用的无线承载标识对应的BEARER参数值，确定为所述第一BEARER参数值。
  17. 根据权利要求12或13所述的方法，其特征在于，所述获取第一BEARER参数值，包括：
    将为所述Uu接口通信分配的以终端设备为粒度的BEARER参数值，作为所述第一BEARER参数值。
  18. 根据权利要求12或13所述的方法，其特征在于，所述获取第一BEARER参数值，包括：
    将所述预设BEARER参数值，确定为所述第一BEARER参数值。
  19. 根据权利要求12至18中任一项所述的方法，其特征在于，所述MAC-I或所述XMAC-I是基于所述第一BEARER参数值，以及基于分组数据汇聚协议计数PDCP COUNT值、Uu接口通信的通信方向、完整性保护秘钥、完整性保护秘钥标识、数据包内容中的至少一种计算的。
  20. 一种用于侧行链路通信的完整性保护的设备，其特征在于，包括：
    获取单元，用于基于以下中的至少一种，获取第一承载BEARER参数值：
    所述侧行链路通信中传输的数据对应的逻辑信道标识LCID、所述侧行链路通信采用的接入通信制式、为所述侧行链路通信分配的BEARER参数值、预设BEARER参数值，其中，所述传输的数据对应的LCID的比特长度大于所述第一BEARER参数值的比特长度；
    计算单元，用于基于所述第一BEARER参数值，计算用于所述侧行链路通信的完整性消息认证码MAC-I或期望的完整性消息认证码XMAC-I。
  21. 根据权利要求20所述的设备，其特征在于，所述第一BEARER参数值的比特长度等于第二BEARER参数值的比特长度，所述第二BEARER参数值用于Uu接口通信中计算MAC-I或XMAC-I。
  22. 根据权利要求20或21所述的设备，其特征在于，所述获取单元进一步用于：
    对所述传输的数据对应的LCID进行处理，得到所述第一BEARER参数值。
  23. 根据权利要求20至22中任一项所述的设备，其特征在于，所述第一BEARER参数值是通过以下方式获取的：获取所述传输的数据对应的LCID的一部分比特位数值，用于生成所述第一BEARER参数值。
  24. 根据权利要求20至23中任一项所述的设备，其特征在于，所述第一BEARER参数值是通过以下方式获取的：截取所述传输的数据对应的LCID最低N个比特位数值或最高N个比特位数值，用于生成所述第一BEARER参数值。
  25. 根据权利要求24所述的设备，其特征在于，所述N等于所述第一BEARER参数值的比特位的数量。
  26. 根据权利要求20或21所述的设备，其特征在于，所述获取单元进一步用于：
    从至少一个LCID与至少一个BEARER参数值的对应关系中，获取与所述传输的数据对应的LCID对应的BEARER参数值，以作为所述第一BEARER参数值。
  27. 根据权利要求20或21所述的设备，其特征在于，所述获取单元进一步用于：
    从至少一个接入通信制式与至少一个BEARER参数值的对应关系中，获取与所述侧行链路通信采用的接入通信制式对应的BEARER参数值，以作为所述第一BEARER参数值。
  28. 根据权利要求20或21所述的设备，其特征在于，为所述侧行链路通信分配的BEARER参数值是由终端设备分配的；或者，
    为所述侧行链路通信分配的BEARER参数值是由网络设备分配的。
  29. 根据权利要求20或21所述的设备，其特征在于，所述获取单元进一步用于：
    将所述预设BEARER参数值，确定为所述第一BEARER参数值。
  30. 根据权利要求20至29中任一项所述的设备，其特征在于，所述MAC-I或所述MAC-I是基于所述第一BEARER参数值，以及基于分组数据汇聚协议计数PDCP COUNT值、所述侧行链路通信的方向、完整性保护秘钥、完整性保护秘钥标识、数据包内容中的至少一种计算的。
  31. 一种用于Uu接口通信的完整性保护的设备，其特征在于，包括：
    获取单元，用于基于以下中的至少一种，获取第一承载BEARER参数值：
    用于侧行链路通信的逻辑信道标识LCID的比特长度、为所述Uu接口通信分配的BEARER参数值、预设BEARER参数值；
    计算单元，用于基于所述第一BEARER参数值，计算用于所述Uu接口通信的完整性消息认证码MAC-I或期望的完整性消息认证码XMAC-I。
  32. 根据权利要求31所述的设备，其特征在于，所述第一BEARER参数值的比特长度等于第二BEARER参数值的比特长度，所述第二BEARER参数值用于侧行链路通信中计算MAC-I或XMAC-I。
  33. 根据权利要求31或32所述的设备，其特征在于，所述获取单元进一步用于：
    基于所述LCID的比特长度，对所述Uu接口通信的无线承载标识进行处理，以得到与所述LCID的比特长度相同的所述第一BEARER参数值。
  34. 根据权利要求33所述的设备，其特征在于，对所述无线承载标识进行的处理包括：在所述无线承载标识之前补至少一个零，或在所述无线承载标识之后补至少一个零。
  35. 根据权利要求31或32所述的设备，其特征在于，所述获取单元进一步用于：
    将为所述Uu接口通信分配的以无线承载标识为粒度的BEARER参数值中，与所述Uu接口通信采用的无线承载标识对应的BEARER参数值，确定为所述第一BEARER参数值。
  36. 根据权利要求31或32所述的设备，其特征在于，所述获取单元进一步用于：
    将为所述Uu接口通信分配的以终端设备为粒度的BEARER参数值，作为所述第一BEARER参数值。
  37. 根据权利要求31或32所述的设备，其特征在于，所述获取单元进一步用于：
    将所述预设BEARER参数值，确定为所述第一BEARER参数值。
  38. 根据权利要求31至37中任一项所述的设备，其特征在于，所述MAC-I或所述XMAC-I是基于所述第一BEARER参数值，以及基于分组数据汇聚协议计数PDCP COUNT值、Uu接口通信的通信方向、完整性保护秘钥、完整性保护秘钥标识、数据包内容中的至少一种计算的。
  39. 一种通信设备，其特征在于，包括：处理器和存储器，该存储器用 于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至19中任一项所述的方法。
  40. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至19中任一项所述的方法。
  41. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至19中任一项所述的方法。
  42. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至19中任一项所述的方法。
  43. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1至19中任一项所述的方法。
PCT/CN2019/084607 2019-04-26 2019-04-26 用于完整性保护的方法或设备 WO2020215323A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
EP19926622.2A EP3846519B1 (en) 2019-04-26 2019-04-26 Method or device for integrity protection
PCT/CN2019/084607 WO2020215323A1 (zh) 2019-04-26 2019-04-26 用于完整性保护的方法或设备
AU2019442498A AU2019442498A1 (en) 2019-04-26 2019-04-26 Method or device for integrity protection
CN201980057442.0A CN112655236A (zh) 2019-04-26 2019-04-26 用于完整性保护的方法或设备
CN202110438087.0A CN113194473B (zh) 2019-04-26 2019-04-26 用于完整性保护的方法或设备
US17/216,637 US11979747B2 (en) 2019-04-26 2021-03-29 Method or device for integrity protection

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/084607 WO2020215323A1 (zh) 2019-04-26 2019-04-26 用于完整性保护的方法或设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/216,637 Continuation US11979747B2 (en) 2019-04-26 2021-03-29 Method or device for integrity protection

Publications (1)

Publication Number Publication Date
WO2020215323A1 true WO2020215323A1 (zh) 2020-10-29

Family

ID=72940590

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/084607 WO2020215323A1 (zh) 2019-04-26 2019-04-26 用于完整性保护的方法或设备

Country Status (5)

Country Link
US (1) US11979747B2 (zh)
EP (1) EP3846519B1 (zh)
CN (2) CN113194473B (zh)
AU (1) AU2019442498A1 (zh)
WO (1) WO2020215323A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113194473B (zh) * 2019-04-26 2022-12-09 Oppo广东移动通信有限公司 用于完整性保护的方法或设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102404721A (zh) * 2010-09-10 2012-04-04 华为技术有限公司 Un接口的安全保护方法、装置和基站
CN102647332A (zh) * 2011-02-21 2012-08-22 电信科学技术研究院 一种传输数据的方法及装置
US20190069308A1 (en) * 2017-08-12 2019-02-28 Lg Electronics Inc. Method for handling for an uplink split operation in wireless communication system and a device therefor
CN109547396A (zh) * 2017-09-22 2019-03-29 维沃移动通信有限公司 完整性保护方法、终端和基站

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0004178D0 (en) * 2000-02-22 2000-04-12 Nokia Networks Oy Integrity check in a communication system
TW200803371A (en) * 2006-05-05 2008-01-01 Interdigital Tech Corp Ciphering control and synchronization in a wireless communication system
US8699711B2 (en) * 2007-07-18 2014-04-15 Interdigital Technology Corporation Method and apparatus to implement security in a long term evolution wireless device
WO2015163625A1 (en) * 2014-04-24 2015-10-29 Lg Electronics Inc. Method for establishing layer-2 entities for d2d communication system and device therefor
CN104125570B (zh) * 2014-07-02 2018-03-27 大唐移动通信设备有限公司 一种信令消息完整性检查的方法及装置
CN108141897A (zh) * 2016-01-30 2018-06-08 华为技术有限公司 一种终端设备、网络设备以及数据传输方法
EP3622741B1 (en) * 2017-06-14 2023-08-30 Samsung Electronics Co., Ltd. Method and user equipment for handling of integrity check failures of pdcp pdus
CN109246705B (zh) * 2017-06-15 2020-10-23 维沃移动通信有限公司 一种数据无线承载完整性保护配置方法、终端及网络设备
US11997738B2 (en) * 2017-06-16 2024-05-28 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods for the handling of data radio bearer integrity protection failure in NR
EP3466151B1 (en) * 2017-08-10 2022-09-14 Telefonaktiebolaget LM Ericsson (publ) Method and device for sidelink data duplication
EP3689061B1 (en) * 2017-09-28 2023-08-16 ZTE Corporation Methods for performing dual connectivity in sidelink communications, communication node and computer-readable medium
US10667185B2 (en) * 2018-03-28 2020-05-26 Telefonaktiebolaget Lm Ericsson (Publ) Method for avoiding unnecessary actions in resume procedure
KR102143023B1 (ko) * 2018-04-16 2020-08-10 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) 비활성 상태로부터의 rrc 재개를 위한 보안 핸들링
CN113194473B (zh) * 2019-04-26 2022-12-09 Oppo广东移动通信有限公司 用于完整性保护的方法或设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102404721A (zh) * 2010-09-10 2012-04-04 华为技术有限公司 Un接口的安全保护方法、装置和基站
CN102647332A (zh) * 2011-02-21 2012-08-22 电信科学技术研究院 一种传输数据的方法及装置
US20190069308A1 (en) * 2017-08-12 2019-02-28 Lg Electronics Inc. Method for handling for an uplink split operation in wireless communication system and a device therefor
CN109547396A (zh) * 2017-09-22 2019-03-29 维沃移动通信有限公司 完整性保护方法、终端和基站

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3846519A4 *

Also Published As

Publication number Publication date
EP3846519A4 (en) 2021-09-01
US20210243606A1 (en) 2021-08-05
CN113194473B (zh) 2022-12-09
EP3846519A1 (en) 2021-07-07
CN112655236A (zh) 2021-04-13
CN113194473A (zh) 2021-07-30
EP3846519B1 (en) 2022-07-06
AU2019442498A1 (en) 2021-05-06
US11979747B2 (en) 2024-05-07

Similar Documents

Publication Publication Date Title
WO2020034229A1 (zh) 一种信息传输方法及装置、通信设备
EP3920491B1 (en) Service processing method, device and computer readable storage medium
US11877326B2 (en) Wireless communication method and communication device
WO2019153272A1 (zh) 基于业务质量进行数据传输的方法和设备
WO2021046778A1 (zh) 无线通信的方法、终端设备和网络设备
WO2021087910A1 (zh) 用于连接网络的方法和设备
WO2020061776A9 (zh) 一种反馈资源的复用方法、终端设备及网络设备
WO2020024249A1 (zh) 一种数据传输方法、终端设备、网络设备及存储介质
WO2019237315A1 (zh) 一种控制安全功能的方法及装置、网络设备、终端设备
US11979747B2 (en) Method or device for integrity protection
WO2020252790A1 (zh) 一种信息传输方法及装置、网络设备、用户设备
CN112703802B (zh) 处理上行覆盖弱化的方法及装置、终端、网络设备
WO2020154929A1 (zh) 一种秘钥信息处理方法和接入网络节点、终端设备
WO2020155157A1 (zh) 切换过程中安全信息的处理方法及装置、网络设备、终端
WO2020061873A1 (zh) 一种资源指示方法、设备及存储介质
US11381963B2 (en) Wireless communication method and device
WO2021138801A1 (zh) 一种业务安全传输方法及装置、终端设备、网络设备
CN112243576B (zh) 一种信息传输方法及装置、通信设备
WO2020258292A1 (zh) 无线通信的方法、终端设备、接入网设备和核心网设备
WO2020087546A1 (zh) 一种网络信息传输方法、获取方法、网络设备及终端设备
WO2020164019A1 (zh) 一种承载配置方法及装置、网络设备
WO2020087475A1 (zh) 一种数据加扰方法及装置、通信设备
WO2021142636A1 (zh) 上行传输的方法和终端设备
WO2021248336A1 (zh) 一种释放配置的方法及装置、终端设备、网络设备
CN114450989A (zh) 设备会话密钥标识字段的填充方法及相关产品

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19926622

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019926622

Country of ref document: EP

Effective date: 20210329

ENP Entry into the national phase

Ref document number: 2019442498

Country of ref document: AU

Date of ref document: 20190426

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE