Communication method, system and device

Abstract

The invention provides a communication method, system and device. The method can provide a scheme capable of configuring appropriate resources for data transmission between an application server and terminal equipment. The method comprises the following steps: an application server sends a data packet to a service management network element, the data volume of the data packet in a scheduling period (which can be any scheduling period) is greater than a first value, and the service management network element processes the data packet; the data volume of the data packet obtained after processing is smaller than or equal to the first value in the scheduling period, and then the data packet obtained after processing is sent to the network equipment. Thus, the network device can uniformly configure resources for the data packets from the application server, the phenomena of excessive resource allocation or too little resource allocation and the like can be effectively avoided, and then proper resources can be configured for data transmission between the application server and the terminal device.

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method, system and device. Background Art

[0002] Currently, the Third Generation Partnership Project (3 rd The 3rd Generation Partnership Project (3GPP) standard defines a group communication service (GCS), which can distribute the same content to multiple terminal devices in a controlled manner.

[0003] Specifically, the application server (AS) in the GCS can use the multimedia broadcast / multicast service (MBMS) or evolved MBMS (eMBMS) bearer service, which is used to support data transmission between the application server and the terminal device.

[0004] However, the above GCS mechanism cannot support the configuration of appropriate resources for data transmission between the application server and the terminal device, which may lead to the problem of excessive or insufficient resource allocation. Therefore, how to configure appropriate resources for data transmission between the application server and the terminal device is a technical problem that needs to be solved urgently. Summary of the invention

[0005] The present application provides a communication method, system and apparatus, which can configure appropriate resources for data transmission between an application server and a terminal device.

[0006] In a first aspect, a communication method is provided, including: receiving a first data packet, wherein the data volume of the first data packet in a first scheduling period is greater than a first value; and sending a second data packet, wherein the second data packet is a data packet obtained after processing the first data packet, and the data volume of the second data packet in the first scheduling period is less than or equal to the first value.

[0007] The execution subject of the solution described in the first aspect may be a service management network element, or a module or chip for executing the function of the service management network element, etc., without limitation. For ease of description, the following description is made by taking the service management network element as an example.

[0008] It can be understood that the above-mentioned first scheduling period can be any scheduling period, and the first data packet can be any data packet with a data volume greater than the first value.

[0009] Specifically, when the data volume of a data packet received by the service management network element is greater than a first value, the service management network element can process the data packet so that the data volume of the data packet obtained after processing is less than or equal to the first value. In this way, the network device can configure appropriate resources for the data packet and avoid excessive or insufficient resource allocation.

[0010] A possible implementation method is that the second data packet is a data packet obtained after processing the first data packet, including: the second data packet is a data packet obtained by allocating additional data volume of the first data packet to the second scheduling period, and the additional data volume of the first data packet is the difference between the data volume of the first data packet in the first scheduling period and the first value.

[0011] In this way, the data volume of the second data packet in the first scheduling period can be less than or equal to the first value.

[0012] In a possible implementation, the first value is a maximum amount of data that can be scheduled by the network device in the first scheduling period.

[0013] In this way, the data volume of the data packets from the service management network element will not exceed the maximum scheduling capability of the network device.

[0014] In a possible implementation manner, the method further includes: receiving a first value.

[0015] In this way, the service management network element can process the first data packet according to the first value.

[0016] In a possible implementation manner, the first value is a ratio of a guaranteed bit rate of the first data packet to a scheduling period of the first data packet.

[0017] In this way, the network device can configure appropriate resources for data packet transmission according to the guaranteed bit rate of the first data packet and the scheduling period of the first data packet.

[0018] In a possible implementation manner, the scheduling period of the first data packet is preconfigured.

[0019] In this way, the service management network element can obtain the value of the scheduling period of the first data packet without interacting with other devices, which can save signaling overhead.

[0020] In a possible implementation manner, the method further includes: receiving a scheduling period of the first data packet.

[0021] In this way, the service management network element can determine the first value.

[0022] In a possible implementation manner, the first scheduling period is adjacent to the second scheduling period.

[0023] In this way, the complexity of processing the data volume of the first data packet can be reduced.

[0024] In a possible implementation, a ratio of a guaranteed bit rate of the first data packet to a scheduling period of the first data packet is less than or equal to a maximum amount of data that can be scheduled by the network device in the first scheduling period.

[0025] In this way, the data volume of the data packets from the service management network element will not exceed the maximum scheduling capability of the network device.

[0026] In a possible implementation, the first scheduling period is a first multicast channel scheduling period (multicast channel scheduling period, MSP), and the second scheduling period is a second MSP.

[0027] In this way, compatibility with existing technologies can be achieved.

[0028] In a second aspect, a communication method is provided, including: receiving a second data packet, the second data packet being a data packet obtained by processing a first data packet, the data volume of the first data packet in a first scheduling period being greater than a first value, and the data volume of the second data packet in the first scheduling period being less than or equal to the first value; and sending the second data packet. .

[0029] The execution subject of the solution described in the second aspect may be a network device, or a module or chip for executing the function of the network device, etc., which is not limited. For ease of description, the following description is taken as an example of a network device.

[0030] A possible implementation method is that the second data packet is a data packet obtained after processing the first data packet, including: the second data packet is a data packet obtained by allocating additional data volume of the first data packet to the second scheduling period, and the additional data volume of the first data packet is the difference between the data volume of the first data packet in the first scheduling period and the first value.

[0031] In a possible implementation, the first value is a maximum amount of data that can be scheduled by the network device in the first scheduling period.

[0032] In a possible implementation manner, the method further includes: sending a first value.

[0033] In a possible implementation manner, the scheduling period of the first data packet is preconfigured.

[0034] In a possible implementation manner, the method further includes: sending a scheduling period for the first data packet.

[0035] In a possible implementation manner, the first scheduling period is adjacent to the second scheduling period.

[0036] In a possible implementation, a ratio of a guaranteed bit rate of the first data packet to a scheduling period of the first data packet is less than or equal to a maximum amount of data that can be scheduled by the network device in the first scheduling period.

[0037] In a possible implementation, the first scheduling period is a first MSP, and the second scheduling period is a second MSP.

[0038] The above description can refer to the corresponding description in the first aspect and will not be repeated here.

[0039] According to a third aspect, a communication system is provided, including: a service management network element and a network device; the service management network element is used to receive a first data packet, the data volume of the first data packet in a first scheduling period is greater than a first value; the service management network element is used to send a second data packet to the network device, the second data packet is a data packet obtained after the service management network element processes the first data packet, and the data volume of the second data packet in the first scheduling period is less than or equal to the first value; the network device is used to receive the second data packet; and the network device is also used to send the second data packet.

[0040] A possible implementation method is that the second data packet is a data packet obtained after the service management network element processes the first data packet, including: the second data packet is a data packet obtained by the service management network element allocating the additional data volume of the first data packet to the second scheduling period, and the additional data volume of the first data packet is the difference between the data volume of the first data packet in the first scheduling period and the first value.

[0041] In a possible implementation, the first value is a maximum amount of data that can be scheduled by the network device in the first scheduling period.

[0042] In a possible implementation method, the communication system also includes: a mobility management entity network element and a gateway network element; a network device, used to send a first value to the mobility management entity network element: a mobility management entity network element, used to receive the first value, and used to send the first value to the gateway network element; a gateway network element, used to receive the first value, and used to send the first value to the service management network element.

[0043] In a possible implementation manner, the first value is a ratio of a guaranteed bit rate of the first data packet to a scheduling period of the first data packet.

[0044] In a possible implementation manner, the scheduling period of the first data packet is preconfigured.

[0045] In a possible implementation, the communication system also includes: a mobility management entity network element and a gateway network element; a network device, used to send a scheduling period of the first data packet to the mobility management entity network element; a mobility management entity network element, used to receive a scheduling period of the first data packet, and used to send a scheduling period of the first data packet to the gateway network element; a gateway network element, used to receive a scheduling period of the first data packet, and used to send a scheduling period of the first data packet to the service management network element.

[0046] In a possible implementation manner, the first scheduling period is adjacent to the second scheduling period.

[0047] In a possible implementation, a ratio of a guaranteed bit rate of the first data packet to a scheduling period of the first data packet is less than or equal to a maximum amount of data that can be scheduled by the network device in the first scheduling period.

[0048] In a possible implementation, the first scheduling period is a first MSP, and the second scheduling period is a second MSP.

[0049] In a fourth aspect, a communication device is provided, which may be a service management network element, or a device in a service management network element (for example, a chip (also called a chip system), or a circuit), or a device that can be used in combination with a service management network element.

[0050] In a possible implementation, the communication device includes a module or unit corresponding to each of the methods / operations / steps / actions described in any one of the first aspects. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software.

[0051] In a fifth aspect, a communication device is provided, which may be a network device, or a device in a network device (for example, a chip (also known as a chip system), or a circuit), or a device that can be used in conjunction with a network device.

[0052] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in any one of the second aspects. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software.

[0053] In a sixth aspect, a communication device is provided, comprising a processor, wherein the processor is used to enable the communication device to execute the method described in the first aspect and any possible method described in the first aspect by executing a computer program or instruction, or by a logic circuit; or to enable the communication device to execute the method described in the second aspect and any possible method described in the second aspect.

[0054] In a possible implementation manner, the communication device further includes a memory for storing the computer program or instruction.

[0055] In a possible implementation manner, the communication device further includes a communication interface, which is used to input and / or output signals.

[0056] In the seventh aspect, a communication device is provided, comprising a logic circuit and an input / output interface, the input / output interface being used to input and / or output signals, the logic circuit being used to execute the method described in the first aspect and any possible embodiment of the first aspect; or, the logic circuit being used to execute the method described in the second aspect and any possible embodiment of the second aspect.

[0057] In an eighth aspect, a computer-readable storage medium is provided, on which a computer program or instruction is stored. When the computer program or the instruction is run on a computer, the method described in the first aspect and any possibility of the first aspect is executed; or, the method described in the second aspect and any possibility of the second aspect is executed.

[0058] In the ninth aspect, a computer program product is provided, comprising instructions, which, when executed on a computer, cause the method described in the first aspect and any possible method of the first aspect to be executed; or, cause the method described in the second aspect and any possible method of the second aspect to be executed.

[0059] The descriptions of the beneficial effects of the second to ninth aspects may correspond to the descriptions of the beneficial effects of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figure 1 It is a schematic block diagram of a communication system 100 to which an embodiment of the present application is applicable.

[0061] Figure 2 is a schematic block diagram of a GCS architecture 200 .

[0062] Figure 3 It is a schematic diagram of the interaction flow of the communication method 300 according to an embodiment of the present application.

[0063] Figure 4 This is a schematic diagram of the relationship between data packet 1 and data packet 2.

[0064] Figure 5 It is a schematic diagram showing the change in the data volume of a data packet before and after processing.

[0065] Figure 6 It is a schematic diagram of the interaction flow of the communication method 600 according to an embodiment of the present application.

[0066] Figure 7It is a schematic diagram of the interaction flow of the communication method 700 according to an embodiment of the present application.

[0067] Figure 8 It is a schematic block diagram of a communication device 800 according to an embodiment of the present application.

[0068] Fig. 9 It is a schematic block diagram of a communication device 900 according to an embodiment of the present application. DETAILED DESCRIPTION

[0069] In order to facilitate understanding of the embodiments of the present application, the following points are first explained.

[0070] 1. In this application, unless otherwise specified, "plurality" means two or more.

[0071] 2. In each embodiment of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment according to their internal logical relationships.

[0072] 3. The various digital numbers involved in this application are only used for the convenience of description and are not used to limit the scope of protection of this application. The size of the serial numbers involved in this application does not mean the order of execution. The execution order of each process should be determined by its function and internal logic. For example, the terms "first", "second", "third", "fourth" and other various terminology labels (if any) in the specification and claims and drawings of this application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. Among them, the data used in this way can be interchangeable where appropriate, so that the embodiments described here can be implemented in an order other than what is illustrated or described here.

[0073] At the same time, any embodiment or design described in the present application as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0074] 4. The terms "comprise", "include", "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product or apparatus.

