CN114765803A

CN114765803A - Method and equipment used for wireless communication

Info

Publication number: CN114765803A
Application number: CN202110028262.9A
Authority: CN
Inventors: 陈宇; 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2021-01-11
Filing date: 2021-01-11
Publication date: 2022-07-19

Abstract

A method and apparatus used for wireless communication includes receiving a first parameter; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for the PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for bearing a first service; the first traffic is non-unicast traffic; receiving a first set of data and a first set of sequence numbers; the first set of data is used to generate PDCP SDUs for the first PDCP entity; receiving a second message; in response to receiving the second message, determining a second set of data and sending a second set of sequence numbers; the method and the device help to avoid confusion and inconsistency by receiving the first parameter determination.

Description

Method and equipment used for wireless communication

Technical Field

The present application relates to a transmission method and apparatus in a wireless communication system, and more particularly, to a method for improving efficiency and reducing redundancy in connection with header compression in wireless communication.

Background

In the future, the application scenes of the wireless communication system are more and more diversified, and different application scenes put different performance requirements on the system. In order to meet different performance requirements of multiple application scenarios, research on New Radio interface (NR) technology (or Fifth Generation, 5G) is decided on 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #72 bunions, and Work on NR is started on WI (Work Item) that has passed NR on 3GPP RAN #75 bunions.

In communication, both LTE (Long Term Evolution) and 5G NR relate to accurate reception of reliable information, optimized energy efficiency ratio, determination of information validity, flexible resource allocation, the scalable system structure, high-efficiency non-access stratum information processing, low service interruption and disconnection rate, for low power consumption support, which is for normal communication of base stations and user equipments, for reasonable scheduling of resources, the method has important significance for balancing system load, can be said to be high throughput, meets Communication requirements of various services, improves spectrum utilization rate, and improves service quality, and is essential for both enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communication (URLLC), and enhanced Machine Type Communication (eMTC). Meanwhile, in IIoT (Industrial Internet of Things), in V2X (Vehicular to X), in ProSe (near field communication), in Device to Device communication (Device to Device), in unlicensed spectrum communication, in user communication quality monitoring, in Network planning optimization, in NTN (Non terrestrial Network, Non-terrestrial Network communication), in TN (terrestrial Network, terrestrial Network communication), in a Dual connectivity (Dual connectivity) system, in a system using a Sidelink (Sidelink), in a mixture of the above various communication modes, in radio resource management and codebook selection of multiple antennas, in signaling design, neighborhood management, traffic management, there are wide demands in beamforming, transmission modes of information are classified into broadcast and multicast, and these are indispensable unicast and multicast 5G systems, as they are very helpful in meeting the above needs. In order to increase the coverage of the network and improve the reliability of the system, the information can also be forwarded through relays.

With the continuous increase of the scenes and the complexity of the system, higher requirements are put forward on the reduction of the interruption rate, the reduction of the time delay, the enhancement of the reliability, the enhancement of the stability of the system, the flexibility of the service and the saving of the power, and meanwhile, the compatibility among different versions of different systems needs to be considered when the system is designed.

Disclosure of Invention

In a communication network supporting handover, when handover (handover) is performed, data forwarding (data forwarding) is performed to maintain data continuity, and the data forwarding operation occurs between two nodes of RAN, for example, between a Source Cell (Source Cell) and a destination Cell (Target Cell). For example, for downlink, the data forward mainly refers to data that is not acknowledged and/or sent out, so that the destination cell can continue the original transmission without causing interruption of data transmission and data loss; meanwhile, when the handover is finished, a path (path) from the core network to the source cell for the relevant session is switched (switching) to the destination cell, so that the whole handover process is completed, and the destination cell can continue to transmit. When the UE is handed over to the destination cell, its PDCP protocol can help the UE avoid data duplication (duplication visibility), and can also determine which data has not been received, which all depend on the PDCP sequence number. For unicast service, there is essentially only one path (path) from the core network to the RAN, and although data forwarding and other processing occur, each piece of data is independent, i.e. either in the source cell or the destination cell, as a result, the sequence number of the PDCP is not confused, because the destination cell can arrange the sequence number according to the transmission condition of the source cell. For multicast broadcast services, however, both the source cell and the destination cell may be receiving the same service, both may have established a path or interface or bearer or session or tunnel with the core network to receive the same service at the same time, the transmission of the broadcast-multicast service may thus be performed simultaneously, and transmitted simultaneously, in different cells, when a UE is traveling from the source cell to the destination cell, if the destination cell has started to transmit, it is impossible for the destination cell to re-sequence the sequence number of the PDCP for a single user, since this would have an impact on other users receiving the service, the destination cell needs to associate data that is not received by the handed over UE into its PDCP sequence number, rather than to re-arrange, but if the associated PDCP sequence number is incorrect, it may cause interruption of data received by the UE or repetition or confusion that is difficult to detect, thereby affecting service reception. Since the broadcast multicast service configuration is generally relatively independent in different cells, especially when parameters of RAN are involved, there are many options for the length of the PDCP sequence number of different cells, and if the length settings of the sequence numbers of two cells are different, the sequence numbers may be confused, or more complicated sequence number conversion operation is required and may affect the currently receiving user.

In view of the above, the present application provides a solution.

It should be noted that, in the case of no conflict, the embodiments and features in the embodiments in any node of the present application may be applied to any other node. The embodiments and features of the embodiments of the present application may be combined with each other arbitrarily without conflict.

The application discloses a method in a first node used for wireless communication, comprising:

receiving a first parameter; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by a first PDCP entity for a PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for bearing a first service; the first traffic is non-unicast traffic;

receiving a first set of data and a first set of sequence numbers; the first set of data is used to generate PDCP SDUs for the first PDCP entity;

receiving a second message;

in response to receiving the second message, determining a second set of data and sending a second set of sequence numbers;

wherein the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the first sequence number length; the data forward direction of the handover includes only the second set of data; the first parameter and the first set of data are sent by the core network.

As an embodiment, the problem to be solved by the present application includes: when Broadcast (Broadcast) and/or Multicast (Multicast/group pcast) services are transmitted, the PDCP sequence numbers of different cells may have different lengths, which may cause a risk to service continuity. The method and the device indicate the length of the unified PDCP sequence number through the first parameter, thereby solving the problems.

As an example, the benefits of the above method include: different cells in a service area of a broadcast multicast service have PDCP sequence numbers with the same length, thereby being very helpful for ensuring the continuity of the service and reducing the implementation complexity.

In particular, according to an aspect of the present application, a first GTP-PDU is received; the first GTP-PDU comprises first data, the first data belonging to the first set of data; the header of the first GTP-PDU comprises a first domain and a second domain; the first field is used to indicate a sequence number of the first GTP-PDU, the first field and the second field being used together to generate a sequence number of a first PDCP PDU; the first PDCP PDU is generated by the first PDCP entity.

Specifically, according to an aspect of the present application, the second message includes data forward information;

performing data forward on the second data set through a GTP tunnel indicated by the data forward information included in the second message;

whether the second message includes the data forward information is related to whether a sender of the second message establishes a first interface for transmitting the first service; the first interface is an interface between a sender of the second message and a core network.

Specifically, according to an aspect of the present application, the second set of sequence numbers includes a first subset and a second subset; the first subset and the second subset are both non-empty subsets; the sequence numbers in the first subset are PDCP sequence numbers; the sequence numbers in the second subset include a GTP-U sequence number.

In particular, according to an aspect of the present application, the second message includes a first specific sequence number, which is used to determine the second set of sequence numbers.

Specifically, according to one aspect of the present application, a first message is sent; the second message is used for feeding back the first message.

In particular, according to an aspect of the present application, the first message comprises a first identity; the first identity is an identity associated with the first service, the first identity being used by a sender of the second message to determine whether data forwarding is required.

Specifically, according to an aspect of the present application, the first node is a user equipment.

Specifically, according to an aspect of the present application, the first node is an internet of things terminal.

Specifically, according to an aspect of the present application, the first node is a relay.

Specifically, according to an aspect of the present application, the first node is a vehicle-mounted terminal.

In particular, according to one aspect of the application, the first node is an aircraft.

Specifically, according to an aspect of the present application, the first node is a base station.

In particular, according to an aspect of the application, the first node is a cell or a group of cells.

In particular, according to an aspect of the application, the first node is a gateway.

In particular, according to an aspect of the present application, the first node is an access point.

The application discloses a method in a second node used for wireless communication, comprising:

sending a second message; the second message is used to trigger a recipient of the second message to send a second set of sequence numbers;

wherein a recipient of the second message receives a first set of data, a first parameter, and a first set of sequence numbers; the first set of data is used to generate PDCP SDUs for a first PDCP entity; the first parameter is used for indicating a first sequence number length, and the length of the sequence number allocated by the first PDCP entity for the PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for carrying a first service; the first traffic is non-unicast traffic; the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the first sequence number length; the data forward of the handover comprises only the second set of data; the first parameter and the first set of data and the first set of sequence numbers are sent by a core network;

in particular, according to an aspect of the present application, a second GTP-PDU is received; the second GTP-PDU comprises first data, the first data belonging to the first set of data; the header of the second GTP-PDU comprises a first field and a second field; the first field is used to indicate a sequence number of the second GTP-PDU, the first field and the second field are used together to generate a sequence number of a second PDCP PDU; the second PDCP PDU is generated by a second PDCP entity.

In particular, according to an aspect of the application, the second message comprises a first specific sequence number, which is used to determine the second set of sequence numbers.

Specifically, according to one aspect of the present application, a first message is received; the second message is used for feeding back the first message.

In particular, according to an aspect of the present application, the first message comprises a first identity; the first identity is an identity related to the first service, the first identity being used to determine whether data forwarding is required.

Specifically, according to an aspect of the present application, the second message includes data forward information; receiving the second set of sequence numbers.

receiving the second data set through a GTP tunnel indicated by data forward information included in the second message;

whether the second message includes the data forward information is related to whether the second node establishes a first interface for transmitting the first service; the first interface is an interface between the second node and a core network.

In particular, according to an aspect of the present application, the first node is a gateway.

The application discloses a first node for wireless communication, comprising:

a first receiver for receiving a first parameter, a second message, a first set of data and a first set of sequence numbers, the first set of data being used for generating PDCP SDUs of a first PDCP entity; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for a PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for bearing a first service; the first traffic is non-unicast traffic;

a first transmitter, responsive to receiving the second message, for determining a second set of data and transmitting a second set of sequence numbers;

wherein the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the first sequence number length; the data forward of the handover comprises only the second set of data; the first parameter and the first set of data are sent by the core network.

The application discloses a second node for wireless communication, comprising:

a second transmitter for transmitting a second message; the second message is used to trigger a recipient of the second message to send a second set of sequence numbers;

wherein a recipient of the second message receives a first set of data, a first parameter, and a first set of sequence numbers; the first set of data is used to generate PDCP SDUs for a first PDCP entity; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for a PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for carrying a first service; the first traffic is non-unicast traffic; the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the first sequence number length; the data forward direction of the handover includes only the second set of data; the first parameter and the first set of data and the first set of sequence numbers are transmitted by a core network.

As an example, compared with the conventional scheme, the method has the following advantages:

firstly, the method provided by the application can ensure that the sequence numbers of the PDCP entities of different cells transmitting the same broadcast multicast service or the sequence numbers carried by the generated PDCP PDUs are the same in length, which is beneficial to ensuring the continuity of the service when a user moves, avoiding the repetition of data and eliminating possible confusion.

Furthermore, the method provided by the application can ensure that the PDCP sequence numbers allocated to the same data by different cells are the same, which is very useful for avoiding the confusion of the sequence numbers and ensuring the continuity of the service.

Further, the method provided by the application carries/associates/assigns a serial number to all data forwarding related data, that is, data forwarding is not performed on data without serial numbers, which can ensure that a destination cell can identify and match data from data forwarding, and compares the data with locally received data through the serial numbers, thereby avoiding duplication and confusion.

Further, the method provided by the application only needs to notify the sequence number to the destination cell by the source cell and does not need to forward data during switching under certain conditions, so that the problems of chaos/data repetition/SN circulation and the like caused by delay of a data forwarding flow or message can be avoided, and the system is more efficient and reliable.

