Cell handover method, network side device and readable storage medium

Abstract

The application provides a cell switching method, a network side device and a readable storage medium, and relates to the technical field of communication. The method comprises the following steps: in a cell switching preparation phase, sending packet data convergence protocol (PDCP) data and association identification information to a second network side device through an Xn interface. The association identification information is used for indicating an association relationship between a sequence number (SN) of the PDCP data and a quality of service (QoS) flow identification. According to the application, the first network side device sends the PDCP data and the association identification information to the second network side device in the cell switching preparation phase, so that the second network side device determines the QoS flow identification according to the association identification information, schedules the PDCP data, and reduces the time delay of data transmission.

Description

Technical Field

[0001] This invention relates to the field of communication technology, specifically to a cell handover method, network-side equipment, and readable storage medium. Background Technology

[0002] In existing network systems, when a terminal transmits high-bandwidth services, it needs to associate multiple video streams. These different video streams have varying levels of importance. Differential transmission of these different-level video streams ensures the Quality of Service (QoS) for the terminal when transmitting high-bandwidth services. However, in related technologies, the implementation of fifth-generation mobile communication technology (5G) at the terminal... th In the case of cell handover (-Generation, 5G), the target base station cannot quickly determine multiple video streams within the source base station, resulting in significant data transmission latency.

[0003] It is evident that existing technologies suffer from significant data transmission latency. Summary of the Invention

[0004] This invention provides a cell handover method, a network-side device, and a readable storage medium to solve the problem of large data transmission latency in the prior art.

[0005] To solve the above problems, the present invention is implemented as follows:

[0006] In a first aspect, embodiments of the present invention provide a cell handover method, executed by a first network-side device, comprising:

[0007] During the cell handover preparation phase, Packet Data Convergence Protocol (PDCP) data and association identification information are sent to the second network-side device via the Xn interface. The association identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier.

[0008] Optionally, the QoS identification stream includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain;

[0009] The association identification information includes the association relationship between the data stream identifiers of service frames in different time domains and the SN of the PDCP data, and / or the association relationship between the data stream identifiers of different spatial domains in service frames in the same time domain and the SN of the PDCN data.

[0010] Optionally, the data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to characterize the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

[0011] Optionally, the data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and the different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or,

[0012] Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

[0013] Secondly, embodiments of the present invention also provide a cell handover method, executed by a second network-side device, comprising:

[0014] During the cell handover preparation phase, the Packet Data Convergence Protocol (PDCP) data and association identification information sent by the first network-side device are received through the Xn interface. The association identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier.

[0015] The PDCP data is scheduled based on the associated identification information.

[0016] Optionally, the QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain;

[0017] The association identification information includes the association relationship between the data stream identifier of service frames in different time domains and the SN of PDCP data, and / or the association relationship between the data stream identifier of different spatial domains in service frames in the same time domain and the SN of PDCN data.

[0018] Optionally, scheduling the PDCP data based on the associated identifier information includes:

[0019] The first scheduling weight is determined based on the number of data packets corresponding to the data stream identifiers of service frames in different time domains and the number of PDCP data packets received by the second network-side device.

[0020] The second scheduling weight is determined based on the number of data packets corresponding to the data stream identifiers in different spatial domains within the same time domain service frame;

[0021] The PDCP data is scheduled according to the first scheduling weight and the second scheduling weight.

[0022] Optionally, the data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to characterize the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

[0023] Optionally, the data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and the different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or,

[0024] Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

[0025] Thirdly, embodiments of the present invention also provide a network-side device, comprising:

[0026] The sending module is used to send Packet Data Convergence Protocol (PDCP) data and associated identification information to the second network-side device through the Xn interface during the cell handover preparation phase. The associated identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier.

[0027] Optionally, the association identification information includes the association relationship between the data stream identifier of service frames in different time domains and the SN of the PDCP data, and / or the association relationship between the data stream identifier of different spatial domains in service frames in the same time domain and the SN of the PDCN data.

[0028] Optionally, the data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to characterize the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

[0029] Optionally, the data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and the different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or,

[0030] Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

[0031] Fourthly, embodiments of the present invention also provide a network-side device, comprising:

[0032] The receiving module is used to receive Packet Data Convergence Protocol (PDCP) data and association identification information sent by the first network-side device through the Xn interface during the cell handover preparation phase. The association identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier.

[0033] The processing module is used to schedule the PDCP data according to the associated identification information.

[0034] Optionally, the QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain;

[0035] The association identification information includes the association relationship between the data stream identifier of service frames in different time domains and the SN of PDCP data, and / or the association relationship between the data stream identifier of different spatial domains in service frames in the same time domain and the SN of PDCN data.

[0036] Optionally, the processing module includes:

[0037] The first processing unit is used to determine the first scheduling weight based on the number of data packets corresponding to the data stream identifiers of service frames in different time domains and the number of PDCP data packets received by the second network-side device.

[0038] The second processing unit is used to determine the second scheduling weight based on the number of data packets corresponding to the data stream identifiers of different spatial domains in the same time domain service frame;

[0039] The third processing unit is used to schedule the PDCP data according to the first scheduling weight and the second scheduling weight.

[0040] Optionally, the data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to characterize the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

[0041] Optionally, the data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and the different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or,

[0042] Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

[0043] Fifthly, embodiments of the present invention also provide a network-side device, including a transceiver and a processor.

[0044] The transceiver is used to send Packet Data Convergence Protocol (PDCP) data and associated identification information to the second network-side device via the Xn interface during the cell handover preparation phase. The associated identification information is used to indicate the association between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier.

[0045] Optionally, the association identification information includes the association relationship between the data stream identifier of service frames in different time domains and the SN of the PDCP data, and / or the association relationship between the data stream identifier of different spatial domains in service frames in the same time domain and the SN of the PDCN data.

[0046] Optionally, the data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to characterize the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

[0047] Optionally, the data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and the different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or,

[0048] Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

[0049] Sixthly, embodiments of the present invention also provide a network-side device, including a transceiver and a processor.

[0050] The transceiver is used to receive Packet Data Convergence Protocol (PDCP) data and association identification information sent by the first network-side device through the Xn interface during the cell handover preparation phase. The association identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier.

[0051] The processor is used to schedule the PDCP data according to the associated identification information.

[0052] Optionally, the QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain;

[0053] The association identification information includes the association relationship between the data stream identifier of service frames in different time domains and the SN of PDCP data, and / or the association relationship between the data stream identifier of different spatial domains in service frames in the same time domain and the SN of PDCN data.

[0054] Optionally, the processor is further configured to determine a first scheduling weight based on the number of data packets corresponding to the data stream identifiers of service frames in different time domains and the number of PDCP data packets received by the second network-side device;

[0055] The second scheduling weight is determined based on the number of data packets corresponding to the data stream identifiers in different spatial domains within the same time domain service frame;

[0056] The PDCP data is scheduled according to the first scheduling weight and the second scheduling weight.

[0057] Optionally, the data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to characterize the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

[0058] Optionally, the data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and the different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or,

[0059] Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

[0060] In a seventh aspect, embodiments of the present invention provide a network-side device, including: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in the first aspect above.

[0061] Eighthly, embodiments of the present invention provide a network-side device, including: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in the second aspect above.

[0062] Ninthly, embodiments of the present invention provide a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in the first aspect; or the computer program, when executed by a processor, implements the steps of the method described in the second aspect.

[0063] In this embodiment of the invention, the first network-side device sends PDCP data and associated identification information to the second network-side device during the cell handover preparation phase. This enables the second network-side device to determine the QoS flow identifier based on the associated identification information and schedule the PDCP data, thereby reducing data transmission latency. Attached Figure Description

[0064] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0065] Figure 1 This is a flowchart of a cell handover method provided in an embodiment of the present invention;

[0066] Figure 2 This is a schematic diagram of a cell handover provided in an embodiment of the present invention;

[0067] Figure 3 This is a structural diagram of the handover preparation information provided in an embodiment of the present invention;

[0068] Figure 4 This is a flowchart of a cell handover method provided in an embodiment of the present invention;

[0069] Figure 5 This is a schematic diagram of the structure of a network-side device provided in an embodiment of the present invention;

[0070] Figure 6 This is a schematic diagram of the structure of a network-side device provided in an embodiment of the present invention;

