Communication method and apparatus

Abstract

Provided in the present application are a communication method and apparatus. The method comprises: a first access network device receiving first information from a core network device, and sending second information to a second access network device, wherein the first information is used for indicating the size of a first data burst, the second information is used for indicating the size of a second data burst, and the second data burst is a data burst in the first data burst that is distributed to the second access network device. The first access network device sends the second information to the second access network device, such that the second access network device can learn of in a timely manner the size of the second data burst distributed to the second access network device, the second access network device can use the size of the second data burst to accurately schedule the second data burst, and the second access network device can accurately reserve a corresponding resource on the basis of the size of the second data burst, so as to ensure timely and effective scheduling of the second data burst.

Description

A communication method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510229502.X, filed on February 27, 2025, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] With the development of communication technology, access network equipment can provide burst-based services for extended reality (XR) services. Before providing burst-based services, access network equipment can obtain information related to data bursts from core network equipment, which can be used to assist access network equipment in scheduling data bursts.

[0005] However, in dual-connectivity scenarios, a terminal device can connect to two access network devices simultaneously, such as access network device A and access network device B. Taking access network device A obtaining a data burst from the core network device as an example, the data packets included in the data burst obtained by access network device A from the core network device may be diverted to access network device B. Since only access network device A obtains information related to the data burst, while access network device B does not, access network device B cannot use the information related to the data burst for data burst scheduling, resulting in inaccurate data burst scheduling.

[0006] How to achieve accurate scheduling of data bursts requires further research. Summary of the Invention

[0007] This application provides a communication method and apparatus for accurately scheduling data bursts.

[0008] Firstly, this application provides a communication method that can be executed by a first access network device or a module within the first access network device (e.g., a communication module, a circuit or chip responsible for communication functions (such as a modem chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip), a chip system, or a processor, etc.). Optionally, the method can also be implemented by a logical node, logical module, or software capable of implementing all or part of the functions of the first access network device. The following example illustrates the communication method executed by the first access network device. The method may include the following steps: the first access network device receives first information from a core network device; subsequently, the first access network device may send second information to a second access network device, wherein the first information indicates the size of a first data burst, the second information indicates the size of a second data burst, and the second data burst is a data burst from the first data burst that is diverted to the second access network device (this can refer to a data burst formed by part or all of the data packets diverted to the second access network device from the first data burst).

[0009] In this method, the first access network device sends second information to the second access network device, enabling the second access network device to promptly obtain the size of the second data burst allocated to it. This allows the second access network device to accurately schedule the second data burst based on its size and to accurately reserve corresponding (or matching) resources for its scheduling. In other words, it facilitates resource reservation and scheduling arrangements based on the size of the second data burst, ensuring timely and effective transmission (or scheduling). Furthermore, this method can also enable the first access network device to accurately indicate the size of the data burst (i.e., the size of the data packets allocated to the second access network device from the multiple data packets included in the first data burst) based on the distribution ratio of the first data burst (e.g., the proportion of data packets or data volume allocated to the second access network device from the multiple data packets included in the first data burst), thus assisting the second access network device in accurately scheduling the allocated data packets. It should be understood that the first access network device can also use the size of other data packets in the first data burst (excluding the second data burst) to accurately schedule other data packets, and can also accurately reserve corresponding resources for the scheduling of other data packets based on the size of other data packets, so as to ensure the timely and effective transmission of other data packets.

[0010] In one possible implementation, the method further includes: a first access network device receiving third information from a core network device, wherein the third information is used to indicate the arrival time of a third data burst, the third data burst being located after the first data burst; and after receiving the third information, the first access network device may send fourth information to a second access network device, wherein the fourth information is used to indicate the arrival time of the third data burst.

[0011] In the above implementation, the first access network device sends fourth information to the second access network device, enabling the second access network device to promptly perceive or obtain the arrival time of the third data burst and more rationally perform sleep mode or instruct terminal devices to sleep mode. This helps prevent the second access network device from waiting indefinitely for data from the first access network device due to the inability to obtain the arrival time of the third data burst, thus facilitating energy-saving optimization for the second access network device or terminal device and effectively reducing their energy consumption. Furthermore, this implementation also allows the second access network device to make early resource reservation and other scheduling arrangements based on the fourth information to ensure the timely and effective transmission of offloaded data. It should be understood that the first access network device can also more rationally perform sleep mode based on the arrival time of the third data burst, or it can instruct terminal devices to sleep mode based on the arrival time of the third data burst, thereby facilitating energy-saving optimization for the first access network device or terminal device and effectively reducing their energy consumption. Additionally, the first access network device can also make early resource reservation and other scheduling arrangements based on the arrival time of the third data burst to ensure the timely and effective transmission of data it needs to transmit.

[0012] Secondly, this application provides a communication method, which can be executed by a second access network device or a module in the second access network device (e.g., a communication module, a circuit or chip responsible for communication functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.). Optionally, the method can also be implemented by a logical node, logical module, or software capable of implementing all or part of the functions of the second access network device. The following example illustrates the communication method executed by the second access network device. The method may include the following steps: the second access network device receives second information from a first access network device, wherein the second information indicates the size of a second data burst, and the second data burst is a data burst that is diverted from the first data burst received by the first access network device to the second access network device.

[0013] The technical effects achievable in the second aspect are similar to those achievable in the first aspect, and will not be elaborated upon here.

[0014] In one possible implementation, the method further includes: a second access network device receiving fourth information from a first access network device, wherein the fourth information is used to indicate the arrival time of a third data burst, the third data burst being located after the first data burst.

[0015] The technical effects achievable by the above implementation method can be referred to the technical effects achievable by the corresponding implementation method provided in the first aspect above, and will not be repeated here.

[0016] Based on the first or second aspect, in one possible implementation, the fourth information may also be used to indicate that the first data burst has ended, or the fourth information may also be used to indicate that the size of the first data burst is 0.

[0017] In the above implementation, if the first data burst is not diverted to the second access network device, by indicating to the second access network device that the first data burst has ended or that the size of the first data burst is 0, the second access network device can promptly determine that it will no longer receive data packets from the first data burst, thus allowing it to enter sleep mode in advance and helping to improve energy efficiency.

[0018] Based on the first or second aspect, in one possible implementation, the fourth information can be carried in the header of an empty data packet.

[0019] In the above implementation, by carrying the fourth information in the header of the empty data packet, the second access network device can obtain the fourth information earlier (or quickly or timely), which can facilitate the second access network device to make resource reservation and other scheduling arrangements in advance to ensure timely and effective data transmission.

[0020] Based on the first or second aspect, in one possible implementation, the fourth information may be carried in the header of the last p data packets included in the second data burst, where p is an integer greater than or equal to 1.

[0021] In the above implementation, when the first data burst is diverted to the second access network device, by carrying fourth information in the header of the last one or more data packets included in the second data burst, the second access network device can more accurately determine the sleep duration. That is, it is easier for the second access network device to know more clearly when to enter sleep and when to end sleep, so that the timing of the second access network device entering sleep is more reasonable and more accurate.

[0022] Based on the first or second aspect, in one possible implementation, the second information may be carried in the header of the first data packet included in the second data burst.

[0023] In the above implementation, by carrying the second information in the header of the first data packet included in the second data burst, the second access network device can know (or sense) the size of the second data burst that is diverted to the second access network device earlier, thereby facilitating the second access network device to make scheduling arrangements such as resource reservation in advance, for example, reserving corresponding resources for the scheduling of the second data burst in advance.

[0024] Thirdly, this application provides a communication method, which can be executed by a first access network device or a module in the first access network device (e.g., a communication module, a circuit or chip responsible for communication functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.). Optionally, the method can also be implemented by a logical node, logical module, or software capable of implementing all or part of the functions of the first access network device. The following example illustrates the execution of the communication method by the first access network device. The method may include the following steps: the first access network device receives third information from a core network device, wherein the third information indicates the arrival time of a third data burst, the third data burst being located after the first data burst; subsequently, the first access network device may send fourth information to a second access network device, wherein the fourth information indicates the arrival time of the third data burst.

[0025] The technical effects achievable in the third aspect are similar to those achieved by the corresponding implementation method provided in the first aspect above, and will not be elaborated upon here.

[0026] In one possible implementation, the method further includes: a first access network device receiving first information from a core network device, and then the first access network device sending second information to a second access network device, wherein the first information is used to indicate the size of a first data burst, the second information is used to indicate the size of a second data burst, and the second data burst is a data burst that is diverted from the first data burst to the second access network device.

[0027] The technical effects achievable by the above implementation method can be referred to the technical effects achievable by the corresponding implementation method provided in the first aspect above, and will not be repeated here.

[0028] Fourthly, this application provides a communication method that can be executed by a second access network device or a module within the second access network device (e.g., a communication module, a circuit or chip responsible for communication functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.). Optionally, the method can also be implemented by a logical node, logical module, or software capable of implementing all or part of the functions of the second access network device. The following example illustrates the execution of the communication method by the second access network device. The method may include the following steps: the second access network device receives fourth information from a first access network device, wherein the fourth information indicates the arrival time of a third data burst, the third data burst being located after the first data burst.

[0029] The technical effects achievable in the fourth aspect are similar to those achieved by the corresponding implementation methods provided in the first aspect above, and will not be elaborated upon here.

