A method and device for wireless communication
By indicating the data generation time in the first domain of the PDCP PDU, the key mismatch problem caused by separation of PDCP and RLC entities is solved, reducing the complexity of the relay node and improving the reliability of data transmission.
Patent Information
- Application Number
- CN202110451961.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-04-26
- Publication Date
- 2024-11-22
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
In wireless communication, especially during the reconstruction process of PDCP entity, the separation of PDCP and RLC entities leads to a mismatch of keys, resulting in a decryption error on the receiver side, which increases the packet error rate of the application layer, and the relay node faces the reconstruction during reconstruction. Problems of distributed control and control delay.
By indicating in the first domain of the PDCP PDU whether the data is generated before or after the PDCP entity reconstruction, the receiver can correctly identify and process the data, and avoid the problem of key mismatch.
It effectively reduces the complexity of the relay node, avoids confusion caused by the receiving end receiving old key encrypted data, and ensures the correctness and reliability of data transmission, especially in multi-hop relay and multi-user scenarios.
Smart Images

Figure CN115334692B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to a transmission method and device in a wireless communication system, and more particularly to a method and device for reducing service interruption, improving service continuity, enhancing reliability, and ensuring security in wireless communications. Background Art
[0002] In the future, the application scenarios of wireless communication systems will become more and more diversified, and different application scenarios will put forward different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #72 plenary meeting decided to study the new radio (NR) (or Fifth Generation, 5G) technology, and the NR WI (Work Item) was passed at the 3GPP RAN #75 plenary meeting, and the standardization work on NR began.
[0003] In communication, both LTE (Long Term Evolution) and 5G NR involve accurate reception of reliable information, optimized energy efficiency, determination of information validity, flexible resource allocation, scalable system structure, efficient non-access layer information processing, low service interruption and drop rate, and support for low power consumption. This is of great significance to the normal communication between base stations and user equipment, the reasonable scheduling of resources, and the balancing of system loads. It can be said to be the cornerstone of high throughput, meeting the communication needs of various services, improving spectrum utilization, and improving service quality. It is indispensable for eMBB (ehanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication) and eMTC (enhanced Machine Type Communication). At the same time, in IIoT (Industrial Internet of Things), V2X (Vehicular to X), device to device, unlicensed spectrum communication, user communication quality monitoring, network planning optimization, NTN (Non Territerial Network), TN (Territial Network), dual connectivity systems, wireless resource management and multi-antenna codebook selection, signaling design, neighbor management, business management, and beamforming, there are extensive demands. Information transmission methods are divided into broadcast and unicast. Both transmission methods are essential for 5G systems because they are very helpful in meeting the above requirements.
[0004] As the scenarios and complexity of the system continue to increase, higher requirements are placed on reducing interruption rates, reducing latency, enhancing reliability, enhancing system stability, business flexibility, and power saving. At the same time, compatibility between different versions of different systems also needs to be considered during system design. Summary of the invention
[0005] In various communication scenarios, the establishment and reconstruction of entities and links are involved, especially when the key is updated. In order to ensure security, the relevant entities need to be rebuilt. When encryption is performed by the PDCP entity, the relevant PDCP entity will be rebuilt. In scenarios involving relays, involving communications between UEs, especially communications between relay nodes and UEs, distributed control problems and control delay problems will arise. For example, reconstruction involves PDCP and may also involve the RLC entity associated with it, but in the relay scenario, the PDCP entity and the RLC entity may not be in the same node, resulting in the two entities being out of sync if they are to be rebuilt. When the PDCP entity uses the old key for encryption before reconstruction and the new key for encryption after reconstruction, due to the separation of the PDCP and RLC entities, the receiving end may still receive data encrypted with the old key even after the PDCP entity is rebuilt, resulting in decryption errors, causing communication failures or increasing the packet error rate at the application layer. The present application indicates whether the data is generated before or after the relevant PDCP entity is rebuilt through the first field in the PDCP PDU, which can help the receiving end correctly distinguish the data and use the correct key for decryption.
[0006] With regard to the above-mentioned problems, this application provides a solution.
[0007] It should be noted that, in the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.
[0008] The present application discloses a method in a first node used for wireless communication, comprising:
[0009] receiving a first message; and in response to receiving the first message, reestablishing a first PDCP entity;
[0010] Sending a first PDCP PDU, where the first PDCP PDU is generated by the first PDCP entity;
[0011] The first PDCP PDU includes a first field and data, the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
[0012] As an embodiment, the problems to be solved by the present application include: in scenarios where communication between UEs is required, such as when communicating through side-link technology, especially when using a layer 2 relay architecture, there will be a situation where the PDCP entity is separated from (partial or full) the associated RLC entity. This can easily cause confusion on the receiving end during the PDCP entity reconstruction process, because the relay node caches an uncertain amount of data. These data are generated before the PDCP entity is reconstructed, but are sent after the PDCP entity is reconstructed. In conventional scenarios, the PDCP entity and the associated RLC entity are on the same node, and they can be reconstructed at the same time. During the reconstruction, the data of the RLC entity will be cleared. The present application avoids possible conflicts through the indication of the first field of the PDCP PDU.
[0013] As an embodiment, the benefits of the above method include: The method proposed in the present application can solve the above problems. Even if the receiving end receives data encrypted with an old key, it can still correctly identify it, and can either use the old key to decrypt it or discard it, and no confusion will be caused in any case. On the other hand, the present application is conducive to reducing the complexity of the relay node, and even if there are many hops and many relays involved, it will not cause any problems.
[0014] As an embodiment, the characteristics of the present application include: PDU is Protocol Data Unit.
[0015] Specifically, according to one aspect of the present invention, the behavior of sending a first PDCP PDU includes: sending a first RLC PDU, the first RLC PDU includes the first PDCP PDU, the first RLC PDU includes a first RLC SN; wherein the first message is not used to reset the first RLC SN.
[0016] Specifically, according to one aspect of the present invention, a second message is sent;
[0017] The behavior of reconstructing the first PDCP entity includes: reconstructing a first RLC entity, the first RLC entity is associated with the first PDCP entity; and the second message indicates that the first RLC entity is reconstructed.
[0018] Specifically, according to one aspect of the present invention, a first report is sent, wherein the first report indicates that the second PDCP SDU has not been received by indicating a second sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; and the behavior of sending the first report is executed after the behavior rebuilds the first PDCP entity.
[0019] Specifically, according to one aspect of the present invention, a first report is sent, wherein the first report indicates that the second PDCP SDU has not been received by indicating a fourth sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; the second sequence number is different from the fourth sequence number, and the second sequence number is used to determine the fourth sequence number; the behavior of sending the first report is executed after the behavior rebuilds the first PDCP entity.
[0020] Specifically, according to one aspect of the present invention, a second report is received, and the second report is used to indicate a first COUNT value; the first COUNT value is the first lost COUNT value; the first COUNT value is used to determine a first initial value; the initial value of at least one state variable of the first PDCP entity is set to the first initial value after the behavior reconstructs the first PDCP entity, and the first initial value is not 0.
[0021] Specifically, according to one aspect of the present invention, the first message is used to indicate a first key, and the first PDCP entity uses the first key to encrypt the data included in the first PDCP PDU.
[0022] Specifically, according to one aspect of the present application, the first node is a user equipment.
[0023] Specifically, according to one aspect of the present application, the first node is an Internet of Things terminal.
[0024] Specifically, according to one aspect of the present application, the first node is a relay.
[0025] Specifically, according to one aspect of the present application, the first node is a vehicle-mounted terminal.
[0026] Specifically, according to one aspect of the present application, the first node is an aircraft.
[0027] The present application discloses a method in a second node used for wireless communication, comprising:
[0028] Sending a first message; the first message is used to trigger the reestablishment of a first PDCP entity;
[0029] receiving a first PDCP PDU, where the first PDCP PDU is generated by the first PDCP entity;
[0030] The first PDCP PDU includes a first field and data, the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
[0031] Specifically, according to one aspect of the present invention, the behavior of receiving a first PDCP PDU includes:
[0032] A first RLC PDU is received, wherein the first RLC PDU includes the first PDCP PDU, and the first RLC PDU includes a first RLC SN; wherein the first message is not used to reset the first RLC SN.
[0033] Specifically, according to one aspect of the present invention, a first report is received, wherein the first report indicates that the second PDCP SDU has not been received by indicating a second sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; and the behavior of sending the first report is executed after the behavior rebuilds the first PDCP entity.
[0034] Specifically, according to one aspect of the present invention, a first report is received, wherein the first report indicates that the second PDCP SDU has not been received by indicating a fourth sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; the second sequence number is different from the fourth sequence number, and the second sequence number is used to determine the fourth sequence number; the behavior of sending the first report is executed after the behavior rebuilds the first PDCP entity.
[0035] Specifically, according to one aspect of the present invention, a second report is sent, and the second report is used to indicate a first COUNT value; the first COUNT value is the first lost COUNT value; the first COUNT value is used to determine a first initial value; the initial value of at least one state variable of the first PDCP entity is set to the first initial value after the behavior reconstructs the first PDCP entity, and the first initial value is not 0.
[0036] Specifically, according to one aspect of the present invention, the first message is used to indicate a first key, and the first PDCP entity uses the first key to encrypt the data included in the first PDCP PDU.
[0037] Specifically, according to one aspect of the present application, the first node is a user equipment.
[0038] Specifically, according to one aspect of the present application, the first node is an Internet of Things terminal.
[0039] Specifically, according to one aspect of the present application, the first node is a relay.
[0040] Specifically, according to one aspect of the present application, the first node is a vehicle-mounted terminal.
[0041] Specifically, according to one aspect of the present application, the first node is an aircraft.
[0042] The present application discloses a first node used for wireless communication, comprising:
[0043] A first receiver receives a first message; and in response to receiving the first message, reestablishes a first PDCP entity;
[0044] A first transmitter is configured to send a first PDCP PDU, where the first PDCP PDU is generated by the first PDCP entity;
[0045] The first PDCP PDU includes a first field and data, the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
[0046] The present application discloses a second node used for wireless communication, comprising:
[0047] A second transmitter sends a first message, wherein the first message is used to trigger the reestablishment of a first PDCP entity;
[0048] A second receiver, receiving a first PDCP PDU, where the first PDCP PDU is generated by the first PDCP entity;
[0049] The first PDCP PDU includes a first field and data, the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
[0050] As an embodiment, compared with the traditional solution, the present application has the following advantages: in the method proposed in the present application, the reconstruction of the PDCP entity due to key update and other reasons requires the use of new keys before and after the reconstruction; when the RLC entity and the PDCP entity are logically or physically separated and cannot be reconstructed at the same time, the method proposed in the present application can prevent the receiving end from receiving data encrypted by the old key without knowing it.
[0051] As an embodiment, compared with the traditional solution, the present application has the following advantages: when an RLC entity associated with a PDCP entity is in a relay node, the relay node can multiplex data of multiple channels or multiple UEs on the RLC bearer corresponding to the same RLC entity. When a PDCP entity associated with this RLC entity needs to be rebuilt, the method proposed in the present application does not need to rebuild the RLC entity, thereby reducing the impact on other channels or other users.
[0052] As an embodiment, compared with the traditional solution, the present application has the following advantages: for a DRB, the RRC connection is continued or the first reconfiguration after the RRC reconstruction generally requires the RLC entity to be rebuilt. If the RLC entity is in the relay node and some services already exist, the reconstruction will affect the existing services. The method proposed in the present application can avoid these impacts and ensure that the data transmission and reception itself has the same technical effect as the RLC reconstruction when there is no data multiplexing.
[0053] As an embodiment, compared with the traditional solution, the present application has the following advantages: when the PDCP entity corresponding to a bearer of a Uu interface is associated with an RLC entity of a PC5 interface, the reconstruction of the PDCP entity of the Uu interface can trigger the reconstruction of the RLC entity of the PC5 interface. This helps to reduce the delay of the PC5 interface and the Uu interface and improve resource utilization efficiency.
[0054] As an embodiment, compared with the traditional solution, the present application has the following advantages: the existing PDCP header format can be used without adding additional bits, so no additional overhead is added. BRIEF DESCRIPTION OF THE DRAWINGS
[0055] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings:
[0056] Figure 1 A flowchart of receiving a first message and sending a first PDCP PDU according to an embodiment of the present application is shown;
[0057] Figure 2A schematic diagram of a network architecture according to an embodiment of the present application is shown;
[0058] Figure 3 A schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;
[0059] Figure 4 A schematic diagram of a first node and a second node according to an embodiment of the present application is shown;
[0060] Figure 5 A flow chart showing transmission according to an embodiment of the present application is shown;
[0061] Figure 6 A flow chart showing transmission according to an embodiment of the present application is shown;
[0062] Figure 7 A schematic diagram of a PDCP PDU according to an embodiment of the present application is shown;
[0063] Figure 8 A schematic diagram of a protocol stack of a layer 2 relay according to an embodiment of the present application is shown;
[0064] Fig. 9 A schematic diagram showing a first message according to an embodiment of the present application being used to set a first field of a first PDCP PDU;
[0065] Fig.10 A schematic diagram showing that a first message according to an embodiment of the present application is not used to reset a first RLC SN;
[0066] Fig.11 A schematic diagram showing a second sequence number being used to determine a fourth sequence number according to an embodiment of the present application;
[0067] Fig.12 A schematic diagram showing a first COUNT value being used to determine a first initial value according to an embodiment of the present application;
[0068] Fig.13 A schematic diagram illustrating a processing device in a first node according to an embodiment of the present application is illustrated;
[0069] Fig.14 A schematic diagram illustrating a processing device in a second node according to an embodiment of the present application is illustrated; DETAILED DESCRIPTION
[0070] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily.
[0071] Example 1
[0072] Embodiment 1 illustrates a flowchart of receiving a first message and sending a first PDCP PDU according to an embodiment of the present application, as shown in the attached Figure 1 Attached Figure 1 In the figure, each box represents a step. It should be emphasized that the order of the boxes in the figure does not represent the temporal relationship between the steps represented.
[0073] In embodiment 1, the first node in the present application receives a first message in step 101; sends a first PDCP PDU in step 102;
[0074] In which, in response to receiving the first message, the first node reconstructs the first PDCP entity; the first PDCP PDU is generated by the first PDCP entity; the first PDCP PDU includes a first field and data, and the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
[0075] As an embodiment, the first node is a UE (User Equipment).
[0076] As an embodiment, the AS (Access Stratum) security of the first node is activated.
[0077] As an embodiment, the first message is an RRC (Radio Resource Control) message.
[0078] As an embodiment, the first message is transmitted via the Uu interface.
[0079] As an embodiment, the first message is transmitted via SRB of the Uu interface.
[0080] As an embodiment, the first message includes RRCReconfiguration.
[0081] As an embodiment, the first message includes RRCConnectionReconfiguration.
[0082] As an embodiment, the first message includes RRCResume.
[0083] As an embodiment, the first message includes RRCConnectionResume.
[0084] As an embodiment, the first message includes RLC-BearerConfig.
[0085] As an embodiment, the first message does not include RLC-BearerConfig.
[0086] As an embodiment, the first message includes cellgroupConfig.
[0087] As an embodiment, the first message does not include cellgroupConfig.
[0088] As an embodiment, the first message includes radioBearerConfig.
[0089] As an embodiment, the first message includes radioBearerConfig2.
[0090] As an embodiment, the first message includes drb-ToAddModList.
[0091] As an embodiment, the first message includes PDCP-Config.
[0092] As an embodiment, the first message includes reestablishPDCP, and reestablishPDCP is set to true.
[0093] As an embodiment, the first message includes keyToUse, and the key indicated by keyToUse has changed compared with the key in the configuration stored by the first node.
[0094] As an embodiment, the first message is a NAS (non-Access Stratum) message.
[0095] As an embodiment, the first message includes SECURITY MODE COMMAND.
[0096] As an embodiment, the first message includes PDU SESSION MODIFICATION COMMAND.
[0097] As an embodiment, the first message includes an AUTHENTICATION REQUEST.
[0098] As an embodiment, the first message includes an AUTHENTICATION REQUEST.
[0099] As an embodiment, the first message includes REGISTRATION ACCEPT.
[0100] As an embodiment, the first message includes SERVICE ACCEPT.
[0101] As an embodiment, the first message includes CONFIGURATION UPDATE COMMAND.
[0102] As an embodiment, the first message includes higher layer signaling.
[0103] As an embodiment, the first message includes a PDCP status report message.
[0104] As an embodiment, the physical channel occupied by the first message includes PSCCH (Physical sidelink control channel) channel transmission.
[0105] As an embodiment, the physical channel occupied by the first message includes PSSCH (Physical sidelink shared channel) channel transmission.
[0106] As an embodiment, the physical channel occupied by the first message includes PDSCH (Physical downlink Shared channel) channel transmission.
[0107] As an embodiment, the first message is transmitted via a secondary link.
[0108] As an embodiment, the first message is used to configure DRB (Data RB).
[0109] As an embodiment, the first message is used to configure RB (Radio Bearer).
[0110] As an embodiment, the first message is used to configure SLRB (Sidelink RB).
[0111] As an embodiment, the first message is used to indicate that the first field of the first PDCP PDU is set to a first initial value.
[0112] As an embodiment, the first domain includes a PDCP SN, and the first initial value is configurable.
[0113] As a sub-embodiment of the above embodiment, the first message is used to set a first state variable, and the first state variable is used to calculate the first initial value.
[0114] As a sub-embodiment of the above embodiment, the first initial value is not 0.
[0115] As a sub-embodiment of the above embodiment, the first initial value is a positive number.
[0116] As a sub-embodiment of the above embodiment, the first initial value is related to the COUNT value associated with the first PDCP PDU.
[0117] As a sub-embodiment of the above embodiment, the first initial value is related to a COUNT value associated with a PDCP SDU carried by the first PDCP PDU.
[0118] As an embodiment, the first field includes at least one R, and each R occupies 1 bit.
[0119] As a sub-embodiment of the above embodiment, the first field of the first PDCP PDU indicates the number of times the first PDCP entity is reestablished.
[0120] As a sub-embodiment of the above embodiment, the first field of the first PDCP PDU is equal to the remainder obtained by taking the number of times the first PDCP entity is reconstructed modulo Q, where Q is 2 to the power of Q1, and Q1 is the number of R included in the first field.
[0121] As an embodiment, the first message explicitly indicates the first initial value.
[0122] As an embodiment, the first message implicitly indicates the first initial value.
[0123] As an embodiment, the first field includes a PDCP SN, and the first message is used to indicate that the first field of the first PDCP PDU is set to a first initial value.
[0124] As an embodiment, the first PDCP entity corresponds to the wireless bearer of the PC5 interface.
[0125] As an embodiment, the first PDCP entity is a sending PDCP entity.
[0126] As an embodiment, the first PDCP entity is a receiving PDCP entity.
[0127] As an embodiment, after the first PDCP entity is rebuilt, all PDCP PDUs of all data types sent before the next rebuilt include the first field, and the value of the first field is the same.
[0128] As an embodiment, after the first PDCP entity is rebuilt, all PDCP PDUs of all data types sent before the next rebuilt include the first field, and the value of the first field changes one by one.
[0129] As a sub-embodiment of the above embodiment, the value of the first field changes cyclically. Each time the first PDCP entity generates a PDCP PDU of a data type, the value of the first field increases by 1 until the maximum value that the first field can represent is reached, and then starts again from 0.
[0130] As an embodiment, the header of the first PDCP PDU includes the first field.
[0131] As an embodiment, the first PDCP PDU is a PDCP PDU of a data type.
[0132] As an embodiment, the first PDCP entity corresponds to the first wireless bearer.
[0133] As an embodiment, the first radio bearer is a radio bearer of a Uu interface.
[0134] As an embodiment, the action of sending the first PDCP PDU is performed after the action of reestablishing the first PDCP entity.
[0135] As an embodiment, the first PDCP PDU is the first PDCP PDU generated by the first PDCP entity after the behavior reestablishes the first PDCP entity.
[0136] As an embodiment, the first radio bearer is an AM DRB.
[0137] As an embodiment, the first radio bearer is a UM DRB.
[0138] As an embodiment, the first radio bearer is configured with encryption.
[0139] As an embodiment, the first radio bearer is not configured with integrity protection.
[0140] As an embodiment, the first PDCP PDU does not use integrity protection.
[0141] As an embodiment, the first RLC entity generates a first RLC PDU based on the first PDCP PDU.
[0142] As an embodiment, the radio bearer used by the first PDCP PDU is the first radio bearer.
[0143] As an embodiment, the first message is used to indicate a first key, and the first PDCP entity encrypts the data included in the first PDCP PDU using the first key;
[0144] As a sub-embodiment of this embodiment, the first key includes K AMF ;
[0145] As a sub-embodiment of this embodiment, the first key includes K gNB ;
[0146] As a sub-embodiment of this embodiment, the first key includes K UP-enc ;
[0147] As a sub-embodiment of this embodiment, the data included in the first PDCP PDU is a PDCP SDU;
[0148] As a sub-embodiment of this embodiment, the data included in the first PDCP PDU includes an IP packet;
[0149] As a sub-embodiment of this embodiment, the data included in the first PDCP PDU includes non-IP data;
[0150] As a sub-embodiment of this embodiment, the data included in the first PDCP PDU includes non-3GPP data;
[0151] As a sub-embodiment of this embodiment, the data included in the first PDCP PDU is Data of the first PDCP PDU;
[0152] As a sub-embodiment of this embodiment, the encryption algorithms used for encrypting the data of the first PDCP PDU include 128-NEA1 and 128-NIA1.
[0153] As a sub-embodiment of this embodiment, the encryption algorithms used for encrypting the data of the first PDCP PDU include 128-NEA2 and 128-NIA2.
[0154] As a sub-embodiment of this embodiment, the encryption algorithms used for encrypting the data of the first PDCP PDU include 128-NEA3 and 128-NIA3.
[0155] As a sub-embodiment of this embodiment, the encryption algorithms used for encrypting the data of the first PDCP PDU include 128-EEA1 and 128-EIA1.
[0156] As a sub-embodiment of this embodiment, the encryption algorithms used for encrypting the data of the first PDCP PDU include 128-EEA2 and 128-EIA2.
[0157] As a sub-embodiment of this embodiment, the encryption algorithms used for encrypting the data of the first PDCP PDU include 128-EEA3 and 128-EIA3.
[0158] As a sub-embodiment of this embodiment, the encryption algorithm used for encrypting the data of the first PDCP PDU includes SNOW.
[0159] As a sub-embodiment of this embodiment, the encryption algorithm used for encrypting the data of the first PDCP PDU includes AES.
[0160] As a sub-embodiment of this embodiment, the encryption algorithm used for encrypting the data of the first PDCP PDU includes ZUC.
[0161] As an embodiment, the first message indicates a keySetChangeIndicator, and the keySetChangeIndicator is used to generate the first key.
[0162] As an embodiment, the first message directly and explicitly indicates the first key.
[0163] As an embodiment, the first message indicates parameters used to generate the first key.
[0164] As an embodiment, the first message indicates that the first key needs to be generated, and the first node generates the first key according to configured or pre-agreed parameters.
[0165] As an embodiment, the first message indicates a nextHopChainingCount, and the nextHopChainingCount is used to generate the first key.
[0166] As an embodiment, the first message indicates a sk-counter, and the sk-counter is used to generate the first key.
[0167] As an embodiment, the first message is used for re-keying.
[0168] As an embodiment, the first message is used for key refresh.
[0169] As an embodiment, the AS security of the first node is activated.
[0170] As an embodiment, the first message indicates a full configuration.
[0171] As an embodiment, the first message is used to trigger the reconstruction of the first PDCP entity.
[0172] As an embodiment, the first message indicates the reconstruction of the first PDCP entity.
[0173] As an embodiment, after the first message is executed, the reconstruction of the first PDCP entity occurs.
[0174] As an embodiment, the first message is executed or applied, resulting in the re-establishment of the first PDCP entity.
[0175] As an embodiment, the behavior of reconstructing the first PDCP entity includes: resetting the uplink header compression protocol and reopening it in the U mode IR state.
[0176] As an embodiment, the behavior of reconstructing the first PDCP entity includes: resetting the EHC uplink header compression protocol.
[0177] As an embodiment, the behavior of reconstructing the first PDCP entity includes: setting TX_NEXT to an initial value.
[0178] As an embodiment, the behavior of reconstructing the first PDCP entity includes: setting TX_NEXT to the first initial value.
[0179] As an embodiment, the behavior of reconstructing the first PDCP entity includes: applying an encryption algorithm and key provided by a higher layer during the PDCP entity reconstruction process.
[0180] As an embodiment, the behavior of reconstructing the first PDCP entity includes: for each PDCP SDU associated with a PDCP SN, and the PDCP PDUs corresponding to these PDCP SDUs have not been submitted to the lower layer, these PDCP SDUs are considered to be received from a higher layer, and these PDCP SDUs are sent in the order of COUNT values associated with these PDCP SDUs respectively and determined before the first PDCP entity is reconstructed, and there is no need to restart the discard timer.
[0181] As an embodiment, the behavior of reconstructing the first PDCP entity includes: for each PDCP SDU associated with a PDCP SN, and the PDCP PDUs corresponding to these PDCP SDUs have not been confirmed by the lower layer and the bearer corresponding to the first PDCP entity is suspended, these PDCP SDUs are considered to be received from a higher layer, and these PDCP SDUs are sent in the order of the COUNT values associated with these PDCP SDUs respectively and determined before the first PDCP entity is reconstructed, and there is no need to restart the discard timer.
[0182] As an embodiment, the behavior of reestablishing the first PDCP entity includes: starting from the first PDCP SDU whose corresponding PDCP data PDU has not been confirmed by the lower layer, for all PDCP SDUs that have been associated with PDCP SNs, performing retransmission or transmission, and the order of transmission is determined according to the COUNT values associated with these PDCP SDUs before the first PDCP entity is reestablished;
[0183] As a sub-embodiment of this embodiment, ROHC is used and / or header compression is performed on these PDCP SDUs;
[0184] As a sub-embodiment of this embodiment, the PDCP SDUs are encrypted using COUNT values associated with the PDCP SDUs;
[0185] As a sub-embodiment of this embodiment, the PDCP PDU generated by these PDCP SDUs is submitted to a lower layer.
[0186] As an embodiment, the behavior of reconstructing the first PDCP entity includes: processing a PDCP data PDU received from a lower layer due to the reconstruction of the lower layer.
[0187] As an embodiment, the behavior of reconstructing the first PDCP entity includes: stopping and resetting the t-Reordering timer; after header decompression, sending all cached PDCP SDUs to a higher layer according to the associated COUNT value.
[0188] As an embodiment, the behavior of reconstructing the first PDCP entity includes: using ROHC to perform header decompression.
[0189] As an embodiment, the behavior of reconstructing the first PDCP entity includes: using EHC to perform header decompression.
[0190] As an embodiment, the behavior of reconstructing the first PDCP entity includes: for the ROHC protocol, resetting the ROHC protocol and entering the NC state of the U mode.
[0191] As an embodiment, the behavior of reconstructing the first PDCP entity includes: resetting the EHC protocol.
[0192] As an embodiment, the behavior of reconstructing the first PDCP entity includes: setting RX_NEXT and RX_DELIV to initial values.
[0193] As a sub-embodiment of this embodiment, the initial value is the first initial value.
[0194] As an embodiment, the first message explicitly sets the first domain of the first PDCP PDU.
[0195] As an embodiment, the first PDCP entity is a generator of the first PDCP PDU.
[0196] As an embodiment, the first PDCP PDU includes the first field and data, and the data is PDCP SDU.
[0197] As an embodiment, the first PDCP PDU includes the first domain and data, and the data is an IP packet.
[0198] As an embodiment, the first PDCP PDU includes the first domain and data, and the data is SDAPPDU.
[0199] As an embodiment, the first PDCP PDU includes the first domain and data, and the data is a non-IP data packet.
[0200] As an embodiment, the first PDCP PDU includes the first domain and data, and the data is the payload of the first PDCP PDU.
[0201] As an embodiment, the first PDCP PDU carries a first PDCP SDU; a PDCP PDU carries only one PDCP SDU.
[0202] As a sub-embodiment of this embodiment, the PDCP SDU is received before the behavior reestablishes the first PDCP entity, and the PDCP PDU corresponding to the first PDCP SDU is not submitted to a lower layer before the behavior reestablishes the first PDCP entity;
[0203] As a sub-embodiment of this embodiment, the PDCP SDU is received before the behavior reestablishes the first PDCP entity, and the PDCP PDU corresponding to the first PDCP SDU is not confirmed by a lower layer before the behavior reestablishes the first PDCP entity;
[0204] As a sub-embodiment of this embodiment, the PDCP SDU is received before the behavior reestablishes the first PDCP entity and is associated with a PDCP SN, and the PDCP PDU corresponding to the first PDCP SDU is not submitted to a lower layer before the behavior reestablishes the first PDCP entity;
[0205] As a sub-embodiment of this embodiment, the PDCP SDU is received after the behavior reestablishes the first PDCP entity.
[0206] As an embodiment, the first PDCP PDU is generated using parameters after the first PDCP entity is reestablished.
[0207] As an embodiment, the header of the first PDCP PDU is generated or determined by a state variable after the first PDCP entity is reestablished.
[0208] As an embodiment, the sending or resending of the first PDCP PDU occurs after the first PDCP entity is reestablished.
[0209] As an embodiment, the state variables related to sending of the first PDCP entity are reset and set to initial values during the PDCP entity reconstruction process, the state variables related to receiving of the first PDCP entity are not reset during the PDCP entity reconstruction process, and the state variables related to receiving of the first PDCP entity are reset and set to initial values after the PDCP entity is reconstructed and a PDCP PDU is received.
[0210] As a sub-embodiment of the above embodiment, the first message is used to indicate the initial value of the state variable related to the sending.
[0211] As a sub-embodiment of the above embodiment, the first message is used to indicate the initial value of the state variable related to the reception.
[0212] As a sub-embodiment of the above embodiment, the reception-related state variable of the first PDCP entity is generated after the PDCP entity is rebuilt and the first field of the one PDCP PDU is received, indicating that the one PDCP PDU is generated after the corresponding PDCP entity is rebuilt.
[0213] As an embodiment, the state variables related to sending of the first PDCP entity are reset and set to initial values during the PDCP entity reconstruction process, the state variables related to receiving of the first PDCP entity are not reset during the PDCP entity reconstruction process, the reconstruction of the first PDCP entity includes starting a first timer, and the state variables related to receiving of the first PDCP entity are reset and set to initial values after the first timer expires.
[0214] As a sub-embodiment of the above embodiment, the first timer is predefined, for example, 100 ms.
[0215] As a sub-embodiment of the above embodiment, the first timer is indicated by the first message.
[0216] As a sub-embodiment of the above embodiment, the first message is used to indicate the initial value of the state variable related to the sending.
[0217] As a sub-embodiment of the above embodiment, the first message is used to indicate the initial value of the state variable related to the reception.
[0218] As an embodiment, the state variables related to transmission are reset during the reestablishment to facilitate rapid reestablishment, and the state variables related to reception are reset later to facilitate reception of data sent before the reestablishment but buffered in the RLC.
[0219] Example 2
[0220] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 Attached Figure 2The V2X communication architecture under the 5G NR (New Radio), LTE (Long-Term Evolution) and LTE-A (Long-Term Evolution Advanced) system architecture is described. The 5G NR or LTE network architecture may be referred to as 5GS (5G System) / EPS (Evolved Packet System) or some other appropriate terminology.
[0221] The V2X communication architecture of embodiment 2 includes UE (User Equipment) 201, UE 241, NG-RAN (next generation radio access network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, ProSe function 250 and ProSe application server 230. The V2X communication architecture can be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the V2X communication architecture provides packet switching services, but technicians in the field will easily understand that the various concepts presented throughout this application can be extended to networks that provide circuit switching services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol termination towards UE 201. gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). The gNB 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (transmit receive node), or some other suitable term. The gNB 203 provides an access point to the 5GC / EPC 210 for the UE 201. Examples of UE 201 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device. The UE 201 may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term. The gNB 203 is connected to the 5GC / EPC 210 via an S1 / NG interface.5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF214, S-GW (Service Gateway) / UPF (User Plane Function) 212 and P-GW (Packet Data Network Gateway) / UPF213. MME / AMF / SMF211 is the control node that handles the signaling between UE201 and 5GC / EPC210. In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocal) packets are transmitted through S-GW / UPF212, which itself is connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes Internet protocol services corresponding to operators, which may specifically include Internet, intranet, IMS (IP Multimedia Subsystem) and packet switching streaming services. The ProSe function 250 is a logical function for network-related behaviors required for Proximity-based Service (ProSe); including DPF (Direct Provisioning Function), Direct Discovery Name Management Function, EPC-level Discovery ProSe Function, etc. The ProSe application server 230 has the functions of storing EPC ProSe user identities, mapping between application layer user identities and EPC ProSe user identities, and allocating ProSe restricted code suffix pools.
[0222] As an embodiment, the UE201 and the UE241 are connected via a PC5 reference point (Reference Point).
[0223] As an embodiment, the ProSe function 250 is connected to the UE 201 and the UE 241 via a PC3 reference point respectively.
[0224] As an embodiment, the ProSe function 250 is connected to the ProSe application server 230 via a PC2 reference point.
[0225] As an embodiment, the ProSe application server 230 is connected to the ProSe application of the UE 201 and the ProSe application of the UE 241 through a PC1 reference point respectively.
[0226] As an embodiment, the second node, the first node and the third node in the present application are NR Node B, UE201 and UE241 respectively.
[0227] As an embodiment, the first node and the second node in the present application are UE201 and UE241 respectively.
[0228] As an embodiment, the first node and the third node in the present application are UE201 and UE241 respectively.
[0229] As an embodiment, the second node and the third node in the present application are UE201 and UE241 respectively.
[0230] As an embodiment, the wireless link between the UE201 and the UE241 corresponds to the side link (Sidelink, SL) in this application.
[0231] As an embodiment, the wireless link from the UE201 to the NR Node B is an uplink.
[0232] As an embodiment, the wireless link from the NR Node B to UE201 is a downlink.
[0233] As an embodiment, the UE 201 supports relay transmission.
[0234] As an embodiment, the UE 241 supports relay transmission.
[0235] As an embodiment, the UE 201 is a vehicle including a car.
[0236] As an embodiment, the UE 241 is a vehicle including a car.
[0237] As an embodiment, the gNB203 is a macrocellular base station.
[0238] As an embodiment, the gNB203 is a micro cell base station.
[0239] As an embodiment, the gNB203 is a picoCell base station.
[0240] As an embodiment, the gNB203 is a flying platform device.
[0241] As an embodiment, the gNB203 is a satellite device.
[0242] Example 3
[0243] Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture of the control plane 300 for a first node (UE, satellite or aircraft in gNB or NTN) and a second node (satellite or aircraft in gNB, UE or NTN), or between two UEs is shown in three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to as PHY301 in this article. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first node and the second node and the two UEs through PHY301. The L2 layer 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second node. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides support for inter-zone mobility of the first node between the second node. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between the first nodes. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layer using RRC signaling between the second node and the first node. The PC5-S (PC5 Signaling Protocol) sublayer 307 is responsible for processing the signaling protocol of the PC5 interface. The radio protocol architecture of the user plane 350 includes Layer 1 (L1 layer) and Layer 2 (L2 layer). The radio protocol architecture for the first node and the second node in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS flows and data radio bearers (DRBs) to support the diversity of services. Although not shown, the first node may have several upper layers above the L2 layer 355. In addition, it also includes a network layer (e.g., an IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., a remote UE, a server, etc.). For UEs involved in relay services, their control plane may also include an adaptation sublayer AP308, and their user plane may also include an adaptation sublayer AP358. The introduction of the adaptation layer helps lower layers, such as the MAC layer, such as the RLC layer, to multiplex and / or distinguish data from multiple source UEs. In addition, the adaptation sublayers AP308 and AP358 may also be used as sublayers within PDCP304 and PDCP354, respectively. RRC306 can be used to process RRC signaling of the Uu interface and signaling of the PC5 interface.
[0244] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.
[0245] As an example, Figure 3 The wireless protocol architecture in is applicable to the second node in this application.
[0246] As an example, Figure 3 The wireless protocol architecture in is applicable to the third node in this application.
[0247] As an embodiment, the first message in the present application is generated in RRC306 or PC5-S307 or NAS.
[0248] As an embodiment, the second message in the present application is generated in RRC306 or PC5-S307 or NAS.
[0249] As an embodiment, the first PDCP PDU in the present application is generated by the PDCP354.
[0250] As an embodiment, the second PDCP PDU in the present application is generated by the PDCP354.
[0251] As an embodiment, the second PDCP SDU in the present application is generated at a layer above SDAP356 or PDCP354.
[0252] As an embodiment, the first report in the present application is generated by the PDCP354.
[0253] As an embodiment, the second report in the present application is generated by the PDCP354.
[0254] As an embodiment, the first RLC PDU in the present application is generated in the PDCP353.
[0255] Example 4
[0256] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in the attached figure. Figure 4 shown. Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.
[0257] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454 and an antenna 452.
[0258] The second communication device 410 includes a controller / processor 475 , a memory 476 , a receive processor 470 , a transmit processor 416 , a multi-antenna receive processor 472 , a multi-antenna transmit processor 471 , a transmitter / receiver 418 and an antenna 420 .
[0259] In transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements the functionality of the L2 layer. In transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.
[0260] In the transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program codes and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.
[0261] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission function at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream, and then provides it to the antenna 452.
[0262] In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the reception function at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 storing program codes and data. The memory 476 can be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.
[0263] As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 apparatus at least: receives a first message; in response to receiving the first message, reconstructs a first PDCP entity; sends a first PDCP PDU, the first PDCP PDU is generated by the first PDCP entity; wherein the first PDCP PDU includes a first field and data, the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
[0264] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: receiving a first message; reestablishing a first PDCP entity in response to receiving the first message; sending a first PDCP PDU, wherein the first PDCP PDU is generated by the first PDCP entity; wherein the first PDCP PDU includes a first field and data, and the first message is used to set the first field of the first PDCP PDU; and the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
[0265] As an embodiment, the second communication device 410 device includes: at least one processor and at least one memory, the at least one memory includes computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 410 device at least: sends a first message; the first message is used to trigger the reestablishment of a first PDCP entity; receives a first PDCP PDU, the first PDCP PDU is generated by the first PDCP entity; wherein the first PDCP PDU includes a first field and data, the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reestablishment of the first PDCP entity.
[0266] As an embodiment, the second communication device 410 apparatus includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: sending a first message; the first message is used to trigger the reconstruction of a first PDCP entity; receiving a first PDCP PDU, the first PDCP PDU being generated by the first PDCP entity; wherein the first PDCP PDU includes a first field and data, the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
[0267] As an embodiment, the first communication device 450 corresponds to the first node in this application.
[0268] As an embodiment, the second communication device 410 corresponds to the second node in this application.
[0269] As an embodiment, the second communication device 410 corresponds to the third node in this application.
[0270] As an embodiment, the first communication device 450 is a UE.
[0271] As an embodiment, the first communication device 450 is a vehicle-mounted terminal.
[0272] As an embodiment, the second communication device 410 is a UE.
[0273] As an embodiment, the first communication device 410 is a vehicle-mounted terminal.
[0274] As an embodiment, the receiver 456 (including the antenna 460), the receiving processor 452 and the controller / processor 490 are used to receive the first message in the present application.
[0275] As an embodiment, the receiver 456 (including the antenna 460), the receiving processor 452 and the controller / processor 490 are used in the present application to receive the second report.
[0276] As an embodiment, the transmitter 456 (including the antenna 460), the transmission processor 455 and the controller / processor 490 are used to send the second message in the present application.
[0277] As an embodiment, the transmitter 456 (including the antenna 460), the transmit processor 455 and the controller / processor 490 are used to send the first PDCP PDU in the present application.
[0278] As an embodiment, the transmitter 456 (including the antenna 460), the transmit processor 455 and the controller / processor 490 are used to send the first RLC PDU in the present application.
[0279] As an embodiment, the transmitter 456 (including the antenna 460), the transmit processor 455 and the controller / processor 490 are used to send the first report in the present application.
[0280] As an embodiment, the transmitter 416 (including the antenna 420), the transmit processor 412 and the controller / processor 440 are used to send the first message in the present application.
[0281] As an embodiment, the transmitter 416 (including the antenna 420), the transmit processor 412 and the controller / processor 440 are used to send the second report in the present application.
[0282] As an embodiment, the receiver 416 (including the antenna 420), the receiving processor 412 and the controller / processor 440 are used to receive the first PDCP PDU in the present application.
[0283] As an embodiment, the receiver 416 (including the antenna 420), the receiving processor 412 and the controller / processor 440 are used to receive the first RLC PDU in the present application.
[0284] As an embodiment, the receiver 416 (including the antenna 420), the receiving processor 412 and the controller / processor 440 are used to receive the first report in the present application.
[0285] Example 5
[0286] Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 Attached Figure 5 In the example, U01 corresponds to the first node of the present application, and U02 corresponds to the second node of the present application. It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in the present application, wherein the steps in F51 are optional.
[0287] for First node U01 , receiving a first message in step S5101; sending a first PDCP PDU in step S5102; receiving a second report in step S5103; and sending a first report in step S5104.
[0288] for Second node U02, sending a first message in step S5201; receiving a first PDCP PDU in step S5202; sending a second report in step S5203; receiving the first report in step S5204.
[0289] In Example 5, in response to receiving the first message, the first node U01 reconstructs the first PDCP entity; the first PDCP PDU is generated by the first PDCP entity; the first PDCP PDU includes a first field and data, and the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
[0290] As an embodiment, the communication interface between the first node U01 and the second node U02 is Uu.
[0291] As an embodiment, the communication interface between the first node U01 and the second node U02 is PC5.
[0292] As an embodiment, the radio bearer associated with the first PDCP entity is a first radio bearer, and the identity of the first radio bearer is used for encryption of the data included in the first PDCP PDU.
[0293] As an embodiment, the second node N02 is a service cell of the first node U01.
[0294] As an embodiment, the second node N02 is the primary service cell of the first node U01.
[0295] As an embodiment, the second node N02 is the service cell group of the first node U01.
[0296] As an embodiment, the second node N02 is a relay node of the first node U01.
[0297] As an embodiment, before the second node N02 sends the first message, the second node N02 receives a message from the core network indicating that the key of the first node U01 needs to be updated.
[0298] As a sub-embodiment of the above embodiment, the message from the core network is used to trigger the first message.
[0299] As an embodiment, before the second node N02 sends the first message, the message received by the second node N02 from the core network is used to indicate or to generate a new key for the first node U01.
[0300] As a sub-embodiment of the above embodiment, the message from the core network is used to trigger the first message.
[0301] As an embodiment, before the second node N02 sends the first message, the second node N02 receives a message from the core network indicating that the security context of the first node U01 is out of synchronization.
[0302] As a sub-embodiment of the above embodiment, the message from the core network is used to trigger the first message.
[0303] As an embodiment, before the second node N02 sends the first message, the first node U01 receives a message from the core network indicating that the key of the first node U01 needs to be updated.
[0304] As an embodiment, before the second node N02 sends the first message, the message received by the first node U01 from the core network is used to indicate or generate a new key for the first node U01.
[0305] As a sub-embodiment of the above embodiment, the message from the core network is used to trigger the re-establishment of the first PDCP entity.
[0306] As an embodiment, the message from the core network includes SECURITY MODE COMMAND.
[0307] As an embodiment, the message from the core network includes PDU SESSION MODIFICATION COMMAND.
[0308] As an embodiment, the message from the core network includes an AUTHENTICATION REQUEST.
[0309] As an embodiment, the message from the core network includes an AUTHENTICATION REQUEST.
[0310] As an embodiment, the message from the core network includes REGISTRATION ACCEPT.
[0311] As an embodiment, the message from the core network includes SERVICE ACCEPT.
[0312] As an embodiment, the message from the core network includes a CONFIGURATION UPDATE COMMAND.
[0313] As an embodiment, the first message comes from the core network, and the second node N02 forwards the first message.
[0314] As an embodiment, the radio bearer occupied by the first PDCP PDU is suspended before the first PDCP entity is reestablished.
[0315] As an embodiment, the radio bearer occupied by the first PDCP PDU is active before the first PDCP entity is reestablished.
[0316] As an embodiment, the first PDCP PDU uses the first radio bearer.
[0317] As an embodiment, the first radio bearer is an AM DRB.
[0318] As an embodiment, the first radio bearer is a UM DRB.
[0319] As an embodiment, the first PDCP PDU is forwarded by a relay node before being received by the second node N02.
[0320] As an embodiment, the D / C field of the header of the first PDCP PDU is 1.
[0321] As an embodiment, the behavior of sending a first PDCP PDU includes: sending a first RLC PDU, the first RLC PDU includes the first PDCP PDU, the first RLC PDU includes a first RLC SN; wherein the first message is not used to reset the first RLC SN;
[0322] As a sub-embodiment of this embodiment, the first RLC PDU is generated by the first node U01;
[0323] As a sub-embodiment of this embodiment, the first RLC PDU is generated by a node other than the first node U01;
[0324] As a sub-embodiment of this embodiment, the RLC SDU corresponding to the first RLC PDU is the first PDCP PDU;
[0325] As a sub-embodiment of this embodiment, the first RLC PDU includes at least a part of the first PDCP PDU;
[0326] As a sub-embodiment of this embodiment, the header of the first RLC PDU includes a first RLC SN;
[0327] As a sub-embodiment of this embodiment, the RLC mode used by the RLC entity corresponding to the first RLC PDU is AM;
[0328] As a sub-embodiment of this embodiment, the RLC mode used by the RLC entity corresponding to the first RLC PDU is UM;
[0329] As a sub-embodiment of this embodiment, the RLC mode used by the RLC entity corresponding to the first RLC PDU is bidirectional UM;
[0330] As a sub-embodiment of this embodiment, the RLC layer where the RLC entity corresponding to the first RLC PDU is located is a lower layer of the first PDCP entity;
[0331] As a sub-embodiment of this embodiment, the RLC bearer corresponding to the first RLC PDU belongs to the bearer of the PC5 interface;
[0332] As a sub-embodiment of this embodiment, the RLC bearer corresponding to the first RLC PDU belongs to a bearer of a Uu interface;
[0333] As a sub-embodiment of this embodiment, the first message is used to reset the first RLC SN;
[0334] As a sub-embodiment of this embodiment, the first message is used to reconstruct the RLC entity corresponding to the first RLC PDU.
[0335] As an embodiment, the first report indicates that the second PDCP SDU is not received by indicating a second sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is reestablished is the second sequence number; the behavior of sending the first report is performed after the behavior reestablishes the first PDCP entity;
[0336] As a sub-embodiment of this embodiment, the first report is a PDCP status report;
[0337] As a sub-embodiment of this embodiment, the first report indicates the second sequence number through a bitmap;
[0338] As a sub-embodiment of this embodiment, before the first PDCP entity is reestablished, the PDCP SN associated with the second PDCP SDU is the second sequence number;
[0339] As a sub-embodiment of this embodiment, the re-establishment of the first PDCP entity does not affect the PDCP SDU to which the PDCP SN has been allocated or associated;
[0340] As a sub-embodiment of this embodiment, the second sequence number is a PDCP SN;
[0341] As a sub-embodiment of this embodiment, the second sequence number is a COUNT value of the PDCP SDU;
[0342] As a sub-embodiment of this embodiment, the first report indicates the second sequence number through an FMC field;
[0343] As a sub-embodiment of this embodiment, the PDCP SDUs corresponding to all sequence numbers indicated by the first report are not received by the sender of the first report;
[0344] As a sub-embodiment of this embodiment, the PDU Type field of the first report is set to 000;
[0345] As a sub-embodiment of this embodiment, the first report does not carry the PDCP SN;
[0346] As a sub-embodiment of this embodiment, the first report is a control type PDCP PDU;
[0347] As a sub-embodiment of this embodiment, the COUNT value associated with the second PDCP SDU before the first PDCP entity is rebuilt is updated after the first PDCP entity is rebuilt; the PDCP SN associated with the second PDCP SDU before the first PDCP entity is rebuilt is not updated after the first PDCP entity is rebuilt.
[0348] As an embodiment, the first report indicates that the second PDCP SDU is not received by indicating a fourth sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is reestablished is a second sequence number; the second sequence number is different from the fourth sequence number, and the second sequence number is used to determine the fourth sequence number; the behavior of sending the first report is performed after the behavior reestablishes the first PDCP entity;
[0349] As a sub-embodiment of this embodiment, the first report is a PDCP status report;
[0350] As a sub-embodiment of this embodiment, the first report indicates the fourth sequence number through a bitmap;
[0351] As a sub-embodiment of this embodiment, before the first PDCP entity is reestablished, the PDCP SN associated with the second PDCP SDU is the second sequence number;
[0352] As a sub-embodiment of this embodiment, the fourth sequence number is a PDCP SN;
[0353] As a sub-embodiment of this embodiment, the fourth sequence number is a COUNT value of the PDCP SDU;
[0354] As a sub-embodiment of this embodiment, the first report indicates the fourth sequence number through an FMC field;
[0355] As a sub-embodiment of this embodiment, the PDCP SDUs corresponding to all sequence numbers indicated by the first report are not received by the sender of the first report;
[0356] As a sub-embodiment of this embodiment, the PDU Type field of the first report is set to 000;
[0357] As a sub-embodiment of this embodiment, the first report does not carry the PDCP SN;
[0358] As a sub-embodiment of this embodiment, the first report is a control type PDCP PDU;
[0359] As a sub-embodiment of this embodiment, the PDCP SN associated with the second PDCP SDU before the first PDCP entity is reestablished is updated after the first PDCP entity is reestablished;
[0360] As a sub-embodiment of this embodiment, the COUNT value associated with the second PDCP SDU before the first PDCP entity is reestablished is updated after the first PDCP entity is reestablished;
[0361] As a sub-embodiment of this embodiment, the PDCP SN associated with the second PDCP SDU before the first PDCP entity is reestablished is updated after the first PDCP entity is reestablished; the COUNT value associated with the second PDCP SDU before the first PDCP entity is reestablished is not updated after the first PDCP entity is reestablished;
[0362] As a sub-embodiment of this embodiment, the COUNT value associated with the second PDCP SDU before the first PDCP entity is rebuilt is updated after the first PDCP entity is rebuilt; the PDCP SN associated with the second PDCP SDU before the first PDCP entity is rebuilt is updated after the first report is sent.
[0363] As an embodiment, the reception of the first message is used to trigger the sending of the first report.
[0364] As an embodiment, the reconstruction of the first PDCP entity triggers the sending of the first report.
[0365] As an embodiment, the second report is used to indicate a first COUNT value; the first COUNT value is a first lost COUNT value; the first COUNT value is used to determine a first initial value; the initial value of at least one state variable of the first PDCP entity is set to the first initial value after the behavior reestablishes the first PDCP entity, and the first initial value is non-0;
[0366] As a sub-embodiment of this embodiment, the second report is a PDCP status report;
[0367] As a sub-embodiment of this embodiment, the PDU Type field of the first report is set to 000;
[0368] As a sub-embodiment of this embodiment, the FMC (First Missing Count) field of the second report indicates the first missing COUNT value;
[0369] As a sub-embodiment of this embodiment, the FMC (First Missing Count) field of the second report indicates a COUNT value associated with the first lost PDCP SDU;
[0370] As a sub-embodiment of this embodiment, the at least one state variable of the first PDCP entity includes TX_NEXT;
[0371] As a sub-embodiment of this embodiment, the at least one state variable of the first PDCP entity includes RX_NEXT;
[0372] As a sub-embodiment of this embodiment, the at least one state variable of the first PDCP entity includes RX_DELIV;
[0373] As a sub-embodiment of this embodiment, the first initial value is greater than 0;
[0374] As a sub-embodiment of this embodiment, the value range of the first initial value is 0 to 2 to the power of Q minus 1; wherein Q is the length of the PDCP sequence number allocated by the first PDCP entity;
[0375] As a sub-embodiment of this embodiment, the value range of the first initial value is 0 to 2 to the power of Q minus 1; wherein Q is the length of the sequence number of the first PDCP PDP;
[0376] As a sub-embodiment of this embodiment, the first PDCP entity updates a COUNT associated with the PDCP SDU that is not correctly received and indicated by the second report;
[0377] As a sub-embodiment of this embodiment, the COUNT associated with the PDCP SDU that is not correctly received and indicated by the second report by the first PDCP entity is increased by the first initial value respectively;
[0378] As a sub-embodiment of this embodiment, the PDCP SN associated with the PDCP SDU that is not correctly received and indicated by the second report by the first PDCP entity is increased by the first initial value respectively;
[0379] As a sub-embodiment of this embodiment, the COUNT value associated with the PDCP SDU that is not correctly received and indicated by the second report is discarded by the first PDCP entity;
[0380] As a sub-embodiment of this embodiment, the COUNT associated with the PDCP SDU that is not correctly received and indicated by the second report by the first PDCP entity is re-determined and associated according to TX_NEXT;
[0381] As a sub-embodiment of this embodiment, the first PDCP entity encrypts the PDCP SDU indicated by the second report that is not correctly received using a newly associated COUNT value;
[0382] As a sub-embodiment of this embodiment, the first PDCP entity retransmits the PDCP SDU that is not correctly received and indicated by the second report, and the first field of the PDCP PDU sent by the retransmission indicates that the retransmitted PDCP PDU is generated after the reestablishment of the first PDCP entity;
[0383] As a sub-embodiment of this embodiment, the reception of the second report is used to trigger the re-establishment of the first PDCP entity;
[0384] As a sub-embodiment of this embodiment, a field of the second report indicates the reconstruction of the first PDCP entity.
[0385] As an embodiment, the first PDCP PDU is sent via a secondary link.
[0386] As an embodiment, the MAC subheader of the MAC sub-PDU carrying the first PDCP PDU includes at least a portion of bits of the first link layer identity and at least a portion of bits of the second link layer identity.
[0387] As a sub-embodiment of the above embodiment, the first link layer identity is used to identify the first node U01.
[0388] As a sub-embodiment of the above embodiment, the second link layer identity is used to identify a relay node of the first node U01.
[0389] As a sub-embodiment of the above embodiment, the second link layer identity is used to identify the second node N02.
[0390] Example 6
[0391] Embodiment 6 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 6 Attached Figure 6 In the example, U11 corresponds to the first node of the present application, and U13 corresponds to the third node of the present application. It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in the present application, wherein the steps in F61 are optional. Example 6 is based on Example 5, and the parts involved but not described in detail in Example 6 can refer to Example 5.
[0392] for First node U11 , sending the second message in step S6101; receiving the third message in step S6102.
[0393] for The third node U13 , receiving the second message in step S6301; sending the third message in step S6302.
[0394] As an embodiment, the third node U13 is a relay node of the first node U11.
[0395] As an embodiment, the third node U13 is a relay node from the first node U11 to the serving cell.
[0396] As an embodiment, the interface between the first node U01 and the third node U13 is a PC5 interface.
[0397] As an embodiment, the second message includes higher layer signaling.
[0398] As an embodiment, the second message includes RRC (Radio Resource Control) signaling.
[0399] As an embodiment, the RRC signaling includes PC5-RRC signaling.
[0400] As an embodiment, the second message includes PC5-S signaling.
[0401] As an embodiment, the second message includes ProSe signaling.
[0402] As an embodiment, the second message is sent on the Uu interface.
[0403] As an embodiment, the second message is sent on the PC5 interface.
[0404] As an embodiment, the second message is transmitted via the SCCH (Sidelink Control Channel) channel.
[0405] As an embodiment, the second message is transmitted via the STCH (Sidelink Traffic Channel) channel.
[0406] As an embodiment, the second message is transmitted via a PSCCH (Physical sidelink control channel) channel.
[0407] As an embodiment, the second message is transmitted via a PSSCH (Physical sidelink shared channel) channel.
[0408] As an embodiment, the second message is transmitted via a PSBCH (Physical sidelink broadcast channel) channel.
[0409] As an embodiment, the second message is transmitted via the SL-SCH channel.
[0410] As an embodiment, the second message is transmitted via a secondary link.
[0411] As an embodiment, the second message is used to configure DRB (Data RB).
[0412] As an embodiment, the second message is used to configure RB (Radio Bearer).
[0413] As an embodiment, the second message is used to configure SLRB (Sidelink RB).
[0414] As an embodiment, the second message includes RRCReconfigurationSidelink.
[0415] As an embodiment, the second message includes RRCReconfigurationCompleteSidelink.
[0416] As an embodiment, the second message includes a partial field in RRCReconfigurationSidelink.
[0417] As an embodiment, the second message includes RRCReconfiguration.
[0418] As an embodiment, the second message includes SIB12.
[0419] As an embodiment, the second message includes SLRB-Config.
[0420] As an embodiment, the second message includes sl-PDCP-ConfigPC5.
[0421] As an embodiment, the second message includes sl-RLC-ConfigPC5.
[0422] As an embodiment, the second message includes sl-MAC-LogicalChannelConfigPC5.
[0423] As an embodiment, the second message includes PC5-S signaling.
[0424] As an embodiment, the second message includes SL-LogicalChannelConfigPC5.
[0425] As an embodiment, the second message includes SL-LogicalChannelConfig.
[0426] As an embodiment, the second message includes SL-LogicalChannelConfig-r16.
[0427] As an embodiment, the second message includes SL-LogicalChannelConfig-r17.
[0428] As an embodiment, the second message includes part of the fields in SL-LogicalChannelConfig.
[0429] As an embodiment, the second message includes sl-RLC-Config.
[0430] As an embodiment, the second message includes sl-RLC-Config-r16.
[0431] As an embodiment, the second message includes sl-RLC-Config-r17.
[0432] As an embodiment, the second message includes part of the fields in sl-RLC-Config.
[0433] As an embodiment, the second message includes sl-LogicalChannelGroup.
[0434] As an embodiment, the second message includes RRCConnectionReconfigurationSidelink.
[0435] As an embodiment, the second message includes RRCConnectionReconfiguration.
[0436] As an embodiment, the second message includes a DIRECT LINK ESTABLISHMENT REQUEST.
[0437] As an embodiment, the second message includes DIRECT LINK ESTABLISHMENT ACCEPT.
[0438] As an embodiment, the second message includes a DIRECT LINK MODIFICATION REQUEST.
[0439] As an embodiment, the second message includes DIRECT LINK MODIFICATION ACCEPT.
[0440] As an embodiment, the second message includes a DIRECT LINK KEEPALIVE REQUEST.
[0441] As an embodiment, the second message includes a DIRECT LINK KEEPALIVE RESPONSE.
[0442] As an embodiment, the second message includes a DISCOVERY_REQUEST.
[0443] As an embodiment, the second message includes DISCOVERY_RESPONSE.
[0444] As an embodiment, the second message includes a Direct Security Mode Command.
[0445] As an embodiment, the second message includes Direct Security Mode Complete.
[0446] As an embodiment, the second message is a message from a serving cell forwarded by the first node U11.
[0447] As an embodiment, the behavior of reestablishing the first PDCP entity includes: reestablishing a first RLC entity, the first RLC entity being associated with the first PDCP entity; the second message indicating that the first RLC entity is reestablished;
[0448] As a sub-embodiment of this embodiment, the first RLC entity is in the third node U13;
[0449] As a sub-embodiment of this embodiment, the first RLC entity being rebuilt includes: discarding all RLC SDUs, RLC SDU segments and RLC PDUs;
[0450] As a sub-embodiment of this embodiment, the first RLC entity being reestablished includes: stopping and resetting the timers of all RLC entities;
[0451] As a sub-embodiment of this embodiment, the first RLC entity is rebuilt including: resetting all state variables and setting the state variables to initial values.
[0452] As an embodiment, the first RLC entity is used to transmit the first PDCP PDU.
[0453] As an embodiment, the first RLC entity generates a first RLC PDU, and the first RLC PDU carries the first PDCP PDU.
[0454] As an embodiment, the third message is used to feedback the second message.
[0455] As an embodiment, the second message is used to feed back the third message.
[0456] As an embodiment, the third message includes higher layer signaling.
[0457] As an embodiment, the third message includes RRC (Radio Resource Control) signaling.
[0458] As an embodiment, the RRC signaling includes PC5-RRC signaling.
[0459] As an embodiment, the third message includes PC5-S signaling.
[0460] As an embodiment, the third message includes ProSe signaling.
[0461] As an embodiment, the third message is sent on the Uu interface.
[0462] As an embodiment, the third message is sent on the PC5 interface.
[0463] As an embodiment, the third message is transmitted via the SCCH (Sidelink Control Channel) channel.
[0464] As an embodiment, the third message is transmitted via the STCH (Sidelink Traffic Channel) channel.
[0465] As an embodiment, the third message is transmitted via a PSCCH (Physical sidelink control channel) channel.
[0466] As an embodiment, the third message is transmitted via a PSSCH (Physical sidelink shared channel) channel.
[0467] As an embodiment, the third message is transmitted via a PSBCH (Physical sidelink broadcast channel).
[0468] As an embodiment, the third message is transmitted through the SL-SCH channel.
[0469] As an embodiment, the third message is transmitted via a secondary link.
[0470] As an embodiment, the third message is used to configure DRB (Data RB).
[0471] As an embodiment, the third message is used to configure RB (Radio Bearer).
[0472] As an embodiment, the third message is used to configure SLRB (Sidelink RB).
[0473] As an embodiment, the third message includes RRCReconfigurationSidelink.
[0474] As an embodiment, the third message includes RRCReconfigurationCompleteSidelink.
[0475] As an embodiment, the third message includes a partial field in RRCReconfigurationSidelink.
[0476] As an embodiment, the third message includes RRCReconfiguration.
[0477] As an embodiment, the third message includes SIB12.
[0478] As an embodiment, the third message includes SLRB-Config.
[0479] As an embodiment, the third message includes sl-PDCP-ConfigPC5.
[0480] As an embodiment, the third message includes sl-RLC-ConfigPC5.
[0481] As an embodiment, the third message includes sl-MAC-LogicalChannelConfigPC5.
[0482] As an embodiment, the third message includes PC5-S signaling.
[0483] As an embodiment, the third message includes SL-LogicalChannelConfigPC5.
[0484] As an embodiment, the third message includes SL-LogicalChannelConfig.
[0485] As an embodiment, the third message includes SL-LogicalChannelConfig-r16.
[0486] As an embodiment, the third message includes SL-LogicalChannelConfig-r17.
[0487] As an embodiment, the third message includes part of the fields in SL-LogicalChannelConfig.
[0488] As an embodiment, the third message includes sl-RLC-Config.
[0489] As an embodiment, the third message includes sl-RLC-Config-r16.
[0490] As an embodiment, the third message includes sl-RLC-Config-r17.
[0491] As an embodiment, the third message includes part of the fields in sl-RLC-Config.
[0492] As an embodiment, the third message includes sl-LogicalChannelGroup.
[0493] As an embodiment, the third message includes RRCConnectionReconfigurationSidelink.
[0494] As an embodiment, the third message includes RRCConnectionReconfiguration.
[0495] As an embodiment, the third message includes DIRECT LINK ESTABLISHMENT REQUEST.
[0496] As an embodiment, the third message includes DIRECT LINK ESTABLISHMENT ACCEPT.
[0497] As an embodiment, the third message includes a DIRECT LINK MODIFICATION REQUEST.
[0498] As an embodiment, the third message includes DIRECT LINK MODIFICATION ACCEPT.
[0499] As an embodiment, the third message includes a DIRECT LINK KEEPALIVE REQUEST.
[0500] As an embodiment, the third message includes a DIRECT LINK KEEPALIVE RESPONSE.
[0501] As an embodiment, the third message includes DISCOVERY_REQUEST.
[0502] As an embodiment, the third message includes DISCOVERY_RESPONSE.
[0503] As an embodiment, the third message includes a Direct Security Mode Command.
[0504] As an embodiment, the third message includes Direct Security Mode Complete.
[0505] As an embodiment, the reception of the third message is used to trigger the reconstruction of the first PDCP entity.
[0506] As an embodiment, the reconstruction of the first PDCP entity triggers the sending of the second message.
[0507] As an embodiment, the second message is used to indicate the release of the RLC entity associated with the first PDCP entity.
[0508] As an embodiment, the second message is used to indicate the establishment of a new RLC entity associated with the first PDCP entity.
[0509] As an embodiment, the second message indicates a target logical channel identity, and the MAC subheader of the MAC sub-PDU carrying the first PDCP PDU includes a first logical channel identity; the first logical channel identity is different from the target logical channel identity.
[0510] As an embodiment, the second message indicates a target logical channel identity, and the MAC subheader of the MAC sub-PDU carrying the first PDCP PDU includes a first logical channel identity; the first logical channel identity is the same as the target logical channel identity.
[0511] As an embodiment, the second message includes the identity of the first radio bearer.
[0512] As an embodiment, the second message includes the first link layer identity.
[0513] As an embodiment, the third message includes the identity of the first radio bearer.
[0514] Example 7
[0515] Embodiment 7 illustrates a schematic diagram of a PDCP PDU according to an embodiment of the present application, as shown in the attached Figure 7 shown.
[0516] As an embodiment, a PDCP PDU includes a header and data, wherein the data (Data) is a field of a PDCP PDU used to carry data (Data).
[0517] As an embodiment, a header of a PDCP PDU includes a first field.
[0518] As an embodiment, before the first field included in the header of a PDCP PDU, optionally, other bits exist;
[0519] As a sub-embodiment of the above embodiment, the other bits correspond to other fields.
[0520] As an embodiment, after the first field included in the header of a PDCP PDU, optionally, other bits exist.
[0521] As a sub-embodiment of the above embodiment, the other bits correspond to other fields.
[0522] As an embodiment, the first field includes 12 bits.
[0523] As an embodiment, the first field includes 18 bits.
[0524] As an embodiment, the length of the first field is configurable.
[0525] As an embodiment, the bits before the first field are higher order bits.
[0526] As an embodiment, the bits after the first field are lower-order bits.
[0527] As an example, Figure 7 The PDCP PDU in is applicable to DRB.
[0528] As an example, Figure 7 The header of the PDCP PDU also includes a D / C field, where the D / C field occupies 1 bit.
[0529] As an example, Figure 7 The PDCP PDU in is the PDU generated by the first PDCP entity.
[0530] As an embodiment, the first domain is a PDCP SN domain.
[0531] As an embodiment, the first message is used to indicate that the first field of the first PDCP PDU is set to a first initial value.
[0532] As an embodiment, the length of the first field is K bits, and the first message is used to indicate that the first field of the first PDCP PDU is set to the K lowest bits of a first initial value.
[0533] As a sub-embodiment of the above embodiment, the first PDCP PDU is the first PDCP PDU generated after the first PDCP entity is reestablished.
[0534] As a sub-embodiment of the above embodiment, the first PDCP PDU is the first data PDCP PDU generated after the first PDCP entity is reestablished.
[0535] As a sub-embodiment of the above embodiment, K is a positive integer.
[0536] As a sub-embodiment of the above embodiment, K is one of {1, 2, 3, 4, 12, 18}.
[0537] As a sub-embodiment of the above embodiment, the first message indicates that a first state variable is reset and its initial value is set to the first initial value, and the value of the first state variable is used to set the first domain.
[0538] As a sub-embodiment of the above embodiment, the first message indicates that the first state variable is reset and its initial value is set to the first initial value, that is, the value of the first state variable is set to the first domain.
[0539] As a sub-embodiment of the above embodiment, the first message indicates that the first state variable is reset and its initial value is set to the first initial value, and the K lowest bits of the first state variable are set to the first domain.
[0540] As a sub-embodiment of the above embodiment, the value of the first field of all data PDCP PDUs sent by the first PDCP entity after being reestablished is the same.
[0541] As a sub-embodiment of the above embodiment, the value of the first field of all data PDCP PDUs sent after the first PDCP entity is reestablished increases successively until the maximum value that can be identified by the first field starts again from 0.
[0542] As a sub-embodiment of the above embodiment, the value of the first field of all data PDCP PDUs sent after the first PDCP entity is reestablished increases successively until the maximum value that can be represented by the first field is reached and then starts again from the first initial value.
[0543] As an embodiment, the first domain includes a PDCP SN, and the first initial value is configurable.
[0544] As a sub-embodiment of the above embodiment, the first message is used to set a first state variable, and the first state variable is used to calculate the first initial value.
[0545] As a sub-embodiment of the above embodiment, the first initial value is not 0.
[0546] As a sub-embodiment of the above embodiment, the first initial value is a positive number.
[0547] As a sub-embodiment of the above embodiment, the first initial value is related to the COUNT value associated with the first PDCP PDU.
[0548] As a sub-embodiment of the above embodiment, the first initial value is related to a COUNT value associated with a PDCP SDU carried by the first PDCP PDU.
[0549] As a sub-embodiment of the above embodiment, the value of the first state variable is set to the first initial value.
[0550] As a sub-embodiment of the above embodiment, the sum of the value of the first state variable and an offset is set to the first initial value.
[0551] As a sub-embodiment of the above embodiment, the sum of the value of the first state variable and an offset is set to the first initial value.
[0552] As an embodiment, the first field includes at least one R, and each R occupies 1 bit.
[0553] As a sub-embodiment of the above embodiment, the first field of the first PDCP PDU indicates the number of times the first PDCP entity is reestablished.
[0554] As a sub-embodiment of the above embodiment, the first field of the first PDCP PDU is equal to the remainder obtained by taking the number of times the first PDCP entity is reconstructed modulo Q, where Q is 2 to the power of Q1, and Q1 is the number of R included in the first field.
[0555] As an embodiment, the header of the first PDCP PDU includes the first field, and the first field includes 1 or 2 or 3 bits.
[0556] As a sub-embodiment of the above embodiment, the first field of the first PDCP PDU indicates the number of times the first PDCP entity is reestablished.
[0557] As a sub-embodiment of the above embodiment, the first field of the first PDCP PDU is equal to the remainder obtained by taking the number of times the first PDCP entity is reconstructed modulo Q, where Q is 2 to the power of Q1, and Q1 is the number of bits included in the first field.
[0558] As an embodiment, the first message explicitly indicates the first initial value.
[0559] As an embodiment, the first message implicitly indicates the first initial value.
[0560] As an embodiment, one PDCP PDU corresponds to one PDCP SDU.
[0561] As an example, Figure 7 The format of the PDCP PDU in is applicable to the first PDCP PDU of the present application.
[0562] As an example, Figure 7 The format of the PDCP PDU in is applicable to the second PDCP PDU of the present application.
[0563] As an example, Figure 7 The format of the PDCP PDU in is applicable to the third PDCP PDU of the present application.
[0564] As an example, Figure 7 The PDCP PDU and the first domain in are applicable to the first PDCP PDU of the present application.
[0565] As an example, Figure 7 The first field of the PDCP PDU in the PDCP PDU occupies 1 bit, and the header of the PDCP PDU includes 2 R bits, wherein the attached Figure 7 The header of the PDCP PDU includes a 12-bit SN field.
[0566] As an example, Figure 7 The first field of the PDCP PDU in the PDCP PDU occupies 2 bits, and the header of the PDCP PDU includes 1 R bit, wherein the attached Figure 7 The header of the PDCP PDU includes a 12-bit SN field.
[0567] As an example, Figure 7 The first field of the PDCP PDU in the PDCP PDU occupies 3 bits, and the header of the PDCP PDU includes 0 R bits, wherein the attached Figure 7 The header of the PDCP PDU includes a 12-bit SN field.
[0568] As an example, Figure 7 The first field of the PDCP PDU in the PDCP PDU occupies 1 bit, and the header of the PDCP PDU includes 4 R bits, wherein the attached Figure 7 The header of the PDCP PDU includes an 18-bit SN field.
[0569] As an example, Figure 7 The first field of the PDCP PDU in the PDCP PDU occupies 2 bits, and the header of the PDCP PDU includes 3 R bits, wherein the attached Figure 7 The header of the PDCP PDU includes an 18-bit SN field.
[0570] As an example, Figure 7 The first field of the PDCP PDU in the PDCP PDU occupies 3 bits, and the header of the PDCP PDU includes 2 R bits, wherein the attached Figure 7 The header of the PDCP PDU includes an 18-bit SN field.
[0571] As an example, Figure 7 The first field of the PDCP PDU in the PDCP PDU occupies 4 bits, and the header of the PDCP PDU includes 1 R bit, wherein the attached Figure 7 The header of the PDCP PDU includes an 18-bit SN field.
[0572] As an example, Figure 7 The first field of the PDCP PDU in the PDCP PDU occupies 5 bits, and the header of the PDCP PDU includes 0 R bits, wherein the attached Figure 7 The header of the PDCP PDU includes an 18-bit SN field.
[0573] As an embodiment, the first field of the first PDCP PDU indicates the number of times the first PDCP entity is reestablished.
[0574] As an embodiment, the first field of the first PDCP PDU is equal to the remainder obtained by taking the number of times the first PDCP entity is reconstructed modulo Q, where Q is 2 to the power of Q1, and Q1 is the number of bits included in the first field.
[0575] As an embodiment, the first field is a portion of bits in the PDCP Data; as a sub-embodiment of this embodiment, the first field is the first B bytes in the Data of the PDCP PDU, where B is a positive integer, for example, B is equal to 1.
[0576] As an embodiment, the first field is a field carrying check bits in the PDCP PDU.
[0577] As a sub-embodiment of this embodiment, the check bit is used to check whether the first PDCP PDU is generated after the PDCP entity is re-established.
[0578] As a sub-embodiment of this embodiment, the check bit is used to check whether the first PDCP PDU is generated after the PDCP entity is reestablished for the Xth time, where X is a positive integer.
[0579] Example 8
[0580] Embodiment 8 illustrates a schematic diagram of a protocol stack of a layer 2 relay according to an embodiment of the present application, as shown in the attached Figure 8 Embodiment 8 is based on Embodiment 3 and shows a control plane protocol stack and interface related to a relay node.
[0581] In Example 8, NAS is the non-access layer, Uu-RRC is the RRC protocol of the Uu interface, Uu-PDCP is the PDCP entity of the Uu interface; Uu-RLC is the RLC entity of the Uu interface, Uu-MAC is the MAC entity of the Uu interface, and Uu-PHY is the physical layer entity of the Uu interface; PC5-RLC is the RLC entity of the PC5 interface; PC5-MAC is the MAC entity of the PC5 interface; PC5-PHY is the physical layer entity of the PC5 interface; Adaptation is the adaptation entity between the relay node and the network; N2 Stack is the protocol stack of the N2 interface, and the N2 interface is the interface between the gNB and the core network.
[0582] As an example, in the attached Figure 8 In the embodiment, the UE corresponds to the first node of the present application, the relay corresponds to the third node of the present application, and the gNB corresponds to the second node of the present application;
[0583] As a sub-embodiment of this embodiment, the first radio bearer is a radio bearer between the UE and the gNB; the first radio bearer corresponds to the first PDCP entity;
[0584] As a sub-embodiment of this embodiment, the first RLC bearer is an RLC bearer of a Uu interface, the first RLC bearer is an RLC bearer between the relay and the gNB; the first RLC bearer corresponds to the first RLC entity;
[0585] As a sub-embodiment of this embodiment, the SRB used to transmit the first message is an SRB between the UE and the gNB;
[0586] As a sub-embodiment of this embodiment, the generator of the first message is the gNB;
[0587] As a sub-embodiment of this embodiment, the generator of the first message is a core network to which the gNB is connected;
[0588] As a sub-embodiment of this embodiment, the generator of the first message is the relay;
[0589] As a sub-embodiment of this embodiment, the second message is sent using an SRB other than the SRB used to transmit the first signaling;
[0590] As a sub-embodiment of this embodiment, the receiver of the second message is different from the generator of the first message;
[0591] As a sub-embodiment of this embodiment, the recipient of the second message is a node capable of decoding the second message.
[0592] As an embodiment, the second message is attached by Figure 8 The PC5 interface is used for transmission.
[0593] As an embodiment, the second message is generated at the NAS layer or PC5-RRC layer of the UE.
[0594] As an embodiment, the first message is a NAS message.
[0595] As an embodiment, the first message is a Uu-RRC message.
[0596] As an embodiment, the first PDCP entity is attached Figure 8 Uu-PDCP in.
[0597] As an embodiment, the first RLC PDU is generated in the attached Figure 8 PC5-RLC of the UE.
[0598] As an embodiment, the second message is used to reestablish the PC5-RLC entity of the relay.
[0599] As an embodiment, the second message is used to reset the SN of the relayed PC5-RLC entity.
[0600] As an embodiment, the first message is not used to reset the sequence number of the PC5-RLC entity of the UE.
[0601] As an embodiment, the first message is used to reset the sequence number of the PC5-RLC entity of the UE.
[0602] As an embodiment, the Uu-RLC entity of the relay associated with the first PDCP entity is not reestablished.
[0603] As an embodiment, the re-establishment of the first PDCP entity does not trigger the re-establishment of the Uu-RLC entity associated with the first PDCP entity of the relay.
[0604] As an embodiment, the re-establishment of the first PDCP entity is not accompanied by the re-establishment of the Uu-RLC entity of the relay associated with the first PDCP entity.
[0605] Example 9
[0606] Embodiment 9 illustrates a schematic diagram of a first message according to an embodiment of the present application being used to set a first field of a first PDCP PDU, as shown in the attached Fig. 9 shown.
[0607] As an embodiment, the first message indicates a first initial value, and the initial value of the state variable TX_NEXT after the first PDCP entity is reconstructed is set to the first initial value.
[0608] As an embodiment, the value of the state variable TX_NEXT is set to the value of the first field of the first PDCP PDU.
[0609] As an embodiment, the first message indicates the reconstruction of the first PDCP entity, and the state variable TX_NEXT of the first PDCP entity after reconstruction is set to a first initial value, and the first initial value is FMC+2^L+X, where ^ is a power operation, L is the length of the first domain -1, and FMC indicates the first lost COUNT value.
[0610] As a sub-embodiment of the above embodiment, the FMC is indicated by the second report.
[0611] As a sub-embodiment of the above embodiment, the FMC is indicated by a PDCP status report received by the first PDCP entity.
[0612] As a sub-embodiment of the above embodiment, the parameter X is a positive integer.
[0613] As a sub-embodiment of the above embodiment, the parameter X is equal to 1.
[0614] As a sub-embodiment of the above embodiment, the parameter X is equal to -1.
[0615] As a sub-embodiment of the above embodiment, the parameter X is equal to 0.
[0616] As an embodiment, the first message is used to indicate a receiving window of a receiver of the first PDCP PDU.
[0617] As an embodiment, the first message is used to indicate the starting value of the receiving window of the receiver of the first PDCP PDU.
[0618] As an embodiment, the length of the receiving window of the receiver of the first PDCP PDU is fixed.
[0619] As an embodiment, the length of the receiving window of the receiver of the first PDCP PDU is equal to 2^(E-1), where ^ is a power operation and E is the length of the PDCP sequence number.
[0620] As a sub-embodiment of the above embodiment, the length of the PDCP sequence number is 12 bits or 18 bits.
[0621] As an embodiment, the first initial value is not within a receiving window before a receiver of the first PDCP PDU sends the first message.
[0622] As an embodiment, the first initial value is not within a receiving window before a receiver of the first PDCP PDU receives a feedback message of the first message.
[0623] As an embodiment, the value of the first domain determined by the first initial value is not within the receiving window of the first PDCP PDU receiver when sending the first message.
[0624] As an embodiment, the value of the first domain is not within the receiving window maintained by the receiver of the first PDCP PDU when sending the first message, which is used to indicate that the first PDCP PDU is generated after the first PDCP entity is rebuilt.
[0625] As an embodiment, the difference between the value of the first field of the first PDCP PDU and the value of the first field of the last PDCP PDU sent by the first PDCP entity before reconstruction is Y.
[0626] As a sub-embodiment of the above embodiment, the first PDCP PDU is the first PDCP PDU sent after the first PDCP entity is reestablished.
[0627] As a sub-embodiment of the above embodiment, the first PDCP PDU is the first data PDCP PDU sent after the first PDCP entity is reestablished.
[0628] As a sub-embodiment of the above embodiment, the last PDCP PDU sent by the first PDCP entity before re-establishment is a data PDCP PDU.
[0629] As a sub-embodiment of the above embodiment, the value of Y is a positive integer.
[0630] As a sub-embodiment of the above embodiment, the value of Y is greater than the size of the PDCP receiving window.
[0631] As a sub-embodiment of the above embodiment, the value of Y is equal to the size of the PDCP receiving window.
[0632] As a sub-embodiment of the above embodiment, the size of the PDCP receiving window is equal to 2^(E-1), where ^ is a power operation and E is the length of the PDCP sequence number.
[0633] As a sub-embodiment of the above embodiment, the value of Y being greater than the size of the PDCP receiving window is used to indicate that the first PDCP PDU is generated after the first PDCP entity is reestablished.
[0634] As a sub-embodiment of the above embodiment, the value of Y is equal to the size of the PDCP receiving window, which is used to indicate that the first PDCP PDU is generated after the first PDCP entity is reestablished.
[0635] As an embodiment, the initial value of the state variable TX_NEXT of the first PDCP entity after the first PDCP entity is reset is related to the value of TX_NEXT before the first PDCP entity is reestablished.
[0636] As an embodiment, the first message is used to indicate the reconstruction of the first PDCP entity, and the reconstruction of the first PDCP entity includes resetting the state variable of the first PDCP entity and setting the state variable of the first PDCP entity to an initial value; the initial value of the state variable TX_NEXT of the first PDCP entity is equal to MOD(T+Z, 2^L); wherein MOD is a modulo operation, T is the TX_NEXT value of the first PDCP entity before being reconstructed, L is the length of the sequence number of the first PDCP PDU, and ^ is a power operation.
[0637] As a sub-embodiment of the above embodiment, Z is an integer.
[0638] As a sub-embodiment of the above embodiment, Z is equal to 2^(L-1).
[0639] As a sub-embodiment of the above embodiment, the value of L is 12 or 18.
[0640] As a sub-embodiment of the above embodiment, Z is equal to 2^(L-1)-1.
[0641] As a sub-embodiment of the above embodiment, Z is equal to 2^(L-1)+1.
[0642] As an embodiment, the receiving window of the PDCP is determined by the receiving end according to predefined parameters and parameters configured by the serving cell when the PDCP entity is established.
[0643] Example 10
[0644] Embodiment 10 illustrates a schematic diagram in which the first message according to an embodiment of the present application is not used to reset the first RLC SN, as shown in the attached figure. Fig.10 shown.
[0645] As an embodiment, the first message is not used to reestablish the RLC entity corresponding to the first RLC SN.
[0646] As an embodiment, the first RLC SN is equal to the SN+1 of the most recent RLC PDU before the RLC PDU corresponding to the first RLC SN is sent.
[0647] As an embodiment, the first RLC SN and the SN of the most recent RLC PDU before the RLC PDU corresponding to the first RLC SN is sent remain continuous.
[0648] As an embodiment, the state variables of the RLC entity of the PC5 interface associated with the first PDCP entity remain continuous before and after the first PDCP entity is reestablished.
[0649] As a sub-embodiment of the above embodiment, the RLC entity of the PC5 interface associated with the first PDCP entity is used to send the PDCP PDU generated by the first PDCP entity.
[0650] As an embodiment, the state variables of the RLC entity of the Uu interface associated with the first PDCP entity remain continuous before and after the first PDCP entity is reestablished.
[0651] As a sub-embodiment of the above embodiment, the RLC entity of the PC5 interface associated with the first PDCP entity is used to send the PDCP PDU generated by the first PDCP entity.
[0652] As an embodiment, the SN of the RLC PDU sent by the RLC entity of the PC5 interface associated with the first PDCP entity remains continuous before and after the first PDCP entity is reestablished.
[0653] As a sub-embodiment of the above embodiment, the RLC entity of the PC5 interface associated with the first PDCP entity is used to send the PDCP PDU generated by the first PDCP entity.
[0654] As an embodiment, the SN of the RLC PDU sent by the RLC entity of the Uu interface associated with the first PDCP entity remains continuous before and after the first PDCP entity is reestablished.
[0655] As a sub-embodiment of the above embodiment, the RLC entity of the PC5 interface associated with the first PDCP entity is used to send the PDCP PDU generated by the first PDCP entity.
[0656] Embodiment 11
[0657] Embodiment 11 illustrates a schematic diagram of a second sequence number being used to determine a fourth sequence number according to an embodiment of the present invention, as shown in the attached figure. Fig.11 shown.
[0658] As an embodiment, the first message is used to indicate the first initial value.
[0659] As an embodiment, the value of the fourth serial number is equal to the sum of the second serial number and the first initial value.
[0660] As an embodiment, the value of the fourth serial number is equal to the sum of the values of the second serial number and the K lowest bits of the first initial value.
[0661] As an embodiment, the first report indicates that the second PDCP SDU has not been received by indicating a fourth sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; the second sequence number is different from the fourth sequence number, and the second sequence number is used to determine the fourth sequence number; the behavior of sending the first report is performed after the behavior rebuilds the first PDCP entity.
[0662] As an embodiment, among all PDCP SDUs to which PDCP sequence numbers have been assigned before the first PDCP entity is rebuilt but whose corresponding PDCP PDUs have not yet been submitted to lower layer transmission, the second PDCP SDU is the Mth one arranged in the order of the assigned PDCP SN, and the value of the fourth sequence number is M+the second sequence number+the first initial value.
[0663] Example 12
[0664] Embodiment 12 illustrates a schematic diagram of a first COUNT value being used to determine a first initial value according to an embodiment of the present invention, as shown in the attached figure. Fig.12 shown.
[0665] As an embodiment, the second report is used to indicate a first COUNT value; the first COUNT value is the first lost COUNT value; the first COUNT value is used to determine a first initial value; the initial value of at least one state variable of the first PDCP entity is set to the first initial value after the behavior reconstructs the first PDCP entity, and the first initial value is not 0.
[0666] As an embodiment, the first COUNT value is determined as the first initial value.
[0667] As an embodiment, the sum of the first COUNT value and the first offset is determined as the first initial value; wherein the first offset is an integer.
[0668] As an embodiment, the sum of the first COUNT value and 1 is determined as the first initial value.
[0669] As an embodiment, the sum of the first COUNT value and -1 is determined as the first initial value.
[0670] As an embodiment, the FMC field of the second report indicates the first COUNT value.
[0671] As an embodiment, the K1 least significant bits of the FMC field of the second report are determined as the first initial value.
[0672] As an embodiment, the sum of the value of the K1 least significant bits of the FMC field of the second report and a first offset is determined as the first initial value; wherein the first offset is an integer.
[0673] As an embodiment, the sum of the value of the K1 least significant bits of the FMC field of the second report and 1 is determined as the first initial value.
[0674] As an embodiment, the sum of K1 least significant bits of the FMC field of the second report and -1 is determined as the first initial value.
[0675] As an embodiment, K1 is a positive integer.
[0676] As an embodiment, K1 is fixed.
[0677] As an embodiment, K1 is configurable.
[0678] As an embodiment, K1 is equal to 12 or 18.
[0679] As an embodiment, K1 is equal to one of {1, 2, 3, 5}.
[0680] As an embodiment, the K1 is equal to the length of the SN of the first PDCP PDU.
[0681] As an embodiment, the K1 is equal to the length of the first field of the first PDCP PDU.
[0682] As an embodiment, the first offset is equal to the length of the receiving window of the PDCP entity.
[0683] Embodiment 13
[0684] Embodiment 13 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Fig.13 As shown in the attached Fig.13 In the embodiment 13, the processing device 1300 in the first node includes a first receiver 1301 and a first transmitter 1302.
[0685] The first receiver 1301 receives a first message; in response to receiving the first message, reestablishes a first PDCP entity;
[0686] A first transmitter 1302 sends a first PDCP PDU, where the first PDCP PDU is generated by the first PDCP entity;
[0687] The first PDCP PDU includes a first field and data, the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
[0688] As an embodiment, the behavior of sending a first PDCP PDU includes: sending a first RLC PDU, the first RLC PDU includes the first PDCP PDU, the first RLC PDU includes a first RLC SN;
[0689] The first message is not used to reset the first RLC SN.
[0690] As an embodiment, the first transmitter 1302 sends a second message;
[0691] The behavior of reconstructing the first PDCP entity includes: reconstructing a first RLC entity, the first RLC entity is associated with the first PDCP entity; and the second message indicates that the first RLC entity is reconstructed.
[0692] As an embodiment, the first transmitter 1302 sends a first report, wherein the first report indicates that the second PDCP SDU has not been received by indicating a second sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; and the behavior of sending the first report is executed after the behavior rebuilds the first PDCP entity.
[0693] As an embodiment, the first transmitter 1302 sends a first report, wherein the first report indicates that the second PDCP SDU has not been received by indicating a fourth sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; the second sequence number is different from the fourth sequence number, and the second sequence number is used to determine the fourth sequence number; the behavior of sending the first report is executed after the behavior rebuilds the first PDCP entity.
[0694] As an embodiment, the first receiver 1301 receives a second report, the second report is used to indicate a first COUNT value; the first COUNT value is a first lost COUNT value; the first COUNT value is used to determine a first initial value; the initial value of at least one state variable of the first PDCP entity is set to the first initial value after the behavior reestablishes the first PDCP entity, and the first initial value is non-0.
[0695] As an embodiment, the first message is used to indicate a first key, and the first PDCP entity uses the first key to encrypt the data included in the first PDCP PDU.
[0696] As an embodiment, the first node is a user equipment (UE).
[0697] As an embodiment, the first node is a terminal supporting a large delay difference.
[0698] As an embodiment, the first node is a terminal supporting NTN.
[0699] As an embodiment, the first node is an aircraft.
[0700] As an embodiment, the first node is a vehicle-mounted terminal.
[0701] As an embodiment, the first node is a relay.
[0702] As an embodiment, the first node is a vessel.
[0703] As an embodiment, the first node is an Internet of Things terminal.
[0704] As an embodiment, the first node is an industrial Internet of Things terminal.
[0705] As an embodiment, the first node is a device supporting low-latency and high-reliability transmission.
[0706] As an embodiment, the first receiver 1301 includes at least one of the antenna 452, receiver 454, receiving processor 456, multi-antenna receiving processor 458, controller / processor 459, memory 460, or data source 467 in Example 4.
[0707] As an embodiment, the first transmitter 1302 includes at least one of the antenna 452, transmitter 454, transmit processor 468, multi-antenna transmit processor 457, controller / processor 459, memory 460, or data source 467 in Embodiment 4.
[0708] Embodiment 14
[0709] Embodiment 14 illustrates a structural block diagram of a processing device used in a second node according to an embodiment of the present application; Fig.14 As shown in the attached Fig.14 In the embodiment 14, the processing device 1400 in the second node includes a second receiver 1402 and a second transmitter 1401.
[0710] The second transmitter 1401 sends a first message; the first message is used to trigger the reestablishment of the first PDCP entity;
[0711] A second receiver 1402 receives a first PDCP PDU, where the first PDCP PDU is generated by the first PDCP entity;
[0712] The first PDCP PDU includes a first field and data, the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
[0713] As an embodiment, the behavior of receiving the first PDCP PDU includes:
[0714] receiving a first RLC PDU, the first RLC PDU including the first PDCP PDU, the first RLC PDU including a first RLC SN;
[0715] The first message is not used to reset the first RLC SN.
[0716] As an embodiment, the second receiver 1402 receives a first report, wherein the first report indicates that the second PDCP SDU has not been received by indicating a second sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; and the behavior of sending the first report is executed after the behavior rebuilds the first PDCP entity.
[0717] As an embodiment, the second receiver 1402 receives a first report, wherein the first report indicates that the second PDCP SDU has not been received by indicating a fourth sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; the second sequence number is different from the fourth sequence number, and the second sequence number is used to determine the fourth sequence number; the behavior of sending the first report is executed after the behavior rebuilds the first PDCP entity.
[0718] As an embodiment, the second transmitter 1401 sends a second report, the second report is used to indicate a first COUNT value; the first COUNT value is the first lost COUNT value; the first COUNT value is used to determine a first initial value; the initial value of at least one state variable of the first PDCP entity is set to the first initial value after the behavior reestablishes the first PDCP entity, and the first initial value is non-0.
[0719] As an embodiment, the first message is used to indicate a first key, and the first PDCP entity uses the first key to encrypt the data included in the first PDCP PDU.
[0720] As an embodiment, the second node is a user equipment (UE).
[0721] As an embodiment, the second node is a terminal supporting a large delay difference.
[0722] As an embodiment, the second node is a terminal supporting NTN.
[0723] As an embodiment, the second node is an aircraft.
[0724] As an embodiment, the second node is a vehicle-mounted terminal.
[0725] As an embodiment, the second node is a relay.
[0726] As an embodiment, the second node is a vessel.
[0727] As an embodiment, the second node is an Internet of Things terminal.
[0728] As an embodiment, the second node is an industrial Internet of Things terminal.
[0729] As an embodiment, the second node is a device supporting low-latency and high-reliability transmission.
[0730] As an embodiment, the second transmitter 1401 includes at least one of the antenna 420, transmitter 418, transmit processor 416, multi-antenna transmit processor 471, controller / processor 475, and memory 476 in Embodiment 4.
[0731] As an embodiment, the second receiver 1402 includes at least one of the antenna 420, the receiver 418, the receiving processor 470, the multi-antenna receiving processor 472, the controller / processor 475, and the memory 476 in Embodiment 4.
[0732] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The user equipment, terminal and UE in the present application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication, machine type communication) terminals, eMTC (enhanced MTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers, satellite communication equipment, ship communication equipment, NTN user equipment and other wireless communication equipment. The base stations or system equipment in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B) NR Node B, TRP (Transmitter Receiver Point), NTN base stations, satellite equipment, flight platform equipment and other wireless communication equipment.
[0733] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims
1. A first node for wireless communication, wherein: include: A first receiver receives a first message; In response to receiving the first message, reestablishing a first PDCP entity; A first transmitter sends a first PDCP PDU, where the first PDCP PDU is generated by the first PDCP entity; The first PDCP PDU includes a first field and data, and the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
2. The first node according to claim 1, characterized in that: The behavior of sending a first PDCP PDU includes: Sending a first RLC PDU, where the first RLC PDU includes the first PDCP PDU, and the first RLC PDU includes a first RLCSN; The first message is not used to reset the first RLCSN.
3. The first node according to claim 1, characterized in that: include: The first transmitter sends a second message; The behavior of reconstructing the first PDCP entity includes: reconstructing a first RLC entity, the first RLC entity is associated with the first PDCP entity; and the second message indicates that the first RLC entity is reconstructed.
4. The first node according to any one of claims 1 to 3, characterized in that: include: The first transmitter sends a first report, wherein the first report indicates that the second PDCP SDU has not been received by indicating a second sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; and the behavior of sending the first report is executed after the behavior rebuilds the first PDCP entity.
5. The first node according to any one of claims 1 to 3, characterized in that: include: The first transmitter sends a first report, wherein the first report indicates that the second PDCP SDU has not been received by indicating a fourth sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; the second sequence number is different from the fourth sequence number, and the second sequence number is used to determine the fourth sequence number; the behavior of sending the first report is executed after the behavior rebuilds the first PDCP entity.
6. The first node according to any one of claims 1 to 5, characterized in that: include: The first receiver receives a second report, wherein the second report is used to indicate a first COUNT value; the first COUNT value is the first lost COUNT value; the first COUNT value is used to determine a first initial value; the initial value of at least one state variable of the first PDCP entity is set to the first initial value after the behavior reconstructs the first PDCP entity, and the first initial value is not 0.
7. The first node according to any one of claims 1 to 6, characterized in that: include: The first message is used to indicate a first key, and the first PDCP entity uses the first key to encrypt the data included in the first PDCP PDU.
8. The first node according to any one of claims 1 to 7, characterized in that: The first domain is a PDCP SN domain.
9. The first node according to any one of claims 1 to 7, characterized in that: The first field is a field that carries the parity bits in the PDCP PDU.
10. A second node for wireless communication, wherein: include: A second transmitter sends a first message; The first message is used to trigger the reestablishment of the first PDCP entity; A second receiver, receiving a first PDCP PDU, where the first PDCP PDU is generated by the first PDCP entity; The first PDCP PDU includes a first field and data, and the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
11. The second node according to claim 10, characterized in that: The behavior of receiving a first PDCP PDU includes: receiving a first RLC PDU, the first RLC PDU including the first PDCP PDU, the first RLC PDU including a first RLCSN; The first message is not used to reset the first RLCSN.
12. The second node according to claim 10 or 11, characterized in that: The second receiver receives a first report, wherein the first report indicates that the second PDCP SDU has not been received by indicating a second sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; and the behavior of sending the first report is executed after the behavior rebuilds the first PDCP entity.
13. The second node according to claim 10 or 11, characterized in that: The second receiver receives a first report, wherein the first report indicates that the second PDCP SDU has not been received by indicating a fourth sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is rebuilt is the second sequence number; the second sequence number is different from the fourth sequence number, and the second sequence number is used to determine the fourth sequence number; the behavior of sending the first report is executed after the behavior rebuilds the first PDCP entity.
14. The second node according to any one of claims 10 to 13, characterized in that: The second transmitter sends a second report, wherein the second report is used to indicate a first COUNT value; the first COUNT value is the first lost COUNT value; the first COUNT value is used to determine a first initial value; the initial value of at least one state variable of the first PDCP entity is set to the first initial value after the behavior reconstructs the first PDCP entity, and the first initial value is not 0.
15. The second node according to any one of claims 10 to 14, characterized in that: The first message is used to indicate a first key, and the first PDCP entity uses the first key to encrypt the data included in the first PDCP PDU.
16. A method in a first node for wireless communication, wherein: include: receiving a first message; In response to receiving the first message, reestablishing a first PDCP entity; Sending a first PDCP PDU, where the first PDCP PDU is generated by the first PDCP entity; The first PDCP PDU includes a first field and data, and the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
17. The method in the first node according to claim 16, characterized in that: The behavior of sending a first PDCP PDU includes: sending a first RLC PDU, the first RLC PDU includes the first PDCP PDU, the first RLC PDU includes a first RLCSN; wherein the first message is not used to reset the first RLCSN.
18. The method in the first node according to claim 16 or 17, characterized in that: sending a second message; The behavior of reconstructing the first PDCP entity includes: reconstructing a first RLC entity, the first RLC entity is associated with the first PDCP entity; and the second message indicates that the first RLC entity is reconstructed.
19. The method in the first node according to any one of claims 16 to 18, characterized in that: Sending a first report, wherein the first report indicates that a second PDCP SDU has not been received by indicating a second sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is reestablished is the second sequence number; the act of sending the first report is executed after the act of reestablishing the first PDCP entity.
20. The method in the first node according to any one of claims 16 to 18, characterized in that: Sending a first report, wherein the first report indicates that a second PDCP SDU has not been received by indicating a fourth sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is reestablished is the second sequence number; the second sequence number is different from the fourth sequence number, and the second sequence number is used to determine the fourth sequence number; the act of sending the first report is performed after the act of reestablishing the first PDCP entity.
21. The method in the first node according to any one of claims 16 to 20, characterized in that: Receive a second report, wherein the second report is used to indicate a first COUNT value; the first COUNT value is the first lost COUNT value; the first COUNT value is used to determine a first initial value; the initial value of at least one state variable of the first PDCP entity is set to the first initial value after the behavior reconstructs the first PDCP entity, and the first initial value is not 0.
22. The method in the first node according to any one of claims 16 to 21, characterized in that: The first message is used to indicate a first key, and the first PDCP entity uses the first key to encrypt the data included in the first PDCP PDU.
23. The method in the first node according to any one of claims 16 to 22, characterized in that: The first domain is a PDCP SN domain.
24. The method in the first node according to any one of claims 16 to 22, characterized in that: The first field is a field that carries the parity bits in the PDCP PDU.
25. A method in a second node for wireless communication, wherein: include: Sending a first message; The first message is used to trigger the reestablishment of the first PDCP entity; receiving a first PDCP PDU, where the first PDCP PDU is generated by the first PDCP entity; The first PDCP PDU includes a first field and data, and the first message is used to set the first field of the first PDCP PDU; the first field of the first PDCP PDU is used to indicate that the first PDCP PDU is generated after the reconstruction of the first PDCP entity.
26. The method in the second node according to claim 25, characterized in that: The behavior of receiving a first PDCP PDU includes: receiving a first RLC PDU, the first RLC PDU including the first PDCP PDU, the first RLC PDU including a first RLCSN; The first message is not used to reset the first RLCSN.
27. The method in the second node according to claim 25 or 26, characterized in that: Receive a first report, wherein the first report indicates that a second PDCP SDU has not been received by indicating a second sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is reestablished is the second sequence number; the behavior of sending the first report is performed after the behavior reestablishes the first PDCP entity.
28. The method in the second node according to claim 25 or 26, characterized in that: Receive a first report, wherein the first report indicates that a second PDCP SDU has not been received by indicating a fourth sequence number; the PDCP sequence number assigned to the second PDCP SDU before the first PDCP entity is reestablished is a second sequence number; the second sequence number is different from the fourth sequence number, and the second sequence number is used to determine the fourth sequence number; the act of sending the first report is performed after the act reestablishes the first PDCP entity.
29. The method in the second node according to any one of claims 25 to 28, characterized in that: Sending a second report, wherein the second report is used to indicate a first COUNT value; the first COUNT value is the first lost COUNT value; the first COUNT value is used to determine a first initial value; the initial value of at least one state variable of the first PDCP entity is set to the first initial value after the behavior reconstructs the first PDCP entity, and the first initial value is not 0.
30. The method in the second node according to any one of claims 25 to 29, characterized in that: The first message is used to indicate a first key, and the first PDCP entity uses the first key to encrypt the data included in the first PDCP PDU.