[0071] Figure 7 This is a schematic diagram of the structure of a network-side device provided in an embodiment of the present invention;

[0072] Figure 8 This is a schematic diagram of the structure of a network-side device provided in an embodiment of the present invention. Detailed Implementation

[0073] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0074] Please see Figure 1 , Figure 1 This is a flowchart of a cell handover method provided in an embodiment of the present invention, executed by a first network-side device, such as... Figure 1 As shown, it includes the following steps:

[0075] Step 101: During the cell handover preparation phase, Packet Data Convergence Protocol (PDCP) data and associated identification information are sent to the second network-side device via the Xn interface. The associated identification information is used to indicate the association between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier.

[0076] The first network-side device and / or the second network-side device can be a base station, an Access and Mobility Management Function (AMF), a relay, an access point, or other network elements. Specifically, in this embodiment, the first network-side device is the source base station (Source gNB) during the cell handover process, and the second network-side device is the target base station (Target gNB) during the cell handover process. It should be understood that the cell handover process of the terminal is as follows: Figure 2 As shown, during the cell handover preparation phase, the target base station sends a cell handover request confirmation message to the source base station. At this time, the source base station sends PDCP data and associated identification information to the target base station.

[0077] It should be understood that QoS stream identifiers correspond to data streams of different importance levels, including data streams in different time domains, such as I-frame, P-frame, and B-frame data streams; and / or, data streams in different spatial domains, such as primary and secondary view data streams. The first network-side device and / or the second network-side device perform differentiated transmission of data streams of different importance levels to ensure the quality of service for high-bandwidth services.

[0078] It should be understood that PDCP data includes data corresponding to QoS flow identifiers. The first network-side device sends association identifier information to the second network-side device, enabling the second network-side device to determine the QoS flow identifiers corresponding to the SNs of different PDCN data through the association identifier information, and then schedule PDCP data according to the QoS flow identifiers.

[0079] In this embodiment, the first network-side device sends PDCP data and associated identification information to the second network-side device during the cell handover preparation phase. This enables the second network-side device to determine the QoS flow identifier based on the associated identification information and schedule the PDCP data, thereby reducing data transmission latency.

[0080] In one embodiment, the QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain;

[0081] The association identification information includes the association relationship between the data stream identifiers of service frames in different time domains and the SN of the PDCP data, and / or the association relationship between the data stream identifiers of different spatial domains in service frames in the same time domain and the SN of the PDCN data.

[0082] It should be understood that data streams are divided according to the time domain into I-frame, P-frame, and B-frame data streams; and according to the spatial domain into primary view and secondary view data streams. Different data streams have different levels of importance and correspond to different data stream identifiers.

[0083] For example, the primary view data stream identifier is set to 0, and the secondary view data stream identifier is set to 1. The association between the data stream identifiers in different spatial domains and the SN of PDCN data is shown in the table below:

[0084]

[0085] In the table above, the PDCP data sequence number is associated with the data stream identifiers in different spatial domains within the same time domain service frame. This allows the second network-side device to quickly determine the identifier of the data stream by associating the identifier information, identifying whether it is a primary or secondary viewpoint data stream, and then scheduling the data stream according to the corresponding importance level.

[0086] It should be understood that the data stream identifiers of service frames in different time domains are associated with the SN of PDCP data. For example, the data stream identifier of I frame is associated with PDCP SN=9, the data stream identifier of P frame is associated with PDCP SN=10, and the data stream identifier of B frame is associated with PDCP SN=11. This enables the second network-side device to quickly determine the identifiers of data streams in different time domains through the associated identifier information, and then schedule the data streams according to the corresponding importance level.

[0087] In this context, data streams in different spatial domains are identified in the PDCP data packet PDU and associated with the PDCP data SN; data streams in different temporal domain service frames are identified in the Information Element (IE) of the preparation information, and the IE is associated with the PDCP data SN. The structure of the IE is as follows: Figure 3 As shown.

[0088] In one embodiment, the data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to characterize the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

[0089] For example, the data format of a PDU is shown in the table below:

[0090]

[0091]