Further, the method provided by the application can determine whether data forwarding is needed to be received according to different situations, and in some situations, for example, if the service IDs are the same, but the contents are different, data forwarding is not needed, so that the system is faster and more efficient.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof with reference to the accompanying drawings in which:

fig. 1 shows a flow diagram of receiving a first parameter, a second message, a first set of data and a first set of sequence numbers, determining a second set of data, and sending the second set of sequence numbers according to one embodiment of the application;

FIG. 2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

figure 3 shows a schematic diagram of an embodiment of a radio protocol architecture for the user plane and the control plane according to an embodiment of the present application;

fig. 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the application;

FIG. 5 shows a flow diagram of transmission of a wireless signal according to one embodiment of the present application;

FIG. 6 is a diagram illustrating a PDCP PDU according to an embodiment of the present application;

FIG. 7a shows a schematic diagram of a GTP-U header according to one embodiment of the application;

figure 7b shows a schematic diagram of GTP-U extension according to one embodiment of the present application;

figure 7c shows a schematic diagram of GTP-U extension according to one embodiment of the present application;

FIG. 8 shows a schematic diagram of a first set of sequence numbers being used to generate a second set of sequence numbers according to an embodiment of the present application;

FIG. 9 illustrates a diagram of a first specific sequence number being used to determine a second set of sequence numbers according to one embodiment of the present application;

FIG. 10 shows a schematic diagram of a first identity being used by a sender of a second message to determine whether data forward is required according to one embodiment of the present application;

figure 11 illustrates a schematic diagram of a processing apparatus for use in a first node according to one embodiment of the present application;

fig. 12 illustrates a schematic diagram for a processing arrangement in a second node according to an embodiment of the application.

Detailed Description

The technical solutions of the present application will be further described in detail with reference to the accompanying drawings, and it should be noted that the embodiments and features of the embodiments in the present application can be arbitrarily combined with each other without conflict.

Example 1

Embodiment 1 illustrates a flow chart for receiving a first parameter, a second message, a first set of data and a first set of sequence numbers, determining a second set of data, and sending the second set of sequence numbers according to one embodiment of the application, as shown in fig. 1. In fig. 1, each block represents a step, and it is particularly emphasized that the sequence of the blocks in the figure does not represent a chronological relationship between the represented steps.

In embodiment 1, a first node in the present application receives a first parameter, a second message, a first data set, and a first sequence number set in step 101; determining a second set of data and sending a second set of sequence numbers in step 102;

the first set of data is used to generate PDCP SDUs for a first PDCP entity; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for a PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for carrying a first service; the first traffic is non-unicast traffic; in response to receiving the second message, determining a second set of data and sending a second set of sequence numbers; the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the length of the first sequence number; the data forward of the handover comprises only the second set of data; the first parameter and the first set of data are sent by the core network.

As an embodiment, the first node is a UE.

As an embodiment, the first node is a base station.

As one embodiment, the first node is a serving cell.

As an embodiment, the first node is a DU (Distributed Unit) entity.

As an embodiment, the first node is a CU (Centralized Unit) entity.

As an embodiment, the first node is a primary cell.

As one embodiment, the first node is a master cell group.

As one embodiment, the first node is a cell group.

As one embodiment, the first node is a relay.

As one embodiment, the first parameter includes a sequence number (sequence number).

As an embodiment, the first parameter includes a GTP-U sequence number (sequence number).

As one embodiment, the first parameter includes the first sequence number length.

As an embodiment, the first parameter indicates a context of the first service.

For one embodiment, the first parameter includes a DL QFI Sequence Number.

As one embodiment, the first parameter includes a first index indicating the first sequence number length, the first index being an index of a set of sequence number lengths to which the first sequence number length belongs.

As a sub-implementation of this embodiment, the set of sequence numbers includes {12 bits, 18 bits }.

As an embodiment, the first parameter includes a size of a packet of the first service, and when the size of the packet of the first service is smaller than a first threshold, the first sequence number length is determined to be 12 bits; when the size of the packet of the first service is greater than a second threshold, the first sequence number length is determined to be 18 bits.

As a sub-embodiment of this embodiment, when the size of the packet of the first service is equal to a first threshold, the length of the first sequence number is determined to be 12 bits.

As a sub-embodiment of this embodiment, when the size of the data packet of the first service includes a statistical characteristic of the size of the data packet.

As a sub-embodiment of this embodiment, when the size of the data packet of the first service includes an average size of data packets.

As a sub-embodiment of this embodiment, the first threshold is equal to the second threshold.

As a sub-embodiment of this embodiment, the first threshold is not equal to the second threshold.

As a sub-embodiment of this embodiment, the first threshold and the second threshold are respectively indicated by a core network.

As a sub-embodiment of this embodiment, the first threshold and the second threshold are predefined.

As a sub-embodiment of this embodiment, the first threshold and the second threshold are indicated by a service description.

As one example, the service description is used to describe the first service.

As one example, the Service Description includes a User Service Description (User Service Description).

As an embodiment, the first parameter includes a service type of the first service, and when the type of the first service is a first type, the length of the first sequence number is determined to be 12 bits; when the type of the first service is a second type, the first sequence number length is determined to be 18 bits.

As a sub-embodiment of this embodiment, the second type comprises only services other than the first type.

As a sub-embodiment of this embodiment, the service description of the first service includes the first type of service and/or the second type of service.

As a sub-embodiment of this embodiment, the service of the first service includes a service of a small data packet.

As a sub-embodiment of this embodiment, the traffic of the second service includes traffic of large data packets.

As an embodiment, the first parameter includes a data arrival of the first service, and when the data arrival of the first service is less than a first arrival threshold, the first sequence number length is determined to be 12 bits; the first sequence number length is determined to be 18 bits when the data arrival of the first traffic is greater than the first arrival threshold.

As a sub-embodiment of this embodiment, said data arrival of said first service comprises a period of data arrival.

As a sub-embodiment of this embodiment, said data arrival of said first service comprises a frequency of data arrival.

As a sub-embodiment of this embodiment, the service description of the first service includes the first arrival threshold.

As an embodiment, the first parameter is transmitted by broadcasting.

As an embodiment, the first parameter is sent by means of unicast.

For one embodiment, the first parameter may uniquely determine the length of the first sequence number.

In one embodiment, the first sequence number length includes 12 bits.

For one embodiment, the first sequence number length includes 16 bits.

In one embodiment, the first sequence number length comprises 18 bits.

For one embodiment, the first sequence number length includes 20 bits.

For one embodiment, the first sequence number length includes 22 bits.

As an embodiment, the first sequence number length comprises 24 bits.

As an embodiment, the second message is sent over an X2 interface.

As an embodiment, the second message is sent over an Xn interface.

As an embodiment, the second message is used for mobility management.

For one embodiment, the second message comprises a NAS message.

For one embodiment, the second message comprises a HANDOVER REQUEST.

For one embodiment, the second message includes a HANDOVER REQUEST ACKNOWLEDGE.

As one embodiment, the first set of data includes IP (Internet Protocol) data.

For one embodiment, the first set of data includes non-IP data.

As an embodiment, the first Data set includes a GTP-U (GPRS tunneling Protocol User Plane) PDU (Protocol Data Unit).

For one embodiment, the first set of data comprises GTP-PDUs.

For one embodiment, the first set of data includes T-PDUs.

For one embodiment, the first set of data includes IP multicast data.

For one embodiment, the first set of data includes a positive integer number of data.

For one embodiment, the first set of data includes a positive integer number of PDUs.

For one embodiment, the first set of data includes data of the first service transmitted through an N3 interface.

For one embodiment, the first set of data includes data of the first service transmitted over an MB-N3 interface.

In one embodiment, the first set of data includes PDCP SDUs.

For one embodiment, the first set of data includes an SDAP SDU.

For one embodiment, the first set of data includes SDAP PDUs.

For one embodiment, the first set of sequence numbers includes PDCP sequence numbers.

As an embodiment, the first set of sequence numbers comprises GTP-U sequence numbers.

As an embodiment, the first set of sequence numbers comprises sequence numbers in an extension header of a GTP-PDU.

As an embodiment, the Sequence Number in the first Sequence Number set is determined by a DL QFI Sequence Number field of a GTP PDU used for transmitting the first service.

As an embodiment, the Sequence Number in the first Sequence Number set is determined by the value of DL QFI Sequence Number field of GTP PDU for transmitting the first service and the module value of 2^ L, wherein L is the length of the first Sequence Number.

As an embodiment, the Sequence numbers in the first Sequence Number set are the least significant bits of the length of the first Sequence Number of the DL QFI Sequence Number field of the GTP PDU for transmitting the first service.

As an embodiment, the Sequence numbers in the first Sequence Number set are the highest order bits of the length of the first Sequence Number of the DL QFI Sequence Number field of the GTP PDU for transmitting the first service.

As an embodiment, the ith sequence number is any one of the sequence numbers in the first set of sequence numbers, and the ith sequence number corresponds to the ith data in the first set of data.

As an embodiment, the sequence numbers in the first sequence number set correspond to the data in the first data set one to one.

As an embodiment, the number of elements included in the first sequence number set is the same as the number of elements included in the first data set.

As an embodiment, the sequence number included in the first set of sequence numbers is a sequence number of data in the first set of data.

As an embodiment, the Data in the first Data set is input into a PDCP SDU (Service Data Unit) of the first PDCP entity, which becomes the first PDCP entity.

As an embodiment, the Data in the first Data set is processed by the SDAP layer and then input to the first PDCP entity to become a PDCP SDU (Service Data Unit) of the first PDCP entity.

As an embodiment, the data in the first data set is input into the first PDCP entity after being encapsulated by the SDAP layer, and becomes the PDCP SDU of the first PDCP entity.

As an embodiment, the first PDCP PDU is any one PDCP PDU generated or transmitted by the first PDCP entity, and the sequence number of the header of the first PDCP PDU is a sequence number allocated by the first PDCP entity to a PDCP SDU included in the first PDCP PDU.

For one embodiment, each sequence number in the first set of sequence numbers is used to identify a data in the first set of data.

For one embodiment, each sequence number in the first set of sequence numbers is used to identify a unique piece of data in the first set of data; each data in the first data set has a unique serial number in the first serial number set corresponding to it.

As an embodiment, the sequence number assigned by the first PDCP entity for PDCP SDUs is a PDCP sequence number.

As an embodiment, the first PDCP entity is a PDCP entity of the first radio bearer.

As an embodiment, the first PDCP entity is bound with the first radio bearer.

As an embodiment, the first PDCP entity is configured to transmit only a first flow of the first service.

As a sub-embodiment of this embodiment, the first flow comprises a QoS flow.

As a sub-embodiment of this embodiment, the first stream comprises an IP stream.

As an embodiment, the first radio bearer is used only for transmitting the first flow of the first traffic.

As an embodiment, NAS signaling sent by a core network to the first node includes the first parameter.

As an embodiment, a header of a GTP-PDU sent by the core network to said first node comprises said first parameter.

For one embodiment, the second message does not include data forward information.

As an embodiment, the second set of sequence numbers is sent only if the second message includes data forward information.

As an embodiment, the action determines that the second set of data is executed only if the second message includes data forward information.

As one embodiment, the second set of sequence numbers is sent only if the second message includes an indication that the second set of sequence numbers is needed.

As an embodiment, the second set of sequence numbers is transmitted only if the second message includes an indication that data forward is required.

As one embodiment, the action determines that the second set of data is to be executed only if the second message includes an indication that data forward is required.

As one embodiment, the first radio bearer is a non-unicast bearer.

As one embodiment, the first radio bearer is a unicast bearer.

As one embodiment, the first radio bearer comprises an MRB.

For one embodiment, the first radio bearer comprises a SC-MRB.

As an embodiment, the first radio bearer comprises an MBS-MRB.

For one embodiment, the first radio bearer comprises 5 MRBs.

As an embodiment, the first service includes an MBMS service.

As an embodiment, the first service includes an MBS service.

For one embodiment, the first service includes a broadcast service.

For one embodiment, the first traffic comprises multicast traffic.