[0075] 5. In this application, "used to indicate" can be understood as "enable", and "enable" can include direct enablement and indirect enablement. When describing that a certain information is used to enable A, it can include that the information directly enables A or indirectly enables A, and it does not mean that the information must carry A.

[0076] The information enabled by the information is called information to be enabled. In the specific implementation process, there are many ways to enable the information to be enabled, such as but not limited to, the information to be enabled can be directly enabled, such as the information to be enabled itself or the index of the information to be enabled. The information to be enabled can also be indirectly enabled by enabling other information, wherein there is an association relationship between the other information and the information to be enabled. It is also possible to enable only a part of the information to be enabled, while the other parts of the information to be enabled are known or agreed in advance. For example, the enabling of specific information can also be achieved by means of the arrangement order of each piece of information agreed in advance (such as specified by the protocol), thereby reducing the enabling overhead to a certain extent. At the same time, the common parts of each piece of information can also be identified and enabled uniformly to reduce the enabling overhead caused by enabling the same information separately.

[0077] 6. In this application, "pre-configuration" may include pre-definition, such as protocol definition. Among them, "pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including each network element), and this application does not limit its specific implementation method.

[0078] 7. The term "storage" or "saving" as used in this application may refer to saving in one or more memories. The one or more memories may be provided separately or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories may also be partially provided separately and partially integrated in a decoder, a processor, or a communication device. The type of memory may be any form of storage medium, without limitation.

[0079] 8. The "protocol" referred to in this application may refer to a standard protocol in the field of communications, for example, the fourth generation (4 th generation, 4G) network, fifth generation (5 th generation, 5G) network protocol, new radio (NR) protocol, 5.5G network protocol, sixth generation (6 th generation, 6G) network protocols and related protocols used in future communication systems are not limited to this.

[0080] 9. The dotted arrows or boxes in the schematic diagrams of the drawings in the specification of this application represent optional steps or optional modules.

[0081] 10. In this application, unless otherwise specified, " / " indicates that the objects associated with each other are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is only a description of the association relationship between the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. Among them, A and B can be singular or plural.

[0082] In order to better understand the technical solution of the present application, the following description is made from the following aspects: communication system, method and device.

[0083] 1. Communication system

