Data processing method, communication apparatus and computer-readable storage medium

Abstract

A data processing method, a communication apparatus and a computer-readable storage medium. The data processing method comprises: acquiring data of at least one service, the at least one service comprising a first service; using a packet data convergence protocol (PDCP) entity corresponding to the first service to process data of the first service, so as to obtain a first service data unit, different services corresponding to different PDCP entities; on the basis of the first service data unit, generating a first protocol data unit, the first protocol data unit comprising first indication information, and the first indication information being at least used for indicating the first service; and submitting the first protocol data unit to a radio link layer control (RLC) entity, so as to send the first protocol data unit. The solution provided in the present application can improve the security of data plane data while meeting the data transmission requirements of data planes.

Description

Data processing methods, communication devices, and computer-readable storage media

[0001] This application claims priority to Chinese Patent Application No. 202411463838.4, filed on October 18, 2024, entitled "Data Processing Method, Communication Apparatus, Computer-Readable Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a data processing method, a communication device, and a computer-readable storage medium. Background Technology

[0003] In the prior art, the user plane protocol stack is used to implement the transmission of user data, and the control plane protocol stack is used to implement the transmission of control signaling.

[0004] With the development of mobile communication technology, in order to better maintain and manage the network and support certain service characteristics, mobile communication systems need to transmit service data other than user data and control signaling. This includes service data such as Optimizing Networks (SON) data obtained by network devices from terminal devices, Minimization of Drive Test (MDT) data, and data related to locating service interactions. Current user plane and control plane protocol stacks cannot meet the transmission requirements of these service data. Therefore, it is urgent to introduce a new protocol stack to satisfy these transmission needs. Summary of the Invention

[0005] One of the technical objectives of this application is to provide a data processing method, communication device, and computer-readable storage medium that can meet the data transmission requirements of the data plane while ensuring the security of the data plane.

[0006] In a first aspect, embodiments of this application provide a data processing method, the method comprising: acquiring data of at least one service, the at least one service including a first service; processing the data of the first service using a Packet Data Convergence Protocol (PDCP) entity corresponding to the first service to obtain a first service data unit, wherein the PDCP entities corresponding to different services are different; generating a first protocol data unit based on the first service data unit, wherein the first protocol data unit includes first indication information, the first indication information being used at least to indicate the first service; and submitting the first protocol data unit to a Radio Link Layer Control (RLC) entity to transmit the first protocol data unit.

[0007] Optionally, the first indication information is also used to indicate the radio bearer of the first protocol data unit.

[0008] Optionally, the at least one service further includes a second service, wherein the radio bearer of the first protocol data unit and the radio bearer of the second protocol data unit are the same or different; wherein the second protocol data unit is generated based on the second service data unit, and the second service data unit is obtained by processing the data of the second service using the PDCP entity corresponding to the second service.

[0009] Optionally, processing the data of the first service using the PDCP entity corresponding to the first service includes: processing the data of the first service using the first key parameter and the second key parameter to obtain the first service data unit; or, processing the data of the first service using the third key parameter and the fourth key parameter to obtain the first service data unit; wherein the first key parameter is used for integrity protection of the data of the at least one service, the second key parameter is used for encryption of the data of the at least one service, the third key parameter is dedicated to integrity protection of the data of the first service, and the fourth key parameter is dedicated to encryption of the data of the first service.

[0010] Secondly, embodiments of this application provide a communication method, the method comprising: obtaining at least one protocol data unit from a Radio Link Layer Control (RLC) entity, the at least one protocol data unit including a first protocol data unit; parsing the first protocol data unit to obtain first indication information and a first service data unit, wherein the first indication information is used to indicate at least a first service; and processing the first service data unit using a Packet Data Convergence Protocol (PDCP) entity corresponding to the first service according to the first indication information to obtain data of the first service.

[0011] Optionally, the first indication information is also used to indicate the radio bearer of the first protocol data unit.

[0012] Optionally, the at least one protocol data unit further includes a second protocol data unit, and the method further includes: parsing the second protocol data unit to obtain second indication information and a second service data unit, wherein the second indication information is used to indicate at least a second service; processing the second service data unit using a second PDCP entity corresponding to the second service according to the second indication information to obtain data of the second service; wherein the radio bearer of the second protocol data unit is the same as or different from the radio bearer of the first protocol data unit.

[0013] Optionally, the first service data unit is processed using the PDCP entity corresponding to the first service, including: processing the data of the first service data unit using the first key parameter and the second key parameter to obtain the data of the first service; or, processing the data of the first service data unit using the third key parameter and the fourth key parameter to obtain the data of the first service; wherein, the first key parameter is used for integrity protection of the data of at least one service, the second key parameter is used for decryption of the data of at least one service, the third key parameter is dedicated to integrity protection of the data of the first service, and the fourth key parameter is dedicated to decryption of the data of the first service.