[0030] In one possible implementation, the method further includes: a second access network device receiving second information from a first access network device, wherein the second information is used to indicate the size of a second data burst, the second data burst being a data burst that is diverted from a first data burst received by the first access network device to the second access network device.

[0031] Based on the third or fourth aspect, in one possible implementation, the second information may be carried in the header of the first data packet included in the second data burst.

[0032] Based on the third or fourth aspect, in one possible implementation, the fourth information can also be used to indicate that the first data burst has ended, or the fourth information can also be used to indicate that the size of the first data burst is 0.

[0033] Based on the third or fourth aspect, in one possible implementation, the fourth information can be carried in the header of an empty data packet.

[0034] Based on the third or fourth aspect, in one possible implementation, the fourth information can be carried in the header of the last p data packets included in the second data burst, where p is an integer greater than or equal to 1.

[0035] The technical effects achievable by the above implementation methods can be referred to the corresponding implementation methods provided in the first or second aspect above, and will not be repeated here.

[0036] Fifthly, this application provides a communication device that implements the functions described in the first to fourth aspects above. For example, the communication device includes modules, units, or means corresponding to the operations described in the first to fourth aspects above. These functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software. For instance, in some examples, the communication device can be a first access network device or a module within a first access network device, and the communication device has the functions described in the first or third aspects above. In other examples, the communication device can be a second access network device or a module within a second access network device, and the communication device has the functions described in the second or fourth aspects above.

[0037] In one possible implementation, the communication device may include a transceiver unit. Optionally, the communication device may further include a processing unit. The transceiver unit can be used to transmit and receive signals to enable communication between the communication device and other devices; for example, the transceiver unit can be used to send data to other communication devices. The processing unit can be used to perform some internal operations of the communication device. The functions performed by the transceiver unit and the processing unit may correspond to the operations involved in the first to fourth aspects described above.

[0038] In one possible implementation, the communication device includes at least one processor, which can be coupled to a memory. The memory can store necessary computer programs or instructions for implementing the functions described in the first to fourth aspects above. The processor can execute the computer programs or instructions stored in the memory, causing the communication device to implement the methods in any possible implementation of any of the first to fourth aspects above when the computer programs or instructions are executed.

[0039] In one possible implementation, the communication device includes at least one processor and a memory, the memory of which may store necessary computer programs or instructions for implementing the functions involved in the first to fourth aspects described above. The at least one processor may execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication device to implement the methods in any possible implementation of any of the first to fourth aspects described above.

[0040] In one possible implementation, the communication device includes at least one processor and an interface circuit (or communication interface), wherein the at least one processor is configured to communicate with other devices via the interface circuit and execute the methods in any of the possible implementations of any of the first to fourth aspects described above. The interface circuit is used to enable communication between the communication device and other devices, for example, to receive signals from other communication devices and transmit them to the at least one processor, or to send signals from the at least one processor of the communication device to other communication devices, such as the transmission or reception of data and / or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0041] It is understood that, in the fifth aspect mentioned above, the processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. Furthermore, there can be one or more processors, and one or more memories. The memory can be integrated with the processor, or the memory and processor can be separate. In specific implementations, the memory can be integrated with the processor on the same chip, or it can be set on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0042] Sixthly, this application provides a possible communication system that may include a first access network device and a second access network device. Optionally, it may also include core network equipment.

[0043] In one implementation method, the first access network device can implement the first aspect or any implementation method of the first aspect, and the second access network device can implement the second aspect or any implementation method of the second aspect. When the communication system includes a core network device, the core network device is used to execute the first aspect, the second aspect, any implementation method of the first aspect, or any implementation method of the second aspect.

[0044] In another implementation, the first access network device can implement the third aspect or any implementation of the third aspect described above, and the second access network device can implement the fourth aspect or any implementation of the fourth aspect described above. When the communication system includes core network equipment, the core network equipment is used to execute the third aspect, the fourth aspect, any implementation of the third aspect, or any implementation of the fourth aspect described above.

[0045] For example, the number of first access network devices, second access network devices, or core network devices can be one or more.

[0046] In a seventh aspect, this application provides a computer program product comprising a computer program or instructions that, when executed on a communication device (or computer), cause the communication device (or computer) to perform the method in any possible implementation of any of the first to fourth aspects described above.

[0047] Eighthly, this application provides a computer-readable storage medium storing a computer program or instructions that, when executed by a communication device (or computer), cause the communication device (or computer) to perform the method in any possible implementation of any of the first to fourth aspects described above.

[0048] Ninthly, this application provides a chip that may include at least one processor and may also include a memory (or the chip may be coupled to the memory), wherein the at least one processor executes program instructions in the memory to cause the chip to perform any possible implementation of any of the first to fourth aspects described above. Here, "coupling" means that two components are directly or indirectly connected to each other, such as coupling can refer to an electrical connection between two components.

[0049] In a tenth aspect, this application also provides a chip system including at least one processor for supporting a computer device in implementing any possible implementation of the methods in any of the first to fourth aspects described above. In one possible implementation, the chip system further includes a memory for storing programs and data necessary for the computer device. The chip system may be composed of chips or may include chips and other discrete devices.

[0050] Based on the implementation methods provided in the above aspects, this application can be further combined to provide more implementation methods. Attached Figure Description

[0051] Figure 1 illustrates, by way of example, a schematic diagram of the relationship between a data burst and a PDU set provided in an embodiment of this application;

[0052] Figures 2a to 2d exemplarily illustrate several scenario diagrams of the MR-DC architecture provided in the embodiments of this application;

[0053] Figure 3 illustrates, by way of example, several bearer types supported by an MR-DC architecture provided in an embodiment of this application;

[0054] Figure 4 illustrates a possible architecture diagram of a communication system provided in an embodiment of this application.

[0055] Figure 5 illustrates an exemplary architecture diagram of an access network device provided in an embodiment of this application;

[0056] Figure 6 illustrates a flowchart of a communication method provided in an embodiment of this application;

[0057] Figure 7a is an exemplary schematic diagram of a DBS indication for a bearer type terminated at MN supported by an MR-DC architecture provided in an embodiment of this application.

[0058] Figure 7b is an exemplary schematic diagram of a DBS indication for a bearer type terminated at the SN, supported by an MR-DC architecture provided in an embodiment of this application.

[0059] Figure 8a is an exemplary schematic diagram of a TTNB indication for a MR-DC architecture provided in this application, where the bearer type is a separate bearer terminated at MN.

[0060] Figure 8b is an exemplary schematic diagram of a TTNB indication for a bearer type terminated at the SN, supported by an MR-DC architecture according to an embodiment of this application.

[0061] Figure 9 illustrates a flowchart of another communication method provided in an embodiment of this application;

[0062] Figure 10 illustrates a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0063] Figure 11 illustrates a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0064] Before introducing the technical solutions provided in this application, some of the terms used in this application will be explained in order to facilitate understanding by those skilled in the art.

[0065] (1) XR services:

[0066] XR refers to various environments that combine reality and virtuality, generated by computing technology and wearable devices, as well as human-computer interaction. Specifically, it includes several typical forms: Augmented Reality (AR), Mixed Reality (MR), and Virtual Reality (VR). XR is currently one of the key 5G multimedia applications being considered in the industrial sector. Typically, XR services generate data frames periodically at a certain frame rate. Taking an AR service with a frame rate of 60 frames per second (fps) as an example, 60 frames of video images are generated per second, with one video frame appearing approximately every 16.66 milliseconds (ms). A single video frame may be transmitted via multiple data packets.

[0067] One video frame can correspond to one data burst. In other words, multiple data packets used to transmit one video frame can constitute one data burst. One video frame can correspond to one or more protocol data unit (PDU) sets. In other words, multiple data packets used to transmit one video frame can be divided into one or more PDU sets (or PDU collections). Therefore, a data burst can include one or more PDU sets. Different video frames can be the same or different in size. Correspondingly, the number of PDU sets included in data bursts transmitted in different periods can be the same or different. Figure 1 illustrates an example where the number of PDU sets included in data bursts transmitted in different periods is different. Optionally, in some embodiments, the "PDU set" shown in Figure 1 can be replaced with "data packet or PDU".

[0068] (2) Information related to data bursts (or data burst information):

[0069] Data burst information can be carried within data packets, for example, in the packet header, indicating information about the data burst associated with that data packet. A data burst can be a group of data packets generated and sent by an application within a very short period of time. For example, a data burst may include multiple data packets used to transmit a video frame; in other words, a data burst may correspond to a single video frame. Optionally, a data burst may contain one or more PDU sets.

[0070] For example, data burst information may include at least one of the following:

[0071] a. Data burst size (DBS): Represents the total size of the current data burst, expressed in bytes. For example, size can refer to the amount of data, the amount of space occupied, or the screen dimensions, etc.

[0072] b. Time to Next Burst (TTNB): This represents the time interval between the next data burst and the current data burst, such as the time interval between the arrival or generation of the last data packet of the current data burst and the arrival or generation of the first data packet of the next data burst. Based on this, access network devices can predict (or know, or determine) the arrival time of the next data burst in advance, thereby optimizing scheduling strategies.

[0073] Optionally, the data burst information may also include an end-of-data-burst identifier (EDB). The EDB indicates whether the data packet is the last data packet in its data burst. Based on this, the access network device can determine whether all data packets included in the data burst have arrived. In other words, the access network device can determine whether it will receive more data packets included in that data burst. For example, if the data packets received by the access network device include the EDB of a certain data burst, the access network device can determine that all data packets included in that data burst have arrived; in other words, the access network device can determine that it will not receive more data packets included in that data burst. If the data packets received by the access network device do not include the EDB of a certain data burst, the access network device can determine that all data packets included in that data burst have not arrived. In other words, the access network device can determine that it will receive more data packets included in that data burst.