[0084] In order to solve the technical problems mentioned in the background technology section, the present application provides an applicable communication system 100. Figure 1 As shown, the communication system 100 includes: a service management network element 110 and a network device 120. Optionally, the communication system 100 may further include: a mobility management entity network element 130 and a gateway network element 140.

[0085] In the communication system 100, the service management network element 110 has the function of service management, for example, it can be responsible for: session management (such as session start, session stop, etc.); proxy and transmission; service data synchronization and forwarding management, etc. The mobility management entity network element 130 has the ability of mobility management, for example, it can be responsible for: receiving and transmitting session control information to the network device 120; session management (such as session start, session stop, etc.). The gateway network element 140 has the ability of a gateway, for example, it can be responsible for: transmitting session control information to the mobility management entity network element 130, and forwarding service data packets to the network device 120, etc.

[0086] In the communication system 100, data and signaling between the service management network element 110 and the network device 120 can be transmitted through the mobility management entity network element 130 and the gateway network element 140. For example, the service management network element 110 sends data 1 to the gateway network element 140, and the gateway network element 140 sends data 1 to the network device 120; the network device 120 sends signaling 1 to the mobility management entity network element 130, the mobility management entity network element 130 sends signaling 1 to the gateway network element 140, and the gateway network element 140 sends signaling 1 to the service management service 110.

[0087] It should be noted that the names of the service management network element 110, the mobility management entity network element 130 and the gateway network element 140 may be different or the same in different communication architectures, and are not limited. The following description takes the application of the communication system 100 to the GCS architecture as an example.

[0088] Figure 2is a schematic block diagram of the GCS architecture 200. Figure 2 As shown, the GCS architecture 200 includes: terminal equipment, network equipment, MBMS gateway (gateway, GW), broadcast / multicast service center (BMSC), GCS application server (group communication service application service, GCSAS), multi-cell / multicast coordination entity (MCE), mobility management entity (MME), home subscriber server (HSS), policy and charging rules function (PCRF), serving gateway (S-GW) and public data network (PDN) gateway (P-GW). Among them, MCE can be a module of the network equipment, that is, integrated in the network equipment, or deployed outside the network equipment, which is not limited. For the convenience of description, the following description takes the deployment of MCE outside the network equipment as an example.

[0089] Specifically, the terminal device communicates with the network device through the Uu interface, the network device communicates with the MBMS-GW through the M1 interface, the MBMS-GW communicates with the BMSC through the SG-mb / SGi-mb interface, and the BMSC communicates with the GCSAS1 and GCSAS2 through the MB2-U / MB2-C interface. The network device communicates with the MCE through the M2 interface, the MCE communicates with the MME through the M3 interface, the MME communicates with the MBMS-GW through the Sm interface, the MME communicates with the network device through the S1-MME interface, the MME communicates with the HSS through the S6a interface, the MME communicates with the S / P-GW through the S11 interface, and the S / P-GW communicates with the network device through the S1-u interface. GCSAS1 communicates with the PCRF through the Rx interface, and GCSAS communicates with the S / P-GW through the SGi interface.

[0090] Furthermore, the M1 interface is used for MBMS-GW to send MBMS services to network devices in an Internet protocol (IP) multicast manner. The M2 interface is a control plane interface between the network device and the MCE, and is used to transmit eMBMS service session control information. The M3 interface is used to transmit MBMS session control information and MBMS service information, such as MBMS broadcast area, quality of service (QoS) of MBMS services, etc. The Sm interface is used to transmit the bearer context information of the eMBMS service. The SG-mb interface is used to transmit information such as control information of the eMBMS service, eMBMS service parameters, and eMBMS service bearer context maintenance. The S1-MME interface is a signaling plane interface between the network device and the MME. The signaling connection function of the S1-MME interface provides reliable transmission for wireless network signaling. The S6a interface is a signaling plane interface between the MME and the HSS, and is used to provide functions related to user subscription data management and authentication. The S11 interface is the signaling interface between the MME and the S-GW, and is mainly used to transmit bearer creation, update and deletion request information between the MME and the S-GW, and when the UE is in the evolved packet system connection management (ECM)-idle (IDLE) state, the S-GW notifies the MME to page the UE and restore the S1 bearer. The Rx interface is the interface between the GCSAS and the PCRF, and is used for the GCSAS to interact with the application function (AF) system, and to receive service requests from the application server. The GCSAS exchanges information with the AF system through the Rx interface to complete the application-based policy control function. The SGi interface is the interface between the PGW-U and the PDN, and is used for users to access the PDN network. The SGi-mb interface is used for multicast transmission of MBMS service data packets. The MB2-C interface is used for control plane negotiation, specifically for: requesting the allocation / cancellation of a group of temporary mobile group identities (TMGI), and requesting the activation, deactivation and modification of MBMS bearers. MB2-U is used for user plane data transmission.

[0091] Specifically, the terminal device can be used to:

[0092] 1) Exchange group communication 1 (GC1) signaling with GCSAS (including GCS session and group management aspects);

[0093] 2) receiving data from the GCSAS using unicast delivery or MBMS delivery or both;

[0094] 3) Use unicast to send uplink data to GCSAS;

[0095] 4) Support service continuity procedures to switch between unicast delivery and MBMS delivery;

[0096] 5) Monitor and receive one or more MBMS services simultaneously.

[0097] GCSAS can be used to:

[0098] 1) Exchange GC1 signaling with terminal equipment (including GCS session and group management aspects);

[0099] 2) receiving uplink data sent by a terminal device through unicast; transmitting data to all terminal devices belonging to a group, which may be transmitted by unicast and / or MBMS;

[0100] 3) Transmit application-level session information to PCRF via the Rx interface;

[0101] 4) Support the service continuity process of terminal equipment switching between unicast transmission and MBMS transmission.

[0102] BMSC can be used for:

[0103] 1) eMBMS session management (such as session start, session stop, etc.);

[0104] 2) Agent and transmission;

[0105] 3) Business data synchronization and forwarding management, etc.

[0106] MBMS-GW can be used for:

[0107] 1) Deliver MBMS session control information to MME and forward MBMS services to network devices.

[0108] MME can be used to:

[0109] 1) Receive and transmit MBMS session control information to MCE;

[0110] 2) MBMS session management (such as session start, session stop, etc.).

[0111] MCE can be used to:

[0112] 1) Receive and transmit MBMS session control information to network equipment;

[0113] 2) Schedule radio resources to ensure that the radio resources occupied by each cell in a single MBMS area (MBSFN area, MA) are consistent;

[0114] 3) MBMS session management (such as session start, session stop, etc.).

[0115] Network devices are used to:

[0116] 1) Receive control and resource scheduling from MCE;

[0117] 2) Receive the IP multicast message (i.e., eMBMS service data) sent by MBMS-GW, and broadcast it to the designated MBMS service area.

[0118] Figure 2 The naming of each network element shown is just a name, and the name does not limit the function of the network element itself. In 5G networks and future networks, the above network elements can be named by other names, which is not limited. For example, in 6G networks, some or all of the above network elements can use the terminology in 5G, or they may be named by other names. They are explained here uniformly and will not be repeated below.