For one embodiment, the first service includes a multicast service.

As an embodiment, the second message is used to trigger the first node to send the second set of sequence numbers.

For one embodiment, the first node determines the second data set from the first data set.

For one embodiment, the first set of data is used to generate a first set of SDAP SDUs.

As a sub-embodiment of this embodiment, all data in the first set of data is input as input to an SDAP entity, generating the first set of SDAP SDUs.

As a sub-embodiment of this embodiment, a load (payload) carried by each data packet in the first data set is input as an input to an SDAP entity to generate the first set of SDAP SDUs.

As a sub-embodiment of this embodiment, the SDAP entity is associated with the first PDCP entity.

For one embodiment, the first set of SDAP SDUs includes a first subset of SDAP SDUs that are input to the first PDCP entity to generate a first initial set of PDCP SDUs; each SDAP SDU in the first subset of SDAP SDUs corresponds to one PDCP SDU in the first initial set of PDCP SDUs.

As a sub-embodiment of this embodiment, the first subset of SDAP SDUs includes all SDAP SDUs in the first set of SDAP SDUs that have been processed by the first PDCP entity.

As a sub-embodiment of this embodiment, the first subset of SDAP SDUs includes all the SDAP SDUs input to the first PDCP entity in the first set of SDAP SDUs.

As a sub-embodiment of this embodiment, the first subset of SDAP SDUs includes all SDAP SDUs in the first set of SDAP SDUs for which corresponding PDCP SDUs exist.

As a sub-embodiment of this embodiment, the first subset of SDAP SDUs includes all the SDAP SDUs in the first set of SDAP SDUs that generated PDCP SDUs.

As an embodiment, the first initial set of PDCP SDUs includes a first set of PDCP SDUs, and the first PDCP entity assigns a PDCP sequence number to each PDCP SDU in the first set of PDCP SDUs.

In one embodiment, the first initial set of PDCP SDUs includes a second set of PDCP SDUs, and the first PDCP entity does not assign a PDCP sequence number to each PDCP SDU in the second set of PDCP SDUs.

As an embodiment, the second SDAP SDU subset is a complement of the first SDAP SDU subset with respect to the first SDAP SDU subset, that is, a union of the first SDAP SDU subset and the second SDAP SDU subset is the first SDAP SDU subset, and the second SDAP SDU subset is not empty; the second set of data does not include the second subset of SDAP SDUs.

As an embodiment, the second set of data does not include elements other than PDCP SDUs.

As a sub-embodiment of this embodiment, the second set of data does not include PDCP SDUs to which PDCP sequence numbers are not assigned.

In one embodiment, the second set of PDCP SDUs is not empty, and the second set of data does not include the second set of PDCP SDUs.

As an embodiment, the second set of data includes unacknowledged PDCP SDUs from the first set of PDCP SDUs.

As a sub-embodiment of this embodiment, the RLC bearer with which the first radio bearer is associated is in AM mode.

As a sub-embodiment of this embodiment, the unacknowledged PDCP SDU is that its corresponding PDCP PDU is not acknowledged by the receiving UE.

As an embodiment, the second set of data includes PDCP SDUs in which corresponding PDCP PDUs in the first set of PDCP SDUs are not acknowledged by the UE.

In one embodiment, the second set of data includes non-transmitted PDCP SDUs of the first set of PDCP SDUs.

As an embodiment, each sequence number in the second set of sequence numbers is a PDCP sequence number.

As an embodiment, the above method has a benefit that the source cell does not forward data for data without PDCP sequence number, which can avoid confusion and confusion caused by the destination cell receiving data without sequence number.

As an embodiment, the second set of PDCP SDUs is not empty, and the first PDCP entity assigns a PDCP sequence number to each PDCP SDU in the second set of PDCP SDUs when the first node determines the second set of data or performs data forwarding; the second set of data includes the second set of PDCP SDUs.

As an embodiment, the second set of PDCP SDUs is not empty, the act determining that the second set of data or the act performs data forwarding triggers the first PDCP entity to assign a PDCP sequence number to each PDCP SDU in the second set of PDCP SDUs; the second set of data includes the second set of PDCP SDUs.

For one embodiment, each sequence number in the second set of sequence numbers is a PDCP sequence number.

As an embodiment, the above method has the advantages that, in the process of performing data forward, the first node pairs PDCP SDUs which have not been assigned SDU sequence numbers, and of course, PDCP SDUs which have not been transmitted, assign PDCP sequence numbers, and then perform data forward; that is, the first node will not perform data forwarding on SDUs without PDCP sequence numbers, so as to avoid confusion and confusion caused by the destination cell receiving data without sequence numbers.

As an embodiment the sender of said second message discards data without sequence numbers onwards.

As an embodiment, the sender of the second message discards data that is forwarded without a corresponding PDCP sequence number.

For one embodiment, the second set of sequence numbers includes a first subset and a second subset; the first subset and the second subset are both non-empty subsets; the sequence numbers in the first subset are PDCP sequence numbers; the sequence numbers in the second subset include sequence numbers other than PDCP sequence numbers.

As a sub-embodiment of this embodiment, the sequence numbers other than the PDCP sequence number include a GTP-U sequence number.

As a sub-embodiment of this embodiment, the sequence number other than the PDCP sequence number includes a sequence number included in an extension field of a GTP-U.

As a sub-embodiment of this embodiment, the sequence numbers other than the PDCP sequence number include extended sequence numbers.

As a sub-embodiment of this embodiment, the sequence number other than the PDCP sequence number includes a sequence number of a TCP or a UDP.

As a sub-embodiment of this embodiment, the sequence numbers other than the PDCP sequence number include sequence numbers higher than the PDCP layer protocol.

As a sub-embodiment of this embodiment, the second subset corresponds to SDUs in the second data set to which no PDCP sequence number is assigned.

As an embodiment, the sequence numbers in the second subset correspond to the SDAP SDUs in the second subset of SDAP SDUs one-to-one.

For one embodiment, the first set of sequence numbers includes the second subset.

For one embodiment, the first set of data includes the second subset of SDAP SDUs.

As an embodiment, the sequence numbers in the second subset are used to generate PDCP sequence numbers.

As an embodiment, the above method has a benefit that each data for the source cell to perform data forward has a sequence number, even if it is not the PDCP sequence number, so as to avoid confusion and confusion of the destination cell.

As an example, the data forward direction of the sentence said switching includes only the second data set including the following meaning: the data forward triggered by the second message comprises only the second set of data.

As an embodiment, said data forward direction of said sentence said switching comprises only said second data set including the following meanings: the handover-triggered data forwarding of the second message comprises only the second set of data.

As an embodiment, said data forward direction of said sentence said switching comprises only said second data set including the following meanings: data of the data forward direction of the handoff for which the second message is used includes only data from the second set of data.

As an embodiment, said data forward direction of said sentence said switching comprises only said second data set including the following meanings: the data forward direction of the first node for the handover for which the second message is used does not include data of the first traffic outside the second set of data.

As an example, the data forward direction of the sentence said switching includes only the second data set including the following meaning: data of the data forward of the handoff includes only data from the second set of data.

As an embodiment, said data forward direction of said sentence said switching comprises only said second data set including the following meanings: the data forward direction for the handover does not include data of the first traffic outside of the second set of data.

As an embodiment, said data forward direction of said sentence said switching comprises only said second data set including the following meanings: and the forward direction of data in the switching process to which the second message belongs does not comprise data except the second data set.

For one embodiment, each sequence number in the second set of sequence numbers is used to identify a unique piece of data in the second set of data.

As an embodiment, each data in the second data set has a unique one of the second sequence numbers corresponding to it.

As an embodiment, the sentence that the first data set belongs to the first service includes the following meanings: the first set of data includes and only includes data of the first service.

In one embodiment, the length of the PDCP sequence number included in the first subset is the first sequence number length.

For one embodiment, the second set of sequence numbers does not include PDCP sequence numbers.

As an embodiment, the sentence the second data set is used for the data forward direction of the switch includes the following meaning: the handover-triggered data forward direction comprises forward (forward) the second set of data.

As an embodiment, the sentence the second data set is used for the data forward direction of the switch includes the following meaning: the handover-triggered data forwarding comprises sending the second set of data to a sender of the second message.

As an embodiment, the sentence the second data set is used for the data forward direction of the switch includes the following meaning: the data forward direction included or brought about by the handover includes sending the second set of data to a sender of the second message.

As an embodiment, the sentence the second data set is used for the data forward of the handover includes the following meanings: the forward direction of data in the handover procedure includes sending the second set of data to a sender of the second message.

As an embodiment, the first parameter and the first data set of the sentence and the phrase core network in the core network transmission include 5 GC.

As an embodiment, the first parameter and the first data set of the sentence and the core network in the transmission by the core network comprise UPF.

As an embodiment, the first parameter and the first data set of the sentence and the core network in the transmission by the core network comprise MB-UPF.

For one embodiment, the first parameter and the first data set of the sentence and the core network being transmitted by the core network include AMF.

As an embodiment, the first parameter and the first data set of the sentence and the core network in the transmission by the core network comprise SMF.

As an embodiment, the first parameter and the first data set of the sentence and the core network in the transmission by the core network comprise MB-SMF.

As an embodiment, the first parameter and the first data set of the sentence and the core network in the core network transmission comprise MBSF-C.

As an embodiment, the first parameter and the first data set of the sentence and the core network in the core network transmission comprise MBSF-U.

As an embodiment, the first parameter and the first data set of the sentence and the core network in the sending by the core network comprise AFs.

As an embodiment, a sequence number in the first set of sequence numbers is determined to be a PDCP sequence number.

As an embodiment, the sequence number in the first set of sequence numbers is determined to be a PDCP sequence number of a PDCP SDU comprising data in the first set of data corresponding to the sequence number in the first set of sequence numbers.

Example 2

Embodiment 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in fig. 2.

Fig. 2 illustrates a diagram of a network architecture 200 of 5G NR, LTE (Long-Term Evolution) and LTE-a (Long-Term Evolution Advanced) systems. The 5G NR or LTE network architecture 200 may be referred to as a 5GS (5G System)/EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS/EPS 200 may include one or more UEs (User Equipment) 201, NG-RANs (next generation radio access networks) 202, 5 GCs (5G Core networks )/EPCs (Evolved Packet cores) 210, HSS (Home Subscriber Server)/UDMs (Unified Data Management) 220, and internet services 230. The 5GS/EPS may interconnect with other access networks, but these entities/interfaces are not shown for simplicity. As shown, the 5GS/EPS provides packet switched services, however those skilled in the art will readily appreciate that the various concepts presented throughout this application may be extended to networks providing circuit switched services or other cellular networks. The NG-RAN includes NR node b (gNB)203 and other gnbs 204. The gNB203 provides user and control plane protocol terminations towards the UE 201. The gnbs 203 may be connected to other gnbs 204 via an Xn interface (e.g., backhaul). The gNB203 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 (transmitting receiving node), or some other suitable terminology. The gNB203 provides the UE201 with an access point to the 5GC/EPC 210. Examples of the UE201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, 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., MP3 player), a camera, a game console, a drone, an aircraft, a narrowband internet of things device, a machine type communication device, a terrestrial vehicle, an automobile, a wearable device, or any other similar functioning device. A person of ordinary skill in the art may also refer to a UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile 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 terminology. The gNB203 is connected to the 5GC/EPC210 through an S1/NG interface. The 5GC/EPC210 includes MME (Mobility Management Entity)/AMF (Authentication Management domain)/SMF (Session Management Function) 211, other MME/AMF/SMF214, S-GW (serving Gateway)/UPF (User Plane Function) 212, and P-GW (Packet data Network Gateway)/UPF 213. The MME/AMF/SMF211 is a control node that handles signaling between the UE201 and the 5GC/EPC 210. In general, the MME/AMF/SMF211 provides bearer and connection management. All user IP (Internet protocol) packets are transported through the S-GW/UPF212, which S-GW/UPF212 itself is connected to the P-GW/UPF 213. The P-GW provides UE IP address allocation as well as other functions. The P-GW/UPF213 is connected to the internet service 230. The internet service 230 includes an operator-corresponding internet protocol service, and may specifically include the internet, an intranet, an IMS (IP Multimedia Subsystem), and a packet-switched streaming service.