[0074] It should be understood that the above data burst information is only an example. During the evolution of the standard, the data burst information may include more or less information, and this application does not limit this.

[0075] (3) Multi-radio dual connectivity (MR-DC):

[0076] MR-DC is a general term for dual connectivity in 5th generation (5G) communication systems. Terminal devices can simultaneously connect to two access network devices (such as base stations), such as a primary access network device or a secondary access network device. The primary access network device acts as the control anchor point, while the secondary access network device provides additional air interface transmission capabilities. Dual-connectivity terminal devices have two media access control (MAC) entities, corresponding to either the primary or secondary access network device. For example, the primary access network device could be the master node (MN), and the secondary access network device could be the secondary node (SN).

[0077] For example, the MR-DC architecture can include the following scenarios or types.

[0078] 1. Evolved Universal Terrestrial Radio Access - New Radio-DC (E-UTRA-NR DC, abbreviated as EN-DC):

[0079] Referring to Figure 2a, when the core network is an evolved packet core (EPC), the Long Term Evolution (LTE) base station acts as the primary base station, and the NR base station acts as the secondary base station. In this case, there is an X2 interface between the LTE base station (e.g., eNB) and the NR base station (e.g., gNB), providing at least a control plane connection and potentially a user plane connection. There is an S1 interface between the LTE base station and the EPC, providing at least a control plane connection and potentially a user plane connection. There is an S1-U interface between the NR base station and the EPC, providing only a user plane connection. In this case, the LTE base station can provide air interface resources to the terminal device through at least one LTE cell, which is called the master cell group (MCG). Similarly, the NR base station can also provide air interface resources to the terminal device through at least one NR cell, which is called the secondary cell group (SCG).

[0080] 2. Next-generation radio access network - Evolved Universal Terrestrial Radio Access Dual Connectivity (NG-RAN-E-UTRA DC, abbreviated as NGEN-DC):

[0081] Referring to Figure 2b, when the core network is a 5G core network (5GC), the LTE base station acts as the primary base station, and the NR base station acts as the secondary base station. At this time, there is an Xn interface between the LTE and NR base stations, providing at least a control plane connection and potentially a user plane connection. There is an NG interface between the LTE base station and the 5GC, providing at least a control plane connection and potentially a user plane connection. There is an NG-U interface between the NR base station and the 5GC, meaning only a user plane connection is possible. In this scenario, the LTE base station can provide air interface resources to the terminal device through at least one LTE cell, referred to as the MCG. Similarly, the NR base station can also provide air interface resources to the terminal device through at least one NR cell, referred to as the SCG.

[0082] 3. New Radio - Evolved Universal Terrestrial Radio Access Dual Connectivity (NR-E-UTRA DC, NE-DC):

[0083] Referring to Figure 2c, when the core network is 5GC, the NR base station acts as the primary base station, and the LTE base station acts as the secondary base station. At this time, there is an Xn interface between the NR and LTE base stations, providing at least a control plane connection and potentially a user plane connection. There is an NG interface between the NR and 5GC, providing at least a control plane connection and potentially a user plane connection. There is an NG-U interface between the LTE and 5GC, meaning only a user plane connection is possible. In this case, the NR base station can provide air interface resources to the terminal equipment through at least one NR cell, referred to as the MCG. Similarly, the LTE base station can also provide air interface resources to the terminal equipment through at least one LTE cell, referred to as the SCG.

[0084] 4. New Wireless Dual Connectivity (NR-DC):

[0085] Referring to Figure 2d, when the core network is 5GC, both the primary and secondary base stations are NR base stations. The interface between the primary and secondary base stations is the Xn interface, which has at least a control plane connection and may also have a user plane connection. There is an NG interface between the NR primary base station and the 5GC, which has at least a control plane connection and may also have a user plane connection. There is an NG-U interface between the NR secondary base station and the 5GC, meaning only a user plane connection is possible. In this case, the NR primary base station can provide air interface resources to the terminal equipment through at least one NR cell, which is called an MCG. Correspondingly, the NR secondary base station can also provide air interface resources to the terminal equipment through at least one NR cell, which is called an SCG.

[0086] It is understood that the MR-DC architecture can support multiple bearer types, as shown in Figure 3. As shown in Figure 3, the multiple bearer types may include, but are not limited to, the following.

[0087] A1, the MCG bearer terminated in MN, transmits its data through the packet data convergence protocol (PDCP) entity and the radio link control (RLC) entity / MAC entity / physical (PHY) entity located in MN.

[0088] A2, terminated in the MN's SCG bearer, carries data that is transmitted through the PDCP entity located in the MN and the RLC / MAC / PHY entity located in the SN.

[0089] A3, terminated in the split bearer of MN, carries data that is transmitted through the PDCP entity, the RLC / MAC / PHY entity and the RLC / MAC / PHY entity located in MN and the SN respectively.

[0090] A4, terminated at SN, carries data via the PDCP entity located at SN and the RLC / MAC / PHY entity located at MN.

[0091] A5, terminated on the SN's SCG bearer, carries data that is transmitted through the PDCP entity and the RLC / MAC / PHY entity located on the SN.

[0092] A6, terminated at the SN, carries data that is transmitted through the PDCP entity located at the SN, the RLC / MAC / PHY entity located at the MN, and the RLC / MAC / PHY entity located at the SN.

[0093] It is understood that the above-mentioned MCG bearer refers to a bearer that only involves MCG air interface resources. SCG bearer refers to a bearer that only involves SCG air interface resources. Split bearer refers to a bearer that involves both MCG and SCG air interface resources. MN / SN termination means that the PDCP entity is located in MN or SN.

[0094] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0095] The following describes the communication system architecture to which the communication method provided in this application is applicable. It should be noted that this description is for the convenience of those skilled in the art and is not intended to limit the scope of protection claimed in this application.

[0096] The communication scheme provided in this application can be applied to various communication systems, such as: LTE systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, sidelink (SL) communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5G communication systems or NR access technology, satellite communication systems, etc. Among them, the 5G mobile communication system can include non-standalone (NSA) and / or standalone (SA) networking. The technical solution provided in this application can also be applied to future evolved communication systems or other similar communication systems. The satellite communication system can be a satellite communication system integrated with the 4th generation (4G) communication system, 5G communication system, or future communication systems, such as a non-terrestrial network (NTN), etc. NTN communication systems can be, for example, satellite communication systems, or include unmanned aerial vehicles, high altitude platform stations (HAPS), and other aerial access network equipment; this application does not limit the scope of such systems.

[0097] In a communication system, one network element can send signals to or receive signals from another network element. These signals can include information, signaling, or data. The term "network element" can also be replaced by entities, network entities, devices, communication equipment, communication modules, nodes, communication nodes, etc.

[0098] Figure 4 illustrates an exemplary architecture of a possible communication system applicable to embodiments of this application. As shown in Figure 4, the communication system may include a core network (CN) and an access network (AN). The access network may include at least one access network device. Optionally, the access network may also include at least one terminal device. The terminal device may be, for example, the XR device shown in Figure 4. In some implementations, the terminal devices can communicate with each other via a sidelink (SL). Figure 4 illustrates an example with one access network device and two terminal devices.

[0099] Optionally, as shown in Figure 4, the communication system may also include a data network (DN). The DN can be a network located outside the mobile communication system, providing services to users. For example, the DN can be a packet data network (PDN), such as the Internet, an Internet Protocol Multimedia Service (IMS) network, a dedicated data network for certain applications, Ethernet, or an Internet Protocol (IP) local area network. The DN can deploy various services, providing data and / or voice services to terminal devices. The DN can contain multiple application servers (AS), each of which can provide at least one service.

[0100] For example, in this communication system, for downlink transmission, data generated by the application server is forwarded through the data network and sent to the core network via the N6 interface. The core network then transmits the data to the access network device via the N3 interface, and the access network device sends the data to the terminal device via the Uu air interface. The uplink transmission path is the reverse of the downlink transmission path and will not be described further.

[0101] The core network can include control plane network elements and user plane network elements. Control plane network elements include, for example, access management function network elements, unified data management network elements, session management function network elements, or policy control function network elements. User plane network elements include, for example, user plane function network elements. The following is a description of some network elements in the core network.

[0102] Access management function (AMF) network elements are responsible for access control and mobility management of terminal devices accessing the operator's network. This includes functions such as mobility state management, assigning temporary user identities, authentication, and authorization. In 5G communication systems, this AMF network element may be an Access and Mobility Management Function (AMF) network element. In future communication systems, AMF network elements may have other names, without limitation.

[0103] The unified data management network element is responsible for generating authentication credentials, processing user identifiers (such as storing and managing permanent user identities), and managing subscription data. In 5G communication systems, this unified data management network element can be a unified data management (UDM) network element. In future communication systems, this unified data management network element may have other names, without limitation.

[0104] The session management function (SMF) network element is primarily responsible for session management in mobile networks, such as session establishment, modification, and release. It can also assign Internet Protocol (IP) addresses to users and select user plane function (MPF) network elements that provide packet forwarding capabilities. In 5G communication systems, this SMF network element may be a Session Management Function (SMF) network element. In future communication systems, the SMF network element may have other names without limitation.