[0119] In addition, the "network element" in this article may also be referred to as a network function instance, device, apparatus or module, etc., without limitation. Among them, the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation. This application does not exclude the possibility of adopting other names in 5G networks and other future networks. In addition, the interface name between the above-mentioned network elements is only an example. The name of the interface in the specific implementation may be other names, which is not limited. In addition, the name of the information (or signaling) transmitted between the above-mentioned network elements is only an example and does not constitute any limitation on the function of the information itself.

[0120] Figure 1 The service management network element 110 in the example can be Figure 2 The BMSC in the mobility management entity network element 130 may be Figure 2 The MME in the gateway network element 140 may be Figure 2 The MBMS-GW in the network device 120 may be Figure 2 For the convenience of description, the following description is made by taking the service management network element 110 as a BMSC, the mobility management entity network element 130 as an MME, and the gateway network element 140 as an MBMS-GW as an example.

[0121] Combined with the following Figure 3 The interaction between the BMSC and the network device is further described.

[0122] 2. Communication method

[0123] Figure 3 It is a schematic diagram of the interaction flow of the communication method 300 according to an embodiment of the present application. Figure 3The method shown can be executed by the BMSC and the network device, or by a module and / or device (for example, a chip or an integrated circuit, etc.) with corresponding functions installed in the BMSC and the network device, without limitation. The following description takes the BMSC and the network device as an example. Figure 3 As shown, the method 300 includes:

[0124] S310. The BMSC receives data packet 1 (eg, a first data packet). The data volume of data packet 1 in scheduling period 1 (eg, a first scheduling period) is greater than a first value.

[0125] BMSC receives data packet 1 from GCSAS. GCSAS may send multiple data packets to BMSC, for example, GCSAS sends data packet a, data packet b, data packet c, and ... to BMSC. The data volume of each data packet in its corresponding scheduling period may be different or the same. Taking the different data volumes of different data packets in their corresponding scheduling periods as an example, for example, the data volume of data packet a in scheduling period a is 40Kbit, the data volume of data packet b in scheduling period b is 20Kbit, the data volume of data packet c in scheduling period c is 30Kbit, and so on. Therefore, the present application is described by taking data packet 1 representing a data packet with a data volume greater than the first value as an example. For example, the above-mentioned data packet 1 may be the aforementioned data packet a. Scheduling period 1 may be the aforementioned scheduling period a.

[0126] S320: The BMSC sends data packet 2 to the network device. Data packet 2 is a data packet obtained after the BMSC processes data packet 1, and the data volume of data packet 2 in scheduling cycle 1 is less than or equal to the first value.

[0127] In a possible implementation, the BMSC sends the data packet 2 to the network device. This may be as follows: the BMSC sends the data packet 2 to the MBMS-GW, and the MBMS-GW sends the data packet 2 to the network device.

[0128] Among them, data packet 2 is a data packet obtained after the BMSC processes data packet 1. The BMSC can process data packet 1 according to the first value so that the data volume of data packet 2 obtained after processing data packet 1 in scheduling period 1 is less than or equal to the first value.

[0129] In a possible implementation manner, data packet 2 is a data packet obtained by BMSC allocating the additional data volume of data packet 1 to scheduling period 2, and the additional data volume of data packet 1 is the difference between the data volume of data packet 1 in scheduling period 1 and the first value. In this way, BMSC reallocates the data volume of data packet 1 in scheduling period 1 so that the data volume of data packet 2 obtained after processing data packet 1 in scheduling period 1 is less than or equal to the first value.

[0130] The above-mentioned scheduling period 2 can be an adjacent scheduling period of scheduling period 1 (it can be the previous scheduling period of scheduling period 1 or the next scheduling period of scheduling period 1, without limitation). There are also multiple scheduling periods between scheduling period 1 and scheduling period 2, without limitation. For the description of data packet 1 and data packet 2, please refer to Figure 4 .

[0131] Figure 4 This is a schematic diagram of the relationship between data packet 1 and data packet 2. Figure 4 As shown, taking the first value of 30Kbit as an example, the data volume of data packet 1 in scheduling cycle 1 is 40Kbit, and BMSC allocates 10Kbit of data volume of data packet 1 in scheduling cycle 1 to scheduling cycle 2 to obtain data packet 2, and the data volume of data packet 2 in scheduling cycle 1 is 30Kbit. Among them, scheduling cycle 2 is an adjacent scheduling cycle of scheduling cycle 1 (taking scheduling cycle 2 as the next scheduling cycle of scheduling cycle 1 as an example for description, but not limited to other scenarios).

[0132] To further describe the changes in the amount of data before and after processing, see Figure 5 .

[0133] Figure 5 This is a schematic diagram showing the change in the amount of data in a data packet before and after processing. Figure 5 As shown in (a), GCSAS sends data packets a, b and c to BMSC. The data volume of data packet a in scheduling period a is 40Kbit (which can be the aforementioned data packet 1), the data volume of data packet b in scheduling period b is 20Kbit, and the data volume of data packet c in scheduling period c is 30Kbit. The first value is 30Kbit, and BMSC processes data packet a and data packet b according to the first value to obtain processed data packets a and b. Among them, the data volume of processed data packet a (which can be the aforementioned data packet 2) in scheduling period a is 30Kbit, and the data volume of processed data packet b in scheduling period b is 30Kbit.

[0134] Specifically, the BMSC allocates the extra data volume 10Kbit (represented by a cross-texture pattern) of data packet a in scheduling period a to scheduling period b, so that the data volume of the processed data packet a in scheduling period a is 30Kbit. This extra data volume is sent together with data packet b in scheduling period b. Figure 5 In the example shown, data packet c may not be modified because data packet c does not exceed the first value.

[0135] like Figure 5As shown in (b), GCSAS sends data packets a, b and c to BMSC, the data volume of data packet a (which may be the aforementioned data packet 1) in scheduling period a is 40Kbit, the data volume of data packet b in scheduling period b is 30Kbit, the data volume of data packet c in scheduling period c is 20Kbit, and the first value is 30Kbit. BMSC processes data packets a, b and c according to the first value to obtain processed data packets a (which may be the aforementioned data packet 2), b and c. Among them, the data volume of processed data packet a in scheduling period a is 30Kbit, the data volume of processed data packet b in scheduling period b is 30Kbit, and the data volume of processed data packet c in scheduling period c is 30Kbit.

[0136] Specifically, the BMSC allocates the additional data volume of 10Kbit (represented by a cross-texture box) of data packet a in scheduling period a to scheduling period b, so that the data volume of the processed data packet a in scheduling period a is equal to 30Kbit, and the data volume of data packet b with an additional data volume of 10Kbit of data packet 1 in scheduling period b is 40Kbit. The additional data volume of 10Kbit of data packet 1 and the additional data volume of 10Kbit of data packet b in scheduling period b (represented by a cross-texture box) can be reallocated to data packet c, so that the additional data volume of data packet b and the data volume of data packet c in scheduling period c are 30Kbit.

[0137] When the data volume of the data packet received by the BMSC is greater than the first value, the BMSC may process the data packet so that the data volume of the data packet obtained after processing is less than or equal to the first value. In this way, the network device may configure appropriate resources for the data packet, thereby avoiding the phenomenon of excessive or insufficient resource allocation.