[0014] Thirdly, embodiments of this application provide a communication apparatus, the apparatus comprising: an acquisition module, configured to acquire data of at least one service, the at least one service including a first service; a PDCP module, configured to process the data of the first service using a Packet Data Convergence Protocol (PDCP) entity corresponding to the first service to obtain a first service data unit, wherein the PDCP entities corresponding to different services are different; an indication module, configured to generate a first protocol data unit based on the first service data unit, wherein the first protocol data unit includes first indication information, the first indication information being used at least to indicate the first service; and a delivery module, configured to deliver the first protocol data unit to a Radio Link Layer Control (RLC) entity to transmit the first protocol data unit.

[0015] Fourthly, embodiments of this application provide a communication apparatus, the apparatus comprising: an acquisition module, configured to acquire at least one protocol data unit from a Radio Link Layer Control (RLC) entity, the at least one protocol data unit including a first protocol data unit; an indication module, configured to parse the first protocol data unit to obtain first indication information and a first service data unit, wherein the first indication information is used to indicate at least a first service; and a PDCP module, configured to process the first service data unit according to the first indication information using a first Packet Data Convergence Protocol (PDCP) entity corresponding to the first service to obtain data for the first service.

[0016] Fifthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when run by a processor, causes the method provided in either aspect to be executed.

[0017] In a sixth aspect, embodiments of this application provide a communication device including a memory and a processor, wherein the memory stores a computer program executable on the processor, and the processor executes the steps of the method provided in the first aspect when running the computer program.

[0018] In a seventh aspect, embodiments of this application provide a communication device including a memory and a processor, wherein the memory stores a computer program executable on the processor, and the processor executes the steps of the method provided in the second aspect when running the computer program.

[0019] Eighthly, embodiments of this application provide a chip (or communication device) storing a computer program, which, when executed by the chip, causes the methods provided in any of the above aspects to be executed.

[0020] Ninthly, embodiments of this application provide a chip module on which a computer program is stored, such that when the computer program is executed by the chip module, the methods provided in any of the above aspects are executed.

[0021] In a tenth aspect, embodiments of this application provide a computer program product, which includes a computer program that, when run on a computer, causes the computer to execute the methods provided in any of the above aspects.

[0022] Eleventhly, embodiments of this application provide a communication system, the communication system including at least one of the following: means for performing the method provided in the first aspect, and means for performing the method provided in the second aspect.

[0023] Compared with the prior art, the technical solution of the embodiments of this application has the following beneficial effects:

[0024] In the scheme of this application embodiment, different services correspond to different PDCP entities. For the data of the first service obtained from the upper layer, the PDCP entity corresponding to the first service processes the data of the first service to obtain a first service data unit; then, a first protocol data unit is generated based on the first service data unit, wherein the first protocol data unit includes first indication information, which is at least used to indicate the first service; the first protocol data unit is further submitted to the RLC entity to send the first protocol data unit. In the above scheme, different services correspond to different PDCP entities, different PDCP entities are used to process the data of different services, and a new protocol layer is introduced between the PDCP layer and the RLC layer to indicate the service to which the service data belongs, so as to realize the diversion of service data. Therefore, by adopting the above scheme, the security of service data can be improved while realizing the diversion of service data. Attached Figure Description

[0025] Figure 1 is a schematic diagram of a user plane protocol stack.

[0026] Figure 2 is a schematic diagram of a control plane protocol stack;

[0027] Figure 3 is a schematic diagram of a data plane protocol stack;

[0028] Figure 4 is a schematic diagram of another data plane protocol stack;

[0029] Figure 5 is a schematic diagram of a data plane protocol stack in an embodiment of this application;

[0030] Figure 6 is a flowchart illustrating a data processing method according to an embodiment of this application;

[0031] Figure 7 is a flowchart illustrating another data processing method in an embodiment of this application;

[0032] Figure 8 is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0033] Figure 9 is a schematic diagram of another communication device in an embodiment of this application;

[0034] Figure 10 is a schematic diagram of the hardware structure of a communication device according to an embodiment of this application;

[0035] Figure 11 is a schematic diagram of a first protocol data unit in an embodiment of this application. Detailed Implementation

[0036] It should be understood that the "and / or" appearing in the embodiments of this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document indicates that the related objects before and after it have an "or" relationship.

[0037] In this application's embodiments, "at least one" refers to one or more. In this application's embodiments, "multiple" refers to two or more.

[0038] The descriptions of "first," "second," etc., appearing in the embodiments of this application are for illustrative purposes and to distinguish the objects being described. They have no order and do not indicate any special limitation on the number of devices in the embodiments of this application, nor do they constitute any limitation on the embodiments of this application.

[0039] The communication systems applicable to the embodiments of this application include, but are not limited to, Long Term Evolution (LTE) systems, 5th-generation (5G) systems (such as New Radio (NR) systems), and future evolution systems or multiple converged communication systems. The 5G system can be a non-standalone (NSA) 5G system or a standalone (SA) 5G system. The solutions of the embodiments of this application can also be applied to future new communication systems, such as 6th-generation (6G) communication systems, 7th-generation (7G) systems, or other future communication systems; the embodiments of this application are not limited in this regard.