As an embodiment, the UE201 supports transmission in a non-terrestrial network (NTN).

As an embodiment, the UE201 supports transmission in a large delay-difference network.

As an embodiment, the UE201 supports V2X transmission.

As an embodiment, the UE201 supports MBS transmissions.

As an embodiment, the UE201 supports 5MBS transmission.

As an embodiment, the UE201 supports MBMS transmission.

As an embodiment, the gNB203 corresponds to the first node in this application.

As one embodiment, the gNB203 supports transmissions over a non-terrestrial network (NTN).

As an embodiment, the gNB203 supports transmission in a large latency difference network.

As an embodiment, the gNB203 supports V2X transmissions.

As an embodiment, the gNB203 supports MBS transmissions.

As an embodiment, the gNB203 supports 5MBS transmissions.

As an embodiment, the gNB203 supports MBMS transmission.

As an embodiment, the gNB203 supports multicast broadcast services.

As an embodiment, the gNB204 corresponds to the second node in this application.

As one embodiment, the gNB204 supports transmissions over a non-terrestrial network (NTN).

As one embodiment, the gNB204 supports transmission in large latency difference networks.

For one embodiment, the gNB204 supports V2X transmissions.

As an embodiment, the gNB204 supports MBS transmissions.

As an embodiment, the gNB204 supports MBMS transmission.

As an embodiment, the gNB204 supports multicast broadcast services.

Example 3

Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture for a user plane and a control plane according to the present application, as shown in fig. 3. Fig. 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, fig. 3 showing the radio protocol architecture for the control plane 300 between a first node (UE, satellite or aircraft in a gNB or NTN) and a second node (gNB, satellite or aircraft in a UE or NTN), or two UEs, 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 herein as PHY 301. Layer 2(L2 layer) 305 is above PHY301 and is responsible for the link between the first and second nodes and the two UEs through PHY 301. 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 ciphering data packets and provides handoff support between second nodes to the first node. The RLC sublayer 303 provides segmentation and reassembly of upper layer packets, retransmission of lost packets, and reordering of 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 the various radio resources (e.g., resource blocks) in one 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 (layer L3) in the Control plane 300 is responsible for obtaining Radio resources (i.e., Radio bearers) and configuring the lower layers using RRC signaling between the second node and the first node. The radio protocol architecture of the user plane 350 includes layer 1(L1 layer) and layer 2(L2 layer), the radio protocol architecture in the user plane 350 for the first and second nodes is substantially the same 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 as the corresponding layers and sublayers in the control plane 300, but the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 further includes an SDAP (Service Data Adaptation Protocol) sublayer 356, and the SDAP sublayer 356 is responsible for mapping between QoS streams and Data Radio Bearers (DRBs) to support diversity of services. One SDAP SDU becomes SDAP PDU through the processing of the SDAP layer, and the SDAP PDU is PDCP SDU after entering the PDCP layer. One SDAP PDU can also be considered as a PDCP SDU. For example, one IP packet may be considered an SDAP SDU. Although not shown, the first node may have several upper layers above the L2 layer 355. Also included are a network layer (e.g., IP layer) that terminates at the P-GW on the network side and an application layer that terminates at the other end of the connection (e.g., far end UE, server, etc.). In the protocol structure, the SDU of each layer is changed into PDU by the current layer, and the PDU changed by the processing enters the next layer to become the next layer SDU, which becomes the next layer PDU after being processed by the next layer. If a layer is transported in transparent mode, i.e. without a protocol header, the SDUs and PDUs of this layer are essentially identical.

As an example, the wireless protocol architecture in fig. 3 is applicable to the first node in this application.

As an example, the radio protocol architecture in fig. 3 is applicable to the second node in this application.

As an embodiment, the first set of SDAP SDUs in this application is directed to the SDAP 356.

As an example, the first subset of SDAP SDUs in this application is generated in the SDAP 356.

As an example, the second subset of SDAP SDUs in this application is generated in the SDAP 356.

As an example, the first initial set of PDCP SDUs in this application is processed by the PDCP 354.

As an embodiment, the first set of PDCP SDUs in this application is processed by the PDCP 354.

As an embodiment, the second set of PDCP SDUs in this application is processed for the PDCP 354.

As an embodiment, the first PDCP entity in this application is the PDCP 354.

Example 4

Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in fig. 4. Fig. 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. Fig. 4 shows that the first communication device and the second communication device are connected in a wireless manner, and the first communication device and the second communication device can also be connected in a wired manner; when the connection is made by a wired connection, a wireless module such as an antenna shown in fig. 4 may be replaced with a wired transceiver module.

The first communications device 450 includes a controller/processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multiple antenna transmit processor 457, a multiple antenna receive processor 458, a transmitter/receiver 454, and an antenna 452.

The second communication device 410 includes a controller/processor 475, a memory 476, a receive processor 470, a transmit processor 416, a multiple antenna receive processor 472, a multiple antenna transmit processor 471, a transmitter/receiver 418, and an antenna 420.

In the 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 layer L2. In transmissions from the second communications device 410 to the first communications 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 communications 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 constellation 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. Transmit processor 416 then maps each spatial stream to subcarriers, multiplexes with reference signals (e.g., pilots) in the time and/or frequency domain, and then uses an Inverse Fast Fourier Transform (IFFT) to generate the physical channels carrying the time-domain multicarrier symbol streams. The multi-antenna transmit processor 471 then performs transmit analog precoding/beamforming operations on the time domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream that is then provided to a different antenna 420.

In a transmission from the second communications apparatus 410 to the first communications apparatus 450, each receiver 454 receives a signal through its respective antenna 452 at the first communications apparatus 450. Each receiver 454 recovers information modulated onto a radio frequency carrier and converts the radio frequency stream into a baseband multi-carrier symbol stream that is provided to a receive processor 456. Receive processor 456 and multi-antenna receive processor 458 implement the various signal processing functions of the L1 layer. A multi-antenna receive processor 458 performs receive analog precoding/beamforming operations on the baseband multi-carrier symbol streams from receiver 454. Receive processor 456 converts the baseband multicarrier symbol stream after the receive analog precoding/beamforming operation from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signals and the reference signals to be used for channel estimation are demultiplexed by the receive processor 456, and the data signals are subjected to multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered at a receive processor 456 and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communications device 410 on the physical channel. The upper layer data and control signals are then provided to a controller/processor 459. The controller/processor 459 implements the functionality of the L2 layer. The controller/processor 459 may be associated with a memory 460 that stores program codes and data. Memory 460 may be referred to as a computer-readable medium. In transmissions from the second communications device 410 to the second communications device 450, the controller/processor 459 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the core network. The upper layer packet is then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

In a transmission from the first communications device 450 to the second communications device 410, a data source 467 is used at the first communications device 450 to provide upper layer data packets to a controller/processor 459. Data source 467 represents all protocol layers above the L2 layer. Similar to the send function at the second communications apparatus 410 described in the transmission from the second communications apparatus 410 to the first communications apparatus 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, implementing L2 layer functions for the user plane and control plane. The controller/processor 459 is also responsible for retransmission of lost packets and signaling to said second communication device 410. A transmit processor 468 performs modulation mapping, channel coding, and digital multi-antenna spatial precoding by a multi-antenna transmit processor 457 including codebook-based precoding and non-codebook based precoding, and beamforming, and the transmit processor 468 then modulates the resulting spatial streams into multi-carrier/single-carrier symbol streams, which are provided to different antennas 452 via a transmitter 454 after analog precoding/beamforming 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 provides the radio frequency symbol stream to the antenna 452.

In a transmission from the first communication device 450 to the second communication device 410, the functionality at the second communication device 410 is similar to the receiving functionality 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 an rf signal through its respective antenna 420, converts the received rf signal to a baseband signal, and provides the baseband signal to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multiple antenna receive processor 472 collectively implement the functionality of the L1 layer. The controller/processor 475 implements the L2 layer functions. The controller/processor 475 can be associated with a memory 476 that stores program codes and data. Memory 476 may be referred to as a computer-readable medium. In transmission from the first communications device 450 to the second communications device 410, the controller/processor 475 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the UE 450. Upper layer data packets from the controller/processor 475 may be provided to a core network.

As an embodiment, the first communication device 450 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, for use with the at least one processor, the first communication device 450 apparatus at least: receiving a first parameter; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for the PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for carrying a first service; the first traffic is non-unicast traffic; receiving a first set of data and a first set of sequence numbers; the first set of data is used to generate PDCP SDUs for the first PDCP entity; receiving a second message; in response to receiving the second message, determining a second set of data and sending a second set of sequence numbers; wherein the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the first sequence number length; the data forward of the handover comprises only the second set of data; the first parameter and the first set of data are sent by the core network.

As an embodiment, the first communication device 450 includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: receiving a first parameter; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for the PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for carrying a first service; the first traffic is non-unicast traffic; receiving a first set of data and a first set of sequence numbers; the first set of data is used to generate PDCP SDUs for the first PDCP entity; receiving a second message; in response to receiving the second message, determining a second set of data and sending a second set of sequence numbers; wherein the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the first sequence number length; the data forward of the handover comprises only the second set of data; the first parameter and the first set of data are sent by the core network.

As an embodiment, the second communication device 410 apparatus includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The second communication device 410 means at least: sending a second message; the second message is used to trigger a recipient of the second message to send a second set of sequence numbers; wherein a recipient of the second message receives a first set of data, a first parameter, and a first set of sequence numbers; the first set of data is used to generate PDCP SDUs for a first PDCP entity; the first parameter is used for indicating a first sequence number length, and the length of the sequence number allocated by the first PDCP entity for the PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for carrying a first service; the first traffic is non-unicast traffic; the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the first sequence number length; the data forward of the handover comprises only the second set of data; the first parameter and the first set of data and the first set of sequence numbers are sent by a core network.

As an embodiment, the second communication device 410 apparatus includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: sending a second message; the second message is used to trigger a recipient of the second message to send a second set of sequence numbers; wherein a recipient of the second message receives a first set of data, a first parameter, and a first set of sequence numbers; the first set of data is used to generate PDCP SDUs for a first PDCP entity; the first parameter is used for indicating a first sequence number length, and the length of the sequence number allocated by the first PDCP entity for the PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for carrying a first service; the first traffic is non-unicast traffic; the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the length of the first sequence number; the data forward of the handover comprises only the second set of data; the first parameter and the first set of data and the first set of sequence numbers are sent by a core network.

As an embodiment, the first communication device 450 corresponds to a first node in the present application.

As an embodiment, the second communication device 410 corresponds to a second node in the present application.

For one embodiment, the first communication device 450 is a UE.

For one embodiment, the first communication device 450 is a base station.

As an embodiment, the first communication device 450 is a vehicle-mounted terminal.

For one embodiment, the second communication device 450 is a relay.

For one embodiment, the second communication device 450 is a satellite.

For one embodiment, the second communication device 410 is a base station.

For one embodiment, the second communication device 410 is a relay.

For one embodiment, the second communication device 410 is a UE.

For one embodiment, the second communication device 410 is a satellite.

For one embodiment, receiver 456 (including antenna 460), receive processor 452, and controller/processor 490 are used to receive the second message.

For one embodiment, receiver 456 (including antenna 460), receive processor 452, and controller/processor 490 are used to receive the first set of data in this application.

For one embodiment, receiver 456 (including antenna 460), receive processor 452, and controller/processor 490 are used to receive the first set of sequence numbers in this application.

For one embodiment, receiver 456 (including antenna 460), receive processor 452, and controller/processor 490 are used to receive the first parameters described herein.

For one embodiment, a transmitter 456 (including an antenna 460), a transmit processor 455, and a controller/processor 490 are used to transmit the first message.

For one embodiment, the transmitter 456 (including the antenna 460), the transmit processor 455, and the controller/processor 490 are used to transmit the second set of sequence numbers in this application.

For one embodiment, a transmitter 456 (including an antenna 460), a transmit processor 455, and a controller/processor 490 are used to transmit the second set of data in this application.