[0138] In summary, the BMSC adjusts the data volume of the data packet in the scheduling period according to the first value, so that the data volume of the processed data packet in the scheduling period is less than or equal to the first value, so that the data volume distribution of the data packet in the scheduling period is more consistent.

[0139] In a possible implementation, the first value may be a maximum amount of data that the network device can schedule in scheduling period 1. In this way, the amount of data packets from the BMSC in the scheduling period will not exceed the maximum amount of data that the network device can schedule in the scheduling period, which can effectively avoid the occurrence of data packet loss.

[0140] In a possible implementation, the first value may be a guaranteed bit rate (GBR) of data packet 1 and a value of a scheduling period of data packet 1. In this way, the network device may configure appropriate resources for data packet transmission according to the GBR of data packet 1 and the scheduling period of data packet 1, and the data volume of data packets from the BMSC may be distributed more evenly.

[0141] For example, the GBR of data packet 1 is 750 Kbit / s, and the scheduling period of data packet 1 is 40 ms (it can also be other values, not limited to this). 1 second includes 25 scheduling periods, and the data volume of data packet 1 in 1 second is averaged to the data volume of each scheduling period: 750 Kbit (1 / 40) = 30 Kbit. Therefore, the first value can be 30 Kbits.

[0142] In a possible implementation, the value of the GBR of data packet 1 and the scheduling period of data packet 1 is less than or equal to the maximum amount of data that can be scheduled by the network device in the scheduling period 1. In this way, the amount of data packets from the BMSC in the scheduling period will not exceed the maximum amount of data that can be scheduled by the network device in the scheduling period, which can effectively avoid the occurrence of data packet loss.

[0143] In another possible implementation, the first value may be preconfigured in the BMSC, or sent by a network device (such as a base station or an access network device) to the BMSC. For example, the network device sends the maximum amount of data that the network device can schedule within a scheduling period to the BMSC, or the network device sends the scheduling period of the data packet 1 to the BMSC. In this way, the BMSC may process the data packet 1 according to the first value.

[0144] It is understandable that if the BMSC does not adjust the data volume of the data packets from the GCSAS within the scheduling period, the network device cannot configure appropriate resources for the data packets from the BMSC for transmission. For example, the data volume of data packet a in scheduling period a is 40Kbit, the data volume of data packet b in scheduling period b is 20Kbit, and the data volume of data packet c in scheduling period c is 30Kbit. If the network device configures resources for transmitting data packets with a data volume of 40Kbit, it will cause a waste of resources for data packets with a data volume of 20Kbit and 30Kbit; if the network device configures resources for transmitting data packets with a data volume of 30Kbit, it will cause insufficient resource allocation for data packets with a data volume of 40Kbit, and packet loss may occur.

[0145] It should be noted that the above scheduling period may be MSP, for example, the scheduling period 1 is MSP1, the scheduling period 2 is MSP2, etc. In this way, it can be compatible with the existing technology.

[0146] In summary, the present application supports BMSC to process data packets so that the data volume of the processed data packets within the scheduling period is less than or equal to the first value, thereby making the data volume distribution of the data packets within the scheduling period more consistent. In this way, the network equipment can uniformly configure resources for data transmission.

[0147] It should be noted that the type of the data packets (such as data packet 1 or data packet a, etc.) appearing in the above content may be MBMS service data packets, or may be data packet types similar or close to MBMS service data packets, and this is not limited.

[0148] Combined with the following Figure 6 and Figure 7 right Figure 3 The method shown is further described.

[0149] Figure 6 600 is a schematic diagram of the interaction process of the communication method 600 of the embodiment of the present application. Figure 6 As shown, the method 600 includes:

[0150] S601. GCSAS sends a request message 1 to BMSC, where the request message 1 is used to request activation of an MBMS bearer.

[0151] Correspondingly, the BMSC receives the request information 1, and determines based on the request information 1 that an MBMS bearer needs to be activated, which is used to carry the transmission of MBMS service data 1. The MBMS service data 1 includes the data packet 1 mentioned above.

[0152] The request information 1 includes one or more of the following: temporary mobile group identity (TMGI) of the MBMS bearer (TMGI is optional), quality of service (QoS), and MBMS broadcast area and start time.

[0153] Among them, TMGI is used to identify the group of eMBMS sessions. QoS indicates the GBR, maximum bit rate (MBR) and priority requirements of the service flow. MBMS broadcast area is used to indicate the area where the receiving object of MBMS service data 1 is located, and the start time is used to indicate the transmission time of MBMS service data 1. For a detailed description of the above parameters, please refer to the description of sections 5.3.2 and 6.6.2 in the 3GPP protocol technical standard (technical specification, TS) 29.468, which will not be repeated here.

[0154] In addition, the request information 1 may also include the service type and GBR of the MBMS service data 1, etc., which can be used by the BMSC to determine the value of the scheduling period of the MBMS service data 1, and further determine the first value.

[0155] S602. The BMSC sends a session start request message 1 to the MBMS-GW, which is used to indicate that the transmission of the MBMS service data 1 is about to start.

[0156] Correspondingly, the MBMS-GW receives the session start request information 1.

[0157] The session start request information 1 includes the session attribute information 1 of the MBMS service data 1, and the session attribute information 1 includes one or more of the following: TMGI, flow identifier, QoS, MBMS service area, cell identifier list, session identifier, estimated session duration, MBMS control plane node list configured for MBMS-GW, transmission time of MBMS service data 1, MBMS service data 1 transmission start, access indicator, etc. The TMGI and QoS in the above message can refer to the above description and will not be repeated here.

[0158] Among them, TMGI is used to identify the group of eMBMS sessions. Since an eMBMS may carry multiple service flows, the flow identifier is used to identify which service flow is currently being transmitted. The MBMS service area represents the range in which the eMBMS session needs to be sent (MBMS service areas are configured on the MCE and the base station, and the service flow corresponding to the session is only sent under the corresponding SA). The cell ID list is used to indicate in which cells broadcast multicast services are currently being broadcast. The session identifier is used to identify the ID of the current session. The estimated session duration indicates how long the current session may last. The MBMS control plane node list configured for the MBMS-GW is used to indicate the control plane nodes participating in the eMBMS session. The transmission time of MBMS service data 1 is used to indicate the specific time of the transmission of MBMS service data 1. The start of MBMS service data 1 transmission is used to indicate that the transmission of MBMS service data 1 is about to start. For a detailed description of the above parameters, please refer to the descriptions in sections 20.3.1 and 20.4.1 of the 3GPP protocol TS29.061, which will not be repeated here.

[0159] S603. MBMS-GW sends a session start response message (session start response) 1 to BMSC.

[0160] Correspondingly, the BMSC receives the session start response information 1.

[0161] Among them, the session start response information 1 is a response to the session start request information 1. The session response information 1 may include: a result code (Result-Code) (which is used to indicate whether the request is successful or failed) and MBMS-GW-UDP-Port (used to indicate the port on which the MBMS-GW receives BMSC data), etc. For details, refer to Section 20.4.2 of 3GPP protocol TS29.061. For a detailed description of the above parameters, refer to Sections 20.3.1 and 20.4.2 of 3GPP protocol TS29.061, which will not be repeated here.

[0162] S604. BMSC sends a response message 1 to GCSAS.