[0040] In this application, "terminal equipment" can refer to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device, etc. For example, terminal equipment can be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal in a future 5G network, or terminal equipment in a future evolved Public Land Mobile Network (PLMN), etc. This application does not limit the scope of the term. In some embodiments of this application, the terminal equipment can be an electronic device with wireless data transmission capabilities. In other embodiments of this application, the terminal equipment can also be a device with transceiver capabilities, such as a chip system. The chip system can include chips and other discrete components.

[0041] The network device in this application embodiment can refer to a device that provides wireless communication functions for terminal devices. The network device can be called an access network device, such as a radio access network (RAN) device or an access network element. The network device can support at least one wireless communication technology, such as LTE or NR. For example, the network device can be a base station (BS) (also called base station equipment), a base transceiver station (BTS), a Node B, an evolved Node B (eNB), or a device that provides base station functions in a 5G network, such as a next-generation node B (gNB) and a further evolved Node B (ng-eNB). The gNB communicates with the terminal device using NR technology, while the ng-eNB communicates with the terminal device using Evolved Universal Terrestrial Radio Access (E-UTRA) technology. Both the gNB and ng-eNB can connect to the 5G core network. In wireless local area networks (WLANs), the device that provides base station functionality is called an access point (AP). The network device in this application embodiment also includes devices that provide wireless communication functionality in future new communication systems. In some embodiments, the network device may also be a means of providing wireless communication functionality for terminal devices, such as a chip system. For example, a chip system may include a chip, and may also include other discrete devices.

[0042] In some embodiments, network equipment may refer to a centralized unit (CU) or a distributed unit (DU) of a base station.

[0043] Referring to Figure 1, which is a schematic diagram of a user plane protocol stack in the prior art, the user plane protocol stack, from top to bottom, consists of: Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer. The PHY layer belongs to Layer 1 (L1), while the SDAP, PDCP, RLC, and MAC layers belong to Layer 2, used to implement user plane functions. The terms "upper" and "lower" are relative; the layer closer to the physical layer is the lower layer, and the layer further away is the upper layer.

[0044] Referring to Figure 2, which is a schematic diagram of a control plane protocol stack in the prior art, the control plane protocol stack, from top to bottom, consists of: Non-Access Stratum (NAS) layer, Radio Resource Control (RRC) layer, PDCP layer, RLC layer, MAC layer, and PHY layer. The PHY layer belongs to Layer 1, the PDCP, RLC, and MAC layers belong to Layer 2 (L2), and the NAS and RRC layers belong to Layer 3 (L3). The NAS, RRC, PDCP, RLC, and MAC layers are used to implement the functions of the control plane.

[0045] As described in the background section, in order to better maintain and manage the network and support certain service characteristics, mobile communication systems also need to transmit some data other than user data and control signaling. In the scheme of this application embodiment, the above-mentioned "data other than user data and control signaling" is referred to as "service data" or "service data" or "data plane data".

[0046] It should be noted that, unlike user data, the "business data" in this application embodiment terminates at the internal nodes of the communication network and is visible to the network, while user data terminates outside the communication network and is transparent to the network.

[0047] When the amount of service data is relatively small, a control plane transmission scheme can be used. That is, the service data is processed based on the control plane protocol stack and transmitted using the control plane's Signaling Radio Bearer (SRB).

[0048] However, with the further development of communication technologies, such as the introduction of AI models, communication systems may need to transmit large amounts of service data. If control plane transmission is still used, it will affect existing control signaling transmission, such as causing congestion and increasing control signaling latency. Furthermore, transmitting this type of data as control signaling will make the design of the control plane protocol stack more complex.

[0049] Therefore, a new plane, called the "data plane," is introduced to implement the transmission of business data. When designing the data plane protocol stack, it is necessary to distinguish between data from different services to achieve data splitting within the communication device. The data plane protocol stack can have the following schemes:

[0050] Option 1: The data plane protocol stack is built upon the user plane protocol stack by introducing a Data Forwarding Control Protocol (DFCP) layer. Refer to Figure 3, which is a schematic diagram of a data plane protocol stack. As shown in Figure 3, the data plane protocols include: DFCP layer, PDCP layer, RLC layer, MAC layer, and PHY layer. The DFCP layer is the layer above the PDCP layer.

[0051] Option 2: The data plane protocol stack introduces a Data Plane Adaptation Protocol (DPAP) layer on top of the user plane protocol stack. The DPAP layer is used for data offloading on the data plane. Refer to Figure 4, which illustrates another data plane protocol stack. As shown in Figure 4, the data plane protocol includes: DPAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer. The DPAP layer is the layer above the PDCP layer. In specific implementations, if the communication device acts as the data sender, the DPAP layer determines the service to which the service data obtained from the upper layer belongs, and then further submits the service data to the PDCP layer for processing. If the communication device acts as the data receiver, the DPAP layer determines the service to which the service data obtained from the PDCP layer belongs, and then submits the service data to the upper layer.