For one embodiment, transmitter 416 (including antenna 420), transmit processor 412, and controller/processor 440 are used to transmit the second message in this application.

For one embodiment, receiver 416 (including antenna 420), receive processor 412, and controller/processor 440 are used to receive the first information in this application.

For one embodiment, receiver 416 (including antenna 420), receive processor 412, and controller/processor 440 are used to receive the second set of data in this application.

For one embodiment, receiver 416 (including antenna 420), receive processor 412, and controller/processor 440 are used to receive the second set of sequence numbers in this application.

Example 5

Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in fig. 5. In fig. 5, U01 corresponds to the first node of the present application, N02 corresponds to the second node of the present application, and C03 is a core network, and it is specifically illustrated that the sequence in the present example does not limit the signaling sequence and the implemented sequence in the present application, wherein the steps in F50 and F51 and F52 are optional.

For theFirst node N01Receiving a first parameter in step S5101; receiving a first set of data and a first set of sequence numbers in step S5102; sending a first message in step S5103; receiving a second message in step S5104; sending a second set of sequence numbers in step S5105; the second set of data is sent in step S5106.

For theSecond node N02Receiving a first parameter in step S5201; receiving a first set of data and a first set of sequence numbers in step S5202; receiving a first message in step S5203; transmitting a second message in step S5204; receiving a second set of sequence numbers in step S5205; a second data set is received in step S5206.

For theCore network C03In step S5301, the first stepA parameter; the first set of data and the first set of parameters are transmitted in step S5302.

In embodiment 5, the first parameter is used to indicate a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for PDCP SDUs is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for bearing a first service; the first traffic is non-unicast traffic; the first set of data is used to generate PDCP SDUs for the first PDCP entity; in response to receiving the second message, determining a second set of data and sending a second set of sequence numbers; the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the length of the first sequence number; the data forward of the handover comprises only the second set of data; the first parameter and the first set of data are sent by the core network.

As an embodiment, the first node N01 is a UE.

As an example, the first node N01 is a relay.

For one embodiment, the second node N01 is a base station.

As an embodiment, the second node N02 is a UE.

As an example, the second node N02 is a relay.

For one embodiment, the second node N02 is a base station.

For one embodiment, the core network C03 is the core network of the first node N01.

As an embodiment, the core network C03 is the core network of the first node N02.

For one embodiment, the core network C03 is an entity within the core network.

For one embodiment, the core network C03 is an entity in the core network that is related to the broadcast multicast service.

As an embodiment, the core network C03 is a 5GC (5G core network).

For one embodiment, the interface between the core network C03 and the first node N01 includes N3.

For one embodiment, the interface between the core network C03 and the first node N01 includes MB-N3.

As an embodiment, the interface between the core network C03 and the first node N01 includes N2.

For one embodiment, the interface between the core network C03 and the second node N02 includes N3.

For one embodiment, the interface between the core network C03 and the second node N02 includes MB-N3.

As an embodiment, the interface between the core network C03 and the second node N02 includes N2.

As an embodiment, the first parameter is sent to the first node N01 and the second node N02 by unicast.

As an embodiment, the first parameter is transmitted to the first node N01 and the second node N02 by means of broadcasting or multicasting.

As an embodiment, the first parameter is sent via a PDU SESSION INFORMATION message.

As an embodiment, the first parameter is sent via a DL PDU SESSION INFORMATION message.

As an embodiment, the first parameter is sent via an MBS PDU SESSION INFORMATION message.

As an embodiment, the first parameter is sent via an MB PDU SESSION INFORMATION message.

As an embodiment, the first parameter is sent via a 5MB PDU SESSION INFORMATION message.

As an embodiment, the first parameter is sent through a 5MBS PDU SESSION INFORMATION message.

As an embodiment, the first parameter is sent via a message of the N2 interface.

As an embodiment, the first parameter is sent via a message of the N3 interface.

As an embodiment, the first parameter is sent via a message of the MB-N3 interface.

For one embodiment, the first set of data is sent to the first node N01 via a tunneling protocol between the core network C03 and the first node N01.

For one embodiment, the first set of data is sent to the first node N01 via IP multicast between the core network C03 and the first node N01.

For one embodiment, the first set of data is sent to the second node N02 via a tunneling protocol between the core network C03 and the second node N02.

For one embodiment, the first set of data is sent to the second node N02 via IP multicast between the core network C03 and the second node N02.

For one embodiment, the second node N02 receives the first set of data and the first set of sequence numbers.

For one embodiment, the second node N02 did not receive the first set of data and the first set of sequence numbers.

For one embodiment, the second node N02 receives only partial data in the first set of data and partial sequence numbers in the first set of sequence numbers; and partial data in the first data set corresponds to partial sequence numbers in the first sequence number set in a one-to-one mode.

For one embodiment, the second node N02 receives data belonging to the first service other than the first set of data and sequence numbers other than the first set of sequence numbers; and the data belonging to the first service except the first data set corresponds to the sequence numbers except the first sequence number set in a one-to-one manner.

As an embodiment, the core network C03 sends data belonging to the first service except for the first data set and sequence numbers except for the first sequence number set; and the data belonging to the first service except the first data set corresponds to the sequence numbers except the first sequence number set in a one-to-one manner.

As an embodiment, the first node N01 does not receive data belonging to the first service other than the first set of data and also does not receive sequence numbers other than the first set of sequence numbers.

As an embodiment, the first set of data is sent to the first node N01 through a multicast distribution session (multicast distribution session).

As an embodiment, the first set of data is sent to the second node N02 through a multicast distribution session (multicast distribution session).

As an embodiment, the first parameter is sent using the same GTP tunnel as the first set of data.

As an embodiment, the first parameter and the first data set are sent using different GTP tunnels.

As an embodiment, the first node N01 and the second node N02 receive the first traffic from the core network C03 using the same GTP TEID.

As an embodiment, the first node N01 and the second node N02 receive the first traffic from the core network C03 using different GTP TEIDs.

As an embodiment, the first parameter is sent through a Session Request message.

As an embodiment, the first parameter is sent through an N2 Session Request message.

As an embodiment, the first parameter is sent through a Multicast Distribution Request message.

As an embodiment, the first parameter is sent through an MBS Distribution Request message.

As an embodiment, the first parameter is sent through a 5MBS Distribution Request message.

As an embodiment, the first parameter is sent via GTP-U protocol.

As an embodiment, the first parameter is sent through a GTP-U configuration message sent by the core network C03.

As an embodiment, the first node N01 determines that a first UE needs to be handed over, in response to determining that the first UE needs to be handed over, the first node N01 sends the first message; the first message and the second message are both used for handover of the first UE.

As a sub-embodiment of this embodiment, the first message comprises an identity of the first UE.

As a sub-embodiment of this embodiment, the first message includes a context of the first UE.

As an embodiment, the interface between the first node N01 and the second node N02 comprises Xn.

For one embodiment, the interface between the first node N01 and the second node N02 includes X2.

As an embodiment, the first message is sent directly to the second node N02.

As an embodiment, the first message is sent to the second node N02 through a core network C03.

As an embodiment, the second message is sent directly to the first node N01.

As an embodiment, the second message is sent to the first node N01 through a core network C03.

For one embodiment, the second message does not include a data forward direction.

For one embodiment, the second message includes data forward information;

the first node N01, performing data forwarding on the second data set through a GTP tunnel indicated by the data forwarding information included in the second message;

whether the second message includes the data forward information is related to whether the second node N02 established a first interface for transmitting the first traffic; the first interface is an interface between a sender of the second message and a core network.

As a sub-embodiment of this embodiment, the data forward information indicates a GTP tunnel between the first node N01 and the second node N02.

As a sub-embodiment of this embodiment, the data forward information indicates a GTP-U interface between the first node N01 and the second node N02.

As a sub-embodiment of this embodiment, the Data Forwarding information includes Data Forwarding Info from target NG-RAN node.

As a sub-embodiment of this embodiment, the Data Forwarding information includes Secondary Data Forwarding Info from target NG-RAN node List.

As a sub-embodiment of this embodiment, the data forward Information includes PDU Session level DL data forwarding UP TNL Information.

As a sub-embodiment of this embodiment, the sentence performing the data forward on the second data set includes: sending the second set of data using a GTP tunnel indicated by data forward information included in the second message.

As a sub-embodiment of this embodiment, the first interface is an interface between the second node N02 and a core network.

As a sub-embodiment of this embodiment, the first interface is an interface between the second node N02 and the core network C03.

As a sub-embodiment of this embodiment, the first interface comprises an N2 interface.

As a sub-embodiment of this embodiment, the first interface comprises an N3 interface.

As a sub-embodiment of this embodiment, the first interface comprises an MB-N3 interface.

As a sub-embodiment of this embodiment, the first interface is an interface of a user plane.

As a sub-embodiment of this embodiment, the first interface is an interface used by the second node N02 to receive the first service data from a core network.

As a sub-embodiment of this embodiment, when the first interface is not established, the second message includes data forward information.

As a sub-embodiment of this embodiment, the second message may not include the data forward information when the first interface has been established.

For one embodiment, the first message includes the second set of sequence numbers.

As an embodiment, the second data set includes only PDCP PDUs of the first service that are next not transmitted or to be transmitted; the second set of sequence numbers includes only PDCP sequence numbers of PDCP PDUs that are not transmitted or are to be transmitted next for the first service.

As an embodiment, the second set of data includes only the next untransmitted or to be transmitted PDCP PDUs of the first radio bearer; the second set of sequence numbers includes only sequence numbers of a next untransmitted or pending PDCP PDU of the first radio bearer.

As an embodiment, the second data set includes only PDCP PDUs of the first PDCP entity that are next not transmitted or to be transmitted; the second set of sequence numbers includes only sequence numbers of the next untransmitted or pending PDCP PDUs of the first PDCP entity.

As an embodiment, the second data set only includes a next untransmitted or to-be-transmitted PDCP SDU of the first service; the second set of sequence numbers includes only PDCP sequence numbers of a next untransmitted or to-be-transmitted PDCP SDU of the first service.

As an embodiment, the second set of data includes only the next untransmitted or to-be-transmitted PDCP SDU of the first radio bearer; the second set of sequence numbers includes only sequence numbers of a next untransmitted or pending PDCP SDU of the first radio bearer.

As an embodiment, the second data set includes only the next non-transmitted or to-be-transmitted PDCP SDU of the first PDCP entity; the second set of sequence numbers includes only sequence numbers of a next untransmitted or to-be-transmitted PDCP SDU of the first PDCP entity.

As a sub-embodiment of this embodiment, the second set of sequence numbers includes a COUNT value of the first PDCP entity, and the COUNT value of the first PDCP entity includes a sequence number of a next non-transmitted or to-be-transmitted PDCP SDU of the first PDCP entity.

As a sub-embodiment of this embodiment, the first message comprises the second set of sequence numbers.

As a sub-embodiment of this embodiment, the SN status transfer message comprises said second set of sequence numbers.

For one embodiment, the second node N02 sends the second set of sequence numbers via an SN status Transfer message.

As an embodiment, the second set of sequence numbers and the second set of data are transmitted simultaneously.

For one embodiment, the second set of sequence numbers is sent via a control plane message.

As an embodiment, the second set of sequence numbers is sent through a GTP tunnel indicated by data forward information included in the second message.

As an embodiment, the data forward information included in the second message is for the first service.

As an embodiment, the data forward information included in the second message is for a session of the first service.

For one embodiment, the first node N01 does not send the second set of sequence numbers when the second message does not include data forward information.

For one embodiment, the first node N01 does not send the second set of data when the second message does not include data forward information.

For one embodiment, the first node N01 sends the second set of sequence numbers when the second message does not include data forward information.

For one embodiment, the second message indicates whether the second set of sequence numbers is required.

For one embodiment, the second message indicates whether the second set of data is needed.

As an embodiment, the second message indicates whether data forwarding is required.

As one embodiment, the second message indicates that only the second set of sequence numbers is needed and the second set of data is not needed when performing data forwarding.

For one embodiment, the first node N01 sends the second data set through the GTP tunnel determined by the data forward information indicated by the second message.