[0163] Correspondingly, GCSAS receives response information 1, which is used to indicate that MBMS bearer 1 has been activated.

[0164] The above-mentioned response information 1 is a response to the request information 1. The response information 1 includes one or more of the following: bearer activation result (which can be used to indicate that the MBMS bearer has been activated), TMGI, allocated flow ID, service description, BM-SC user plane IP address and port number, expiration time, etc. For a detailed description of the response information 1, please refer to 3GPP TS29.4685.3.2 and 6.4.7, which will not be repeated here.

[0165] S605 . MBMS-GW creates MBMS bearer context 1 , which is used to reserve resources for transmission of MBMS service data 1 .

[0166] Specifically, the MBMS-GW stores the session attribute information 1 and the MBMS control plane node list in the MBMS bearer context 1, and allocates a transport network IP multicast address.

[0167] S606. MBMS-GW sends session start request information 2 to MME.

[0168] Correspondingly, the MME receives the session start request information 2.

[0169] Specifically, the session start request information 2 includes the session attribute information 2 of the MBMS service data 1, and the session attribute information 2 includes one or more of the following: TMGI, flow identifier, QoS, MBMS service area, cell ID list, session identifier, estimated session duration, transmission network IP multicast address, etc. For a detailed description of the above parameters, please refer to the description of section 7.13.1 of 3GPP protocol TS29.274, which will not be repeated here.

[0170] S607 . The MME creates an MBMS bearer context 2 , which is used to notify the corresponding MCE to create a session corresponding to transmitting the MBMS service data 1 .

[0171] Specifically, the MME stores the session attribute information 2 in the MBMS bearer context 2 .

[0172] S608. MME sends session start request information 3 to MCE.

[0173] Correspondingly, the MCE receives the session start request information 3 , wherein the session start request information 3 includes the session attribute information 2 .

[0174] S609. MCE sends session start response information 3 to MME.

[0175] Correspondingly, the MME receives the session start response information 3 , and determines based on the session start response information 3 that the MCE has received the session start request information 3 .

[0176] The above-mentioned session start response information 3 is a response to the session start request information 3 .

[0177] S610. MME sends session start response information 2 to MBMS-GW.

[0178] Correspondingly, the MBMS-GW receives the session start response information 2 , and determines based on the session start response information 2 that the MME has received the session start request information 2 .

[0179] The above-mentioned session start response information 2 is a response to the session start request information 2 .

[0180] S611. MCE sends a session start request message 4 to the network device.

[0181] Correspondingly, the network device receives the session start request information 4 .

[0182] Specifically, the session start request information 4 includes the session attribute information 3 of the MBMS service data 1, and the session attribute information 3 includes one or more of the following: TMGI, MBMS session ID, MBMS service area, transmission network IP multicast address, multicast source IP address, etc. For a detailed description of the above parameters, please refer to the description of section 8.3.2 of 3GPP protocol TS23246, which will not be repeated here.

[0183] S612: The network device creates an MBMS bearer context 3, which is used to reserve resources for transmission of MBMS service data 1.

[0184] Specifically, the network device stores session attribute information 3 in the MBMS bearer context 3.

[0185] More specifically, the network device saves the session attribute information 3 by creating the MBMS bearer context 3, so as to subsequently perform multicast address joining, air interface resource allocation, etc. according to the information.

[0186] S613. The network device sends a session start response message 4 to the MCE.

[0187] Correspondingly, the MCE receives the session start response information 4 , and determines based on the session start response information 4 that the network device has received the session start request information 4 .

[0188] The above-mentioned session start response information 4 is a response to the session start request information 4 .

[0189] S614. The network device allocates wireless resources for MBMS service data 1.

[0190] Specifically, the network device generally configures wireless resources for MBMS service data 1 according to the GBR of MBMS service data 1, and the unit of GBR is seconds, but the network device actually schedules data according to MSP, and the unit of MSP is milliseconds. Generally speaking, the network device can normally schedule the data volume of MBMS service data 1 in each MSP. However, since the amount of data in each MSP may be different, the network device may cause packet loss in some MSPs due to excessive data volume. Therefore, the data volume of the data packet sent to the network device needs to be adjusted so as not to exceed the maximum scheduling capacity of the network device. The specific adjustment method can be seen in the steps below.

[0191] S615. The network device joins the IP multicast address.

[0192] Specifically, if the network device accepts IP multicast distribution, it adds the transmission network IP multicast address (including the IP address of the multicast source) allocated by the MBMS-GW to enable the receiving function of the MBMS service data 1 .

[0193] Specifically, since the multicast data is sent to the network device by MBMS-GW in the form of multicast, the network device needs to join the multicast group (that is, join the transmission network IP multicast address allocated by MBMS-GW) to receive the multicast packet sent by MBMS-GW.

[0194] S616. GCSAS sends MBMS service data 1 to BMSC.

[0195] Correspondingly, the BMSC receives MBMS service data 1.

[0196] For a detailed description of S601-S616, please refer to the description in section 8.3.2 of 3GPP protocol TS23246, which will not be repeated here.

[0197] It should be noted that the sequence between S601-S616 can be as indicated by the number, the number in front means the execution is first, and the number in the back means the execution is later, but this is not limited. For example, S616 can be executed after S604 (for example, it can be synchronized with S605, etc.). Therefore, the above description is only an example and not a final limitation. Among them, the content described in S601-S615 can be understood as the process of preparing for the transmission of MBMS service data 1 between multiple network elements such as GCSAS-BMSC-MBMS-GW-MME-MCE. Therefore, the detailed description can refer to the description of the existing protocol, which will not be repeated here.

[0198] S617. The BMSC processes the MBMS service data 1 according to the first value to obtain the MBMS service data 2.

[0199] Specifically, the BMSC obtains the service type and GBR of the MBSMS service data 1 through the request information 1, and finds the scheduling period corresponding to the MBMS service data 1 from the pre-configured parameters. Further, the BMSC processes the received MBMS service data 1 according to the first value to obtain the MBMS service data 2. The first value is the ratio of the GBR of the MBMS service data 1 to the scheduling period. For a detailed description, see S320, Figure 4 as well as Figure 5 The description of etc. will not be repeated here.

[0200] S618. BMSC sends MBMS service data 2 to MBMS-GW.

[0201] Correspondingly, the MBMS-GW receives the MBMS service data 2.

[0202] S619. MBMS-GW sends MBMS service data 2 to the network device.

[0203] Correspondingly, the network device receives MBMS service data 2.

[0204] S620. The network device sends MBMS service data 2 to the terminal device.

[0205] Correspondingly, the terminal device receives MBMS service data 2.

[0206] In summary, the present application supports BMSC to process data packets so that the data volume of the processed data packets within the scheduling period is less than or equal to the first value, thereby making the data volume distribution of the data packets within the scheduling period more consistent. In this way, the network equipment can uniformly configure resources for data transmission.

[0207] In addition, by pre-configuring the scheduling period of each type of service in the BMSC, the BMSC can directly obtain the scheduling period of each type of service, thereby reducing the signaling overhead of the BMSC exchanging scheduling periods with other network elements.