[0052] Option 3: The data plane protocol stack is based on the user plane protocol stack, with modifications made to the SDAP layer. Specifically, the existing Data Radio Bearer (DRB) is used to carry data plane data. Through DRB configuration, service data is terminated within the communication network. In one approach, the existing SDAP layer's field definitions are modified to carry service information. Specifically, in the SDAP packet header, the QoS flow identifier (QFI) is replaced with a General Service Flow Identifier (SFI). The SFI indicates the Service-flow Type, thus identifying the service to which the data belongs. The base station can identify the service to which the data belongs based on the SFI and forward the received service data to the corresponding network element.

[0053] In Schemes 1 and 2, the business to which the service data belongs is distinguished at a layer above the PDCP layer (such as the DFCP layer or DPAP layer). In Scheme 3, the business to which the service data belongs is distinguished at the SDAP layer. It should be noted that Schemes 1, 2, and 3 do not involve any changes to the PDCP layer. Specifically, the PDCP layer does not distinguish the business to which the service data belongs; data packets from different services share the same PDCP entity. Since the PDCP layer is responsible for security processing, such as data integrity protection, encryption, and decryption, schemes where data from different services share the same PDCP entity are prone to security issues.

[0054] In view of this, embodiments of this application provide a data processing method. In the scheme of this application embodiment, different services correspond to different PDCP entities. For data of a first service obtained from the upper layer, the PDCP entity corresponding to the first service is used to process the data of the first service to obtain a first service data unit; then, a first protocol data unit is generated based on the first service data unit, wherein the first protocol data unit includes first indication information, which is at least used to indicate the first service; further, the first protocol data unit is submitted to the RLC entity to send the first protocol data unit. In the above scheme, different services correspond to different PDCP entities, different PDCP entities are used to process data of different services, and a new protocol layer is introduced between the PDCP layer and the RLC layer to indicate the service to which the service data belongs, so as to realize the diversion of service data. Therefore, by adopting the above scheme, the security of service data can be improved while realizing the diversion of service data.

[0055] The specific embodiments of this application will be described in detail below with reference to the accompanying drawings. The actions performed by the communication device in the following embodiments can be performed by a device, a component within the device (e.g., a processor, a chip), a chip, etc., and this application does not impose any limitations. For ease of description, the embodiments provided in this application are illustrated using a communication device as the executing entity. It should be noted that the device in the embodiments of this application can be a terminal device or a network device.

[0056] Referring to Figure 5, which is a schematic diagram of a data plane protocol stack according to an embodiment of this application, the data plane protocol stack provided in this embodiment includes: a PDCP layer, a first protocol layer, and an RLC layer. The first protocol layer is located between the PDCP layer and the RLC layer. More specifically, the layer above the first protocol layer is the PDCP layer, and the layer below the first protocol layer is the RLC layer.

[0057] Furthermore, in the protocol stack shown in Figure 5, each type of service corresponds to a single PDCP entity, and different services correspond to different PDCP entities. As shown in Figure 5, taking N services as an example, the first service corresponds to PDCP entity 1, which processes the data of the first service; the second service corresponds to PDCP entity 2, which processes the data of the second service; and so on, with the Nth service corresponding to PDCP entity N, which processes the data of the Nth service. Here, N is a positive integer greater than 1.

[0058] It should be noted that the services in the embodiments of this application can be SON services, MDT services, positioning services, sensing services, AI services, etc., or new data plane services introduced later.

[0059] In the embodiments of this application, data plane data is processed based on the protocol stack shown in FIG5 to meet the data transmission requirements of the data plane. More details about the protocol stack shown in FIG5 can be found in the following descriptions of FIG6 and FIG7. The processing handled by the first protocol layer can be found in the following descriptions of S63 and S72.

[0060] Referring to Figure 6, which is a flowchart illustrating a data processing method according to an embodiment of this application, the method shown in Figure 6 may include steps S61 to S64. In this application, the 'S' in the step numbers represents a step. In a specific implementation, when the communication device acts as the data sender, the communication device can execute the scheme shown in Figure 6.

[0061] S61, acquire data for at least one service, wherein the at least one service includes a first service;

[0062] S62, the data of the first service is processed by the PDCP entity corresponding to the first service to obtain the first service data unit, wherein the PDCP entities corresponding to different services are different.

[0063] S63, Generate a first protocol data unit based on the first service data unit, wherein the first protocol data unit includes first indication information, and the first indication information is used to indicate the first service at least;

[0064] S64, submit the first protocol data unit to the RLC entity to send the first protocol data unit.