[0092] The reserved bits are designated R. These reserved bits are used to represent data stream identifiers for service frames in different time domains, or to represent data stream identifiers for different spatial domains within service frames in the same time domain. For example, data stream identifiers for different spatial domains within service frames in the same time domain include a primary view data stream identifier and a secondary view data stream identifier. The primary view data stream identifier is set as follows:

[0093]

[0094] Set the secondary view data stream identifier as follows:

[0095]

[0096] It should be understood that by adjusting the data format corresponding to the PDU, data stream identifiers are used to represent service frames in different time domains, or to represent data stream identifiers in different spatial domains within service frames in the same time domain. This enables the first network-side device and / or the second network-side device to determine the importance level of the data stream based on the data stream identifier and to schedule the data stream according to the importance level, thereby ensuring the service quality of high-bandwidth services.

[0097] In one embodiment, data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and these different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or

[0098] Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

[0099] It should be understood that data streams in different spatial domains within the same time domain service frame are mapped to different IPs, and different IPs correspond to different ports on the first network side device and / or the second network side. Data streams of different importance levels are transmitted through different ports to ensure the service quality of high-bandwidth services.

[0100] Please see Figure 4 , Figure 4 This is a flowchart of a cell handover method provided in an embodiment of the present invention, executed by a second network-side device, such as... Figure 4 As shown, it includes the following steps:

[0101] Step 401: During the cell handover preparation phase, the Packet Data Convergence Protocol (PDCP) data and association identification information sent by the first network-side device are received through the Xn interface. The association identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier.

[0102] Step 402: Schedule the PDCP data according to the associated identification information.

[0103] In one embodiment, the QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain;

[0104] The association identification information includes the association relationship between the data stream identifier of service frames in different time domains and the SN of PDCP data, and / or the association relationship between the data stream identifier of different spatial domains in service frames in the same time domain and the SN of PDCN data.

[0105] In one embodiment, scheduling the PDCP data based on the associated identification information includes:

[0106] The first scheduling weight is determined based on the number of data packets corresponding to the data stream identifiers of service frames in different time domains and the number of PDCP data packets received by the second network-side device.

[0107] The second scheduling weight is determined based on the number of data packets corresponding to the data stream identifiers in different spatial domains within the same time domain service frame;

[0108] The PDCP data is scheduled according to the first scheduling weight and the second scheduling weight.

[0109] It should be understood that the first scheduling weight is the inter-frame scheduling weight for different services. For example, the first scheduling weight is determined by the following formula:

[0110] First scheduling weight = Number of data packets already received by the second network-side device / Total number of PDCP data packets × Proportional Fairness (PF) scheduling parameters × 5G QoS Identifier (5QI) scheduling weight

[0111] The total number of PDCP packets is determined by the data stream identifier of the service frame. When scheduling PDCP packets on the second network side, the PDCP data is scheduled according to the first scheduling weight to ensure the integrity scheduling at the service frame level.

[0112] It should be understood that the second scheduling weight is the scheduling weight within the same service frame. For example, the second scheduling weight is determined by the following formula:

[0113] Second scheduling weight = 5QI scheduling weight × PF scheduling parameter

[0114] When scheduling data packets within the same service frame on the second network side, PDCP data is scheduled according to the second scheduling weight to ensure QoS flow continuity and reduce transmission latency.

[0115] In one embodiment, the data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to characterize the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

[0116] In one embodiment, data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and these different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or

[0117] Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

[0118] It should be noted that this embodiment is as a comparison with... Figure 1 The implementation methods of the network-side devices shown in the embodiments can be found in the following examples. Figure 1 To avoid repetition, the relevant descriptions in the embodiments shown will not be repeated in this embodiment.

[0119] The cell handover method of this invention can reduce the latency of cell handover by enabling the second network-side device to determine the QoS flow identifier through the association identifier.

[0120] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of a network-side device provided in an embodiment of the present invention, such as... Figure 5 As shown, the network-side device 500 includes:

[0121] The sending module 501 is used to send Packet Data Convergence Protocol (PDCP) data and associated identification information to the second network-side device through the Xn interface during the cell handover preparation phase. The associated identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier.