[0208] It should be noted that Figure 6 The content shown is described by taking the scheduling period as a preconfigured example. The maximum amount of data that the network device can schedule within the scheduling period can also be preconfigured. The two schemes are similar and will not be described in detail. Among them, the present application also supports other methods that enable the BMSC to obtain the scheduling period. Please refer to Figure 7 .

[0209] Figure 7 FIG. 7 is a schematic diagram of the interaction flow of the communication method 700 according to an embodiment of the present application. Figure 7 As shown, the method 700 includes:

[0210] S701. GCSAS sends request information 1 to BMSC.

[0211] For the description of S701, please refer to the description of S601, which will not be repeated here.

[0212] S702. BMSC sends a session start request message 1 to MBMS-GW.

[0213] For the description of S702, please refer to the description of S602, which will not be repeated here.

[0214] S703. BMSC sends a response message 1 to GCSAS.

[0215] For the description of S703, please refer to the description of S604, which will not be repeated here.

[0216] S704 . The MBMS-GW creates an MBMS bearer context 1 , which is used to reserve resources for transmission of MBMS service data 1 .

[0217] For the description of S704, please refer to the description of S605, which will not be repeated here.

[0218] S705. MBMS-GW sends session start request information 2 to MME.

[0219] For the description of S705, please refer to the description of S606, which will not be repeated here.

[0220] S706: MME creates MBMS bearer context 2.

[0221] For the description of S706, please refer to the description of S607, which will not be repeated here.

[0222] S707. MME sends session start request information 3 to MCE.

[0223] For the description of S705, please refer to the description of S608, which will not be repeated here.

[0224] S708. MCE sends session start request information 4 to the network device.

[0225] For the description of S708, please refer to the description of S611, which will not be repeated here.

[0226] S709: The network device allocates wireless resources for MBMS service data 1.

[0227] For the description of S709, please refer to the description of S614, which will not be repeated here.

[0228] S710. The network device sends a session start response message 4 to the MCE.

[0229] For the description of S710, please refer to the description of S613, which will not be repeated here.

[0230] S711. MCE sends a session start response message 3 to MME. The session start response message 3 includes the scheduling period of MBMS service data 1. The scheduling period of MBMS service data 1 may be pre-configured in MCE.

[0231] The present application supports that MCE can pre-configure the correspondence between the scheduling period of MBMS service data 1 and the service type of MBMS service data 1, and can determine the service type of MBMS service data 1 based on session attribute information sent from other network elements, and further determine the scheduling period of MBMS service data 1.

[0232] For the description of S711, please refer to the description of S609, which will not be repeated here.

[0233] S712: MME sends session start response information 2 to MBMS-GW. The session start response information 2 includes the scheduling period of MBMS service data 1.

[0234] For the description of S712, reference may be made to the description of S610 and will not be repeated here.

[0235] S713 . The MBMS-GW sends a session start response message 1 to the BMSC. The session start response message 1 includes a scheduling period of the MBMS service data 1 .

[0236] For the description of S713, please refer to the description of S603, which will not be repeated here.

[0237] S714. The network device joins the IP multicast address.

[0238] For the description of S714, please refer to the description of S615, which will not be repeated here.

[0239] S715. GCSAS sends MBMS service data 1 to BMSC.

[0240] For a detailed description of S701-S715, please refer to the description in section 8.3.2 of 3GPP protocol TS23246, which will not be repeated here.

[0241] S716. The BMSC processes the MBMS service data 1 according to the first value to obtain the MBMS service data 2.

[0242] The BMSC can obtain the service type and GBR of the MBSMS service data 1 from the request information 1, and obtain the scheduling period of the MBMS service data 1 from the session start response information 1. Further, the BMSC processes the received MBMS service data 1 according to the first value (the first value is the ratio between the GBR and the scheduling period) to obtain the MBMS service data 2. For a detailed description, please refer to the aforementioned S320, Figure 4 as well as Figure 5 The description of etc. will not be repeated here.

[0243] S717. BMSC sends MBMS service data 2 to MBMS-GW.

[0244] S718. MBMS-GW sends MBMS service data 2 to the network device.

[0245] S719. The network device sends MBMS service data 2 to the terminal device.

[0246] Correspondingly, the terminal device receives MBMS service data 2.

[0247] In summary, the present application supports BMSC to process data packets so that the data volume of the processed data packets within the scheduling period is less than or equal to the first value, thereby making the data volume distribution of the data packets within the scheduling period more consistent. In this way, the network equipment can uniformly configure resources for data transmission.

[0248] It should be noted that Figure 7 The content shown is described by taking the scheduling period sent by the network device to the BMSC as an example. The network device can also send the maximum amount of data that the network device can schedule within the scheduling period to the BMSC. The two schemes are similar and will not be repeated.

[0249] In addition, by sending the scheduling period from the network device to the BMSC, it is possible to avoid configuring the scheduling period for each type of service on the BMSC, thereby reducing the overhead of the BMSC.

[0250] Finally, the device embodiment of the embodiment of the present application is introduced.

[0251] In order to implement the functions in the method provided in this application, the terminal device and the network device may include a hardware structure and / or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether one of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

[0252] Figure 88 is a schematic block diagram of a communication device 800 of an embodiment of the present application. The communication device 800 includes a processor 810 and a communication interface 820, and the processor 810 and the communication interface 820 can be connected to each other via a bus 830. The communication device 800 can be a network device, a service management network element, etc., or other network elements or devices involved in the above method embodiments.

[0253] Optionally, the communication device 800 may further include a memory 840. The memory 840 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or a portable read-only memory (CD-ROM), and the memory 840 is used for related instructions and data.

[0254] The processor 810 may be one or more central processing units (CPUs). When the processor 810 is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The processor 810 may be a signal processor, a chip, or other integrated circuit that can implement the method of the present application, or a portion of the circuit for processing functions in the aforementioned processor, chip, or integrated circuit. In addition, the communication interface 820 may also be an input / output interface, which is used for input or output of signals or data, or may be an input / output circuit.

[0255] When the communication device 800 is a service management network element, illustratively, the processor 810 is configured to perform the following operations: receiving data packet 1; sending data packet 2, etc.

[0256] When the communication device 800 is a network device, illustratively, the processor 810 is used to perform the following operations: receiving data packet 2; sending data packet 2, etc.

[0257] The above contents are only exemplary descriptions. When the communication device 800 is a network device or a service management network element, it will be responsible for executing the methods or steps related to the network device or the service management network element in the above method embodiments.

[0258] It is understandable that when the communication device 800 is a network device or a service management network element, the communication interface 820 may also be referred to as a transceiver. The above description is only an exemplary description. For specific content, please refer to the content shown in the above method embodiment. Figure 8 The implementation of each operation in can also refer to Figures 3 to 7 The corresponding description of the method embodiment shown.

[0259] Fig. 9 1 is a schematic block diagram of a communication device 900 of an embodiment of the present application. The communication device 900 may be a network device or a service management network element, or may be a chip or module in a network device or a service management network element, for implementing the method involved in the above embodiment. The communication device 900 includes a transceiver unit 910. The transceiver unit 910 is exemplarily introduced below.

[0260] The transceiver unit 910 may include a sending unit and a receiving unit. The sending unit is used to perform a sending action of the communication device, and the receiving unit is used to perform a receiving action of the communication device. For ease of description, the embodiment of the present application combines the sending unit and the receiving unit into one transceiver unit. A unified description is given here, and no further description is given later.