[0065] In S61, within the communication device, the upper layer of the PDCP layer transmits data of at least one service to the PDCP layer. The upper layer of the PDCP layer can be an application layer, or it can be a protocol layer defined by existing or future communication protocols; this embodiment does not impose any limitations on this. As mentioned above, different services correspond to different PDCP entities at the PDCP layer. A PDCP entity refers to a device or module used to implement the functions of the PDCP layer. The following description primarily uses the first service and the second service as examples. That is, the data of at least one service may include data from the first service and data from the second service.

[0066] In S62, the PDCP entity corresponding to the first service is used to process the data of the first service to obtain the first service data unit (SDU). Further, after obtaining the first SDU, the first SDU is transmitted to the first protocol layer to execute S63.

[0067] In S63, a first Protocol Data Unit (PDU) is generated based on the first SDU. Specifically, the entity corresponding to the first protocol layer generates the first PDU based on the first SDU. The entity corresponding to the first protocol layer can refer to a device or module used to implement the functions of the first protocol layer. The first PDU includes first indication information, which can be used to indicate a first service. More specifically, the first indication information can indicate that the first PDU is a PDU for the first service. In other words, the first indication information can indicate that the first PDU carries data for the first service.

[0068] In specific implementation, the first indication information can be determined based on the PDCP entity from which the first SDU comes, and the first PDU can be generated based on the first indication information and the first SDU.

[0069] In one example, first indication information can be added to the first SDU to obtain the first PDU. Referring to Figure 11, which is a schematic diagram of a first protocol data unit in an embodiment of this application, as shown in Figure 11, the first PDU may include a header and the first SDU, wherein the header carries the first indication information.

[0070] In one possible implementation, the first indication information may include the service identifier of the first service.

[0071] In another possible implementation, the first indication information can be used to indicate the radio bearer of the first PDU. For example, the first indication information may include an identifier of the radio bearer of the first PDU. It should be noted that in this embodiment, "radio bearer" refers to a data plane radio bearer. In one embodiment, the first PDU can also be mapped to its radio bearer based on the first indication information. In specific implementations, the identifiers of the radio bearers of PDUs for different services may be the same or different.

[0072] In S64, the first protocol layer submits the first PDU to the RLC layer. Specifically, the entity corresponding to the first protocol layer submits the first PDU to the RLC entity to send the first PDU. Specifically, the communication device can send the first PDU to the receiving RLC entity. It should be noted that submitting the first PDU to the RLC entity can refer to mapping the first PDU to the RLC channel.

[0073] In one embodiment, if the "data of at least one service" in S61 further includes data of a second service, then S62 further includes: processing the data of the second service using the PDCP entity corresponding to the second service to obtain a second SDU. The PDCP entity corresponding to the first service is different from the PDCP entity corresponding to the second service. Further, the second SDU is submitted to the first protocol layer, which generates a second PDU based on the second SDU. That is, in S63, a second PDU is generated based on the second SDU. The second PDU includes second indication information, which can be used to indicate the second service. Further, in S64, the second PDU is submitted to the RLC entity. In addition, the second indication information can also be used to indicate the radio bearer of the second PDU, thereby mapping the second PDU to its radio bearer. The identifiers of the radio bearer of the second PDU and the radio bearer of the first PDU may be the same or different.

[0074] For example, data plane radio bearers can be uniformly numbered, meaning all service radio bearers share the same numbering space. Each service can correspond to at least one radio bearer. If all service radio bearers share the same numbering space, then different radio bearer identifiers are assigned to different services. In other words, the identifiers of radio bearers for different services must be different. For example, the first service corresponds to 4 radio bearers, and the identifiers of these 4 radio bearers are 0, 1, 2, and 3, respectively; the second service corresponds to 4 radio bearers, and the identifiers of these 4 radio bearers are 4, 5, 6, and 7, respectively.

[0075] For example, data plane radio bearers can be numbered independently. That is, each service has its own independent numbering space. Specifically, if all service radio bearers share the same numbering space, then different services can be assigned the same radio bearer identifier. In other words, the identifiers of radio bearers for different services can be the same. For example, the first service corresponds to 4 radio bearers, and the identifiers of these 4 radio bearers are 0, 1, 2, and 3, respectively. The second service corresponds to 4 radio bearers, and the identifiers of these 4 radio bearers are also 0, 1, 2, and 3, respectively.

[0076] As can be seen from the above, when the communication device acts as the sender of service data, the first protocol layer is responsible for receiving SDUs from the PDCP layer and generating PDUs based on the SDUs. The generated PDUs carry indication information, which is used to indicate the service to which the service data belongs and / or the radio bearer of the service data. In addition, the first protocol layer is also used to map the PDUs to the RLC channel and / or to the radio bearer indicated by the indication information.

[0077] In practical implementation, the PDCP layer can perform integrity protection, encryption, and / or decryption of business data.