[0122] In one embodiment, the association identification information includes the association relationship between the data stream identifiers of service frames in different time domains and the SN of the PDCP data, and / or the association relationship between the data stream identifiers of different spatial domains in service frames in the same time domain and the SN of the PDCN data.

[0123] In one embodiment, the data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to characterize the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

[0124] In one embodiment, data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and these different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or

[0125] Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

[0126] The network-side device is capable of implementing each process of the above-described location verification method applied to the first network-side device. The technical features are one-to-one and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0127] Please see Figure 6 , Figure 6 This is a schematic diagram of the structure of a network-side device provided in an embodiment of the present invention, such as... Figure 6 As shown, the network-side device 600 includes:

[0128] The receiving module 601 is used to receive Packet Data Convergence Protocol (PDCP) data and association identification information sent by the first network-side device through the Xn interface during the cell handover preparation phase. The association identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier.

[0129] Processing module 602 is used to schedule the PDCP data according to the associated identification information.

[0130] In one embodiment, the QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain;

[0131] The association identification information includes the association relationship between the data stream identifier of service frames in different time domains and the SN of PDCP data, and / or the association relationship between the data stream identifier of different spatial domains in service frames in the same time domain and the SN of PDCN data.

[0132] In one embodiment, the processing module 602 includes:

[0133] The first processing unit is used to determine the first scheduling weight based on the number of data packets corresponding to the data stream identifiers of service frames in different time domains and the number of PDCP data packets received by the second network-side device.

[0134] The second processing unit is used to determine the second scheduling weight based on the number of data packets corresponding to the data stream identifiers of different spatial domains in the same time domain service frame;

[0135] The third processing unit is used to schedule the PDCP data according to the first scheduling weight and the second scheduling weight.

[0136] In one embodiment, the data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to characterize the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

[0137] In one embodiment, data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and these different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or

[0138] Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

[0139] The network-side device is capable of implementing each process of the above-described location verification method applied to the second network-side device. The technical features are one-to-one and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0140] For details, see Figure 7 The present invention also provides a network-side device, including a bus 701, a transceiver 702, an antenna 703, a bus interface 704, a processor 705, and a memory 706.

[0141] The transceiver 702 is used to send Packet Data Convergence Protocol (PDCP) data and associated identification information to the second network-side device through the Xn interface during the cell handover preparation phase. The associated identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier.

[0142] In one embodiment, the association identification information includes the association relationship between the data stream identifiers of service frames in different time domains and the SN of the PDCP data, and / or the association relationship between the data stream identifiers of different spatial domains in service frames in the same time domain and the SN of the PDCN data.

[0143] In one embodiment, the data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to characterize the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

[0144] In one embodiment, data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and these different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or

[0145] Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

[0146] exist Figure 7 In this document, a bus architecture (represented by bus 701) is used. Bus 701 can include any number of interconnected buses and bridges, linking various circuits including one or more processors represented by processor 705 and memory represented by memory 706. Bus 701 can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 704 provides an interface between bus 701 and transceiver 702. Transceiver 702 can be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by processor 705 is transmitted over a wireless medium via antenna 703, which further receives data and transmits data to processor 705.

[0147] Processor 705 manages bus 701 and general processing, and also provides various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. Memory 706 can be used to store data used by processor 705 during operation.

[0148] Optionally, the processor 705 can be a CPU, ASIC, FPGA, or CPLD.

[0149] This invention also provides a computer-readable storage medium storing a computer program. When executed by a processor, this computer program implements the various processes of the above-described location verification method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0150] This invention also provides a network-side device, including: a processor, a memory, and a program stored in the memory and executable on the processor. When the program is executed by the processor, it implements the various processes of the above-described location verification method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0151] For details, see Figure 8The present invention also provides a network-side device, including a bus 801, a transceiver 802, an antenna 803, a bus interface 804, a processor 805, and a memory 806.

[0152] The transceiver 802 is used to receive Packet Data Convergence Protocol (PDCP) data and association identification information sent by the first network-side device through the Xn interface during the cell handover preparation phase. The association identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier.

[0153] The processor 805 is used to schedule the PDCP data according to the associated identification information.

[0154] In one embodiment, the QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain;

[0155] The association identification information includes the association relationship between the data stream identifier of service frames in different time domains and the SN of PDCP data, and / or the association relationship between the data stream identifier of different spatial domains in service frames in the same time domain and the SN of PDCN data.