As an example, the above method has the benefits of: transmitting the second set of sequence numbers and/or the second set of data only when needed; for example, the second node is also receiving the data of the first service, and the first node only needs to inform the second sequence number set of the first node, and does not need to forward the data in the corresponding second data set, thereby saving resources, increasing reliability, and avoiding the problem caused by the delay of the data forward.

As an embodiment, the first message includes a COUNT value of the first PDCP entity, and the COUNT value of the first PDCP entity included in the first message is used to determine whether a sender of the second message requires data forward.

As a sub-embodiment of this embodiment, when the COUNT value of the PDCP entity of the sender of the second message for transmitting the first service is smaller than the COUNT value of the first PDCP entity included in the first message, the sender of the second message determines that no data forward is required; otherwise, the sender of the second message determines that data forward is required.

Example 6

Embodiment 6 illustrates a schematic diagram of a structure of a PDCP PDU according to an embodiment of the present invention, as shown in fig. 6.

FIG. 6 illustrates an exemplary PDCP PDU for transmitting data, including a D/C domain, an R domain, a PDCP SN domain, a data domain, and a MAC-I domain; wherein the MAC-I domain is optional. The data field can be used for carrying data of an upper layer; one PDCP PDU may further include a field not shown in fig. 6.

As an embodiment, the D/C field includes 1 bit for indicating data/control.

As one embodiment, the R domain is a reserved domain.

As an embodiment, the PDCP PDU of fig. 6 is applied to the PDCP PDU generated by the first PDCP entity.

For one embodiment, the data field includes data in the first set of data.

As an embodiment, the data field includes data in the first subset of SDAP SDUs in embodiment 1.

As an embodiment, the data field includes data in the first set of PDCP SDUs in embodiment 1.

As an embodiment, the data field includes data in the second set of PDCP SDUs in embodiment 1.

For one embodiment, the sequence number included in the PDCP SN field is a PDCP sequence number.

In one embodiment, the sequence number included in the PDCP SN field is a sequence number assigned by the first PDCP entity for PDCP SDUs.

As an embodiment, the length of the PDCP SN field is the first sequence number length.

As an embodiment, the PDCP SN field is 12 bits long.

As an embodiment, the PDCP SN field is 18 bits long.

For one embodiment, the data field comprises an SDAP PDU.

As an embodiment, the structure of the PDCP PDU in fig. 6 is applicable to the PDCP PDU in the first PDCP PDU set of the present application.

As an embodiment, the structure of the PDCP PDU in fig. 6 is applicable to the PDCP PDU in the second PDCP PDU set of this application.

Example 7a

Embodiment 7a illustrates a schematic diagram of the structure of a GTP-U header according to one embodiment of the present invention, as shown in fig. 7 a.

A GTP-U (General Packet Radio System (GPRS) tunneling Protocol User Plane) header in embodiment 7a is applicable to communication between the first node and the sender of the second message, communication between the first node and the core network, and communication between the sender of the second message and the core network.

As an embodiment, the sender of the second message is the second node.

As an example, the header of GTP-U in example 7a applies to GTPv 1-U.

As an embodiment, the data in the first set of data is one GTP-PDU; said one GTP-PDU is a GTP-PDU.

For one embodiment, the data in the first set of data is a G-PDU.

As an embodiment, the data in the first data set is carried by G-PDUs.

As an embodiment, the data in the first data set is carried by GTP-PDUs.

As an embodiment, the data in the first data set is carried by a GTP-U PDU.

For one embodiment, the data in the first set of data is a T-PDU.

As an example, the version field in fig. 7a is used to indicate the version, and the PN field is used to indicate whether there is a meaningful value in the N-PDU Numbers field; the fourth bit of the first byte in the GTP-U header is a reserved bit set to 0; the E field is used for indicating whether a meaningful value exists in the extension header field; the S field is used for indicating whether a meaningful value exists in the GTP serial number field; the PT field is used for indicating the version of GTP; the message type field is used for indicating the message type of the GTP-U; the length field is used for indicating the length of the load in bytes; the TEID (Tunnel Endpoint Identifier) includes a plurality of bytes for indicating a Tunnel Endpoint identity; the SN field includes 2 bytes to indicate a sequence number; the N-PDU Numbers are used for switching or updating the routing and other functions; the next extension header type field is used to indicate the type of extension header that immediately follows this field.

As an embodiment, the GTP-U header may further include a field, not shown in fig. 7a, for carrying sequence numbers in the first set of sequence numbers.

As an embodiment, the SN field is used to carry sequence numbers in the first set of sequence numbers.

As an embodiment, one field in the extension header is used to carry sequence numbers in the first set of sequence numbers.

As an embodiment, the first GTP-PDU comprises first data, the first data belonging to the first set of data; the header of the first GTP-PDU comprises a first domain and a second domain; the first field is used to indicate a sequence number of the first GTP-PDU, the first field and the second field being used together to generate a sequence number of a first PDCP PDU; the first PDCP PDU is generated by the first PDCP entity.

For one embodiment, the first domain is the SN domain.

As an embodiment, the second field is the N-PDU Number field.

As an embodiment, the second field is at least a part of bits in the N-PDU Number field.

As an embodiment, the SN field is used to generate a PDCP sequence number when the first sequence number is 12 bits long.

As a sub-embodiment of this embodiment, the PDCP sequence number is the value/sequence number included in the PDCP SN field in embodiment 6.

As a sub-embodiment of this embodiment, the SN field is used with a modulo 2^12 modulus for determining a PDCP sequence number.

As one embodiment, the ^ symbols are power operations, e.g., 2^3 equals 8; e.g., 3 < Lambda > 2 equals 9.

In one embodiment, the first data is used to generate the first PDCP PDU.

As an embodiment, the first data is a payload of the first PDCP PDU.

As an embodiment, when the first sequence Number length is 18 bits, the first field is the SN field, and the second field includes 2 bits in the N-PDU Number field.

As a sub-embodiment of this embodiment, the second field comprises that the 2 bits in the N-PDU Number field are either the two least significant bits or the two most significant bits of the N-PDU Number field.

As an embodiment, when the first sequence number length is 18 bits, the first field is the SN field, and the second field includes 2 bits in an extension header.

Example 7b

Embodiment 7b illustrates a schematic diagram of the structure of a GTP-U extension according to one embodiment of the present invention, as shown in fig. 7 b.

Figure 7b shows an extension header of a GTP-U, where the extension header identification field is used to identify the type of the extension header; the extended sequence number field is used for indicating an extended sequence number; the next extension header type field is used for indicating the type of the next extension header; the extension header in fig. 7b may further include a free bit field or a reserved bit field or a padding field.

In one embodiment, the extended sequence number field includes a number of bits equal to the length of the first sequence number, and the sequence number included in the extended sequence number field is a sequence number in the first sequence number set.

As a sub-embodiment of this embodiment, the sequence number included in the extended sequence number field is determined to be a PDCP sequence number.

As an embodiment, the extended sequence number field includes 2 bits, and is used to generate a PDCP sequence number when the first sequence number length is 18 bits.

As a sub-embodiment of this embodiment, the extended sequence number field includes the 2 most significant bits of the PDCP sequence number, and the sequence number field in the GTP-U header includes the 16 least significant bits of the PDCP sequence number.

As a sub-embodiment of this embodiment, the extended sequence number field includes the 2 least significant bits of the PDCP sequence number, and the sequence number field in the GTP-U header includes the 16 most significant bits of the PDCP sequence number.

As an embodiment, the extended sequence number field includes 8 bits, and when the first sequence number length is 18 bits, 2 bits in the extended sequence number field are used to generate a PDCP sequence number.

As an embodiment, the sequence number included in the extended sequence number field is a sequence number in the first set of sequence numbers.

In one embodiment, the extended sequence number field and a sequence number field in a GTP-U header are used together to include sequence numbers in the first set of sequence numbers.

As an embodiment said first set of sequence numbers only comprises sequence numbers in the GTP-U header.

As an embodiment, the first set of sequence numbers only includes sequence numbers carried by the extended sequence number field.

As an embodiment, the first set of sequence numbers comprises sequence numbers and/or extended sequence numbers in a GTP-U header and/or an extended header of the GTP-U header.

In one embodiment, the second set of sequence numbers includes PDCP sequence numbers.

As an embodiment, the extended sequence number field includes 12 bits, and when the first sequence number is 12 bits long, the extended sequence number field includes the PDCP sequence number.

As an embodiment, the extended sequence number field includes K bits, and the first sequence number length of the extended sequence number field indicates the PDCP sequence number assigned by the first PDCP entity.

As a sub-embodiment of this embodiment, K is equal to the first sequence number length.

As a sub-embodiment of this embodiment, K is a positive integer greater than the length of the first sequence number.

In one embodiment, the sequence number field in the GTP-U header and the extension sequence field included in the extension header of the GTP-U are used together to determine the PDCP sequence number assigned by the first PDCP entity for the PDCP SDU.

As an embodiment, the first PDCP PDU entity determines a sequence number in the first set of sequence numbers corresponding to data in the first data set as a sequence number of a PDCP SDU including the data in the first data set.

As an embodiment, a first GTP-U comprises first data, the first data belonging to the first set of data; and the first PDCP entity determines the value of X bits included in the head of the first GTP-U as the PDCP serial number of the PDCP SDU carrying the first data.

As a sub-embodiment of this embodiment, X is equal to the first sequence number length.

As a sub-embodiment of this embodiment, the min (length of the first sequence number, length of the sequence number field in the header of the first GTP-U) bits included in the sequence number field in the header of the first GTP-U are X bits included in the header of the first GTP-U; wherein min is the minimum value operation.

As a sub-embodiment of this embodiment, the X bits comprised by the header of the first GTP-U comprise all bits in the sequence number field in the header of the first GTP-U.

As a sub-embodiment of this embodiment, the X bits included in the header of the first GTP-U include all bits in the sequence number field in the header of the first GTP-U and 2 bits in the extension header.

The first PDCP PDU entity determines sequence numbers in the first sequence number set corresponding to the data in the first data set as sequence numbers of PDCP SDUs including the data in the first data set.

Example 7c

Embodiment 7c illustrates a schematic diagram of the structure of a GTP-U extension according to one embodiment of the present invention, as shown in fig. 7 c.

Figure 7c shows an extension header of a GTP-U, where the extension header identification field is used to identify the type of the extension header; the PDU session container is used for carrying additional information; the next extension header type field is used for indicating the type of the next extension header; the extension header in fig. 7c may further include a free bit field or a reserved bit field or a padding field.

As an embodiment, the PDU session container field includes the first sequence number length of bits, and the sequence number indicated by the first sequence number length of bits included in the PDU session container field belongs to the first sequence number set.

As an embodiment, the PDU session container field includes the first sequence number length of bits, and the first sequence number length of bits included in the PDU session container field is used to generate a PDCP sequence number allocated by the first PDCP entity for PDCP SDUs.

As an embodiment, the first Sequence Number length of the DL QFI Sequence Number field in the DL PDU SESSION INFORMATION included in the PDU SESSION container is used to generate the PDCP Sequence Number allocated by the first PDCP entity for the PDCP SDU.

As an embodiment, the first GTP-PDU comprises the first data and the first extension header, the first extension header comprising a PDU SESSION container, the PDU SESSION container comprising a DL PDU SESSION INFORMATION, wherein the first PDCP PDU comprises the first data, and the value of the first Sequence Number length Number bit of the DL QFI Sequence Number field is determined as the PDCP Sequence Number of the first PDCP PDU.

As a sub-embodiment of this embodiment, said first data belongs to said first set of data.

As a sub-embodiment of this embodiment, said first data is a T-PDU of said GTP-PDUs.

As a sub-embodiment of this embodiment, the sequence number in the first sequence number set corresponding to the first data is a sequence number in a header of the first GTP-PDU.

As a sub-embodiment of this embodiment, the Sequence Number in the first Sequence Number set corresponding to the first data is a value of length of the first Sequence Number in the DL QFI Sequence Number field in the DL PDU SESSION INFORMATION included in the PDU SESSION container.

As an embodiment, the GTP-U header of the GTP-PDU comprising each data of said first set of data comprises at least one extension header.