[0105] The policy control function network element primarily provides policy rules and is also responsible for acquiring user subscription information related to policy decisions. In 4G communication systems, this policy control function network element can be a policy and charging rules function (PCRF) network element. In 5G communication systems, this policy control function network element can be a policy control function (PCF) network element. In future communication systems, the policy control function network element may have other names, without limitation.

[0106] User plane function (UDP) network elements are responsible for receiving and forwarding user data. For example, they can receive user data from the DN (Digital Network Node) and transmit it to the terminal device through the access network equipment; UDP network elements can also receive user data from the terminal device through the access network equipment and forward it to the DN. In 5G communication systems, this UDP network element can be a user plane function (UPF) network element. In future communication systems, UDP network elements may have other names, without limitation.

[0107] The above describes some of the network elements involved in the core network. It is understood that the core network may also involve other network elements, such as one or more of the following: unified data repository (UDR) network elements, network slice selection function (NSSF) network elements, or network exposure function (NEF) network elements, etc. The term "network element" mentioned in this application can be replaced with "device." For example, core network element and core network equipment have the same meaning. Optionally, the term "network element" can be omitted from the device name mentioned in this application. For example, AMF network element and AMF have the same meaning.

[0108] Terminal equipment can also be referred to as user equipment (UE), terminal, access terminal, subscriber unit, user station, mobile station, mobile station (MS), remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent, or user device.

[0109] Terminal devices can be any device providing wireless communication capabilities, and can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, aircraft, ships, robots, robotic arms, smart home devices, etc. This application does not limit the specific technology or form of the terminal device.

[0110] In this application, the terminal device can be fixed in location or mobile, and this application does not limit it in this regard. For example, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted, or it can also be deployed on water (such as ships), or it can also be deployed in the air (such as airplanes, balloons or satellites).

[0111] An access network device is a network-side device with wireless transceiver capabilities. For example, it is a device in a radio access network (RAN) that provides wireless communication capabilities to terminal devices, and is sometimes referred to as a RAN node, RAN entity, network device, or access node. As an example, the RAN can be an access network in the 3rd Generation Partnership Project (3GPP), such as a 4G network, a 5G network (e.g., an NR network), or a future-oriented network. As another example, the RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a communication network combining two or more of these. Exemplarily, access network devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on aircraft, drones, balloons, and satellites. This application does not limit the application scenarios of the access network device.

[0112] In one possible application scenario, the access network device can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a transmission point (TP), a future base station in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. The access network device can be a macro base station, a micro base station or indoor station, a relay node or donor node, or a radio controller in a CRAN scenario. Exemplarily, the access network device can also be a server, a wearable device, a vehicle, or an in-vehicle device. For example, the access network device in V2X technology can be a roadside unit (RSU). All or part of the functions of the access network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The access network device in this application can also be a logical node, logical module, or software capable of implementing all or part of the access network device functions.

[0113] In another possible application scenario, access network equipment can be a module or unit that performs some of the functions of a base station; or multiple access network devices can collaborate to assist terminal devices in achieving wireless access, with different access network devices each performing some of the functions of a base station. For example, access network equipment can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio equipment or radio units, such as in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0114] As shown in Figure 5, in some implementations, access network equipment can adopt a CU-DU separation architecture, where the access network equipment can include a CU and a DU. In this architecture, the access network equipment including a CU and a DU separates the protocol layers of the gNB in ​​the NR system. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed in the DU, which is centrally controlled by the CU. In a typical protocol stack partitioning method, the CU includes radio resource control (RRC) and the PDCP corresponding to the control plane, while the DU includes the radio link control (RLC) layer, MAC layer, and PHY layer. Optionally, the access network equipment can also adopt a CU-DU-RU separation architecture. It can be understood that in the CU-DU-RU separation architecture, the interface between the DU and RU can be called fronthaul, the interface between the CU and DU can be called midhaul, and the interface between the CU and the core network equipment can be called backhaul. Optionally, in the ORAN system, the access network equipment can be split into O-DU and O-RU, or it can be split into O-CU, O-DU, and O-RU. It should be understood that when the O-CU and O-DU are deployed together, they function as a single unit. When the O-CU and O-DU are deployed separately, they communicate with each other via the F1 interface. Specifically, the O-RU is responsible for receiving and sending information (or data or signals), while the O-DU is responsible for processing that information (or data or signals).

[0115] Optionally, the CU can be further divided into CP and UP. CU-CP is responsible for control plane functions, mainly including RRC and the corresponding PDCP (i.e., PDCP-control plane, PDCP-C) for the control plane. PDCP-C is mainly responsible for control plane data encryption / decryption, integrity protection, and data transmission. CU-UP is responsible for user plane functions, mainly including the Service Data Adaptation Protocol (SDAP) and the corresponding PDCP (i.e., PDCP-user plane, PDCP-U) for the user plane. SDAP is mainly responsible for processing core network data and mapping flows to bearers. PDCP-U is mainly responsible for data plane encryption / decryption, integrity protection, header compression, sequence number maintenance, and data transmission. CU-CP and CU-UP can be connected via the E1 interface. CU-CP represents the gNB connecting to the core network via the NG-C interface for control plane connection, and connecting to the DU via the F1 interface control plane (i.e., F1-C). CU-UP represents access network devices (such as gNBs) connecting to the core network via the NG-U interface for the user plane, and connecting to the DU via the F1 interface (i.e., F1-U) for the user plane. Another possible implementation is that the PDCP-C is also located in CU-UP.

[0116] It is understood that CU (or CU-CP and CU-UP), DU, or RU may have different names in different systems, but those skilled in the art will understand their meaning. For example, in an open access network system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (open CU-CP, O-CU-CP), CU-UP can also be called an open CU-UP (open CU-UP, O-CU-UP), and RU can also be called an open RU (open RU, O-RU). For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0117] It is understood that access network devices can communicate with each other, with terminal devices, or with each other using licensed spectrum, unlicensed spectrum, or both simultaneously. Access network devices and terminal devices can communicate using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. This application does not limit the spectrum resources used between access network devices and terminal devices.

[0118] In this embodiment, the functions of the access network device (such as a base station) can be executed by modules (such as chips) within the access network device, or by a control subsystem that includes access network device functions. This control subsystem can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal device can be executed by modules (such as chips or modems) within the terminal device, or by a device that includes terminal functions.

[0119] It is understood that the communication system and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0120] With the development of communication technology, access network equipment can provide data burst-based services for XR services. Before providing data burst-based services, access network equipment can obtain data burst-related information from core network equipment (such as DBS, TTNB, etc.), which can be used to assist access network equipment in scheduling data bursts.

[0121] In this context, the Data Block Separator (DBS) is provided by the core network equipment to the access network equipment (such as a base station). For example, the DBS is carried in the header of the first data packet in a data burst sent from the core network equipment to the access network equipment. Upon receiving the data burst, the access network equipment can determine the amount of data to be transmitted based on the DBS carried in the data burst, thereby performing resource reservation and other scheduling arrangements to ensure timely transmission of the data burst. The Time-to-Break Node (TTNB) can also be provided by the core network equipment to the access network equipment. For example, the TTNB is carried in the header of some data packets (such as the last one or several data packets) in a data burst sent from the core network equipment to the access network equipment. Based on the TTNB, the access network equipment can understand how long it will be before it needs to transmit data for this service, thus assisting the access network equipment and terminal equipment in saving energy. For example, the access network equipment can instruct the terminal equipment to enter a sleep state for a period of time.

[0122] However, in a DC (Data Center) scenario, a UE can connect to two base stations simultaneously, such as base station A and base station B. Taking base station A obtaining a data burst from the core network equipment as an example, the data packets included in the data burst obtained by base station A from the core network equipment may be offloaded to base station B. Since only base station A obtains the data burst-related information, while base station B does not (which can be understood as base station B being unable to obtain the data burst-related information), base station B cannot use the data burst-related information for data burst scheduling, resulting in inaccurate data burst scheduling.

[0123] In view of this, this application provides a communication method that, by sending data burst-related information to base station B, enables base station B to effectively utilize the data burst-related information for accurate scheduling of data bursts, thereby enabling the network side to accurately schedule data bursts.