[0078] In one embodiment of this application, the communication device can generate a first key parameter and a second key parameter. The first key parameter can be used to protect the integrity of data for various services, and the second key parameter can be used to encrypt and / or process the data for various services. That is, the first key parameter can be shared by multiple services, and the second key parameter can be shared by multiple services. For example, the first key parameter and the second key parameter can be keys derived from a KgNB key.

[0079] Specifically, in S62, the communication device can process the data of the first service using the first key parameter and the second key parameter to obtain the first SDU. Furthermore, the communication device can process the data of the second service using the first key parameter and the second key parameter to obtain the second SDU. More specifically, the communication device can perform integrity protection on the data of the first service using the first key parameter, and also perform integrity protection on the data of the second service using the first key parameter. Additionally, the communication device can perform encryption processing on the data of the first service using the second key parameter, and also perform encryption processing on the data of the second service using the second key parameter.

[0080] In practice, when various services share the same key parameters (such as the first key parameter and the second key parameter), the identifiers of the radio bearers corresponding to different services are different.

[0081] It should be noted that the key parameters in this embodiment can be used together with other parameters to generate a keystream block. The sender can obtain a ciphertext block based on the keystream block and the plaintext block. After receiving the ciphertext block, the receiver can obtain the plaintext block based on the keystream block and the ciphertext block. For example, the sender or receiver can generate a keystream block based on the key parameters, the sequence number of the data packet, the radio bearer identifier, the transmission direction (uplink or downlink), and the length of the data packet.

[0082] In another embodiment of this application, the communication device can generate at least one set of key parameter groups, wherein different key parameter groups correspond to different services. The at least one set of key parameter groups can be derived from a KgNB key.

[0083] For example, at least one set of key parameters includes a first key parameter set, which includes a third key parameter and a fourth key parameter. The first key parameter set is used to process the data of the first service. The third key parameter is used for integrity protection of the data of the first service, and the fourth key parameter is used for encryption and / or decryption of the data of the first service. In S62, the communication device can use the third key parameter and the fourth key parameter to process the data of the first service to obtain a first SDU.

[0084] Furthermore, at least one key parameter group may also include a second key parameter group, which may include a fifth key parameter and a sixth key parameter. The second key parameter group is used to process the data of the second service. Specifically, the fifth key parameter is used for integrity protection of the second service data, and the sixth key parameter is used for encryption and / or decryption of the second service data. In S62, the communication device can use the fifth and sixth key parameters to process the data of the first service to obtain the second SDU.

[0085] In practice, when different services use their respective key parameter sets, the identifiers of the radio bearers for different services can be the same or different.

[0086] Referring to Figure 7, which is a flowchart illustrating another data processing method in an embodiment of this application, the method shown in Figure 7 may include steps S71 to S73. In a specific implementation, when the communication device acts as the data receiver, the communication device can execute the scheme shown in Figure 7.

[0087] S71, at least one protocol data unit is obtained from the RLC entity, the at least one protocol data unit including a first protocol data unit. In S71, at least one PDU is submitted from the RLC layer to the first protocol layer to execute S72.

[0088] S72, parse the first protocol data unit to obtain first indication information and a first service data unit, wherein the first indication information is used to indicate at least a first service. Specifically, the header of the first PDU can be parsed to obtain the first indication information. The first indication information may include the identifier of the service corresponding to the first PDU and / or the identifier of the radio bearer.

[0089] S73, according to the first instruction information, the first service data unit is processed by the PDCP entity corresponding to the first service to obtain the data of the first service. Specifically, the first SDU can be transmitted to the PDCP entity corresponding to the first service, and the PDCP entity corresponding to the first service can process the first SDU to obtain the data of the first service.

[0090] If at least one PDU also includes a second PDU, in S72, parsing the second PDU can yield second indication information and a second SDU. In S73, the second SDU can be transmitted to the PDCP entity corresponding to the second service according to the second indication information. The PDCP entity corresponding to the second service can process the second SDU to obtain the data of the second service.

[0091] In S73, the processing of SDU by the PDCP entity can be the inverse operation performed by the PDCP entity in S62.

[0092] In one embodiment, the PDCP entity processes the data of the first SDU using a first key parameter and a second key parameter to obtain the data of the first service. Specifically, the PDCP entity uses the first key parameter to perform integrity protection on the first SDU and uses the second key parameter to decrypt the first SDU to obtain the data of the first service.

[0093] In another embodiment, the PDCP entity processes the data of the first SDU using a first key parameter set to obtain the data of the first service. Specifically, the PDCP entity uses a third key parameter to protect the integrity of the first SDU and uses a fourth key parameter to decrypt the first SDU to obtain the data of the first service.

[0094] For details regarding the first, second, third, and fourth key parameters, please refer to the relevant descriptions above; they will not be repeated here.

[0095] As can be seen from the above, when the communication device is the receiver of service data, the first protocol layer is responsible for receiving PDU from the RLC layer and generating SDU and indication information based on the PDU. The indication information is used to indicate the service to which the SDU belongs, so that the SDU can be transmitted to the PDCP entity corresponding to the service to which the SDU belongs.