As a sub-embodiment of this embodiment, the at least one extension header included in the GTP-U header of the GTP-PDU comprising each data of the first set of data comprises a Long PDCP PDU Number type extension header.

As a sub-embodiment of this embodiment, the at least one extension header included in the GTP-U header of the GTP-PDU comprising each data of the first set of data comprises a PDCP PDU Number type extension header.

As a sub-embodiment of this embodiment, the at least one extension header comprised by the GTP-U header of the GTP-PDU comprising each data of the first set of data comprises an extension header of the PDU Session Container type.

Example 8

Embodiment 8 illustrates a schematic diagram in which a first set of sequence numbers is used to generate a second set of sequence numbers according to an embodiment of the present application, as shown in fig. 8.

As an embodiment, the sequence numbers included in the first sequence number set correspond to the data included in the first data set in a one-to-one manner.

As an embodiment, the sequence numbers in the first set of sequence numbers comprise Y bits, where Y is equal to the first sequence number length, the sequence numbers in the first set of sequence numbers being determined to be PDCP sequence numbers.

As an embodiment, the first sequence number is any one sequence number in the first set of sequence numbers, the first sequence number identifies and only identifies first data, the first data belongs to the first set of data, the first PDCP SDU includes the first data, and the PDCP sequence number allocated by the first PDCP entity for the first PDCP SDU is the first sequence number.

As an embodiment, the first sequence number is any one sequence number in the first sequence number set, the first sequence number identifies and only identifies first data, the first data belongs to the first data set, the first PDCP PDU includes the first data, and the sequence number of the first PDCP PDU is the first sequence number.

As an embodiment, sequence numbers in the first set of sequence numbers are directly used for generating PDCP sequence numbers; the second set of sequence numbers includes PDCP sequence numbers directly generated by sequence numbers in the first set of sequence numbers.

As an embodiment, a sum of a value of sequence numbers in the first set of sequence numbers and an offset is used to generate PDCP sequence numbers, and the second set of sequence numbers includes PDCP sequence numbers generated by a sum of a value of sequence numbers in the first set of sequence numbers and an offset.

In one embodiment, the value of the sequence number in the first sequence number set and the modulus of one parameter are used to generate a PDCP sequence number, and the second sequence number set comprises the value of the sequence number in the first sequence number set and the modulus generated PDCP sequence number of one parameter.

As an embodiment, the first PDCP SDU is an SDU of the first PDCP PDU.

As an embodiment, a first GTP-PDU carries first data, the first data being any one of the first set of data, the first sequence number being a sequence number in a header of the first GTP-PDU, the first sequence number belonging to the first set of sequence numbers; the first sequence number and a second field in the first GTP-PDU are commonly used for generating a sequence number of a first PDCP PDU, and the first PDCP PDU comprises the first data.

As a sub-embodiment of this embodiment, the second field comprises 2 bits.

As a sub-embodiment of this embodiment, said second field is a field other than a sequence number field in a header of said first GTP-PDU.

As a sub-embodiment of this embodiment, said second field is a field in an extension header of said first GTP-PDU.

As an embodiment, the sequence numbers in the second sequence number set correspond to the data in the second data set one to one; the sequence number included in the second set of sequence numbers is a PDCP sequence number.

As an embodiment, the second sequence number is any sequence number in the second set of sequence numbers, the second sequence number is used for identifying and only identifying second data, and the second data belongs to the second set of data.

As a sub-embodiment of this embodiment, the second data set belongs to the first data set.

As a sub-embodiment of this embodiment, a second PDCP SDU includes the second data, and the second sequence number is a sequence number allocated by the first PDCP entity to the second PDCP SDU.

As a sub-embodiment of this embodiment, a first sequence number is used for identifying and only for identifying the second data, the first sequence number belonging to the first data set; the first sequence number is used to generate a PDCP sequence number for the second PDCP SDU.

As a sub-embodiment of this embodiment, the second PDCP PDU includes the second data, and the second sequence number is an assigned sequence number of the second PDCP PDU.

As a sub-embodiment of this embodiment, a first sequence number is used for identifying and only for identifying the second data, the first sequence number belonging to the first data set; the first sequence number is used to generate a PDCP sequence number for the second PDCP PDU.

As a sub-embodiment of this embodiment, the second PDCP SDU is an unsent PDCP SDU.

As a sub-embodiment of this embodiment, the second PDCP PDU is an unacknowledged PDCP PDU.

As an embodiment, the first SDAP SDU includes third data, the first SDAP SDU has not been received or processed by the first PDCP entity, a third sequence number is used to identify the third data, the third data belongs to the first set of data, and the third sequence number belongs to the first set of sequence numbers.

As a sub-embodiment of this embodiment, the second set of sequence numbers includes the third sequence number.

As a sub-embodiment of this embodiment, the data forward process in the handover procedure to which the second message belongs includes allocating a PDCP sequence number to the first SDAP SDU; the third sequence number is used to generate the sequence number assigned for the first SDAP SDU.

As a sub-embodiment of this embodiment, the data forward process in the handover process to which the second message belongs includes generating a third PDCP SDU, where the third PDCP SDU includes the first SDAP SDU; the first PDCP entity assigns PDCP sequence numbers to the third PDCP SDU, and the second set of sequence numbers includes the PDCP sequence numbers assigned by the first PDCP entity for the third PDCP SDU.

Example 9

Embodiment 9 illustrates a schematic diagram in which a first specific sequence number is used for determining a second set of sequence numbers according to an embodiment of the present application, as shown in fig. 9.

As an embodiment, the second message indicates a first specific sequence number.

As an embodiment, the sender of the second message is a second node.

As an embodiment, the second node receives a third data set and a third sequence number set from a core network, where the third data set is data of the first service; and the sequence numbers in the third sequence number set correspond to the data in the third data set one by one.

As an embodiment, the sequence numbers in the third set of sequence numbers are arranged in order, and the last sequence number is the first specific sequence number.

As an embodiment, the sequence numbers in the third set of sequence numbers are arranged in order, and the first sequence number is the first specific sequence number.

As an embodiment, sequence numbers in the first sequence number set are arranged in order, and a fourth data set is data in the first data set corresponding to sequence numbers greater than the first specific sequence number in the first sequence number set which are arranged in order.

In one embodiment, the sequence numbers in the first sequence number set are arranged in order, and the fourth data set is data in the first data set corresponding to sequence numbers greater than or equal to the first specific sequence number in the first sequence number set which are arranged in order.

As an embodiment, the sequence numbers in the first sequence number set are arranged in order, and the fourth data set is data in the first data set corresponding to sequence numbers smaller than the first specific sequence number in the first sequence number set which are arranged in order.

As an embodiment, the sequence numbers in the first sequence number set are arranged in order, and the fourth data set is data in the first data set corresponding to sequence numbers smaller than and equal to the first specific sequence number in the first sequence number set which are arranged in order.

As an embodiment, a fourth PDCP SDU set is used to carry data in the fourth data set, wherein an unsent PDCP SDU in the fourth PDCP SDU set belongs to the second data set, and a PDCP sequence number of an unsent PDCP SDU in the fourth PDCP SDU set belongs to the second sequence number set.

As an embodiment, a fourth PDCP PDU set is configured to carry data in the fourth data set, where PDCP SDUs included in unacknowledged PDCP PDUs in the fourth PDCP PDU set belong to the second data set, and PDCP sequence numbers of PDCP PDUs not transmitted in the fourth PDCP PDU set belong to the second sequence number set.

As an embodiment, a fourth set of SDAP SDUs is used to carry data in the fourth data set, an SDAP SDU not processed by the first PDCP entity in the fourth set of SDAP SDUs belongs to the second data set, and sequence numbers belonging to the first set of sequence numbers and corresponding to data in the first data set included in the fourth set of SDAP SDUs belong to the second set of sequence numbers.

As an embodiment, the first specific sequence number comprises a sequence number in a GTP-U header.

As an embodiment, the first specific sequence number comprises a sequence number in an extension header of a GTP-U header.

As one embodiment, the first specific sequence number belongs to the first set of sequence numbers.

As an embodiment, the first specific sequence number is a PDCP sequence number.

As an embodiment, a fifth PDCP sequence number list is sequence numbers of PDCP SDUs that are assigned sequence numbers but not transmitted for the first service, and sequence numbers in the fifth PDCP sequence number list are arranged according to a transmission order; a PDCP SDU corresponding to a PDCP sequence number later than the first specific sequence number in the fifth PDCP sequence number list is determined to belong to the second data set; a PDCP sequence number in the fifth PDCP sequence number list that is later than the first specific sequence number belongs to the second sequence number set.

As an embodiment, a sixth PDCP sequence number list is sequence numbers of PDCP SDUs assigned with sequence numbers that have been sent but corresponding PDCP PDUs are not acknowledged by the UE for the first service, and the sequence numbers in the sixth PDCP sequence number list are arranged according to a sending order; determining a PDCP SDU corresponding to a PDCP sequence number later than the first specific sequence number in the sixth PDCP sequence number list as belonging to the second data set; a PDCP sequence number in the sixth PDCP sequence number list that is later than the first specific sequence number belongs to the second sequence number set.

As an embodiment, the second set of data and the second set of sequence numbers are both sent during a data forward procedure in the belonging handover to which the second message belongs.

As an embodiment, the second set of sequence numbers is sent in a data forward process in the belonging handover to which the second message belongs; the second set of data is not transmitted.

As an embodiment, the above method has the advantage that, in the forward direction of data, since the data of the multicast service is sent to each cell or base station, only the data that has not been received by the UE needs to be sent or indicated, and further, only the sequence number of the data that has not been received by the user needs to be indicated, which can reduce the delay, save the transmission resources, and the opposite side does not need to wait for the data transmitted through GTP-U.

Example 10

Embodiment 10 illustrates a schematic diagram of a first identity used by a sender of a second message to determine whether data forward is required according to one embodiment of the present application, as shown in fig. 10.

As an embodiment, when the sender of the second message determines that data forward is required, the second message includes data forward information.

As an embodiment, the second message is used to indicate that data forward is required when the sender of the second message determines that data forward is required.

For one embodiment, the second message is used to indicate that forward forwarding of the second set of data is required when the sender of the second message determines that forward forwarding of data is required.

As an embodiment, when the sender of the second message determines that data forward is required, the second message is used to indicate that forward of the second set of sequence numbers is required.

In one embodiment, the second message includes data forward information in response to the sender of the second message needing data forward.

In response to the sender of the second message needing forward data, the second message is used to indicate that forward data is needed, as one embodiment.

In one embodiment, the second message is used to indicate that forward forwarding of the second set of data is required in response to a sender of the second message needing forward data.

In one embodiment, the second message is used to indicate that forward forwarding of the second set of sequence numbers is required in response to a sender of the second message requiring forward data.

As an embodiment, the sender of the second message is the second node.

As an embodiment, the sender of the second message is a serving cell.

As an embodiment, the sender of the second message is a base station.

As an embodiment, the sender of the second message is a group of cells.

As an embodiment, the sender of the second message is a destination cell.

As one embodiment, the first node is a source cell.

As one embodiment, the interface between the first node and the second node comprises an Xn interface.

For one embodiment, the interface between the first node and the second node comprises an X2 interface.

As an embodiment, the data forwarding direction is data forwarding.

As one embodiment, the data forward information includes GTP information for data forward.

As an embodiment, the Data forward information comprises Data Forwarding Info from target NG-RAN node.

As an embodiment, the Data forward information includes a second Data Forwarding Info from target NG-RAN node List.

As an embodiment, the data forward Information includes PDU Session level DL data forwarding UP TNL Information.

As one embodiment, the first message includes a first identity; the first identity is an identity associated with the first service, the first identity being used by a sender of the second message to determine whether data forwarding is required.

As an embodiment, the first identity is a session identity of the first service; when the session of the first service sent by the sender of the second message does not include the session determined by the first identity, the second message does not include the data forward information.

As an embodiment, the first identity is a session identity of the first service; when the session of the first service sent by the sender of the second message does not include the session determined by the first identity, the second message indicates that no data forward is required.

As an embodiment, the first identity is a flow identity of the first service; when the flow of the first service sent by the sender of the second message does not include the flow determined by the first identity, the second message does not include the data forward information.