[0124] The specific implementation of the communication method in the embodiments of this application will be described in detail below with reference to the accompanying drawings. It is understood that this application uses the first access network device and the second access network device as examples of the execution subjects in the interactive illustration, but this application does not limit the execution subjects in the interactive illustration. For example, the method executed by the first access network device in this application can also be executed by a module applied to the first access network device (e.g., a communication module, a circuit or chip responsible for communication functions (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first access network device, or it can be implemented through a combination of hardware and software. Similarly, the method executed by the second access network device in this application can also be executed by a module applied to the second access network device (e.g., a communication module, a circuit or chip responsible for communication functions (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.), or by a logical node, logical module, or software capable of implementing all or part of the functions of the second access network device, or it can be implemented through a combination of hardware and software. Optionally, the execution subject in the embodiments of this application may also include a core network device. The method executed by the core network equipment in this application can also be executed by a module applied to the core network equipment (e.g., a communication module, a circuit or chip responsible for communication functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor, etc.), or can be implemented by a logical node, logical module, or software that can implement all or part of the functions of the core network equipment, or can be implemented by a combination of hardware and software.

[0125] For example, the first access network device is MN, and the second access network device is SN. Alternatively, the first access network device is CU (e.g., the CU in MN), and the second access network device is DU (e.g., the DU in MN). Alternatively, the first access network device is a CU-CP device, and the second access network device is a CU-UP device. The core network device can be an AMF network element, an SMF network element, or a UPF network element. Optionally, the first access network device is SN, and the second access network device is MN. Alternatively, the first access network device is DU, and the second access network device is CU. Alternatively, the first access network device is a CU-UP device, and the second access network device is a CU-CP device.

[0126] Figure 6 illustrates a flowchart of a communication method provided in an embodiment of this application. This method is applicable to the communication system architecture shown in Figure 4. As shown in Figure 6, the method includes:

[0127] S601: The core network device sends first information to the first access network device. Correspondingly, the first access network device receives the first information from the core network device.

[0128] The first information can be used to indicate the size of the first data burst (or the data burst size).

[0129] The first information will be introduced through the following possible examples.

[0130] Example a1: The first information may be carried (or included) in the header of the first data packet included in the first data burst sent by the core network device to the first access network device, or the first information may also be carried in the header of other data packets included in the first data burst sent by the core network device to the first access network device (such as the header of data packets located after the first data packet).

[0131] Example a2: The first message can be independent of the first data burst. That is, the first message is not included in the first data burst. For example, in terms of transmission timing, the first message can be after the first data burst, or the first message can be before the first data burst.

[0132] S602: The first access network device sends second information to the second access network device. Correspondingly, the second access network device receives the second information from the first access network device.

[0133] The second information can be used to indicate the size of the second data burst. The second data burst can be a data burst that was diverted from the first data burst to the second access network device; for example, some or all of the data packets from the first data burst can be diverted to the second access network device as the second data burst. In other words, the second data burst is diverted to the second access network device for transmission to the corresponding terminal device. It can be understood that the size of the second data burst is less than or equal to the size of the first data burst.

[0134] For example, consider a first data burst as data burst #1 and a second data burst as data burst #2. If the first access network device needs to offload some data packets from data burst #1 to the second access network device, then some data packets from data burst #1 form (or become, or are determined) data burst #2. In this case, the size of data burst #2 is smaller than the size of data burst #1. If the first access network device needs to offload all data packets from data burst #1 to the second access network device, then all data packets from data burst #1 form data burst #2, and in this case, data burst #2 is also data burst #1. In this case, the size of data burst #2 is equal to the size of data burst #1.

[0135] In one possible implementation, when the first access network device determines that the first data burst needs to be offloaded to the second access network device, the first access network device may send second information to the second access network device.

[0136] In another possible implementation, when the first access network device determines that the first data burst does not need to be offloaded to the second access network device, the first access network device may not need to send the second information to the second access network device.

[0137] The second piece of information will be introduced through the following possible examples.

[0138] Example b1: The second information may be carried in the header of the first data packet included in the second data burst sent by the first access network device to the second access network device, or the second information may also be carried in the header of other data packets included in the second data burst sent by the first access network device to the second access network device (such as the header of data packets located after the first data packet).

[0139] Example b2: The second message can be independent of the second data burst. That is, the second message is not included in the second data burst. For example, in terms of transmission timing, the second message can be after the second data burst, or it can be before the second data burst.

[0140] For example, taking the terminal device as UE, and the UE simultaneously connected to a first access network device and a second access network device, where the first access network device is MN and the second access network device is SN, and the MR-DC architecture supports a separate bearer type terminated at MN as an example. When MN obtains the first data burst from a core network device (such as a UPF element), if MN needs to offload some or all of the data packets in the first data burst to SN, MN can indicate the DBS to SN. This allows SN to accurately schedule data to the UE using the corresponding DBS. Some or all of the data packets in the first data burst can form a second data burst. For example, MN can carry the DBS in the header of a data packet (such as the first data packet) included in the second data burst, where the DBS indicates the size of the second data burst. The size of the second data burst can be less than or equal to the size of the first data burst.

[0141] Optionally, if the first access network device adopts a CU-DU separation architecture, and some data packets in the first data burst are diverted to the second access network device, the CUs included in the first access network device need to indicate the DBS (e.g., the size of the second data burst) to the second access network device, and also need to indicate the DBS (e.g., the size of other data packets in the first data burst besides the second data burst) to the DUs included in the first access network device. For example, the CUs included in the first access network device can carry the corresponding DBS in the header of the first data packet in the partial data packets sent to the second access device, and carry the corresponding DBS in the header of the first data packet in one or more data packets sent to the DUs included in the first access network device. This facilitates both the DUs included in the first access network device and the second access network device to accurately schedule data using the corresponding DBS, and facilitates both the DUs included in the first access network device and the second access network device to reserve corresponding resources for data scheduling based on the corresponding DBS, or in other words, facilitates both the DUs included in the first access network device and the second access network device to reasonably reserve resources for data scheduling based on the corresponding DBS, ensuring timely and effective data transmission.

[0142] For example, taking a terminal device as a UE, where the UE is simultaneously connected to a first access network device and a second access network device, the first access network device is MN, the second access network device is SN, and the MR-DC architecture supports a bearer type terminated at MN, with the first data burst being data burst#1 and the second data burst being data burst#2. The size of data burst#2 is smaller than the size of data burst#1. As shown in Figure 7a, both MN and SN adopt a CU-DU separation architecture, and the UPF network element in the core network sends data burst#1 to MN. When MN offloads some data packets from data burst#1 to SN, the CUs included in MN (which can be called MN-CU) need to indicate DBS#1 (to indicate the size of data burst#2) to SN (or SN-CU), and also need to indicate DBS#2 (to indicate the size of other data packets in data burst#1 besides data burst#2) to the DUs included in MN (which can be called MN-DU). The size of other data packets in data burst#1 besides data burst#2 is also smaller than the size of data burst#1. The sum of DBS#1 and DBS#2 equals the size of data burst#1. It is understandable that, since data burst #1 needs to be offloaded, the actual amount of data that MN and SN need to transmit is less than the amount of data burst #1 provided by the UPF network element in the core network. By indicating the corresponding (or matching) DBS to MN-DU and SN respectively, MN-CU can enable MN-DU and SN to indicate the accurate DBS according to the actual offload ratio, thereby assisting MN-DU and SN to accurately schedule data to UE. In other words, it can be understood as making it easier for MN-DU and SN to accurately schedule data to UE based on the corresponding DBS.

[0143] For example, consider a terminal device (UE) that is simultaneously connected to a first access network device (SN) and a second access network device (MN). The first access network device is SN, and the second access network device is MN. The MR-DC architecture supports a bearer type that terminates at SN, with the first data burst being data burst#1 and the second data burst being data burst#2. The size of data burst#2 is smaller than the size of data burst#1. As shown in Figure 7b, both MN and SN adopt a CU-DU separation architecture. The UPF network element in the core network sends data burst#1 to SN. When SN offloads some data packets from data burst#1 to MN, the CUs included in SN (referred to as SN-CU) need to indicate DBS#1 (to indicate the size of data burst#2) to MN, and also need to indicate DBS#2 (to indicate the size of other data packets in data burst#1 besides data burst#2) to the DUs included in SN (referred to as SN-DU). It is understandable that, since data burst #1 needs to be offloaded, the actual amount of data that MN and SN need to transmit is less than the amount of data burst #1 provided by the UPF network element in the core network. By indicating the corresponding DBS to SN-DU and MN respectively, SN-CU can accurately indicate the DBS to SN-DU and MN according to the actual offload ratio. This can help SN-DU and MN accurately schedule data to UE. In other words, it can be understood as making it easier for SN-DU and MN to accurately schedule data to UE based on the corresponding DBS.

[0144] Optionally, before the first access network device sends the second information to the second access network device, or after the first access network device sends the second information to the second access network device, or before the first access network device receives the first information from the core network device, or after the first access network device receives the first information from the core network device, the first access network device may also receive the third information from the core network device. The third information can be used to indicate the arrival time of the third data burst. The third data burst is located after the first data burst. That is, the third data burst is a data burst received or generated after the first data burst, for example, the third data burst is the first data burst received or generated after the first data burst. Afterwards, the first access network device may send a fourth information to the second access network device. The fourth information can be used to indicate the arrival time of the third data burst.

[0145] Optionally, in some embodiments, the third information may be the same as the first information, or it may be different from the first information. When the third information and the first information are the same, the size of the first data burst and the arrival time of the third data burst can be indicated by the same information; for example, the same information can indicate both the size of the first data burst and the arrival time of the third data burst. For instance, the same information includes two indications: one indicating the size of the first data burst and the other indicating the arrival time of the third data burst. When the third information and the first information are different, the size of the first data burst and the arrival time of the third data burst can each be indicated by a separate piece of information.

[0146] The following examples illustrate the concept of third-party information.

[0147] Example c1: The third information can be carried in the header of the last q data packets included in the first data burst sent by the core network device to the first access network device, or the third information can also be carried in the header of other data packets included in the first data burst (such as in the header of the first data packet or other data packets). Wherein, q is an integer greater than or equal to 1.

[0148] Example c2: The third information can be independent of the first data burst. That is, the third information is not included in the first data burst. For example, in terms of transmission timing, the third information can be after the first data burst, or it can be before the first data burst.

[0149] The fourth piece of information will be introduced through the following possible examples.

[0150] Example d1: In cases where the first data burst needs to be offloaded to the second access network device (e.g., some or all of the data packets included in the first data burst need to be offloaded to the second access network device), the fourth information can be carried in the header of the last p data packets included in the second data burst, or the fourth information can also be carried in the header of other data packets included in the second data burst (e.g., located in the header of the first data packet or other data packets). Here, p is an integer greater than or equal to 1.

[0151] For example, continuing with the terminal device as UE, the UE is simultaneously connected to a first access network device and a second access network device. The first access network device is MN, and the second access network device is SN. The MR-DC architecture supports a separate bearer type terminating at MN. When MN obtains the first data burst from a core network device (e.g., a UPF element), if MN needs to offload some or all data packets in the first data burst to SN, MN can indicate the TTNB to SN. This allows SN to promptly perceive or obtain the TTNB, enabling accurate data scheduling. It also allows SN to promptly initiate a sleep period based on the TTNB or instruct the UE to initiate a sleep period based on the TTNB, helping to save energy for SN or UE and achieving good energy-saving effects. Some or all data packets in the first data burst can form a second data burst. For example, MN can carry the TTNB in ​​the header of one (e.g., the last data packet) or multiple (e.g., the last few data packets) included in the second data burst. This TTNB indicates the arrival time of the third data burst. The TTNB indicated by MN to SN is equal to the TTNB indicated by the core network device to MN.

[0152] Optionally, in some embodiments, the third information and the fourth information can be the same information, that is, after receiving the third information, the first access network device directly sends the third information to the second access network device. Alternatively, the third information and the fourth information can be different information, that is, after receiving the third information, the first access network device generates the fourth information based on the third information, and then sends the fourth information to the second access network device.

[0153] Optionally, if the first access network device adopts a CU-DU separation architecture, and some data packets in the first data burst are diverted to the second access network device, the CU included in the first access network device needs to indicate the TTNB (e.g., the arrival time of the third data burst) to both the second access network device and the DU included in the first access network device. For example, the CU included in the first access network device can carry the TTNB in ​​the header of the last one or more data packets in the partial data packets sent to the second access device, and carry the TTNB in ​​the header of the last one or more data packets in the one or more data packets sent to the DU included in the first access network device. This allows both the DU included in the first access network device and the second access network device to accurately schedule data using the TTNB, and enables the MN and SN to promptly hibernate for a period of time based on the TTNB or promptly instruct the UE to hibernate for a period of time based on the TTNB, which helps to save energy consumption of the MN, SN and UE, achieving a better energy-saving effect.

[0154] For example, taking a terminal device as a UE, where the UE is simultaneously connected to a first access network device (MN) and a second access network device (SN), and the MR-DC architecture supports a bearer type that terminates at the MN, with the first data burst being data burst#1 and the third data burst being data burst#3, as shown in Figure 8a, both MN and SN adopt a CU-DU separation architecture. The UPF network element in the core network sends data burst#1 to MN. When MN offloads some data packets from data burst#1 to SN, the CUs included in MN (referred to as MN-CU) need to indicate the TTNB (to indicate the arrival time of data burst#3) to both SN (or SN-CU) and DUs included in MN (referred to as MN-DU). The TTNB indicated by MN-CU to SN is equal to the TTNB indicated by MN-CU to MN-DU, and also equal to the TTNB indicated by the UPF network element to MN-CU.

[0155] For example, consider a terminal device (UE) that is simultaneously connected to a first access network device (SN) and a second access network device (MN). The MR-DC architecture supports a separate bearer type terminated at the SN, with the first data burst being data burst #1 and the third data burst being data burst #3. As shown in Figure 8b, both MN and SN adopt a CU-DU separate architecture. The UPF element in the core network sends data burst #1 to the SN. When the SN offloads some data packets from data burst #1 to the MN, the CU (referred to as SN-CU) within the SN needs to indicate the TTNB (to indicate the arrival time of data burst #3) to both the MN (or MN-CU) and the DU (referred to as SN-DU). The TTNB indicated by the SN-CU to the MN is equal to the TTNB indicated by the SN-CU to the SN-DU, and also equal to the TTNB indicated by the UPF element to the SN-CU.

[0156] Example d2: If the first data burst does not need to be diverted to the second access network device, the fourth information can be carried in the header of an empty data packet.

[0157] In this embodiment, when the first data burst does not need to be offloaded to the second access network device, all data packets included in the first data burst are transmitted to the corresponding terminal device through the first access network device. In this case, to avoid the second access network device scheduling data according to the TTNB but actually transmitting no data, or to avoid the second access network device or terminal device consuming energy (e.g., battery power) due to prolonged wake-up waiting for data offloaded from the first access network device, or to facilitate the second access network device's timely detection or acquisition of the TTNB and its early entry into sleep mode or instruction to the terminal device to enter sleep mode, the first access network device can determine (or generate or construct) an empty data packet and carry fourth information in the header of the empty data packet. Here, an empty data packet refers to a data packet that does not contain valid data or payload. In this embodiment, the empty data packet can be specifically used to carry the fourth information.

[0158] It is understandable that, even when the first data burst does not need to be offloaded to the second access network device, the first access network device still sends the fourth information to the second access network device. This is because the second access network device may, based on the TTNB associated with the previous (or earlier) data burst (such as the TTNB carried by the previous data burst), end the sleep state of the second access network device or terminal device when the current data burst arrives, in order to prepare for data transmission. However, if the current data burst is not offloaded, the second access network device may have to wait for data for a long time, which will cause the second access network device to consume a certain amount of energy, which is not conducive to energy saving of the second access network device or the terminal device.

[0159] For example, consider a terminal device (UE) connected to both a first access network device (MN) and a second access network device (SN). The previous data burst is data burst #1, and the current data burst is data burst #3. Assume that TTNB #1 carried in data burst #1 is 50ms, and TTNB #2 carried in data burst #3 is 40ms. MN receives data burst #1 at time t0, and needs to offload a portion of the data packets included in data burst #1 to the SN. Therefore, MN can indicate TTNB #1 to the SN. After the SN completes the transmission of the portion of the data packets included in data burst #1 (i.e., after transmitting the portion to the UE), it can send indication information 01 to the UE. Indication information 01 instructs the UE to sleep until time (t0+50ms). It should be understood that the SN can also sleep until time (t0+50ms).

[0160] Optionally, the MN receives data burst #3 at time (t0+50ms), and data burst #3 does not need to be offloaded to the SN. However, the UE's sleep on the SN side has ended, or the SN's sleep has ended. Since the SN has not received data (or data packets or data bursts), the SN may assume that the data has not yet arrived and continue to wait for data. In this case, the UE cannot enter sleep mode, and of course, the SN cannot enter sleep mode either. But in fact, the SN does not need to transmit data until the next data burst (the data burst following data burst #3) arrives. Based on this, the MN can construct an empty data packet to indicate TTNB #2 carried in data burst #3 to the SN. For example, the MN can carry TTNB #2 in the header of the empty data packet and send the empty data packet to the SN. This makes it easier for the SN and UE to enter sleep mode based on TTNB #2 without waking up, thereby effectively reducing the energy consumption of the SN and UE and achieving a better energy-saving effect. After receiving the empty data packet from the MN, the SN can obtain TTNB #2 from the empty data packet. Afterwards, the SN can continue to sleep based on TTNB #2 until time (t0+50ms+40ms). To facilitate the UE's continued sleep mode on the SN side and save UE power consumption, the SN can also send indication information 02 to the UE. Indication information 02 is used to instruct the UE to sleep until (t0+50ms+40ms).

[0161] Optionally, if the first data burst does not need to be offloaded to the second access network device, in order to facilitate the second access network device's timely awareness that the current data burst (the data burst following the first data burst) is not offloaded to it, the first access network device may also indicate that the first data burst has ended through the fourth information, or indicate that the size of the first data burst is 0 through the fourth information. For example, the first access network device may carry first indication information and second indication information in the fourth information. The first indication information is used to indicate the arrival time of the third data burst. The second indication information is used to indicate that the first data burst has ended (or that the transmission of the first data burst has ended), or to indicate that the size of the first data burst is 0. Optionally, the first access network device may also carry fifth information in the header of the empty data packet, the fifth information being used to indicate that the first data burst has ended, or to indicate that the size of the first data burst is 0.

[0162] For example, consider a terminal device (UE) connected to both a first access network device (MN) and a second access network device (SN). When MN indicates the TTNB (e.g., TTNB#2) to SN, it can also indicate that the current data burst (e.g., data burst#3) has ended or that the current data burst size is 0. For instance, MN can carry indication information 03 in the header of an empty data packet. Indication information 03 indicates that the current data burst (e.g., data burst#3) has ended or that the current data burst size is 0. In this way, after receiving an empty data packet, SN can obtain indication information 03 from the empty data packet and determine, based on indication information 03, that SN will not receive any more data packets from the current data burst, or that the current data burst does not require SN transmission. This allows SN to enter sleep mode earlier, improving energy efficiency.

[0163] Optionally, if the first access network device adopts a CU-DU separation architecture, then if the first data burst is not diverted to the second access network device, the CU included in the first access network device can indicate the TTNB (such as the arrival time of the third data burst) to the second access network device. For example, the CU included in the first access network device can carry the TTNB in ​​the header of the constructed empty data packet, which can enable the SN to hibernate for a period of time based on the TTNB in ​​a timely manner, which helps to save energy consumption on the SN side and achieve a better energy saving effect.

[0164] For example, taking a UE as the terminal device, the UE is simultaneously connected to a first access network device (MN) and a second access network device (SN). The first access network device is MN, and the second access network device is SN. The MR-DC architecture supports a separate bearer type that terminates at MN, and the current data burst is data burst #3. Both MN and SN adopt a CU-DU separate architecture. The UPF network element in the core network sends data burst #3 to MN. If data burst #3 is not offloaded to SN, the CU included in MN (which can be called MN-CU) can indicate the TTNB (to indicate the arrival time of data burst #3) to SN (or SN-CU). Optionally, MN-CU can also indicate to SN (or SN-CU) that data burst #3 has ended or that the size of data burst #3 is 0.

[0165] For example, consider a terminal device (UE) that is simultaneously connected to a first access network device (MN) and a second access network device (SN). The MR-DC architecture supports a separate bearer type terminated at the SN, with the current data burst being data burst #3. Both MN and SN employ a CU-DU separate architecture. The UPF element in the core network sends data burst #3 to the SN. If data burst #3 is not offloaded to the MN, the CU (which can be called SN-CU) within the SN can indicate the TTNB (to indicate the arrival time of data burst #3) to the MN (or MN-CU). Optionally, the SN-CU can also indicate to the MN (or MN-CU) that data burst #3 has ended or that its size is 0.

[0166] As can be seen from S601 to S602 above, by sending second information to the second access network device, the first access network device can promptly obtain the size of the second data burst allocated to it. This allows the second access network device to accurately schedule the second data burst based on its size and to accurately reserve corresponding resources for its scheduling. In other words, it facilitates resource reservation and other scheduling arrangements based on the size of the second data burst, ensuring its timely and effective transmission. Furthermore, this method can also enable the first access network device to accurately indicate the size of the data burst (i.e., the size of the data packets allocated to the second access network device from the multiple data packets included in the first data burst) to the second access network device according to the distribution ratio of the first data burst, thus assisting the second access network device in accurately scheduling the allocated data packets. It should be understood that the first access network device can also accurately schedule other data packets in the first data burst (excluding the second data burst) based on their sizes, and can also accurately reserve corresponding resources for their scheduling, ensuring their timely and effective transmission.

[0167] Figure 9 is a flowchart illustrating another communication method provided in an embodiment of this application. This method is applicable to the communication system architecture shown in Figure 4. As shown in Figure 9, the method includes:

[0168] S901: The core network device sends third information to the first access network device. Correspondingly, the first access network device receives the third information from the core network device.

[0169] The third information can be used to indicate the arrival time of the third data burst.

[0170] It is understandable that the details of the third information not described in detail can be found in the relevant descriptions of examples c1 to c2 above, and will not be repeated here.

[0171] S902: The first access network device sends fourth information to the second access network device. Correspondingly, the second access network device receives the fourth information from the first access network device.

[0172] The fourth piece of information can be used to indicate the arrival time of the third data burst. The third data burst occurs after the first data burst. That is, the third data burst is a data burst received or generated after the first data burst, for example, the third data burst is the first data burst received or generated after the first data burst.

[0173] It is understandable that the details of the fourth piece of information not described in detail can be found in the relevant descriptions of examples d1 to d2 above, and will not be repeated here.

[0174] Optionally, before the first access network device sends the fourth information to the second access network device, or after the first access network device sends the fourth information to the second access network device, or before the first access network device receives the third information from the core network device, or after the first access network device receives the third information from the core network device, the first access network device may also receive the first information from the core network device. The first information can be used to indicate the size of the first data burst. Afterwards, the first access network device may send second information to the second access network device. The second information can be used to indicate the size of the second data burst. The second data burst can be a data burst that is diverted from the first data burst to the second access network device. That is, the second data burst is diverted to the second access network device for transmission to the corresponding terminal device. It can be understood that the size of the second data burst is less than or equal to the size of the first data burst.

[0175] For example, consider a first data burst as data burst #1 and a second data burst as data burst #2. If the first access network device needs to offload some data packets from data burst #1 to the second access network device, then some data packets from data burst #1 form (or become, or are determined) data burst #2. In this case, the size of data burst #2 is smaller than the size of data burst #1. If the first access network device needs to offload all data packets from data burst #1 to the second access network device, then all data packets from data burst #1 form data burst #2, and in this case, data burst #2 is also data burst #1. In this case, the size of data burst #2 is equal to the size of data burst #1.

[0176] In one possible implementation, when the first access network device determines that the first data burst needs to be offloaded to the second access network device, the first access network device may send second information to the second access network device. In another possible implementation, when the first access network device determines that the first data burst does not need to be offloaded to the second access network device, the first access network device may not need to send second information to the second access network device.

[0177] It is understood that the content of the first information not described in detail here can be referred to the relevant descriptions of examples a1 to a2 above, the content of the second information not described in detail can be referred to the relevant descriptions of examples b1 to b2 above, and the relevant content involved in the case where the first access network device or the second access network device adopts the CU-DU separation architecture can be referred to the relevant introduction above, which will not be repeated here.

[0178] As can be seen from S901 to S902 above, by sending the fourth information to the second access network device, the first access network device can more effectively detect or obtain the arrival time of the third data burst and thus more rationally enter sleep mode. This helps prevent the second access network device from waiting indefinitely for data from the first access network device due to the inability to obtain the arrival time of the third data burst, thereby facilitating energy-saving optimization for the second access network device or terminal device and effectively reducing their energy consumption. Furthermore, this implementation also allows the second access network device to make resource reservation and other scheduling arrangements early based on the fourth information to ensure the timely and effective transmission of offloaded data. It should be understood that the first access network device can also more rationally enter sleep mode based on the arrival time of the third data burst, or it can instruct the terminal device to enter sleep mode based on the arrival time of the third data burst, thereby facilitating energy-saving optimization for the first access network device or terminal device and effectively reducing their energy consumption. Additionally, the first access network device can also make resource reservation and other scheduling arrangements early based on the arrival time of the third data burst to ensure the timely and effective transmission of data that it needs to transmit.

[0179] It is understood that, in order to achieve the functions in the above embodiments, the first access network device, the second access network device, and the core network device include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware, computer software, or a combination of both. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0180] Figures 10 and 11 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of the first access network device, the second access network device, or the core network device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0181] The communication device 1000 shown in Figure 10 includes a transceiver unit 1010 (or a communication module, transceiver module, or communication unit, used for sending and receiving data). Optionally, the communication device 1000 shown in Figure 10 may further include a processing unit 1020 (or a processing module). The communication device 1000 can be used to implement the functions of the first access network device, the second access network device, or the core network device in the method embodiments shown in Figures 6 or 9 above. For example, the transceiver unit 1010 can perform the receiving and sending actions performed by the first access network device, the second access network device, or the core network device in the above method embodiments. The processing unit 1020 can perform other actions besides the sending and receiving actions performed by the first access network device, the second access network device, or the core network device in the above method embodiments.

[0182] When the communication device 1000 is used to implement the function of the first access network device in the method embodiment shown in FIG6: the transceiver unit 1010 is used to receive first information from the core network device. The first information indicates the size of the first data burst. The transceiver unit 1010 is also used to send second information to the second access network device. The second information indicates the size of the second data burst, which is a data burst that is diverted from the first data burst to the second access network device. The processing unit 1020 is used to perform corresponding processing operations, such as calling the transceiver unit 1010 to execute the transceiver actions required by the first access network device in the method embodiment shown in FIG6, or determining whether the first data burst is diverted to the second access network device.

[0183] When the communication device 1000 is used to implement the function of the second access network device in the method embodiment shown in FIG. 6: the transceiver unit 1010 is used to receive second information from the first access network device. The second information indicates the size of the second data burst, which is a data burst that is diverted from the first data burst to the second access network device. The processing unit 1020 is used to perform corresponding processing operations, such as calling the transceiver unit 1010 to execute the transceiver actions required by the second access network device in the method embodiment shown in FIG. 6, or scheduling data to the terminal device.

[0184] When the communication device 1000 is used to implement the function of the first access network device in the method embodiment shown in FIG9: the transceiver unit 1010 is used to receive third information from the core network device. The third information indicates the arrival time of the third data burst. The transceiver unit 1010 is also used to send fourth information to the second access network device. The fourth information indicates the arrival time of the third data burst, which is located after the first data burst. The processing unit 1020 is used to perform corresponding processing operations, such as calling the transceiver unit 1010 to execute the transceiver actions required by the first access network device in the method embodiment shown in FIG9, or determining whether the first data burst is diverted to the second access network device.

[0185] When the communication device 1000 is used to implement the function of the second access network device in the method embodiment shown in FIG9: the transceiver unit 1010 is used to receive fourth information from the first access network device. The fourth information indicates the arrival time of the third data burst, which is located after the first data burst. The processing unit 1020 is used to perform corresponding processing operations, such as calling the transceiver unit 1010 to execute the transceiver actions required by the second access network device in the method embodiment shown in FIG9, or scheduling data to the terminal device.

[0186] For a more detailed description of the processing unit 1020 and the transceiver unit 1010, please refer to the relevant descriptions in the method embodiments shown in Figures 6 or 9 above, which will not be repeated here.

[0187] It should be understood that the transceiver unit 1010 in the embodiments of this application can be implemented by an interface circuit or interface circuit-related circuit components, and the processing unit 1020 can be implemented by a processor or processor-related circuit components.

[0188] It should be noted that the module division in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical entities, or have two or more units integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0189] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, or a server, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0190] The communication device 1100 shown in Figure 11 includes at least one processor 1120 and interface circuitry 1110. The at least one processor 1120 and interface circuitry 1110 may be coupled to each other. It is understood that interface circuitry 1110 may be a transceiver or an input / output interface. Exemplarily, the communication device 1100 may also include a memory 1130. Memory 1130 is used to store instructions executed by at least one processor 1120, or to store input data required for at least one processor 1120 to execute instructions, or to store data generated after at least one processor 1120 executes instructions.