[0096] It is understandable that, in specific implementation, the above method can be implemented using a software program that runs in the processor integrated inside the chip or chip module; or, the method can be implemented using hardware or a combination of hardware and software, such as using a dedicated chip or chip module, or using a dedicated chip or chip module combined with a software program.

[0097] Referring to Figure 8, which is a schematic diagram of a communication device according to an embodiment of this application, the communication device shown in Figure 8 can be deployed on a terminal device or a network device. The device shown in Figure 8 may include:

[0098] Acquisition module 81 is used to acquire data of at least one service, wherein the at least one service includes a first service;

[0099] PDCP module 82 is used to process the data of the first service using the Packet Data Convergence Protocol (PDCP) entity corresponding to the first service to obtain the first service data unit, wherein the PDCP entities corresponding to different services are different.

[0100] Indication module 83 is used to generate a first protocol data unit based on the first service data unit, wherein the first protocol data unit includes first indication information, and the first indication information is used to indicate the first service at least;

[0101] The delivery module 84 is used to deliver the first protocol data unit to the Radio Link Layer Control (RLC) entity in order to send the first protocol data unit.

[0102] In specific implementations, the communication device shown in Figure 8 may correspond to a chip with communication function in the device; or it may correspond to a chip or chip module with communication function in the device; or it may correspond to the device itself.

[0103] Referring to Figure 9, which is a schematic diagram of another communication device in an embodiment of this application, the communication device shown in Figure 9 can be deployed on the aforementioned terminal equipment or network equipment. The device shown in Figure 9 may include:

[0104] Acquisition module 91 is used to acquire at least one protocol data unit from the Radio Link Layer Control (RLC) entity, wherein the at least one protocol data unit includes a first protocol data unit;

[0105] Indication module 92 is used to parse the first protocol data unit to obtain first indication information and first service data unit, wherein the first indication information is used to indicate at least the first service;

[0106] PDCP module 93 is used to process the first service data unit using the first packet data aggregation protocol PDCP entity corresponding to the first service according to the first indication information, so as to obtain the data of the first service.

[0107] In specific implementations, the communication device shown in Figure 9 may correspond to a chip with communication function in the device; or to a chip or chip module that includes communication function in the device; or to the device itself.

[0108] For more information on the working principle, working method, and beneficial effects of the communication device in the embodiments of this application, please refer to the relevant description of the method above, which will not be repeated here.

[0109] This application also provides a computer-readable storage medium storing a computer program thereon. When the computer program is run by a processor, the above-described method is executed. The storage medium may include ROM, RAM, a magnetic disk, or an optical disk, etc. The storage medium may also include non-volatile memory or non-transitory memory, etc.

[0110] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the above-described method.

[0111] This application also provides a communication device, including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor runs the computer program, it performs the steps of the data processing method described above. This communication device can be either a network device or a terminal device as described above.

[0112] Referring to Figure 10, which is a schematic diagram of the hardware structure of a communication device according to an embodiment of this application, the communication device shown in Figure 10 can be either a network device or a terminal device as described above. The communication device shown in Figure 10 includes a memory 101, a processor 102, and a transceiver 103. The processor 102 is coupled to the memory 101 and the transceiver 103. The memory 101 can be located inside or outside the communication device. The memory 101, processor 102, and transceiver 103 can be connected via a communication bus. The transceiver 103 is used to communicate with other devices. The memory 101 stores a computer program that can run on the processor 102. When the processor 102 runs the computer program, it executes the steps in the methods provided in the above embodiments, and / or, when the processor 102 runs the computer program, the transceiver 103 executes the steps in the methods provided in the above embodiments.

[0113] It should be understood that in the embodiments of this application, the processor can be a central processing unit (CPU), or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0114] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0115] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means.

[0116] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply 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 this application.

[0117] In the several embodiments provided in this application, it should be understood that the disclosed methods, apparatuses, and systems can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for example, the division of units is merely a logical functional division, and other division methods may exist in actual implementation; for example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0118] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0119] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can be physically included separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or in a combination of hardware and software functional units. For example, for various devices or products applied to or integrated into a chip, each module / unit can be implemented using hardware such as circuits, or at least some modules / units can be implemented using software programs running on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware such as circuits; for various devices or products applied to or integrated into a chip module, each module / unit can be implemented using hardware such as circuits, and different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware such as circuits. The components can be implemented using software programs that run on the processor integrated within the chip module. The remaining (if any) modules / units can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into the terminal, each of its components / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or in different components within the terminal. Alternatively, at least some modules / units can be implemented using software programs that run on the processor integrated within the terminal, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits.

[0120] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute some steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0121] While this application discloses the above information, it is not limited thereto. Any person skilled in the art can make various modifications and alterations without departing from the spirit and scope of this application; therefore, the scope of protection of this application shall be determined by the scope defined in the claims.