As an embodiment, the first identity is a flow identity of the first service; the second message indicates that data forward is not required when the flow of the first traffic sent by the sender of the second message does not include the flow determined by the first identity.

As an embodiment, the first identity is an area identity of the first service; when the sender of the second message does not belong to the area determined by the first identity, the second message does not include the data forward information.

As an embodiment, the first identity is a zone identity of the first service; the second message indicates that no data forward is required when the sender of the second message does not belong to the area determined by the first identity.

As an embodiment, the first identity is a sub-area identity of the first service; when the sender of the second message does not belong to the sub-region determined by the first identity, the second message does not include the data forward information.

As an embodiment, the first identity is a sub-area identity of the first service; the second message indicates that no data forward is required when the sender of the second message does not belong to the area determined to include the first identity.

As an embodiment, the first identity is a GTP TEID the first node receives the first traffic from a core network; when a sender of the second message receives the GTP TEID of the first service from a core network and is different from the first identity, the second message does not include the data forward information.

As an embodiment, the first identity is a GTP TEID the first node receives the first traffic from a core network; when a sender of the second message receives a GTP TEID of the first service from a core network, the GTP TEID is different from the first identity, the second message indicates that data forward is not needed.

As an embodiment, the first identity is an identity of a core network entity that sends the first service to the first node; when a core network entity that transmits the first service to a sender of the second message is different from the first identity, the second message does not include the data forward information.

As an embodiment, the first identity is an identity of a core network entity that sends the first service to the first node; the second message indicates that data forward is not required when a core network entity that sends the first service to a sender of the second message is different from the first identity.

As an embodiment, the first identity is an IP address used by the first node to receive the first traffic; when the IP address of the first service received to the sender of the second message is different from the IP address determined by the first identity, the second message does not include the data forward information.

As an embodiment, the first identity is an IP address used by the first node to receive the first traffic; the second message indicates that no data forward is required when the IP address of the first service received to the sender of the second message is different from the IP address determined by the first identity.

As a sub-embodiment of this embodiment, the IP address comprises an IP multicast address.

As a sub-embodiment of this embodiment, the IP address includes a source address.

As a sub-embodiment of this embodiment, the IP address comprises a destination address.

Example 11

Embodiment 11 illustrates a block diagram of a processing apparatus for use in a first node according to an embodiment of the present application; as shown in fig. 11. In fig. 11, a processing means 1100 in a first node comprises a first receiver 1101 and a first transmitter 1102. In the case of the embodiment 11, however,

a first receiver 1101 that receives a first parameter, a second message, a first set of data and a first set of sequence numbers, the first set of data being used to generate PDCP SDUs for a first PDCP entity; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for a PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for bearing a first service; the first traffic is non-unicast traffic;

a first transmitter 1102, responsive to receiving the second message, determining a second set of data and transmitting a second set of sequence numbers;

For one embodiment, the first receiver 1101 receives a first GTP-PDU; the first GTP-PDU comprises first data, the first data belonging to the first set of data; the header of the first GTP-PDU comprises a first domain and a second domain; the first field is used to indicate a sequence number of the first GTP-PDU, the first field and the second field being used together to generate a sequence number of a first PDCP PDU; the first PDCP PDU is generated by the first PDCP entity.

For one embodiment, the second message includes data forward information;

the first transmitter 1102 performs data forwarding on the second data set through a GTP tunnel indicated by the data forwarding information included in the second message;

For one embodiment, the second set of sequence numbers includes a first subset and a second subset; the first subset and the second subset are both non-empty subsets; the sequence numbers in the first subset are PDCP sequence numbers; the sequence numbers in the second subset include GTP-U sequence numbers.

As an embodiment, the second message comprises a first specific sequence number, which is used to determine the second set of sequence numbers.

For one embodiment, the first transmitter 1102, transmits a first message; the second message is used for feeding back the first message.

As an embodiment, the first node is a base station.

As an embodiment, the first node is a terminal supporting a large delay difference.

As an embodiment, the first node is a terminal supporting NTN.

As an embodiment, the first node is an aircraft.

As an embodiment, the first node is a vehicle-mounted terminal.

As an embodiment, the first node is a relay.

As an embodiment, the first node is a ship.

As an embodiment, the first node is an internet of things terminal.

As an embodiment, the first node is a terminal of an industrial internet of things.

As an embodiment, the first node is a device supporting low-latency high-reliability transmission.

As an embodiment, the first node is a multicast enabled device.

For one embodiment, the first receiver 1101 includes at least one of the antenna 452, the receiver 454, the receive processor 456, the multiple antenna receive processor 458, the controller/processor 459, the memory 460, or the data source 467 of embodiment 4.

For one embodiment, the first transmitter 1102 includes at least one of the antenna 452, the transmitter 454, the transmit processor 468, the multi-antenna transmit processor 457, the controller/processor 459, the memory 460, or the data source 467 of embodiment 4.

Example 12

Embodiment 12 illustrates a block diagram of a processing apparatus for use in a second node according to an embodiment of the present application; as shown in fig. 12. In fig. 12, the processing means 1200 in the second node comprises a second transmitter 1201 and a second receiver 1202. In the case of the embodiment 12, however,

a second transmitter 1201 that transmits a second message; the second message is used to trigger a recipient of the second message to send a second set of sequence numbers;

wherein a recipient of the second message receives a first set of data, a first parameter, and a first set of sequence numbers; the first set of data is used to generate PDCP SDUs for a first PDCP entity; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for a PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for bearing a first service; the first traffic is non-unicast traffic; the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the first sequence number length; the data forward of the handover comprises only the second set of data; the first parameter and the first set of data and the first set of sequence numbers are transmitted by a core network.

As an embodiment, a second GTP-PDU is received; the second GTP-PDU comprises first data, the first data belonging to the first set of data; the header of the second GTP-PDU comprises a first field and a second field; the first field is used to indicate a sequence number of the second GTP-PDU, the first field and the second field being used together to generate a sequence number of a second PDCP PDU; the second PDCP PDU is generated by a second PDCP entity.

For one embodiment, the second set of sequence numbers includes a first subset and a second subset; the first subset and the second subset are both non-empty subsets; the sequence numbers in the first subset are PDCP sequence numbers; the sequence numbers in the second subset include a GTP-U sequence number.

As one embodiment, the second message includes a first specific sequence number, which is used to determine the second set of sequence numbers.

As an embodiment, the second receiver 1202 receives a first message; the second message is used for feeding back the first message.

As one embodiment, the first message includes a first identity; the first identity is an identity related to the first service, the first identity being used to determine whether data forward is required.

For one embodiment, the second message includes data forward information; the second receiver 1202 receives the second set of sequence numbers.

For one embodiment, the second message includes data forward information.

For one embodiment, the second message does not include data forward information;

the second receiver 1202, receiving the second data set through a GTP tunnel indicated by the data forward information included in the second message;

whether the second message includes the data forward information is related to whether the second node establishes a first interface for transmitting the first traffic; the first interface is an interface between the second node and a core network.

As an embodiment, the second node is a UE (user equipment).

As one embodiment, the second node is an IoT node.

As one embodiment, the second node is a wearable node.

As an embodiment, the second node is a base station.

As one embodiment, the second node is a relay.

For one embodiment, the second node is an access point.

For one embodiment, the second node is a multicast-enabled node.

As one embodiment, the second node is a satellite.

For one embodiment, the second transmitter 1201 includes at least one of the antenna 420, the transmitter 418, the transmit processor 416, the multi-antenna transmit processor 471, the controller/processor 475, and the memory 476 of embodiment 4.

For one embodiment, the second receiver 1202 includes at least one of the antenna 420, the receiver 418, the receive processor 470, the multi-antenna receive processor 472, the controller/processor 475, and the memory 476 of embodiment 4.

It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, such as a read-only memory, a hard disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented by using one or more integrated circuits. Accordingly, the module units in the above embodiments may be implemented in a hardware form, or may be implemented in a form of software functional modules, and the present application is not limited to any specific form of combination of software and hardware. User equipment, terminal and UE in this application include but not limited to unmanned aerial vehicle, Communication module on the unmanned aerial vehicle, remote control aircraft, the aircraft, small aircraft, the cell-phone, the panel computer, the notebook, vehicle Communication equipment, wireless sensor, network card, thing networking terminal, the RFID terminal, NB-IoT terminal, MTC (Machine Type Communication) terminal, eMTC (enhanced MTC) terminal, the data card, network card, vehicle Communication equipment, low-cost cell-phone, low-cost panel computer, satellite Communication equipment, ship Communication equipment, wireless Communication equipment such as NTN user equipment. The base station or the system device in the present application includes, but is not limited to, a macro cellular base station, a micro cellular base station, a home base station, a relay base station, a gbb (NR node B) NR node B, a TRP (Transmitter Receiver Point), an NTN base station, a satellite device, a flight platform device and other wireless communication devices, an eNB (LTE node B), a test device, for example, a transceiver simulating a partial function of a base station, a signaling tester, and the like.

The above description is only a preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like 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 to be used for wireless communication, comprising:

a first receiver for receiving a first parameter, a second message, a first set of data and a first set of sequence numbers, the first set of data being used for generating PDCP SDUs of a first PDCP entity; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for a PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for carrying a first service; the first traffic is non-unicast traffic;

2. The first node of claim 1, comprising:

the first receiver receives a first GTP-PDU; the first GTP-PDU comprises first data, which belongs to the first set of data; the header of the first GTP-PDU comprises a first domain and a second domain; the first field is used to indicate a sequence number of the first GTP-PDU, the first field and the second field being used together to generate a sequence number of a first PDCP PDU; the first PDCP PDU is generated by the first PDCP entity.

3. The first node according to claim 1 or 2,

the second message comprises data forward information;

the first transmitter performs data forward on the second data set through a GTP tunnel indicated by the data forward information included in the second message;

4. The first node according to any of claims to 3,

the second set of sequence numbers comprises a first subset and a second subset; the first subset and the second subset are both non-empty subsets; the sequence numbers in the first subset are PDCP sequence numbers; the sequence numbers in the second subset include a GTP-U sequence number.

5. The first node according to any of claims 1 to 4,

the second message includes a first specific sequence number, which is used to determine the second set of sequence numbers.

6. The first node according to any of claims 1 to 5, comprising:

the first transmitter transmits a first message; the second message is used for feeding back the first message.

7. The first node of claim 6,

the first message comprises a first identity; the first identity is an identity associated with the first service, the first identity being used by a sender of the second message to determine whether data forwarding is required.

8. A second node for wireless communication, comprising:

wherein a recipient of the second message receives a first set of data, a first parameter, and a first set of sequence numbers; the first set of data is used to generate PDCP SDUs for a first PDCP entity; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for a PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for carrying a first service; the first traffic is non-unicast traffic; the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the first sequence number length; the data forward direction of the handover includes only the second set of data; the first parameter and the first set of data and the first set of sequence numbers are sent by a core network.

9. A method in a first node used for wireless communication, comprising:

receiving a first parameter; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for the PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for carrying a first service; the first traffic is non-unicast traffic;

receiving a second message;

10. A method in a second node used for wireless communication, comprising:

wherein a recipient of the second message receives a first set of data, a first parameter, and a first set of sequence numbers; the first set of data is used to generate PDCP SDUs for a first PDCP entity; the first parameter is used for indicating a first sequence number length, and the length of a sequence number allocated by the first PDCP entity for a PDCP SDU is the first sequence number length; the first PDCP entity corresponds to a first radio bearer, and the first radio bearer is used for bearing a first service; the first traffic is non-unicast traffic; the first set of data belongs to the first service; the sequence numbers in the first sequence number set correspond to the data units in the first data set one by one; the second message is used for handover; the second set of data is used for data forward of the handover; the first set of sequence numbers is used to generate the second set of sequence numbers; the sequence numbers in the second sequence number set correspond to the data units in the second data set one by one; the length of the PDCP sequence number included in the second sequence set is the first sequence number length; the data forward direction of the handover includes only the second set of data; the first parameter and the first set of data and the first set of sequence numbers are sent by a core network.