[0191] When the communication device 1100 is used to implement the method embodiment shown in FIG6 or FIG9, at least one processor 1120 is used to implement the function of the processing unit 1020, and the interface circuit 1110 is used to implement the function of the transceiver unit 1010.

[0192] For example, taking a terminal device as a UE, and the terminal device simultaneously connected to a first access network device and a second access network device, where the first access network device is base station a and the second access network device is base station b, when the aforementioned communication device is a chip applied to base station a, the chip of base station a implements the functions corresponding to base station a in the above method embodiment. For example, when the chip of base station a receives information from the core network device, it can be understood that the information is first received by other modules (such as radio frequency modules or antennas) in base station a, and then sent to the chip of base station a by these modules. When the chip of base station a sends information to the UE, it can be understood that the information is first sent to other modules (such as radio frequency modules or antennas) in base station a, and then sent to the UE by these modules.

[0193] When the aforementioned communication device is a chip applied to base station b, the chip of base station b implements the functions corresponding to base station b in the above method embodiments. For example, when the chip of base station b receives information from base station a, it can be understood that the information is first received by other modules (such as radio frequency modules or antennas) in base station b, and then sent to the chip of base station b by these modules. When the chip of base station b sends information to the UE, it can be understood that the information is first sent to other modules (such as radio frequency modules or antennas) in base station b, and then sent to the UE by these modules.