Claims

1. A data processing method, characterized by, The method includes: Acquire data for at least one service, wherein the at least one service includes a first service; The data of the first service is processed by the Packet Data Convergence Protocol (PDCP) entity corresponding to the first service to obtain the first service data unit. The PDCP entities corresponding to different services are different. A first protocol data unit is generated based on the first service data unit, wherein the first protocol data unit includes first indication information, and the first indication information is used to indicate at least the first service; The first protocol data unit is delivered to the Radio Link Layer Control (RLC) entity to transmit the first protocol data unit.

2. The data processing method according to claim 1, characterized in that, The first indication information is also used to indicate the radio bearer of the first protocol data unit.

3. The data processing method according to claim 2, characterized in that, The at least one service further includes a second service, wherein the radio bearer of the first protocol data unit and the radio bearer of the second protocol data unit are the same or different; The second protocol data unit is generated based on the second service data unit, which is obtained by processing the data of the second service using the PDCP entity corresponding to the second service.

4. The data processing method of claim 1, wherein, Processing the data of the first service using the PDCP entity corresponding to the first service includes: The data of the first service is processed using the first key parameter and the second key parameter to obtain the first service data unit; Alternatively, the data of the first service can be processed using the third key parameter and the fourth key parameter to obtain the first service data unit; Wherein, the first key parameter is used for the integrity protection of the data of the at least one service, the second key parameter is used for the encryption of the data of the at least one service, the third key parameter is dedicated to the integrity protection of the data of the first service, and the fourth key parameter is dedicated to the encryption of the data of the first service.

5. A data processing method, characterized by, The method includes: At least one protocol data unit is obtained from the Radio Link Layer Control (RLC) entity, the at least one protocol data unit including a first protocol data unit; Parse the first protocol data unit to obtain first indication information and first service data unit, wherein the first indication information is used to indicate at least the first service; Based on the first instruction information, the first service data unit is processed using the Packet Data Convergence Protocol (PDCP) entity corresponding to the first service to obtain the data of the first service.

6. The data processing method according to claim 5, characterized in that, The first indication information is also used to indicate the radio bearer of the first protocol data unit.

7. The data processing method according to claim 6, characterized in that, The at least one protocol data unit further includes a second protocol data unit, and the method further includes: Parse the second protocol data unit to obtain second indication information and second service data unit, wherein the second indication information is used to indicate at least the second service; According to the second instruction information, the PDCP entity corresponding to the second service is used to process the second service data unit to obtain the data of the second service; The radio bearer of the second protocol data unit may be the same as or different from the radio bearer of the first protocol data unit.

8. The data processing method according to claim 6, characterized in that, The first service data unit is processed using the PDCP entity corresponding to the first service, including: The data of the first service data unit is processed using the first key parameter and the second key parameter to obtain the data of the first service; Alternatively, the data of the first service data unit can be processed using the third key parameter and the fourth key parameter to obtain the data of the first service; Wherein, the first key parameter is used for the integrity protection of the data of the at least one service, the second key parameter is used for the decryption of the data of the at least one service, the third key parameter is dedicated to the integrity protection of the data of the first service, and the fourth key parameter is dedicated to the decryption of the data of the first service.

9. A communications device, characterized by The device includes: The acquisition module is used to acquire data from at least one service, wherein the at least one service includes a first service; The PDCP module is used to process the data of the first service using the Packet Data Convergence Protocol (PDCP) entity corresponding to the first service to obtain the first service data unit. The PDCP entities corresponding to different services are different. An indication module is configured to generate a first protocol data unit based on the first service data unit, wherein the first protocol data unit includes first indication information, and the first indication information is used to indicate at least the first service; The delivery module is used to deliver the first protocol data unit to the Radio Link Layer Control (RLC) entity in order to send the first protocol data unit.

10. A communications device, characterized by The device includes: An acquisition module is configured to acquire at least one protocol data unit from a Radio Link Layer Control (RLC) entity, wherein the at least one protocol data unit includes a first protocol data unit. An indication module is used to parse the first protocol data unit to obtain first indication information and a first service data unit, wherein the first indication information is used to indicate at least a first service; The PDCP module is used to process the first service data unit according to the first indication information using the first packet data aggregation protocol PDCP entity corresponding to the first service, so as to obtain the data of the first service.

11. A computer readable storage medium having stored thereon a computer program, characterized in that, When the computer program is run by the processor, the data processing method according to any one of claims 1 to 4 or the data processing method according to any one of claims 5 to 8 is executed.

12. A computer program product comprising a computer program, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 8.

13. A communication device comprising a memory and a processor, said memory having stored thereon a computer program executable on said processor, characterized in that, When the processor runs the computer program, it performs the steps of the data processing method according to any one of claims 1 to 4 or the data processing method according to any one of claims 5 to 8.

Images