[0261] When the communication device 900 is a service management network element, illustratively, the transceiver unit 910 is used to receive data packet 1; and is also used to send data packet 2, etc.

[0262] Optionally, the communication device 900 may further include a processing unit 920, which is used to execute the content of the steps of processing, coordination, etc. involved in the service management network element. For example, the processing unit 920 is used to process the data packet 1 to obtain the data packet 2.

[0263] When the communication device 900 is a network device, illustratively, the transceiver unit 910 is used to receive data packet 2 and send data packet 2.

[0264] The above contents are only exemplary descriptions. When the communication device 900 is a network device or a service management network element, it will be responsible for executing the methods or steps related to the network device or the service management network element in the above method embodiments.

[0265] Optionally, the communication device 900 further includes a storage unit 930, and the storage unit 930 is used to store a program or code for executing the aforementioned method.

[0266] Figure 8 and Fig. 9 The device embodiment shown is used to implement Figures 3 to 7 The content described. Figure 8 and Fig. 9 The specific execution steps and methods of the device shown can refer to the contents described in the aforementioned method embodiment.

[0267] The present application also provides a chip, including a processor, for calling and executing instructions stored in a memory from the memory, so that a communication device equipped with the chip executes the methods in the above examples.

[0268] The present application also provides another chip, including: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is used to execute the code in the memory, and when the code is executed, the processor is used to execute the method in each of the above examples. Optionally, the chip also includes a memory, and the memory is used to store computer programs or codes.

[0269] The present application also provides a processor, which is coupled to a memory and is used to execute the methods and functions involving a network device or a terminal device in any of the above-mentioned embodiments.

[0270] In another embodiment of the present application, a computer program product including instructions is provided. When the computer program product is run on a computer, the method of the above embodiment is implemented.

[0271] The present application also provides a computer program. When the computer program is executed in a computer, the method of the above embodiment is implemented.

[0272] In another embodiment of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the method described in the above embodiment is implemented.

[0273] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0274] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0275] In several embodiments provided in the present application, the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0277] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0278] If the function is implemented in the form of 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 the embodiment of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0279] The above are only specific implementations of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be based on the protection scope of the claims.

Claims

1. A communication method, characterized in that: include: receiving a first data packet, wherein the data volume of the first data packet in a first scheduling period is greater than a first value; A second data packet is sent, where the second data packet is a data packet obtained by processing the first data packet, and the data volume of the second data packet in the first scheduling period is less than or equal to the first value.

2. The method according to claim 1, characterized in that The second data packet is a data packet obtained by processing the first data packet, including: The second data packet is a data packet obtained by allocating the extra data volume of the first data packet to the second scheduling period, and the extra data volume of the first data packet is the difference between the data volume of the first data packet in the first scheduling period and the first value.

3. The method according to claim 1 or 2, characterized in that: The first value is the maximum amount of data that the network device can schedule in the first scheduling period.

4. The method according to claim 3, characterized in that The method further comprises: The first value is received.

5. The method according to claim 1 or 2, characterized in that: The first value is a ratio of a guaranteed bit rate of the first data packet to a scheduling period of the first data packet.

6. The method according to claim 5, characterized in that The scheduling period of the first data packet is preconfigured.

7. The method according to claim 5, characterized in that The method further comprises: A scheduling period for receiving the first data packet.

8. The method according to any one of claims 2 to 7, characterized in that The first scheduling period is adjacent to the second scheduling period.

9. The method according to any one of claims 5 to 8, characterized in that A ratio of the guaranteed bit rate of the first data packet to the scheduling period of the first data packet is less than or equal to a maximum amount of data that can be scheduled by the network device in the first scheduling period.

10. The method according to any one of claims 2 to 9, characterized in that The first scheduling period is a first multicast transmission channel scheduling period MSP, and the second scheduling period is a second MSP.

11. A communication method, characterized in that: The method comprises: receiving a second data packet, where the second data packet is a data packet obtained by processing the first data packet, the data volume of the first data packet in the first scheduling period is greater than a first value, and the data volume of the second data packet in the first scheduling period is less than or equal to the first value; The second data packet is sent.

12. The method according to claim 11, characterized in that The second data packet is a data packet obtained by processing the first data packet, including: The second data packet is a data packet obtained by allocating the extra data volume of the first data packet to the second scheduling period, and the extra data volume of the first data packet is the difference between the data volume of the first data packet in the first scheduling period and the first value.

13. The method according to claim 11 or 12, characterized in that: The first value is the maximum amount of data that the network device can schedule in the first scheduling period.

14. The method according to claim 13, characterized in that The method further comprises: The first value is sent.

15. The method according to claim 11 or 12, characterized in that: The first value is a ratio of a guaranteed bit rate of the first data packet to a scheduling period of the first data packet.

16. The method according to claim 15, characterized in that The scheduling period of the first data packet is preconfigured.

17. The method according to claim 15, characterized in that The method further comprises: The scheduling period for sending the first data packet.

18. The method according to any one of claims 12 to 17, characterized in that The first scheduling period is adjacent to the second scheduling period.

19. The method according to any one of claims 15 to 18, characterized in that A ratio of the guaranteed bit rate of the first data packet to the scheduling period of the first data packet is less than or equal to a maximum amount of data that can be scheduled by the network device in the first scheduling period.

20. The method according to any one of claims 12 to 19, characterized in that The first scheduling period is a first MSP, and the second scheduling period is a second MSP.

21. A communication system, characterized in that: include: Business management network elements and network equipment; The service management network element is used to receive a first data packet, the data volume of the first data packet in the first scheduling period is greater than a first value; and is also used to send a second data packet to the network device, the second data packet is a data packet obtained after the service management network element processes the first data packet, and the data volume of the second data packet in the first scheduling period is less than or equal to the first value; The network device is used to receive the second data packet; and is also used to send the second data packet.

22. The system according to claim 21, characterized in that It also includes: a mobility management entity network element and a gateway network element; The network device is configured to send the first value to the mobility management entity network element: The mobility management entity network element is used to receive the first value, and to send the first value to the gateway network element; The gateway network element is used to receive the first value, and to send the first value to the service management network element.

23. The system according to claim 21, characterized in that Also includes: Mobility management entity network element and gateway network element; The network device is used to send a scheduling period of the first data packet to the mobility management entity network element: The mobility management entity network element is used to receive the scheduling period of the first data packet, and is used to send the scheduling period of the first data packet to the gateway network element; The gateway network element is used to receive the scheduling period of the first data packet, and to send the scheduling period of the first data packet to the service management network element.

24. A communication device, characterized in that: The method comprises a unit for executing the method according to any one of claims 1 to 10, or comprises a unit for executing the method according to any one of claims 11 to 20.

25. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program or instructions, and when the computer program or the instructions are executed on a computer, the method according to any one of claims 1 to 10 is executed, or the method according to any one of claims 11 to 20 is executed.

26. A computer program product, characterized in that The invention comprises instructions, which, when executed on a computer, cause the method according to any one of claims 1 to 10 to be executed, or cause the method according to any one of claims 11 to 20 to be executed.

Images