[0156] In one embodiment, the processor 805 is further configured to determine a first scheduling weight based on the number of data packets corresponding to the data stream identifiers of service frames in different time domains and the number of PDCP data packets received by the second network-side device;

[0157] The second scheduling weight is determined based on the number of data packets corresponding to the data stream identifiers in different spatial domains within the same time domain service frame;

[0158] The PDCP data is scheduled according to the first scheduling weight and the second scheduling weight.

[0159] In one embodiment, the data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to characterize the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

[0160] In one embodiment, data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and these different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or

[0161] Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

[0162] exist Figure 8 In this document, a bus architecture (represented by bus 801) is used. Bus 801 can include any number of interconnected buses and bridges, linking various circuits including one or more processors represented by processor 805 and memory represented by memory 806. Bus 801 can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 804 provides an interface between bus 801 and transceiver 802. Transceiver 802 can be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by processor 805 is transmitted over a wireless medium via antenna 803, which further receives data and transmits data to processor 805.

[0163] The processor 805 manages the bus 801 and handles general processing, and also provides various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 806 can be used to store data used by the processor 805 during operation.

[0164] Optionally, the processor 805 can be a CPU, ASIC, FPGA, or CPLD.

[0165] This invention also provides a computer-readable storage medium storing a computer program. When executed by a processor, this computer program implements the various processes of the above-described location verification method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0166] This invention also provides a network-side device, including: a processor, a memory, and a program stored in the memory and executable on the processor. When the program is executed by the processor, it implements the various processes of the above-described location verification method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0167] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0168] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods of the various embodiments of the present invention.

[0169] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of the present invention.

Claims

1. A cell handover method, executed by a first network-side device, characterized in that, include: During the cell handover preparation phase, Packet Data Convergence Protocol (PDCP) data and associated identification information are sent to the second network-side device via the Xn interface. The associated identification information is used to indicate the association between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier. The QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain; The association identification information includes the association relationship between the data stream identifiers of service frames in different time domains and the SN of the PDCP data, and / or the association relationship between the data stream identifiers of different spatial domains in service frames in the same time domain and the SN of the PDCP data; The second network-side device is used to determine the first scheduling weight based on the number of data packets corresponding to the data stream identifiers of service frames in different time domains and the number of PDCP data packets received by the second network-side device; And, for determining a second scheduling weight based on the number of data packets corresponding to data stream identifiers in different spatial domains within the same time domain service frame; and for scheduling the PDCP data based on the first scheduling weight and the second scheduling weight.

2. The method according to claim 1, characterized in that, The data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to represent the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

3. The method according to claim 1, characterized in that, Data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and these different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or, Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

4. A cell handover method, executed by a second network-side device, characterized in that, include: During the cell handover preparation phase, the Packet Data Convergence Protocol (PDCP) data and association identification information sent by the first network-side device are received through the Xn interface. The association identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier. The PDCP data is scheduled according to the associated identification information; The QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain; The association identification information includes the association relationship between the data stream identifier of service frames in different time domains and the SN of PDCP data, and / or the association relationship between the data stream identifier of different spatial domains in service frames in the same time domain and the SN of PDCP data; The step of scheduling the PDCP data according to the associated identifier information includes: The first scheduling weight is determined based on the number of data packets corresponding to the data stream identifiers of service frames in different time domains and the number of PDCP data packets received by the second network-side device. The second scheduling weight is determined based on the number of data packets corresponding to the data stream identifiers in different spatial domains within the same time domain service frame; The PDCP data is scheduled according to the first scheduling weight and the second scheduling weight.

5. The method according to claim 4, characterized in that, The data format corresponding to the Protocol Data Unit (PDU) of the PDCP data includes reserved bits, which are used to represent the data stream identifier of service frames in different time domains, or the data stream identifier of different spatial domains in service frames in the same time domain.

6. The method according to claim 4, characterized in that, Data streams of service frames in different time domains correspond to different Internet Protocol (IP) addresses, and these different IP addresses correspond to different ports of the first network-side device and / or the second network-side device; and / or, Data streams in different spatial domains within the same time domain service frame correspond to different IPs, and the different IPs correspond to different ports of the first network-side device and / or the second network-side device.