[0194] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be terminal devices or access network devices, or modules within those devices. Information transmission and reception can be between a terminal device and an access network device, such as between a UE and a base station. Information transmission and reception can also be between two base stations, such as between a CU and a DU. Furthermore, information transmission and reception can be between different modules within a single device, such as between a UE chip and other UE modules, or between a base station chip and other modules within that base station.

[0195] Based on the same concept, embodiments of this application also provide a possible communication system. This communication system may include one or more of a first access network device, a second access network device, or a core network device. The first access network device can be used to implement the technical solutions related to the first access network device in the above embodiments. The second access network device can be used to implement the technical solutions related to the second access network device in the above embodiments. The core network device can be used to implement the technical solutions related to the core network device in the above embodiments.

[0196] Based on the same concept, this application also provides a computer program product, which includes a computer program or instructions that, when run on a communication device (or computer), cause the communication device (or computer) to perform the methods provided in the above embodiments.

[0197] Based on the same concept, embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions that, when executed by a communication device (or computer), cause the communication device (or computer) to perform the methods provided in the above embodiments.

[0198] The storage medium can be any available medium that a computer can access. For example, but not limited to, computer-readable media can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0199] Based on the same concept, embodiments of this application also provide a chip, which may include a processor and a memory (or the chip may be coupled to the memory). The processor executes program instructions in the memory to cause the chip to perform the methods provided in the above embodiments. Here, "coupling" means that two components are directly or indirectly connected to each other, such as coupling can refer to an electrical connection between two components.