7. A network-side device, characterized in that, include: The sending module is used to send Packet Data Convergence Protocol (PDCP) data and association identification information to the second network-side device through the Xn interface during the cell handover preparation phase. The association identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier. The QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain; The association identification information includes the association relationship between the data stream identifiers of service frames in different time domains and the SN of the PDCP data, and / or the association relationship between the data stream identifiers of different spatial domains in service frames in the same time domain and the SN of the PDCP data; The second network-side device is used to determine the first scheduling weight based on the number of data packets corresponding to the data stream identifiers of service frames in different time domains and the number of PDCP data packets received by the second network-side device; And, for determining a second scheduling weight based on the number of data packets corresponding to data stream identifiers in different spatial domains within the same time domain service frame; and for scheduling the PDCP data based on the first scheduling weight and the second scheduling weight.

8. A network-side device, characterized in that, include: The receiving module is used to receive Packet Data Convergence Protocol (PDCP) data and association identification information sent by the first network-side device through the Xn interface during the cell handover preparation phase. The association identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier. The processing module is used to schedule the PDCP data according to the associated identification information; The QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain; The association identification information includes the association relationship between the data stream identifier of service frames in different time domains and the SN of PDCP data, and / or the association relationship between the data stream identifier of different spatial domains in service frames in the same time domain and the SN of PDCP data; The processing module includes: The first processing unit is used to determine the first scheduling weight based on the number of data packets corresponding to the data stream identifiers of service frames in different time domains and the number of PDCP data packets received by the network-side device. The second processing unit is used to determine the second scheduling weight based on the number of data packets corresponding to the data stream identifiers of different spatial domains in the same time domain service frame; The third processing unit is used to schedule the PDCP data according to the first scheduling weight and the second scheduling weight.

9. A network-side device, characterized in that, Including transceivers and processors, The transceiver is used to send Packet Data Convergence Protocol (PDCP) data and association identification information to the second network-side device through the Xn interface during the cell handover preparation phase. The association identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier. The QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain; The association identification information includes the association relationship between the data stream identifiers of service frames in different time domains and the SN of the PDCP data, and / or the association relationship between the data stream identifiers of different spatial domains in service frames in the same time domain and the SN of the PDCP data; The second network-side device is used to determine the first scheduling weight based on the number of data packets corresponding to the data stream identifiers of service frames in different time domains and the number of PDCP data packets received by the second network-side device; And, for determining a second scheduling weight based on the number of data packets corresponding to data stream identifiers in different spatial domains within the same time domain service frame; and for scheduling the PDCP data based on the first scheduling weight and the second scheduling weight.

10. A network-side device, characterized in that, Including transceivers and processors, The transceiver is used to receive Packet Data Convergence Protocol (PDCP) data and association identification information sent by the first network-side device through the Xn interface during the cell handover preparation phase. The association identification information is used to indicate the association relationship between the sequence number (SN) of the PDCP data and the Quality of Service (QoS) flow identifier. The processor is used to schedule the PDCP data according to the associated identification information; The QoS stream identifier includes data stream identifiers of service frames in different time domains, and / or data stream identifiers of service frames in different spatial domains within the same time domain; The association identification information includes the association relationship between the data stream identifier of service frames in different time domains and the SN of PDCP data, and / or the association relationship between the data stream identifier of different spatial domains in service frames in the same time domain and the SN of PDCP data; The step of scheduling the PDCP data according to the associated identifier information includes: The first scheduling weight is determined based on the number of data packets corresponding to the data stream identifiers of service frames in different time domains and the number of PDCP data packets received by the network-side device. The second scheduling weight is determined based on the number of data packets corresponding to the data stream identifiers in different spatial domains within the same time domain service frame; The PDCP data is scheduled according to the first scheduling weight and the second scheduling weight.

11. A network-side device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method as described in any one of claims 1 to 3.

12. A network-side device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method as described in any one of claims 4 to 6.

13. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any one of the methods of claims 1 to 3; or when executed by a processor, implements the steps of any one of the methods of claims 4 to 6.

Images