[0200] Based on the same concept, embodiments of this application also provide a chip system, which includes a processor for supporting a computer device in implementing the functions involved in the first access network device, the second access network device, or the core network device in the above embodiments. In one possible implementation, the chip system further includes a memory for storing necessary programs and data of the computer device. The chip system may be composed of chips or may include chips and other discrete components.

[0201] It is understood that the processor in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0202] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a communication device. Of course, the processor and storage medium can also exist as discrete components in the communication device.

[0203] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. A computer program is a set of instructions that directs each step of an action of an electronic computer or other device with message processing capabilities. It is typically written in a programming language and runs on a target architecture. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed, in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be volatile or non-volatile, or it can include both types of storage media.

[0204] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0205] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects.

[0206] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, The method includes: (The method is applied to a first access network device or a module within the first access network device.) Receive the first information from the core network equipment; Send the second information to the second access network device; Wherein, the first information is used to indicate the size of the first data burst, the first data burst is diverted to the second access network device, and the second information is used to indicate the size of the data burst.

2. The method as described in claim 1, characterized in that, The method further includes: Receive third information from the core network device, the third information being used to indicate the time interval between the next data burst and the first data burst; A fourth message is sent to the second access network device, the fourth message indicating the time interval between the next data burst and the first data burst.

3. The method as described in claim 2, characterized in that, The fourth information is also used to indicate that the first data burst has ended, or the fourth information is also used to indicate that the size of the first data burst is 0.

4. The method as described in claim 2 or 3, characterized in that, The fourth piece of information is carried in the header of the empty data packet.

5. The method as described in claim 2, characterized in that, The fourth information is carried in the header of the last p data packets included in the data burst distributed to the second access network device, where p is an integer greater than or equal to 1.

6. The method as described in claim 1, 2, or 5, characterized in that, The second information is carried in the header of the first data packet included in the data burst distributed to the second access network device.

7. A communication method, characterized in that, The method includes: (The method is applied to a second access network device or a module within the second access network device.) Receive second information from the first access network device; The second piece of information is used to indicate the size of the data burst.

8. The method as described in claim 7, characterized in that, The method further includes: The system receives fourth information from the first access network device, the fourth information indicating the time interval between the next data burst and the first data burst, the first data burst being diverted to the second access network device.

9. The method as described in claim 8, characterized in that, The fourth information is also used to indicate that the first data burst has ended, or the fourth information is also used to indicate that the size of the first data burst is 0.

10. The method as described in claim 8 or 9, characterized in that, The fourth piece of information is carried in the header of the empty data packet.

11. The method as described in claim 8, characterized in that, The fourth information is carried in the header of the last p data packets included in the data burst distributed to the second access network device, where p is an integer greater than or equal to 1.

12. The method as described in claim 7, 8, or 11, characterized in that, The second information is carried in the header of the first data packet included in the data burst distributed to the second access network device.

13. A communication method, characterized in that, The method includes: (The method is applied to a first access network device or a module within the first access network device.) Receive third-party information from core network equipment; Send the fourth message to the second access network device; The third information is used to indicate the time interval between the next data burst and the first data burst, and the fourth information is used to indicate the time interval between the next data burst and the first data burst, wherein the first data burst is diverted to the second access network device.

14. The method as described in claim 13, characterized in that, The method further includes: Receive first information from the core network device; Send the second information to the second access network device; Wherein, the first information is used to indicate the size of the first data burst, and the second information is used to indicate the size of the data burst.

15. The method as described in claim 14, characterized in that, The second information is carried in the header of the first data packet included in the data burst distributed to the second access network device.

16. The method as described in claim 13, characterized in that, The fourth information is also used to indicate that the first data burst has ended, or the fourth information is also used to indicate that the size of the first data burst is 0.

17. The method as described in claim 13 or 16, characterized in that, The fourth piece of information is carried in the header of the empty data packet.

18. The method according to any one of claims 13-15, characterized in that, The fourth information is carried in the header of the last p data packets included in the data burst distributed to the second access network device, where p is an integer greater than or equal to 1.

19. A communication method, characterized in that, The method includes: (The method is applied to a second access network device or a module within the second access network device.) The system receives fourth information from the first access network device, the fourth information indicating the time interval between the next data burst and the first data burst, the first data burst being diverted to the second access network device.

20. The method as described in claim 19, characterized in that, The method further includes: Receive second information from the first access network device; The second piece of information is used to indicate the size of the data burst.

21. The method as described in claim 20, characterized in that, The second information is carried in the header of the first data packet included in the data burst distributed to the second access network device.

22. The method as described in claim 19, characterized in that, The fourth information is also used to indicate that the first data burst has ended, or the fourth information is also used to indicate that the size of the first data burst is 0.

23. The method as described in claim 19 or 22, characterized in that, The fourth piece of information is carried in the header of the empty data packet.

24. The method according to any one of claims 19-21, characterized in that, The fourth information is carried in the header of the last p data packets included in the data burst distributed to the second access network device, where p is an integer greater than or equal to 1.

25. A communication device, characterized in that, It includes modules or units for performing the method as described in any one of claims 1-6, or modules or units for performing the method as described in any one of claims 7-12, or modules or units for performing the method as described in any one of claims 13-18, or modules or units for performing the method as described in any one of claims 19-24.

26. A communication device, characterized in that, Includes at least one processor and interface circuitry; The interface circuit is used to receive signals from other communication devices and transmit them to the at least one processor, or to send signals from the at least one processor to other communication devices. The at least one processor is configured to implement the method of any one of claims 1-6, or the method of any one of claims 7-12, or the method of any one of claims 13-18, or the method of any one of claims 19-24, through logic circuits or executing code instructions.

27. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed by a communication device, cause the method as described in any one of claims 1-6, or the method as described in any one of claims 7-12, or the method as described in any one of claims 13-18, or the method as described in any one of claims 19-24 to be implemented.

28. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed on a communication device, cause the method as described in any one of claims 1-6, or the method as described in any one of claims 7-12, or the method as described in any one of claims 13-18, or the method as described in any one of claims 19-24 to be implemented.

Images